CIS339 Entire Course includes:
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:
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:
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:
iLAB STEPS
STEP 1: Review the Method Contract, Method Specification for the GetCDByCDID() Method, and Coding & Unit Testing GetCDByCDID() Method using Java (not Graded)
STEP 2: Code & Unit Test the GetCourseByCourseID() method of the CourseList class
Decide on your OOP programming language that you will use for this lab and then download the corresponding shell from the following:
Both the Visual Basic and C# shells are Visual Studio projects while the Java shell include only the *.java source files that could be loaded into any Java IDE.
Code and unit test the CourseList.GetCourseByCourseID() method in your favorite programming language. You only need to add code for the GetCourseByCourseID() method and then run the application (the unit test will automatically test your code), then print out problem messages, if any
Explain your work and the decisions you made to arrive at your proposed solution.
STEP 3: Submit your assignment
Copy and paste into a Word document:
Save your document with the file name CIS339_Lab7_YourName.
Then, zip all the lab file into one zip file so that the entire project would run on a different machine.
Save your zip file with the file name CIS339_Lab7_YourName.zip.
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.
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.
Deliverables
iLAB STEPS
STEP 1: Create a Public Method Contract
STEP 2: Create a Method Specification
STEP 3: Save and Upload
Scenario and Summary
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.
Deliverables
Evolved package diagram
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.
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
iLAB STEPS
STEP 1:
STEP 2: Create the Sequence Diagram
STEP 3: Create a Communication Diagram
STEP 4: Create an Object State Diagram
STEP 5: Save and Upload the Project
Scenario and Summary
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
iLAB STEPS
STEP 1:
STEP 2: Create the Class Diagram
STEP 3: Complete the CRC Cards
STEP 4: Copy the Diagram Into an MS Word document
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
iLAB STEPS
STEP 1: Diagram
STEP 2: Generate the Use Case Diagram
STEP 3: Generate the Use Case Descriptions
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 CIS339_Lab2_YourName.
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.
iLAB STEPS
STEP 1: Review Starting RSA on Citrix (not graded)
STEP 2: Download and Complete the System Request Form
STEP 3: Upload the Document to your Dropbox
Save the System Request Form MS Word document with the file name CIS339_Lab1_YourName.
