Return to home page
Searching: Muskingum library catalog
Some OPAL libraries remain closed or are operating at reduced service levels. Materials from those libraries may not be requestable; requested items may take longer to arrive. Note that pickup procedures may differ between libraries. Please contact your library for new procedures, specific requests, or other assistance.
  Previous Record Previous Item Next Item Next Record
  Reviews, Summaries, etc...
Author Alebrahim, Azadeh,
Title Bridging the gap between requirements engineering and software architecture : a problem-oriented and quality-driven method / Azadeh Alebrahim ; with a foreword by Maritta Heisel.
Imprint Wiesbaden : Springer Vieweg, 2017.

View online
View online
Author Alebrahim, Azadeh,
Series Research
Research (Wiesbaden, Germany)
Subject Requirements engineering.
Software engineering.
System design.
Alt Name Heisel, Maritta,
Description 1 online resource.
polychrome rdacc
Bibliography Note Includes bibliographical references.
Summary This book systematically identifies the lack of methodological support for development of requirements and software architecture in the state-of-the-art. To overcome this deficiency, the QuaDRA framework is proposed as a problem-oriented approach. It provides an instantiation of the Twin Peaks model for supporting the intertwining relationship of requirements and software architecture. QuaDRA includes several structured methods which guide software engineers in quality- and pattern-based co-development of requirements and early design alternatives in an iterative and concurrent manner. Contents Context Elicitation & Problem Analysis Architectural Pattern Selection & Application Domain Knowledge Analysis Requirements Interaction Analysis Software Architecture Alternatives Derivation & Evaluation Problem-Oriented Requirements Engineering for Software Product Lines Target Groups Students in the software engineering discipline Researchers who aim at investigating the relationship between requirements engineering and software architecture Practitioners such as software engineers working in the areas of requirements engineering and software architecture design The Author Ms. Azadeh Alebrahim is currently working as an IT consultant. She advises the customers on IT Service Management, process optimization, restructuring the IT organization, and digitalization.
Contents Foreword; Preface; Acknowledgements; Contents; Acronyms; 1 Introduction; 1.1 Problem Statement; 1.2 Research Questions & Contribution; 1.2.1 Research Questions; 1.2.2 Contribution; 1.3 Outline; 2 Background; 2.1 Requirements Engineering; 2.1.1 Quality Requirements; 2.1.2 Problem Frames; 2.2 Software Architecture Concepts; 2.2.1 Definition of Software Architecture; 2.2.2 Difference between Architecture and Design; 2.2.3 Architectural Patterns; 2.2.4 Quality-specific Mechanisms and Tactics; 2.2.5 Viewpoint Models; 2.2.6 Architecture Description Languages vs UML; 2.2.7 Architecture Evaluation.
2.3 UML Profiles2.3.1 UML profile for Problem Frames; 2.3.2 Architecture Profile; 2.3.3 Dependability Profile; 2.3.4 MARTE Profile; 2.4 Life-Cycle Expressions; 2.5 Variability Modeling; 2.6 Case Study Smart Grid; 2.6.1 Description of Smart Grids; 2.6.2 Functional Requirements; 2.6.3 Security Requirements; 2.6.4 Performance Requirements; 3 Framework for Identifying Meta-Requirements; 3.1 Introduction; 3.2 Meta-Requirement Derivation; 3.2.1 Essential Meta-Requirements; 3.2.2 Recommended Meta-Requirements; 3.2.3 Optional Meta-Requirements; 3.2.4 Method Characteristics.
3.3 The Evaluation Framework NIMSAD3.3.1 Methodology Context; 3.3.2 Methodology User; 3.3.3 Methodology Contents; 3.3.4 Evaluation; 3.4 Our Proposed Evaluation Framework; 3.5 Related Review; 3.6 Research Method; 3.6.1 Planning Phase; 3.6.2 Conducting Phase; 3.7 Results and Discussion; 3.7.1 Description of Selected Methods; 3.7.2 Results of the SLR; 3.8 Comparative Evaluation; 3.8.1 Value Assignment Schema; 3.8.2 Framework Application; 3.9 Threats to Validity; 3.10 Contributions; 4 Phase 1: Context Elicitation & Problem Analysis; 4.1 Introduction; 4.2 UML4PF Extension for Quality Requirements.
4.3 Method for Problem-oriented Requirement Analysis4.4 Related Work; 4.5 Contributions; 5 Phase 2: Architectural Pattern Selection & Application; 5.1 Introduction; 5.2 Artifacts and their Relations; 5.3 External Input for the Process; 5.3.1 Question Catalog (Questions); 5.3.2 Question Catalog (Indicator Questions); 5.3.3 Relations between Problem Frames and Questions; 5.3.4 Benefits and Liabilities of Architectural Patterns; 5.3.5 Architectural Pattern Catalog; 5.4 The Pattern Selection Process; 5.5 Application to the Case Study Smart Grid; 5.6 Derivation of Initial Architecture.
5.6.1 Design Desicion regarding Architectural Pattern Selection5.6.2 Design Desicion regarding Gateway Physical Boundary; 5.6.3 Further Iterations -- Problem Diagram Splitting; 5.6.4 Method for Deriving Initial Architecture; 5.7 Related Work; 5.8 Contributions; 6 Phase 3: Domain Knowledge Analysis; 6.1 Introduction; 6.2 Structured Meta-Process; 6.3 Structured Object-Process; 6.4 Related Work; 6.5 Contributions; 7 Phase 4: Requirements Interaction Analysis; 7.1 Introduction; 7.2 Functional Requirements Interaction Detection; 7.2.1 Sunblind Example.
Note Online resource; title from PDF title page (EBSCO, viewed April 13, 2017).
ISBN 9783658176945 (electronic bk.)
3658176946 (electronic bk.)
ISBN/ISSN 10.1007/978-3-658-17694-5
OCLC # 982121213
Additional Format Print version: Alebrahim, Azadeh. Bridging the Gap between Requirements Engineering and Software Architecture : A Problem-Oriented and Quality-Driven Method. Wiesbaden : Springer Fachmedien Wiesbaden, 2017 9783658176938

If you experience difficulty accessing or navigating this content, please contact the OPAL Support Team