CIS 339 Object-Oriented Analysis Design Alpharetta

$39.00

CIS 339 Object-Oriented Analysis Design Alpharetta
You have been hired by the School of Prosperity (SoP) as a software architect to…

Description

CIS 339 Object-Oriented Analysis Design Alpharetta

CIS 339 Object-Oriented Analysis Design Alpharetta

A+ Course: iLab Week 1-7| Discussions Week 1-7

CIS 339 Object-Oriented Analysis Design Alpharetta

iLab Week 1-7 

https://www.hiqualitytutorials.com/product/cis-339-all-ilabs/

ilab Week 1 

https://www.hiqualitytutorials.com/product/cis339-ilab-week-1/

iLAB 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

  • System Request Form for the SRS
  • Verification and validation of your work
  • Explanation of your work

CIS 339 Object-Oriented Analysis Design Alpharetta

ilab Week 2 

https://www.hiqualitytutorials.com/product/cis339-ilab-week-2/

iLAB OVERVIEW

Scenario and Summary

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
  • Verfication and validation of your work
  • Explanation of your work

CIS 339 Object-Oriented Analysis Design Alpharetta

ilab Week 3 

https://www.hiqualitytutorials.com/product/cis339-ilab-week-3/

iLAB OVERVIEW

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

  1. Class diagram for the SRS system
  2. CRC cards for each class in your class diagram
  3. Verification and validation of your work
  4. Explanation of your work

CIS 339 Object-Oriented Analysis Design Alpharetta

ilab Week 4 

https://www.hiqualitytutorials.com/product/cis339-ilab-week-4/

iLAB OVERVIEW

Scenario and Summary

You are deep into the analysis phase of your Internet-accessible Student Records System (SRS). You have finished both the Functional Modeling (activity diagram, use case diagram, and use case description) and the Structural Modeling (class diagram and the CRC cards). Now you are ready to move into the Behavioral Modeling where you will model the behavior or the objects that make up the SRS system.

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.

  1. Sequence diagram
  2. Communication diagram

In addition, you will also need to create a state machine diagram for the RegistrationRecord 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

  1. Sequence diagram for the Register a Student for Classes use case
  2. Communication diagram for the Register a Student for Classes use case
  3. State Machine diagram for a Registration Record object
  4. Verification and validation of your work
  5. Explanation of your work

CIS 339 Object-Oriented Analysis Design Alpharetta

ilab Week 5 

https://www.hiqualitytutorials.com/product/cis339-ilab-week-5/

iLAB OVERVIEW

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

  • SRS package diagram
  • Verification and validation of your work
  • Explanation of your work

CIS 339 Object-Oriented Analysis Design Alpharetta

ilab Week 6 

https://www.hiqualitytutorials.com/product/cis339-ilab-week-6/

iLAB OVERVIEW

Scenario and Summary

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

  1. Method contract of the GetCourseByCourseID() method of the CourseList class
  2. Method specification of the GetCourseByCourseID() method of the CourseList class

CIS 339 Object-Oriented Analysis Design Alpharetta

ilab Week 7 

https://www.hiqualitytutorials.com/product/cis339-ilab-week-7/

iLAB OVERVIEW

Scenario and Summary

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.

  1. Code that implements the GetCourseByCourseID() method
  2. 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:

  1. complete code for the Course class;
  2. partially completed code for CourseList class; and
  3. 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

  • 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.
  • a zip file of the completed shell after you added your code so that the shell could be executed on a different machine.
  • Verification and validation of your work
  • Explanation of your work

CIS 339 Object-Oriented Analysis Design Alpharetta

Discussions Week 1-7 All Students Posts 103 Pages 

https://www.hiqualitytutorials.com/product/cis-339-all-discussions/

Determine Requirements and Lab Forum Discussions Week 1 All Students Posts 14 Pages 

https://www.hiqualitytutorials.com/product/cis-339-determine-requirements/

Determine Requirements – 7 Pages

What phase or phases do you spend the most time gathering requirements in the traditional/classic four SDLC phases (Planning, Analysis, Design and Implementation) and Why?  On an IT system development project, what team members are required to participate in requirements definition?

