Chap03PPT_Update

Chap03PPT_Update - Chapter 3 Models for Software...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 3 Models for Software Architecture
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Objectives Introduce concepts of the view models of software architecture Discuss the UML notations as modeling tools for software architecture specification
Background image of page 2
Agenda Overview 4+1 View Model UML for Software Architecture Structural Diagrams Behavioral Diagrams
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Overview Software architecture a high-level of abstraction of a software system by employing decomposition, composition, architectural styles, and quality attributes. Describe the collection of Components Connections Interactions between these components. Also specify the deployment configuration of all components and connections. Its design must conform to the functional and non- functional requirements of the software project.
Background image of page 4
Many effective ways to describe a software architecture Formally (formal modelling is applied at the level of style) informally. To Describe the business concepts and processes: Box-and-line diagrams are often used. Descriptions of components and connectors Provide clarify understanding ( intuitive interpretation ). Overview (cont)
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 6
The “4+1” view model Another way to show different views of the functional and non-functional requirements There are 5 views in the model the logical view Identify software modules and their boundaries, interfaces, external environment, usage scenarios, etc. the process view Addresses non-functional requirements such as module communication styles and performance issues at runtime. the development view Organizes the software units according to the actual file or directory structure the physical view Specify the deployment infrastructure in terms of software, hardware, and networking configurations, installation , and deployment for delivery purposes the user interface view 4+1 view Model
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
UML for Software Architecture With a software-intensive system, the Unified Modeling Language (UML) is Is a graphical language for visualizing • specifying • constructing documenting the artifacts Offer a standard way to draw a system’s design ( system’s blueprints ), Including conceptual notions such as Business processes • System functions Concrete designs such as programming language statements, database schemas, and reusable software components.
Background image of page 8
a typical OO analysis and design notational tool provides many useful diagrams used to map requirement specifications to architectural designs UML diagram could be group into 2 major categories: Structural (static) Behavioral (dynamic) sequence diagram, collaboration diagram, activity diagram, etc. – With object collaboration, interaction, activity, and concurrency notation.
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 66

Chap03PPT_Update - Chapter 3 Models for Software...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online