MODEL-DRIVEN SOFTWARE SYSTEMS DEVELOPMENT USING THE META-ARTIFACT PROCESS [electronic resource].
- [S.l.] : AUERBACH PUBLICATIONS, 2024.
- 1 online resource
Cover -- Half Title -- Title Page -- Copyright Page -- Dedication -- Table of Contents -- Preface -- Note -- Chapter 1 Introduction -- Approach -- Goals -- Role of Requirements -- Explicit and Tacit Knowledge -- Knowledge Management Overview -- Notes -- Chapter 2 Meta-Artifact Process -- Dynamic Interdependence of the Eight Elements of MAP -- Gaps -- Roles of Knowledge Management, and Selected Extensions and Enablers in Mitigating Gaps-Detailed Discussion -- Knowledge Management -- Extensions and Enablers -- Further Benefits of MAP-Detailed Discussion -- Capture Domain Knowledge Recursive Use of Meta-Artifact -- Domain-Wide Focus -- Single Repository -- Team Continuity -- Impact of Evolving Technology On Requirements -- Hidden Risks of Increasing Automation-Detailed Discussion -- Hidden Risks of Breakdowns-Detailed Discussion -- Notes -- Chapter 3 Meta-Artifact -- Properties, Qualities, and Capabilities-Detailed Discussion -- Visual Representation of the Meta-Artifact -- Knowledge Management Impact-Detailed Discussion -- Impact On Problem and Solution Space Gaps -- Need for Special-Purpose Views Results of Key Properties, Qualities, and Capabilities-Detailed Discussion -- Unifying Vision -- Special-Purpose Views -- Visual Verification and Validation -- Process and Product Are Different Views Rather Than Separate Things -- Active Semantic Chain -- Eliminate Temporal and Semantic Gaps-Detailed Discussion -- Notes -- Chapter 4 Domain Rules Analysis -- Domain Rules Analysis and Related Technologies-Detailed Discussion -- Practical Considerations for Domain Rules Analysis -- Domain Rules-Detailed Discussion -- Application of Domain Rules Frameworks and Other Benefits to Justify Domain Rules Analysis-Detailed Discussion -- Chapter 5 Bifurcated Architecture -- Business Rules and Volatile Variability-Detailed Discussion -- Means of Identifying Business Rules -- Commonality and Variability -- Objective of Bifurcated Architecture-Detailed Discussion -- Architecture Neutrality -- Role of Object-Oriented Technology -- Chapter 6 Architecture Centricity -- Central Role of Architecture Centricity -- Unifying Vision -- Process Implications-Detailed Discussion -- Chapter 7 Procedure to Apply MAP -- Step Summary -- Diagram of Steps Modeling Considerations in Applying the Procedure-Detailed Discussion -- Chapter 8 Summary Review -- Impact of MAP -- Interaction of the Three Extensions -- Architecture Centricity -- Changing Roles -- Glossary -- Note -- Bibliography -- Index
The book is concerned in particular with software systems, specifically software code. It describes three major innovations for making software, which are combined with five widely used enabling technologies, to provide a complete, hypothesis-driven, software development process.