Version History Date Author Version Changes made Rationale 10/16/2013 Qianu Liao 1.0 System Context Diagram Consolidated System Context Diagram to match OCD 10/17/2013 Qianyu Liao 1.1 System Users Behavior Consolidated System Users Behavior to match OCD 10/17/2013 Qianyu Liao 1.2 System Use Case Consolidated use to match OCD 10/18/2013 Qianyu Liao 1.3 System Use Case Consolidated use to match OCD 10/18/2013 Qianyu Liao 1.4 System Use Case Consolidated use cases to match OCD 10/18/2013 Qianyu Liao 1.5 System physical architecture Consolidated use cases to match the clients requirement 10/19/2013 Qianyu Liao 1.6 Add Survey Monkey to System Context Diagram Added System Context Diagram to match Client Requirement 10/20/2013 Qianyu Liao 2.1 Reduce Use Case Reduced use cases to match ARB Review 11/20/2013 Qianyu Liao 2.2 Modify use case, physical architecture Modified use cases and physical architecture to match DCR Review 11/27/2013 Qianyu Liao 2.3 Rewrite the SSAD Rewrite the SSAD document to match the DCR Review and prepare for the development phase 11/28/2013 Qianyu Liao 2.4 Modify Artifact and Information Diagram To satisfy the requirement 12/09/2013 Qianyu Liao 2.5 Add the NDI/NCS evaluation part to SSAD To complete the SSAD 02/09/2014 Ye Tao 3.0 Update Artifact and Information Diagram and System Behavior To comply with the system requirement 02/17/2014 Ye Tao 3.1 Update Artifact and Information Diagram and System Behavior To comply with the system requirement
Introduction Purpose of the SSAD The purpose of the SSAD is to document the results of the object-oriented analysis and design (OOA&D) of the website being developed. The SSAD is used by the developer as reference to the system architecture. The website being developed should be faithful to the architecture specified in the SSAD. Furthermore, the SSAD is used by the maintainer and clients to help understand the structure of the system once the proposed website is delivered. Status of the SSAD The current version of the SSAD is 3.0 and it is at the end of the Rebaselined Foundation At this point, all sections of the document are filled out with system context diagram, system behavior diagram, use case diagram, component diagram, deployment diagram, class diagram and sequence diagram. Team is actively exploring NDI, NCS and the selected architecture (3-tier architecture) and prototyping the system using it. Thus this document reflects current understanding of the developing system and the high risk features, and is an agreement with current prototype.
Updates the answer in the temporary storage file. Typical Course of Action -2 1 Displays a question with multiple choice (multiple answer) 2 Clicks a collection of the answers 3 The answers are chosen. Updates the answer in the temporary storage file Typical Course of Action -3 1 Displays a comment question with an edit box 2 Types in comments in the edit box 3 Updates the answer in the temporary storage file Typical Course of Action -4 1 Displays a tally question with a number, a plus and a minus mark 2 Clicks on plus or minus 3 Updates the answer in the temporary storage file Exceptional Course of Action -1 1 Click the function bar 2 Display a function menu including show map, save, quit without saving and submit 3 Click one of these choices 4 Jump to execute corresponding feature Exceptional Course of Action -2 1 category button 2 Jump to question category list Table : Use Case Description Identifier UC-9-2: User navigates in the category list. Pre-conditions The system shows a question category list of the selected survey. Post-conditions The system jumps into the selected question page. Typical Course of Action Actor Input System Response 1 Display a question category list 2 Click a question type (Block/Tally/Other)