1 / 10

End of analysis

End of analysis. System sequence diagram Operation contract. We have. Functional requirement Use case model Use case diagram Brief use case description Ranking of the use cases Fully dressed for the most important Information requirement Domain model

brent
Download Presentation

End of analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. End of analysis System sequence diagram Operation contract

  2. We have Functional requirement • Use case model • Use case diagram • Brief use case description • Ranking of the use cases • Fully dressed for the most important Information requirement • Domain model • The classes in the system and the structure between them

  3. Moving from analyses to design • System sequence diagram • For each fully dressed use case make a system sequence diagram • For each system operation that changes the state of the domain model write an operation contract (we will not do much about operation contracts in this course just mention their existence)

  4. System sequence diagram In the systems sequence diagram the system is seen as a black box. The system events (the arrows between the actor an the system) are found from the Fully dressed description The response from the system can shown as dottetlinies

  5. System events • Name the system event with a verb • Put the values (parameters) on • Response from the system can be shown as information on a dotted line • Loops can be shown as a box around system events. Please see the book for details on how it is written in UML

  6. System operations and contract • A system operation is an operation the system has to offer, to handle the system events. • There are different kind op system operations, the one that changes the state of the domain model is the one you should consider making a contract on. • The contract describe in detail what state the domain model is in after the system operation.

  7. System operation changing the state of the domain model

  8. Example of operation contract Part of the domain model Operations contract Operation: addLineItem (itemID, quantity) Use-cases: Process sale Precondition: A Sale instance (object) has been created Post conditions: • A SalesLineItem instance (object) sli was created • sli was associated with the current Sale • sli.quantity became quantity • sli was associated with a ProductSpecification (object), based on itemID match (association formed).

  9. Operation contracts Operations contract Operation: addLineItem (itemID, quantity) Use-cases: Process sale Precondition: A Sale instance (object) has been created Postconditions: • A SalesLineItem instance (object) sli was created • sli was associated with the current Sale • sli.quantity became quantity • sli was associated with a ProductSpecification (object), based on itemID match (association formed). Important notes: Reference to the use case Precondition: what information has to be present in the system, before the operations starts Postcondition: Which object has been created Which attributes has been changed Which object structure has been created

  10. Ready to move from what to how

More Related