05 Viewpoints and Perspectives

Question 1

Constraints

Answer 1

Mandated by environment, technology, integrations, bussiness & stakeholders, laws & standards, deadlines.

Little or not control - but accounted for.

Question 2

View

Answer 2

A representation of one or more aspects of an architecture

Illustrates how the architecture addresses one or more concerns.

Question 3

View Scope

Answer 3

What structural aspects of the architecture are you trying to represent?

Question 4

Element types:

Answer 4

What types(s) of architectural element are you trying to categorize?

Question 5

Audience

Answer 5

What class(es) of stakeholder is the view aimed at?

Question 6

Audience expertise:

Answer 6

How much technical understanding do these stakeholders have?

Question 7

Scope of concerns

Answer 7

What stakeholder concerns is the view intended to address?

Question 8

Level of detail

Answer 8

How much do these stakeholders need to know about these aspect of the architecture?

Question 9

Viewpoint

Answer 9

A collection of patterns, templates, and convetions for constructing one type of view

The guidelines, principles and template models for constructioning its views.

Defines a standard approach, language, and even metamodel for describing different aspects of a system.

Question 10

Benefits of Viewpoints

Answer 10

Separation of concerns
Communication with stakeholder group
Management of complexity
Improved devloper focus

Question 11

Pitfalls of Viewpoints

Answer 11

Inconsistency
Selection of wrong set of views
Fragmentation

Question 12

Context Viewpoint

Answer 12

Describes the relationships dependencies, and interactions between the system and its environment (the people, systems, and external entities with which it interacts)

Question 13

What viewpoints characterize the fundamental organization of the system?

Answer 13

Functional
Information
Concurrency Viewpoints

Question 14

Development Viewpoint

Answer 14

Exists to support the system’s construction

Question 15

What viewpoints characterize the system oncie in its live environment?

Answer 15

Deployment and Operational

Question 16

Crosscutting Concerns

Answer 16

Architectural decisions address concerns that are common to many or all views.

Normally driven by the need to for the system to exhibit a certain quality property rather than to proivde a particular function.

Question 17

Security

Answer 17

Consider process security, information security, deployment security, operational security.

Question 18

Perspectives

Answer 18

A collection of architectural activities, tactics, and guidelines

used to ensure that a system exhibits a particular set of related quality properties

Gudies the process of design so that the system will exhibit one or more important qualities

Question 19

Perspective Benefits

Answer 19

Defines concerns
Provides common conventions
Describes validation
Offers recognized solutions
Enables a systematic approach

Question 20

Pitfall

Answer 20

Conflicts between persepctives
Stakeholder concerns and priorities are different for every system.