Individual Project – Object Oriented methods

Please read instructions carefully and follow outline. Please complete all weeks.

Throughout this course, you will be working on an object-oriented project to design an ordering system for a company of your choosing. You will work on a part of the project each week. Additional information and deliverables for each Individual Project will be provided in the assignment description for that project. The project will culminate in a final Key Assignment draft that will be due in Week 4. The final Key Assignment will be comprised of the following:

• Week 1: Section 1: Use Case Diagram
• Week 2: Section 2: Class Diagram
• Week 3: Section 3: Sequence and Collaboration Diagram
• Week 4: Section 4: State Transition and Activity Diagram
• Week 5: Revision of full design for a new requirement; final discussion of OO and UML

Project Selection:

The first step is to select an organization for your object-oriented design. This organization can be real or fictitious. This organization will be used as a basis for each of the assignments throughout the course. You should be familiar with the organization to allow focus on the object-oriented design.

Select an enterprise, and submit your proposal to your instructor before proceeding with the assignments for the course. Approval should be sought within the first several days of the course. Your instructor will tell you how to submit this proposal and what notification will be given for project approval.

Assignment:

For the assignments in this course, you will be developing an object-oriented design document. Your first task will be to select an enterprise to use as a basis for the project. You will be asked to create the shell document for the final Key Assignment project deliverable that you will be working on for each phase. As you proceed through each project phase, you will add content to each section of the final design document to gradually complete the final project.

The object-oriented design that you create will be for an ordering system for your chosen company. Following are the scope and assumptions for this design:

• The project will support ordering and payment processing.
• Payments can be by credit card only.
• Assume that the customers already exist.
• Other business functions are out of scope (for example, calendaring, customer management, delivery, etc.).

This week’s project deliverables are the following:

• Submit your project proposal to the instructor for approval.
• Create the Object-Oriented Design Document shell.
• Create the deliverables described in the New Content section below for Project Description and Use Case Model.
• Use Word: Paste models into the Word document.
• Follow this format:
• Title Page
• Course number and name
• Project name
• Student name
• Date
• Table of Contents
• Use autogenerated TOC
• Be sure to update the fields of the TOC so it is up-to-date before submitting your project
• Section Headings (create each heading on a new page with TBD as content except for sections listed under New Content below)
• Project description (Week 1)
• Use Case Diagram (Week 1)
• Class Diagram (Week 2)
• Sequence and Collaboration Diagram (Week 3)
• State Transition and Activity Diagram (Week 4)
• Follow-Up Discussion on Use of Object-Oriented and Recap of Design Changes (Week 5)
• Change Control Document (Week 5)
• New Content
• Project Description
• Brief description of the enterprise (can be hypothetical)
• Description of the ordering system to be designed
• Material can be taken from approved proposal submitted to instructor
• Be sure the project is approved by the instructor
• Use Case Diagram and Narratives (3–5 pages)
• Prepare a use case diagram and accompanying narratives that reflect an understanding of what the system will do.
• This will require you to identify all of the actors in the system, including other systems.
• Identify the use cases including all relationships.
• Note that only existing customers are within scope. Also note that orders are not updateable.
• There must be at least 2 employee types represented, such as a manager, owner, or clerk.
• The following use cases should be identified on the diagram:
• Create an order and payment entry
• Update a payment entry
• View an order and payment entry
• Delete an order and payment entry
• Prepare a use case narrative for each use case using the following template: Download Use Case Template http://class.coloradotech.edu/CbFileShareCommon/ctu/CS377/Assignment_Assets/Use%20Case%20Template.pdf

Week 1:

• New Content
• Project Description
• Brief description of the enterprise (can be hypothetical)
• Description of the ordering system to be designed
• Material can be taken from approved proposal submitted to instructor
• Be sure the project is approved by the instructor
• Use Case Diagram and Narratives (3–5 pages)
• Prepare a use case diagram and accompanying narratives that reflect an understanding of what the system will do.
• This will require you to identify all of the actors in the system, including other systems.
• Identify the use cases including all relationships.
• Note that only existing customers are within scope. Also note that orders are not updateable.
• There must be at least 2 employee types represented, such as a manager, owner, or clerk.
• The following use cases should be identified on the diagram:
• Create an order and payment entry
• Update a payment entry
• View an order and payment entry
• Delete an order and payment entry
• Prepare a use case narrative for each use case using the following template: Download Use Case Template http://class.coloradotech.edu/CbFileShareCommon/ctu/CS377/Assignment_Assets/Use%20Case%20Template.pdf

Week 2:

Project Deliverables: 

• Update the Object Oriented Design Document title page with the new date.
• Update the previously completed sections based on instructor feedback.
• Create a class diagram that reflects an understanding of the new ordering system that was described in Week 1.
• Identify the objects based on the use case model created in Week 1.
• Create the corresponding class diagram.
• The diagram must demonstrate inheritance
• Include all entities, classes, properties, and relationships between objects.
• The diagram should show the data types for each property.
• The diagram must use the correct class diagram notations.
• Create the diagram and submit it in a paper of 1–3 pages. This diagram will be Section 2 of the Key Assignment.
• Be sure to update your table of contents before submission.

