SOFTWARE ARCHITECTURE

SOFTWARE ARCHITECTURE

1. 3. Reflections on an Evolving Discipline

   • David Garlan
     • 1987/1990
       • software architecture,
       • self-adaptive systems
       • formal methods
       • cyber-physical systems
   • Mary Saw
     • Areas
       • programming languages
       • specifications
       • abstraction techniques.

2. 2. Evaluating and Improving Software Architecture

   • Disadvantages
     • Failures in software
     • Significant costs
   • Advantage
     • Eficiency
       • Functionality
         • Evaluation
           • Reliability
             • Frequency and severity failures
             • Recovery capacity
             • Failure prediction ability
           • Help development of software.
           • Detect fauls
           • FODA
             • Threats/Strengths/Weaknesses/Opportunities
         • Security of software
         • Continuos update
         • Architecture refactoring
         • Improve internal quality
         • Improve external quality
       • -Revenues depend of software.
       • - Solve problems
       • Selft-adaptive systems
       • Performance speed

3. 1. HOW MODELLING SOFTWARE ARCHITECTURE?

   • STANDARD
     • USING
       • SOFTWARE
         • ACME
           • Components -Connectors -Systems (Jairo
       • Runtime architecture (C&C)
         • notations, tools
           • components – connectors -system
     • UML, MDA
       • Considering
         • Modules
           • Runtime entities – Devices – Developers
     • improve
       • Clarity of architectural designs