2/1/2022

Sequence And Collaboration Diagram

Collaboration diagrams and Sequence diagrams express similar information, but show it in different ways. In Together, the two diagrams are closely coupled. Both diagrams are based on a view file with a.vfSequence extension, and the navigation icon is identical. The toolbars for the diagrams are similar, except that the Collaboration diagram.

  1. Sequence And Collaboration Diagrams
  2. Sequence And Collaboration Diagrams
  3. Sequence Diagram And Collaboration Diagram

Sequence Diagram: Sequence diagrams typically show the flow of functionality through a use case, and consist of the following components: 1. Actors, involved in the functionality 2. Objects, that a system needs to provide the functionality 3. Messages, which represent communication between objects. Sequence and Communication Diagrams An interaction diagram is either a sequence diagram or a communication diagram, both of which show essentially the same information. These diagrams, along with class diagrams, are used in a use case realization, which is a way to achieve or accomplish a use case.

Assignment 1

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. The following are the scope and assumptions for this design:

Collaboration
  • 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 (e.g., 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 the project description and the 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 (TOC)
    • Use an 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 the 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 Design and Recap of Design Changes (Week 5)
    • Change Control Document (Week 5)
  • New Content
    • Project Description
    • Provide a brief description of the enterprise (can be hypothetical).
    • Describe the ordering system to be designed.
    • Material can be taken from your approved proposal that is submitted to your instructor.
    • Be sure the project is approved by the instructor.
  • Use Case Diagram and Narratives (35 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 updatable.
    • 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.

Submit a Word document of 35 pages that includes the above.

Assignment 2

For this assignment, you will continue developing the object-oriented design for the ordering system. The new content this week will be the class diagram for the ordering system.

Project Deliverables

Complete the following:

  • 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 13 pages. This diagram will be Section 2 of the Key Assignment.
  • Be sure to update your table of contents before submission.

Assignment 3

For this assignment, you will continue development of the object-oriented design for the ordering system. The new content this week will be the sequence and collaboration diagram for the system.

Create a sequence and collaboration diagram for each use case that was identified in Week 1. Correctly identify the objects, methods, sequences, and collaborations. Begin by creating the sequence diagrams. Then, convert the sequence diagrams to collaboration diagrams.

Project Deliverables

Complete the following:

  • 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 13 pages. This submission will be Section 3 of the Key Assignment.
  • Be sure to update your table of contents before submission.

Assignment 4

For this assignment, 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.

Complete the following:

  • 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

Complete the following:

  • 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 document.
  • Update all of your diagrams as needed based on feedback from your instructor.
  • This week's project is draft of the project document, and it should contain all the models updated with any feedback received from your instructor.
  • Be sure to update your table of contents before submission.

Assignment 5

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.

Complete the following:

Sequence And Collaboration Diagrams

  • 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 Unified Modeling Language (UML) enhanced the process of developing the system design? Please provide a 1-page 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 that 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

Complete the following:

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

Questions

1. Is there an advantage to creating use cases before coding the system?

2. Describe what information is included in a use case. Describe the difference between a regular use case and a fully dressed one. Explain when to use the different types of use cases.

3. Does using a database add or delete from the functionality of a computer system?

4. Relate the concept of objects in a class diagram to the concept of tables in a database. Discuss tables, rows, and records specifically. Explain how the objects in a class diagram relate to objects in a table.

5. What do collaboration and sequence diagrams contribute to the object-oriented design process?

Sequence And Collaboration Diagrams

6. Write 400600 words that respond to the following questions with your thoughts, ideas, and comments. This will be the foundation for future discussions by your classmates. Be substantive and clear, and use examples to reinforce your ideas:

  • Compare and contrast the sequence diagram and the collaboration diagram.
  • When would you use one instead of the other? Provide examples, and explain your reasons.

7. What do activity diagrams contribute to an object-oriented project?

8. Explain the reasons and process for creating activity diagrams.

9. How will the design document that you created be used to create an entire system?

Sequence Diagram And Collaboration Diagram

10. How would you compare the object-oriented design process with the structured design process?