Assignment#2

Due Date: Tuesday, March 8 (at start of lab)

In this assignment you are (teams of 5) to write an approximately 15 - 20 pages long System Design Document (SDD) for the project your group has chosen. Download the following template (System Design Document). Use this template as a guideline for the tasks that need to be done for this assignment. The format (fonts, etc) of this template is not consistent, so make sure the format of your final document is consistent.

Start by meeting with your group members and distributing the work. Each person's work should be reviewed by at least one other person in the group, and be prepared to merge and check your work with other group members. At the end, the document must be consistent in terms of formatting and, more importantly, concepts used throughout the document. On March 8 (at start of lab), hand in your document (printed version), ALONG WITH the REVISED Requirements Analysis Document, enclosed in a binder.

IMPORTANT NOTES:

• There is a lot of work involved, so please do not underestimate and start ASAP.
• The System Design Document template contains questions. The goal of these questions is to help you think about your system and what related material go into each section. In other words, DO NOT leave the questions in the document. REPLACE all text in each section/subsection with material related to your system.
• Some of the subsections in the system design document are relevant to client/server and web-based systems. These are very relevant to the project you are working on.
• In this assignment, pretend you are the 'system designer' and you need to communicate via the system design document your system design (subsystems, components, how the system will be deployed, etc) to those who will implement the system. Do not assume you will do the implementation of the system yourselves.

Marking Scheme: you will be marked out of 50 according to the following scheme:

• 3 marks: spelling (use a spell checker)
• 4 marks: aimed at the correct audience and understandable by them
• 5 marks: concentration on architecture and system design and not implementation details
• 6 marks: precise description of the design goals and trade-offs. Make sure they are clearly stated
• 11 marks: description of the architecture, subsystems, and physical architecture of the system using packages, component diagrams, deployment diagrams (make sure you show dependencies)
• 6 marks: clear description and explanation of other issues (e.g. concurrency, access control, boundary conditions, etc)
• 4 marks: design rationale. Describe why certain decisions were made
• 4 marks: consistent terms throughout the document. Make sure all terms used by different team members are consistent. Consider adding new terms to the Glossary of Assignment#1 and moving that Glossary to the end of this document. Make sure you hand in the revised Requirements Analysis Document.
• 7 marks: description of changes (and the actual changes) made to the Requirements Analysis Document in the appropriate place (e.g. revision history).

If you have any questions, please see me during my office hours or make an appointment.

Note on sending questions via email: Allow two working days (weekend not counted) to receive a reply to your question.