Week 3:

Project Deliverables:

• Update the Object-Oriented Design Document title page with the new date.
• Update the previously completed sections based on instructor feedback.
• Create the Sequence and Collaboration diagrams for each use case identified in Week 1.
• All objects should be identified in the diagrams, including other system objects.
• Identify all methods needed to complete a use case.
• Number all of the steps in a sequence to show the order in which the methods are called.
• Convert the sequence diagram to a collaboration diagram.
• Add all links and notations to the collaboration diagram.
• Create a brief narrative explaining the sequence diagrams. The narrative should be written for someone who does not understand how to read a sequence diagram.
• There should be 1 sequence diagram and 1 collaboration diagram for each of the use cases identified. (4)
• Include all sequence and collaboration diagrams and the narrative. Submit them in a paper of 1–3 pages. This submission will be Section 3 of the Key Assignment.
• Be sure to update your table of contents before submission.

Week 4:

You will continue development of the object-oriented design for the ordering system. The new content this week will be the Activity Diagram and State Transition Diagram for the system. Create an activity diagram and state transition diagram for each use case that was identified in Week 1.

• State transition diagram: Identify all of the states and correctly identify the order of changes in state.
• Activity diagram: Correctly identify all of the activities for each use case.
• Use correct notation for both diagrams.

Project Deliverables:

• Update the Object-Oriented Design Document title page with the new date.
• Update the previously completed sections based on instructor feedback.
• Create the Activity and State Transition diagrams for each use case identified in Week 1.
• Identify all of the states, and correctly identify the order of changes in state.
• Identify all of the activities for each use case.
• There should be 1 activity diagram and 1 state transition diagram for each of the use cases identified. (4)
• This submission will be Section 4 of the Key Assignment.
• Update all of your diagrams as needed based on feedback from your instructor.
• This week’s project is the Key Assignment draft and should contain all the models updated with any feedback received from your instructor.
• Be sure to update your table of contents before submission.

Week 5:

You will continue development of the object-oriented design for the ordering system. New content this week will be an update to the models for a new requirement, change control document, and a recap and conclusion that discusses the use of the object-oriented approach.

In the previous weeks, you were asked to create the use case model, class diagrams, sequence and collaboration diagrams, and activity and state diagrams for an ordering system. After further review, it has become clear that modifications to the ordering system need to be considered. The new requirement is to provide the ability for an outside party to read existing orders. You are tasked with designing and documenting the add-on functionality that is needed to allow the outside party to read the orders.

• All of the original models should be updated to reflect this new requirement: use case, class, state, transition, activity, sequence, and collaboration diagrams. The updated models should reflect the new requirements.
• Object-oriented recap: This week, you will recap the use of each model in the design and answer the following question:
• Now that you have created and revised the design, how did you feel that the object-oriented methodology with UML enhanced the process of developing they system design? Please provide a 1-page document.
• Change control document: Throughout the development of the models, you have made changes to your models based on feedback from your instructor and possible discoveries as you progressed through the design. Create a change control document that documents these changes. This does not need to include the changes made for the new requirement this week. It should include other changes made throughout the project. Please include the following for each change you made:
• What was the original information?
• What change was made?
• Where is the change located in the document?
• Why was the change needed?

Project Deliverables:

• Update the Object-Oriented Design Document title page with the new date.
• Update the previously completed sections based on instructor feedback.
• Update all of the design models to reflect the new requirements
• Use Case
• Class
• Sequence and Collaboration
• State Transition and Activity
• Change Control Document for changes made to model prior to Week 5
• What was the original information?
• What change was made?
• Where is the change located in the document?
• Why was the change needed?
• Object-Oriented Design Recap
• Recap of each model used in the design
• Discussion: Now that you have created and revised the design, how did you feel that the object-oriented methodology with UML enhanced the process of developing the system design?
• This week’s project is the final Key Assignment and should contain all of the models with updates based on feedback received from your instructor and classmates.
• Be sure to update your table of contents before submission.

Collepals.com Plagiarism Free Papers

Are you looking for custom essay writing service or even dissertation writing services? Just request for our write my paper service, and we'll match you with the best essay writer in your subject! With an exceptional team of professional academic experts in a wide range of subjects, we can guarantee you an unrivaled quality of custom-written papers.

Get ZERO PLAGIARISM, HUMAN WRITTEN ESSAYS

Why Hire Collepals.com writers to do your paper?

Quality- We are experienced and have access to ample research materials.

We write plagiarism Free Content

Confidential- We never share or sell your personal information to third parties.

Support-Chat with us today! We are always waiting to answer all your questions.