1. 1 Package Diagram

2. 2 הדיאגרמות

3. 3 אבני יסוד: דיאגרמות פריסת התוכנה על גבי החומרה PackageDiagram “חבילות עבודה” מקרא: מודל סטטי מודל דינמי מודל ניהולי Statechart פונקציונליות, אינטראקציה ActivityDiagram לוגיקה, זרימה ComponentDiagram ארכיטקטורת התוכנה SequenceDiagram התנהגות ישויות, קשרים, יחסים ClassDiagram Use Case Model שחקנים, תרחישים, אופני פעולה דרישות מערכת DeploymentDiagram ארכיטקטורת מערכת

4. 4 Package  The OMG UML specifications states:  "A package is a grouping of model elements. Packages themselves may be nested within other packages. A package may contain subordinate packages as well as other kinds of model elements. All kinds of UML model elements can be organized into packages."  A package is a general-purpose mechanism for organizing elements of a model, such as classes or use case diagrams, into groups.  Every element within a model is uniquely owned by one package. Also, that element’s name must be unique within that package.  Packages that are friends to another may see all the elements of that package, no matter what their visibility.  If an element is visible within a package, it is visible within all packages nested inside the package  Packages should be cohesive. Anything you put into the package should make sense when considered with the rest of the contents of the package. To determine whether a package is cohesive, a good test is you should be able to give your package a short, descriptive name. If you can’t, then you may have put several unrelated things into the package  Packages provide units of configuration management

5. 5 חלוקת הדרישות למארזים

6. 6 חלוקת ה UC למארזים

7. 7 חלוקת המערכת למארזים

8. 8

9. 9 Package Diagrams: Standard Stereotypes

10. 10 Package Diagrams: Standard Stereotypes  Fa ç ade — A stereotyped package containing only references to model elements owned by another package. It is used to provide a 'public view' of some of the contents of a package.  Framework — A stereotyped package that contains model elements which specify a reusable architecture for all or part of a system. Frameworks typically include classes, patterns or templates. When frameworks are specialized for an application domain, they are sometimes referred to as application frameworks.  Stub — a package that serves as a proxy for the public contents of another package.  Subsystem — a package representing an independent part of the system being modeled.  System — a package representing the entire system being modeled.

11. 11 דוגמא ל Package Diagram

12. 12 דוגמא ל Package Diagram

13. 13 דוגמא ל Package Diagram

14. 14 דוגמא ל Package Diagram

15. 15 דוגמא ל Package Diagram

16. 16 קשרים בין מארזים

17. 17 קשרים בין מארזים

18. 18 Merge A package merge indicates a relationship between two packages whereby the contents of the target package are merged with those of the source package. Private contents of a target package are not merged. The applicability of a package merge addresses any situation of multiple packages containing identically-named elements, representing the same thing. A merging package will merge all matching elements across its merged packages, along with their relationships and behaviors. Note that a package merge essentially performs generalizations and redefinitions of all matching elements, but the merged packages and their independent element representations still exist and are not affected.

19. 19 Dependency

20. 20 Import Public elements of the supplier namespace are added as public elements to the client namespace. Elements in the client can access all public elements in the supplier using unqualified names

21. 21 access Public elements of the supplier namespace are added as private elements to the client namespace. Elements in the client can access all public elements in the supplier using unqualified names

22. 22 Dependency –Among Packages  Two Stereotypes of Dependency Among Packages:  access: the source package is granted the right to reference the elements of the target package (:: convention)  import: a kind of access; the public contents of the target package enter the flat namespace of the source as if they had been declared in the source packageName subPackageName packageName PackageClass > + OrderForm + TrackingForm - Order Client +OrderRules -GUI:Window Policies > +Window +Form #EventHandler GUI > imports exports