Lect3：软件工程最佳实践.ppt

Module 1 - Best Practices of Software Engineering Mastering OOAD w/ UML 2.0 – Instructor Notes A heading compartment is a string contained in a name tag (a rectangle with cutoff corner) in the upper leftmost corner with the following syntax: [kind]name[parameters] ? This kind can be: activity - activity diagram package - class diagram, package diagram communication - communication diagram component - component diagram class - composite structure diagram deployment - deployment diagram intover - interaction overview diagram object - object diagram state machine - state machine diagram sd - sequence diagram timing -timing diagram use case - use case diagram The UML 2 specification does not have consistent usage of kind, for example, the interactions chapter uses sd for all kinds of interaction diagrams (including timing), which is clearly erroneous. The frame is primarily used in cases where the diagrammed element has graphical border elements, like ports for classes and components (in connection with composite structures), entry/exit points on state machines, and gates/fragments on sequence diagrams. Module 1 - Best Practices of Software Engineering Mastering OOAD w/ UML 2.0 – Instructor Notes Module 1 - Best Practices of Software Engineering Mastering OOAD w/ UML 2.0 – Instructor Notes 1. The four basic principles of object orientation include: abstraction, encapsulation, modularity and hierarchy. An abstraction is any model that includes the most important aspects of something while suppressing or ignoring less important details. Encapsulation is the physical localization of features that hides their implementation behind a public interface. Modularity is the logical and physical decomposition of things into small, simple groupings, which increase the achievements of software-engineering goals. Hierarchy is any ranking or ordering of abstractions into a tree-like structure. 2. A class is a description of a set of objects that share the same attributes, operat