Uml package diagram

UML Package diagram

1. UML Package
Diagrams
M.Vedaraj
Assistant Professor/CSE
R.M.D. Engineering College

2. UML Package Diagram:
• Packagediagramisusedtorepresentthelogical
architectureofthesystem.
• Itillustratesthelayers,subsystem,andpackages.
• UsingUMLpackagediagram,theelementsofthesystem
canbegroupedtogether.
• UMLpackagescangroupanything,forinstanceclasses,
otherpackages,usecasesandsoon.
• Packagescanbenested.Thatmeansonepackagemay
containotherpackage.
• Ifthepackageshavesomeinnermembersthenitsname
mustbeshownonthetab.
• Thedependencylinecanbeshowninthepackage
diagram.itshowsthedependentpackages.

3. Basic Notations used in
Package diagram
•Apackageisanorganizedgroupofelements.Apackage
maycontainstructuralthingslikeclasses,components,
andotherpackagesinit.

4. Types of Layers:
Types of 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 the relationship between
SSD and UseCase ?
•Asystemsequencediagram(SSD)isapicturethatshows,
foraparticularscenarioofausecase,theeventsthat
externalactorsgeneratetheirorder,andinter-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. Example of an SSD

8. Relationship between SSDs and Use Case

9. How to Name System
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 sequence diagram 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 conceptual class
hierarchies.
•Generalization
Generalizationistheactivityofidentifyingcommonality
amongconceptsanddefiningsuperclass(generalconcept)
andsubclass(specializedconcept)relationships.

12. UML notation

13. Generalization and Class
Sets
Allmembersofaconceptualsubclasssetare
membersoftheirsuperclassset.Forexample,interms
ofsetmembership,allinstancesoftheset
CreditPaymentarealsomembersofthesetPayment.
InaVenndiagram,thisisshownasinFigure.

14. Conceptual Subclass
Definition Conformance
•Whenaclasshierarchyiscreated,statementsabout
superclassesthatapplytosubclassesaremade.For
example,AllPaymentshaveanamountandare
associatedwithaSale.

15. Guideline: 100% Rule
•100%oftheconceptualsuperclass'sdefinitionshouldbe
applicabletothesubclass.Thesubclassmustconform
to100%ofthesuperclass's:
•Attributes
•Associations

16. Is-a Rule
•All the members of a subclass set must be members of
their superclass set.

17. What Is a Correct
Conceptual Subclass?
•Apotentialsubclassshouldconformtothe:
•100%Rule(definitionconformance)
•Is-aRule(setmembershipconformance)

18. When to Define a
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 Define a
Conceptual Superclass
• Thepotentialconceptualsubclassesrepresent
variationsofasimilarconcept.
• Thesubclasseswillconformtothe100%andIs-a
rules.

20. Attribute:
•An attribute is 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:
•ThefullsyntaxforanattributeintheUMLis:
visibilityname:typemultiplicity=default{property-string

23. Derived Attributes:

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. Valid Attribute Types:

26. 'Description' Class
•Adescriptionclasscontainsinformationthatdescribes
somethingelse.Forexample,aProductDescriptionthat
recordstheprice,picture,andtextdescriptionofanItem.

27. Inception
Thepurposeoftheinceptionphaseisnottodefineallthe
requirements,orgenerateabelievableestimateorprojectplan.
Mostrequirementsanalysisoccursduringtheelaborationphase,
inparallelwithearlyproduction-qualityprogrammingand
testing.

28. Inception