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
    • 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.