100 likes | 224 Views
L A B O V E R V I E W Scenario and Summary<br>You have been hired by the School of Prosperity (SoP) as a software architect to help the school plan, design, and implement a new online system called the Student Records System (SRS).<br>The Student Records System (SRS), described in the SRS Preliminary Planning Overview document, is the 7-week-long project that you will work on throughout this course. You will be developing UML models and documents for the planning, design, and implementation phases of SRS development.<br>In each week, you will be provided with the information you need to continue to develop your analysis and design UML models and documents for this project.<br>
E N D
FOR MORE CLASSES VISIT www.cis339guide.com cis 339 guide Peer Educator/cis339guidedotcom
CIS 339 Entire Course (UOP) CIS 339 iLab 1 System Requirements (Devry) • CIS 339iLab 1 System Requirements • CIS 339 iLab 2 of 7 • CIS 339iLab 3 - Structural Modeling - Class Diagram and CRCs • CIS 339iLab 4 - Sequence, Communication, and State Diagrams • CIS 339iLab 5 - Package Diagrams • L A B O V E R V I E W Scenario and Summary • You have been hired by the School of Prosperity (SoP) as a software architect to help the school plan, design, and implement a new online system called the Student Records System (SRS). • The Student Records System (SRS), described in the SRS Preliminary Planning Overview document, is the 7-week-long project that you will work on throughout this course. You will be developing UML models and documents for the planning, design, and implementation phases of SRS development. cis 339 guide Peer Educator/cis339guidedotcom
CIS 339 iLab 2 of 7 (Devry) CIS 339 iLab 3 - Structural Modeling - Class Diagram and CRCs (Devry) • Use Case Diagram and Use Case Description • Work has already started on the planning phase of the Student Record System (SRS) for the School of Prosperity (SoP) and everyone is excited about this new system. • As the software architect of this project, you met with many users and stakeholders of the old system to determine the requirements of the new Internet-accessible SRS software system. Your meetings and requirement-gathering efforts resulted in an SRS Requirement Definition document that summarizes all of the requirements of the project. • As the software architect for the SRS system, you are making good progress in your work. After finishing the Functional Modeling (activity diagram, use case diagram, and use case descriptions) of the SRS system, you are now ready to move on to its Structural Modeling. cis 339 guide Peer Educator/cis339guidedotcom
CIS 339 iLab 4 - Sequence, Communication, and State Diagrams (Devry) CIS 339 iLab 5 - Package Diagrams (Devry) • 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. • Sequence diagram Communication diagram • In addition, you will also need to create a state machine diagram for the Registration class (the class that maintains the registration of a student in a class). • Your analysis phase of the SRS project went well and your team feels good about their Functional, Structural, and Behavioral models. You also discussed the result of your analysis with the School of Prosperity (SoP) administration and they seem to be in line with your analysis models. • Now is the time to start the design phase where you generate specific directions for the implementation of the system by the software development group cis 339 guide Peer Educator/cis339guidedotcom
CIS 339 iLab 6 - CRCs, Contracts, and Method Specifications (Devry) CIS 339 iLab 7 - Object-Oriented Application Coding (Devry) • The design phase of the SRS project is in full swing and every developer on the team is assigned a group of packages to work on and to complete the design details of the classes in the package. To help speed up the design process, you—as the software architect of the project—were assigned the task of providing a samplemethod contract and a sample method specification to demonstrate to your team how these two documents are developed. • Your demonstrations of how to create both method contract and the method specification for the GetCourseByCourseID() method of the CourseList class were very well received by your team members. They then asked you for one final demonstration of how to implement the method specification using an object-oriented (OO) programming language and see the method actually execute. • You realize that it is easy to implement the method specification in an OO programming language, but it is hard to test it because the rest of the application is not developed yet. You decided, therefore, to write two pieces of code. • Code that implements the GetCourseByCourseID() method Code that implements a unit test for that method alone (outside of any other application code) cis 339 guide Peer Educator/cis339guidedotcom
FOR MORE CLASSES VISIT www.cis339guide.com cis 339 guide Peer Educator/cis339guidedotcom