Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

IEEE-1471- Architectural Description of Software-Intensive Systems

No description
by

Christian Tzolov

on 28 April 2011

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of IEEE-1471- Architectural Description of Software-Intensive Systems

Software System
Architecture
has an
Architectural
Description (AD)

is described by
Stakeholders
documents architecture for
exists to address
the needs of
has
View
AD is comprissed of
Concern
confirms to
Viewpoint
Fundamental organization of a system embodied in its components, their relationships to each other and to the environment and the principles guiding its design and evolution
requirement, objective or an intention a stakeholder has for the architecture
person, group, or entity with an interest in or concerns about the realization of the architecture
Documents an architecture in way its stakeholders can understand and demonstrate that the architecture met their concerns.
Illustrates how the architecture addresses one or more of concerns held by one or more stakeholders
It is not possible to capture the functional features and quality properties of a complex system in a single model
Representation of a whole system from the
perspective of a set of concerns
addresses
Guidelines and conventions for constructing one view
Describes the architecture that supports the software development proces
Viewpoint
catalog
Functional
Describes systems’ functional elements, responsibilities, interfaces and primary interactions
Describes how the architecture stores, manipulates, manages and distributes information
Informational
Development
Describes the environment into which the system will be deployed, capturing the dependencies that system has on its runtime environment
Deployment
Describes how the system will be operated, administrated, and supported when it is running in production environmen
Operational
Concerns
Functional Capabilities
External Interfaces
Internal Structure
Design Quality
Module organization
Common processing
Standardization of design
Standardization of testing
Instrumentation
/Maven, SVN, Hudson, Sonar, JProfiler/
Code-line organization
Identifies the stakeholders
Identifies set of concerns
Define language and notation
Problem
Space

Requirements
Analysis
Solution
Space

Software Design
Architecture
Definition
Process
Bridges
the gap
Architecturally
Significant

has wide impact on
Structure
Performance
Scalability
Security
Reliability
Evolvability

focus on
focus on
Every system has an architecture.
Either Accidental or Intentional
System Static Structures
System Dynamic Structures
Externally Visible System Properties
Design-time elements and their structure
Runtime elements and their interactions
System-Environment interaction (APIs)
Quality properties
Irreversibility is prime drivers of complexity
concerns, problems, system elements
Understand the requirements and their importance
Identify and mange the
Architecturally Significant elements
Feed back what can and cannot be achieved
contain complexity by reducing irreversibility
IEEE-1471- Architectural Description of Software-Intensive Systems
Architecture Represents:
Full transcript