0
IT6602                                          SOFTWARE ARCHITECTURES                                            L T P C
3 0 0  3
OBJECTIVES:
  • Understand software architectural requirements and drivers
  • Be exposed to architectural styles and views
  • Be familiar with architectures for emerging technologies

UNIT I          INTRODUCTION AND ARCHITECTURAL DRIVERS                                                      9
Introduction – What is software architecture? – Standard Definitions – Architectural structures – Influence  of  software  architecture  on  organization-both  business  and  technical    –  Architecture Business Cycle- Introduction – Functional requirements – Technical constraints – Quality Attributes.

UNIT II         QUALITY ATTRIBUTE WORKSHOP                                                                               9
Quality Attribute Workshop – Documenting Quality Attributes – Six part scenarios – Case studies.

UNIT III        ARCHITECTURAL VIEWS                                                                                                9
Introduction – Standard Definitions for views – Structures and views - Representing views-available notations – Standard views – 4+1 view of RUP, Siemens 4 views, SEI's perspectives and views – Case studies

UNIT IV      ARCHITECTURAL STYLES                                                                                               9
Introduction – Data flow styles – Call-return styles – Shared Information styles - Event styles – Case studies for each style.

UNIT V       DOCUMENTING THE ARCHITECTURE                                                                            9
Good practices – Documenting the Views using UML – Merits and Demerits of using visual languages
–  Need  for  formal  languages  -    Architectural Description  Languages  –  ACME  –  Case  studies. Special topics: SOA and Web services – Cloud Computing – Adaptive structures

OUTCOMES:
Upon Completion of the course, the students will be able to
  • Explain influence of software architecture on business and technical activities
  • Identify key architectural structures
  • Use styles and views to specify architecture
  • Design document for a given architecture

TEXT BOOKS:
  1. Len Bass, Paul Clements, and Rick Kazman, “Software Architectures Principles and Practices”,
2nd Edition, Addison-Wesley, 2003.
  1. Anthony J Lattanze, “Architecting Software Intensive System. A Practitioner's Guide”, Auerbach
Publications, 2010.

REFERENCES:
  • Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Paulo Merson, Robert Nord, and Judith Stafford, “Documenting Software Architectures. Views and Beyond”, 2nd Edition, Addison-Wesley, 2010.
  • Paul Clements, Rick Kazman, and Mark Klein, “Evaluating software architectures: Methods and
case studies. Addison-Wesley, 2001.
  • Rajkumar Buyya, James Broberg, and Andrzej Goscinski, “Cloud Computing. Principles and
Paradigms”, John Wiley & Sons, 2011
  • Mark Hansen, “SOA Using Java Web Services”, Prentice Hall, 2007

  • David Garlan, Bradley Schmerl, and Shang-Wen Cheng, “Software Architecture-Based Self- Adaptation,” 31-56. Mieso K Denko, Laurence Tianruo Yang, and Yan Zang (eds.), “Autonomic Computing and Networking”. Springer Verlag, 2009



#################################################################################################


ANNA UNIVERSITY | SYLLABUS | UNIVERSITY QUESTION PAPER | NOTES
ANNA UNIVERSITY | SYLLABUS | UNIVERSITY QUESTION PAPER | NOTES

Post a Comment Blogger

 
Top