10IS81

The Eduladder is a community of students, teachers, and programmers just interested to make you pass any exams. So we solve previous year question papers for you.
See Our team
Wondering how we keep quality?
Got unsolved questions?

Ask Questions


You are here:Open notes-->VTU-->10IS81

10IS81

How to study this subject



UNIT–16 HoursIntroduction: The Architecture Business Cycle: Where doarchitectures come from?Softwareprocesses and the architecture business cycle;whatmakes a“good” architecture?What software architecture is and what it is not; Other points of view; Architecturalpatterns, reference models and referencearchitectures; Importance of softwarearchitecture; Architectural structures and views.

UNIT–27 HoursArchitectural Styles and Case Studies: Architectural styles; Pipes and filters; Dataabstraction and object-oriented organization; Event-based, implicit invocation; Layeredsystems; Repositories; Interpreters; Process control; Other familiar architectures;Heterogeneous architectures. CaseStudies: Keyword in Context; Instrumentation software;Mobilerobotics; Cruisecontrol;Three vignettes in mixed style.

UNIT–36 HoursQuality: Functionality and architecture; Architecture and quality attributes; System qualityattributes; Quality attribute scenarios in practice; Other system quality attributes;Business qualities; Architecture qualities. Achieving Quality: Introducing tactics;Availability tactics; Modifiability tactics; Performance tactics; Security tactics;Testability tactics; Usability tactics;Relationship of tactics to architectural patterns;Architectural patterns and styles.

UNIT–47 HoursArchitectural Patterns–1: Introduction;from mud to structure: Layers, Pipes and Filters,Blackboard.

UNIT–57 HoursArchitectural Patterns–2: Distributed Systems: Broker; Interactive Systems: MVC,Presentation-Abstraction-Control.

UNIT–66 HoursArchitectural Patterns–3: Adaptable Systems: Microkernel; Reflection.

UNIT–76 HoursSome Design Patterns: Structural decomposition: Whole–Part;Organization of work:Master–Slave; Access Control: Proxy.

UNIT–87 HoursDesigning and Documenting Software Architecture: Architecture in thelife cycle;Designing the architecture; Forming the team structure; Creating a skeletal system. Uses ofarchitecturaldocumentation;views; choosing the relevant views; documentinga view;documentation across views.

Text Books:

1.Len Bass, Paul Clements, Rick Kazman: Software Architecture in Practice, 2ndEdition, Pearson Education, 2003. (Chapters 1, 2, 4, 5, 7, 9)2.Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, MichaelStal: Pattern-Oriented Software Architecture, A System of Patterns, Volume 1, JohnWiley and Sons, 2007. (Chapters 2, 3.1 to 3.4)3.Mary Shaw and David Garlan: Software Architecture-Perspectives on an EmergingDiscipline, Prentice-Hall of India, 2007. (Chapters 1.1, 2, 3)Reference Books:1.E. Gamma, R. Helm, R. Johnson, J. Vlissides: Design Patterns-Elements ofReusable Object-Oriented Software, Pearson Education, 1995.Web Reference:http://www.hillside.net/patterns/


Official Notes


Add contents here

Notes from other sources

Download from here

  Sjbit Notes

Model question papers


Assignment

Previous year question papers

Question Paper

Solution

Useful links


Add contents here

Editors

RajivRajivRajivRajivRajivneenu2


Join eduladder!