CIS 339 DEVRY Course Tutorial / cis339dotcom

CIS 339 Entire Course (UOP)

For more course tutorials visit

www.cis339.com

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 339iLab 7 — Object-Oriented Application Coding

…………………………………………………………………………………………………………………

CIS 339 iLab 1 System Requirements (Devry)

For more course tutorials visit

www.cis339.com

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.

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.

In this very first week, you will develop the System Request document that articulates the business needs and values of the SRS. The Sop school is excited about this project and allowed you to ask them five questions to clarify project issues for you about the SRS project. You are to include these five questions in your submitted System Request.

Deliverables

Complete the System Request Form for the SRS, including your five questions.

I L A B S T E P S

STEP 1: Review Starting RSA on Citrix (not graded)

The video tutorial below demonstrates how to start the IBM Rational Software Architect (RSA) in the Citrix lab environment.

Starting Rational Software Architect

STEP 2: Download and Complete the System Request Form

Download the SRS — Preliminary Planning Overview and review it to prepare for your System Request Form. Download the System Request Template. Complete the System Request Form for the SRS based on your review of the SRS — Preliminary Planning Overview. See the Figure 2–13 example in the text. As you create the System Request, generate and document at least five questions and specify who you think the best point of contact might be for each question. Explain your work and the decisions you made to arrive at your proposed solution.

STEP 3: Upload the Document to your Drop box

Save the System Request Form MS Word document with the file name CIS 339_Lab1_YourName.

Student Records System SRS — Preliminary Planning Overview

The School of Prosperity (Sop) is a small Information Technology & Science school located in the nation’s capital of Washington, D.C. The school serves a growing student population of about 5000 students by offering programs leading to the Bachelor and Master degrees in IT and Software development.

SoP has, traditionally, offered most of its classes in a face-to-face modality. Recently and because of the increased demands of student enrollments, the school started to offer some of its classes online as well.

The school staff currently uses an in-house desktop application to keep track of students, courses, and to register students for classes. School staff has to be physically in the office in order to access the in-house application. To register for a class (either face-to-face or online class), a student must complete a paper registration form, submit it to the school staff, and the staff will then enter the registration information into the desktop application.

This process always generates many errors in moving from the paper form to the electronic registration filing. Moreover, since there are so many add/drops at the beginning of each semester, the school staff experiences a higher than normal work volume handling these add/drop forms preventing them for completing other tasks allocated to them like staff development and training.

To keep up with the high demands of increased enrollments and to allow students to handle their own registrations online, SoP decided to invest in a new Internet-accessible Student Record System dubbed SRS.

The SRS is to maintain records for students enrolled in the school, courses offered by the school, classes offered of these courses in the two modalities of online and face-to-face, and student grades for the classes that they have completed. The SRS should be Internet-accessible and thus allows students to self-register directly for their own classes and allows the staff to work from any location that has an Internet connection and a web browser.

System Request –??? Project

Project sponsor:

Business Need:

Business Requirements:

The functionality that the system should have is listed below:

Business Value:

Conservative estimates of tangible value to the company includes:

Special Issues or Constraints:

Questions

#

Question

Who to Ask?

1.

2.

3.

4.

5.

………………………………………………………………………………………………………………………

CIS 339 iLab 3 — Structural Modeling — Class Diagram and CRCs (Devry)

For more course tutorials visit

www.cis339.com

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.

Deliverables

Class diagram for the SRS system

CRC cards for each class in your class diagram

STEP 2: Create the Class Diagram

Download the CRC Card Template and use it for your deliverables this week. (Attached)

Explain your work and the decisions you made to arrive at your proposed solution.

STEP 3: Complete the CRC Cards

Create CRC cards for each class that you designed in your class diagrams, ensuring that you identify all appropriate attributes, operations, relationships (including types), responsibilities, and collaborations. Be sure that you complete the front and back of each card. Be sure that your CRC cards exactly reflect what you created in your class diagrams.

Explain your work and the decisions you made to arrive at your proposed solution.

STEP 4: Copy the Diagram into an MS Word document

…………………………………………………………………………………………………………………………

CIS 339 iLab 4 — Sequence, Communication, and State Diagrams (Devry)

For more course tutorials visit

www.cis339.com

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).

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 Sequence diagram for the Register a Student for Classes use case Communication diagram for the Register a Student for Classes use case State Machine diagram for a Registration object

STEP 2: Create the Sequence Diagram

Create a sequence diagram for the Register a Student for Classes use case using the Rational Software Architect software in the Citrix iLab environment. Explain your work and the decisions you made to arrive at your proposed solution.

STEP 3: Create a Communication Diagram

Create a communication diagram for the Register a Student for Classes use case using the Rational Software Architect software in the Citrix iLab environment. Explain your work and the decisions you made to arrive at your proposed solution.

STEP 4: Create an Object State Diagram

Create a state machine diagram for an object of the Registration class (the class that maintains the registration of a student in a class) using the Rational Software Architect software in the Citrix iLab environment. Explain your work and the decisions you made to arrive at your proposed solution.

STEP 5: Save and Upload the Project

……………………………………………………………………………………………………………………

CIS 339 iLab 5 — Package Diagrams (Devry)

For more course tutorials visit

www.cis339.com

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.

Your deliverable this week is to generate a package diagram for the SRS system.

· Create a package diagram of the SRS system (to simplify the SRS class diagram) using the Rational Software Architect software on the Citrix iLab environment.

· Explain your work and the decisions you made to arrive at your proposed solution.

Like what you read? Give takeita.lllwithyouswitchbetween a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.