1 - Software Architectures Course Motivation Why...

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

View Full Document Right Arrow Icon
Software Architectures
Background image of page 1

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

View Full DocumentRight Arrow Icon
Course Motivation Why Architectures ?
Background image of page 2
Basics … Programs, Programming, Idioms Design, Implement, Testing Programs vs Software Software, Software Engg. Software lifecycle Design Process Software, Design, Patterns Typical engineering aspects Requirements, specification, design, analysis, risk management, development, testing, integration, maintenance … Hallmark of “good engineering”: Ability to determine post-production “behavior” during the production process Architecture, Arch. Design, Frameworks
Background image of page 3

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

View Full DocumentRight Arrow Icon
Role of Design Process Design acts as the medium between requirements specs. and implementation Compartmentalization of the product development process: Ultimate cost / benefit leverage: Good designs lead to good products Bad implementation of good design can be rectified but good implementation of bad design is fruitless
Background image of page 4
Evolution of Design Over the years software design has matured: High level design (Architecture) vs. detailed design Design principles incorporated into implementation tools and techniques Tools support for design Design patterns and architectural frameworks.
Background image of page 5

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

View Full DocumentRight Arrow Icon
Architectural Design Focus of the course: Architectural Design Design Patterns and other peripheral aspects of design will be referred to but not emphasized. Thin on process Emphasis on applying architectures for real problems (rather than studying them) Individualistic approach (as opposed to team- oriented approach) Communicating design choices is important!
Background image of page 6
Understanding Architectures Issues of Architecture Design
Background image of page 7

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

View Full DocumentRight Arrow Icon
What is an Architecture A description of system structure(s) Module decomposition, process, deployment, layered, etc First artifact that can be analyzed to determine how well its quality attributes are being achieved, and it also serves as the project blueprint Serves as the vehicle for communication , is the manifestation of earliest design decisions Re-usable abstraction that can be transferred to new systems Architectural view of a system is abstract , distilling away details of implementation, algorithm, and data representation and concentrating on the behavior and interaction of ‘black box’ elements
Background image of page 8
Example Architectures www – desire to share documents quickly and easily without centralized control Air traffic control – safety through ultra- high availability Architectures with smooth integration of subsystems Infrastructures like .NET, J2EE & EJB – standardizing architectural approaches
Background image of page 9

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

View Full DocumentRight Arrow Icon
Architectural Issues Types of choices that architects must make to achieve their quality goals ( design trade-offs ) How organizational goals affect the final systems Designing, building, evaluating software architectures ( arch. design process ) Techniques for understanding quality requirements in the context of an architecture
Background image of page 10
Issues contd. . Architecture representation and reconstruction
Background image of page 11

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

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

This note was uploaded on 03/14/2010 for the course CSE SS ZG653 taught by Professor Sundarsb during the Summer '10 term at Birla Institute of Technology & Science.

Page1 / 44

1 - Software Architectures Course Motivation Why...

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

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