Domain Modeling-Based Software Engineering: A Formal Approach (The International Series on Asian Studies in Computer and Information Science (8))

✍ Scribed by Ruqian Lu, Zhi Jin

• Publisher: Springer
• Year: 2000
• Tongue: English
• Leaves: 272
• Series: The International Series on Asian Studies in Computer and Information Science (8) (Book 8)
• Edition: 2000
• Category: Library

✦ Synopsis

Many approaches have been proposed to enhance software productivity and reliability. These approaches typically fall into three categories: the engineering approach, the formal approach, and the knowledge-based approach. The optimal gain in software productivity cannot be obtained if one relies on only one of these approaches. Thus, the integration of different approaches has also become a major area of research.
No approach can be said to be perfect if it fails to satisfy the following two criteria. Firstly, a good approach should support the full life cycle of software development. Secondly, a good approach should support the development of large-scale software for real use in many application domains. Such an approach can be referred to as a five-in-one approach.
The authors of this book have, for the past eight years, conducted research in knowledge-based software engineering, of which the final goal is to develop a paradigm for software engineering which not only integrates the three approaches mentioned above, but also fulfils the two criteria on which the five-in-one approach is based. Domain Modeling- Based Software Engineering: A Formal Approach explores the results of this research.
Domain Modeling-Based Software Engineering: A Formal Approach will be useful to researchers of knowledge-based software engineering, students and instructors of computer science, and software engineers who are working on large-scale projects of software development and want to use knowledge-based development methods in their work.

✦ Table of Contents

