Student Records System (SRS) Week 1 — System Request 3 Week 2 — Use Case Diagram AND Use Cases Descriptions 5 Week 3 — Class Diagram AND CRC Cards 9 Week 4 — Sequence, Communication, and State Machine Diagrams 15 Week 5 — Package Diagram 19 Week 6 — Method Contract AND Method Specification 21 Week 7 — Object-Oriented Application Coding 24 Week 1—System Request 1 Use this system request template and complete the SRS system request. System Request— Name of Project Project sponsor: Name of Project Sponsor Business Need: Short description of business need Business Requirements: Description of business requirements Business Value: Expected value that the system will provide Special Issues or Constraints: Any additional information that may be relevant to the stakeholders 2 Validate and verify that your system request addresses the SRS Preliminary Planning Overview. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week 2—Use Case Diagram and Use Cases Descriptions 1 Generate a use case diagram for all of your use cases, including their actors. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: SRS Use Case Diagram Use this use case description template and complete the two SRS use cases of (1) Maintain Class Records and (2) Register a Student for Classes. Maintain Class Records Use Case Name: ID: Importance Level: Primary Actor: Use Case Type: Stakeholders and Interests: Brief Description: Trigger: Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events: 1. SubFlows: Alternate/Exceptional Flows: 2 Validate and verify your use case diagram and use case descriptions against the SRS Requirement Definition and the SRS System Request. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week 3—Class Diagram and CRC Cards 1 Generate a class diagram for the SRS system. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: SRS Class Diagram Use this CRC template and complete a CRC card for each class you designed in your SRS class diagram. Class1 CRC Card Front: Class Name: ID: Type: Description: Associated Use Cases: Responsibilities Collaborators Back: Attributes: Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations: Class2 CRC Card Front: Class Name: ID: Type: Description: Associated Use Cases: Responsibilities Collaborators Back: Attributes: Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations: Class3 CRC Card Front: Class Name: ID: Type: Description: Associated Use Cases: Responsibilities Collaborators Back: Attributes: Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations: Class4 CRC Card Back: Class Name: ID: Type: Description: Associated Use Cases: Responsibilities Collaborators Back: Attributes: Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations: 2 Validate and verify your class diagram and CRC cards against the SRS use case diagram and use case descriptions. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week 4—Sequence, Communication, and State Machine Diagrams 1 Generate a sequence diagram for the SRS system Register a Student for Classes use case. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: Sequence Diagram for the Register a Student for Classes Use Case Generate a communication diagram for the SRS system Register a Student for Classes use case. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: Communication Diagram for the Register a Student for Classes Use Case Generate a state machine diagram for the SRS system RegistrationRecord object/class (the class that maintains the registration of a student in a class). The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: State Machine Diagram for the RegistrationRecord Object 2 Validate and verify your behavioral diagrams against the SRS Register a Student for Classes use case description and the SRS class diagram. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week 5—Package Diagram 1 Generate a package diagram for the SRS system. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: SRS Package Diagram 2 Validate and verify your package diagrams against the SRS class diagram and the SRS Register a Student for Classes use case sequence and communication diagrams. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week 6—Method Contract and Method Specification 1 Use this method contract template and complete a method contract for the GetCourseByCourseID() method of the CourseList class. CourseList.GetCourseByCourseID() Method Contract Method Name: Class Name: ID: Clients (Consumers): Associated Use Cases: Description of Responsibilities: Arguments Received: Type of Value Returned: Pre-Conditions:: Post-Conditions: Use this method specification template and complete a method specification for the GetCourseByCourseID() method of the CourseList class. CourseList.GetCourseByCourseID() Method Specification Method Name: Class Name: ID: Contract ID: Programmer: Date Due: Programming Language: Visual Basic Smalltalk C# Java Triggers/Events: Arguments Received: Data Type: Notes: Messages Sent & Arguments Passed: ClassName.MethodName: Data Type: Notes: Argument Returned: Data Type: Notes: Algorithm Specification: Misc.Notes: 2 Validate and verify your method contract and method specification against the CRC card for the CourseList class and the CRC card for the Course class. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week 7—Object-Oriented Application Coding 1 Copy your code text of the CourseList.GetCourseByCourseID() method and paste it here: Code Text of Your CourseList.GetCourseByCourseID() Method Copy a screenshot of running the unit test of the CourseList.GetCourseByCourseID() method and paste it here: Screenshot of running the Unit Test of CourseList.GetCourseByCourseID() Method Zip all the files you used in this coding project; copy and paste the .zip file here so that it can be unzipped and loaded into the IDE and run on another computer: A .zip File of all of the Coding Project Files 2 Validate and verify your code and screenshot of the CourseList.GetCourseByCourseID() method against the method contract and the method specification of the same method. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. 26 of 26 Scenario/Summary You are deep into the analysis phase of your Internet-accessible Student Records System (SRS). You have finished both the Functional Modeling (activity diagram, use case diagram, and use case description) and the Structural Modeling (class diagram and the CRC cards). Now you are ready to move into the Behavioral Modeling where you will model the behavior or the objects that make up the SRS system. In this week, you will use your functional and structural models as the basis for your behavioral models that need to be developed for the SRS system. Specifically, your deliverables for this week are designed to develop these two behavioral diagrams for the Register a Student for Classes use case. 1 Sequence diagram 2 Communication diagram In addition, you will also need to create a state machine diagram for the RegistrationRecord class (the class that maintains the registration of a student in a class). These behavioral model and diagrams are major milestones in your architectural and design work. They give you your first opportunity to verify that the use case (in this case, Register a Student for Classes) could actually be implemented using the objects of your class diagram design. If you reach this verification, then you are done with the analysis phase of your SRS project. Deliverables NOTE Submit your assignment to the Dropbox, located at the top of this page. For instructions on how to use the Dropbox, read these step-by-step instructions . (See the Syllabus section "Due Dates for Assignments & Exams" for due dates.) 1 Sequence diagram for the Register a Student for Classes use case 2 Communication diagram for the Register a Student for Classes use case 3 State Machine diagram for a RegistrationRecord object 4 Verification and validation of your work 5 Explanation of your work Remember This! Connect to the iLab here . Lab Steps STEP 1: Review Starting RSA on Citrix, Drawing a Sequence Diagram, Drawing a Communication Diagram, and Drawing a StateMachine Diagram (Not Graded) 1 The video tutorial below demonstrates how to start the IBM Rational Software Architect (RSA) in the Citrix iLab environment. Starting Rational Software Architect 2 The video tutorial below demonstrates how to draw a Sequence diagram using RSA. Drawing a Sequence Diagram with Rational Software Architect 3 The video tutorial below demonstrates how to draw a Communication diagram using RSA. Drawing a Communication Diagram with Rational Software Architect 4 The video tutorial below demonstrates how to draw a State Machine diagram using RSA. Drawing a State Machine Diagram with Rational Software Architect STEP 2: Generate the Sequence Diagram 1 Dowload the iLabWeeklySubmissionTemplate. You are going to use this template for all of your iLab submissions throughout this course. This template is available in week1 iLab. 2 Create a sequence diagram for the Register a Student for Classes use case using the Rational Software Architect software in the Citrix iLab environment based on your functional and structural models 3 Using the iLabWeeklySubmissionTemplate, copy and paste your sequence diagram into the template. STEP 3: Generate a Communication Diagram 1 Create a communication diagram for the Register a Student for Classes use case using the Rational Software Architect software in the Citrix iLab environment based on your functional and structural models. 2 Using the iLabWeeklySubmissionTemplate, copy and paste your communication diagram into the template. STEP 4: Generate an Object State Diagram 1 Create a state machine diagram for an object of the RegistrationRecord class (the class that maintains the registration of a student in a class) using the Rational Software Architect software in the Citrix iLab environment based on your functional and structural models. 2 Using the iLabWeeklySubmissionTemplate, copy and paste your object state diagram into the template. STEP 5: Verify, Validate, & Explain Your Work 1 Using the iLabWeeklySubmissionTemplate, verify and validate your work 2 Using the iLabWeeklySubmissionTemplate, explain your work, the decisions you made to arrive at your proposed solution, and lessons learned. STEP 6: Upload your iLabWeeklySubmissionTemplate Document to your Dropbox Save the iLabWeeklySubmissionTemplate MS Word document with the file name iLabWeeklySubmissionTemplate_YourName and upload to your Dropbox.
