cis339-blog

[cis339-blog]

CIS 339 iLab 7 Object Oriented Application Coding

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) This way you can demonstrate the method implementation and also verify its correct behavior.

You are under a deadline constraint for this deliverable, so you asked some of your peer architects for help. They each are well versed in different OO languages like VB.NET, C#, and Java and they all have done unit testing before so they are familiar of how to construct one.

Your peer architects provided you with partially-completed shells for your demonstration. Each shell contains:

complete code for the Course class; partially completed code for CourseList class; and complete code for the CourseListTest class that unit tests the CourseList.GetCourseByCourseID() method.

Your task is now easy. Just select one of these shells and complete the code for the partially completed CourseList by coding it GetCourseByCourseID() method. When you compile and run the shell, it will automatically test your GetCourseByCourseID() code to ensure its correct behavior.

Deliverables One Word file that contains the following. A copy of the code you wrote for the GetCourseByCourseID method() of the CourseList class in your favorite OO programming language A screen shot of the output of running the provided unit test in the shell (the CourseListTest class) showing that your code works as expected. Note that these unit tests only print out messages of testing problems. If your code is correct, the unit tests will succeed silently without any success messages. An explanation of your work and the decisions you made to arrive at your proposed code A zip file of the completed shell after you added your code so that the shell could be executed on a different machine i L A B S T E P S

STEP 1: Review the Method Contract, Method Specification for the GetCDByCDID() Method, and Coding & Unit Testing GetCDByCDID() Method using Java (not Graded)

Download the Method Contract for GetCDByCDID() Method and review it prior to reviewing this week’s video tutorial. Download the Method Specification for the GetCDByCDID() Method and review it prior to reviewing this week’s video tutorial

STEP 2: Code & Unit Test the GetCourseByCourseID() method of the CourseList class

Decide on your OO programming language that you will use for this lab and then download the corresponding shell from the following.

Visual Basic Shell C# Shell Java Sh

[cis339-blog]

CIS 339 iLab 5 Package Diagrams

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.

[cis339-blog]

CIS 339 iLab 3 Structural Modeling Class Diagram and CRCs

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

[cis339-blog]

CIS 339 iLab 2

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 Register a Student for Classes use cases. Deliverables SRS use case diagram

Use case descriptions for the Maintain Class Records and Register a Student for Classes use cases

STEP 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 Register 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.

[cis339-blog]

CIS 339 iLab 1 System Requirements

Lab Overview 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.

[cis339-blog]

CIS 339 Entire Course

CIS 339iLab 1 System Requirements

CIS 339 iLab 2

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

CIS 339 iLab 7 - Object Oriented Application Coding