Packages and Deployment Software Engineering 67528 Fall 2012

Packages and Deployment Software Engineering 67528 Fall 2012

Packages and Deployment • Purpose of Packages – Organizes Modeling elements into groups – Necessary for large subsystems – Idea is to manipulate these packages as groups – Tend to change together

Packages and Deployment • Terms and Concepts for packages – Names – Owned Elements – Visibility – Importing Exporting

Packages and Deployment • What to Model – Modeling groups of elements that are conceptually close – Modeling architectural views

Packages and Deployment • Summary – Packages provide a border around a set of related elements – Export only elements that other packages need to see – Minimize nesting for comprehension purposes – Size consideration too large (clumsy) too small(elements that can be grouped naturally are not together)

Packages and Deployment • Deployment and Artifacts – SW system consists of logical and physical aspects – Logical are classes, interfaces – Physical are Nodes and Artifacts – Artifacts are things that participate in the system’s execution (e. g. sources, scripts etc). Versions of artifacts maintained with configuration control like GIT – Nodes are things that execute artifacts. In multiprocessor systems modeling these issues are of utmost importance