CIS 339 All iLabs Week 1 to Week 6

iLab 1 of 7: System Request

iLab 2 of 7: Case Description, Case Diagram

CIS 339 iLab 3 – Structural Modeling – Class Diagram and CRCs

CIS 339 iLab 4 – Sequence, Communication, and State Diagrams

CIS 339 iLab 5 – Package Diagrams

CIS 339 iLab 6 – CRCs, Contracts, and Method Specifications

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 2 of 7

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.

One of your development team members was excited about this
project and wanted to start working on it immediately. She therefore took the
initiative and created a high-level business process activity diagram for the
SRS system. You reviewed the activity diagram and found it to be a good
foundation from which to create the SRS use case diagram and the SRS use case
descriptions.

There is still work to be done to complete the Functional
Modeling of the SRS. Your deliverables for this week’s iLab are the SRS use
case diagram and two use case descriptions for the Maintain Class Records and
the ter a Student for Classes use cases.

Deliverables

SRS use case diagram Use case descriptions for the Maintain
Class Records and ter a Student for Classes use casesSTEP 2: Generate the
Use Case Diagram

Download the SRS Requirement Definition and review it to
prepare for your deliverables this week.Download the SRS Business Process
Activity Diagram and review it to prepare for your deliverables this
week.Download the Use Case Description Template and use it for your
deliverables this week.Create the use case diagram for the SRS system using the
Rational Software Architect software on the Citrix iLab environment. Pay
attention to the possible need for Include and Extends relationships.Explain
your work and the decisions you made to arrive at your proposed solution.STEP
3: Generate the Use Case Descriptions

Create use case descriptions for the two major use cases in
the SRS system. These two major use cases are the Maintain Class Records and
the ter a Student for Classes use cases. See the Figure 5-5 example in the
text.Explain your work and the decisions you made to arrive at your proposed
solution.STEP 4: Copy the Diagram Into an MS Word document

Be sure to include all deliverables in one Word document.
Copy and paste the use case diagram into the same Word document that contains
the use case descriptions. Save your document with the file name CIS
339_Lab2_YourName.

CIS
339 iLab 3

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

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 ter a Student for Classes
use case.

Sequence diagram Communication diagram

In addition, you will also need to create a state machine
diagram for the tration 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, ter 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 ter a Student for
Classes use case Communication diagram for the ter a Student for Classes
use case State Machine diagram for a tration object

STEP 2: Create the Sequence Diagram

Create a sequence diagram for the ter 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

CIS
339 iLab 5

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.

CIS
339 iLab 6

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.

You decided to use the CourseList and the Course classes for
your demonstrations. The CourseList class maintains and populates the current
list of courses that the end user is working with while registering for clases.
You will demonstrate the contract and the specification of the GetCourseByCourseID()
of the CourseList class.

The GetCourseByCourseID() method searches the current list
of courses for a course whose CourseID matches the ID supplied to the method.
If a matched course is found, it is returned by the GetCourseByCourseID()
method; otherwise a null value is returned, indicating there are no matching
courses.

Method contract of the GetCourseByCourseID() method of the
CourseList class Method specification of the GetCourseByCourseID() method of
the CourseList class

i L A B S T E P S

STEP 1:
Create a Public Method ContractDownload the CRC Cards for the CourseList
and Course classes and review them to prepare for your deliverables this week.
Download the Method Contract Template and use it for your deliverables this
week. Create the method contract for the GetCourseByCourseID() method of the
CourseList class. Explain your work and the decisions you made to arrive at
your proposed solution.

STEP 2:Create a Method SpecificationDownload the Method
Specification Template and use it for your deliverables this week. Create the
method specification for the GetCourseByCourseID() method of the CourseList
class. Explain your work and the decisions you made to arrive at your proposed
solution.

STEP 3:Save and Upload