CSC 444 project
Phase 2: Architecture, design, and implementation plans

Objective: Based on a SRS, you must create a design document that enables a group of developers to implement your application. Your design document augments your SRS and as such must be traceable to it. The implementation team not always will be your team. Hence, communication is a key objective of the design document.

Your task

Your task is to first make sure your SRS is in accordance to the marking scheme. If not, you must change it through your change management process. In other words, you need to document what is being changed and why according to the change management process. If your change management process is not effective, you must revise it. From this phase on, you will lose marks if your change management process does not support your work.

Analyze the specification requirement document that you created in the phase 1. Based on the analysis, create an architecture description for your system to be implemented. Choose an existing architectural style as desribed in your text book (e.g., Pipe and filter, Three-tier (layered), Abstract data type, Object oriented, Repository, etc). Make sure you decide your architectural style based on a set of criteria chosen by the team! Analyze your specification against your architecture by asking yourself, which component implements a requirement or what the connections between components are with respect to your SRS.

Analyze each component in depth and create a design for each component. This is used as a blue-print for implementing your application (the actual programs). You may use UML, SADT, DFD, Sequence diagrams, and other tools available to you. English prose and customized diagrams are also allowed but note that they may not be a good means of communication. (The marker acts as the person responsible for implementing your design.)

HINT: Later on you may not be able to implement all functionalities stated in the SRS. A solution will be to acquire some functionalities from other teams. Make sure your design has strong components enabling component acquisitions.

Treat this phase as a project on its own. The input to the project is your SRS. Create a WBS. Divide the tasks among team member. Establish team responsibilities. Make sure you use the practical session(s) as your status meeting. (If you don't have a participation session log signed by TA, you will lose part of your marks).

You must also update your risk management as needed. Has any of the risks identified previously changed, its impact changed, or are there any new risks? Change your risk management. Make sure the history is still available. In other words, apply change management process to your risk management document.

What to deliver as a team

1. A cover page stating the names, emails, student numbers of all team members, and your tutorial section.
2. A table of content showing where the following are: change management document, risk management plan, project management reports (TA signed plan documents and the actual documents, e.g. WBS), SRS and its revision history, design document.
3. If you have made any changes to previously submitted documents, you must have a revision history. The original must still be viewable (e.g. cross out fonts, highlights). Furthermore, you must describe why a change is necessary. If you had identified it in your risk management, then state that and make appropriate references.
4. Your phase 1 SRS with all revisions and their history.
5. Your change management process documentation with all revisions and their history.
6. Your risk management plan with all revisions and their history.
7. Singed Work breakdown structure (WBS): create a work breakdown structure with your team members during the practical session and have the TA sign it. If you have already done that prior to the practical session, perform a status meeting, reassess your risk management plan and get TA's signature.
8. If you have deviated from your change process plan, you must include a description as why you made these changes and what changes you made to the process.
9. For the design document, use IEEE Std 1016 as the basis. You should include:
   • Overall architecture: what is your chosen architectural style and briefly justify your selection. Identify each component of your architecture and describe which functionalities are realized by each component. Describe how components interact with one another (i.e. define the edges)
   • For each component describe a detailed analysis as how it realizes the specification. For example, you may use the UML class diagrams, sequence diagrams, and state charts.
   • Describe what the interfaces between components are.

   What to deliver individually

   Each team member must forward an email containing the 360 degree feedback for each team member. Notes:
   • Send one email for each team member to homy at ecf.
   • The subject line must be of the form: 360 degree feedback: YOUR NAME, TEAM MEMBER'S NAME, YOUR LECTURE SECTION

   Due date

   This assignment is due on Tuesday Oct. 21 at 12:00. Please drop your assignment in the assignment drop box in ...

   Marks

   This assignment constitutes 9 percent of your total marks. You will receive 1 mark for practice session participation and 8 marks for your deliverable. During the practice session, you must decide with your team members on what you will deliver. Create a WBS and on your assignment clearly marks what each member performed. If