000780814 000__ 05370cam\a2200553Mu\4500
000780814 001__ 780814
000780814 005__ 20230306143201.0
000780814 006__ m\\\\\o\\d\\\\\\\\
000780814 007__ cr\nn\nnnunnun
000780814 008__ 170415s2017\\\\gw\\\\\\o\\\\\000\0\eng\d
000780814 019__ $$a982150880$$a982234046$$a982339448$$a982417842$$a982450918$$a982584924$$a982846657$$a982987337$$a988378249$$a1005758554$$a1012071102
000780814 020__ $$a9783658176945
000780814 020__ $$a3658176946
000780814 020__ $$z9783658176938
000780814 020__ $$z3658176938
000780814 0247_ $$a10.1007/978-3-658-17694-5$$2doi
000780814 035__ $$aSP(OCoLC)ocn982121213
000780814 035__ $$aSP(OCoLC)982121213$$z(OCoLC)982150880$$z(OCoLC)982234046$$z(OCoLC)982339448$$z(OCoLC)982417842$$z(OCoLC)982450918$$z(OCoLC)982584924$$z(OCoLC)982846657$$z(OCoLC)982987337$$z(OCoLC)988378249$$z(OCoLC)1005758554$$z(OCoLC)1012071102
000780814 040__ $$aN$T$$beng$$erda$$epn$$cN$T$$dN$T$$dGW5XE$$dOCLCF$$dYDX$$dNJR$$dCOO$$dCAUOI$$dEBLCP$$dCHVBK$$dUAB$$dMERER$$dESU$$dAZU$$dUPM$$dJG0$$dIOG$$dOTZ$$dVT2$$dIDB$$dU3W$$dMERUC$$dOCLCQ
000780814 049__ $$aISEA
000780814 050_4 $$aTA180
000780814 08204 $$a624.068$$223
000780814 1001_ $$aAlebrahim, Azadeh.
000780814 24510 $$aBridging the gap between requirements engineering and software architecture :$$ba problem-oriented and quality-driven method /$$cAzadeh Alebrahim ; with a foreword by Maritta Heisel.
000780814 260__ $$aWiesbaden :$$bSpringer Fachmedien Wiesbaden,$$c2017.
000780814 300__ $$a1 online resource (514 pages)
000780814 336__ $$atext$$btxt$$2rdacontent
000780814 337__ $$acomputer$$bc$$2rdamedia
000780814 338__ $$aonline resource$$bcr$$2rdacarrier
000780814 4901_ $$aResearch
000780814 500__ $$a7.2.2 Method for Functional Requirements Interaction Detection
000780814 504__ $$aIncludes bibliographical references.
000780814 5050_ $$aForeword; 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
000780814 5058_ $$a2.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
000780814 5058_ $$a3.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
000780814 5058_ $$a4.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
000780814 5058_ $$a5.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
000780814 506__ $$aAccess limited to authorized users.
000780814 588__ $$aDescription based on print version record.
000780814 650_0 $$aRequirements engineering.
000780814 650_0 $$aSoftware engineering.
000780814 650_0 $$aSystem design.
000780814 7001_ $$aHeisel, Maritta,$$eauthor of foreword.
000780814 77608 $$iPrint version:$$aAlebrahim, Azadeh$$tBridging the Gap between Requirements Engineering and Software Architecture : A Problem-Oriented and Quality-Driven Method$$dWiesbaden : Springer Fachmedien Wiesbaden,c2017$$z9783658176938
000780814 830_0 $$aResearch (Wiesbaden, Germany)
000780814 85280 $$bebk$$hSpringerLink
000780814 85640 $$3SpringerLink$$uhttps://univsouthin.idm.oclc.org/login?url=http://link.springer.com/10.1007/978-3-658-17694-5$$zOnline Access$$91397441.1
000780814 909CO $$ooai:library.usi.edu:780814$$pGLOBAL_SET
000780814 980__ $$aEBOOK
000780814 980__ $$aBIB
000780814 982__ $$aEbook
000780814 983__ $$aOnline
000780814 994__ $$a92$$bISE