Downloaded 15 times
Uml package diagram
- 1. UML Package Diagrams M.Vedaraj Assistant Professor/CSE R.M.D.Engineering College
- 2. UML Package Diagram: •Package diagram is used to represent the logical architecture of the system. • It illustrates the layers, subsystem, and packages. • Using UML package diagram, the elements of the system can be grouped together. • UML packages can group anything, for instance classes, other packages, use cases and so on. • Packages can be nested. That means one package may contain other package. • If the packages have some inner members then its name must be shown on the tab. • The dependency line can be shown in the package diagram.it shows the dependent packages.
- 3. Basic Notations usedin Package diagram • A package is an organized group of elements. A package may contain structural things like classes, components, and other packages in it.
- 4. Types of Layers: Typesof Layers: • There are three types of layer. They are • UI layer: This layer is created using the web pages or swing or applet classes. • Domain Layer: This layer consists of software objects for representing domain concepts. • Technical Service layer: For working of the higher layer object some services are required such as maintaining error logs or accessing the database and so on.
- 6. What is therelationship between SSD and UseCase ? •A system sequence diagram (SSD) is a picture that shows, for a particular scenario of a use case, the events that external actors generate their order, and inter-system events. A system sequence diagram should specify and show the following: •External actors •Messages invoked by these actors •Return values associated with previous messages •Indication of any loops or iteration area
- 7.
- 8. Relationship between SSDsand Use Case
- 9. How to NameSystem Events and Operations? •Choose event and operation names at abstract level. •Start the name of a system with verb such as add, enter, insert, make etc. .
- 10. Guidelines • The sequencediagram generally represents only one scenario of use case model. • System event must be represented at the abstract level. • The system event must be usually a verb. For example display, enter, select, eject and so on. • The sequence diagram can represent the collaboration with other external systems.
- 11. Finding the conceptualclass hierarchies. • Generalization Generalization is the activity of identifying commonality among concepts and defining superclass (general concept) and subclass (specialized concept) relationships.
- 12.
- 13. Generalization and Class Sets Allmembers of a conceptual subclass set are members of their superclass set. For example, in terms of set membership, all instances of the set CreditPayment are also members of the set Payment. In a Venn diagram, this is shown as in Figure.
- 14. Conceptual Subclass Definition Conformance •When a class hierarchy is created, statements about superclasses that apply to subclasses are made. For example, All Payments have an amount and are associated with a Sale.
- 15. Guideline: 100% Rule •100% of the conceptual superclass's definition should be applicable to the subclass. The subclass must conform to 100% of the superclass's: •Attributes • Associations
- 16. Is-a Rule • Allthe members of a subclass set must be members of their superclass set.
- 17. What Is aCorrect Conceptual Subclass? • A potential subclass should conform to the: • 100% Rule (definition conformance) • Is-a Rule (set membership conformance)
- 18. When to Definea Conceptual Subclass? • The subclass has additional attributes of interest. • The subclass has additional associations of interest. • The subclass concept is operated on, handled, reacted to, or manipulated differently than the superclass.
- 19. When to Definea Conceptual Superclass • The potential conceptual subclasses represent variations of a similar concept. • The subclasses will conform to the 100% and Is-a rules.
- 20. Attribute: • An attributeis a logical data value of an object. • Attributes are used to describe any object or concept or anything. • Attributes are also defined as characteristic property of an object. Student Name Regno address
- 21. UML Attribute Notation: •Attributes are shown in the second compartment of the class box .
- 22. More Notation: • Thefull syntax for an attribute in the UML is: visibility name: type multiplicity = default {property-string
- 23.
- 24. Valid Attribute Types: •The attributes in a domain model should preferably be simple attributes or data types. • Very common attribute data types include: Boolean, Date, Number, String(Text), Time • Other common types include: Address, Color, Geometries (Point, Rectangle),Phone Number, Social Security Number, Universal Product Code (UPC), SKU,ZIP or postal codes, enumerated types
- 25.
- 26. 'Description' Class • Adescription class contains information that describes something else. For example, a Product Description that records the price, picture, and text description of an Item.
- 27. Inception The purpose ofthe inception phase is not to define all the requirements, or generate a believable estimate or project plan. Most requirements analysis occurs during the elaboration phase, in parallel with early production-quality programming and testing.
- 28.