TEMPO PERSONAL ORGANISER
Joe Parman
Matt Thompson
Steve Ellis
Olivier Orand
Nolan Harley
As part of my third year cousre of 'Projects and Their Management' we were
put into a group of five people and given the following problem:
specify, design, implement and document a program to provide the functions
of a personal organizer. In outline, this organizer should be able to record
one-off diary entries, anniversaries, regular events, absences, to-do lists,
addresses, temporary notes and permanent information. It should also be possible
to search and link all of this information in various ways.
Your task is to
Submission requirements
The documents submitted for each of the two milestones must:
Have a front page identifying the group and the group members.
Have a clear front cover and a card back cover.
Separate the parts with tabbed dividers.
Be spiral bound.
Milestones
The first milestone is due on Wednesday March 17.
This submission should comprise a single document in four parts, as follows:
Project plan: The project plan should identify the resources available to the group, explain how the group will be managed, the quality assurance procedures to be applied, coding standards, the verification and validation plan, and the scheduling of the project. Remember that the object of verification is to establish that the program is working reliably and validation to establish that the system is as the customer desired (according to the requirements definition). The project schedule, should be presented in terms of milestones and a Gannt chart.
Requirements document: This comprises the requirements definition and specification, both of which should be agreed with the supervisor relatively early on in the project. It should have the following structure: introduction, system model, functional requirements definition, functional requirements specification, hardware requirements, database requirements, non-functional requirements definition and specification, and possibly a glossary and an index. (Note: this organisation merges elements of the requirements definition and the requirements specification into a single document, being more in keeping with the scale of the project.)
Draft user manual: We practice a methodology called user manual first in this unit, where you have to write the draft user manual before writing the system. See the heading User documentation under the second milestone.
Top-level design document: This comprises the software design, using a suitable formal design notation, the user interface design, using a state diagram, and the database specification, using entity-relationship diagrams.
The second milestone is due on Wednesday May 12.
This submission should comprise a single document in four parts plus a floppy disk containing
the software package ready for installation:
Project overview: This should be a short section which ties together all the other sections in this milestone, indicating clearly how the work was divided up amongst the individual group members, and covering any additional aspects of the project that the team wishes to report. This section should also include the Project log and the Project critique. The latter should be a review of the system, highlighting how you would now do things differently, what additional functionality you would include and an outline of how it might be implemented.
User documentation: This comprises a functional description, installation guide, introductory manual and reference manual.
Test plan: This should cover the plan for testing of program components, integration and final acceptance. It does not include test results (see next section).
Program listing and program documentation: The program documentation is something separate from the comments in the code itself: it should take the reader through the program, identifying the main data structures used and make clear the overall program structure. It should act as the basis for a maintenance document, inasmuch as the reader should be able to work out where to start making appropriate changes. The test results form part of the program documentation.
The Following Documents are also available that accompanied the Final Project: