CIS339 Object Oriented Analysis Course

$39.00

CIS339 Object Oriented Analysis Course
The Student Records System (SRS), described in the SRS Preliminary Planning Overview document…

SKU: CIS 339 Object-Oriented Analysis Design Alpharetta Categories: , , , Tags: , , , , ,

Description

CIS339 Object Oriented Analysis Course

CIS339 Object Oriented Analysis Course

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

iLab Week 1-7 

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

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

CIS339 Object Oriented Analysis Course

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

CIS339 Object Oriented Analysis Course

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

CIS339 Object Oriented Analysis Course

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

CIS339 Object Oriented Analysis Course

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

CIS339 Object Oriented Analysis Course

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

CIS339 Object Oriented Analysis Course

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

CIS339 Object Oriented Analysis Course

Course Discussions Week 1-7 All Students Posts – 103 Pages 

https://www.hiqualitytutorials.com/product/cis339-course-discussions-week-1-7/

Week 1 All Students Posts – 14 Pages 

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

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?

SDLC stands for Systems Development Life Cycle and its four phases are Planning, Analysis, Design, and Implementation.  I also learned this in Structured Analysis & Design and applied this concept in Project Management.  I would typically spend the most time gathering requirements in the planning stage because I must plan everything before I analyze, design, and implement.  This ensures that I am obtaining the necessary requirements in order to complete a project successfully.  If I were to miss any of the requirements, this is a problem because I must follow the four phases of the SDLC in the correct order to have a project completed successfully.  Also, missing any of the requirements on the project can lead to project failure.  So, it is important to follow each step carefully by checking everything twice so I am sure of what I need in order to complete the IT system development project…

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.

There are some important tips to keep in mind in order to complete the lab successfully.
-Participate in discussion topics everyday by replying to each of your classmates responses with your own information
-Attend class weekly
-Ask professor questions if you do not understand the concepts for this lab
-Become familiar with RSA before completing the lab
-Take notes of important information
-Read the material before coming to class
-Read lab instructions first before completing the lab…

Week 2 All Students Posts – 18 Pages

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

 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”?

A use case is used in system analysis to identify, clarify, and organize system requirements. The use case is consists of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. It consists of a group of elements such as classes and interfaces that can be used together in a way that will have an effect larger than the sum of the separate elements combined. The use case should contain all system activities that have significance to the users. A use case can be thought of as a collection of possible scenarios related to a particular goal, indeed, the use case and goal are sometimes considered to be synonymous.

A use case or set of use cases has these characteristics:

  • Organizes functional requirements
  • Models the goals of system/actor (user) interactions
  • Records paths (called scenarios) from trigger events to goals
  • Describes one main flow of events (also called a basic course of action), and possibly other ones, called exceptional flows of events (also called alternate courses of action)
  • Is multi-level, so that one use case can use the functionality of another one.

Use cases can be employed during several stages of software development, such as planning system requirements, validating design, testing software, and creating an outline for online help and user manuals

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.

There are important tips to keep in mind while reviewing the tutorial on how to create a use case diagram which is something we are creating for our Week 2 iLab.  It is crucial to have an understanding of the business process, its activities, and its flows.  There are four steps the tutorial discusses on how to create an activity diagram and are listed as follows:
1. Draw a single initial mode
2. Draw Activity Diagram Elements in the same order as the flow of the Business Process
3. Draw Swimlanes to simplify the diagram, if appropriate
4. Draw final nodes.  Usually, 1 final node when modeling Business Process flow

By carefully following these steps on how to create an activity diagram, you will find it easier to work on the next iLab and will be more comfortable with it…

Week 3 All Students Posts – 14 Pages 

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

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.

A class diagram illustrates the relationships and source code dependencies among classes in the Unified Modeling Language (UML). In this context, a class defines the methods and variables in an object.  Objects are specific entities in a program or the unit of code that represents that entity. Class diagrams are useful in all forms of object-oriented programming (OOP). The concept is several years old, but has been refined as OOP modeling paradigms have evolved.

In a class diagram, the classes are arranged in groups that share common characteristics.  A class diagram is similar to a flowchart in which classes are portrayed as boxes, with each having three rectangles inside. The top rectangle contains the name of the class.  The middle rectangle contains the attributes of the class.  The lower rectangle contains the methods, also called operations, of the class. Lines, which may have arrows at one or both ends, connect the boxes. These lines define the relationships, also called associations, between the classes…

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.

