IT技术讲座建模 build-models.pptVIP

* * * Split and Constraints A large invariant can often be split into smaller ones at the and operations easier to read and write localizes the problem in case of a broken invariant easier to maintain context LoyaltyProgram inv: participants - forAll (age() 0) and partners.deliveredServices - forAll (pointsEarned = 0) context LoyaltyProgram inv: participants - forAll (age() 0) inv: partners.deliveredServices - forAll (pointsEarned = 0) * Always Name Association Ends Naming association ends is a good practice indicates the purpose of the associated object suggests the attribute name to maintain the association * Building Models with OCL Introduction Completing UML Diagrams Modeling Tips and Hints Summary * Summary A model allows one to focus on high level design decisions, rather than low level details. One way to identify constraints is to look for optional/dynamic multiplicities and cycles. OCL expressions can also be used to simplify a class diagram. Design by contract allows the interface of an object to be precisely specified. The rule of thumb for writing a good OCL spec is to keep the expressions as simple as possible. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Today’s Agenda Quick Review Continue on OCL Build Models Using OCL * Quick Review What is software specification? Why do we need formal specification? * Building Models with OCL Introduction Completing UML Diagrams Modeling Tips and Hints Summary * What Is a Model? Simply put, a model is a high level system description. It consists of a consistent, coherent set of model elements, i.e., artifacts written in a well-defined modeling language such as UML and OCL. * UML and OCL (1) Both UML diagrams and OCL expressions are part of a model. They are connected by the context definition. Note that OCL expressions can be written in a textual format or attached to the UML diagrams directly. * Example LoyaltyAccount points: Integer number: Integer earn (i: Inte