Red flags are statements of concern, things that need to be taken care of if the project is to succeed. Most red flags are threats of various kinds. It is important both to state the flag and to declare an action to take care of it.
(1) Code for the ls command must be changed to represent changes made in the command interpreter.
(2) Output redirection does not save the output to the desired file.
When a red flag is resolved, move it into this section at the next report, and drop it from this section at the report after that.
(1) mv command can only move file object down the file system structure.
(2) Code for all of the file system files must be changed to represent changes make in the command interpreter.
(3) More work needs to be done on the file system and parser to make the command interpreter all work together properly as one unit.
Each promise consists of a person responsible, the condition of satisfaction, and the due date. The table provides extra columns to state the actual completion date and when it was due.
| Responsibility | Assignment | Planned Date | Actual Date | Due Date |
| Team | Baseline simulator works (+ pipes, I/O redirection) | 3/26/01 | 3/28/01 | 3/28/01 |
| Team | Enhanced OS | 4/9/01 | 4/11/01 | |
| Team | Whole simulator works; draft report URL submitted | 4/9/01 | 4/11/01 | |
| John | Project URL delivered | 4/21/01 | 4/23/01 | |
| Team | Exihibition | 5/1/01 | 5/1/01 |
When a promise is completed it is moved to this section.
| Responsibility | Assignment | Planned Date | Actual Date | Due Date |
| Team | Form team | 1/17/01 | 1/17/01 | 1/17/01 |
| Team | Select team leader | 1/24/01 | 1/22/01 | |
| Ely | Create Console Window | 1/24/01 | 1/24/01 | 1/31/01 |
| Ely | Console window operational | 1/29/01 | 1/27/01 | 1/31/01 |
| John | System Specifications | 2/12/01 | 2/12/01 | 2/14/01 |
| Dennis | Prototype Parser Works | 2/12/01 | 2/13/01 | 2/14/01 |
| John & Ely | Testing and Understanding of Parser | 2/12/01 | 2/13/01 | 2/14/01 |
| John | File System(all but mv) | 2/26/01 | 2/27/01 | 2/28/01 |
| John | 'cat' function operational | 2/26/01 | 2/27/01 | 2/28/01 |
| Dennis & Ely | Testing and Understanding of File System | 2/26/01 | 2/28/01 | 2/28/01 |
| John | mv command | 3/12/01 | 3/18/01 | 2/28/01 |
| Team | Set up meeting with Professor Denning | 3/14/01 | 3/19/01 | 3/14/01 |
| Ely | Command interpreter operational | 3/12/01 | 3/12/01 | 3/14/01 |
| Dennis | Parser Revisions | 3/12/01 | 3/28/01 | 2/14/01 |
Baseline simulator (+ pipes, I/O redirection):
The baseline simulator is operational. However, we did not have the time resources to successfully finish the implementation of piping. Input and output redirection work for our simulator, with the condition that the output for output redirection is not put in the /usr directory, rather in the /bin directory. This is a minor bug, and it will be fixed in the very near future. With time against us, we could not finalize piping, but the framework is in place. With a little bit of effort piping will be complete, and the baseline simulator will meet specifications. We are pleased with the progress of the project and do not anticipate any significant trouble spots. With a little bit more time, all of the specifications will be met.
It is very difficult to show the output for several reasons. You cannot prove that it is working through screen shots but I hope this is enough. It is especially difficult because the output redirection puts the file in a directory that we cannot use ls on. Below is a series of screen shots to show what files exist and shows the new file: final.txt and its contents.
cat.java
cd.java
ConsoleWindow.java
edit.java
date.java
FileClassLoader.java
Handle.java
help.java
KeyboardBuffer.java
listproc.java
login.java
logout.java
ls.java
mkdir.java
mv.java
newusr.java
Osvm.java
pass
Parser.java
receive.java
rm.java
rmdir.java
send.java
shell.java
Sysapi.java
User.java
VMachine.java
Contents | PAR #1 | PAR #2 | PAR #3 | PAR #4 | PAR #5 | PAR #6