Lab OverviewScenario/SummaryYou 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 di

Lab Overview

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 your 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

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.
6. Name of each member of your team and how they participated. 

STEP 2: Generate the Sequence Diagram

1. Dowload the LabWeeklySubmissionTemplate. You are going to use this template for all of your Lab submissions throughout this course. This template is available in week1 Lab.
2. Create a sequence diagram for the Register a Student for Classes use case using the Rational Software Architect software in the Citrix Lab environment based on your functional and structural models
3. Using the LabWeeklySubmissionTemplate, 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 Lab environment based on your functional and structural models.
2. Using the LabWeeklySubmissionTemplate, 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 Lab environment based on your functional and structural models.
2. Using the LabWeeklySubmissionTemplate, copy and paste your object state diagram into the template.

STEP 5: Verify, Validate, & Explain Your Work

1. Using the LabWeeklySubmissionTemplate, verify and validate your work
2. Using the LabWeeklySubmissionTemplate, explain your work, the decisions you made to arrive at your proposed solution, and lessons learned.