Lab Forum – 7 Pages

This forum is used to discuss the Rational Software Architect (RSA) iLabs assignments and techniques. Please post any UML modeling questions or hints and tips that you have concerning this week’s RSA modeling lab. At a minimum, post at least three notes that highlight the key modeling techniques, problems, or lessons learned or experienced with this week’s lab.

Requirements Discovery and Lab Forum Discussions Week 2 All Students Posts 18 Pages

https://www.hiqualitytutorials.com/product/cis-339-requirements-discovery/

Requirements Discovery – 10 Pages

What are use cases?  Requirement discovery can indirect or directly indicate functional (process) or data requirements. Search the web to see what you can find on the term “use case requirements” or “use case stories”?

Lab Forum – 8 Pages

This forum is used to discuss the Rational Software Architect (RSA) iLab assignments and techniques. Please post any UML modeling questions or hints and tips that you have concerning this week’s RSA modeling lab. At a minimum, post at least three notes that highlight the key modeling techniques and/or problems or lessons learned that you experienced with this week’s lab.

The Class Diagram and Lab Forum Discussions Week 3 All Students Posts 14 Pages 

https://www.hiqualitytutorials.com/product/cis-339-class-diagram/

The Class Diagram – 9 Pages

Explain the purpose of the class diagram and why is it important to identify class early in the Unified Process methodology.

Lab Forum – 5 Pages

This forum is used to discuss the Rational Software Architect (RSA) iLab assignments and techniques. Please post any UML modeling questions or hints and tips that you have concerning this week’s RSA modeling lab. At a minimum, post at least three notes that highlight the key modeling techniques and/or problems or lessons learned that you experienced with this week’s lab.

The Sequence and Communication Diagrams and Lab Forum Discussions Week 4 All Students Posts 14 Pages

https://www.hiqualitytutorials.com/product/sequence-and-communication-diagrams/

The Sequence and Communication Diagrams – 6 Pages

What are these two UML diagrams called? Explain the similarities and the differences between the information represented by these two UML diagrams.  Find examples of each on the web to support your post.

Lab Forum – 8 Pages

This forum is used to discuss the Rational Software Architect (RSA) iLab assignments and techniques. Please post any UML modeling questions or hints and tips that you have concerning this week’s RSA modeling lab. At a minimum, post at least three notes that highlight the key modeling techniques and/or problems or lessons learned that you experienced with this week’s lab.

The Package Diagram and Lab Forum Discussions Week 5 All Students Posts 16 Pages 

https://www.hiqualitytutorials.com/product/cis-339-package-diagram/

Method Contract and Specification Diagrams and Lab Forum Discussions Week 6 All Students Posts 16 Pages 

https://www.hiqualitytutorials.com/product/method-contract-specification-diagrams/

Method Contract and Specification Diagrams – 10 Pages

What are a method contract and a method specification?  How do you accommodate the novice user and the experience user interface design?  What are some of the things you would do?  Search the web for support in your answer?

Lab Forum – 6 Pages

This forum is used to discuss the Rational Software Architect (RSA) iLabs assignments and techniques. Please post any UML modeling questions or hints and tips that you have concerning this week’s RSA modeling lab. At a minimum, post at least three notes that highlight the key modeling techniques and/or problems or lessons learned that you experienced with this week’s lab.

Validation and Verification Testing and Lab Forum Discussions Week 7 All Students Posts 11 Pages

https://www.hiqualitytutorials.com/product/validation-and-verification-testing/

Validation and Verification Testing Discussions 1 Week 7 All Students Posts 10 Pages

What is the difference between Validation and Verification testing? Give an example of each one.  Please use web resources to support your post.

Lab Forum Discussions 2 Week 7 All Students Posts 1 Page

This forum is used to discuss the lab coding assignment of the week. Please post your questions, concerns, or any ideas that you want to share with the class regarding the coding assignment. At a minimum, post at least three notes that highlight the key coding techniques and/or problems or lessons learned that you experienced with this week’s lab.

CIS 339 Object-Oriented Analysis Design Alpharetta

DeVry