PROJECT REPORT DESCRIPTION You will use an iterative software development process (UP) for this project. We have discussed this process in class and described the differences between iterative and waterfall process. You will do two iterations of analysis, design, and implementation for this project. In addition to the two iterations, you will be given testing requirements to conduct verification on your software. Teams are expected to develop their respective modules based on the Unified Process Systems Development Life Cycle concepts (Inception, Elaboration and Construction which includes the business modeling, requirement definition, analysis, design and implementation activities, but excludes Transition). Planning for each iteration is needed. Planning means that the team (1) identify activities to be completed during this iteration (2) identify team member(s) responsible for those activities and (3) establish deadlines for completion of those activities. Be certain to allocate enough time in establishing deadlines so that the person(s) having primary responsibility for an activity can complete a draft version that can be checked by at least one other group member. It is also a good idea to allow yourselves several days before the delivery date for final packaging of the material to be submitted. The deliverables are due on dates specified below. They will not be accepted late unless I give extension to all teams. A team member should identify his/her contributions for each task mentioned below. You should meet with your team members and discuss before you submit your team deliverables. It is NOT ACCEPTABLE to work on these deliverables individually and then combine them later without discussing it with your team members. The rough timeline for various deliverable are as follows: First Iteration (due February 23rd): 1. Create a vision to summary your project 2. Choose three to four use Cases (each use case should include one success and one failure scenarios), provide full-dressed descriptions. Each scenario should discuss a different use of your system. 3. Draw use Case Diagram to include actors and those use cases your team discovers during the first iteration. 4. Put other non-functional requirements in supplementary specification document 5. Create a simple document for glossary which includes those terms and descriptions used in your project 6. Create domain model by studying those use cases you describe in this iteration. You should use noun phase approach (noun extraction). The domain model should include a. Conceptual classes, attributes, and associations for all actors from your use case submission.b. Multiplicity of associations should be specified 7. Draw System Sequence diagrams and operation contracts for each use case (you describe in this iteration) 8. Develop the design models for this iteration of the project including both static Design Class Diagrams and dynamic Interaction Diagrams (Sequence Diagrams). For Sequence diagram, there should be a. Separate system sequence diagrams for each use case scenario. b. Primary and secondary actors should be shown wherever necessary. c. Correspondence between the use case scenario and system sequence diagrams should be made explicit. For example, one can label the system sequence diagram as "Main Success Scenario", where "Main Success Scenario" is a use case scenario. d. All success and one failure scenarios should be present. 9. Implement those functions described by those use cases you choose for this iteration Second Iteration (due March16th): 1. Revise the vision as necessary 2. Choose the rest use cases (each use case should include one success and one failure scenarios), to provide full-dressed descriptions. Each scenario should discuss a different use of your system. 3. Revise the use case diagram to include those use cases which have not been discovered during the first iteration. 4. Add additional non-functional requirements in supplementary specification document as necessary 5. Add those new terms you found during this iteration into glossary 6. Modify/revise the domain model and add new domain concepts to the model as needed 7. Draw System Sequence diagrams and operation contracts for each use case (you describe in this iteration) 8. Modify/revise the design models for this iteration of the project including both static Design Class Diagrams and dynamic Interaction Diagrams (Sequence Diagrams). You need to draw the sequence diagrams for those use cases you found in this iteration. 9. Implement those functions described by those use cases you choose for this iteration and complete the implementation for this project. Last Part: Testing (Due: March 30th, 2014) I will provide the testing requirements during last two weeks.Your project report should be structured in the following fashion: Project Title Project Group Member Name, Project Group Member Name … (Student ID) Part 1: Iteration 1 1. Vision 2. Use Case Modelling a. Use case diagrams b. Use case description c. System Sequence Diagrams d. Operation Contracts 3. Domain Modelling 4. Class Modelling and Dynamic Modelling a. Class diagram b. Sequence diagrams 5. Implementation Part 2: Iteration 2 1. Vision 2. Use Case Modelling a. Use case diagrams b. Use case description c. System Sequence Diagrams d. Operation Contracts 3. Domain Modelling 4. Class Modelling and Dynamic Modelling a. Class diagram b. Sequence diagrams 5. Implementation Part 3: Testing Appendix 1: Supplementary Specification Appendix 2: Glossary Appendix 3: Annotated screen shots of your working system. Grading 1. Vision 2. Use Case Modelling (30%) a. Use case diagramsb. Use case description c. System Sequence Diagrams d. Operation Contracts 3. Domain Modelling (5%) 4. Class Modelling and Dynamic Modelling (20%) a. Class diagram b. Sequence diagrams 5. Implementation (40%) 6. Testing (5%) Submission The final report must be professionally prepared and organized, containing all the earlier deliverables as well as supplementary materials, if available. You should also provide a sheet to show the percentage of work done by EACH member for EACH major document. The final report should be systematically organized in a ring-binded report document. The electronic copy for all documents (including the source code) should be saved on a CD or USB and submitted together with the project documentation.