In order to complete this week’s iLab, you need to do the following:

-Review the tutorial that shows you how to create a class diagram
-Meet with group to discuss the iLab instructions
-Attend class
-Take notes on important concepts on how to create class diagrams
-Ask professor questions if you do not understand the assignment
-Follow lab instructions carefully
-Read the chapter(s) and lecture to get an understanding of class diagrams…

Week 4 All Students Posts – 14 Pages

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

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.

Using class diagrams, it is easier to describe all the classes, packages, and interfaces that constitute a system and how these components are connected. Class diagrams show classes, their attributes, the functions or operations that are associated with them, and the relationships among the different classes that make up a system…

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 longest part is analyzing the data which you extrapolate from the use-case diagram and description. If you don’t have the description information it would become much more complicated and difficult to create. This week’s homework was made much easier by accessing the solution for the week 2 lab with the descriptive answers along with the use-case diagram…

Week 5 All Students Posts – 16 Pages 

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

The Package Diagram – 10 Pages

What is the purpose of packages? What are the advantages of packaging the classes?  Give an example?

Packages organize model elements and diagrams into groups to make UML diagrams simpler and easier to understand. Packages are shown as file folders. Packages can be used in any diagrams. The requirements states that all names must be unique and group related elements together. The package diagram consist of classes and shows elements such as processes (activities), actor(s), packages, interactions, etc…

Lab Forum – 6 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, problems, or lessons you learned or experienced with this week’s lab.

To create a package diagram in RSA, you will need the class diagram, collaboration diagrams, groupings of classes into packages with package names, and dependency relationships among packages.

There are two major steps listed in the tutorial that show you how to create the package diagram for this week’s iLab.

1. Draw all packages with package names and content
2. Draw all dependency relationships among packages…

Week 6 All Students Posts – 16 Pages 

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

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?

A method specification outlines a specific materials selection and construction operation process to be followed in providing a product. In the past, many construction specifications were written in this manner. A contractor would be told what type of material to produce, what equipment to use and in what manner it was to be used in building a structure. In its strictest sense, only the final form of the structure can be stipulated. This type of specification allows for a greater degree of competition than the proprietary product specification, but as long as the structure is built according to the materials and methods stipulated, the agency bears the responsibility for the performance.

Method specifications have several key disadvantages although they are frequently used.  First, they tend to stifle contractor innovation. Since a contractor’s only motivation is instructional compliance, there is virtually no incentive to develop better, more efficient construction methods. Second, since they are not statistically based and 100 percent compliance is usually not possible, method specifications usually required “substantial compliance,” a purposely vague and undefined term that can lead to disputes. Finally, spot checks of material quality, which are often used in method specifications, do not reflect overall material quality because they are taken from subjectively determined non-random locations. Since they are not random, these spot checks have no statistical validity and therefore do not reflect overall material quality…

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.

It is important for everyone to be familiar with RSA because it will be necessary for the iLab mini project that we have to complete for week 6 and week 7.  Also, if anyone needs reinforcement on any of the diagrams, it will be a good idea to review the tutorials for each of the diagrams if possible one more time before completing any of the diagrams for our Amusement Park System on our mini project…

Week 7 All Students Posts – 11 Pages

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

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.

Verification evaluates the intermediary products to check whether it meets the specific requirements of the particular phase.  It checks whether the product is built as per the specified requirement and design specification.  It also checks “Are we building the product right”?  Verification is done without executing the software and it involves all the static testing techniques.  Examples of verification include reviews, inspection and walkthrough.

Validation evaluates the final product to check whether it meets the business needs.  It determines whether the software is fit for use and satisfy the business need.  It also checks “Are we building the right product”?  Validation is done with executing the software and includes all the dynamic testing techniques.  Examples of validation include all types of testing like smoke, regression, functional, systems and UAT…

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.

Most software engineering interviews conducted today usually cover a wide variety of subjects. It makes sense, because anyone who has ever worked as a programmer knows that doing the job well requires that you work well with different subjects. If I work as a C++ developer, I would probably need to know some basic sql so I can retrieve information from a database.  I may also even need to learn some basic O.S. concepts so that I can interface with Windows, aside from just C++. The point, which may seem obvious to some, is that I cannot just expect to know one subject and get by in an interview, because no programmer job is realistically like that…

CIS339 Object Oriented Analysis Course

DeVry