100 likes | 116 Views
FOR MORE CLASSES VISIT <br>www.cis339master.com <br>CIS 339iLab 1 System Requirements<br>CIS 339 iLab 2 of 7<br>CIS 339iLab 3 - Structural Modeling - Class Diagram and CRCs<br>CIS 339iLab 4 - Sequence, Communication, and State Diagrams<br>CIS 339iLab 5 - Package Diagrams<br>CIS 339iLab 6 - CRCs, Contracts, and Method Specifications<br>CIS 339iLab 7 - Object-Oriented Application Coding<br>
E N D
CIS 339 master Perfect Education/cis339master.com FOR MORE CLASSES VISIT www.cis339master.com
CIS 339 Entire Course (UOP) • 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 • CIS 339iLab 6 - CRCs, Contracts, and Method Specifications
CIS 339 iLab 1 System Requirements (Devry) • 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).
CIS 339 iLab 2 of 7 (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.
CIS 339 iLab 3 - Structural Modeling - Class Diagram and CRCs (Devry) • 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. • In this week, you will use the models of your Functional Modeling to determine and design your class diagram and complete a CRC card for each class. The Structural Modeling is very critical for the success of your project since it is the backbone upon which the entire project is built, so take the time to design and refine your class diagram and its corresponding CRC cards.
CIS 339 iLab 4 - Sequence, Communication, and State 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
CIS 339 iLab 5 - Package Diagrams (Devry) • 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. The first step in the design phase is to examine the SRS class diagram and to try to simplify its organization using a package diagram. The package diagram ensures that classes that belong together are grouped into a single package and thus simplify the development of these classes and their maintenance.
CIS 339 iLab 6 - CRCs, Contracts, and Method Specifications (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 sample • method contract and a sample method specification to demonstrate to your team how these two documents are developed.
CIS 339 iLab 7 - Object-Oriented Application Coding (Devry) • 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.
CIS 339 master Perfect Education/cis339master.com FOR MORE CLASSES VISIT www.cis339master.com