[]{.cart-text} {.btn .cart .open-checkout} []{.btn-text-span .d-none .d-sm-inline-block .d-lg-none .d-hg-inline-block}{.btn .btn-secondary .checkout .open-checkout}
{.home} / UML{.type} / Modeling Business Systems{.type}
Constructing Package Diagrams {#constructing-package-diagrams .title}
The following checklist shows the steps that are necessary for the construction of package diagrams. Subsequently, we will further explain the individual steps.
Checklist 3.7 Constructing Package Diagrams in the Internal View
- Develop an initial package diagram of the business system---Which workers and business objects make up the business system?
- Find additional organization units---Who else is there?
- Assign workers and business objects to the organization units---Who belongs where?
- Find additional organization units, workers, or business objects---What else is there?
- Verify the view---Is everything correct?
Develop an Initial Package Diagram of the Business System---Which Workers and Business Objects Make up the Business System?
At first, the entire business system makes up the organization unit that is supposed to be depicted. In our case, this is passenger services (see Figure 3.32). Initially, we search for relevant worker roles (jobs) and business objects for this organization unit. Existing job descriptions and organization charts can be helpful for this:
Find Additional Organization Units---Who Else is There?
Potentially, the organization unit can be divided into further organization units (divisions, teams, groups). You can use organization charts and job descriptions as the basis and select the organization units that are relevant for the model. Relevant organization units and jobs are those that are directly integrated into the processing of goods and services.
In our case study, we divide passenger service in further organization units: check-in and boarding. A further division is only wise if it is important for the illustration of business processes. For instance, a secretary pool is not important for the business processes under consideration.
Assign Workers and Business Objects to the Organization Units---Who Belongs Where?
Employees and business objects have to be assigned to the additional organization units. You can see in Figure 3.33 that the business objects were divided. Because of this, structure and assignments are clearly recognizable.
Find Additional Organization Units, Workers, or Business Objects---What Else is There?
UML package diagrams representing organization units should not be confused with organization charts. In fact, organization charts are related to package diagrams as they are shown here. However, package diagrams contain business objects in addition to employees. From organization charts we can derive hierarchical structure and the roles of the various workers, and use them as the basis for the construction of package diagrams:
Verify the View---Is Everything Correct?
The completed package diagram can be checked with the following checklist:
Checklist 3.8 Verifying Package Diagrams in the Internal View
- Are all workers and organization units that are affected by the processing of goods and services provided by the business system included in the package diagram?
- Are there no workers and organization units that are unrelated to the processing of goods and services of the business system included in the package diagram?
- Are all business objects that are needed for providing and processing goods and services included in the package diagram?
- Are there no business objects that are unrelated to the processing of goods and services of the business system included in the package diagram?
Read next
Class Diagram []{.fa .fa-arrow-right}{.btn .btn-primary rel=“next”}
Return
[]{.fa .fa-arrow-left} Package Diagram{.btn .btn-default rel=“prev”}
Computer Science Distilled{.btn .btn-landing-ref .btn-hg .btn-block .btn-secondary style=“font-size: 16px; position: relative”}
Do you remember anything at all from your computer science class? Quicksort, Graph traversal, Big’O and other stuff? Revise your memories with our new book on Computer Science.
Psst! Did I mention that we’re offering sexy discounts right now?
{width=“250”
height=“312”
srcset=“/images/content-public/logos/logo-2x.png?id=fee3b4b0a14ba60dc0fe368695d78be9 2x”}{.menu-brand}
- Premium Stuff
- Design Patterns
- AntiPatterns
- Refactoring
- Code Smells
- Refactoring techniques
- Composing Methods
- Moving Features between Objects
- Organizing Data
- Self Encapsulate Field
- Replace Data Value with Object
- Change Value to Reference
- Change Reference to Value
- Replace Array with Object
- Duplicate Observed Data
- Change Unidirectional Association to Bidirectional
- Change Bidirectional Association to Unidirectional
- Replace Magic Number with Symbolic Constant
- Encapsulate Field
- Encapsulate Collection
- Replace Type Code with Class
- Replace Type Code with Subclasses
- Strategy
- Replace Subclass with Fields
- Simplifying Conditional Expressions
- Simplifying Method
Calls
- Rename Method
- Add Parameter
- Remove Parameter
- Separate Query from Modifier
- Parameterize Method
- Replace Parameter with Explicit Methods
- Preserve Whole Object
- Replace Parameter with Method Call
- Introduce Parameter Object
- Remove Setting Method
- Hide Method
- Replace Constructor with Factory Method
- Replace Error Code with Exception
- Replace Exception with Test
- Dealing with Generalisation
- UML
- Introduction
- Basic Principles and Background
- Modeling Business Systems
- Business Processes and Business Systems
- One Model---Two Views
- External View
- The Elements of a View
- Use Case Diagrams
- Constructing Use Case Diagrams
- Activity Diagrams
- Constructing Activity Diagrams
- Sequence Diagrams
- Constructing Sequence Diagrams
- High-Level Sequence Diagrams
- Sequence Diagrams for Scenarios of Business Use Cases
- Internal View
- Package Diagram
- Constructing Package Diagrams
- Class Diagram
- Constructing Class Diagrams
- Activity Diagram
- Modeling IT Systems
- External View
- The User View or “I don’t care how it works, as long as it works.”
- The Elements of a View
- Use Case Diagram
- Query Events and Mutation Events
- Use Case Sequence Diagram
- Constructing the External View
- Structural View
- Objects and Classes
- Generalization, Specialization, and Inheritance
- Static and Dynamic Business Rules
- Elements of the View
- Class Diagram
- Constructing Class Diagrams
- The Behavioral View
- The Life of an Object
- The Elements of the View
- Statechart Diagram
- Constructing Statechart Diagrams
- Interaction View
- Seeing What Happens Inside the IT System
- Elements of the View
- Communication Diagram
- Sequence Diagram
- Constructing Communication Diagrams
- Constructing Sequence Diagrams
- Modeling for System
Integration
- Terminology of System Integration
- Messages in UML
- One Model---Two Views
- Process View
- The Business System Model as Foundation
- Elements of the View
- Activity Diagrams
- Sequence Diagram
- Constructing Diagrams in the Process View
- The Static View
- Elements of the View
- Class Diagram
- Constructing Class Diagrams
- Transforming Data from the IT System to the Message “passenger list”
- Transformation of UML Messages into Various Standard Formats
Log in Contact us{.userecho-public rel=“nofollow”}
{srcset=“/images/content-public/logos/logo-min-xs-2x.png?id=34fc05750336c33b7815e231a0f227df 2x”}{.navigation-brand}
Shop Now!{.btn .btn-md .btn-primary .btn-featured}
-
[Contact us]{.caption .d-none .d-xl-inline-block}{.userecho-private rel=“nofollow”}
-
Forum{.userecho-public rel=“nofollow”}
-
Contact us{.userecho-private rel=“nofollow”}
© 2007-2023 SourceMaking.com[ / ]{.d-none .d-md-inline}
All rights reserved.
[]{.cart-text} {.btn .cart .open-checkout} []{.btn-text-span .d-none .d-sm-inline-block .d-lg-none .d-hg-inline-block}{.btn .btn-secondary .checkout .open-checkout}
{.home} / UML{.type} / Modeling Business Systems{.type}
Constructing Package Diagrams {#constructing-package-diagrams-1 .title}
The following checklist shows the steps that are necessary for the construction of package diagrams. Subsequently, we will further explain the individual steps.
Checklist 3.7 Constructing Package Diagrams in the Internal View
- Develop an initial package diagram of the business system---Which workers and business objects make up the business system?
- Find additional organization units---Who else is there?
- Assign workers and business objects to the organization units---Who belongs where?
- Find additional organization units, workers, or business objects---What else is there?
- Verify the view---Is everything correct?
Develop an Initial Package Diagram of the Business System---Which Workers and Business Objects Make up the Business System?
At first, the entire business system makes up the organization unit that is supposed to be depicted. In our case, this is passenger services (see Figure 3.32). Initially, we search for relevant worker roles (jobs) and business objects for this organization unit. Existing job descriptions and organization charts can be helpful for this:
Find Additional Organization Units---Who Else is There?
Potentially, the organization unit can be divided into further organization units (divisions, teams, groups). You can use organization charts and job descriptions as the basis and select the organization units that are relevant for the model. Relevant organization units and jobs are those that are directly integrated into the processing of goods and services.
In our case study, we divide passenger service in further organization units: check-in and boarding. A further division is only wise if it is important for the illustration of business processes. For instance, a secretary pool is not important for the business processes under consideration.
Assign Workers and Business Objects to the Organization Units---Who Belongs Where?
Employees and business objects have to be assigned to the additional organization units. You can see in Figure 3.33 that the business objects were divided. Because of this, structure and assignments are clearly recognizable.
Find Additional Organization Units, Workers, or Business Objects---What Else is There?
UML package diagrams representing organization units should not be confused with organization charts. In fact, organization charts are related to package diagrams as they are shown here. However, package diagrams contain business objects in addition to employees. From organization charts we can derive hierarchical structure and the roles of the various workers, and use them as the basis for the construction of package diagrams:
Verify the View---Is Everything Correct?
The completed package diagram can be checked with the following checklist:
Checklist 3.8 Verifying Package Diagrams in the Internal View
- Are all workers and organization units that are affected by the processing of goods and services provided by the business system included in the package diagram?
- Are there no workers and organization units that are unrelated to the processing of goods and services of the business system included in the package diagram?
- Are all business objects that are needed for providing and processing goods and services included in the package diagram?
- Are there no business objects that are unrelated to the processing of goods and services of the business system included in the package diagram?
Read next
Class Diagram []{.fa .fa-arrow-right}{.btn .btn-primary rel=“next”}
Return
[]{.fa .fa-arrow-left} Package Diagram{.btn .btn-default rel=“prev”}
Computer Science Distilled{.btn .btn-landing-ref .btn-hg .btn-block .btn-secondary style=“font-size: 16px; position: relative”}
Do you remember anything at all from your computer science class? Quicksort, Graph traversal, Big’O and other stuff? Revise your memories with our new book on Computer Science.
Psst! Did I mention that we’re offering sexy discounts right now?
{width=“250”
height=“312”
srcset=“/images/content-public/logos/logo-2x.png?id=fee3b4b0a14ba60dc0fe368695d78be9 2x”}{.menu-brand}
- Premium Stuff
- Design Patterns
- AntiPatterns
- Refactoring
- Code Smells
- Refactoring techniques
- Composing Methods
- Moving Features between Objects
- Organizing Data
- Self Encapsulate Field
- Replace Data Value with Object
- Change Value to Reference
- Change Reference to Value
- Replace Array with Object
- Duplicate Observed Data
- Change Unidirectional Association to Bidirectional
- Change Bidirectional Association to Unidirectional
- Replace Magic Number with Symbolic Constant
- Encapsulate Field
- Encapsulate Collection
- Replace Type Code with Class
- Replace Type Code with Subclasses
- Strategy
- Replace Subclass with Fields
- Simplifying Conditional Expressions
- Simplifying Method
Calls
- Rename Method
- Add Parameter
- Remove Parameter
- Separate Query from Modifier
- Parameterize Method
- Replace Parameter with Explicit Methods
- Preserve Whole Object
- Replace Parameter with Method Call
- Introduce Parameter Object
- Remove Setting Method
- Hide Method
- Replace Constructor with Factory Method
- Replace Error Code with Exception
- Replace Exception with Test
- Dealing with Generalisation
- UML
- Introduction
- Basic Principles and Background
- Modeling Business Systems
- Business Processes and Business Systems
- One Model---Two Views
- External View
- The Elements of a View
- Use Case Diagrams
- Constructing Use Case Diagrams
- Activity Diagrams
- Constructing Activity Diagrams
- Sequence Diagrams
- Constructing Sequence Diagrams
- High-Level Sequence Diagrams
- Sequence Diagrams for Scenarios of Business Use Cases
- Internal View
- Package Diagram
- Constructing Package Diagrams
- Class Diagram
- Constructing Class Diagrams
- Activity Diagram
- Modeling IT Systems
- External View
- The User View or “I don’t care how it works, as long as it works.”
- The Elements of a View
- Use Case Diagram
- Query Events and Mutation Events
- Use Case Sequence Diagram
- Constructing the External View
- Structural View
- Objects and Classes
- Generalization, Specialization, and Inheritance
- Static and Dynamic Business Rules
- Elements of the View
- Class Diagram
- Constructing Class Diagrams
- The Behavioral View
- The Life of an Object
- The Elements of the View
- Statechart Diagram
- Constructing Statechart Diagrams
- Interaction View
- Seeing What Happens Inside the IT System
- Elements of the View
- Communication Diagram
- Sequence Diagram
- Constructing Communication Diagrams
- Constructing Sequence Diagrams
- Modeling for System
Integration
- Terminology of System Integration
- Messages in UML
- One Model---Two Views
- Process View
- The Business System Model as Foundation
- Elements of the View
- Activity Diagrams
- Sequence Diagram
- Constructing Diagrams in the Process View
- The Static View
- Elements of the View
- Class Diagram
- Constructing Class Diagrams
- Transforming Data from the IT System to the Message “passenger list”
- Transformation of UML Messages into Various Standard Formats
Log in Contact us{.userecho-public rel=“nofollow”}
{srcset=“/images/content-public/logos/logo-min-xs-2x.png?id=34fc05750336c33b7815e231a0f227df 2x”}{.navigation-brand}
Shop Now!{.btn .btn-md .btn-primary .btn-featured}
-
[Contact us]{.caption .d-none .d-xl-inline-block}{.userecho-private rel=“nofollow”}
-
Forum{.userecho-public rel=“nofollow”}
-
Contact us{.userecho-private rel=“nofollow”}
© 2007-2023 SourceMaking.com[ / ]{.d-none .d-md-inline}
All rights reserved.