Environment Modeling-Based Requirements Engineering for Software Intensive Systems
Copyright
About the Author
Preface
Organization
Acknowledgments
Introduction
1 - Requirements and Requirements Engineering∗∗This chapter serves to deliver general background knowledge about requirements a ...
1.1 Requirements
1.1.1 System Level Versus Function Level
1.1.2 “What” Versus “How”
1.1.3 Problem Versus Solution
1.1.4 Summary
1.2 Requirements Engineering
1.3 Three Dimensions of Requirements Engineering
2 - Requirements Engineering Methodologies
2.1 Metaphor: “To-Be System Is for Automatically Measuring and Controlling the Reality”
2.2 Metaphor: “To-Be System Is for Fulfilling Real-World Goals That Stakeholders Want to Achieve”
2.3 Metaphor: “To-Be System Is for Improving the Dependencies Among Intentional Actors”
2.4 Metaphor: “To-Be System Is for Enhancing the As-Is System Usage Experience”
2.5 Metaphor: “To-Be System Is for Establishing Relationships Among Phenomena of Reality”
2.6 Summary
3 - Importance of Interactive Environment
3.1 Software-Intensive Systems
3.2 Challenges to Requirements Engineering
3.2.1 Increasing Size and Complexity
3.2.2 Open and Nondeterministic Environment
3.2.3 Situation Awareness and Adaptation
3.2.4 Innovation-Enabled Requirements
3.3 Environment, Requirements, and Specification
3.3.1 Relationships Among the Three
3.3.2 Environment Properties Is the First Citizen
3.3.2.1 First, Requirements Are the Problem That Is Expected to Be Solved
3.3.2.2 Second, Environment Properties Constitute the Context of the Problem
3.3.2.3 Third, the System Is a Candidate Solution for Solving the Problem Within the Context
3.3.3 Interfaces Are Another Concern
3.3.4 Summary
Part One References
Introduction
4 - Ontology-Oriented Interactive Environment Modeling
4.1 Ontology and Ontologies
4.1.1 Background
4.1.2 Different Viewpoints on Ontology
4.1.3 Common Structure of Ontology
4.2 Types of Ontologies
4.3 Ontology-Oriented Domain Modeling
4.3.1 The Process for Ontology-Oriented Domain Modeling
4.3.2 The Structure for Domain Ontology
4.4 Top-Level Environment Ontology
4.4.1 Software System Problem and Its Location
4.4.2 Concept Categories and Associations of System Environment
4.5 Domain Environment Ontology
4.5.1 Conceptualization of Environment Entities
4.5.2 Formalization of Environment Entity
4.5.3 Dependency Between Environment Entities
5 - Domain Environment Ontology Construction
5.1 Domain Environment Modeling via Knowledge Engineering
5.2 Domain Environment Ontology Construction
5.3 Automatic Domain Environment Ontology Construction
Algorithm 5.1. Constructing Basic State Machines
Algorithm 5.2. Constructing Domain Tree-Based Hierarchical State Machine in Terms of the Inheritance Relationship
Algorithm 5.3. Constructing Domain Tree-Based Hierarchical State Machine in Terms of the Component Relationship
5.4 Another Example of Domain Environment Ontology
5.5 Summary
6 - Feature Model of Domain Environment
6.1 Feature Model and Feature Configuration
6.1.1 Primitive Elements in Feature Model
6.1.2 Feature Configuration and Software System Feature Model
6.2 Environment Feature Model
6.2.1 Features for Environment Conceptualization
6.2.2 Hierarchy of Environment Feature Model
6.2.3 Environment Feature Configuration
6.3 Goal Feature Model
6.3.1 Autonomous Entity and Intentional Property
6.3.2 Intentional Goal and Goal Feature Model
6.3.3 Hierarchy of Goal Feature Models
6.4 Summary
Part Two References
Further Reading
Introduction
7 - Effect-Oriented System Capability
7.1 Capability Specification of Semantic Web Services
7.1.1 Capability Description in Web Ontology Language for Services66See footnote 3.
7.1.2 Web Service Modeling in Web Service Modeling Ontology99See footnote 4.
7.1.3 Summary of the Web Service Capability Description
7.2 Effect-Based Capability Model
7.2.1 Effect Upon the Interactive Environment
7.2.2 System Capability Conceptualization
7.3 System Capability Profile
7.3.1 Capability Profile
7.3.2 An Example Capability Profile
7.3.3 Capability Specification Generation
7.4 Summary
8 - Reasoning I: System Capability Comparison and Composition
8.1 Related Work in Service-Oriented Computing
8.1.1 Standard Languages Enabling Matchmaking
8.1.2 Syntactic Similarity-Based Matchmaking
8.1.3 Behavior-Based Intelligent Matchmaking
8.1.4 Service Composition
8.2 Environment Modeling-Based Capability Comparison
8.2.1 Required Capability
8.2.2 Context Similarity
8.2.3 Effect Comparison
8.3 Environment Modeling-Based Capability Composition
8.4 Summary
9 - Reasoning II: System Capability Refinement
9.1 Guided Process for Scenario Description
9.1.1 The Process
9.1.2 An Example
9.2 Scenario-Based Capability Projection
9.2.1 Preliminary
9.2.2 Well-Formed Scenario (Jin et al., 2009)
9.2.3 Heuristic Strategies for Scenario Elaboration (Jin et al., 2009)
9.2.4 Projection Upon Well-Formed Scenario
9.3 Summary
10 - Reasoning III: System Capability Aggregation
10.1 Principles and Architecture
10.1.1 General Principles
10.1.2 Architecture
10.2 Requirements-Driven Agent Aggregation
10.2.1 Capability Projection Rephrasing
10.2.2 Capability Realization Pattern
10.2.3 Capability Aggregation: Notations
10.2.4 Capability Aggregation: Mechanism Design
10.2.5 Capability Aggregation: Benevolent Objective Function
10.3 Capability Assignment Problem (Tang and Jin, 2010)
10.3.1 Problem Definition
10.3.2 Normative Systems
10.3.3 Negotiation-Based Task Assignment
10.4 Summary
Part Three References
Part Four References
Introduction
11 - The System Dependability Problem
11.1 Background and Principles
11.1.1 Background
11.1.2 State of Art
11.1.2.1 Unified Model of Dependability
11.1.3 Principles of Identifying Dependability Requirements
11.2 Cybernetics and Model of Dependable Systems
11.2.1 Cybernetics and Control Loops
11.2.2 Model of Dependable Systems
11.3 Function and Control Capability Profile Cluster Requirements Elicitation and Modeling
11.3.1 Function and Control Capability Profile Cluster Metamodel
11.3.2 Elicitation of Dependability Requirements
11.3.2.1 Hazard and Operability Study–Based Threat and System Behavior Deviation Identification
11.3.2.2 Risk Assessment
11.3.2.3 Control Capability Determination
11.3.2.4 Control Capability Specification
11.3.3 Case Study: Online Stock Trading System
11.3.3.1 Eliciting Dependability Requirements by Identifying Needs for Controllers
11.4 Summary
12 - The System Dynamic Adaptability Concern
12.1 Dynamic Adaptation Mechanisms
12.1.1 Rule-Based Dynamic Adaptation
12.1.2 Goal-Oriented Adaptation Mechanism
12.1.3 Control Loop–Based System Model
12.2 Modeling Dynamic Adaptation Capability
12.2.1 Conformance Among Req, Env, and Spec as Dynamic Adaptation Logic
12.2.2 Structuring the Environment
12.2.3 Capability Model for Adaptation Mechanism
12.3 Expression of Conformance-Based Dynamical Adaptation
12.3.1 νRule: Syntax and Semantics
12.3.2 Conformance Relationships by νRules
12.3.3 Function Identification According to νRules-Based Adaptation Logic
12.4 Summary
13 - Other Nonfunctionality Patterns
13.1 Introduction
13.1.1 Problem-Oriented Nonfunctional Requirement Patterns
13.1.2 Structure of a Problem-Oriented Nonfunctional Requirement Pattern
13.1.3 Process of Using a Problem-Oriented Nonfunctional Requirement Pattern
13.2 Problem-Oriented Nonfunctional Requirement Patterns and Their Concerns
13.2.1 Authorization Pattern
13.2.2 Buffer Pattern
13.2.3 Index Pattern
13.2.4 Log Pattern
13.2.5 Perception and Reaction Pattern
13.2.6 Encryption and Decryption Pattern
13.3 A Case Study
13.4 Discussion
Part Four References
Index
A
B
C
D
E
F
G
H
I
K
L
M
N
O
P
R
S
T
U
V
W