close
1.

電子ブック
ＥＢ
1. Cooperative Bug Isolation
Ben Liblit, David Hutchison, Takeo Kanade, Association for Computing Machinery.
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2007
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Perfect, or Close Enough / 1.1：
Automatic Failure Reporting / 1.2：
The Next Step Forward / 1.3：
Cooperative Bug Isolation / 1.4：
Instrumentation Framework / 2：
Basic Instrumentation Strategy / 2.1：
Sampling the Bernoulli Way / 2.1.1：
From Blocks to Functions / 2.1.2：
Interprocedural Issues / 2.1.3：
Instrumentation Schemes for Distributed Debugging / 2.2：
Issues in Remote Sampling / 2.2.1：
Counter-Based Instrumentation Schemes / 2.2.2：
Additional Instrumentation Schemes / 2.2.3：
Performance and Optimizations / 2.3：
Static Branch Prediction / 2.3.1：
Weightless Functions / 2.3.2：
Empty and Singleton Regions / 2.3.3：
Local Countdown Caching / 2.3.4：
Random Countdown Generation / 2.3.5：
Path Balancing / 2.3.6：
Statically Selective Sampling / 2.3.7：
Optimization Recap / 2.3.8：
Adaptive Sampling / 2.4：
Nonuniformity Via Multiple Countdowns / 2.4.1：
Nonuniformity Via Non-Unit Site Weights / 2.4.2：
Policy Notes / 2.4.3：
Realistic Sampling Rates / 2.5：
Practical Considerations / 3：
Native Compiler Integration / 3.1：
Static Site Information / 3.1.1：
Libraries and Plugins / 3.2：
Threads / 3.3：
Next-Sample Countdown / 3.3.1：
Predicate Counters / 3.3.2：
Compilation Unit Registry and Report File / 3.3.3：
Time Stamp Clock / 3.3.4：
Performance Evaluation / 3.3.5：
Privacy and Security / 3.4：
User Interaction / 3.5：
Status of the Public Deployment / 3.6：
Resource Requirements / 3.6.1：
Reporting Trends / 3.6.2：
Techniques for Statistical Debugging / 4：
Notation and Terminology / 4.1：
Predicate Elimination / 4.2：
Instrumentation Strategy / 4.2.1：
Elimination Strategies / 4.2.2：
Data Collection and Analysis / 4.2.3：
Refinement over time / 4.2.4：
Performance Impact / 4.2.5：
Limitations and Insights / 4.2.6：
Regularized Logistic Regression / 4.3：
Crash Prediction Using Logistic Regression / 4.3.1：
Moss: A Multiple-Bug Challenge / 4.3.2：
Nonuniform Sampling / 4.4.1：
Analysis Results / 4.4.2：
Iterative Bug Isolation and Elimination / 4.5：
Increase Scores / 4.5.1：
Statistical Interpretation / 4.5.2：
Balancing Specificity and Sensitivity / 4.5.3：
Redundancy Elimination / 4.5.4：
Case Studies / 4.6：
Moss / 4.6.1：
CCRYPT / 4.6.2：
BC / 4.6.3：
EXIF / 4.6.4：
Rhythmbox / 4.6.5：
Related Work / 5：
Static Analysis / 5.1：
Profiling and Tracing / 5.2：
Dynamic Analysis / 5.3：
Conclusion / 6：
References
Introduction / 1：
Perfect, or Close Enough / 1.1：
Automatic Failure Reporting / 1.2：
2.

電子ブック
ＥＢ
2. Cooperative Bug Isolation
Ben Liblit, David Hutchison, Takeo Kanade, Association for Computing Machinery.
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2007
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Perfect, or Close Enough / 1.1：
Automatic Failure Reporting / 1.2：
The Next Step Forward / 1.3：
Cooperative Bug Isolation / 1.4：
Instrumentation Framework / 2：
Basic Instrumentation Strategy / 2.1：
Sampling the Bernoulli Way / 2.1.1：
From Blocks to Functions / 2.1.2：
Interprocedural Issues / 2.1.3：
Instrumentation Schemes for Distributed Debugging / 2.2：
Issues in Remote Sampling / 2.2.1：
Counter-Based Instrumentation Schemes / 2.2.2：
Additional Instrumentation Schemes / 2.2.3：
Performance and Optimizations / 2.3：
Static Branch Prediction / 2.3.1：
Weightless Functions / 2.3.2：
Empty and Singleton Regions / 2.3.3：
Local Countdown Caching / 2.3.4：
Random Countdown Generation / 2.3.5：
Path Balancing / 2.3.6：
Statically Selective Sampling / 2.3.7：
Optimization Recap / 2.3.8：
Adaptive Sampling / 2.4：
Nonuniformity Via Multiple Countdowns / 2.4.1：
Nonuniformity Via Non-Unit Site Weights / 2.4.2：
Policy Notes / 2.4.3：
Realistic Sampling Rates / 2.5：
Practical Considerations / 3：
Native Compiler Integration / 3.1：
Static Site Information / 3.1.1：
Libraries and Plugins / 3.2：
Threads / 3.3：
Next-Sample Countdown / 3.3.1：
Predicate Counters / 3.3.2：
Compilation Unit Registry and Report File / 3.3.3：
Time Stamp Clock / 3.3.4：
Performance Evaluation / 3.3.5：
Privacy and Security / 3.4：
User Interaction / 3.5：
Status of the Public Deployment / 3.6：
Resource Requirements / 3.6.1：
Reporting Trends / 3.6.2：
Techniques for Statistical Debugging / 4：
Notation and Terminology / 4.1：
Predicate Elimination / 4.2：
Instrumentation Strategy / 4.2.1：
Elimination Strategies / 4.2.2：
Data Collection and Analysis / 4.2.3：
Refinement over time / 4.2.4：
Performance Impact / 4.2.5：
Limitations and Insights / 4.2.6：
Regularized Logistic Regression / 4.3：
Crash Prediction Using Logistic Regression / 4.3.1：
Moss: A Multiple-Bug Challenge / 4.3.2：
Nonuniform Sampling / 4.4.1：
Analysis Results / 4.4.2：
Iterative Bug Isolation and Elimination / 4.5：
Increase Scores / 4.5.1：
Statistical Interpretation / 4.5.2：
Balancing Specificity and Sensitivity / 4.5.3：
Redundancy Elimination / 4.5.4：
Case Studies / 4.6：
Moss / 4.6.1：
CCRYPT / 4.6.2：
BC / 4.6.3：
EXIF / 4.6.4：
Rhythmbox / 4.6.5：
Related Work / 5：
Static Analysis / 5.1：
Profiling and Tracing / 5.2：
Dynamic Analysis / 5.3：
Conclusion / 6：
References
Introduction / 1：
Perfect, or Close Enough / 1.1：
Automatic Failure Reporting / 1.2：
3.

電子ブック
ＥＢ
3. Constructing Correct Software
John Cooke
出版情報: Springer eBooks Computer Science , Springer London, 2005
所蔵情報: loading…
目次情報: 続きを見る
Abridged Preface to First Edition
Preface to Second Edition
Introduction / 0：
What Is this Book About? / 0.1：
Some Terminology / 0.2：
How Might Programs Fail? / 0.3：
A Way Forward / 0.4：
On Mathematics / 0.5：
Linking Paradigms / 0.6：
Problem Solving / 0.7：
The Book Plan / 0.8：
Preliminaries / Part A：
The Technical Background / 1：
Functions, Relations and Specifications / 1.0：
Summary of Features / 1.1.1：
Guidelines for Specifications / 1.1.2：
Equational Reasoning and Types / 1.2：
The Origin and Application of Rules / 1.3：
Data Types / 1.4：
A Glimpse at the Integers / 1.4.1：
Logical Types / 1.4.2：
The Boolean Type, IB / 1.4.2.1：
Implication and Deduction / 1.4.2.2：
Boolean Quantifiers / 1.4.2.3：
Extended (3-valued) Logic / 1.4.2.4：
Sets / 1.4.3：
Integers / 1.4.4：
Inequalities / 1.4.4.1：
Bags / 1.4.5：
Lists / 1.4.6：
Records and n-tuples / 1.4.7：
Union Types / 1.4.8：
Sub-types and Sub-ranges / 1.4.9：
Type Transfer Functions and Casts / 1.4.10：
Data Types and Transformations / 1.4.11：
On Quantification / 1.4.12：
Applying Unfold/Fold Transformations / 1.5：
On Programming / 2：
Overview / 2.0：
Procedural Programming / 2.1：
'Good' Programming / 2.2：
Structuring and (control) Flowcharts / 2.3：
PDL Overview / 2.4：
"Let" and "Where" / 2.4.1：
Scope and Parameters / 2.4.2：
Comments and Assertions / 2.5：
Verification of Procedural Programs / 2.6：
Sequencing / 2.6.1：
Alternation / 2.6.2：
Iteration / 2.6.3：
Program Derivation / 2.7：
Fundamentals / Part B：
Algorithm Extraction / 3：
On Converging Recursion / 3.0：
Design Tactics / 3.2：
Checking Perceived Answers / 3.2.1：
Problem Reduction / 3.2.2：
Problem Decomposition / 3.2.3：
Structural Splitting / 3.2.3.1：
Predicated Splitting / 3.2.3.2：
Mixed Strategies / 3.2.3.3：
Domain Partitioning / 3.2.3.4：
The Use of Analogy / 3.2.4：
'Eureka' Processes / 3.3：
Summary
Recursion Removal / 4：
Tail Recursion / 4.1：
Associative Recursion / 4.2：
Up and Down Iteration / 4.3：
Speeding up Iteratons / 4.4：
Recursive Procedures / 4.5：
Quantifications / 5：
Defining Composite Values / 5.0：
Derived Composite Values / 5.2：
1-place Functions / 5.2.1：
2-place Functions / 5.2.2：
Application to Program Development / 5.3：
An Extended Example: The Factorial Function / 5.3.1：
Some Rules for Quantifications / 5.4：
General Rules / 5.4.1：
Special Rules for Logical Quantifiers / 5.4.2：
Refinement and Re-use / 6：
Operational Refinement / 6.1：
On Correctness / 6.1.1：
Some Properties of Design Refinement / 6.1.2：
An Alternative View / 6.1.3：
Re-using Designs / 6.2：
Developments / Part C：
Sorting / 7：
Specification and Initial Discussion / 7.1：
Initial Designs / 7.2：
Predicated Splitting (Partitioning) / 7.2.1：
Complete Designs / 7.3：
Exchange Sorts / 7.3.1：
Merge Sorts / 7.3.2：
The Basic Merge Sort / 7.3.2.1：
Partition Sorts / 7.3.3：
Simple Partition Sort / 7.3.3.1：
A Quick Design / 7.4：
Data Refinement / 8：
On 'Internal' Data Types / 8.1：
Changing Data Types / 8.2：
Where to next? / 8.3：
Sorting Revisited / 9：
Variants of the Merge Sort / 9.1：
Failures and Fixes / 9.3：
Inadequate Pre-Conditions / 10.1：
Failures in Structural Splitting / 10.2：
Loss of Vital Information / 10.2.1：
Further Examples / 11：
The 2-D Convex Hull / 11.1：
Topological Sort / 11.2：
Experimentation / 11.2.1：
A Proper Formulation / 11.2.2：
Some 'Extremal' Problems / 11.3：
On Interactive Software / 12：
Specifications Involving Change / 12.1：
Specifications of Input/Output / 12.1.1：
Conventional Communications / 12.1.2：
The Enabling of Computations / 12.1.3：
Pertaining to (Software) Systems / 12.2：
System Requirements / 12.2.1：
Specifying Systems / 12.2.2：
Transformation Digest / Appendix：
Re-write Rule Conventions / A.0：
Data Manipulation Rules / A.1：
The Type IB / A.1.1：
Extended Logic and Conditional Expressions / A.1.2：
Common Conversion Functions / A.1.3：
Quantifier Rules / A.1.8：
Quantifier Properties / A.2：
'Not Occurs in' / A.3：
On PDL Structure / A.4：
PDL Transformation Rules / A.4.1：
Bibliography
Index
Abridged Preface to First Edition
Preface to Second Edition
Introduction / 0：
4.

電子ブック
ＥＢ
4. Constructing Correct Software
John Cooke
出版情報: SpringerLink Books - AutoHoldings , Springer London, 2005
所蔵情報: loading…
目次情報: 続きを見る
Abridged Preface to First Edition
Preface to Second Edition
Introduction / 0：
What Is this Book About? / 0.1：
Some Terminology / 0.2：
How Might Programs Fail? / 0.3：
A Way Forward / 0.4：
On Mathematics / 0.5：
Linking Paradigms / 0.6：
Problem Solving / 0.7：
The Book Plan / 0.8：
Preliminaries / Part A：
The Technical Background / 1：
Functions, Relations and Specifications / 1.0：
Summary of Features / 1.1.1：
Guidelines for Specifications / 1.1.2：
Equational Reasoning and Types / 1.2：
The Origin and Application of Rules / 1.3：
Data Types / 1.4：
A Glimpse at the Integers / 1.4.1：
Logical Types / 1.4.2：
The Boolean Type, IB / 1.4.2.1：
Implication and Deduction / 1.4.2.2：
Boolean Quantifiers / 1.4.2.3：
Extended (3-valued) Logic / 1.4.2.4：
Sets / 1.4.3：
Integers / 1.4.4：
Inequalities / 1.4.4.1：
Bags / 1.4.5：
Lists / 1.4.6：
Records and n-tuples / 1.4.7：
Union Types / 1.4.8：
Sub-types and Sub-ranges / 1.4.9：
Type Transfer Functions and Casts / 1.4.10：
Data Types and Transformations / 1.4.11：
On Quantification / 1.4.12：
Applying Unfold/Fold Transformations / 1.5：
On Programming / 2：
Overview / 2.0：
Procedural Programming / 2.1：
'Good' Programming / 2.2：
Structuring and (control) Flowcharts / 2.3：
PDL Overview / 2.4：
"Let" and "Where" / 2.4.1：
Scope and Parameters / 2.4.2：
Comments and Assertions / 2.5：
Verification of Procedural Programs / 2.6：
Sequencing / 2.6.1：
Alternation / 2.6.2：
Iteration / 2.6.3：
Program Derivation / 2.7：
Fundamentals / Part B：
Algorithm Extraction / 3：
On Converging Recursion / 3.0：
Design Tactics / 3.2：
Checking Perceived Answers / 3.2.1：
Problem Reduction / 3.2.2：
Problem Decomposition / 3.2.3：
Structural Splitting / 3.2.3.1：
Predicated Splitting / 3.2.3.2：
Mixed Strategies / 3.2.3.3：
Domain Partitioning / 3.2.3.4：
The Use of Analogy / 3.2.4：
'Eureka' Processes / 3.3：
Summary
Recursion Removal / 4：
Tail Recursion / 4.1：
Associative Recursion / 4.2：
Up and Down Iteration / 4.3：
Speeding up Iteratons / 4.4：
Recursive Procedures / 4.5：
Quantifications / 5：
Defining Composite Values / 5.0：
Derived Composite Values / 5.2：
1-place Functions / 5.2.1：
2-place Functions / 5.2.2：
Application to Program Development / 5.3：
An Extended Example: The Factorial Function / 5.3.1：
Some Rules for Quantifications / 5.4：
General Rules / 5.4.1：
Special Rules for Logical Quantifiers / 5.4.2：
Refinement and Re-use / 6：
Operational Refinement / 6.1：
On Correctness / 6.1.1：
Some Properties of Design Refinement / 6.1.2：
An Alternative View / 6.1.3：
Re-using Designs / 6.2：
Developments / Part C：
Sorting / 7：
Specification and Initial Discussion / 7.1：
Initial Designs / 7.2：
Predicated Splitting (Partitioning) / 7.2.1：
Complete Designs / 7.3：
Exchange Sorts / 7.3.1：
Merge Sorts / 7.3.2：
The Basic Merge Sort / 7.3.2.1：
Partition Sorts / 7.3.3：
Simple Partition Sort / 7.3.3.1：
A Quick Design / 7.4：
Data Refinement / 8：
On 'Internal' Data Types / 8.1：
Changing Data Types / 8.2：
Where to next? / 8.3：
Sorting Revisited / 9：
Variants of the Merge Sort / 9.1：
Failures and Fixes / 9.3：
Inadequate Pre-Conditions / 10.1：
Failures in Structural Splitting / 10.2：
Loss of Vital Information / 10.2.1：
Further Examples / 11：
The 2-D Convex Hull / 11.1：
Topological Sort / 11.2：
Experimentation / 11.2.1：
A Proper Formulation / 11.2.2：
Some 'Extremal' Problems / 11.3：
On Interactive Software / 12：
Specifications Involving Change / 12.1：
Specifications of Input/Output / 12.1.1：
Conventional Communications / 12.1.2：
The Enabling of Computations / 12.1.3：
Pertaining to (Software) Systems / 12.2：
System Requirements / 12.2.1：
Specifying Systems / 12.2.2：
Transformation Digest / Appendix：
Re-write Rule Conventions / A.0：
Data Manipulation Rules / A.1：
The Type IB / A.1.1：
Extended Logic and Conditional Expressions / A.1.2：
Common Conversion Functions / A.1.3：
Quantifier Rules / A.1.8：
Quantifier Properties / A.2：
'Not Occurs in' / A.3：
On PDL Structure / A.4：
PDL Transformation Rules / A.4.1：
Bibliography
Index
Abridged Preface to First Edition
Preface to Second Edition
Introduction / 0：
5.

電子ブック
ＥＢ
5. Analysis and Design of Advice
Ivan Jureta
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2011
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Coordination and Advice / 2：
When There Is None / 2.1：
From Division of Labor to Dependence on Advice / 2.2：
Autonomy and Coordination / 2.3：
Coordination Through Advice / 2.4：
Advice in Political Coordination / 2.5：
Dictatorship and Consent / 2.5.1：
Under Democracy / 2.5.2：
Advice and Meta-Advice in Politics / 2.5.3：
Advice in Economic Coordination / 2.6：
Central Planning / 2.6.1：
Market / 2.6.2：
Homo Follis / 2.7：
Conceptual Analysis of Advice / 3：
Rigorous Definition / 3.1：
Ostensive and Intensional Definitions / 3.1.1：
Primitive Terms / 3.1.2：
Criteria from Standard Theory / 3.1.3：
Signs to Objects and Back, via Concepts / 3.2：
Signs / 3.2.1：
Objects and Concepts / 3.2.2：
Relating Signs, Objects, and Concepts / 3.2.3：
Sings, Objects, and Concepts, in Advice / 3.2.4：
Ontology and Primitive Terms / 3.3：
Ontology in Philosophy / 3.3.1：
On the Engineering of Ontologies / 3.3.2：
Advice, Defined / 3.4：
Initial Ontological Commitments / 3.4.1：
Advice in Communication, Communication as Action / 3.4.2：
Essential Properties of and Identity Criteria for Advice / 3.4.3：
What Advice Is Not, but May Refer To / 3.4.4：
Relativist's Conceptual Analysis / 3.5：
Interpretation of Advice / 4：
Open Reference / 4.1：
Vague Advice / 4.2：
Referent Lost / 4.3：
Kinds of Advice / 5：
Classification from a Model of Choice / 5.1：
Perfect and Bounded Rational Choice / 5.2：
Ontology of Decision Analysis / 5.2.1：
Ontology of Choice in Organized Anarchies / 5.2.2：
Ontology of Intervowen Organisational Choice / 5.2.3：
Intolerance for Substitutes / 5.3：
Probability Intolerance / 5.3.1：
Utility Intolerance / 5.3.2：
Decision Information / 5.4：
Revealed Intentional States / 5.4.1：
Decision Information Ontology / 5.4.2：
Synthesis of the Decision Information Ontology / 5.4.3：
Taxonomy of Advice / 5.5：
Whose Explanations? / 5.5.1：
Specialization of the Concept of Advice / 5.5.2：
Reinterpreting Advice / 5.6：
Advisor's Problem and Its Solutions / 6：
Advice from Simple Explanations and Predictions / 6.1：
Models of Advice: An Overview / 6.2：
Introductory Example / 6.2.1：
Overview of the Framework for the Modeling of Advice / 6.2.2：
Modeling Language / 6.3：
AML2 / 6.3.1：
AML1 / 6.3.2：
AML / 6.3.3：
A-nets / 6.3.4：
Why the Interest in Structure? / 6.3.5：
Formulation of the Advisor's Problem / 6.4：
Solving the Advisor's Problem / 6.5：
Criteria for a Robust Solution / 6.6：
Criteria for a Clear Solution / 6.7：
Criteria from Empirical Evidence / 6.8：
Perspectives / 7：
References
Index
Introduction / 1：
Coordination and Advice / 2：
When There Is None / 2.1：
6.

電子ブック
ＥＢ
6. Analysis and Design of Advice
Ivan Jureta
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2011
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Coordination and Advice / 2：
When There Is None / 2.1：
From Division of Labor to Dependence on Advice / 2.2：
Autonomy and Coordination / 2.3：
Coordination Through Advice / 2.4：
Advice in Political Coordination / 2.5：
Dictatorship and Consent / 2.5.1：
Under Democracy / 2.5.2：
Advice and Meta-Advice in Politics / 2.5.3：
Advice in Economic Coordination / 2.6：
Central Planning / 2.6.1：
Market / 2.6.2：
Homo Follis / 2.7：
Conceptual Analysis of Advice / 3：
Rigorous Definition / 3.1：
Ostensive and Intensional Definitions / 3.1.1：
Primitive Terms / 3.1.2：
Criteria from Standard Theory / 3.1.3：
Signs to Objects and Back, via Concepts / 3.2：
Signs / 3.2.1：
Objects and Concepts / 3.2.2：
Relating Signs, Objects, and Concepts / 3.2.3：
Sings, Objects, and Concepts, in Advice / 3.2.4：
Ontology and Primitive Terms / 3.3：
Ontology in Philosophy / 3.3.1：
On the Engineering of Ontologies / 3.3.2：
Advice, Defined / 3.4：
Initial Ontological Commitments / 3.4.1：
Advice in Communication, Communication as Action / 3.4.2：
Essential Properties of and Identity Criteria for Advice / 3.4.3：
What Advice Is Not, but May Refer To / 3.4.4：
Relativist's Conceptual Analysis / 3.5：
Interpretation of Advice / 4：
Open Reference / 4.1：
Vague Advice / 4.2：
Referent Lost / 4.3：
Kinds of Advice / 5：
Classification from a Model of Choice / 5.1：
Perfect and Bounded Rational Choice / 5.2：
Ontology of Decision Analysis / 5.2.1：
Ontology of Choice in Organized Anarchies / 5.2.2：
Ontology of Intervowen Organisational Choice / 5.2.3：
Intolerance for Substitutes / 5.3：
Probability Intolerance / 5.3.1：
Utility Intolerance / 5.3.2：
Decision Information / 5.4：
Revealed Intentional States / 5.4.1：
Decision Information Ontology / 5.4.2：
Synthesis of the Decision Information Ontology / 5.4.3：
Taxonomy of Advice / 5.5：
Whose Explanations? / 5.5.1：
Specialization of the Concept of Advice / 5.5.2：
Reinterpreting Advice / 5.6：
Advisor's Problem and Its Solutions / 6：
Advice from Simple Explanations and Predictions / 6.1：
Models of Advice: An Overview / 6.2：
Introductory Example / 6.2.1：
Overview of the Framework for the Modeling of Advice / 6.2.2：
Modeling Language / 6.3：
AML2 / 6.3.1：
AML1 / 6.3.2：
AML / 6.3.3：
A-nets / 6.3.4：
Why the Interest in Structure? / 6.3.5：
Formulation of the Advisor's Problem / 6.4：
Solving the Advisor's Problem / 6.5：
Criteria for a Robust Solution / 6.6：
Criteria for a Clear Solution / 6.7：
Criteria from Empirical Evidence / 6.8：
Perspectives / 7：
References
Index
Introduction / 1：
Coordination and Advice / 2：
When There Is None / 2.1：
7.

電子ブック
ＥＢ
7. Software Architecture
Zheng Qin, Jiankuan Xing, Xiang Zheng
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Introduction to Software Architecture / 1：
A Brief History of Software Development / 1.1：
The Evolution of Programming Language-Abstract Level / 1.1.1：
The Evolution of Software Development-Concerns / 1.1.2：
The Origin and Growth of Software Architecture / 1.1.3：
Basic Terminologies / 1.2：
Understanding IEEE 1471-2000 / 1.2.2：
Views Used in Software Architecture / 1.2.3：
Why We Need Software Architecture / 1.2.4：
Where Is Software Architecture in Software Life Cycle / 1.2.5：
Summary / 1.3：
References
Architectural Styles and Patterns / 2：
Fundamentals of Architectural Styles and Patterns / 2.1：
Pipes Filters / 2.2：
Style Description / 2.2.1：
Study Case / 2.2.2：
Object-oriented / 2.3：
Event-driven / 2.3.1：
Hierarchical Layer / 2.4.1：
Data Sharing / 2.5.1：
Virtual Machine / 2.6.1：
Feedback Loop / 2.7.1：
Comparison among Styles / 2.8.1：
Integration of Heterogeneous Styles / 2.10：
Application and Analysis of Architectural Styles / 2.11：
Introduction to SMCSP / 3.1：
Program Background / 3.1.1：
Technical Routes / 3.1.2：
Function Design / 3.1.3：
System Realization / 3.2：
The Pattern Choice / 3.2.1：
Interaction Mechanism / 3.2.2：
Realization of Mobile Collaboration / 3.2.3：
Knowledge-based Design / 3.2.4：
Software Architecture Description / 3.3：
Formal Description of Software Architecture / 4.1：
Problems in Informal Description / 4.1.1：
Why Are Formal Methods Necessary / 4.1.2：
Architectural Description Language / 4.2：
Introduction to ADL / 4.2.1：
Comparing among Typical ADLs / 4.2.2：
Describing Architectural Behaviors / 4.2.3：
Study Case: WRIGHT System / 4.3：
Description of Component and Connector / 4.3.1：
Description of Configuration / 4.3.2：
Description of Style / 4.3.3：
CSP-Semantic Basis of Formal Behavior Description / 4.3.4：
FEAL: An Infrastructure to Construct ADLs / 4.4：
Design Purpose / 4.4.1：
FEC / 4.4.2：
FEAL Structure / 4.4.3：
FEAL Mapper / 4.4.4：
Examples of FEAL Application / 4.4.5：
Design Strategies in Architecture Level / 4.5：
From Reuse to Architecture Design / 5.1：
Architectural Design Space and Rules / 5.2：
SADPBA / 5.3：
Overview / 5.3.1：
Split Design Process with Design Space / 5.3.2：
Trace Mechanism in SADPBA / 5.3.3：
Life Cycle Model of Software Architecture / 5.3.4：
SADPBA in Practice / 5.3.5：
Study Case: MEECS / 5.4：
Introduction to MEECS / 5.4.1：
Applying SADPBA in MEECS / 5.4.2：
Software Architecture IDE / 5.5：
What Can Software Architecture IDE Do / 6.1：
A Comparison with Formalized Description Approach / 6.1.1：
Important Roles of Architecture IDE / 6.1.2：
Prototype / 6.2：
User Interface Layer / 6.2.1：
Model Layer / 6.2.2：
Foundational Layer / 6.2.3：
IDE Design Tactics / 6.2.4：
ArchStudio 4 System / 6.3：
Introduction / 6.3.1：
Installing ArchStudio 4 / 6.3.2：
ArchStudio 4 Overview / 6.3.3：
Using ArchStudio 4 / 6.3.4：
Evaluating Software Architecture / 6.4：
What Is Software Architecture Evaluation / 7.1：
Quality Attribute / 7.1.1：
Why Is Evaluation Necessary / 7.1.2：
Scenario-based Evaluation Methods / 7.1.3：
SAAM / 7.2：
General Steps of SAAM / 7.2.1：
Scenario Development / 7.2.2：
Architecture Description / 7.2.3：
Scenario Classification and Prioritization / 7.2.4：
Individual Evaluation of Indirect Scenarios / 7.2.5：
Assessment of Scenario Interaction / 7.2.6：
Creation of Overall Evaluation / 7.2.7：
ATAM / 7.3：
Initial ATAM / 7.3.1：
ATAM Improvement / 7.3.2：
General Process of ATAM / 7.3.3：
Presentation / 7.3.4：
Investigation and Analysis / 7.3.5：
Testing / 7.3.6：
Present the Results / 7.3.7：
Comparison among Evaluation Methods / 7.4：
Comparison Framework / 7.4.1：
Overview and Comparison of Evaluation Methods / 7.4.2：
Flexible Software Architecture / 7.5：
What Is Flexibility for / 8.1：
Dynamic Software Architecture / 8.2：
[pi]-ADL: A Behavior Perspective / 8.2.1：
MARMOL: A Reflection Perspective / 8.2.2：
LIME: A Coordination Perspective / 8.2.3：
Flexibility: Beyond the Dynamism / 8.3：
Concept of Flexible Software Architecture / 8.3.1：
Trade-off of Flexibility / 8.3.2：
Study Cases / 8.4：
Rainbow / 8.4.1：
MADAM / 8.4.2：
A Vision on Software Architecture / 8.5：
Software Architecture in Modern Software Industry / 9.1：
Categorizing Software / 9.1.1：
Software Product Line / 9.1.2：
Software Architecture Used in Other Fields / 9.2：
The Outline of Software Architecture Application Practice / 9.2.1：
The Development Trends of Domain-Specific Software / 9.2.2：
Software Architecture's Future Research / 9.3：
Index / 9.4：
Introduction to Software Architecture / 1：
A Brief History of Software Development / 1.1：
The Evolution of Programming Language-Abstract Level / 1.1.1：
8.

電子ブック
ＥＢ
8. Software Architecture
Zheng Qin, Jiankuan Xing, Xiang Zheng, Jian-Kuan Xing
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Introduction to Software Architecture / 1：
A Brief History of Software Development / 1.1：
The Evolution of Programming Language-Abstract Level / 1.1.1：
The Evolution of Software Development-Concerns / 1.1.2：
The Origin and Growth of Software Architecture / 1.1.3：
Basic Terminologies / 1.2：
Understanding IEEE 1471-2000 / 1.2.2：
Views Used in Software Architecture / 1.2.3：
Why We Need Software Architecture / 1.2.4：
Where Is Software Architecture in Software Life Cycle / 1.2.5：
Summary / 1.3：
References
Architectural Styles and Patterns / 2：
Fundamentals of Architectural Styles and Patterns / 2.1：
Pipes Filters / 2.2：
Style Description / 2.2.1：
Study Case / 2.2.2：
Object-oriented / 2.3：
Event-driven / 2.3.1：
Hierarchical Layer / 2.4.1：
Data Sharing / 2.5.1：
Virtual Machine / 2.6.1：
Feedback Loop / 2.7.1：
Comparison among Styles / 2.8.1：
Integration of Heterogeneous Styles / 2.10：
Application and Analysis of Architectural Styles / 2.11：
Introduction to SMCSP / 3.1：
Program Background / 3.1.1：
Technical Routes / 3.1.2：
Function Design / 3.1.3：
System Realization / 3.2：
The Pattern Choice / 3.2.1：
Interaction Mechanism / 3.2.2：
Realization of Mobile Collaboration / 3.2.3：
Knowledge-based Design / 3.2.4：
Software Architecture Description / 3.3：
Formal Description of Software Architecture / 4.1：
Problems in Informal Description / 4.1.1：
Why Are Formal Methods Necessary / 4.1.2：
Architectural Description Language / 4.2：
Introduction to ADL / 4.2.1：
Comparing among Typical ADLs / 4.2.2：
Describing Architectural Behaviors / 4.2.3：
Study Case: WRIGHT System / 4.3：
Description of Component and Connector / 4.3.1：
Description of Configuration / 4.3.2：
Description of Style / 4.3.3：
CSP-Semantic Basis of Formal Behavior Description / 4.3.4：
FEAL: An Infrastructure to Construct ADLs / 4.4：
Design Purpose / 4.4.1：
FEC / 4.4.2：
FEAL Structure / 4.4.3：
FEAL Mapper / 4.4.4：
Examples of FEAL Application / 4.4.5：
Design Strategies in Architecture Level / 4.5：
From Reuse to Architecture Design / 5.1：
Architectural Design Space and Rules / 5.2：
SADPBA / 5.3：
Overview / 5.3.1：
Split Design Process with Design Space / 5.3.2：
Trace Mechanism in SADPBA / 5.3.3：
Life Cycle Model of Software Architecture / 5.3.4：
SADPBA in Practice / 5.3.5：
Study Case: MEECS / 5.4：
Introduction to MEECS / 5.4.1：
Applying SADPBA in MEECS / 5.4.2：
Software Architecture IDE / 5.5：
What Can Software Architecture IDE Do / 6.1：
A Comparison with Formalized Description Approach / 6.1.1：
Important Roles of Architecture IDE / 6.1.2：
Prototype / 6.2：
User Interface Layer / 6.2.1：
Model Layer / 6.2.2：
Foundational Layer / 6.2.3：
IDE Design Tactics / 6.2.4：
ArchStudio 4 System / 6.3：
Introduction / 6.3.1：
Installing ArchStudio 4 / 6.3.2：
ArchStudio 4 Overview / 6.3.3：
Using ArchStudio 4 / 6.3.4：
Evaluating Software Architecture / 6.4：
What Is Software Architecture Evaluation / 7.1：
Quality Attribute / 7.1.1：
Why Is Evaluation Necessary / 7.1.2：
Scenario-based Evaluation Methods / 7.1.3：
SAAM / 7.2：
General Steps of SAAM / 7.2.1：
Scenario Development / 7.2.2：
Architecture Description / 7.2.3：
Scenario Classification and Prioritization / 7.2.4：
Individual Evaluation of Indirect Scenarios / 7.2.5：
Assessment of Scenario Interaction / 7.2.6：
Creation of Overall Evaluation / 7.2.7：
ATAM / 7.3：
Initial ATAM / 7.3.1：
ATAM Improvement / 7.3.2：
General Process of ATAM / 7.3.3：
Presentation / 7.3.4：
Investigation and Analysis / 7.3.5：
Testing / 7.3.6：
Present the Results / 7.3.7：
Comparison among Evaluation Methods / 7.4：
Comparison Framework / 7.4.1：
Overview and Comparison of Evaluation Methods / 7.4.2：
Flexible Software Architecture / 7.5：
What Is Flexibility for / 8.1：
Dynamic Software Architecture / 8.2：
[pi]-ADL: A Behavior Perspective / 8.2.1：
MARMOL: A Reflection Perspective / 8.2.2：
LIME: A Coordination Perspective / 8.2.3：
Flexibility: Beyond the Dynamism / 8.3：
Concept of Flexible Software Architecture / 8.3.1：
Trade-off of Flexibility / 8.3.2：
Study Cases / 8.4：
Rainbow / 8.4.1：
MADAM / 8.4.2：
A Vision on Software Architecture / 8.5：
Software Architecture in Modern Software Industry / 9.1：
Categorizing Software / 9.1.1：
Software Product Line / 9.1.2：
Software Architecture Used in Other Fields / 9.2：
The Outline of Software Architecture Application Practice / 9.2.1：
The Development Trends of Domain-Specific Software / 9.2.2：
Software Architecture's Future Research / 9.3：
Index / 9.4：
Introduction to Software Architecture / 1：
A Brief History of Software Development / 1.1：
The Evolution of Programming Language-Abstract Level / 1.1.1：
9.

電子ブック
ＥＢ
9. Concurrency Theory
Howard Bowman, Rodolfo Gomez
出版情報: Springer eBooks Computer Science , Springer London, 2006
所蔵情報: loading…
目次情報: 続きを見る
Introduction / Part I：
Background on Concurrency Theory / 1：
Concurrency Is Everywhere / 1.1：
Characteristics of Concurrent Systems / 1.2：
Classes of Concurrent Systems / 1.3：
Basic Event Ordering / 1.3.1：
Timing Axis / 1.3.2：
Probabilistic Choice Axis / 1.3.3：
Mobility Axis / 1.3.4：
Mathematical Theories / 1.4：
Overview of Book / 1.5：
Concurrency Theory - Untimed Models / Part II：
Process Calculi: LOTOS / 2：
Example Specifications / 2.1：
A Communication Protocol / 2.2.1：
The Dining Philosophers / 2.2.2：
Primitive Basic LOTOS / 2.3：
Abstract Actions / 2.3.1：
Action Prefix / 2.3.2：
Choice / 2.3.3：
Nondeterminism / 2.3.4：
Process Definition / 2.3.5：
Concurrency / 2.3.6：
Sequential Composition and Exit / 2.3.7：
Syntax of pbLOTOS / 2.3.8：
Example / 2.4：
Basic Interleaved Semantic Models / 3：
A General Perspective on Semantics / 3.1：
Why Semantics? / 3.1.1：
Formal Definition / 3.1.2：
Modelling Recursion / 3.1.3：
What Makes a Good Semantics? / 3.1.4：
Trace Semantics / 3.2：
The Basic Approach / 3.2.1：
Formal Semantics / 3.2.2：
Development Relations / 3.2.3：
Discussion / 3.2.4：
Labelled Transition Systems / 3.3：
Verification Tools / 3.3.1：
Overview of CADP / 3.4.1：
Bisimulation Checking in CADP / 3.4.2：
True Concurrency Models: Event Structures / 4：
The Basic Approach - Event Structures / 4.1：
Event Structures and pbLOTOS / 4.3：
An Event Structures Semantics for pbLOTOS / 4.4：
Relating Event Structures to Labelled Transition Systems / 4.5：
Alternative Event Structure Models / 4.6：
Summary and Discussion / 4.8：
Testing Theory and the Linear Time - Branching Time Spectrum / 5：
Trace-refusals Semantics / 5.1：
Deriving Trace-refusal Pairs / 5.1.1：
Internal Behaviour / 5.1.4：
Development Relations: Equivalences / 5.1.5：
Nonequivalence Development Relations / 5.1.6：
Explorations of Congruence / 5.1.7：
Testing Justification for Trace-refusals Semantics / 5.1.8：
Testing Theory in General and the Linear Time - Branching Time Spectrum / 5.3：
Sequence-based Testing / 5.3.1：
Tree-based Testing / 5.3.2：
Applications of Trace-refusals Relations in Distributed Systems / 5.4：
Relating OO Concepts to LOTOS / 5.4.1：
Behavioural Subtyping / 5.4.2：
Viewpoints and Consistency / 5.4.3：
Concurrency Theory - Further Untimed Notations / Part III：
Beyond pbLOTOS / 6：
Basic LOTOS / 6.1：
Disabling / 6.1.1：
Generalised Choice / 6.1.2：
Generalised Parallelism / 6.1.3：
Verbose Specification Syntax / 6.1.4：
Verbose Process Syntax / 6.1.5：
Syntax of bLOTOS / 6.1.6：
Full LOTOS / 6.2：
Guarded Choice / 6.2.1：
Specification Notation / 6.2.2：
Process Definition and Invocation / 6.2.3：
Value Passing Actions / 6.2.4：
Local Definitions / 6.2.5：
Selection Predicates / 6.2.6：
Parameterised Enabling / 6.2.7：
Syntax of fLOTOS / 6.2.9：
Comments / 6.2.10：
Examples / 6.3：
Communication Protocol / 6.3.1：
Dining Philosophers / 6.3.2：
Extended LOTOS / 6.4：
Comparison of LOTOS with CCS and CSP / 7：
CCS and LOTOS / 7.1：
Parallel Composition and Complementation of Actions / 7.1.1：
Restriction and Hiding / 7.1.2：
Minor Differences / 7.1.3：
CSP and LOTOS / 7.2：
Alphabets / 7.2.1：
Internal Actions / 7.2.2：
Parallelism / 7.2.3：
Hiding / 7.2.5：
Comparison of LOTOS Trace-refusals with CSP Failures-divergences / 7.2.6：
Communicating Automata / 8：
Networks of Communicating Automata / 8.1：
Component Automata / 8.2.1：
Parallel Composition / 8.2.2：
Semantics and Development Relations / 8.2.3：
Verification of Networks of Communicating Automata / 8.2.5：
Relationship to Process Calculi / 8.2.6：
Infinite State Communicating Automata / 8.3：
Networks of Infinite State Communicating Automata / 8.3.1：
Semantics of ISCAs as Labelled Transition Systems / 8.3.2：
Concurrency Theory - Timed Models / Part IV：
Timed Process Calculi, a LOTOS Perspective / 9：
Timed LOTOS - The Issues / 9.1：
Timed Action Enabling / 9.2.1：
Urgency / 9.2.2：
Persistency / 9.2.3：
Synchronisation / 9.2.4：
Timing Domains / 9.2.6：
Time Measurement / 9.2.7：
Timing of Nonadjacent Actions / 9.2.8：
Timed Interaction Policies / 9.2.9：
Forms of Internal Urgency / 9.2.10：
Timed LOTOS Notation / 9.2.11：
The Language / 9.3.1：
Timing Anomalies in tLOTOS / 9.3.2：
E-LOTOS, the Timing Extensions / 9.5：
Semantic Models for tLOTOS / 10：
Branching Time Semantics / 10.1：
Timed Transition Systems / 10.1.1：
Operational Semantics / 10.1.2：
Branching Time Development Relations / 10.1.3：
True Concurrency Semantics / 10.2：
Timed Bundle Event Structures / 10.2.1：
Causal Semantics for tLOTOS / 10.2.3：
Anomalous Behaviour / 10.2.4：
Timed Communicating Automata / 10.2.5：
Timed Automata - Formal Definitions / 11.1：
Syntax / 11.2.1：
Semantics / 11.2.2：
Real-time Model-checking / 11.3：
Forward Reachability / 11.3.1：
Example: Reachability Analysis on the Multimedia Stream / 11.3.2：
Issues in Real-time Model-checking / 11.3.3：
Timelocks in Timed Automata / 12：
A Classification of Deadlocks in Timed Automata / 12.1：
Discussion: Justifying the Classification of Deadlocks / 12.2.1：
Discussion: Timelocks in Process Calculi / 12.2.2：
Time-actionlocks / 12.3：
Timed Automata with Deadlines / 12.3.1：
Example: A TAD Specification for the Multimedia Stream / 12.3.2：
Zeno-timelocks / 12.4：
Example: Zeno-timelocks in the Multimedia Stream / 12.4.1：
Nonzenoness: Syntactic Conditions / 12.4.2：
Nonzenoness: A Sufficient-and-Necessary Condition / 12.4.3：
Timelock Detection in Real-time Model-checkers / 12.5：
Uppaal / 12.5.1：
Kronos / 12.5.2：
Discrete Timed Automata / 13：
Infinite vs. Finite States / 13.1：
Preliminaries / 13.2：
Fair Transition Systems and Invariance Proofs / 13.2.1：
The Weak Monadic Second-order Theory of 1 Successor (WS1S) and MONA / 13.2.2：
Discrete Timed Automata - Formal definitions / 13.3：
Example: A DTA Specification for the Multimedia Stream / 13.3.1：
Verifying Safety Properties over DTAs / 13.3.3：
Discussion: Comparing DTAs and TIOAs with Urgency / 13.5：
References
Appendix
Enabling as a Derived Operator / 14.1：
Strong Bisimulation Is a Congruence / 14.2：
Weak Bisimulation Congruence / 14.3：
Timed Enabling as a Derived Operator / 14.4：
Hiding is Not Substitutive for Timed Bisimulations / 14.5：
Substitutivity of Timed Strong Bisimulation / 14.6：
Substitutivity of Timed Rooted Weak Bisimulation / 14.7：
Index
Introduction / Part I：
Background on Concurrency Theory / 1：
Concurrency Is Everywhere / 1.1：
10.

電子ブック
ＥＢ
10. Concurrency Theory
Howard Bowman, Rodolfo Gomez
出版情報: SpringerLink Books - AutoHoldings , Springer London, 2006
所蔵情報: loading…
目次情報: 続きを見る
Introduction / Part I：
Background on Concurrency Theory / 1：
Concurrency Is Everywhere / 1.1：
Characteristics of Concurrent Systems / 1.2：
Classes of Concurrent Systems / 1.3：
Basic Event Ordering / 1.3.1：
Timing Axis / 1.3.2：
Probabilistic Choice Axis / 1.3.3：
Mobility Axis / 1.3.4：
Mathematical Theories / 1.4：
Overview of Book / 1.5：
Concurrency Theory - Untimed Models / Part II：
Process Calculi: LOTOS / 2：
Example Specifications / 2.1：
A Communication Protocol / 2.2.1：
The Dining Philosophers / 2.2.2：
Primitive Basic LOTOS / 2.3：
Abstract Actions / 2.3.1：
Action Prefix / 2.3.2：
Choice / 2.3.3：
Nondeterminism / 2.3.4：
Process Definition / 2.3.5：
Concurrency / 2.3.6：
Sequential Composition and Exit / 2.3.7：
Syntax of pbLOTOS / 2.3.8：
Example / 2.4：
Basic Interleaved Semantic Models / 3：
A General Perspective on Semantics / 3.1：
Why Semantics? / 3.1.1：
Formal Definition / 3.1.2：
Modelling Recursion / 3.1.3：
What Makes a Good Semantics? / 3.1.4：
Trace Semantics / 3.2：
The Basic Approach / 3.2.1：
Formal Semantics / 3.2.2：
Development Relations / 3.2.3：
Discussion / 3.2.4：
Labelled Transition Systems / 3.3：
Verification Tools / 3.3.1：
Overview of CADP / 3.4.1：
Bisimulation Checking in CADP / 3.4.2：
True Concurrency Models: Event Structures / 4：
The Basic Approach - Event Structures / 4.1：
Event Structures and pbLOTOS / 4.3：
An Event Structures Semantics for pbLOTOS / 4.4：
Relating Event Structures to Labelled Transition Systems / 4.5：
Alternative Event Structure Models / 4.6：
Summary and Discussion / 4.8：
Testing Theory and the Linear Time - Branching Time Spectrum / 5：
Trace-refusals Semantics / 5.1：
Deriving Trace-refusal Pairs / 5.1.1：
Internal Behaviour / 5.1.4：
Development Relations: Equivalences / 5.1.5：
Nonequivalence Development Relations / 5.1.6：
Explorations of Congruence / 5.1.7：
Testing Justification for Trace-refusals Semantics / 5.1.8：
Testing Theory in General and the Linear Time - Branching Time Spectrum / 5.3：
Sequence-based Testing / 5.3.1：
Tree-based Testing / 5.3.2：
Applications of Trace-refusals Relations in Distributed Systems / 5.4：
Relating OO Concepts to LOTOS / 5.4.1：
Behavioural Subtyping / 5.4.2：
Viewpoints and Consistency / 5.4.3：
Concurrency Theory - Further Untimed Notations / Part III：
Beyond pbLOTOS / 6：
Basic LOTOS / 6.1：
Disabling / 6.1.1：
Generalised Choice / 6.1.2：
Generalised Parallelism / 6.1.3：
Verbose Specification Syntax / 6.1.4：
Verbose Process Syntax / 6.1.5：
Syntax of bLOTOS / 6.1.6：
Full LOTOS / 6.2：
Guarded Choice / 6.2.1：
Specification Notation / 6.2.2：
Process Definition and Invocation / 6.2.3：
Value Passing Actions / 6.2.4：
Local Definitions / 6.2.5：
Selection Predicates / 6.2.6：
Parameterised Enabling / 6.2.7：
Syntax of fLOTOS / 6.2.9：
Comments / 6.2.10：
Examples / 6.3：
Communication Protocol / 6.3.1：
Dining Philosophers / 6.3.2：
Extended LOTOS / 6.4：
Comparison of LOTOS with CCS and CSP / 7：
CCS and LOTOS / 7.1：
Parallel Composition and Complementation of Actions / 7.1.1：
Restriction and Hiding / 7.1.2：
Minor Differences / 7.1.3：
CSP and LOTOS / 7.2：
Alphabets / 7.2.1：
Internal Actions / 7.2.2：
Parallelism / 7.2.3：
Hiding / 7.2.5：
Comparison of LOTOS Trace-refusals with CSP Failures-divergences / 7.2.6：
Communicating Automata / 8：
Networks of Communicating Automata / 8.1：
Component Automata / 8.2.1：
Parallel Composition / 8.2.2：
Semantics and Development Relations / 8.2.3：
Verification of Networks of Communicating Automata / 8.2.5：
Relationship to Process Calculi / 8.2.6：
Infinite State Communicating Automata / 8.3：
Networks of Infinite State Communicating Automata / 8.3.1：
Semantics of ISCAs as Labelled Transition Systems / 8.3.2：
Concurrency Theory - Timed Models / Part IV：
Timed Process Calculi, a LOTOS Perspective / 9：
Timed LOTOS - The Issues / 9.1：
Timed Action Enabling / 9.2.1：
Urgency / 9.2.2：
Persistency / 9.2.3：
Synchronisation / 9.2.4：
Timing Domains / 9.2.6：
Time Measurement / 9.2.7：
Timing of Nonadjacent Actions / 9.2.8：
Timed Interaction Policies / 9.2.9：
Forms of Internal Urgency / 9.2.10：
Timed LOTOS Notation / 9.2.11：
The Language / 9.3.1：
Timing Anomalies in tLOTOS / 9.3.2：
E-LOTOS, the Timing Extensions / 9.5：
Semantic Models for tLOTOS / 10：
Branching Time Semantics / 10.1：
Timed Transition Systems / 10.1.1：
Operational Semantics / 10.1.2：
Branching Time Development Relations / 10.1.3：
True Concurrency Semantics / 10.2：
Timed Bundle Event Structures / 10.2.1：
Causal Semantics for tLOTOS / 10.2.3：
Anomalous Behaviour / 10.2.4：
Timed Communicating Automata / 10.2.5：
Timed Automata - Formal Definitions / 11.1：
Syntax / 11.2.1：
Semantics / 11.2.2：
Real-time Model-checking / 11.3：
Forward Reachability / 11.3.1：
Example: Reachability Analysis on the Multimedia Stream / 11.3.2：
Issues in Real-time Model-checking / 11.3.3：
Timelocks in Timed Automata / 12：
A Classification of Deadlocks in Timed Automata / 12.1：
Discussion: Justifying the Classification of Deadlocks / 12.2.1：
Discussion: Timelocks in Process Calculi / 12.2.2：
Time-actionlocks / 12.3：
Timed Automata with Deadlines / 12.3.1：
Example: A TAD Specification for the Multimedia Stream / 12.3.2：
Zeno-timelocks / 12.4：
Example: Zeno-timelocks in the Multimedia Stream / 12.4.1：
Nonzenoness: Syntactic Conditions / 12.4.2：
Nonzenoness: A Sufficient-and-Necessary Condition / 12.4.3：
Timelock Detection in Real-time Model-checkers / 12.5：
Uppaal / 12.5.1：
Kronos / 12.5.2：
Discrete Timed Automata / 13：
Infinite vs. Finite States / 13.1：
Preliminaries / 13.2：
Fair Transition Systems and Invariance Proofs / 13.2.1：
The Weak Monadic Second-order Theory of 1 Successor (WS1S) and MONA / 13.2.2：
Discrete Timed Automata - Formal definitions / 13.3：
Example: A DTA Specification for the Multimedia Stream / 13.3.1：
Verifying Safety Properties over DTAs / 13.3.3：
Discussion: Comparing DTAs and TIOAs with Urgency / 13.5：
References
Appendix
Enabling as a Derived Operator / 14.1：
Strong Bisimulation Is a Congruence / 14.2：
Weak Bisimulation Congruence / 14.3：
Timed Enabling as a Derived Operator / 14.4：
Hiding is Not Substitutive for Timed Bisimulations / 14.5：
Substitutivity of Timed Strong Bisimulation / 14.6：
Substitutivity of Timed Rooted Weak Bisimulation / 14.7：
Index
Introduction / Part I：
Background on Concurrency Theory / 1：
Concurrency Is Everywhere / 1.1：
11.

電子ブック
ＥＢ
11. Adoption-centric Usability Engineering
Ahmed Seffah, Eduard Metzker
出版情報: SpringerLink Books - AutoHoldings , Springer London, 2009
所蔵情報: loading…
目次情報: 続きを見る
Usability Engineering: Definitions, Methods, and Challenges for Integration / Part I：
On Usability and Usability Engineering / 1：
Interactive Systems and User Interface / 1.1：
Usability: A Quality Attribute of the Whole System, Not Just the User Interface / 1.2：
Usability in Traditional Software Quality Models / 1.3：
Other Specific Measurement Models / 1.4：
Cost-benefits of Usability Engineering / 1.5：
Involving the End-User is Central, but Not Enough / 1.6：
Usability Engineering Methods Plethora / 2：
Possible Theories for Usability Engineering / 2.1：
Pure Usability Engineering Methods / 2.2：
A Taxonomy of the Most Popular Usability Engineering (UE) Methods / 2.2.1：
Expert-Based Evaluation / 2.2.2：
Prototyping Techniques / 2.2.3：
Usability Testing / 2.2.4：
Subjective Assessment / 2.2.5：
UE Methods and the Development Lifecycle / 2.3：
Other Usability Engineering-Sensitive Methodologies / 2.4：
Scenario-Based Design / 2.4.1：
Contextual Design / 2.4.2：
Star Lifecycle / 2.4.3：
Usability Engineering Lifecycle / 2.4.4：
Usage-Centered Design / 2.4.5：
Extensions to Traditional Software Engineering Methods / 2.5：
Adding Usage Scenarios to Object-Oriented Analysis and Design / 2.5.1：
Task Analysis Versus Object-Oriented and Use Cases Models / 2.5.2：
UML Notation for User Interface Modeling / 2.5.3：
Enhancing Use Cases for User Interface Prototyping / 2.5.4：
Pitfalls and Obstacles in the Integration and Adoption Path / 3：
The Fallacious Dichotomy Between User Interface and System Functionality / 3.1：
The Cultural Gap Between Psychologists and Engineers / 3.2：
User-Centeredness is an Organizational Learning Process / 3.3：
The Usability of Usability Engineering Methods / 3.4：
The Lack of Process Support Tools / 3.5：
Collecting Best Practices in UE is Missing / 3.6：
Educational Gap Between Software Professionals and Usability Professionals / 3.7：
ACUE Fundamentals, Architecture and Components / Part II：
Usability Engineering Integration as an Adoption Problem / 4：
Key Milestones in the Adoption Process / 4.1：
On the Development of Adoption-Centric Usability Methods / 4.2：
Difficulties of Building an Empirical Driven Adoption Method / 4.3：
Adoption-Centric Usability Engineering - Key Principles / 4.4：
ACUE Architecture and Components / 5：
UE Method Kits / 5.1：
Project Context Profile / 5.2：
USEPacks: Knowledge About UE Methods / 5.3：
USEPack Textual Description / 5.3.1：
USEPack Reusable Artifacts / 5.3.2：
USEPack Context Profile / 5.3.3：
Acceptance Model / 5.3.4：
Context Model vs. Context Profile / 5.3.5：
Configuration of a Method Kit to a Specific Project / 5.4：
USEPack Assessment / 5.5：
ACUE Formal Description / 6：
Foundations for ACUE Formalization / 6.1：
Fuzzy Sets / 6.1.1：
Multi-Criteria Decision-Making / 6.1.2：
Modeling Context Profiles as Fuzzy Sets / 6.1.3：
Context-Based USEPack Selection as a MCDM Problem / 6.1.4：
USEPack Assessment Using the Acceptance Model / 6.2：
USEPack Context Profiles Adaptation / 6.3：
Alternative Approaches for Formalizing ACUE / 6.4：
Operationalization and Validation / Part III：
How Effective Is ACUE? An Empirical Case Study / 7：
Overview of the Study / 7.1：
Goals of the Study / 7.1.1：
Materials: The UE Method Kit / 7.1.2：
Subjects / 7.1.3：
Method / 7.1.4：
Results / 7.2：
Process Sketches / 7.3：
Matching of the Method Kit with Practiced Development Processes / 7.4：
Discussion / 7.5：
Putting it into Practice: The ProUse Tool / 8：
Constraints for Operationalizing the ACUE / 8.1：
Structure and Main Feature / 8.2：
ProUSE Portal / 8.3：
Method Kit Configuration / 8.4：
Method Guidance / 8.5：
Method Capturing and Maintenance / 8.6：
How Well do ACUE and ProUse Work? Overall Evaluation / 9：
Evaluation of ProUSE / 9.1：
Context of the Evaluation / 9.1.1：
Data Collection Techniques / 9.1.2：
Tasks / 9.1.5：
Procedure / 9.1.6：
Results of the Studies and Recommendations / 9.2：
Characteristics of the Subject Groups / 9.2.1：
Understandability of the Proposed ACUE / 9.2.2：
ACUE Perceived Usefulness / 9.2.3：
ACUE Perceived Ease-of-Use / 9.2.4：
Interviewee Statements on the Practiced Software Development Process / 9.3：
Overview / 9.3.1：
Knowledge About the Software Development Process / 9.3.2：
Process Models Used by Subjects / 9.3.3：
The Usability Engineering Process / 9.3.4：
Subjects' Roles as Project Team Members / 9.3.5：
ACUE in Software Engineering: Current Stage and Perspectives / Part IV：
ACUE and the Existing Software Engineering Methodologies / 10：
USEPacks Versus Other Approaches for Reusing UE Knowledge / 10.1：
ProUSE Versus Other Tools for Reusing UE Knowledge / 10.2：
Overall Comparisons Between ACUE and Software Engineering Approaches / 10.3：
ACUE in Relation to Process Improvement Approaches / 10.4：
ACUE as an Approach to Improve Research Utilization / 10.5：
ACUE and Agile Process Concepts / 10.6：
Conclusion and Perspectives / 11：
Conclusion and Limitations / 11.1：
Some Avenues to Explore / 11.2：
A Forum for Cross-Domain Discussion is Needed / 11.3：
References
Index
Usability Engineering: Definitions, Methods, and Challenges for Integration / Part I：
On Usability and Usability Engineering / 1：
Interactive Systems and User Interface / 1.1：
12.

電子ブック
ＥＢ
12. Security Engineering for Service-Oriented Architectures
Michael Hafner, Ruth Breu
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2009
所蔵情報: loading…
目次情報: 続きを見る
The Basics of SOA Security Engineering / Part I：
Introduction / 1：
Service Oriented Architecture / 1.1：
Interoperability and Securitiy Issues in SOA / 1.1.1：
Model Driven Security Engineering / 1.1.2：
Problem Description / 1.2：
Contribution / 1.3：
ProSecO / 1.3.1：
Sectet / 1.3.2：
Related Work / 1.4：
Model Driven Security / 1.4.1：
Formal Systems Engineering / 1.4.2：
Pattern-based Approaches / 1.4.3：
Tools and Frameworks / 1.4.4：
Workflow Management / 1.4.5：
SOA - Standards & Technology / 2：
Service Oriented Architectures / 2.1：
Principles of SOA / 2.1.1：
Motivating Example / 2.1.2：
Web Services / 2.2：
Basic Definition / 2.2.1：
Service Invocation / 2.2.2：
Service Description and Discovery / 2.2.3：
The Web Services Specification Stack / 2.3：
Transport Layer / 2.3.1：
Messaging Layer / 2.3.2：
Description Layer / 2.3.3：
Discovery Layer / 2.3.4：
Quality of Service Layer / 2.3.5：
Web Services Security Standards / 2.3.6：
Services Composition Layer / 2.3.7：
Basic Concepts of SOA Security / 3：
What Is (SOA) Security? / 3.1：
Security Objectives / 3.2：
Security Policies / 3.3：
Basic Security Policies / 3.3.1：
Policy Models / 3.3.2：
Advanced Security Policies / 3.3.3：
Security Analysis / 3.4：
Security Requirements / 3.4.1：
Attacks / 3.4.2：
Confidentiality, Integrity, and Authenticity / 3.5：
Authentication / 3.5.2：
Advanced Web Services Security Standards / 3.5.3：
Domain Architectures / 4：
Model Driven Software Development / 4.1：
The Unified Modeling Language / 4.1.1：
The Meta-Object Facility / 4.1.2：
Model Driven Architecture / 4.1.3：
A Definition of Model Driven Software Development / 4.1.5：
Domain Specific Languages / 4.3：
The Target Architecture / 4.4：
Model-(to-model-)to-code Transformation / 4.5：
Domain Architecture / 4.6：
Framework / 4.7：
Definition / 4.8：
Extensions to the Problem Space / 4.8.2：
Realizing SOA Security / Part II：
Sectino - A Motivating Case Study from E-Government / 5：
Problem Context / 5.1：
Project Mission / 5.2：
Expected Benefits / 5.3：
Scenario Description / 5.4：
Requirements / 5.4.1：
Results / 5.4.2：
Overview / 6：
Modularity / 6.1.1：
Traceability / 6.1.2：
Model-driven Configuration of Security Services / 6.1.3：
Tight Integration of Functional and Security Aspects / 6.1.4：
Security as a Process / 6.1.5：
Functional System View / 6.2：
Level of Interaction / 6.2.1：
Level of Abstraction / 6.2.2：
Functional Meta-models / 6.2.3：
Global Functional Meta-model / 6.2.4：
Local Functional Meta-model / 6.2.5：
Security Analysis Process / 6.3：
Security Concepts / 6.3.1：
The Security Micro-process / 6.3.2：
Elaborate Functional Model / 6.3.3：
Define Security Objectives / 6.3.4：
Identify Dependencies / 6.3.5：
Security Requirements Engineering / 6.3.6：
Threat and Risk Analysis / 6.3.7：
Security Control Engineering / 6.3.8：
Access Control / 6.4：
Standards and Baseline Protection / 6.5：
Security Management / 6.5.2：
Security Analysis in the Software Process / 6.5.3：
Formal Approaches to Security Requirements Specification / 6.5.4：
Modeling Security Critical SOA Applications / 7：
The Sectet Domain Specific Language / 7.1：
Domain Definition / 7.1.1：
Global Worklfow / 7.1.2：
Local Worklfow / 7.1.3：
Sectet Model Views / 7.1.4：
The DSL Meta-models / 7.1.5：
The Workflow View / 7.2.1：
The Interface View / 7.2.2：
Integrating Security into the DSL / 7.3：
Enforcing Security with the Sectet Reference Architecture / 8：
Architectural Blueprint / 8.1：
Components / 8.2：
Service Components / 8.2.1：
Security Components / 8.2.2：
Supporting Security Components / 8.2.3：
Communication Protocols / 8.3：
Enforcing Confidentiality and Integrity / 8.3.1：
Enforcing Non-repudiation / 8.3.2：
Component Configuration / 8.4：
Inbound Messaging - (Executable Security Policy File) / 8.4.1：
Outbound Messaging - (Executable Security Policy Files) / 8.4.2：
Request for Compliance Check / 8.4.3：
Response Request for Compliance Check / 8.4.4：
Technology and Standards / 8.4.5：
Model Transformation & Code Generation / 9：
Transformations in the Sectet-Framework / 9.1：
The Generation of Security Artefacts / 9.1.1：
The Generation of Services Artefacts / 9.1.2：
Security Transformations / 9.2：
Inbound Policy File / 9.2.1：
Outbound Policy Files / 9.2.2：
Services Transformations / 9.3：
Global Workflow to Local Workflow Translation / 9.3.1：
Global Workflow to WSDL Description / 9.3.2：
Global Workflow to XSD Schema Template / 9.3.3：
Implementing Transformation / 9.4：
Template Based Transformations / 9.4.1：
Meta-model Based Transformations / 9.4.2：
Software & Security Management / 10：
Tool Chain / 10.1：
Modeling / 10.1.1：
Code Generation / 10.1.2：
Build Tools and Integrated Development Environments / 10.1.3：
The Realization Process / 10.1.4：
The Engineering Process / 10.1.5：
The Deployment Process / 10.2：
Extending Sectet: Advanced Security Policy Modeling / 11：
Motivation / 11.1：
Extending the DSL / 11.2：
A New Security Objective / 11.2.1：
Introducing the RBAC Policy Model / 11.2.2：
Modeling Policies with Dynamic Constraints / 11.3：
Sectet-PL / 11.3.1：
Static RBAC / 11.3.2：
Dynamic RBAC / 11.3.3：
Rights Delegation / 11.3.4：
Integrating Sectet-PL into the Sectet- Framework / 11.4：
Metamodel Extensions / 11.4.1：
Sectet-PL - Abstract Syntax / 11.4.2：
Extending the Reference Architecture / 11.5：
Access Control, Delegation and Privacy Policies / 11.5.1：
Protocol Extensions / 11.5.2：
PDP Extensions / 11.5.3：
Sectet-PL Transformations / 11.6：
Modeling Advanced Use Cases with Sectet-PL / 11.7：
Break-Glass Policy (BGP) / 11.7.1：
4-Eyes-Principle / 11.7.2：
Usage Control (UC) / 11.7.3：
Qualified Signature / 11.7.4：
A Case Study from Healthcare / Part III：
health@net - A Case Study from Healthcare / 12：
Background / 12.1：
The Electronic Healthcare Record / 12.1.1：
National E-Health Initiatives / 12.1.2：
Technical Standards for Healthcare / 12.1.3：
The Austrian Data Privacy Law / 12.1.4：
health@net / 12.2：
Organizational Setting / 12.2.1：
Architectural Concept / 12.2.3：
health@net - Security Analysis / 12.3：
Identification of Security Objectives / 12.3.1：
Engineering of Security Requirements / 12.3.4：
Conclusion / 12.3.5：
health@net - Security Concept / 12.4：
Phase 1: Service-level Security / 12.4.1：
Phase 2a: Static, Process-level Security / 12.4.2：
Phase 2b: Dynamic, Process-level Security / 12.4.3：
Realizing Security with the Sectet-Framework / 12.5：
Conceptual Background / 12.5.1：
Model Views / 12.5.2：
health@net - Phases 2a & 2b / 12.6：
Use Cases / 12.6.1：
Security Architecture / 12.6.2：
Appendices / Part IV：
Mapping Tables / A：
Mapping Table for Inbound Policy File / A.1：
Mapping Table for Outbound Policy Files / A.2：
Mapping Table for BPEL Files / A.3：
Mapping Table for BPEL Files (continued) / A.4：
Mapping Table for WSDL Files / A.5：
References
Index
The Basics of SOA Security Engineering / Part I：
Introduction / 1：
Service Oriented Architecture / 1.1：
13.

電子ブック
ＥＢ
13. Security Engineering for Service-Oriented Architectures
Michael Hafner, Ruth Breu
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2009
所蔵情報: loading…
目次情報: 続きを見る
The Basics of SOA Security Engineering / Part I：
Introduction / 1：
Service Oriented Architecture / 1.1：
Interoperability and Securitiy Issues in SOA / 1.1.1：
Model Driven Security Engineering / 1.1.2：
Problem Description / 1.2：
Contribution / 1.3：
ProSecO / 1.3.1：
Sectet / 1.3.2：
Related Work / 1.4：
Model Driven Security / 1.4.1：
Formal Systems Engineering / 1.4.2：
Pattern-based Approaches / 1.4.3：
Tools and Frameworks / 1.4.4：
Workflow Management / 1.4.5：
SOA - Standards & Technology / 2：
Service Oriented Architectures / 2.1：
Principles of SOA / 2.1.1：
Motivating Example / 2.1.2：
Web Services / 2.2：
Basic Definition / 2.2.1：
Service Invocation / 2.2.2：
Service Description and Discovery / 2.2.3：
The Web Services Specification Stack / 2.3：
Transport Layer / 2.3.1：
Messaging Layer / 2.3.2：
Description Layer / 2.3.3：
Discovery Layer / 2.3.4：
Quality of Service Layer / 2.3.5：
Web Services Security Standards / 2.3.6：
Services Composition Layer / 2.3.7：
Basic Concepts of SOA Security / 3：
What Is (SOA) Security? / 3.1：
Security Objectives / 3.2：
Security Policies / 3.3：
Basic Security Policies / 3.3.1：
Policy Models / 3.3.2：
Advanced Security Policies / 3.3.3：
Security Analysis / 3.4：
Security Requirements / 3.4.1：
Attacks / 3.4.2：
Confidentiality, Integrity, and Authenticity / 3.5：
Authentication / 3.5.2：
Advanced Web Services Security Standards / 3.5.3：
Domain Architectures / 4：
Model Driven Software Development / 4.1：
The Unified Modeling Language / 4.1.1：
The Meta-Object Facility / 4.1.2：
Model Driven Architecture / 4.1.3：
A Definition of Model Driven Software Development / 4.1.5：
Domain Specific Languages / 4.3：
The Target Architecture / 4.4：
Model-(to-model-)to-code Transformation / 4.5：
Domain Architecture / 4.6：
Framework / 4.7：
Definition / 4.8：
Extensions to the Problem Space / 4.8.2：
Realizing SOA Security / Part II：
Sectino - A Motivating Case Study from E-Government / 5：
Problem Context / 5.1：
Project Mission / 5.2：
Expected Benefits / 5.3：
Scenario Description / 5.4：
Requirements / 5.4.1：
Results / 5.4.2：
Overview / 6：
Modularity / 6.1.1：
Traceability / 6.1.2：
Model-driven Configuration of Security Services / 6.1.3：
Tight Integration of Functional and Security Aspects / 6.1.4：
Security as a Process / 6.1.5：
Functional System View / 6.2：
Level of Interaction / 6.2.1：
Level of Abstraction / 6.2.2：
Functional Meta-models / 6.2.3：
Global Functional Meta-model / 6.2.4：
Local Functional Meta-model / 6.2.5：
Security Analysis Process / 6.3：
Security Concepts / 6.3.1：
The Security Micro-process / 6.3.2：
Elaborate Functional Model / 6.3.3：
Define Security Objectives / 6.3.4：
Identify Dependencies / 6.3.5：
Security Requirements Engineering / 6.3.6：
Threat and Risk Analysis / 6.3.7：
Security Control Engineering / 6.3.8：
Access Control / 6.4：
Standards and Baseline Protection / 6.5：
Security Management / 6.5.2：
Security Analysis in the Software Process / 6.5.3：
Formal Approaches to Security Requirements Specification / 6.5.4：
Modeling Security Critical SOA Applications / 7：
The Sectet Domain Specific Language / 7.1：
Domain Definition / 7.1.1：
Global Worklfow / 7.1.2：
Local Worklfow / 7.1.3：
Sectet Model Views / 7.1.4：
The DSL Meta-models / 7.1.5：
The Workflow View / 7.2.1：
The Interface View / 7.2.2：
Integrating Security into the DSL / 7.3：
Enforcing Security with the Sectet Reference Architecture / 8：
Architectural Blueprint / 8.1：
Components / 8.2：
Service Components / 8.2.1：
Security Components / 8.2.2：
Supporting Security Components / 8.2.3：
Communication Protocols / 8.3：
Enforcing Confidentiality and Integrity / 8.3.1：
Enforcing Non-repudiation / 8.3.2：
Component Configuration / 8.4：
Inbound Messaging - (Executable Security Policy File) / 8.4.1：
Outbound Messaging - (Executable Security Policy Files) / 8.4.2：
Request for Compliance Check / 8.4.3：
Response Request for Compliance Check / 8.4.4：
Technology and Standards / 8.4.5：
Model Transformation & Code Generation / 9：
Transformations in the Sectet-Framework / 9.1：
The Generation of Security Artefacts / 9.1.1：
The Generation of Services Artefacts / 9.1.2：
Security Transformations / 9.2：
Inbound Policy File / 9.2.1：
Outbound Policy Files / 9.2.2：
Services Transformations / 9.3：
Global Workflow to Local Workflow Translation / 9.3.1：
Global Workflow to WSDL Description / 9.3.2：
Global Workflow to XSD Schema Template / 9.3.3：
Implementing Transformation / 9.4：
Template Based Transformations / 9.4.1：
Meta-model Based Transformations / 9.4.2：
Software & Security Management / 10：
Tool Chain / 10.1：
Modeling / 10.1.1：
Code Generation / 10.1.2：
Build Tools and Integrated Development Environments / 10.1.3：
The Realization Process / 10.1.4：
The Engineering Process / 10.1.5：
The Deployment Process / 10.2：
Extending Sectet: Advanced Security Policy Modeling / 11：
Motivation / 11.1：
Extending the DSL / 11.2：
A New Security Objective / 11.2.1：
Introducing the RBAC Policy Model / 11.2.2：
Modeling Policies with Dynamic Constraints / 11.3：
Sectet-PL / 11.3.1：
Static RBAC / 11.3.2：
Dynamic RBAC / 11.3.3：
Rights Delegation / 11.3.4：
Integrating Sectet-PL into the Sectet- Framework / 11.4：
Metamodel Extensions / 11.4.1：
Sectet-PL - Abstract Syntax / 11.4.2：
Extending the Reference Architecture / 11.5：
Access Control, Delegation and Privacy Policies / 11.5.1：
Protocol Extensions / 11.5.2：
PDP Extensions / 11.5.3：
Sectet-PL Transformations / 11.6：
Modeling Advanced Use Cases with Sectet-PL / 11.7：
Break-Glass Policy (BGP) / 11.7.1：
4-Eyes-Principle / 11.7.2：
Usage Control (UC) / 11.7.3：
Qualified Signature / 11.7.4：
A Case Study from Healthcare / Part III：
health@net - A Case Study from Healthcare / 12：
Background / 12.1：
The Electronic Healthcare Record / 12.1.1：
National E-Health Initiatives / 12.1.2：
Technical Standards for Healthcare / 12.1.3：
The Austrian Data Privacy Law / 12.1.4：
health@net / 12.2：
Organizational Setting / 12.2.1：
Architectural Concept / 12.2.3：
health@net - Security Analysis / 12.3：
Identification of Security Objectives / 12.3.1：
Engineering of Security Requirements / 12.3.4：
Conclusion / 12.3.5：
health@net - Security Concept / 12.4：
Phase 1: Service-level Security / 12.4.1：
Phase 2a: Static, Process-level Security / 12.4.2：
Phase 2b: Dynamic, Process-level Security / 12.4.3：
Realizing Security with the Sectet-Framework / 12.5：
Conceptual Background / 12.5.1：
Model Views / 12.5.2：
health@net - Phases 2a & 2b / 12.6：
Use Cases / 12.6.1：
Security Architecture / 12.6.2：
Appendices / Part IV：
Mapping Tables / A：
Mapping Table for Inbound Policy File / A.1：
Mapping Table for Outbound Policy Files / A.2：
Mapping Table for BPEL Files / A.3：
Mapping Table for BPEL Files (continued) / A.4：
Mapping Table for WSDL Files / A.5：
References
Index
The Basics of SOA Security Engineering / Part I：
Introduction / 1：
Service Oriented Architecture / 1.1：
14.

電子ブック
ＥＢ
14. Verification and Validation in Systems Engineering
Mourad Debbabi, Fawzi Hassa?ne
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2010
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Verification and Validation Problem Statement / 1.1：
Systems Engineering / 1.2：
Systems Engineering Standards / 1.3：
Model-Driven Architecture / 1.4：
Systems Engineering Modeling Languages / 1.5：
UML 2.x: Unified Modeling Language / 1.5.1：
SysML: Systems Modeling Language / 1.5.2：
IDEF: Integration Definition Methods / 1.5.3：
Outline / 1.6：
Architecture Frameworks, Model-Driven Architecture, and Simulation / 2：
Architecture Frameworks / 2.1：
Zachman Framework / 2.1.1：
Open Group Architecture Framework / 2.1.2：
DoD Architecture Framework / 2.1.3：
UK Ministry of Defence Architecture Framework / 2.1.4：
UML Profile for DoDAF/MODAF / 2.1.5：
AP233 Standard for Data Exchange / 2.2：
Executable Architectures or from Design to Simulation / 2.3：
Why Executable Architectures? / 2.3.1：
Modeling and Simulation as an Enabler for Executable Architectures / 2.3.2：
DoDAF in Relation to SE and SysML / 2.4：
Conclusion / 2.5：
Unified Modeling Language / 3：
UML History / 3.1：
UML Diagrams / 3.2：
Class Diagram / 3.2.1：
Component Diagram / 3.2.2：
Composite Structure Diagram / 3.2.3：
Deployment Diagram / 3.2.4：
Object Diagram / 3.2.5：
Package Diagram / 3.2.6：
Activity Diagram / 3.2.7：
Activity Diagram Execution / 3.2.8：
Use Case Diagram / 3.2.9：
State Machine Diagram / 3.2.10：
Sequence Diagram / 3.2.11：
Communication Diagram / 3.2.12：
Interaction Overview Diagram / 3.2.13：
Timing Diagram / 3.2.14：
UML Profiling Mechanisms / 3.3：
Systems Modeling Language / 3.4：
SysML History / 4.1：
UML and SysML Relationships / 4.2：
SysML Diagrams / 4.3：
Block Definition Diagram / 4.3.1：
Internal Block Diagram / 4.3.2：
Parametric Diagram / 4.3.3：
Requirement Diagram / 4.3.5：
Verification, Validation, and Accreditation / 4.3.6：
V&V Techniques Overview / 5.1：
Inspection / 5.1.1：
Testing / 5.1.2：
Simulation / 5.1.3：
Reference Model Equivalence Checking / 5.1.4：
Theorem Proving / 5.1.5：
Verification Techniques for Object-Oriented Design / 5.2：
Design Perspectives / 5.2.1：
Software Engineering Techniques / 5.2.2：
Formal Verification Techniques / 5.2.3：
Program Analysis Techniques / 5.2.4：
V&V of Systems Engineering Design Models / 5.3：
Tool Support / 5.4：
Formal Verification Environments / 5.4.1：
Static Analyzers / 5.4.2：
Automatic Approach for Synergistic Verification and Validation / 5.5：
Synergistic Verification and Validation Methodology / 6.1：
Dedicated V&V Approach for Systems Engineering / 6.2：
Automatic Formal Verification of System Design Models / 6.2.1：
Program Analysis of Behavioral Design Models / 6.2.2：
Software Engineering Quantitative Techniques / 6.2.3：
Probabilistic Behavior Assessment / 6.3：
Established Results / 6.4：
Verification and Validation Tool / 6.5：
Software Engineering Metrics in the Context of Systems Engineering / 6.6：
Metrics Suites Overview / 7.1：
Chidamber and Kemerer Metrics / 7.1.1：
MOOD Metrics / 7.1.2：
Li and Henry's Metrics / 7.1.3：
Lorenz and Kidd's Metrics / 7.1.4：
Robert Martin Metrics / 7.1.5：
Bansiya and Davis Metrics / 7.1.6：
Briand et al. Metrics / 7.1.7：
Quality Attributes / 7.2：
Software Metrics Computation / 7.3：
Abstractness (A) / 7.3.1：
Instability (I) / 7.3.2：
Distance from the Main Sequence (DMS) / 7.3.3：
Class Responsibility (CR) / 7.3.4：
Class Category Relational Cohesion (CCRC) / 7.3.5：
Depth of Inheritance Tree (DIT) / 7.3.6：
Number of Children (NOC) / 7.3.7：
Coupling Between Object Classes (CBO) / 7.3.8：
Number of Methods (NOM) / 7.3.9：
Number of Attributes (NOA) / 7.3.10：
Number of Methods Added (NMA) / 7.3.11：
Number of Methods Overridden (NMO) / 7.3.12：
Number of Methods Inherited (NMI) / 7.3.13：
Specialization Index (SIX) / 7.3.14：
Public Methods Ration (PMR) / 7.3.15：
Case Study / 7.4：
Verification and Validation of UML Behavioral Diagrams / 7.5：
Configuration Transition System / 8.1：
Model Checking of Configuration Transition Systems / 8.2：
Property Specification Using CTL / 8.3：
Program Analysis of Configuration Transition Systems / 8.4：
V&V of UML State Machine Diagram / 8.5：
Semantic Model Derivation / 8.5.1：
Application of Program Analysis / 8.5.2：
V&V of UML Sequence Diagram / 8.6：
Sequence Diagram Case Study / 8.6.1：
V&V of UML Activity Diagram / 8.7：
Activity Diagram Case Study / 8.7.1：
Probabilistic Model Checking of SysML Activity Diagrams / 8.8：
Probabilistic Verification Approach / 9.1：
Translation into PRISM / 9.2：
PCTL* Property Specification / 9.3：
Performance Analysis of Time-Constrained SysML Activity Diagrams / 9.4：
Time Annotation / 10.1：
Derivation of the Semantic Model / 10.2：
Model-Checking Time-Constrained Activity Diagrams / 10.3：
Discrete-Time Markov Chain / 10.3.1：
PRISM Input Language / 10.3.2：
Mapping SysML Activity Diagrams into DTMC / 10.3.3：
Threads Identification / 10.3.4：
Performance Analysis Case Study / 10.4：
Scalability / 10.5：
Semantic Foundations of SysML Activity Diagrams / 10.6：
Activity Calculus / 11.1：
Syntax / 11.1.1：
Operational Semantics / 11.1.2：
Markov Decision Process / 11.2：
Soundness of the Translation Algorithm / 11.4：
Notation / 12.1：
Methodology / 12.2：
Formalization of the PRISM Input Language / 12.3：
Formal Translation / 12.3.1：
Simulation Preorder for Markov Decision Processes / 12.5：
References / 12.7：
Index
Introduction / 1：
Verification and Validation Problem Statement / 1.1：
Systems Engineering / 1.2：
15.

電子ブック
ＥＢ
15. Verification and Validation in Systems Engineering
Mourad Debbabi, Fawzi Hassaïne, Luay Alawneh, Yosr Jarraya, Andrei Soeanu
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2010
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Verification and Validation Problem Statement / 1.1：
Systems Engineering / 1.2：
Systems Engineering Standards / 1.3：
Model-Driven Architecture / 1.4：
Systems Engineering Modeling Languages / 1.5：
UML 2.x: Unified Modeling Language / 1.5.1：
SysML: Systems Modeling Language / 1.5.2：
IDEF: Integration Definition Methods / 1.5.3：
Outline / 1.6：
Architecture Frameworks, Model-Driven Architecture, and Simulation / 2：
Architecture Frameworks / 2.1：
Zachman Framework / 2.1.1：
Open Group Architecture Framework / 2.1.2：
DoD Architecture Framework / 2.1.3：
UK Ministry of Defence Architecture Framework / 2.1.4：
UML Profile for DoDAF/MODAF / 2.1.5：
AP233 Standard for Data Exchange / 2.2：
Executable Architectures or from Design to Simulation / 2.3：
Why Executable Architectures? / 2.3.1：
Modeling and Simulation as an Enabler for Executable Architectures / 2.3.2：
DoDAF in Relation to SE and SysML / 2.4：
Conclusion / 2.5：
Unified Modeling Language / 3：
UML History / 3.1：
UML Diagrams / 3.2：
Class Diagram / 3.2.1：
Component Diagram / 3.2.2：
Composite Structure Diagram / 3.2.3：
Deployment Diagram / 3.2.4：
Object Diagram / 3.2.5：
Package Diagram / 3.2.6：
Activity Diagram / 3.2.7：
Activity Diagram Execution / 3.2.8：
Use Case Diagram / 3.2.9：
State Machine Diagram / 3.2.10：
Sequence Diagram / 3.2.11：
Communication Diagram / 3.2.12：
Interaction Overview Diagram / 3.2.13：
Timing Diagram / 3.2.14：
UML Profiling Mechanisms / 3.3：
Systems Modeling Language / 3.4：
SysML History / 4.1：
UML and SysML Relationships / 4.2：
SysML Diagrams / 4.3：
Block Definition Diagram / 4.3.1：
Internal Block Diagram / 4.3.2：
Parametric Diagram / 4.3.3：
Requirement Diagram / 4.3.5：
Verification, Validation, and Accreditation / 4.3.6：
V&V Techniques Overview / 5.1：
Inspection / 5.1.1：
Testing / 5.1.2：
Simulation / 5.1.3：
Reference Model Equivalence Checking / 5.1.4：
Theorem Proving / 5.1.5：
Verification Techniques for Object-Oriented Design / 5.2：
Design Perspectives / 5.2.1：
Software Engineering Techniques / 5.2.2：
Formal Verification Techniques / 5.2.3：
Program Analysis Techniques / 5.2.4：
V&V of Systems Engineering Design Models / 5.3：
Tool Support / 5.4：
Formal Verification Environments / 5.4.1：
Static Analyzers / 5.4.2：
Automatic Approach for Synergistic Verification and Validation / 5.5：
Synergistic Verification and Validation Methodology / 6.1：
Dedicated V&V Approach for Systems Engineering / 6.2：
Automatic Formal Verification of System Design Models / 6.2.1：
Program Analysis of Behavioral Design Models / 6.2.2：
Software Engineering Quantitative Techniques / 6.2.3：
Probabilistic Behavior Assessment / 6.3：
Established Results / 6.4：
Verification and Validation Tool / 6.5：
Software Engineering Metrics in the Context of Systems Engineering / 6.6：
Metrics Suites Overview / 7.1：
Chidamber and Kemerer Metrics / 7.1.1：
MOOD Metrics / 7.1.2：
Li and Henry's Metrics / 7.1.3：
Lorenz and Kidd's Metrics / 7.1.4：
Robert Martin Metrics / 7.1.5：
Bansiya and Davis Metrics / 7.1.6：
Briand et al. Metrics / 7.1.7：
Quality Attributes / 7.2：
Software Metrics Computation / 7.3：
Abstractness (A) / 7.3.1：
Instability (I) / 7.3.2：
Distance from the Main Sequence (DMS) / 7.3.3：
Class Responsibility (CR) / 7.3.4：
Class Category Relational Cohesion (CCRC) / 7.3.5：
Depth of Inheritance Tree (DIT) / 7.3.6：
Number of Children (NOC) / 7.3.7：
Coupling Between Object Classes (CBO) / 7.3.8：
Number of Methods (NOM) / 7.3.9：
Number of Attributes (NOA) / 7.3.10：
Number of Methods Added (NMA) / 7.3.11：
Number of Methods Overridden (NMO) / 7.3.12：
Number of Methods Inherited (NMI) / 7.3.13：
Specialization Index (SIX) / 7.3.14：
Public Methods Ration (PMR) / 7.3.15：
Case Study / 7.4：
Verification and Validation of UML Behavioral Diagrams / 7.5：
Configuration Transition System / 8.1：
Model Checking of Configuration Transition Systems / 8.2：
Property Specification Using CTL / 8.3：
Program Analysis of Configuration Transition Systems / 8.4：
V&V of UML State Machine Diagram / 8.5：
Semantic Model Derivation / 8.5.1：
Application of Program Analysis / 8.5.2：
V&V of UML Sequence Diagram / 8.6：
Sequence Diagram Case Study / 8.6.1：
V&V of UML Activity Diagram / 8.7：
Activity Diagram Case Study / 8.7.1：
Probabilistic Model Checking of SysML Activity Diagrams / 8.8：
Probabilistic Verification Approach / 9.1：
Translation into PRISM / 9.2：
PCTL* Property Specification / 9.3：
Performance Analysis of Time-Constrained SysML Activity Diagrams / 9.4：
Time Annotation / 10.1：
Derivation of the Semantic Model / 10.2：
Model-Checking Time-Constrained Activity Diagrams / 10.3：
Discrete-Time Markov Chain / 10.3.1：
PRISM Input Language / 10.3.2：
Mapping SysML Activity Diagrams into DTMC / 10.3.3：
Threads Identification / 10.3.4：
Performance Analysis Case Study / 10.4：
Scalability / 10.5：
Semantic Foundations of SysML Activity Diagrams / 10.6：
Activity Calculus / 11.1：
Syntax / 11.1.1：
Operational Semantics / 11.1.2：
Markov Decision Process / 11.2：
Soundness of the Translation Algorithm / 11.4：
Notation / 12.1：
Methodology / 12.2：
Formalization of the PRISM Input Language / 12.3：
Formal Translation / 12.3.1：
Simulation Preorder for Markov Decision Processes / 12.5：
References / 12.7：
Index
Introduction / 1：
Verification and Validation Problem Statement / 1.1：
Systems Engineering / 1.2：
16.

電子ブック
ＥＢ
16. Software Product Lines in Action
Frank van der Linden, Eelco Rommes, Klaus Schmid, Frank J. van der Linden
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2007
所蔵情報: loading…
目次情報: 続きを見る
Aspects of Software Product Line Engineering
The Product Line Engineering Approach / 1：
Motivation / 1.1：
A Brief History of Software Product Line Engineering / 1.2：
Fundamentals of the Software Product Line Engineering Approach / 1.3：
Variability Management / 1.4：
Types of Variability / 1.4.1：
Variability Representation / 1.4.2：
Application Engineering and Variability / 1.4.3：
Business-Centric / 1.5：
Architecture-Centric / 1.6：
Two-Life-Cycle Approach / 1.7：
The BAPO Model / 1.8：
Summary / 1.9：
Business / 2：
Product Line Markets / 2.1：
Product Definition Strategy / 2.2.1：
Market Strategies / 2.2.2：
The Product Line Life-Cycle / 2.2.3：
The Relation of Strategy and Product Line Engineering / 2.2.4：
Product Line Economics / 2.3：
Economic Results of Product Line Engineering / 2.3.1：
A Simple Model of Product Line Economics / 2.3.2：
Advanced Aspects of Product Line Economics / 2.3.3：
Product Management and Scoping / 2.4：
Product Portfolio Management / 2.4.1：
Domain Potential Analysis / 2.4.2：
Asset Scoping / 2.4.3：
Architecture / 2.5：
Architecture Concerns / 3.1：
Architecturally Significant Requirements / 3.2.1：
Conceptual Architecture / 3.2.2：
Structure / 3.2.3：
Texture / 3.2.4：
Product Line Architecting / 3.3：
Basic Variability Techniques / 3.3.1：
Concrete Variation Mechanisms / 3.3.2：
Evaluation / 3.4：
Evolution / 3.5：
End of Life / 3.5.1：
Process / 3.6：
The Software Product Line Engineering Framework / 4.1：
Domain Engineering / 4.3：
Product Management / 4.3.1：
Domain Requirements Engineering / 4.3.2：
Domain Design / 4.3.3：
Domain Realisation / 4.3.4：
Domain Testing / 4.3.5：
Application Engineering / 4.4：
Application Requirements Engineering / 4.4.1：
Application Design / 4.4.2：
Application Realisation / 4.4.3：
Application Testing / 4.4.4：
Process Maturity: CMMI / 4.5：
Maturity Levels / 4.5.1：
Structure of CMMI Models / 4.5.2：
Organisation / 4.6：
Roles and Responsibilities / 5.1：
Product Manager / 5.2.1：
Domain Requirements Engineer / 5.2.2：
Domain Architect / 5.2.3：
Domain Developer / 5.2.4：
Domain Tester / 5.2.5：
Domain Asset Manager / 5.2.6：
Application Requirements Engineer / 5.2.7：
Application Architect / 5.2.8：
Application Developer / 5.2.9：
Application Tester / 5.2.10：
Organisational Structures / 5.3：
Product-Oriented Organisation / 5.3.1：
Process-Oriented Organisation / 5.3.2：
Matrix Organisation / 5.3.3：
Testing / 5.3.4：
Asset Management / 5.3.5：
Geographical Distribution / 5.3.6：
Collaboration Schemes / 5.5：
The Family Evaluation Framework / 5.6：
Business Dimension / 6.1：
Level 1: Project-Based / 6.3.1：
Level 2: Aware / 6.3.2：
Level3: Managed / 6.3.3：
Level4: Measured / 6.3.4：
Level 5: Optimised / 6.3.5：
Architecture Dimension / 6.4：
Level 1: Independent Development / 6.4.1：
Level 2: Standardised Infrastructure / 6.4.2：
Level 3: Software Platform / 6.4.3：
Level4: Variant Products / 6.4.4：
Level 5: Configuring / 6.4.5：
Process Dimension / 6.5：
Level1: Initial / 6.5.1：
Level2: Managed / 6.5.2：
Level 3: Defined / 6.5.3：
Level 4: Quantitatively Managed / 6.5.4：
Level 5: Optimising / 6.5.5：
Organisation Dimension / 6.6：
Level 1: Project / 6.6.1：
Level2: Reuse / 6.6.2：
Level 3: Weakly Connected / 6.6.3：
Level 4: Synchronised / 6.6.4：
Level 5: Domain-Oriented / 6.6.5：
Applying the FEF / 6.7：
Complex Organisations / 6.7.1：
Example / 6.7.2：
Connection to Other Approaches / 6.8：
Experience Reports / 6.9：
Experiences in Product Line Engineering / 7：
Experimental Software Engineering / 7.1：
Experience Reports on Product Line Development / 7.2：
Case Study Basics / 7.3：
Setting Up Case Studies / 7.3.1：
The Case Study Format / 7.3.2：
Overview of the Case Studies / 7.4：
AKVAsmart / 8：
Introduction / 8.1：
Case Description / 8.2：
Market Drivers / 8.2.2：
Approach / 8.3：
The Framework / 8.4：
Examples of Plug-ins / 8.4.2：
Results and Impact Evaluation / 8.5：
Lessons Learned / 8.6：
Outlook / 8.7：
Bosch Gasoline Systems / 9：
Business Strategy / 9.1：
Work Products: Software Architecture / 9.3.2：
Software Components / 9.3.3：
Processes and Methods / 9.3.4：
Tool Environment / 9.3.5：
Management Role / 9.3.6：
Product and Process Excellence - Product Line Engineering and CMMI / 9.4.2：
DNV Software / 9.5：
First Generation Product Line Engineering / 10.1：
Second Generation Product Line Engineering / 10.3.2：
market maker Software AG / 10.4：
Adoption Process / 11.1：
Fast Time to Market / 11.3.1：
New Team / 11.3.2：
Early Focus on Applications / 11.3.3：
No Separation of Domain and Application Engineering Teams / 11.3.4：
Encapsulation of Legacy Systems / 11.3.5：
Simple Architectural Style / 11.3.6：
Effective Communication / 11.3.7：
Immediate and Reliable Decisions / 11.3.8：
Coaching / 11.3.9：
Small Investments / 11.3.10：
Current Process / 11.4：
Nokia Mobile Phones / 11.4.1：
Typing and Quality Characteristics / 12.1：
Traceability / 12.3.2：
The ART Environment / 12.3.3：
Example: Security / 12.4：
Nokia Networks / 12.5：
Philips Consumer Electronics Software for Televisions / 13.1：
Business Aspects / 14.1：
Results / 14.5：
Philips Medical Systems / 14.9：
Adoption Approach / 15.1：
Current Development Approach / 15.3.2：
Siemens Medical Solutions / 15.4：
Telvent / 16.1：
Organisation and Business / 17.1：
Using the Abstract Factory Pattern / 17.3.2：
Introducing the Dynamic Abstract Factory Pattern / 17.3.3：
Reusing the Dynamic Abstract Factory Pattern / 17.3.4：
Conclusions / 17.4：
Analysis / 18：
Complexity / 18.1：
Variability and Commonality / 18.1.2：
Efficiency and Costs / 18.1.3：
Reuse and Architecture / 18.1.4：
Quality / 18.1.5：
FEF Evaluations / 18.2：
Evaluations / 18.3：
How to Do It / 18.5：
Guidelines / 18.6.2：
Benefits / 18.6.3：
Concerns / 18.6.4：
Starting with Software Product Line Engineering / 18.6.5：
Decide / 19.1：
Define Business Strategy and Vision / 19.1.1：
Learn About Software Product Line Engineering / 19.1.2：
Perform a Risk Analysis / 19.1.3：
Prepare / 19.2：
Gain Support / 19.2.1：
Set Concrete Goals / 19.2.2：
Scope the Product Line / 19.2.3：
Evaluate the Organisation / 19.2.4：
Plan the Transition / 19.2.5：
Transition / 19.3：
Roll Out and Institutionalise / 19.3.1：
Evolving the Product Line / 19.3.2：
Conclusion / 19.4：
Where We Are / 20：
Current Shortcomings of Product Line Engineering / 20.2：
Methodological Shortcomings / 20.2.1：
Technology and Tools / 20.2.2：
Going Beyond Product Lines / 20.3：
Product Line Engineering for Practitioners / 20.4：
Glossary
References
About the Authors
Index
Aspects of Software Product Line Engineering
The Product Line Engineering Approach / 1：
Motivation / 1.1：
17.

電子ブック
ＥＢ
17. Software Product Lines in Action
Frank van der Linden, Eelco Rommes, Klaus Schmid, Frank J. van der Linden
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2007
所蔵情報: loading…
目次情報: 続きを見る
Aspects of Software Product Line Engineering
The Product Line Engineering Approach / 1：
Motivation / 1.1：
A Brief History of Software Product Line Engineering / 1.2：
Fundamentals of the Software Product Line Engineering Approach / 1.3：
Variability Management / 1.4：
Types of Variability / 1.4.1：
Variability Representation / 1.4.2：
Application Engineering and Variability / 1.4.3：
Business-Centric / 1.5：
Architecture-Centric / 1.6：
Two-Life-Cycle Approach / 1.7：
The BAPO Model / 1.8：
Summary / 1.9：
Business / 2：
Product Line Markets / 2.1：
Product Definition Strategy / 2.2.1：
Market Strategies / 2.2.2：
The Product Line Life-Cycle / 2.2.3：
The Relation of Strategy and Product Line Engineering / 2.2.4：
Product Line Economics / 2.3：
Economic Results of Product Line Engineering / 2.3.1：
A Simple Model of Product Line Economics / 2.3.2：
Advanced Aspects of Product Line Economics / 2.3.3：
Product Management and Scoping / 2.4：
Product Portfolio Management / 2.4.1：
Domain Potential Analysis / 2.4.2：
Asset Scoping / 2.4.3：
Architecture / 2.5：
Architecture Concerns / 3.1：
Architecturally Significant Requirements / 3.2.1：
Conceptual Architecture / 3.2.2：
Structure / 3.2.3：
Texture / 3.2.4：
Product Line Architecting / 3.3：
Basic Variability Techniques / 3.3.1：
Concrete Variation Mechanisms / 3.3.2：
Evaluation / 3.4：
Evolution / 3.5：
End of Life / 3.5.1：
Process / 3.6：
The Software Product Line Engineering Framework / 4.1：
Domain Engineering / 4.3：
Product Management / 4.3.1：
Domain Requirements Engineering / 4.3.2：
Domain Design / 4.3.3：
Domain Realisation / 4.3.4：
Domain Testing / 4.3.5：
Application Engineering / 4.4：
Application Requirements Engineering / 4.4.1：
Application Design / 4.4.2：
Application Realisation / 4.4.3：
Application Testing / 4.4.4：
Process Maturity: CMMI / 4.5：
Maturity Levels / 4.5.1：
Structure of CMMI Models / 4.5.2：
Organisation / 4.6：
Roles and Responsibilities / 5.1：
Product Manager / 5.2.1：
Domain Requirements Engineer / 5.2.2：
Domain Architect / 5.2.3：
Domain Developer / 5.2.4：
Domain Tester / 5.2.5：
Domain Asset Manager / 5.2.6：
Application Requirements Engineer / 5.2.7：
Application Architect / 5.2.8：
Application Developer / 5.2.9：
Application Tester / 5.2.10：
Organisational Structures / 5.3：
Product-Oriented Organisation / 5.3.1：
Process-Oriented Organisation / 5.3.2：
Matrix Organisation / 5.3.3：
Testing / 5.3.4：
Asset Management / 5.3.5：
Geographical Distribution / 5.3.6：
Collaboration Schemes / 5.5：
The Family Evaluation Framework / 5.6：
Business Dimension / 6.1：
Level 1: Project-Based / 6.3.1：
Level 2: Aware / 6.3.2：
Level3: Managed / 6.3.3：
Level4: Measured / 6.3.4：
Level 5: Optimised / 6.3.5：
Architecture Dimension / 6.4：
Level 1: Independent Development / 6.4.1：
Level 2: Standardised Infrastructure / 6.4.2：
Level 3: Software Platform / 6.4.3：
Level4: Variant Products / 6.4.4：
Level 5: Configuring / 6.4.5：
Process Dimension / 6.5：
Level1: Initial / 6.5.1：
Level2: Managed / 6.5.2：
Level 3: Defined / 6.5.3：
Level 4: Quantitatively Managed / 6.5.4：
Level 5: Optimising / 6.5.5：
Organisation Dimension / 6.6：
Level 1: Project / 6.6.1：
Level2: Reuse / 6.6.2：
Level 3: Weakly Connected / 6.6.3：
Level 4: Synchronised / 6.6.4：
Level 5: Domain-Oriented / 6.6.5：
Applying the FEF / 6.7：
Complex Organisations / 6.7.1：
Example / 6.7.2：
Connection to Other Approaches / 6.8：
Experience Reports / 6.9：
Experiences in Product Line Engineering / 7：
Experimental Software Engineering / 7.1：
Experience Reports on Product Line Development / 7.2：
Case Study Basics / 7.3：
Setting Up Case Studies / 7.3.1：
The Case Study Format / 7.3.2：
Overview of the Case Studies / 7.4：
AKVAsmart / 8：
Introduction / 8.1：
Case Description / 8.2：
Market Drivers / 8.2.2：
Approach / 8.3：
The Framework / 8.4：
Examples of Plug-ins / 8.4.2：
Results and Impact Evaluation / 8.5：
Lessons Learned / 8.6：
Outlook / 8.7：
Bosch Gasoline Systems / 9：
Business Strategy / 9.1：
Work Products: Software Architecture / 9.3.2：
Software Components / 9.3.3：
Processes and Methods / 9.3.4：
Tool Environment / 9.3.5：
Management Role / 9.3.6：
Product and Process Excellence - Product Line Engineering and CMMI / 9.4.2：
DNV Software / 9.5：
First Generation Product Line Engineering / 10.1：
Second Generation Product Line Engineering / 10.3.2：
market maker Software AG / 10.4：
Adoption Process / 11.1：
Fast Time to Market / 11.3.1：
New Team / 11.3.2：
Early Focus on Applications / 11.3.3：
No Separation of Domain and Application Engineering Teams / 11.3.4：
Encapsulation of Legacy Systems / 11.3.5：
Simple Architectural Style / 11.3.6：
Effective Communication / 11.3.7：
Immediate and Reliable Decisions / 11.3.8：
Coaching / 11.3.9：
Small Investments / 11.3.10：
Current Process / 11.4：
Nokia Mobile Phones / 11.4.1：
Typing and Quality Characteristics / 12.1：
Traceability / 12.3.2：
The ART Environment / 12.3.3：
Example: Security / 12.4：
Nokia Networks / 12.5：
Philips Consumer Electronics Software for Televisions / 13.1：
Business Aspects / 14.1：
Results / 14.5：
Philips Medical Systems / 14.9：
Adoption Approach / 15.1：
Current Development Approach / 15.3.2：
Siemens Medical Solutions / 15.4：
Telvent / 16.1：
Organisation and Business / 17.1：
Using the Abstract Factory Pattern / 17.3.2：
Introducing the Dynamic Abstract Factory Pattern / 17.3.3：
Reusing the Dynamic Abstract Factory Pattern / 17.3.4：
Conclusions / 17.4：
Analysis / 18：
Complexity / 18.1：
Variability and Commonality / 18.1.2：
Efficiency and Costs / 18.1.3：
Reuse and Architecture / 18.1.4：
Quality / 18.1.5：
FEF Evaluations / 18.2：
Evaluations / 18.3：
How to Do It / 18.5：
Guidelines / 18.6.2：
Benefits / 18.6.3：
Concerns / 18.6.4：
Starting with Software Product Line Engineering / 18.6.5：
Decide / 19.1：
Define Business Strategy and Vision / 19.1.1：
Learn About Software Product Line Engineering / 19.1.2：
Perform a Risk Analysis / 19.1.3：
Prepare / 19.2：
Gain Support / 19.2.1：
Set Concrete Goals / 19.2.2：
Scope the Product Line / 19.2.3：
Evaluate the Organisation / 19.2.4：
Plan the Transition / 19.2.5：
Transition / 19.3：
Roll Out and Institutionalise / 19.3.1：
Evolving the Product Line / 19.3.2：
Conclusion / 19.4：
Where We Are / 20：
Current Shortcomings of Product Line Engineering / 20.2：
Methodological Shortcomings / 20.2.1：
Technology and Tools / 20.2.2：
Going Beyond Product Lines / 20.3：
Product Line Engineering for Practitioners / 20.4：
Glossary
References
About the Authors
Index
Aspects of Software Product Line Engineering
The Product Line Engineering Approach / 1：
Motivation / 1.1：
18.

電子ブック
ＥＢ
18. Model Driven Architecture and Ontology Development
Dragan Gasevic, Vladan Devedzic, Dragan Djuric, Dragan Djuri?c, Dragan Djuri?c
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2006
所蔵情報: loading…
目次情報: 続きを見る
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
Cognitive Science / 1.2：
Types of Human Knowledge / 1.3：
Knowledge Representation Techniques / 1.4：
Object-Attribute-Value Triplets / 1.4.1：
Uncertain Facts / 1.4.2：
Fuzzy Facts / 1.4.3：
Rules / 1.4.4：
Semantic networks / 1.4.5：
Frames / 1.4.6：
Knowledge Representation Languages / 1.5：
Logic-Based Representation Languages / 1.5.1：
Frame-Based Representation Languages / 1.5.2：
Rule-Based Representation Languages / 1.5.3：
Visual Languages for Knowledge Representation / 1.5.4：
Natural Languages and Knowledge Representation / 1.5.5：
Knowledge Engineering / 1.6：
Open Knowledge Base Connectivity (OKBC) / 1.7：
The Knowledge Level / 1.8：
Ontologies / 2：
Definitions / 2.1：
What Do Ontologies Look Like? / 2.1.2：
Why Ontologies? / 2.1.3：
Key Application Areas / 2.1.4：
Examples / 2.1.5：
Ontological Engineering / 2.2：
Ontology Development Tools / 2.2.1：
Ontology Development Methodologies / 2.2.2：
Applications / 2.3：
Magpie / 2.3.1：
Briefing Associate / 2.3.2：
Quickstep and Foxtrot / 2.3.3：
Advanced Topics / 2.4：
Metadata, Metamodeling, and Ontologies / 2.4.1：
Standard Upper Ontology / 2.4.2：
Ontological Level / 2.4.3：
The Semantic Web / 3：
Rationale / 3.1：
Semantic Web Languages / 3.2：
XML and XML Schema / 3.2.1：
RDF and RDF Schema / 3.2.2：
DAML+OIL / 3.2.3：
OWL / 3.2.4：
SPARQL / 3.2.5：
The Role of Ontologies / 3.3：
Semantic Markup / 3.4：
Semantic Web Services / 3.5：
Open Issues / 3.6：
Quotations / 3.7：
The Model Driven Architecture (MDA) / 4：
Models and Metamodels / 4.1：
Platform-Independent Models / 4.2：
Four-Layer Architecture / 4.3：
The Meta-Object Facility / 4.4：
Specific MDA Metamodels / 4.5：
Unified Modeling Language / 4.5.1：
Common Warehouse Metamodel (CWM) / 4.5.2：
Ontology Definition Metamodel / 4.5.3：
UML Profiles / 4.6：
Examples of UML Profiles / 4.6.1：
An XML for Sharing MDA Artifacts / 4.7：
The Need for Modeling Spaces / 4.8：
Modeling Spaces / 5：
Modeling the Real World / 5.1：
The Real World, Models, and Metamodels / 5.2：
The Essentials of Modeling Spaces / 5.3：
Modeling Spaces Illuminated / 5.4：
A Touch of RDF(S) and MOF Modeling Spaces / 5.5：
A Touch of the Semantic Web and MDA Technical Spaces / 5.6：
Instead of Conclusions / 5.7：
The Model Driven Architecture and Ontologies / Part II：
Software Engineering Approaches to Ontology Development / 6：
A Brief History of Ontology Modeling / 6.1：
Networked Knowledge Representation and Exchange Using UML and RDF / 6.1.1：
Extending the Unified Modeling Language for Ontology Development / 6.1.2：
The Unified Ontology Language / 6.1.3：
UML for the Semantic Web: Transformation-Based Approach / 6.1.4：
The AIFB OWL DL Metamodel / 6.1.5：
The GOOD OLD AI ODM Proposal / 6.1.6：
Ontology Development Tools Based on Software Engineering Techniques / 6.2：
Protege / 6.2.1：
DUET (DAML UML Enhanced Tool) / 6.2.2：
An Ontology Tool for IBM Rational Rose UML Models / 6.2.3：
Visual Ontology Modeler (VOM) / 6.2.4：
Summary of Relations Between UML and Ontologies / 6.3：
Summary of Approaches and Tools for Software Engineering-Based Ontology Development / 6.3.1：
Summary of Differences Between UML and Ontology Languages / 6.3.2：
Future Development / 6.3.3：
The MDA-Based Ontology Infrastructure / 7：
Motivation / 7.1：
Overview / 7.2：
Bridging RDF(S) and MOF / 7.3：
Design Rationale for the Ontology UML Profile / 7.4：
The Ontology Definition Metamodel (ODM) / 8：
ODM Metamodels / 8.1：
A Few Issues Regarding the Revised Joint Submission / 8.2：
The Resource Description Framework Schema (RDFS) metamodel / 8.3：
The Web Ontology Language (OWL) Metamodel / 8.4：
The Ontology UML Profile / 9：
Classes and Individuals in Ontologies / 9.1：
Properties of Ontologies / 9.2：
Statements / 9.3：
Different Versions of the Ontology UML Profile / 9.4：
Mappings of MDA-Based Languages and Ontologies / 10：
Relations Between Modeling Spaces / 10.1：
Transformations Between Modeling Spaces / 10.2：
Example of an Implementation: an XSLT-Based Approach / 10.3：
Implementation Details / 10.3.1：
Transformation Example / 10.3.2：
Practical Experience / 10.3.3：
Discussion / 10.3.4：
Using UML Tools for Ontology Modeling / Part III：
MagicDraw / 11.1：
Starting with MagicDraw / 11.1.1：
Things You Should Know when Working with UML Profiles / 11.1.2：
Creating a New Ontology / 11.1.3：
Working with Ontology Classes / 11.1.4：
Working with Ontology Properties / 11.1.5：
Working with Individuals / 11.1.6：
Working with Statements / 11.1.7：
Poseidon for UML / 11.2：
Modeling Ontology Classes in Poseidon / 11.2.1：
Modeling Ontology Individuals and Statements in Poseidon / 11.2.2：
Sharing UML Models Between UML tools and Protege Using the UML Back End / 11.3：
An MDA Based Ontology Platform: AIR / 12：
The Basic Idea / 12.1：
Metamodel - the Conceptual Building Block of AIR / 12.3：
The AIR Metadata Repository / 12.4：
The AIR Workbench / 12.5：
The Role of XML Technologies / 12.6：
Possibilities / 12.7：
Examples of Ontology / 13：
Petri Net Ontology / 13.1：
Organization of the Petri Net Ontology / 13.1.1：
The Core Petri Net Ontology in the Ontology UML Profile / 13.1.2：
Example of an Extension: Upgraded Petri Nets / 13.1.3：
Educational Ontologies / 13.2：
Conceptual Solution / 13.2.1：
Mapping the Conceptual Model to Ontologies / 13.2.2：
References
Index
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
19.

電子ブック
ＥＢ
19. Model Driven Architecture and Ontology Development
Dragan Gasevic, Vladan Devedzic, Dragan Djuric, Dragan Djuriâc, Dragan Djuriâc
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2006
所蔵情報: loading…
目次情報: 続きを見る
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
Cognitive Science / 1.2：
Types of Human Knowledge / 1.3：
Knowledge Representation Techniques / 1.4：
Object-Attribute-Value Triplets / 1.4.1：
Uncertain Facts / 1.4.2：
Fuzzy Facts / 1.4.3：
Rules / 1.4.4：
Semantic networks / 1.4.5：
Frames / 1.4.6：
Knowledge Representation Languages / 1.5：
Logic-Based Representation Languages / 1.5.1：
Frame-Based Representation Languages / 1.5.2：
Rule-Based Representation Languages / 1.5.3：
Visual Languages for Knowledge Representation / 1.5.4：
Natural Languages and Knowledge Representation / 1.5.5：
Knowledge Engineering / 1.6：
Open Knowledge Base Connectivity (OKBC) / 1.7：
The Knowledge Level / 1.8：
Ontologies / 2：
Definitions / 2.1：
What Do Ontologies Look Like? / 2.1.2：
Why Ontologies? / 2.1.3：
Key Application Areas / 2.1.4：
Examples / 2.1.5：
Ontological Engineering / 2.2：
Ontology Development Tools / 2.2.1：
Ontology Development Methodologies / 2.2.2：
Applications / 2.3：
Magpie / 2.3.1：
Briefing Associate / 2.3.2：
Quickstep and Foxtrot / 2.3.3：
Advanced Topics / 2.4：
Metadata, Metamodeling, and Ontologies / 2.4.1：
Standard Upper Ontology / 2.4.2：
Ontological Level / 2.4.3：
The Semantic Web / 3：
Rationale / 3.1：
Semantic Web Languages / 3.2：
XML and XML Schema / 3.2.1：
RDF and RDF Schema / 3.2.2：
DAML+OIL / 3.2.3：
OWL / 3.2.4：
SPARQL / 3.2.5：
The Role of Ontologies / 3.3：
Semantic Markup / 3.4：
Semantic Web Services / 3.5：
Open Issues / 3.6：
Quotations / 3.7：
The Model Driven Architecture (MDA) / 4：
Models and Metamodels / 4.1：
Platform-Independent Models / 4.2：
Four-Layer Architecture / 4.3：
The Meta-Object Facility / 4.4：
Specific MDA Metamodels / 4.5：
Unified Modeling Language / 4.5.1：
Common Warehouse Metamodel (CWM) / 4.5.2：
Ontology Definition Metamodel / 4.5.3：
UML Profiles / 4.6：
Examples of UML Profiles / 4.6.1：
An XML for Sharing MDA Artifacts / 4.7：
The Need for Modeling Spaces / 4.8：
Modeling Spaces / 5：
Modeling the Real World / 5.1：
The Real World, Models, and Metamodels / 5.2：
The Essentials of Modeling Spaces / 5.3：
Modeling Spaces Illuminated / 5.4：
A Touch of RDF(S) and MOF Modeling Spaces / 5.5：
A Touch of the Semantic Web and MDA Technical Spaces / 5.6：
Instead of Conclusions / 5.7：
The Model Driven Architecture and Ontologies / Part II：
Software Engineering Approaches to Ontology Development / 6：
A Brief History of Ontology Modeling / 6.1：
Networked Knowledge Representation and Exchange Using UML and RDF / 6.1.1：
Extending the Unified Modeling Language for Ontology Development / 6.1.2：
The Unified Ontology Language / 6.1.3：
UML for the Semantic Web: Transformation-Based Approach / 6.1.4：
The AIFB OWL DL Metamodel / 6.1.5：
The GOOD OLD AI ODM Proposal / 6.1.6：
Ontology Development Tools Based on Software Engineering Techniques / 6.2：
Protege / 6.2.1：
DUET (DAML UML Enhanced Tool) / 6.2.2：
An Ontology Tool for IBM Rational Rose UML Models / 6.2.3：
Visual Ontology Modeler (VOM) / 6.2.4：
Summary of Relations Between UML and Ontologies / 6.3：
Summary of Approaches and Tools for Software Engineering-Based Ontology Development / 6.3.1：
Summary of Differences Between UML and Ontology Languages / 6.3.2：
Future Development / 6.3.3：
The MDA-Based Ontology Infrastructure / 7：
Motivation / 7.1：
Overview / 7.2：
Bridging RDF(S) and MOF / 7.3：
Design Rationale for the Ontology UML Profile / 7.4：
The Ontology Definition Metamodel (ODM) / 8：
ODM Metamodels / 8.1：
A Few Issues Regarding the Revised Joint Submission / 8.2：
The Resource Description Framework Schema (RDFS) metamodel / 8.3：
The Web Ontology Language (OWL) Metamodel / 8.4：
The Ontology UML Profile / 9：
Classes and Individuals in Ontologies / 9.1：
Properties of Ontologies / 9.2：
Statements / 9.3：
Different Versions of the Ontology UML Profile / 9.4：
Mappings of MDA-Based Languages and Ontologies / 10：
Relations Between Modeling Spaces / 10.1：
Transformations Between Modeling Spaces / 10.2：
Example of an Implementation: an XSLT-Based Approach / 10.3：
Implementation Details / 10.3.1：
Transformation Example / 10.3.2：
Practical Experience / 10.3.3：
Discussion / 10.3.4：
Using UML Tools for Ontology Modeling / Part III：
MagicDraw / 11.1：
Starting with MagicDraw / 11.1.1：
Things You Should Know when Working with UML Profiles / 11.1.2：
Creating a New Ontology / 11.1.3：
Working with Ontology Classes / 11.1.4：
Working with Ontology Properties / 11.1.5：
Working with Individuals / 11.1.6：
Working with Statements / 11.1.7：
Poseidon for UML / 11.2：
Modeling Ontology Classes in Poseidon / 11.2.1：
Modeling Ontology Individuals and Statements in Poseidon / 11.2.2：
Sharing UML Models Between UML tools and Protege Using the UML Back End / 11.3：
An MDA Based Ontology Platform: AIR / 12：
The Basic Idea / 12.1：
Metamodel - the Conceptual Building Block of AIR / 12.3：
The AIR Metadata Repository / 12.4：
The AIR Workbench / 12.5：
The Role of XML Technologies / 12.6：
Possibilities / 12.7：
Examples of Ontology / 13：
Petri Net Ontology / 13.1：
Organization of the Petri Net Ontology / 13.1.1：
The Core Petri Net Ontology in the Ontology UML Profile / 13.1.2：
Example of an Extension: Upgraded Petri Nets / 13.1.3：
Educational Ontologies / 13.2：
Conceptual Solution / 13.2.1：
Mapping the Conceptual Model to Ontologies / 13.2.2：
References
Index
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
20.

電子ブック
ＥＢ
20. Rationale-Based Software Engineering
Janet E.; Carroll, John M.; Mistr?k, Ivan Burge, Janet E. Burge, John M. Carroll
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Introduction / Part 1：
What is Rationale and Why Does It Matter? / 1：
The Scope and Value of Rationale in Software Engineering / 1.1：
Objectives of This Chapter / 1.1.2：
A Rough Sketch of Research on Rationale / 1.2：
Argumentative Approaches to Rationale / 1.2.1：
Rationale Methods That Go Beyond Argumentation / 1.2.2：
Why Rationale Matters / 1.3：
The Usefulness of Rationale for Artifact Creation / 1.3.1：
The Usefulness of Rationale for Software Engineering / 1.3.2：
Summary and Conclusions / 1.4：
What Makes Software Different / 2：
Rationale for Software Artifacts versus Rationale for Physical ARtifacts / 2.1：
The Roles of the Computer / 2.1.2：
Comparison of the Roles of the Computer in the Lifecycles of Physical and Software Artifacts / 2.2.1：
The Significance for Rationale Management in Software Engineering / 2.2.2：
Iteration in Development / 2.3：
The Role of Iteration in Different Types of Development / 2.3.1：
Implications of Iteration for Rationale Management in Software Engineering / 2.3.2：
Summary and Conclusion / 2.4：
Rationale and Software Engineering / 3：
Software Engineering / 3.1：
Software Engineering Rationale / 3.1.2：
Rationale and the Software Process / 3.1.3：
Software Process Definition and Implementation / 3.2.1：
Rationale and SE Process Decision-Making / 3.2.2：
Rationale and Project Management / 3.3：
Rationale and Software Development / 3.4：
Why Capture Software Engineering Rationale? / 3.4.1：
What are the Uses of Software Engineering Rationale? / 3.4.2：
When can Software Engineering Rationale be Used in Software Development? / 3.4.3：
How Can We Support Software Engineering Rationale Use in Software Development? / 3.4.4：
Learning from Rationale Research in Other Domains / 3.5：
Research on Rationale in other Domains / 4.1：
Domain-Oriented Design Environments Using PHI / 4.1.2：
PHIDIAS and JANUS / 4.2.1：
Discussion / 4.2.2：
Automating the Capture of Design Rationale with CAD / 4.3：
The Rationale Capture Problem / 4.3.1：
Solution Approach: Automating the Capture of Rationale / 4.3.2：
Implementation: The Rationale Construction Framework / 4.3.3：
Parameter Dependency Networks as Design Rationale / 4.3.4：
The DRIVE System and Parameter Dependency Networks / 4.4.1：
Case-Based Reasoning as Design Rationale / 4.4.2：
From Automated Case-Based Reasoning to Case-Based Design Aids / 4.5.1：
Decision-Making in Software Engineering / 4.5.2：
General / 5.1：
Objectives of this Chapter
Decision-Making Problems / 5.2：
Where Decisions Go Wrong / 5.2.1：
Poor Decisions in Software / 5.2.2：
Naturalistic Decision-Making / 5.3：
Background / 5.3.1：
The Recognition-Primed Decision Model / 5.3.2：
Rationale as a Resource for Decision-Making / 5.4：
Classical Decision-Making / 5.4.1：
Naturalistic Decision-making / 5.4.2：
Uses for Rationale / 5.5：
Presentation of Rationale / 6：
Codifying Rationale Semiformally / 6.1：
The rationale for rationale notations / 6.2.1：
Hypermedia Presentations of Rationale / 6.2.2：
Using Semiformal Rationales / 6.2.3：
Codifying Rationale Informally / 6.3：
Directions / 6.4：
Reusable Rationale Databases / 6.4.1：
Multi-Scale Presentations of Rationale / 6.4.2：
Integrated Presentation / 6.4.3：
Evaluation / 6.5：
Argumentation-Based Rationale / 7.1：
Scenario-Based Rationale / 7.1.2：
Evaluating the Rationale / 7.1.3：
Completeness / 7.2.1：
Correctness / 7.2.2：
Evaluating the Decisions / 7.3：
Comparing Alternatives / 7.3.1：
Combining Inputs from Multiple Developers / 7.3.2：
Handling Uncertainty / 7.3.3：
Scenario-Based Evaluation / 7.4：
Support for Collaboration / 7.5：
Software Development as Collaborative Work / 8.1：
Collaboration Is Inescapable / 8.2.1：
Collaboration Entrains Challenges / 8.2.2：
Collaboration Supports Rationale / 8.3：
Collaboration Externalizes Rationales / 8.3.1：
Software Development Communities of Practice / 8.3.2：
Rationale Supports Collaboration / 8.4：
Awareness / 8.4.1：
Coordination / 8.4.2：
Change Analysis / 8.5：
Issues with Change in Software Development / 9.1：
Types of Software Changes / 9.1.2：
Functional Requirement Change / 9.2.1：
Nonfunctional Requirement Change / 9.2.2：
Changing Assumptions / 9.2.3：
Structural Changes / 9.2.4：
Defect Correction / 9.2.5：
Change Impact Assessment / 9.3：
Consistency Management / 9.4：
Rationale and the Software Lifecycle / 9.5：
Software Engineering Process / 10.1：
Development Activities and Rationale / 10.1.2：
Project Planning and Management / 10.2.1：
Requirements / 10.2.2：
Design / 10.2.3：
Implementation / 10.2.4：
Verification and Validation / 10.2.5：
Maintenance / 10.2.6：
Retirement / 10.2.7：
Software Lifecycle Models / 10.3：
Sequential Models / 10.3.1：
Iterative Models / 10.3.2：
Other Models / 10.3.3：
Software Process Improvement / 10.4：
CMM / 10.4.1：
Personal Software Process / 10.4.2：
Rationale and Requirements Engineering / 10.5：
Requirements Engineering / 11.1：
Obtaining Requirements / 11.1.2：
Requirements Elicitation / 11.2.1：
Achieving Consensus / 11.2.2：
Requirements Inconsistency / 11.2.3：
Requirements Prioritization / 11.2.4：
Requirements Traceability / 11.3：
Rationale and Nonfunctional Requirements / 11.4：
Nonfunctional Requirement Categorization / 11.4.1：
The NFR Framework / 11.4.2：
SEURAT Argument Ontology and NFR Prioritization / 11.4.3：
NFRs and Conflict Representation and Detection / 11.4.4：
Goal-Based Requirements Engineering / 11.5：
Goal-Based Requirements Analysis / 11.5.1：
Goal-Oriented Requirements Engineering / 11.5.2：
Relationship to Rationale / 11.5.3：
Adapting to Changing Requirements / 11.6：
Rationale and Software Design / 11.7：
The Nature and Importance of Software Design Rationale / 12.1：
Relating Rationale Approaches to Software Design Processes / 12.1.2：
Decision-centric and Usage-centric Rationale Approaches / 12.2.1：
Prescriptive and Descriptive Roles of Rationale Approaches / 12.2.2：
Rationale for Design Space Analysis and Deeper Reflection / 12.2.3：
Specific Approaches that Integrate Rationale into Software Design / 12.3：
Rationale and Software Architecture / 12.3.1：
Strategies for Fitting Rationale into Architectural Design Processes / 12.3.2：
Rationale and Software Verification, Validation, and Testing / 12.4：
Verification, Validation, and Testing / 13.1：
Software Testing Issues / 13.1.2：
Types of Software VV&T / 13.1.3：
Inspection / 13.2.1：
Unit Testing / 13.2.2：
Integration Testing / 13.2.3：
System Testing / 13.2.4：
Rationale Support for Software VV&T / 13.3：
Rationale and Testability / 13.3.1：
Rationale and Test Case Prioritization / 13.3.2：
Rationale, Testing, and Component Selection / 13.3.3：
Software Testing Rationale / 13.4：
Testing Rationale / 13.4.1：
Uses for Testing Rationale / 13.4.2：
Rationale and Software Maintenance / 13.5：
Software Maintenance and Evolution / 14.1：
Types of Software Maintenance / 14.1.2：
Improving Maintainability / 14.3：
Designing for Maintenance / 14.3.1：
System Reengineering / 14.3.2：
Software Maintenance Support / 14.4：
Maintenance Prediction / 14.4.1：
Impact Assessment / 14.4.2：
Program Comprehension / 14.4.3：
Maintenance Recovery / 14.4.4：
Maintenance Rationale / 14.4.5：
Rationale and Software Reuse / 14.5：
Software Reuse / 15.1：
Reuse: Concepts and Categories / 15.1.2：
Types of Reuse / 15.2.1：
Types of Rationale for Reuse / 15.2.2：
Reusable Rationale / 15.2.3：
Applying Rationale / 15.3：
Rationale and Patterns / 15.3.1：
Rationale and Component-Based Software Engineering / 15.3.2：
Rationale and Software Product Lines / 15.3.3：
Rationale and COTS-Based Software Engineering / 15.3.4：
Frameworks for Rationale-Based Software Engineering / 15.4：
A Conceptual Framework / 16：
What a Conceptual Framework Should Do / 16.1：
General Goals of Rationale Usage in Software Engineering / 16.1.2：
Rationale: Types of Approaches, Specific Approaches, and Methods / 16.3：
Decision-centric Rationale in Software Engineering / 16.4：
Decision-Making in Rationale Approaches / 16.4.1：
Question Answering in Software Engineering / 16.4.2：
Using Decision-centric Rationale in the Full Spectrum of SER / 16.4.3：
Usage-centric Rationale in Software Engineering / 16.5：
Rationale and Iterative Software Development / 16.6：
A Rationale-Based Account of Iterative Development / 16.6.1：
Principles for Rationale Approaches to Support Iterative Development / 16.6.2：
Supporting Iterative Development by Combining Decision-centric and Usage-centric Rationale / 16.6.3：
Challenges to Rationale Usage / 16.7：
Solving the Capture Problem / 16.7.1：
Solving the Delivery Problem / 16.7.2：
An Architectural Framework / 16.8：
An Integrative Architecture for Rationale-Based Software Engineering / 17.1：
The Need for an Integrative Approach to Rationale Management / 17.1.2：
Representing and Integrating All Types of Software Engineering Rationale / 17.2.1：
Alleviating the Capture and Delivery Problems / 17.2.2：
Framework of an Integrative Architecture for Rationale Management in Software Engineering / 17.3：
An Overview of the Framework / 17.3.1：
Workings of the Rational Management System / 17.3.2：
Integration with External Systems / 17.3.3：
Rationale-Based Software Engineering: Summary and Prospect / 17.4：
Rationale as an Aid to Software Engineering / 18.1：
Summary of the Book / 18.1.2：
The Challenges of Future Software Development / 18.3：
Managing Change / 18.3.1：
Managing the Increasing Scale, Complexity, and Longevity of Software Projects / 18.3.2：
The Promise of Rationale-Based Software Engineering / 18.4：
Rationale and the Management of Change / 18.4.1：
Using Rationale to Manage the Increasing Scale, Complexity, and Longevity of Software Projects / 18.4.2：
Challenges for Rationale-Based Software Engineering / 18.5：
Addressing the Capture Problem / 18.5.1：
Addressing the Delivery Problem / 18.5.2：
Bibliography / 18.6：
Glossary
Index
Introduction / Part 1：
What is Rationale and Why Does It Matter? / 1：
The Scope and Value of Rationale in Software Engineering / 1.1：
21.

電子ブック
ＥＢ
21. Rationale-Based Software Engineering
Janet E.; Carroll, John M.; Mistrík, Ivan Burge, Janet E. Burge, John M. Carroll, Raymond McCall, Ivan Mistrík
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Introduction / Part 1：
What is Rationale and Why Does It Matter? / 1：
The Scope and Value of Rationale in Software Engineering / 1.1：
Objectives of This Chapter / 1.1.2：
A Rough Sketch of Research on Rationale / 1.2：
Argumentative Approaches to Rationale / 1.2.1：
Rationale Methods That Go Beyond Argumentation / 1.2.2：
Why Rationale Matters / 1.3：
The Usefulness of Rationale for Artifact Creation / 1.3.1：
The Usefulness of Rationale for Software Engineering / 1.3.2：
Summary and Conclusions / 1.4：
What Makes Software Different / 2：
Rationale for Software Artifacts versus Rationale for Physical ARtifacts / 2.1：
The Roles of the Computer / 2.1.2：
Comparison of the Roles of the Computer in the Lifecycles of Physical and Software Artifacts / 2.2.1：
The Significance for Rationale Management in Software Engineering / 2.2.2：
Iteration in Development / 2.3：
The Role of Iteration in Different Types of Development / 2.3.1：
Implications of Iteration for Rationale Management in Software Engineering / 2.3.2：
Summary and Conclusion / 2.4：
Rationale and Software Engineering / 3：
Software Engineering / 3.1：
Software Engineering Rationale / 3.1.2：
Rationale and the Software Process / 3.1.3：
Software Process Definition and Implementation / 3.2.1：
Rationale and SE Process Decision-Making / 3.2.2：
Rationale and Project Management / 3.3：
Rationale and Software Development / 3.4：
Why Capture Software Engineering Rationale? / 3.4.1：
What are the Uses of Software Engineering Rationale? / 3.4.2：
When can Software Engineering Rationale be Used in Software Development? / 3.4.3：
How Can We Support Software Engineering Rationale Use in Software Development? / 3.4.4：
Learning from Rationale Research in Other Domains / 3.5：
Research on Rationale in other Domains / 4.1：
Domain-Oriented Design Environments Using PHI / 4.1.2：
PHIDIAS and JANUS / 4.2.1：
Discussion / 4.2.2：
Automating the Capture of Design Rationale with CAD / 4.3：
The Rationale Capture Problem / 4.3.1：
Solution Approach: Automating the Capture of Rationale / 4.3.2：
Implementation: The Rationale Construction Framework / 4.3.3：
Parameter Dependency Networks as Design Rationale / 4.3.4：
The DRIVE System and Parameter Dependency Networks / 4.4.1：
Case-Based Reasoning as Design Rationale / 4.4.2：
From Automated Case-Based Reasoning to Case-Based Design Aids / 4.5.1：
Decision-Making in Software Engineering / 4.5.2：
General / 5.1：
Objectives of this Chapter
Decision-Making Problems / 5.2：
Where Decisions Go Wrong / 5.2.1：
Poor Decisions in Software / 5.2.2：
Naturalistic Decision-Making / 5.3：
Background / 5.3.1：
The Recognition-Primed Decision Model / 5.3.2：
Rationale as a Resource for Decision-Making / 5.4：
Classical Decision-Making / 5.4.1：
Naturalistic Decision-making / 5.4.2：
Uses for Rationale / 5.5：
Presentation of Rationale / 6：
Codifying Rationale Semiformally / 6.1：
The rationale for rationale notations / 6.2.1：
Hypermedia Presentations of Rationale / 6.2.2：
Using Semiformal Rationales / 6.2.3：
Codifying Rationale Informally / 6.3：
Directions / 6.4：
Reusable Rationale Databases / 6.4.1：
Multi-Scale Presentations of Rationale / 6.4.2：
Integrated Presentation / 6.4.3：
Evaluation / 6.5：
Argumentation-Based Rationale / 7.1：
Scenario-Based Rationale / 7.1.2：
Evaluating the Rationale / 7.1.3：
Completeness / 7.2.1：
Correctness / 7.2.2：
Evaluating the Decisions / 7.3：
Comparing Alternatives / 7.3.1：
Combining Inputs from Multiple Developers / 7.3.2：
Handling Uncertainty / 7.3.3：
Scenario-Based Evaluation / 7.4：
Support for Collaboration / 7.5：
Software Development as Collaborative Work / 8.1：
Collaboration Is Inescapable / 8.2.1：
Collaboration Entrains Challenges / 8.2.2：
Collaboration Supports Rationale / 8.3：
Collaboration Externalizes Rationales / 8.3.1：
Software Development Communities of Practice / 8.3.2：
Rationale Supports Collaboration / 8.4：
Awareness / 8.4.1：
Coordination / 8.4.2：
Change Analysis / 8.5：
Issues with Change in Software Development / 9.1：
Types of Software Changes / 9.1.2：
Functional Requirement Change / 9.2.1：
Nonfunctional Requirement Change / 9.2.2：
Changing Assumptions / 9.2.3：
Structural Changes / 9.2.4：
Defect Correction / 9.2.5：
Change Impact Assessment / 9.3：
Consistency Management / 9.4：
Rationale and the Software Lifecycle / 9.5：
Software Engineering Process / 10.1：
Development Activities and Rationale / 10.1.2：
Project Planning and Management / 10.2.1：
Requirements / 10.2.2：
Design / 10.2.3：
Implementation / 10.2.4：
Verification and Validation / 10.2.5：
Maintenance / 10.2.6：
Retirement / 10.2.7：
Software Lifecycle Models / 10.3：
Sequential Models / 10.3.1：
Iterative Models / 10.3.2：
Other Models / 10.3.3：
Software Process Improvement / 10.4：
CMM / 10.4.1：
Personal Software Process / 10.4.2：
Rationale and Requirements Engineering / 10.5：
Requirements Engineering / 11.1：
Obtaining Requirements / 11.1.2：
Requirements Elicitation / 11.2.1：
Achieving Consensus / 11.2.2：
Requirements Inconsistency / 11.2.3：
Requirements Prioritization / 11.2.4：
Requirements Traceability / 11.3：
Rationale and Nonfunctional Requirements / 11.4：
Nonfunctional Requirement Categorization / 11.4.1：
The NFR Framework / 11.4.2：
SEURAT Argument Ontology and NFR Prioritization / 11.4.3：
NFRs and Conflict Representation and Detection / 11.4.4：
Goal-Based Requirements Engineering / 11.5：
Goal-Based Requirements Analysis / 11.5.1：
Goal-Oriented Requirements Engineering / 11.5.2：
Relationship to Rationale / 11.5.3：
Adapting to Changing Requirements / 11.6：
Rationale and Software Design / 11.7：
The Nature and Importance of Software Design Rationale / 12.1：
Relating Rationale Approaches to Software Design Processes / 12.1.2：
Decision-centric and Usage-centric Rationale Approaches / 12.2.1：
Prescriptive and Descriptive Roles of Rationale Approaches / 12.2.2：
Rationale for Design Space Analysis and Deeper Reflection / 12.2.3：
Specific Approaches that Integrate Rationale into Software Design / 12.3：
Rationale and Software Architecture / 12.3.1：
Strategies for Fitting Rationale into Architectural Design Processes / 12.3.2：
Rationale and Software Verification, Validation, and Testing / 12.4：
Verification, Validation, and Testing / 13.1：
Software Testing Issues / 13.1.2：
Types of Software VV&T / 13.1.3：
Inspection / 13.2.1：
Unit Testing / 13.2.2：
Integration Testing / 13.2.3：
System Testing / 13.2.4：
Rationale Support for Software VV&T / 13.3：
Rationale and Testability / 13.3.1：
Rationale and Test Case Prioritization / 13.3.2：
Rationale, Testing, and Component Selection / 13.3.3：
Software Testing Rationale / 13.4：
Testing Rationale / 13.4.1：
Uses for Testing Rationale / 13.4.2：
Rationale and Software Maintenance / 13.5：
Software Maintenance and Evolution / 14.1：
Types of Software Maintenance / 14.1.2：
Improving Maintainability / 14.3：
Designing for Maintenance / 14.3.1：
System Reengineering / 14.3.2：
Software Maintenance Support / 14.4：
Maintenance Prediction / 14.4.1：
Impact Assessment / 14.4.2：
Program Comprehension / 14.4.3：
Maintenance Recovery / 14.4.4：
Maintenance Rationale / 14.4.5：
Rationale and Software Reuse / 14.5：
Software Reuse / 15.1：
Reuse: Concepts and Categories / 15.1.2：
Types of Reuse / 15.2.1：
Types of Rationale for Reuse / 15.2.2：
Reusable Rationale / 15.2.3：
Applying Rationale / 15.3：
Rationale and Patterns / 15.3.1：
Rationale and Component-Based Software Engineering / 15.3.2：
Rationale and Software Product Lines / 15.3.3：
Rationale and COTS-Based Software Engineering / 15.3.4：
Frameworks for Rationale-Based Software Engineering / 15.4：
A Conceptual Framework / 16：
What a Conceptual Framework Should Do / 16.1：
General Goals of Rationale Usage in Software Engineering / 16.1.2：
Rationale: Types of Approaches, Specific Approaches, and Methods / 16.3：
Decision-centric Rationale in Software Engineering / 16.4：
Decision-Making in Rationale Approaches / 16.4.1：
Question Answering in Software Engineering / 16.4.2：
Using Decision-centric Rationale in the Full Spectrum of SER / 16.4.3：
Usage-centric Rationale in Software Engineering / 16.5：
Rationale and Iterative Software Development / 16.6：
A Rationale-Based Account of Iterative Development / 16.6.1：
Principles for Rationale Approaches to Support Iterative Development / 16.6.2：
Supporting Iterative Development by Combining Decision-centric and Usage-centric Rationale / 16.6.3：
Challenges to Rationale Usage / 16.7：
Solving the Capture Problem / 16.7.1：
Solving the Delivery Problem / 16.7.2：
An Architectural Framework / 16.8：
An Integrative Architecture for Rationale-Based Software Engineering / 17.1：
The Need for an Integrative Approach to Rationale Management / 17.1.2：
Representing and Integrating All Types of Software Engineering Rationale / 17.2.1：
Alleviating the Capture and Delivery Problems / 17.2.2：
Framework of an Integrative Architecture for Rationale Management in Software Engineering / 17.3：
An Overview of the Framework / 17.3.1：
Workings of the Rational Management System / 17.3.2：
Integration with External Systems / 17.3.3：
Rationale-Based Software Engineering: Summary and Prospect / 17.4：
Rationale as an Aid to Software Engineering / 18.1：
Summary of the Book / 18.1.2：
The Challenges of Future Software Development / 18.3：
Managing Change / 18.3.1：
Managing the Increasing Scale, Complexity, and Longevity of Software Projects / 18.3.2：
The Promise of Rationale-Based Software Engineering / 18.4：
Rationale and the Management of Change / 18.4.1：
Using Rationale to Manage the Increasing Scale, Complexity, and Longevity of Software Projects / 18.4.2：
Challenges for Rationale-Based Software Engineering / 18.5：
Addressing the Capture Problem / 18.5.1：
Addressing the Delivery Problem / 18.5.2：
Bibliography / 18.6：
Glossary
Index
Introduction / Part 1：
What is Rationale and Why Does It Matter? / 1：
The Scope and Value of Rationale in Software Engineering / 1.1：
22.

電子ブック
ＥＢ
22. A Process Algebraic Approach to Software Architecture Design
Alessandro Aldini, Marco Bernardo, Flavio Corradini
出版情報: Springer eBooks Computer Science , Springer London, 2010
所蔵情報: loading…
目次情報: 続きを見る
Process Calculi and Behavioral Equivalences / Part 1：
Process Algebra / 1：
Concurrency, Communication, and Nondeterminism / 1.1：
Running Example: Producer-Consumer System / 1.2：
PC: Process Calculus for Nondeterministic Processes / 1.3：
Syntax: Actions and Behavioral Operators / 1.3.1：
Semantics: Structural Operational Rules / 1.3.2：
Bisimulation Equivalence / 1.4：
Equivalence Relations and Preorders / 1.4.1：
Definition of the Behavioral Equivalence / 1.4.2：
Conditions and Characterizations / 1.4.3：
Congruence Property / 1.4.4：
Sound and Complete Axiomatization / 1.4.5：
Modal Logic Characterization / 1.4.6：
Verification Algorithm / 1.4.7：
Abstracting from Invisible Actions / 1.4.8：
Testing Equivalence / 1.5：
Trace Equivalence / 1.5.1：
The Linear-Time/Branching-Time Spectrum / 1.6.1：
Deterministically Timed Process Algebra / 2：
Concurrency, Communication, and Deterministic Time / 2.1：
Deterministically Timed Process Calculi / 2.2：
TPC: Timed Process Calculus with Durationless Actions / 2.2.1：
DPC: Timed Process Calculus with Durational Actions / 2.2.2：
Deterministically Timed Behavioral Equivalences / 2.3：
Definition of Timed Bisimulation Equivalence / 2.3.1：
Durational Bisimulation Equivalence and its Properties / 2.3.2：
Semantics-Preserving Mapping for Eagerness / 2.4：
Differences Between TPC and DPC / 2.4.1：
From DPC to TPC Under Eagerness / 2.4.2：
Semantics-Preserving Mapping for Laziness / 2.5：
Lazy TPC / 2.5.1：
Lazy DPC / 2.5.2：
From DPC to TPC Under Laziness / 2.5.3：
Semantics-Preserving Mapping for Maximal Progress / 2.6：
Maximal Progress TPC / 2.6.1：
Maximal Progress DPC / 2.6.2：
From DPC to TPC Under Maximal Progress / 2.6.3：
Expressiveness of Eagerness, Laziness, Maximal Progress / 2.7：
Synchronization Issues / 2.7.1：
Choosing at Different Times / 2.7.2：
Performing Infinitely Many Actions at the Same Time / 2.7.3：
Performing Finitely Many Actions at the Same Time / 2.7.4：
Coincidence Result for Sequential Processes / 2.7.5：
Stochastically Timed Process Algebra / 3：
Concurrency, Communication, and Stochastic Time / 3.1：
MPC: Markovian Process Calculus with Durational Actions / 3.2：
Markov Chains / 3.2.1：
Syntax and Semantics / 3.2.2：
Markovian Bisimulation Equivalence / 3.3：
Exit Rates and Exit Probabilities / 3.3.1：
Abstracting from Invisible Actions with Zero Duration / 3.3.2：
Markovian Testing Equivalence / 3.4：
Probability and Duration of Computations / 3.4.1：
Markovian Trace Equivalence / 3.4.2：
Exactness of Markovian Behavioral Equivalences / 3.5.1：
The Markovian Linear-Time/Branching-Time Spectrum / 3.7：
Process Algebra for Software Architecture / Part II：
Component-Oriented Modeling / 4：
Software Architecture Description Languages / 4.1：
Running Example: Client-Server System / 4.2：
Architectural Upgrade of Process Algebra: Guidelines / 4.3：
G1: Separating Behavior and Topology Descriptions / 4.3.1：
G2: Reusing Component and Connector Specification / 4.3.2：
G3: Eliciting Component and Connector Interface / 4.3.3：
G4: Classifying Communication Synchronicity / 4.3.4：
G5: Classifying Communication Multiplicity / 4.3.5：
G6: Textual and Graphical Notations (PADL Syntax) / 4.3.6：
G7: Dynamic and Static Operators / 4.3.7：
Translation Semantics for PADL / 4.4：
Semantics of Individual Elements / 4.4.1：
Semantics of Interacting Elements / 4.4.2：
Summarizing Example: Pipe-Filter System / 4.5：
G8: Supporting Architectural Styles / 4.6：
Architectural Types / 4.6.1：
Hierarchical Modeling / 4.6.2：
Behavioral Conformity / 4.6.3：
Exogenous Variations / 4.6.4：
Endogenous Variations / 4.6.5：
Multiplicity Variations / 4.6.6：
Comparisons / 4.7：
Comparison with Process Algebra / 4.7.1：
Comparison with Parallel Composition Operators / 4.7.2：
Comparison with Other Software Architecture Languages / 4.7.3：
Component-Oriented Functional Verification / 5：
Mismdet: Architecture-Level Mismatch Detection / 5.1：
Class of Properties and Detection Strategy / 5.2：
Architectural Compatibility of Star-Shaped Topologies / 5.3：
Case Study: Compressing Proxy System / 5.3.1：
Architectural Interoperability of Cycle-Shaped Topologies / 5.4：
Case Study: Cruise Control System / 5.4.1：
Generalization to Arbitrary Topologies / 5.5：
Case Study: Simulator for the Cruise Control System / 5.5.1：
Generalization to Architectural Types / 5.6：
Generalization to Internal Behavioral Variations / 5.6.1：
Generalization to Exogenous Variations / 5.6.2：
Generalization to Endogenous Variations / 5.6.3：
Generalization to Multiplicity Variations / 5.6.4：
Component-Oriented Performance Evaluation / 5.7：
Perfsel: Performance-Driven Architectural Selection / 6.1：
Class of Measures and Selection Strategy / 6.2：
Emilia: Extending PADL with Performance Aspects / 6.3：
Queueing Systems and Queueing Networks / 6.4：
From ÆEmilia Descriptions to Queueing Networks / 6.5：
General Syntactical Restrictions / 6.5.1：
Queueing Network Basic Elements / 6.5.2：
Documental Functions / 6.5.3：
Characterizing Functions / 6.5.4：
Case Study: Selecting Compiler Architectures / 6.6：
Sequential Architecture / 6.6.1：
Pipeline Architecture / 6.6.2：
Concurrent Architecture / 6.6.3：
Scenario-Based Performance Selection / 6.6.4：
Trading Dependability and Performance / 6.7：
DepPerf: Mixed View of Dependability and Performance / 7.1：
Running Example: Multilevel Security Routing System / 7.2：
First Phase of DepPerf: Noninterference Analysis / 7.3：
Noninterference Theory / 7.3.1：
Noninterference Verification / 7.3.2：
Component-Oriented Noninterference Check / 7.3.3：
Interpretation and Feedback / 7.3.4：
Second Phase of DepPerf: Performance Evaluation / 7.4：
Model Validation / 7.4.1：
Analysis and Tuning / 7.4.2：
Measure Specification Language / 7.4.3：
Case Study I: The Network NRL Pump / 7.5：
Informal Specification / 7.5.1：
Architectural Description / 7.5.2：
Noninterference Analysis / 7.5.3：
Performance Evaluation / 7.5.4：
Case Study II: Power-Manageable System / 7.6：
References / 7.6.1：
Index
Process Calculi and Behavioral Equivalences / Part 1：
Process Algebra / 1：
Concurrency, Communication, and Nondeterminism / 1.1：
23.

電子ブック
ＥＢ
23. A Process Algebraic Approach to Software Architecture Design
Alessandro Aldini, Marco Bernardo, Flavio Corradini
出版情報: SpringerLink Books - AutoHoldings , Springer London, 2010
所蔵情報: loading…
目次情報: 続きを見る
Process Calculi and Behavioral Equivalences / Part 1：
Process Algebra / 1：
Concurrency, Communication, and Nondeterminism / 1.1：
Running Example: Producer-Consumer System / 1.2：
PC: Process Calculus for Nondeterministic Processes / 1.3：
Syntax: Actions and Behavioral Operators / 1.3.1：
Semantics: Structural Operational Rules / 1.3.2：
Bisimulation Equivalence / 1.4：
Equivalence Relations and Preorders / 1.4.1：
Definition of the Behavioral Equivalence / 1.4.2：
Conditions and Characterizations / 1.4.3：
Congruence Property / 1.4.4：
Sound and Complete Axiomatization / 1.4.5：
Modal Logic Characterization / 1.4.6：
Verification Algorithm / 1.4.7：
Abstracting from Invisible Actions / 1.4.8：
Testing Equivalence / 1.5：
Trace Equivalence / 1.5.1：
The Linear-Time/Branching-Time Spectrum / 1.6.1：
Deterministically Timed Process Algebra / 2：
Concurrency, Communication, and Deterministic Time / 2.1：
Deterministically Timed Process Calculi / 2.2：
TPC: Timed Process Calculus with Durationless Actions / 2.2.1：
DPC: Timed Process Calculus with Durational Actions / 2.2.2：
Deterministically Timed Behavioral Equivalences / 2.3：
Definition of Timed Bisimulation Equivalence / 2.3.1：
Durational Bisimulation Equivalence and its Properties / 2.3.2：
Semantics-Preserving Mapping for Eagerness / 2.4：
Differences Between TPC and DPC / 2.4.1：
From DPC to TPC Under Eagerness / 2.4.2：
Semantics-Preserving Mapping for Laziness / 2.5：
Lazy TPC / 2.5.1：
Lazy DPC / 2.5.2：
From DPC to TPC Under Laziness / 2.5.3：
Semantics-Preserving Mapping for Maximal Progress / 2.6：
Maximal Progress TPC / 2.6.1：
Maximal Progress DPC / 2.6.2：
From DPC to TPC Under Maximal Progress / 2.6.3：
Expressiveness of Eagerness, Laziness, Maximal Progress / 2.7：
Synchronization Issues / 2.7.1：
Choosing at Different Times / 2.7.2：
Performing Infinitely Many Actions at the Same Time / 2.7.3：
Performing Finitely Many Actions at the Same Time / 2.7.4：
Coincidence Result for Sequential Processes / 2.7.5：
Stochastically Timed Process Algebra / 3：
Concurrency, Communication, and Stochastic Time / 3.1：
MPC: Markovian Process Calculus with Durational Actions / 3.2：
Markov Chains / 3.2.1：
Syntax and Semantics / 3.2.2：
Markovian Bisimulation Equivalence / 3.3：
Exit Rates and Exit Probabilities / 3.3.1：
Abstracting from Invisible Actions with Zero Duration / 3.3.2：
Markovian Testing Equivalence / 3.4：
Probability and Duration of Computations / 3.4.1：
Markovian Trace Equivalence / 3.4.2：
Exactness of Markovian Behavioral Equivalences / 3.5.1：
The Markovian Linear-Time/Branching-Time Spectrum / 3.7：
Process Algebra for Software Architecture / Part II：
Component-Oriented Modeling / 4：
Software Architecture Description Languages / 4.1：
Running Example: Client-Server System / 4.2：
Architectural Upgrade of Process Algebra: Guidelines / 4.3：
G1: Separating Behavior and Topology Descriptions / 4.3.1：
G2: Reusing Component and Connector Specification / 4.3.2：
G3: Eliciting Component and Connector Interface / 4.3.3：
G4: Classifying Communication Synchronicity / 4.3.4：
G5: Classifying Communication Multiplicity / 4.3.5：
G6: Textual and Graphical Notations (PADL Syntax) / 4.3.6：
G7: Dynamic and Static Operators / 4.3.7：
Translation Semantics for PADL / 4.4：
Semantics of Individual Elements / 4.4.1：
Semantics of Interacting Elements / 4.4.2：
Summarizing Example: Pipe-Filter System / 4.5：
G8: Supporting Architectural Styles / 4.6：
Architectural Types / 4.6.1：
Hierarchical Modeling / 4.6.2：
Behavioral Conformity / 4.6.3：
Exogenous Variations / 4.6.4：
Endogenous Variations / 4.6.5：
Multiplicity Variations / 4.6.6：
Comparisons / 4.7：
Comparison with Process Algebra / 4.7.1：
Comparison with Parallel Composition Operators / 4.7.2：
Comparison with Other Software Architecture Languages / 4.7.3：
Component-Oriented Functional Verification / 5：
Mismdet: Architecture-Level Mismatch Detection / 5.1：
Class of Properties and Detection Strategy / 5.2：
Architectural Compatibility of Star-Shaped Topologies / 5.3：
Case Study: Compressing Proxy System / 5.3.1：
Architectural Interoperability of Cycle-Shaped Topologies / 5.4：
Case Study: Cruise Control System / 5.4.1：
Generalization to Arbitrary Topologies / 5.5：
Case Study: Simulator for the Cruise Control System / 5.5.1：
Generalization to Architectural Types / 5.6：
Generalization to Internal Behavioral Variations / 5.6.1：
Generalization to Exogenous Variations / 5.6.2：
Generalization to Endogenous Variations / 5.6.3：
Generalization to Multiplicity Variations / 5.6.4：
Component-Oriented Performance Evaluation / 5.7：
Perfsel: Performance-Driven Architectural Selection / 6.1：
Class of Measures and Selection Strategy / 6.2：
Emilia: Extending PADL with Performance Aspects / 6.3：
Queueing Systems and Queueing Networks / 6.4：
From ÆEmilia Descriptions to Queueing Networks / 6.5：
General Syntactical Restrictions / 6.5.1：
Queueing Network Basic Elements / 6.5.2：
Documental Functions / 6.5.3：
Characterizing Functions / 6.5.4：
Case Study: Selecting Compiler Architectures / 6.6：
Sequential Architecture / 6.6.1：
Pipeline Architecture / 6.6.2：
Concurrent Architecture / 6.6.3：
Scenario-Based Performance Selection / 6.6.4：
Trading Dependability and Performance / 6.7：
DepPerf: Mixed View of Dependability and Performance / 7.1：
Running Example: Multilevel Security Routing System / 7.2：
First Phase of DepPerf: Noninterference Analysis / 7.3：
Noninterference Theory / 7.3.1：
Noninterference Verification / 7.3.2：
Component-Oriented Noninterference Check / 7.3.3：
Interpretation and Feedback / 7.3.4：
Second Phase of DepPerf: Performance Evaluation / 7.4：
Model Validation / 7.4.1：
Analysis and Tuning / 7.4.2：
Measure Specification Language / 7.4.3：
Case Study I: The Network NRL Pump / 7.5：
Informal Specification / 7.5.1：
Architectural Description / 7.5.2：
Noninterference Analysis / 7.5.3：
Performance Evaluation / 7.5.4：
Case Study II: Power-Manageable System / 7.6：
References / 7.6.1：
Index
Process Calculi and Behavioral Equivalences / Part 1：
Process Algebra / 1：
Concurrency, Communication, and Nondeterminism / 1.1：
24.

電子ブック
ＥＢ
24. Software Configuration Management Using Vesta
David Gries, Allan Heydon, Clark Allan Heydon, Fred B. Schneider
出版情報: Springer eBooks Computer Science , Springer US, 2006
所蔵情報: loading…
目次情報: 続きを見る
Preface
Introducing Vesta / Part I：
Introduction / 1：
Some Scenarios / 1.1：
The Configuration Management Challenge / 1.2：
The Vesta Response / 1.3：
Essential Background / 2：
The Unix File System / 2.1：
Naming Files and Directories / 2.1.1：
Mount Points / 2.1.2：
Links / 2.1.3：
Properties of Files / 2.1.4：
Unix Processes / 2.2：
The Unix Shell / 2.3：
The Unix Programming Environment / 2.4：
Make / 2.5：
The Architecture of Vesta / 3：
System Components / 3.1：
Source Management Components / 3.1.1：
Build Components / 3.1.2：
Storage Components / 3.1.3：
Models and Modularity / 3.1.4：
Vesta's Core Properties / 3.2：
The User's View of Vesta / Part II：
Managing Sources and Versions / 4：
Names and Versions / 4.1：
The Source Name Space / 4.1.1：
Versioning / 4.1.2：
Naming Files and Packages / 4.1.3：
The Development Cycle / 4.2：
The Outer Loop / 4.2.1：
The Inner Loop / 4.2.2：
Detailed Operation of the Repository Tools / 4.2.3：
Version Control Alternatives / 4.2.4：
Additional Repository Tools / 4.2.5：
Mutable Files and Directories / 4.2.6：
Replication / 4.3：
Global Name Space / 4.3.1：
A Replication Example / 4.3.2：
The Replicator / 4.3.3：
Cross-Repository Check-out / 4.3.4：
Repository Metadata / 4.4：
Mutable Attributes / 4.4.1：
Access Control / 4.4.2：
Metadata and Replication / 4.4.3：
System Description Language / 5：
Motivation / 5.1：
Language Highlights / 5.2：
The Environment Parameter / 5.2.1：
Bindings / 5.2.2：
Tool Encapsulation / 5.2.3：
Closures / 5.2.4：
Imports / 5.2.5：
Building Systems in Vesta / 6：
The Organization of System Models / 6.1：
Hierarchies of System Models / 6.2：
Bridges and the Standard Environment / 6.2.1：
Library Models / 6.2.2：
Application Models / 6.2.3：
Putting It All Together / 6.2.4：
Control Panel Models / 6.2.5：
Customizing the Build Process / 6.3：
Handling Large Scale Software / 6.4：
Inside Vesta / Part III：
Inside the Repository / 7：
Support for Evaluation and Caching / 7.1：
Derived Files and Shortids / 7.1.1：
Evaluator Directories and Volatile Directories / 7.1.2：
Fingerprints / 7.1.3：
Inside the Repository Implementation / 7.2：
Directory Implementation / 7.2.1：
Shortids and Files / 7.2.2：
Longids / 7.2.3：
Copy-on-Write / 7.2.4：
NFS Interface / 7.2.5：
RPC Interfaces / 7.2.6：
Implementing Replication / 7.3：
Mastership / 7.3.1：
Agreement / 7.3.2：
Agreement-Preserving Primitives / 7.3.3：
Propagating Attributes / 7.3.4：
Incremental Building / 8：
Overview of Function Caching / 8.1：
Caching and Dynamic Dependencies / 8.2：
The Function Cache Interface / 8.3：
Computing Fine-Grained Dependencies / 8.4：
Representing Dependencies / 8.4.1：
Caching External Tool Invocations / 8.4.2：
Caching User-Defined Function Evaluations / 8.4.3：
Caching System Model Evaluations: A Special Case / 8.4.4：
Error Handling / 8.5：
Function Cache Implementation / 8.6：
Cache Lookup / 8.6.1：
Cache Entry Storage / 8.6.2：
Synchronization / 8.6.3：
Evaluation and Caching in Action / 8.7：
Scratch Build of the Standard Environment / 8.7.1：
Scratch Build of the Vesta Umbrella Library / 8.7.2：
Scratch and Incremental Builds of the Evaluator / 8.7.3：
Weeder / 9：
How Deletion is Specified / 9.1：
Implementation of the Weeder / 9.2：
The Function Call Graph / 9.2.1：
Concurrent Weeding / 9.2.2：
Assessing Vesta / Part IV：
Competing Systems / 10：
Loosely Connected Configuration Management Tools / 10.1：
RCS / 10.1.1：
CVS / 10.1.2：
Integrated Configuration Management Systems / 10.1.3：
DSEE / 10.2.1：
ClearCASE / 10.2.2：
Other Systems / 10.3：
Vesta System Performance / 11：
Platform Configuration / 11.1：
Overall System Performance / 11.2：
Performance Comparison with Make / 11.2.1：
Performance Breakdown / 11.2.2：
Caching Analysis / 11.2.3：
Resource Usage / 11.2.4：
Repository Performance / 11.3：
Speed of File Operations / 11.3.1：
Disk and Memory Consumption / 11.3.2：
Speed of Repository Tools / 11.3.3：
Speed of Cross-Repository Tools / 11.3.4：
Speed of the Replicator / 11.3.5：
Function Cache Performance / 11.4：
Server Performance / 11.4.1：
Measurements of the Stable Cache / 11.4.2：
Disk and Memory Usage / 11.4.3：
Function Cache Scalability / 11.4.4：
Weeder Performance / 11.5：
Interprocess Communication / 11.6：
Conclusions / 12：
Vesta in the Real World / 12.1：
Vesta in the Future / 12.2：
SDL Reference Manual / A：
Lexical Conventions / A.1：
Meta-notation / A.2.1：
Terminals / A.2.2：
Semantics / A.3：
Value Space / A.3.1：
Type Declarations / A.3.2：
Evaluation Rules / A.3.3：
Expr / A.3.3.1：
Literal / A.3.3.2：
Id / A.3.3.3：
List / A.3.3.4：
Binding / A.3.3.5：
Select / A.3.3.6：
Block / A.3.3.7：
Stmt / A.3.3.8：
Assign / A.3.3.9：
Iterate / A.3.3.10：
FuncDef / A.3.3.11：
FuncCall / A.3.3.12：
Model / A.3.3.13：
Files / A.3.3.14：
File Name Interpretation / A.3.3.15：
Pragmas / A.3.3.17：
Primitives / A.3.4：
Functions on Type t_bool / A.3.4.1：
Functions on Type t_int / A.3.4.2：
Functions on Type t_text / A.3.4.3：
Functions on Type t_list / A.3.4.4：
Functions on Type t_binding / A.3.4.5：
Special Purpose Functions / A.3.4.6：
Type Manipulation Functions / A.3.4.7：
Tool Invocation Function / A.3.4.8：
Diagnostic Functions / A.3.4.9：
Concrete Syntax / A.4：
Grammar / A.4.1：
Ambiguity Resolution / A.4.2：
Tokens / A.4.3：
Reserved Identifiers / A.4.4：
The Vesta Web Site / B：
References
Index
Preface
Introducing Vesta / Part I：
Introduction / 1：
25.

電子ブック
ＥＢ
25. Software Configuration Management Using Vesta
David Gries, Allan Heydon, Clark Allan Heydon, Fred B. Schneider, Roy Levin, Timothy P. Mann, Yuan Yu
出版情報: SpringerLink Books - AutoHoldings , Springer US, 2006
所蔵情報: loading…
目次情報: 続きを見る
Preface
Introducing Vesta / Part I：
Introduction / 1：
Some Scenarios / 1.1：
The Configuration Management Challenge / 1.2：
The Vesta Response / 1.3：
Essential Background / 2：
The Unix File System / 2.1：
Naming Files and Directories / 2.1.1：
Mount Points / 2.1.2：
Links / 2.1.3：
Properties of Files / 2.1.4：
Unix Processes / 2.2：
The Unix Shell / 2.3：
The Unix Programming Environment / 2.4：
Make / 2.5：
The Architecture of Vesta / 3：
System Components / 3.1：
Source Management Components / 3.1.1：
Build Components / 3.1.2：
Storage Components / 3.1.3：
Models and Modularity / 3.1.4：
Vesta's Core Properties / 3.2：
The User's View of Vesta / Part II：
Managing Sources and Versions / 4：
Names and Versions / 4.1：
The Source Name Space / 4.1.1：
Versioning / 4.1.2：
Naming Files and Packages / 4.1.3：
The Development Cycle / 4.2：
The Outer Loop / 4.2.1：
The Inner Loop / 4.2.2：
Detailed Operation of the Repository Tools / 4.2.3：
Version Control Alternatives / 4.2.4：
Additional Repository Tools / 4.2.5：
Mutable Files and Directories / 4.2.6：
Replication / 4.3：
Global Name Space / 4.3.1：
A Replication Example / 4.3.2：
The Replicator / 4.3.3：
Cross-Repository Check-out / 4.3.4：
Repository Metadata / 4.4：
Mutable Attributes / 4.4.1：
Access Control / 4.4.2：
Metadata and Replication / 4.4.3：
System Description Language / 5：
Motivation / 5.1：
Language Highlights / 5.2：
The Environment Parameter / 5.2.1：
Bindings / 5.2.2：
Tool Encapsulation / 5.2.3：
Closures / 5.2.4：
Imports / 5.2.5：
Building Systems in Vesta / 6：
The Organization of System Models / 6.1：
Hierarchies of System Models / 6.2：
Bridges and the Standard Environment / 6.2.1：
Library Models / 6.2.2：
Application Models / 6.2.3：
Putting It All Together / 6.2.4：
Control Panel Models / 6.2.5：
Customizing the Build Process / 6.3：
Handling Large Scale Software / 6.4：
Inside Vesta / Part III：
Inside the Repository / 7：
Support for Evaluation and Caching / 7.1：
Derived Files and Shortids / 7.1.1：
Evaluator Directories and Volatile Directories / 7.1.2：
Fingerprints / 7.1.3：
Inside the Repository Implementation / 7.2：
Directory Implementation / 7.2.1：
Shortids and Files / 7.2.2：
Longids / 7.2.3：
Copy-on-Write / 7.2.4：
NFS Interface / 7.2.5：
RPC Interfaces / 7.2.6：
Implementing Replication / 7.3：
Mastership / 7.3.1：
Agreement / 7.3.2：
Agreement-Preserving Primitives / 7.3.3：
Propagating Attributes / 7.3.4：
Incremental Building / 8：
Overview of Function Caching / 8.1：
Caching and Dynamic Dependencies / 8.2：
The Function Cache Interface / 8.3：
Computing Fine-Grained Dependencies / 8.4：
Representing Dependencies / 8.4.1：
Caching External Tool Invocations / 8.4.2：
Caching User-Defined Function Evaluations / 8.4.3：
Caching System Model Evaluations: A Special Case / 8.4.4：
Error Handling / 8.5：
Function Cache Implementation / 8.6：
Cache Lookup / 8.6.1：
Cache Entry Storage / 8.6.2：
Synchronization / 8.6.3：
Evaluation and Caching in Action / 8.7：
Scratch Build of the Standard Environment / 8.7.1：
Scratch Build of the Vesta Umbrella Library / 8.7.2：
Scratch and Incremental Builds of the Evaluator / 8.7.3：
Weeder / 9：
How Deletion is Specified / 9.1：
Implementation of the Weeder / 9.2：
The Function Call Graph / 9.2.1：
Concurrent Weeding / 9.2.2：
Assessing Vesta / Part IV：
Competing Systems / 10：
Loosely Connected Configuration Management Tools / 10.1：
RCS / 10.1.1：
CVS / 10.1.2：
Integrated Configuration Management Systems / 10.1.3：
DSEE / 10.2.1：
ClearCASE / 10.2.2：
Other Systems / 10.3：
Vesta System Performance / 11：
Platform Configuration / 11.1：
Overall System Performance / 11.2：
Performance Comparison with Make / 11.2.1：
Performance Breakdown / 11.2.2：
Caching Analysis / 11.2.3：
Resource Usage / 11.2.4：
Repository Performance / 11.3：
Speed of File Operations / 11.3.1：
Disk and Memory Consumption / 11.3.2：
Speed of Repository Tools / 11.3.3：
Speed of Cross-Repository Tools / 11.3.4：
Speed of the Replicator / 11.3.5：
Function Cache Performance / 11.4：
Server Performance / 11.4.1：
Measurements of the Stable Cache / 11.4.2：
Disk and Memory Usage / 11.4.3：
Function Cache Scalability / 11.4.4：
Weeder Performance / 11.5：
Interprocess Communication / 11.6：
Conclusions / 12：
Vesta in the Real World / 12.1：
Vesta in the Future / 12.2：
SDL Reference Manual / A：
Lexical Conventions / A.1：
Meta-notation / A.2.1：
Terminals / A.2.2：
Semantics / A.3：
Value Space / A.3.1：
Type Declarations / A.3.2：
Evaluation Rules / A.3.3：
Expr / A.3.3.1：
Literal / A.3.3.2：
Id / A.3.3.3：
List / A.3.3.4：
Binding / A.3.3.5：
Select / A.3.3.6：
Block / A.3.3.7：
Stmt / A.3.3.8：
Assign / A.3.3.9：
Iterate / A.3.3.10：
FuncDef / A.3.3.11：
FuncCall / A.3.3.12：
Model / A.3.3.13：
Files / A.3.3.14：
File Name Interpretation / A.3.3.15：
Pragmas / A.3.3.17：
Primitives / A.3.4：
Functions on Type t_bool / A.3.4.1：
Functions on Type t_int / A.3.4.2：
Functions on Type t_text / A.3.4.3：
Functions on Type t_list / A.3.4.4：
Functions on Type t_binding / A.3.4.5：
Special Purpose Functions / A.3.4.6：
Type Manipulation Functions / A.3.4.7：
Tool Invocation Function / A.3.4.8：
Diagnostic Functions / A.3.4.9：
Concrete Syntax / A.4：
Grammar / A.4.1：
Ambiguity Resolution / A.4.2：
Tokens / A.4.3：
Reserved Identifiers / A.4.4：
The Vesta Web Site / B：
References
Index
Preface
Introducing Vesta / Part I：
Introduction / 1：
26.

電子ブック
ＥＢ
26. Best Practices in Software Measurement
Manfred; Dumke, Reiner; Ebert, Christof; Schmietendorf, Andreas Bundschuh, Rainer Dumke, Christof Ebert, Reiner Dumke, Andreas Schmietendorf
出版情報: Springer eBooks Computer Science , Dordrecht : Springer Berlin Heidelberg, 2005
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Making Metrics a Success - The Business Perspective / 2：
The Business Need for Measurement / 2.1：
Managing by the Numbers / 2.2：
Extraction / 2.2.1：
Evaluation / 2.2.2：
Execution / 2.2.3：
Metrics for Management Guidance / 2.3：
Portfolio Management / 2.3.1：
Technology Management / 2.3.2：
Product and Release Planning / 2.3.3：
Making the Business Case / 2.3.4：
Hints for the Practitioner / 2.4：
Summary / 2.5：
Planning the Measurement Process / 3：
Software Measurement Needs Planning / 3.1：
Goal-Oriented Approaches / 3.2：
The GQM Methodology / 3.2.1：
The CAME Approach / 3.2.2：
Measurement Choice / 3.3：
Measurement Adjustment / 3.4：
Measurement Migration / 3.5：
Measurement Efficiency / 3.6：
Performing the Measurement Process / 3.7：
Measurement Tools and Software e-Measurement / 4.1：
Applications and Strategies of Metrics Tools / 4.2：
Software process measurement and evaluation / 4.2.1：
Software Product Measurement and Evaluation / 4.2.2：
Software Process Resource Measurement and Evaluation / 4.2.3：
Software Measurement Presentation and Statistical Analysis / 4.2.4：
Software Measurement Training / 4.2.5：
Solutions and Directions in Software e-Measurement / 4.3：
Introducing a Measurement Program / 4.4：
Making the Measurement Program Useful / 5.1：
Metrics Selection and Definition / 5.2：
Roles and Responsibilities in a Measurement Program / 5.3：
Building History Data / 5.4：
Positive and Negative Aspects of Software Measurement / 5.5：
It is People not Numbers! / 5.6：
Counter the Counterarguments / 5.7：
Information and Participation / 5.8：
Measurement Infrastructures / 5.9：
Access to Measurement Results / 6.1：
Introduction and Requirements / 6.2：
Motivation: Using Measurements for Benchmarking / 6.2.1：
Source of Metrics / 6.2.2：
Dimensions of a Metrics Database / 6.2.3：
Requirements of a Metrics Database / 6.2.4：
Case Study: Metrics Database for Object-Oriented Metrics / 6.3：
Prerequisites for the Effective Use of Metrics / 6.3.1：
Architecture and Design of the Application / 6.3.2：
Details of the Implementation / 6.3.3：
Functionality of the Metrics Database (Users' View) / 6.3.4：
Size and Effort Estimation / 6.4：
The Importance of Size and Cost Estimation / 7.1：
A Short Overview of Functional Size Measurement Methods / 7.2：
The COSMIC Full Function Point Method / 7.3：
Case Study: Using the COSMIC Full Function Point Method / 7.4：
Estimations Can Be Political / 7.5：
Establishing Buy-In: The Estimation Conference / 7.6：
Estimation Honesty / 7.7：
Estimation Culture / 7.8：
The Implementation of Estimation / 7.9：
Estimation Competence Center / 7.10：
Training for Estimation / 7.11：
Project Control / 7.12：
Project Control and Software Measurement / 8.1：
Applications of Project Control / 8.2：
Monitoring and Control / 8.2.1：
Forecasting / 8.2.2：
Cost Control / 8.2.3：
Defect Detection and Quality Improvement / 8.3：
Improving Quality of Software Systems / 9.1：
Fundamental Concepts / 9.2：
Defect Estimation / 9.2.1：
Defect Detection, Quality Gates and Reporting / 9.2.3：
Early Defect Detection / 9.3：
Reducing Cost of Non-Quality / 9.3.1：
Planning Early Defect Detection Activities / 9.3.2：
Criticality Prediction - Applying Empirical Software Engineering / 9.4：
Identifying Critical Components / 9.4.1：
Practical Criticality Prediction / 9.4.2：
Software Reliability Prediction / 9.5：
Practical Software Reliability Engineering / 9.5.1：
Applying Reliability Growth Models / 9.5.2：
Calculating ROI of Quality Initiatives / 9.6：
Software Process Improvement / 9.7：
Process Management and Process Improvement / 10.1：
Making Change Happen / 10.2：
Setting Reachable Targets / 10.2.2：
Providing Feedback / 10.2.3：
Practically Speaking: Implementing Change / 10.2.4：
Critical Success Factors / 10.2.5：
Process Management / 10.3：
Process Definition and Workflow Management / 10.3.1：
Quantitative Process Management / 10.3.2：
Process Change Management / 10.3.3：
Measuring the Results of Process Improvements / 10.4：
Software Performance Engineering / 10.5：
The Method of Software Performance Engineering / 11.1：
Motivation, Requirements and Goals / 11.2：
Performance-related Risk of Software Systems / 11.2.1：
Requirements and Aims / 11.2.2：
A Practical Approach of Software Performance Engineering / 11.3：
Overview of an Integrated Approach / 11.3.1：
Establishing and Resolving Performance Models / 11.3.2：
Generalization of the Need for Model Variables / 11.3.3：
Sources of Model Variables / 11.3.4：
Performance and Software Metrics / 11.3.5：
Persistence of Software and Performance Metrics / 11.3.6：
Case Study: EAI / 11.4：
Introduction of a EAI Solution / 11.4.1：
Available Studies / 11.4.2：
Developing EAI to Meet Performance Needs / 11.4.3：
Costs of Software Performance Engineering / 11.5：
Performance Risk Model (PRM) / 11.5.1：
Service Level Management / 11.6：
Measuring Service Level Management / 12.1：
Web Services and Service Management / 12.2：
Web Services at a Glance / 12.2.1：
Overview of SLAs / 12.2.2：
Service Agreement and Service Provision / 12.2.3：
Web Service Level Agreements / 12.3：
WSLA Schema Specification / 12.3.1：
Web Services Run-Time Environment / 12.3.2：
Guaranteeing Web Service Level Agreements / 12.3.3：
Monitoring the SLA Parameters / 12.3.4：
Use of a Measurement Service / 12.3.5：
Case Study: Building an Intranet Measurement Application / 12.4：
Applying Measurement Tools / 13.1：
The White-Box Software Estimation Approach / 13.2：
First Web-Based Approach / 13.3：
Second Web-Based Approach / 13.4：
Case Study: Measurements in IT Projects / 13.5：
Estimations: A Start for a Measurement Program / 14.1：
Environment / 14.2：
The IT Organization / 14.2.1：
Function Point Project Baseline / 14.2.2：
Function Point Prognosis / 14.3：
Conclusions from Case Study / 14.4：
Counting and Accounting / 14.4.1：
ISO 8402 Quality Measures and IFPUG GSCs / 14.4.2：
Distribution of Estimated Effort to Project Phases / 14.4.3：
Estimation of Maintenance Tasks / 14.4.4：
The UKSMA and NESMA Standard / 14.4.5：
Enhancement Projects / 14.4.6：
Software Metrics for Maintenance / 14.4.7：
Estimation of Maintenance Effort After Delivery / 14.4.8：
Estimation for (Single) Maintenance Tasks / 14.4.9：
Simulations for Estimations / 14.4.10：
Sensitivity analysis / 14.4.11：
Case Study: Metrics in Maintenance / 14.5：
Motivation for a Tool-based Approach / 15.1：
The Software System under Investigation / 15.2：
Quality Evaluation with Logiscope / 15.3：
Application of Static Source Code Analysis / 15.4：
Metrics Communities and Resources / 15.5：
Benefits of Networking / 16.1：
CMG / 16.2：
COSMIC / 16.4：
German GI Interest Group on Software Metrics / 16.6：
IFPUG / 16.7：
ISBSG / 16.8：
ISO / 16.9：
SPEC / 16.10：
The MAIN Network / 16.11：
TPC / 16.12：
Internet URLs of Measurement Communities / 16.13：
Hints for the Practitioner and Summary / 16.14：
Glossary
Literature
Index
Introduction / 1：
Making Metrics a Success - The Business Perspective / 2：
The Business Need for Measurement / 2.1：
27.

電子ブック
ＥＢ
27. Web Engineering
Emilia Mendes, Nile Mosley
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2006
所蔵情報: loading…
目次情報: 続きを見る
The Need for Web Engineering: An Introduction / 1：
Introduction / 1.1：
Web Applications Versus Conventional Software / 1.2：
Web Hypermedia, Web Software, or Web Application? / 1.2.1：
Web Development vs. Software Development / 1.2.2：
The Need for an Engineering Approach / 1.3：
Empirical Assessment / 1.4：
Conclusions / 1.5：
Acknowledgements
References
Authors' Biographies
Web Effort Estimation / 2：
Effort Estimation Techniques / 2.1：
Expert Opinion / 2.2.1：
Algorithmic Techniques / 2.2.2：
Artificial Intelligence Techniques / 2.2.3：
Measuring Effort Prediction Power and Accuracy / 2.3：
Measuring Predictive Power / 2.3.1：
Measuring Predictive Accuracy / 2.3.2：
Which Is the Most Accurate Prediction Technique? / 2.4：
Case Study / 2.5：
Data Validation / 2.5.1：
Variables and Model Selection / 2.5.2：
Extraction of effort Equation / 2.5.3：
Model Validation / 2.5.4：
Web Productivity Measurement and Benchmarking / 2.6：
Productivity Measurement Method / 3.1：
Productivity Measure Construction / 3.3：
Productivity Analysis / 3.3.2：
Web Quality / 3.4：
Different Perspectives of Quality / 4.1：
Standards and Quality / 4.2.1：
Quality Versus Quality in Use / 4.2.2：
Quality and User Standpoints / 4.2.3：
What is Web Quality? / 4.2.4：
Evaluating Web Quality using WebQEM / 4.3：
Quality Requirements Definition and Specification / 4.3.1：
Elementary Measurement and Evaluation / 4.3.2：
Global Evaluation / 4.3.3：
Conclusions and Recommendations / 4.3.4：
Automating the Process using WebQEM_Tool / 4.3.5：
Case Study: Evaluating the Quality of Two Web Applications / 4.4：
External Quality Requirements / 4.4.1：
Designing and Executing the Elementary Evaluation / 4.4.2：
Designing and Executing the Partial/Global Evaluation / 4.4.3：
Analysis and Recommendations / 4.4.4：
Concluding Remarks / 4.5：
Web Usability: Principles and Evaluation Methods / 5：
Usability in the Software Lifecycle / 5.1：
Chapter Organisation / 5.1.2：
Defining Web Usability / 5.2：
Usability and Accessibility / 5.2.1：
Web Usability Criteria / 5.3：
Content Visibility / 5.3.1：
Ease of Content Access / 5.3.2：
Ease of Content Browsing / 5.3.3：
Evaluation Methods / 5.4：
User Testing / 5.4.1：
Inspection Methods / 5.4.2：
Automatic Tools To Support Evaluations / 5.5：
Evaluation of the DEI Application / 5.6：
Design Inspection / 5.6.1：
Web Usage Analysis / 5.6.2：
Web System Reliability and Performance / 5.7：
Web Application Services / 6.1：
Web Resource Classification / 6.2.1：
Web Application's Bearing on System Resources / 6.2.2：
Workload Models and Performance Requirements / 6.2.3：
Applications Predominantly Dynamic / 6.3：
Dynamic Request Service / 6.3.1：
Software Technologies for the Application Logic / 6.3.2：
System Platforms / 6.3.3：
Testing Loop Phase / 6.4：
Representation of the Workload Model / 6.4.1：
Traffic Generation / 6.4.2：
Data Collection and Analysis / 6.4.3：
Performance Improvements / 6.5：
System Tuning / 6.5.1：
System Scale-up / 6.5.2：
System Scale-out / 6.5.3：
Service Characterisation and Design / 6.6：
System Consolidation and Performance Improvement / 6.6.2：
Web Application Testing / 6.7：
Web Application Testing: Challenges and Perspectives / 7.1：
Testing the Non-functional Requirements of a Web Application / 7.2.1：
Testing the Functional Requirements of a Web Application / 7.2.2：
Web Application Representation Models / 7.3：
Unit Integration and System Testing of a Web Application / 7.4：
Unit Testing / 7.4.1：
Integration Testing / 7.4.2：
System Testing / 7.4.3：
Strategies for Web Application Testing / 7.5：
White Box Strategies / 7.5.1：
Black Box Strategies / 7.5.2：
Grey Box Testing Strategies / 7.5.3：
User Session Based Testing / 7.5.4：
Tools for Web Application Testing / 7.6：
A Practical Example of Web Application Testing / 7.7：
An Overview of Process Improvement in Small Settings / 7.8：
Why Do Organisations Initiate SPI Efforts? / 8.1：
Process Improvement Cycle / 8.1.2：
Process Assessments / 8.1.3：
Implementation in Small Settings / 8.2：
Availability of Funds / 8.2.1：
Resources For Process Improvement / 8.2.2：
Process Model / 8.2.3：
Training / 8.2.4：
Relevance of Practices in Assessment Models / 8.2.5：
Changing Behaviour / 8.2.6：
Piloting Practices / 8.2.7：
Where To Start / 8.2.8：
Author's Biography / 8.3：
Conceptual Modelling of Web Applications: The OOWS Approach / 9：
A Method to Model Web Applications / 9.1：
OO-Method Conceptual Modelling / 9.2.1：
OOWS: Extending Conceptual Modelling to Web Environments / 9.2.2：
A Strategy To Develop the Web Solution / 9.3：
Case Study: Valencia CF Web Application / 9.4：
Model-Based Web Application Development / 9.5：
The OOHDM approach - An Overview / 10.1：
Requirements Gathering / 10.1.1：
Conceptual Design / 10.1.2：
Navigational Design / 10.1.3：
Abstract Interface Design / 10.1.4：
Implementation / 10.1.5：
Building an Online CD Store with OOHDM / 10.2：
Conceptual Modelling / 10.2.1：
Navigation Design / 10.2.3：
From Design to Implementation / 10.2.4：
Discussion and Lessons Learned / 10.4：
Authors' Biography / 10.5：
W2000: A Modelling Notation for Complex Web Applications / 11：
Modelling Elements / 11.1：
Models / 11.3：
Adaptability / 11.3.1：
Tool Support / 11.3.2：
Example Application / 11.4：
Information Model / 11.4.1：
Navigation Model / 11.4.2：
Presentation Model / 11.4.3：
Service Model / 11.4.4：
Conclusions and Future Work / 11.5：
What You Need To Know About Statistics / 12：
Describing Individual Variables / 12.1：
Types of Variables / 12.1.1：
Descriptive Statistics / 12.1.2：
The Normal Distribution / 12.2：
Overview of Sampling Theory / 12.3：
Other Probability Distributions / 12.4：
Identifying Relationships in the Data / 12.5：
Chi-Square Test for Independence / 12.5.1：
Correlation Analysis / 12.5.2：
Regression Analysis / 12.5.3：
Analysis of Variance (ANOVA) / 12.5.4：
Comparing Two Estimation Models / 12.5.5：
Final Comments / 12.5.6：
Empirical Research Methods in Web and Software Engineering / 13：
Overview of Empirical Methods / 13.1：
Empirical Methods in an Improvement Context / 13.3：
Controlled Experiments / 13.4：
Design / 13.4.1：
Operation / 13.4.3：
Analysis and Interpretation / 13.4.4：
Case Study Arrangements / 13.5：
Confounding Factors and Other Aspects / 13.5.3：
Survey / 13.6：
Survey Characteristics / 13.6.1：
Survey Purposes / 13.6.2：
Data Collection / 13.6.3：
Post-mortem Analysis / 13.7：
Summary / 13.8：
Authors Biographies
The Need for Web Engineering: An Introduction / 1：
Introduction / 1.1：
Web Applications Versus Conventional Software / 1.2：
28.

電子ブック
ＥＢ
28. Best Practices in Software Measurement
Manfred; Dumke, Reiner; Ebert, Christof; Schmietendorf, Andreas Bundschuh, Rainer Dumke, Christof Ebert, Reiner Dumke, Andreas Schmietendorf, Manfred Bundschuh
出版情報: SpringerLink Books - AutoHoldings , Dordrecht : Springer Berlin Heidelberg, 2005
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Making Metrics a Success - The Business Perspective / 2：
The Business Need for Measurement / 2.1：
Managing by the Numbers / 2.2：
Extraction / 2.2.1：
Evaluation / 2.2.2：
Execution / 2.2.3：
Metrics for Management Guidance / 2.3：
Portfolio Management / 2.3.1：
Technology Management / 2.3.2：
Product and Release Planning / 2.3.3：
Making the Business Case / 2.3.4：
Hints for the Practitioner / 2.4：
Summary / 2.5：
Planning the Measurement Process / 3：
Software Measurement Needs Planning / 3.1：
Goal-Oriented Approaches / 3.2：
The GQM Methodology / 3.2.1：
The CAME Approach / 3.2.2：
Measurement Choice / 3.3：
Measurement Adjustment / 3.4：
Measurement Migration / 3.5：
Measurement Efficiency / 3.6：
Performing the Measurement Process / 3.7：
Measurement Tools and Software e-Measurement / 4.1：
Applications and Strategies of Metrics Tools / 4.2：
Software process measurement and evaluation / 4.2.1：
Software Product Measurement and Evaluation / 4.2.2：
Software Process Resource Measurement and Evaluation / 4.2.3：
Software Measurement Presentation and Statistical Analysis / 4.2.4：
Software Measurement Training / 4.2.5：
Solutions and Directions in Software e-Measurement / 4.3：
Introducing a Measurement Program / 4.4：
Making the Measurement Program Useful / 5.1：
Metrics Selection and Definition / 5.2：
Roles and Responsibilities in a Measurement Program / 5.3：
Building History Data / 5.4：
Positive and Negative Aspects of Software Measurement / 5.5：
It is People not Numbers! / 5.6：
Counter the Counterarguments / 5.7：
Information and Participation / 5.8：
Measurement Infrastructures / 5.9：
Access to Measurement Results / 6.1：
Introduction and Requirements / 6.2：
Motivation: Using Measurements for Benchmarking / 6.2.1：
Source of Metrics / 6.2.2：
Dimensions of a Metrics Database / 6.2.3：
Requirements of a Metrics Database / 6.2.4：
Case Study: Metrics Database for Object-Oriented Metrics / 6.3：
Prerequisites for the Effective Use of Metrics / 6.3.1：
Architecture and Design of the Application / 6.3.2：
Details of the Implementation / 6.3.3：
Functionality of the Metrics Database (Users' View) / 6.3.4：
Size and Effort Estimation / 6.4：
The Importance of Size and Cost Estimation / 7.1：
A Short Overview of Functional Size Measurement Methods / 7.2：
The COSMIC Full Function Point Method / 7.3：
Case Study: Using the COSMIC Full Function Point Method / 7.4：
Estimations Can Be Political / 7.5：
Establishing Buy-In: The Estimation Conference / 7.6：
Estimation Honesty / 7.7：
Estimation Culture / 7.8：
The Implementation of Estimation / 7.9：
Estimation Competence Center / 7.10：
Training for Estimation / 7.11：
Project Control / 7.12：
Project Control and Software Measurement / 8.1：
Applications of Project Control / 8.2：
Monitoring and Control / 8.2.1：
Forecasting / 8.2.2：
Cost Control / 8.2.3：
Defect Detection and Quality Improvement / 8.3：
Improving Quality of Software Systems / 9.1：
Fundamental Concepts / 9.2：
Defect Estimation / 9.2.1：
Defect Detection, Quality Gates and Reporting / 9.2.3：
Early Defect Detection / 9.3：
Reducing Cost of Non-Quality / 9.3.1：
Planning Early Defect Detection Activities / 9.3.2：
Criticality Prediction - Applying Empirical Software Engineering / 9.4：
Identifying Critical Components / 9.4.1：
Practical Criticality Prediction / 9.4.2：
Software Reliability Prediction / 9.5：
Practical Software Reliability Engineering / 9.5.1：
Applying Reliability Growth Models / 9.5.2：
Calculating ROI of Quality Initiatives / 9.6：
Software Process Improvement / 9.7：
Process Management and Process Improvement / 10.1：
Making Change Happen / 10.2：
Setting Reachable Targets / 10.2.2：
Providing Feedback / 10.2.3：
Practically Speaking: Implementing Change / 10.2.4：
Critical Success Factors / 10.2.5：
Process Management / 10.3：
Process Definition and Workflow Management / 10.3.1：
Quantitative Process Management / 10.3.2：
Process Change Management / 10.3.3：
Measuring the Results of Process Improvements / 10.4：
Software Performance Engineering / 10.5：
The Method of Software Performance Engineering / 11.1：
Motivation, Requirements and Goals / 11.2：
Performance-related Risk of Software Systems / 11.2.1：
Requirements and Aims / 11.2.2：
A Practical Approach of Software Performance Engineering / 11.3：
Overview of an Integrated Approach / 11.3.1：
Establishing and Resolving Performance Models / 11.3.2：
Generalization of the Need for Model Variables / 11.3.3：
Sources of Model Variables / 11.3.4：
Performance and Software Metrics / 11.3.5：
Persistence of Software and Performance Metrics / 11.3.6：
Case Study: EAI / 11.4：
Introduction of a EAI Solution / 11.4.1：
Available Studies / 11.4.2：
Developing EAI to Meet Performance Needs / 11.4.3：
Costs of Software Performance Engineering / 11.5：
Performance Risk Model (PRM) / 11.5.1：
Service Level Management / 11.6：
Measuring Service Level Management / 12.1：
Web Services and Service Management / 12.2：
Web Services at a Glance / 12.2.1：
Overview of SLAs / 12.2.2：
Service Agreement and Service Provision / 12.2.3：
Web Service Level Agreements / 12.3：
WSLA Schema Specification / 12.3.1：
Web Services Run-Time Environment / 12.3.2：
Guaranteeing Web Service Level Agreements / 12.3.3：
Monitoring the SLA Parameters / 12.3.4：
Use of a Measurement Service / 12.3.5：
Case Study: Building an Intranet Measurement Application / 12.4：
Applying Measurement Tools / 13.1：
The White-Box Software Estimation Approach / 13.2：
First Web-Based Approach / 13.3：
Second Web-Based Approach / 13.4：
Case Study: Measurements in IT Projects / 13.5：
Estimations: A Start for a Measurement Program / 14.1：
Environment / 14.2：
The IT Organization / 14.2.1：
Function Point Project Baseline / 14.2.2：
Function Point Prognosis / 14.3：
Conclusions from Case Study / 14.4：
Counting and Accounting / 14.4.1：
ISO 8402 Quality Measures and IFPUG GSCs / 14.4.2：
Distribution of Estimated Effort to Project Phases / 14.4.3：
Estimation of Maintenance Tasks / 14.4.4：
The UKSMA and NESMA Standard / 14.4.5：
Enhancement Projects / 14.4.6：
Software Metrics for Maintenance / 14.4.7：
Estimation of Maintenance Effort After Delivery / 14.4.8：
Estimation for (Single) Maintenance Tasks / 14.4.9：
Simulations for Estimations / 14.4.10：
Sensitivity analysis / 14.4.11：
Case Study: Metrics in Maintenance / 14.5：
Motivation for a Tool-based Approach / 15.1：
The Software System under Investigation / 15.2：
Quality Evaluation with Logiscope / 15.3：
Application of Static Source Code Analysis / 15.4：
Metrics Communities and Resources / 15.5：
Benefits of Networking / 16.1：
CMG / 16.2：
COSMIC / 16.4：
German GI Interest Group on Software Metrics / 16.6：
IFPUG / 16.7：
ISBSG / 16.8：
ISO / 16.9：
SPEC / 16.10：
The MAIN Network / 16.11：
TPC / 16.12：
Internet URLs of Measurement Communities / 16.13：
Hints for the Practitioner and Summary / 16.14：
Glossary
Literature
Index
Introduction / 1：
Making Metrics a Success - The Business Perspective / 2：
The Business Need for Measurement / 2.1：
29.

電子ブック
ＥＢ
29. Web Engineering
Emilia Mendes, Nile Mosley
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2006
所蔵情報: loading…
目次情報: 続きを見る
The Need for Web Engineering: An Introduction / 1：
Introduction / 1.1：
Web Applications Versus Conventional Software / 1.2：
Web Hypermedia, Web Software, or Web Application? / 1.2.1：
Web Development vs. Software Development / 1.2.2：
The Need for an Engineering Approach / 1.3：
Empirical Assessment / 1.4：
Conclusions / 1.5：
Acknowledgements
References
Authors' Biographies
Web Effort Estimation / 2：
Effort Estimation Techniques / 2.1：
Expert Opinion / 2.2.1：
Algorithmic Techniques / 2.2.2：
Artificial Intelligence Techniques / 2.2.3：
Measuring Effort Prediction Power and Accuracy / 2.3：
Measuring Predictive Power / 2.3.1：
Measuring Predictive Accuracy / 2.3.2：
Which Is the Most Accurate Prediction Technique? / 2.4：
Case Study / 2.5：
Data Validation / 2.5.1：
Variables and Model Selection / 2.5.2：
Extraction of effort Equation / 2.5.3：
Model Validation / 2.5.4：
Web Productivity Measurement and Benchmarking / 2.6：
Productivity Measurement Method / 3.1：
Productivity Measure Construction / 3.3：
Productivity Analysis / 3.3.2：
Web Quality / 3.4：
Different Perspectives of Quality / 4.1：
Standards and Quality / 4.2.1：
Quality Versus Quality in Use / 4.2.2：
Quality and User Standpoints / 4.2.3：
What is Web Quality? / 4.2.4：
Evaluating Web Quality using WebQEM / 4.3：
Quality Requirements Definition and Specification / 4.3.1：
Elementary Measurement and Evaluation / 4.3.2：
Global Evaluation / 4.3.3：
Conclusions and Recommendations / 4.3.4：
Automating the Process using WebQEM_Tool / 4.3.5：
Case Study: Evaluating the Quality of Two Web Applications / 4.4：
External Quality Requirements / 4.4.1：
Designing and Executing the Elementary Evaluation / 4.4.2：
Designing and Executing the Partial/Global Evaluation / 4.4.3：
Analysis and Recommendations / 4.4.4：
Concluding Remarks / 4.5：
Web Usability: Principles and Evaluation Methods / 5：
Usability in the Software Lifecycle / 5.1：
Chapter Organisation / 5.1.2：
Defining Web Usability / 5.2：
Usability and Accessibility / 5.2.1：
Web Usability Criteria / 5.3：
Content Visibility / 5.3.1：
Ease of Content Access / 5.3.2：
Ease of Content Browsing / 5.3.3：
Evaluation Methods / 5.4：
User Testing / 5.4.1：
Inspection Methods / 5.4.2：
Automatic Tools To Support Evaluations / 5.5：
Evaluation of the DEI Application / 5.6：
Design Inspection / 5.6.1：
Web Usage Analysis / 5.6.2：
Web System Reliability and Performance / 5.7：
Web Application Services / 6.1：
Web Resource Classification / 6.2.1：
Web Application's Bearing on System Resources / 6.2.2：
Workload Models and Performance Requirements / 6.2.3：
Applications Predominantly Dynamic / 6.3：
Dynamic Request Service / 6.3.1：
Software Technologies for the Application Logic / 6.3.2：
System Platforms / 6.3.3：
Testing Loop Phase / 6.4：
Representation of the Workload Model / 6.4.1：
Traffic Generation / 6.4.2：
Data Collection and Analysis / 6.4.3：
Performance Improvements / 6.5：
System Tuning / 6.5.1：
System Scale-up / 6.5.2：
System Scale-out / 6.5.3：
Service Characterisation and Design / 6.6：
System Consolidation and Performance Improvement / 6.6.2：
Web Application Testing / 6.7：
Web Application Testing: Challenges and Perspectives / 7.1：
Testing the Non-functional Requirements of a Web Application / 7.2.1：
Testing the Functional Requirements of a Web Application / 7.2.2：
Web Application Representation Models / 7.3：
Unit Integration and System Testing of a Web Application / 7.4：
Unit Testing / 7.4.1：
Integration Testing / 7.4.2：
System Testing / 7.4.3：
Strategies for Web Application Testing / 7.5：
White Box Strategies / 7.5.1：
Black Box Strategies / 7.5.2：
Grey Box Testing Strategies / 7.5.3：
User Session Based Testing / 7.5.4：
Tools for Web Application Testing / 7.6：
A Practical Example of Web Application Testing / 7.7：
An Overview of Process Improvement in Small Settings / 7.8：
Why Do Organisations Initiate SPI Efforts? / 8.1：
Process Improvement Cycle / 8.1.2：
Process Assessments / 8.1.3：
Implementation in Small Settings / 8.2：
Availability of Funds / 8.2.1：
Resources For Process Improvement / 8.2.2：
Process Model / 8.2.3：
Training / 8.2.4：
Relevance of Practices in Assessment Models / 8.2.5：
Changing Behaviour / 8.2.6：
Piloting Practices / 8.2.7：
Where To Start / 8.2.8：
Author's Biography / 8.3：
Conceptual Modelling of Web Applications: The OOWS Approach / 9：
A Method to Model Web Applications / 9.1：
OO-Method Conceptual Modelling / 9.2.1：
OOWS: Extending Conceptual Modelling to Web Environments / 9.2.2：
A Strategy To Develop the Web Solution / 9.3：
Case Study: Valencia CF Web Application / 9.4：
Model-Based Web Application Development / 9.5：
The OOHDM approach - An Overview / 10.1：
Requirements Gathering / 10.1.1：
Conceptual Design / 10.1.2：
Navigational Design / 10.1.3：
Abstract Interface Design / 10.1.4：
Implementation / 10.1.5：
Building an Online CD Store with OOHDM / 10.2：
Conceptual Modelling / 10.2.1：
Navigation Design / 10.2.3：
From Design to Implementation / 10.2.4：
Discussion and Lessons Learned / 10.4：
Authors' Biography / 10.5：
W2000: A Modelling Notation for Complex Web Applications / 11：
Modelling Elements / 11.1：
Models / 11.3：
Adaptability / 11.3.1：
Tool Support / 11.3.2：
Example Application / 11.4：
Information Model / 11.4.1：
Navigation Model / 11.4.2：
Presentation Model / 11.4.3：
Service Model / 11.4.4：
Conclusions and Future Work / 11.5：
What You Need To Know About Statistics / 12：
Describing Individual Variables / 12.1：
Types of Variables / 12.1.1：
Descriptive Statistics / 12.1.2：
The Normal Distribution / 12.2：
Overview of Sampling Theory / 12.3：
Other Probability Distributions / 12.4：
Identifying Relationships in the Data / 12.5：
Chi-Square Test for Independence / 12.5.1：
Correlation Analysis / 12.5.2：
Regression Analysis / 12.5.3：
Analysis of Variance (ANOVA) / 12.5.4：
Comparing Two Estimation Models / 12.5.5：
Final Comments / 12.5.6：
Empirical Research Methods in Web and Software Engineering / 13：
Overview of Empirical Methods / 13.1：
Empirical Methods in an Improvement Context / 13.3：
Controlled Experiments / 13.4：
Design / 13.4.1：
Operation / 13.4.3：
Analysis and Interpretation / 13.4.4：
Case Study Arrangements / 13.5：
Confounding Factors and Other Aspects / 13.5.3：
Survey / 13.6：
Survey Characteristics / 13.6.1：
Survey Purposes / 13.6.2：
Data Collection / 13.6.3：
Post-mortem Analysis / 13.7：
Summary / 13.8：
Authors Biographies
The Need for Web Engineering: An Introduction / 1：
Introduction / 1.1：
Web Applications Versus Conventional Software / 1.2：
30.

電子ブック
ＥＢ
30. A Concise Introduction to Software Engineering
Pankaj Jalote
出版情報: Springer eBooks Computer Science , Springer London, 2008
所蔵情報: loading…
目次情報: 続きを見る
The Software Problem / 1：
Cost, Schedule, and Quality / 1.1：
Scale and Change / 1.2：
Summary / 1.3：
Self-Assessment Exercises
Software Processes / 2：
Process and Project / 2.1：
Component Software Processes / 2.2：
Software Development Process Models / 2.3：
Waterfall Model / 2.3.1：
Prototyping / 2.3.2：
Iterative Development / 2.3.3：
Rational Unified Process / 2.3.4：
Timeboxing Model / 2.3.5：
Extreme Programming and Agile Processes / 2.3.6：
Using Process Models in a Project / 2.3.7：
Project Management Process / 2.4：
Software Requirements Analysis and Specification / 2.5：
Value of a Good SRS / 3.1：
Requirement Process / 3.2：
Requirements Specification / 3.3：
Desirable Characteristics of an SRS / 3.3.1：
Components of an SRS / 3.3.2：
Structure of a Requirements Document / 3.3.3：
Functional Specification with Use Cases / 3.4：
Basics / 3.4.1：
Examples / 3.4.2：
Extensions / 3.4.3：
Developing Use Cases / 3.4.4：
Other Approaches for Analysis / 3.5：
Data Flow Diagrams / 3.5.1：
ER Diagrams / 3.5.2：
Validation / 3.6：
Planning a Software Project / 3.7：
Effort Estimation / 4.1：
Top-Down Estimation Approach / 4.1.1：
Bottom-Up Estimation Approach / 4.1.2：
Project Schedule and Staffing / 4.2：
Quality Planning / 4.3：
Risk Management Planning / 4.4：
Risk Management Concepts / 4.4.1：
Risk Assessment / 4.4.2：
Risk Control / 4.4.3：
A Practical Risk Management Planning Approach / 4.4.4：
Project Monitoring Plan / 4.5：
Measurements / 4.5.1：
Project Monitoring and Tracking / 4.5.2：
Detailed Scheduling / 4.6：
Software Architecture / 4.7：
Role of Software Architecture / 5.1：
Architecture Views / 5.2：
Component and Connector View / 5.3：
Components / 5.3.1：
Connectors / 5.3.2：
An Example / 5.3.3：
Architecture Styles for C&C View / 5.4：
Pipe and Filter / 5.4.1：
Shared-Data Style / 5.4.2：
Client-Server Style / 5.4.3：
Some Other Styles / 5.4.4：
Documenting Architecture Design / 5.5：
Evaluating Architectures / 5.6：
Design / 5.7：
Design Concepts / 6.1：
Coupling / 6.1.1：
Cohesion / 6.1.2：
The Open-Closed Principle / 6.1.3：
Function-Oriented Design / 6.2：
Structure Charts / 6.2.1：
Structured Design Methodology / 6.2.2：
Object-Oriented Design / 6.2.3：
OO Concepts / 6.3.1：
Unified Modeling Language (UML) / 6.3.2：
A Design Methodology / 6.3.3：
Detailed Design / 6.3.4：
Logic/Algorithm Design / 6.4.1：
State Modeling of Classes / 6.4.2：
Verification / 6.5：
Metrics / 6.6：
Complexity Metrics for Function-Oriented Design / 6.6.1：
Complexity Metrics for OO Design / 6.6.2：
Coding and Unit Testing / 6.7：
Programming Principles and Guidelines / 7.1：
Structured Programming / 7.1.1：
Information Hiding / 7.1.2：
Some Programming Practices / 7.1.3：
Coding Standards / 7.1.4：
Incrementally Developing Code / 7.2：
An Incremental Coding Process / 7.2.1：
Test-Driven Development / 7.2.2：
Pair Programming / 7.2.3：
Managing Evolving Code / 7.3：
Source Code Control and Build / 7.3.1：
Refactoring / 7.3.2：
Unit Testing / 7.4：
Testing Procedural Units / 7.4.1：
Unit Testing of Classes / 7.4.2：
Code Inspection / 7.5：
Planning / 7.5.1：
Self-Review / 7.5.2：
Group Review Meeting / 7.5.3：
Size Measures / 7.6：
Complexity Metrics / 7.6.2：
Testing / 7.7：
Testing Concepts / 8.1：
Error, Fault, and Failure / 8.1.1：
Test Case, Test Suite, and Test Harness / 8.1.2：
Psychology of Testing / 8.1.3：
Levels of Testing / 8.1.4：
Testing Process / 8.2：
Test Plan / 8.2.1：
Test Case Design / 8.2.2：
Test Case Execution / 8.2.3：
Black-Box Testing / 8.3：
Equivalence Class Partitioning / 8.3.1：
Boundary Value Analysis / 8.3.2：
Pairwise Testing / 8.3.3：
Special Cases / 8.3.4：
State-Based Testing / 8.3.5：
White-Box Testing / 8.4：
Control Flow-Based Criteria / 8.4.1：
Test Case Generation and Tool Support / 8.4.2：
Coverage Analysis / 8.5：
Reliability / 8.5.2：
Defect Removal Efficiency / 8.5.3：
Self Assessment-Exercises / 8.6：
Bibliography
Index
The Software Problem / 1：
Cost, Schedule, and Quality / 1.1：
Scale and Change / 1.2：
31.

電子ブック
ＥＢ
31. A Concise Introduction to Software Engineering
Pankaj Jalote
出版情報: SpringerLink Books - AutoHoldings , Springer London, 2008
所蔵情報: loading…
目次情報: 続きを見る
The Software Problem / 1：
Cost, Schedule, and Quality / 1.1：
Scale and Change / 1.2：
Summary / 1.3：
Self-Assessment Exercises
Software Processes / 2：
Process and Project / 2.1：
Component Software Processes / 2.2：
Software Development Process Models / 2.3：
Waterfall Model / 2.3.1：
Prototyping / 2.3.2：
Iterative Development / 2.3.3：
Rational Unified Process / 2.3.4：
Timeboxing Model / 2.3.5：
Extreme Programming and Agile Processes / 2.3.6：
Using Process Models in a Project / 2.3.7：
Project Management Process / 2.4：
Software Requirements Analysis and Specification / 2.5：
Value of a Good SRS / 3.1：
Requirement Process / 3.2：
Requirements Specification / 3.3：
Desirable Characteristics of an SRS / 3.3.1：
Components of an SRS / 3.3.2：
Structure of a Requirements Document / 3.3.3：
Functional Specification with Use Cases / 3.4：
Basics / 3.4.1：
Examples / 3.4.2：
Extensions / 3.4.3：
Developing Use Cases / 3.4.4：
Other Approaches for Analysis / 3.5：
Data Flow Diagrams / 3.5.1：
ER Diagrams / 3.5.2：
Validation / 3.6：
Planning a Software Project / 3.7：
Effort Estimation / 4.1：
Top-Down Estimation Approach / 4.1.1：
Bottom-Up Estimation Approach / 4.1.2：
Project Schedule and Staffing / 4.2：
Quality Planning / 4.3：
Risk Management Planning / 4.4：
Risk Management Concepts / 4.4.1：
Risk Assessment / 4.4.2：
Risk Control / 4.4.3：
A Practical Risk Management Planning Approach / 4.4.4：
Project Monitoring Plan / 4.5：
Measurements / 4.5.1：
Project Monitoring and Tracking / 4.5.2：
Detailed Scheduling / 4.6：
Software Architecture / 4.7：
Role of Software Architecture / 5.1：
Architecture Views / 5.2：
Component and Connector View / 5.3：
Components / 5.3.1：
Connectors / 5.3.2：
An Example / 5.3.3：
Architecture Styles for C&C View / 5.4：
Pipe and Filter / 5.4.1：
Shared-Data Style / 5.4.2：
Client-Server Style / 5.4.3：
Some Other Styles / 5.4.4：
Documenting Architecture Design / 5.5：
Evaluating Architectures / 5.6：
Design / 5.7：
Design Concepts / 6.1：
Coupling / 6.1.1：
Cohesion / 6.1.2：
The Open-Closed Principle / 6.1.3：
Function-Oriented Design / 6.2：
Structure Charts / 6.2.1：
Structured Design Methodology / 6.2.2：
Object-Oriented Design / 6.2.3：
OO Concepts / 6.3.1：
Unified Modeling Language (UML) / 6.3.2：
A Design Methodology / 6.3.3：
Detailed Design / 6.3.4：
Logic/Algorithm Design / 6.4.1：
State Modeling of Classes / 6.4.2：
Verification / 6.5：
Metrics / 6.6：
Complexity Metrics for Function-Oriented Design / 6.6.1：
Complexity Metrics for OO Design / 6.6.2：
Coding and Unit Testing / 6.7：
Programming Principles and Guidelines / 7.1：
Structured Programming / 7.1.1：
Information Hiding / 7.1.2：
Some Programming Practices / 7.1.3：
Coding Standards / 7.1.4：
Incrementally Developing Code / 7.2：
An Incremental Coding Process / 7.2.1：
Test-Driven Development / 7.2.2：
Pair Programming / 7.2.3：
Managing Evolving Code / 7.3：
Source Code Control and Build / 7.3.1：
Refactoring / 7.3.2：
Unit Testing / 7.4：
Testing Procedural Units / 7.4.1：
Unit Testing of Classes / 7.4.2：
Code Inspection / 7.5：
Planning / 7.5.1：
Self-Review / 7.5.2：
Group Review Meeting / 7.5.3：
Size Measures / 7.6：
Complexity Metrics / 7.6.2：
Testing / 7.7：
Testing Concepts / 8.1：
Error, Fault, and Failure / 8.1.1：
Test Case, Test Suite, and Test Harness / 8.1.2：
Psychology of Testing / 8.1.3：
Levels of Testing / 8.1.4：
Testing Process / 8.2：
Test Plan / 8.2.1：
Test Case Design / 8.2.2：
Test Case Execution / 8.2.3：
Black-Box Testing / 8.3：
Equivalence Class Partitioning / 8.3.1：
Boundary Value Analysis / 8.3.2：
Pairwise Testing / 8.3.3：
Special Cases / 8.3.4：
State-Based Testing / 8.3.5：
White-Box Testing / 8.4：
Control Flow-Based Criteria / 8.4.1：
Test Case Generation and Tool Support / 8.4.2：
Coverage Analysis / 8.5：
Reliability / 8.5.2：
Defect Removal Efficiency / 8.5.3：
Self Assessment-Exercises / 8.6：
Bibliography
Index
The Software Problem / 1：
Cost, Schedule, and Quality / 1.1：
Scale and Change / 1.2：
32.

電子ブック
ＥＢ
32. Requirements Engineering
Elizabeth Hull, Jeremy Dick, Ken Jackson
出版情報: Springer eBooks Computer Science , Springer London, 2011
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Introduction to Requirements / 1.1：
Introduction to Systems Engineering / 1.2：
Defining Requirements Engineering / 1.3：
Definition of a Requirement / 1.3.1：
Definition of a Stakeholder / 1.3.2：
Definition of Requirements Engineering / 1.3.3：
Requirements and Quality / 1.4：
Requirements and the Lifecycle / 1.5：
Requirements Tracing / 1.6：
Requirements and Modelling / 1.7：
Requirements and Testing / 1.8：
Requirements in the Problem and Solution Domains / 1.9：
How to Read this Book / 1.10：
A Generic Process for Requirements Engineering / 2：
Developing Systems / 2.1：
Generic Process Context / 2.3：
Input Requirements and Derived Requirements / 2.3.1：
Acceptance Criteria and Qualification Strategy / 2.3.2：
Generic Process Introduction / 2.4：
Ideal Development / 2.4.1：
Development in the Context of Change / 2.4.2：
Generic Process Information Model / 2.5：
Information Classes / 2.5.1：
Agreement State / 2.5.2：
Qualification State / 2.5.3：
Satisfaction State / 2.5.4：
Information Model Constraints / 2.5.5：
Generic Process Details / 2.6：
Agreement Process / 2.6.1：
Analyse and Model / 2.6.2：
Derive Requirements and Qualification Strategy Fig. 2.1.3 Portrays the Process for Deriving Requirements and Qualification Strategy / 2.6.3：
Summary / 2.7：
System Modelling for Requirements Engineering / 3：
Representations for Requirements Engineering / 3.1：
Data Flow Diagrams / 3.2.1：
Entity-Relationship Diagrams / 3.2.2：
Statecharts / 3.2.3：
Object-Oriented Approaches / 3.2.4：
Methods / 3.3：
Viewpoint Methods / 3.3.1：
Object-Oriented Methods / 3.3.2：
The UML Notation / 3.3.3：
Formal Methods / 3.3.4：
Writing and Reviewing Requirements / 3.4：
Requirements for Requirements / 4.1：
Structuring Requirements Documents / 4.3：
Key Requirements / 4.4：
Using Attributes / 4.5：
Ensuring Consistency Across Requirements / 4.6：
Value of a Requirement / 4.7：
The Language of Requirements / 4.8：
Requirement Boilerplates / 4.9：
Granularity of Requirements / 4.10：
Criteria for Writing Requirements Statements / 4.11：
Requirements Engineering in the Problem Domain / 4.12：
What is the Problem Domain? / 5.1：
Instantiating the Generic Process / 5.2：
Agree Requirements with Customer / 5.3：
Analyse & Model / 5.4：
Identify Stakeholders / 5.4.1：
Create Use Scenarios / 5.4.2：
Scoping the System / 5.4.3：
Derive Requirements / 5.5：
Define Structure / 5.5.1：
Capture Requirements / 5.5.2：
Define Acceptance Criteria / 5.5.3：
Define Qualification Strategy / 5.5.4：
Requirements Engineering in the Solution Domain / 5.6：
What is the Solution Domain / 6.1：
Engineering Requirements from Stakeholder Requirements to System Requirements / 6.2：
Producing the System Model / 6.2.1：
Creating System Models to Derive System Requirements / 6.2.2：
Banking Example / 6.2.3：
Car Example / 6.2.4：
Deriving Requirements from a System Model / 6.2.5：
Agreeing the System Requirements with the Design Team / 6.2.6：
Engineering Requirements from System Requirements to Subsystems / 6.3：
Creating a System Architecture Model / 6.3.1：
Deriving Requirements from an Architectural Design Model / 6.3.2：
Other Transformations Using a Design Architecture / 6.4：
Advanced Traceability / 6.5：
Elementary Traceability / 7.1：
Satisfaction Arguments / 7.3：
Requirements Allocation / 7.4：
Reviewing Traceability / 7.5：
The Language of Satisfaction Arguments / 7.6：
Rich Traceability Analysis / 7.7：
Rich Traceability for Qualification / 7.8：
Implementing Rich Traceability / 7.9：
Single-Layer Rich Traceability / 7.9.1：
Multi-Layer Rich Traceability / 7.9.2：
Design Documents / 7.10：
Metrics for Traceability / 7.11：
Breadth / 7.11.1：
Depth / 7.11.2：
Growth / 7.11.3：
Balance / 7.11.4：
Latent Change / 7.11.5：
Management Aspects of Requirements Engineering / 7.12：
Introduction to Management / 8.1：
Requirements Management Problems / 8.2：
Summary of Requirement Management Problems / 8.2.1：
Managing Requirements in an Acquisition Organisation / 8.3：
Planning / 8.3.1：
Monitoring / 8.3.2：
Changes / 8.3.3：
Supplier Organisations / 8.4：
Bid Management / 8.4.1：
Development / 8.4.2：
Product Organisations / 8.5：
DOORS: A Tool to Manage Requirements / 8.5.1：
The Case for Requirements Management / 9.1：
DOORS Architecture / 9.3：
Projects, Modules and Objects / 9.4：
DOORS Database Window / 9.4.1：
Formal Modules / 9.4.2：
Objects / 9.4.3：
Graphical Objects / 9.4.4：
Tables / 9.4.5：
History and Version Control / 9.5：
History / 9.5.1：
Baselining / 9.5.2：
Attributes and Views / 9.6：
Attributes / 9.6.1：
Views / 9.6.2：
Traceability / 9.7：
Links / 9.7.1：
Traceability Reports / 9.7.2：
Import and Export / 9.8：
UML Modelling with DOORS/Analyst / 9.9：
Bibliography / 9.10：
Index
Introduction / 1：
Introduction to Requirements / 1.1：
Introduction to Systems Engineering / 1.2：
33.

電子ブック
ＥＢ
33. Requirements Engineering
Elizabeth Hull, Jeremy Dick, Ken Jackson
出版情報: SpringerLink Books - AutoHoldings , Springer London, 2011
所蔵情報: loading…
目次情報: 続きを見る
Introduction / 1：
Introduction to Requirements / 1.1：
Introduction to Systems Engineering / 1.2：
Defining Requirements Engineering / 1.3：
Definition of a Requirement / 1.3.1：
Definition of a Stakeholder / 1.3.2：
Definition of Requirements Engineering / 1.3.3：
Requirements and Quality / 1.4：
Requirements and the Lifecycle / 1.5：
Requirements Tracing / 1.6：
Requirements and Modelling / 1.7：
Requirements and Testing / 1.8：
Requirements in the Problem and Solution Domains / 1.9：
How to Read this Book / 1.10：
A Generic Process for Requirements Engineering / 2：
Developing Systems / 2.1：
Generic Process Context / 2.3：
Input Requirements and Derived Requirements / 2.3.1：
Acceptance Criteria and Qualification Strategy / 2.3.2：
Generic Process Introduction / 2.4：
Ideal Development / 2.4.1：
Development in the Context of Change / 2.4.2：
Generic Process Information Model / 2.5：
Information Classes / 2.5.1：
Agreement State / 2.5.2：
Qualification State / 2.5.3：
Satisfaction State / 2.5.4：
Information Model Constraints / 2.5.5：
Generic Process Details / 2.6：
Agreement Process / 2.6.1：
Analyse and Model / 2.6.2：
Derive Requirements and Qualification Strategy Fig. 2.1.3 Portrays the Process for Deriving Requirements and Qualification Strategy / 2.6.3：
Summary / 2.7：
System Modelling for Requirements Engineering / 3：
Representations for Requirements Engineering / 3.1：
Data Flow Diagrams / 3.2.1：
Entity-Relationship Diagrams / 3.2.2：
Statecharts / 3.2.3：
Object-Oriented Approaches / 3.2.4：
Methods / 3.3：
Viewpoint Methods / 3.3.1：
Object-Oriented Methods / 3.3.2：
The UML Notation / 3.3.3：
Formal Methods / 3.3.4：
Writing and Reviewing Requirements / 3.4：
Requirements for Requirements / 4.1：
Structuring Requirements Documents / 4.3：
Key Requirements / 4.4：
Using Attributes / 4.5：
Ensuring Consistency Across Requirements / 4.6：
Value of a Requirement / 4.7：
The Language of Requirements / 4.8：
Requirement Boilerplates / 4.9：
Granularity of Requirements / 4.10：
Criteria for Writing Requirements Statements / 4.11：
Requirements Engineering in the Problem Domain / 4.12：
What is the Problem Domain? / 5.1：
Instantiating the Generic Process / 5.2：
Agree Requirements with Customer / 5.3：
Analyse & Model / 5.4：
Identify Stakeholders / 5.4.1：
Create Use Scenarios / 5.4.2：
Scoping the System / 5.4.3：
Derive Requirements / 5.5：
Define Structure / 5.5.1：
Capture Requirements / 5.5.2：
Define Acceptance Criteria / 5.5.3：
Define Qualification Strategy / 5.5.4：
Requirements Engineering in the Solution Domain / 5.6：
What is the Solution Domain / 6.1：
Engineering Requirements from Stakeholder Requirements to System Requirements / 6.2：
Producing the System Model / 6.2.1：
Creating System Models to Derive System Requirements / 6.2.2：
Banking Example / 6.2.3：
Car Example / 6.2.4：
Deriving Requirements from a System Model / 6.2.5：
Agreeing the System Requirements with the Design Team / 6.2.6：
Engineering Requirements from System Requirements to Subsystems / 6.3：
Creating a System Architecture Model / 6.3.1：
Deriving Requirements from an Architectural Design Model / 6.3.2：
Other Transformations Using a Design Architecture / 6.4：
Advanced Traceability / 6.5：
Elementary Traceability / 7.1：
Satisfaction Arguments / 7.3：
Requirements Allocation / 7.4：
Reviewing Traceability / 7.5：
The Language of Satisfaction Arguments / 7.6：
Rich Traceability Analysis / 7.7：
Rich Traceability for Qualification / 7.8：
Implementing Rich Traceability / 7.9：
Single-Layer Rich Traceability / 7.9.1：
Multi-Layer Rich Traceability / 7.9.2：
Design Documents / 7.10：
Metrics for Traceability / 7.11：
Breadth / 7.11.1：
Depth / 7.11.2：
Growth / 7.11.3：
Balance / 7.11.4：
Latent Change / 7.11.5：
Management Aspects of Requirements Engineering / 7.12：
Introduction to Management / 8.1：
Requirements Management Problems / 8.2：
Summary of Requirement Management Problems / 8.2.1：
Managing Requirements in an Acquisition Organisation / 8.3：
Planning / 8.3.1：
Monitoring / 8.3.2：
Changes / 8.3.3：
Supplier Organisations / 8.4：
Bid Management / 8.4.1：
Development / 8.4.2：
Product Organisations / 8.5：
DOORS: A Tool to Manage Requirements / 8.5.1：
The Case for Requirements Management / 9.1：
DOORS Architecture / 9.3：
Projects, Modules and Objects / 9.4：
DOORS Database Window / 9.4.1：
Formal Modules / 9.4.2：
Objects / 9.4.3：
Graphical Objects / 9.4.4：
Tables / 9.4.5：
History and Version Control / 9.5：
History / 9.5.1：
Baselining / 9.5.2：
Attributes and Views / 9.6：
Attributes / 9.6.1：
Views / 9.6.2：
Traceability / 9.7：
Links / 9.7.1：
Traceability Reports / 9.7.2：
Import and Export / 9.8：
UML Modelling with DOORS/Analyst / 9.9：
Bibliography / 9.10：
Index
Introduction / 1：
Introduction to Requirements / 1.1：
Introduction to Systems Engineering / 1.2：
34.

電子ブック
ＥＢ
34. TestGoal
Derk-Jan Grood, Derk-Jan De Grood
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Result-driven Testing / 1：
The Importance of IT / 1.1：
A Statement about Quality / 1.2：
The Perception of Testing / 1.3：
A Common Goal / 1.4：
Tying in with the Business / 1.5：
Focus on the Goal / 1.6：
TestGoal and the Ten Test Principles / 2：
Test Principles / 2.1：
Focus on Result / 2.2：
Build Trust / 2.3：
Take Responsibility / 2.4：
Master the Testing Profession / 2.5：
Build Bridges / 2.6：
Test in Phases / 2.7：
Facilitate the Entire Product Life Cycle / 2.8：
Provide Overview and Insight / 2.9：
Ensure Reusability / 2.10：
Keep in Mind: Testing is Fun / 2.11：
Applying the Test Principles / 2.12：
Test Expertise / 3：
The Test Manager / 3.1：
The Test Coordinator / 3.2：
The Test Analyst / 3.3：
The Test Engineer / 3.4：
The Test Specialist / 3.5：
The Approach / 4：
Context of the Test Project / 4.1：
Test Levels / 4.2：
The Details of the Test Project / 4.3：
The Step Plan / 4.3.1：
Sequence of Activities / 4.3.2：
Testing a New Program / 4.4：
Step 1: Goal / 4.4.1：
Step 2: Approach / 4.4.2：
Step 3: Design / 4.4.3：
Step 4: Set up / 4.4.4：
Step 5: Execution / 4.4.5：
Step 6: Assurance / 4.4.6：
Goal (Information and Communication) / 4.4.7：
Review and Acceptance / 4.4.8：
Testing in a Maintenance Environment / 4.5：
Testing Conformity and Interoperability / 4.6：
Introduction / 4.6.1：
Applying the Step Plan / 4.6.2：
Certification Tests / 4.6.3：
Testing Performance / 4.7：
Test Design Techniques / 4.7.1：
Test Tools / 4.7.4：
Dependencies / 4.7.5：
Testing Security / 4.8：
Approach / 4.8.1：
Getting Started / 4.8.3：
Goal / Step 1：
Assessing the Anticipated Goal / 6：
Aim of the Assessment / 6.1：
Goal Description / 6.3：
Information Gathering / 6.4：
Product Development / 6.4.1：
People / 6.4.2：
Guidelines and Documentation / 6.4.3：
Test Risk Analysis / Step 2：
The 1D Test Risk Analysis / 7.1：
Identify Stakeholders and Kick-off / 7.2.1：
Determine the Functions and Areas of Attention / 7.2.3：
Determine the Relative Importance / 7.2.4：
Process the Data / 7.2.5：
Agree on the TRA / 7.2.6：
The 2D Test Risk Analysis / 7.3：
Establish the Risks / 7.3.1：
Data Processing / 7.3.4：
Generic Test Strategy / 7.3.5：
The Generic Test Strategy / 8.1：
Test Strategy in the DTP and MTP / 8.3：
Test Budget and Planning / 9：
Create the Test Budget / 9.1：
General / 9.2.1：
Work Breakdown Structure / 9.2.2：
Assessing the Requisites / 9.2.3：
Establishing the Budget / 9.2.4：
Test Planning / 9.3：
Generic Planning / 9.3.1：
Detailed Planning / 9.3.2：
Key Indicators / 9.4：
Test Plan / 10：
Description of the Assignment / 10.1：
Test Base / 10.3：
Test Strategy / 10.4：
Description of the Test Strategy / 10.4.1：
Test risk analysis / 10.4.2：
Quality Attributes / 10.4.3：
Strategy Matrix / 10.4.4：
Technique Matrix / 10.4.5：
Previous and Next Phases / 10.4.6：
Test Environment / 10.4.7：
Assuring the Quality of the Test Project / 10.4.8：
Release Advice / 10.4.9：
Change and Error Management / 10.4.10：
Transfer / 10.4.11：
Planning / 10.5：
Test Organization / 10.6：
Organization Chart / 10.6.1：
Responsibilities / 10.6.2：
Meeting Structures / 10.6.3：
Deliverables / 10.7：
Requisites for the Test Process / 10.8：
Changes and Deviations / 10.9：
Design / Step 3：
Sanity Check / 11：
Filling out the Sanity Check Checklist / 11.1：
Continuous Learning / 11.3：
Test Base Review / 11.4：
Registration / 11.5：
Formal Review and Inspection Procedures / 11.6：
Logical Test Design / 12：
Use Test Design Techniques Cleverly / 12.1：
Little Experience with Test Design Techniques? / 12.4：
No Test Design Techniques / 12.5：
Using Test Design Techniques / 12.6：
Syntax Testing / 12.6.1：
EP: Equivalence Partitioning / 12.6.2：
BVA: Boundary Value Analysis / 12.6.3：
C/E: Cause-effect Graphing / 12.6.4：
State Transition / 12.6.5：
CRUD Testing / 12.6.6：
PCT: Process Cycle Test / AT: Algorithm Test / 12.6.7：
Load Tests / 12.6.8：
Stress Testing / 12.6.9：
Reliability Testing / 12.6.10：
Concurrency Tests / 12.6.11：
HT: Heuristic Testing / 12.6.12：
ET: Exploratory Testing / 12.6.13：
Test Design Techniques and Security Testing / 12.7：
The Physical Test Design / 13：
Relationship Between the TRA and the Logical Test Design / 13.1：
Physical Test Case / 13.3：
Test Actions / 13.4：
The Physical Test Scenario / 13.5：
Test Data / 13.6：
Test Data Elements / 14：
Test Data Repository / 14.2：
Live Data Versus Test Data / 14.3：
Test Data Management Strategy / 14.4：
Input from the Application / 14.4.1：
Input from the Database / 14.4.2：
Closed Loop / 14.4.3：
Including Data in the Physical Test Design / 14.5：
Automated Tests / 14.6：
Test Data and Exploratory Testing / 14.7：
Back-up and Restore / 14.8：
Determine the Requirements of the Test Environment / 15：
Module Tests and Module Integration Tests / 15.2.1：
System Tests / 15.2.2：
Functional Acceptation Tests / 15.2.3：
User Acceptance Tests / 15.2.4：
Production Acceptance Tests / 15.2.5：
Chain Tests / 15.2.6：
Pilot / 15.2.7：
Performance Tests / 15.2.8：
Security Tests / 15.2.9：
Training Purposes / 15.2.10：
Test Environment Requirements Checklist / 15.3：
Setting up the Test Environment / 15.4：
Configuration and Smoke Test / 15.5：
Configuring the Test Environment / 15.5.1：
Smoke Test / 15.5.2：
Maintaining the Test Environment / 15.6：
Configuration Management / 15.6.1：
Release Management / 15.6.2：
Set up / 15.6.3：
Test Automation / 16：
What is Test Automation? / 16.1：
Dynamic Test Tools / 16.3：
Additional Testing Possibilities / 16.3.1：
Time Saving / 16.3.2：
Log files / 16.3.3：
Comparing Results / 16.3.4：
Extensive Repeatability / 16.3.5：
Static Test Tools / 16.4：
Supporting Tools / 16.5：
Test Automation: Yes/No / 16.6：
Business Case / 16.6.1：
Making a Well-Informed Decision / 16.6.2：
Developing Test Scripts / 16.7：
Record and Playback / 16.7.1：
Programming Test Scripts / 16.7.2：
Automated Testing for Systems with More Than One Interface / 16.8：
Filling out the Checklist / 17：
Maintaining the Checklist / 17.3：
Execution / Step 5：
Test Execution / 18：
Test Execution and its Activities / 18.1：
Activities During the Test Execution / 18.2：
Test Run and Regression Tests / 18.3：
Leaving the Beaten Track / 18.4：
When is Testing Finished? / 18.5：
Error Logging and Management / 19：
Filling out the Error Log / 19.1：
Error Attributes / 19.3：
Error Management / 19.4：
Test Reporting / 20：
Elements in the Test Report / 20.1：
Scope / 20.2.1：
Hour Estimate / 20.2.2：
Project Risks and Bottlenecks / 20.2.4：
Product Status / 20.2.5：
Completed Versus Planned Tests / 20.2.6：
Error Status / 20.2.7：
Defect Detection Rate / 20.2.8：
Open Errors / 20.2.9：
Test Result by Risk Category or Test Cluster / 20.2.10：
Test Progress - Executed Versus Planned Tests / 20.2.11：
Outstanding Product Risks / 20.2.12：
The Dashboard / 20.3：
Clarity of the Test Report / 20.4：
Assurance / Step 6：
Evaluating the Test Project / 21：
Purpose of the Evaluation / 21.2.1：
Points of Attention / 21.2.2：
Lessons Learned Report / 21.2.3：
Determining the Regression Test Set / 21.3：
Archiving and Securing the Testware / 21.4：
Handover / 21.5：
Discharging the Test Team / 21.6：
Checklist: Sanity Check on the Design / Appendix A：
Checklist: Sanity Check on the Testware / Appendix B：
Checklist: Checklist smoke test system / Appendix C：
Checklist: Test charter exploratory testing / Appendix D：
Glossary / Appendix E：
References
Index
Result-driven Testing / 1：
The Importance of IT / 1.1：
A Statement about Quality / 1.2：
35.

電子ブック
ＥＢ
35. TestGoal
Derk-Jan Grood, Derk-Jan De Grood
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Result-driven Testing / 1：
The Importance of IT / 1.1：
A Statement about Quality / 1.2：
The Perception of Testing / 1.3：
A Common Goal / 1.4：
Tying in with the Business / 1.5：
Focus on the Goal / 1.6：
TestGoal and the Ten Test Principles / 2：
Test Principles / 2.1：
Focus on Result / 2.2：
Build Trust / 2.3：
Take Responsibility / 2.4：
Master the Testing Profession / 2.5：
Build Bridges / 2.6：
Test in Phases / 2.7：
Facilitate the Entire Product Life Cycle / 2.8：
Provide Overview and Insight / 2.9：
Ensure Reusability / 2.10：
Keep in Mind: Testing is Fun / 2.11：
Applying the Test Principles / 2.12：
Test Expertise / 3：
The Test Manager / 3.1：
The Test Coordinator / 3.2：
The Test Analyst / 3.3：
The Test Engineer / 3.4：
The Test Specialist / 3.5：
The Approach / 4：
Context of the Test Project / 4.1：
Test Levels / 4.2：
The Details of the Test Project / 4.3：
The Step Plan / 4.3.1：
Sequence of Activities / 4.3.2：
Testing a New Program / 4.4：
Step 1: Goal / 4.4.1：
Step 2: Approach / 4.4.2：
Step 3: Design / 4.4.3：
Step 4: Set up / 4.4.4：
Step 5: Execution / 4.4.5：
Step 6: Assurance / 4.4.6：
Goal (Information and Communication) / 4.4.7：
Review and Acceptance / 4.4.8：
Testing in a Maintenance Environment / 4.5：
Testing Conformity and Interoperability / 4.6：
Introduction / 4.6.1：
Applying the Step Plan / 4.6.2：
Certification Tests / 4.6.3：
Testing Performance / 4.7：
Test Design Techniques / 4.7.1：
Test Tools / 4.7.4：
Dependencies / 4.7.5：
Testing Security / 4.8：
Approach / 4.8.1：
Getting Started / 4.8.3：
Goal / Step 1：
Assessing the Anticipated Goal / 6：
Aim of the Assessment / 6.1：
Goal Description / 6.3：
Information Gathering / 6.4：
Product Development / 6.4.1：
People / 6.4.2：
Guidelines and Documentation / 6.4.3：
Test Risk Analysis / Step 2：
The 1D Test Risk Analysis / 7.1：
Identify Stakeholders and Kick-off / 7.2.1：
Determine the Functions and Areas of Attention / 7.2.3：
Determine the Relative Importance / 7.2.4：
Process the Data / 7.2.5：
Agree on the TRA / 7.2.6：
The 2D Test Risk Analysis / 7.3：
Establish the Risks / 7.3.1：
Data Processing / 7.3.4：
Generic Test Strategy / 7.3.5：
The Generic Test Strategy / 8.1：
Test Strategy in the DTP and MTP / 8.3：
Test Budget and Planning / 9：
Create the Test Budget / 9.1：
General / 9.2.1：
Work Breakdown Structure / 9.2.2：
Assessing the Requisites / 9.2.3：
Establishing the Budget / 9.2.4：
Test Planning / 9.3：
Generic Planning / 9.3.1：
Detailed Planning / 9.3.2：
Key Indicators / 9.4：
Test Plan / 10：
Description of the Assignment / 10.1：
Test Base / 10.3：
Test Strategy / 10.4：
Description of the Test Strategy / 10.4.1：
Test risk analysis / 10.4.2：
Quality Attributes / 10.4.3：
Strategy Matrix / 10.4.4：
Technique Matrix / 10.4.5：
Previous and Next Phases / 10.4.6：
Test Environment / 10.4.7：
Assuring the Quality of the Test Project / 10.4.8：
Release Advice / 10.4.9：
Change and Error Management / 10.4.10：
Transfer / 10.4.11：
Planning / 10.5：
Test Organization / 10.6：
Organization Chart / 10.6.1：
Responsibilities / 10.6.2：
Meeting Structures / 10.6.3：
Deliverables / 10.7：
Requisites for the Test Process / 10.8：
Changes and Deviations / 10.9：
Design / Step 3：
Sanity Check / 11：
Filling out the Sanity Check Checklist / 11.1：
Continuous Learning / 11.3：
Test Base Review / 11.4：
Registration / 11.5：
Formal Review and Inspection Procedures / 11.6：
Logical Test Design / 12：
Use Test Design Techniques Cleverly / 12.1：
Little Experience with Test Design Techniques? / 12.4：
No Test Design Techniques / 12.5：
Using Test Design Techniques / 12.6：
Syntax Testing / 12.6.1：
EP: Equivalence Partitioning / 12.6.2：
BVA: Boundary Value Analysis / 12.6.3：
C/E: Cause-effect Graphing / 12.6.4：
State Transition / 12.6.5：
CRUD Testing / 12.6.6：
PCT: Process Cycle Test / AT: Algorithm Test / 12.6.7：
Load Tests / 12.6.8：
Stress Testing / 12.6.9：
Reliability Testing / 12.6.10：
Concurrency Tests / 12.6.11：
HT: Heuristic Testing / 12.6.12：
ET: Exploratory Testing / 12.6.13：
Test Design Techniques and Security Testing / 12.7：
The Physical Test Design / 13：
Relationship Between the TRA and the Logical Test Design / 13.1：
Physical Test Case / 13.3：
Test Actions / 13.4：
The Physical Test Scenario / 13.5：
Test Data / 13.6：
Test Data Elements / 14：
Test Data Repository / 14.2：
Live Data Versus Test Data / 14.3：
Test Data Management Strategy / 14.4：
Input from the Application / 14.4.1：
Input from the Database / 14.4.2：
Closed Loop / 14.4.3：
Including Data in the Physical Test Design / 14.5：
Automated Tests / 14.6：
Test Data and Exploratory Testing / 14.7：
Back-up and Restore / 14.8：
Determine the Requirements of the Test Environment / 15：
Module Tests and Module Integration Tests / 15.2.1：
System Tests / 15.2.2：
Functional Acceptation Tests / 15.2.3：
User Acceptance Tests / 15.2.4：
Production Acceptance Tests / 15.2.5：
Chain Tests / 15.2.6：
Pilot / 15.2.7：
Performance Tests / 15.2.8：
Security Tests / 15.2.9：
Training Purposes / 15.2.10：
Test Environment Requirements Checklist / 15.3：
Setting up the Test Environment / 15.4：
Configuration and Smoke Test / 15.5：
Configuring the Test Environment / 15.5.1：
Smoke Test / 15.5.2：
Maintaining the Test Environment / 15.6：
Configuration Management / 15.6.1：
Release Management / 15.6.2：
Set up / 15.6.3：
Test Automation / 16：
What is Test Automation? / 16.1：
Dynamic Test Tools / 16.3：
Additional Testing Possibilities / 16.3.1：
Time Saving / 16.3.2：
Log files / 16.3.3：
Comparing Results / 16.3.4：
Extensive Repeatability / 16.3.5：
Static Test Tools / 16.4：
Supporting Tools / 16.5：
Test Automation: Yes/No / 16.6：
Business Case / 16.6.1：
Making a Well-Informed Decision / 16.6.2：
Developing Test Scripts / 16.7：
Record and Playback / 16.7.1：
Programming Test Scripts / 16.7.2：
Automated Testing for Systems with More Than One Interface / 16.8：
Filling out the Checklist / 17：
Maintaining the Checklist / 17.3：
Execution / Step 5：
Test Execution / 18：
Test Execution and its Activities / 18.1：
Activities During the Test Execution / 18.2：
Test Run and Regression Tests / 18.3：
Leaving the Beaten Track / 18.4：
When is Testing Finished? / 18.5：
Error Logging and Management / 19：
Filling out the Error Log / 19.1：
Error Attributes / 19.3：
Error Management / 19.4：
Test Reporting / 20：
Elements in the Test Report / 20.1：
Scope / 20.2.1：
Hour Estimate / 20.2.2：
Project Risks and Bottlenecks / 20.2.4：
Product Status / 20.2.5：
Completed Versus Planned Tests / 20.2.6：
Error Status / 20.2.7：
Defect Detection Rate / 20.2.8：
Open Errors / 20.2.9：
Test Result by Risk Category or Test Cluster / 20.2.10：
Test Progress - Executed Versus Planned Tests / 20.2.11：
Outstanding Product Risks / 20.2.12：
The Dashboard / 20.3：
Clarity of the Test Report / 20.4：
Assurance / Step 6：
Evaluating the Test Project / 21：
Purpose of the Evaluation / 21.2.1：
Points of Attention / 21.2.2：
Lessons Learned Report / 21.2.3：
Determining the Regression Test Set / 21.3：
Archiving and Securing the Testware / 21.4：
Handover / 21.5：
Discharging the Test Team / 21.6：
Checklist: Sanity Check on the Design / Appendix A：
Checklist: Sanity Check on the Testware / Appendix B：
Checklist: Checklist smoke test system / Appendix C：
Checklist: Test charter exploratory testing / Appendix D：
Glossary / Appendix E：
References
Index
Result-driven Testing / 1：
The Importance of IT / 1.1：
A Statement about Quality / 1.2：
36.

電子ブック
ＥＢ
36. Model-Driven Testing
Paul; Dai, Zhen Ru; Grabowski, Jens; Haugen, ?ystein; Schieferdecker, Ina; Williams, Clay Baker, Paul Baker, Zhen Ru Dai, Jens Grabowski, ??ystein Haugen, Ina Schieferdecker, Clay Williams
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Introduction
Foundations / Part I：
Model-Based Testing / 1：
The Software Development Process / 1.1：
UML and UTP in System Development / 1.2：
Model-Based Test Development / 1.3：
Black-Box Testing Approaches / 1.3.1：
White-Box Testing Approaches / 1.3.2：
Automatic Test Generation / 1.3.3：
Basics / 2：
UML Overview / 2.1：
Introduction to Class Models / 2.1.1：
Introduction to Use Cases / 2.1.2：
Introduction to Sequence Diagrams / 2.1.3：
Introduction to State Machines / 2.1.4：
Introduction to Activities / 2.1.5：
UTP Overview / 2.2：
Library Example Introduction / 3：
What Is a Library? / 3.1：
What Is Inside a Library? / 3.2：
Testing a Library / 3.3：
Functional Testing / Part II：
Overview
Unit Level Testing / 4：
UTP and Unit Level Testing / 4.1：
State Machines / 4.1.1：
Interactions / 4.1.2：
Activity Diagrams / 4.1.3：
Chapter Summary / 4.2：
Component and Integration Level Testing / 5：
Integration Strategies and Integration Level Testing / 5.1：
Test Configuration, Test Components, and Emulators / 5.2：
UTP and Integration Level Testing / 5.3：
System and Acceptance Level Testing / 5.4：
UTP and System Level Testing / 6.1：
Use Cases / 6.1.1：
Advanced Testing Concerns / 6.2：
Data-Driven Testing / 7：
UTP and Data-Driven Testing / 7.1：
Value Specification / 7.1.1：
Parameterization of Tests and Data Pools / 7.1.2：
Encoding and Decoding of Data / 7.1.3：
Real-Time and Performance Testing / 7.2：
Real-Time Testing Concerns / 8.1：
UTP and Real-Time Testing / 8.2：
Hard Real-Time Concerns / 8.2.1：
Soft Real-Time Concerns / 8.2.2：
Performance Testing Concerns / 8.3：
UTP and Performance Testing / 8.4：
Summary / 8.5：
Applications of UTP / Part IV：
User-Interface Testing / 9：
Issues in User-Interface Testing / 9.1：
Planning UI Test Activities / 9.2：
User Interface Context / 9.2.1：
Logical Aspects / 9.2.2：
Physical Aspects / 9.2.3：
Localization Aspects / 9.2.4：
UTP and User-Interface Testing / 9.3：
Test Context and Configuration / 9.3.1：
Using Interaction Diagrams / 9.3.2：
Usability Testing / 9.4：
Testing Service-Oriented Architecture Applications / 9.5：
Service-Oriented Architecture Overview / 10.1：
Service Orientation: Basic Concepts / 10.1.1：
Testing Concerns for SOA / 10.1.2：
UTP Test Specification for SOA Applications / 10.2：
Testing Individual Web Services / 10.2.1：
Testing Business Processes / 10.2.2：
Conclusion / 10.3：
Tools / Part V：
Tool Frameworks and Examples / 11：
Kinds of UTP Tools / 11.1：
Tool Interoperability / 11.2：
Executable UTP / 11.3：
Test Execution with JUnit / 12：
JUnit 4.0 Fundamentals / 12.1：
Annotations: A New Foundation for JUnit / 12.1.1：
Test Methods / 12.1.2：
Set up and Tear down / 12.1.3：
Assertions / 12.1.4：
Test Method Annotations / 12.1.5：
UTP to JUnit Mapping / 12.2：
UTP to JUnit Example / 12.3：
Test Execution with TTCN-3 / 12.4：
Fundamentals of TTCN-3 / 13.1：
Modules and Test Cases / 13.1.1：
Types and Values / 13.1.2：
Test Components and Test Behavior / 13.1.3：
UTP and TTCN-3 Relationship / 13.1.4：
UTP to TTCN-3 Mapping / 13.2：
UTP to TTCN-3 Example / 13.3：
Executing UTP Specifications via TTCN-3 Test Platforms / 13.4：
Representing TTCN-3 Test Suites by UTP / 13.5：
Appendixes / 13.6：
A UTP Reference Guide
Acronyms
References
Index
Introduction
Foundations / Part I：
Model-Based Testing / 1：
37.

電子ブック
ＥＢ
37. Model-Driven Testing
Paul; Dai, Zhen Ru; Grabowski, Jens; Haugen, Øystein; Schieferdecker, Ina; Williams, Clay Baker, Paul Baker, Zhen Ru Dai, Jens Grabowski, Øystein Haugen, Ina Schieferdecker, Clay Williams
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Introduction
Foundations / Part I：
Model-Based Testing / 1：
The Software Development Process / 1.1：
UML and UTP in System Development / 1.2：
Model-Based Test Development / 1.3：
Black-Box Testing Approaches / 1.3.1：
White-Box Testing Approaches / 1.3.2：
Automatic Test Generation / 1.3.3：
Basics / 2：
UML Overview / 2.1：
Introduction to Class Models / 2.1.1：
Introduction to Use Cases / 2.1.2：
Introduction to Sequence Diagrams / 2.1.3：
Introduction to State Machines / 2.1.4：
Introduction to Activities / 2.1.5：
UTP Overview / 2.2：
Library Example Introduction / 3：
What Is a Library? / 3.1：
What Is Inside a Library? / 3.2：
Testing a Library / 3.3：
Functional Testing / Part II：
Overview
Unit Level Testing / 4：
UTP and Unit Level Testing / 4.1：
State Machines / 4.1.1：
Interactions / 4.1.2：
Activity Diagrams / 4.1.3：
Chapter Summary / 4.2：
Component and Integration Level Testing / 5：
Integration Strategies and Integration Level Testing / 5.1：
Test Configuration, Test Components, and Emulators / 5.2：
UTP and Integration Level Testing / 5.3：
System and Acceptance Level Testing / 5.4：
UTP and System Level Testing / 6.1：
Use Cases / 6.1.1：
Advanced Testing Concerns / 6.2：
Data-Driven Testing / 7：
UTP and Data-Driven Testing / 7.1：
Value Specification / 7.1.1：
Parameterization of Tests and Data Pools / 7.1.2：
Encoding and Decoding of Data / 7.1.3：
Real-Time and Performance Testing / 7.2：
Real-Time Testing Concerns / 8.1：
UTP and Real-Time Testing / 8.2：
Hard Real-Time Concerns / 8.2.1：
Soft Real-Time Concerns / 8.2.2：
Performance Testing Concerns / 8.3：
UTP and Performance Testing / 8.4：
Summary / 8.5：
Applications of UTP / Part IV：
User-Interface Testing / 9：
Issues in User-Interface Testing / 9.1：
Planning UI Test Activities / 9.2：
User Interface Context / 9.2.1：
Logical Aspects / 9.2.2：
Physical Aspects / 9.2.3：
Localization Aspects / 9.2.4：
UTP and User-Interface Testing / 9.3：
Test Context and Configuration / 9.3.1：
Using Interaction Diagrams / 9.3.2：
Usability Testing / 9.4：
Testing Service-Oriented Architecture Applications / 9.5：
Service-Oriented Architecture Overview / 10.1：
Service Orientation: Basic Concepts / 10.1.1：
Testing Concerns for SOA / 10.1.2：
UTP Test Specification for SOA Applications / 10.2：
Testing Individual Web Services / 10.2.1：
Testing Business Processes / 10.2.2：
Conclusion / 10.3：
Tools / Part V：
Tool Frameworks and Examples / 11：
Kinds of UTP Tools / 11.1：
Tool Interoperability / 11.2：
Executable UTP / 11.3：
Test Execution with JUnit / 12：
JUnit 4.0 Fundamentals / 12.1：
Annotations: A New Foundation for JUnit / 12.1.1：
Test Methods / 12.1.2：
Set up and Tear down / 12.1.3：
Assertions / 12.1.4：
Test Method Annotations / 12.1.5：
UTP to JUnit Mapping / 12.2：
UTP to JUnit Example / 12.3：
Test Execution with TTCN-3 / 12.4：
Fundamentals of TTCN-3 / 13.1：
Modules and Test Cases / 13.1.1：
Types and Values / 13.1.2：
Test Components and Test Behavior / 13.1.3：
UTP and TTCN-3 Relationship / 13.1.4：
UTP to TTCN-3 Mapping / 13.2：
UTP to TTCN-3 Example / 13.3：
Executing UTP Specifications via TTCN-3 Test Platforms / 13.4：
Representing TTCN-3 Test Suites by UTP / 13.5：
Appendixes / 13.6：
A UTP Reference Guide
Acronyms
References
Index
Introduction
Foundations / Part I：
Model-Based Testing / 1：
38.

電子ブック
ＥＢ
38. Essential Software Architecture
Ian Gorton
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2011
所蔵情報: loading…
目次情報: 続きを見る
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
Architecture Defines Structure / 1.2.1：
Architecture Specifies Component Communication / 1.2.2：
Architecture Addresses Nonfunctional Requirements / 1.3：
Architecture Is an Abstraction / 1.3.1：
Architecture Views / 1.3.2：
What Does a Software Architect Do? / 1.4：
Architectures and Technologies / 1.5：
Architect Title Soup / 1.6：
Summary / 1.7：
Further Reading / 1.8：
General Architecture / 1.8.1：
Architecture Requirements / 1.8.2：
Architecture Patterns / 1.8.3：
Technology Comparisons / 1.8.4：
Enterprise Architecture / 1.8.5：
Introducing the Case Study / 2：
Overview / 2.1：
The ICDE System / 2.2：
Project Context / 2.3：
Business Goals / 2.4：
Constraints / 2.5：
Software Quality Attributes / 2.6：
Quality Attributes / 3.1：
Performance / 3.2：
Throughput / 3.2.1：
Response Time / 3.2.2：
Deadlines / 3.2.3：
Performance for the ICDE System / 3.2.4：
Scalability / 3.3：
Request Load / 3.3.1：
Simultaneous Connections / 3.3.2：
Data Size / 3.3.3：
Deployment / 3.3.4：
Some Thoughts on Scalability / 3.3.5：
Scalability for the ICDE Application / 3.3.6：
Modifiability / 3.4：
Modifiability for the ICDE Application / 3.4.1：
Security / 3.5：
Security for the ICDE Application / 3.5.1：
Availability / 3.6：
Availability for the ICDE Application / 3.6.1：
Integration / 3.7：
Integration for the ICDE Application / 3.7.1：
Other Quality Attributes / 3.8：
Design Trade-Offs / 3.9：
An Introduction to Middleware Architectures and Technologies / 3.10：
Introduction / 4.1：
Middleware Technology Classification / 4.2：
Distributed Objects / 4.3：
Message-Oriented Middleware / 4.4：
Mom Basics / 4.4.1：
Exploiting Mom Advanced Features / 4.4.2：
Publish-Subscribe / 4.4.3：
Application Servers / 4.5：
Enterprise JavaBeans / 4.5.1：
Ejb Component Model / 4.5.2：
Stateless Session Bean Programming Example / 4.5.3：
Message-Driven Bean Programming Example / 4.5.4：
Responsibilities of the Ejb Container / 4.5.5：
Some Thoughts / 4.5.6：
Corba / 4.6：
Service-Oriented Architectures and Technologies / 4.7.2：
Background / 5.1：
Service-Oriented Systems / 5.2：
Boundaries Are Explicit / 5.2.1：
Services Are Autonomous / 5.2.2：
Share Schemas and Contracts, Not Implementations / 5.2.3：
Service Compatibility Is Based on Policy / 5.2.4：
Web Services / 5.3：
Soap and Messaging / 5.4：
Uddi, Wsdl, and Metadata / 5.5：
Security, Transactions, and Reliability / 5.6：
Restful Web Services / 5.7：
Conclusion and Further Reading / 5.8：
Advanced Middleware Technologies / 6：
Message Brokers / 6.1：
Business Process Orchestration / 6.3：
Integration Architecture Issues / 6.4：
What Is an Enterprise Service Bus / 6.5：
A Software Architecture Process / 6.6：
Process Outline / 7.1：
Determine Architectural Requirements / 7.1.1：
Identifying Architecture Requirements / 7.1.2：
Prioritizing Architecture Requirements / 7.1.3：
Architecture Design / 7.2：
Choosing the Architecture Framework / 7.2.1：
Allocate Components / 7.2.2：
Validation / 7.3：
Using Scenarios / 7.3.3：
Prototyping / 7.3.2：
Summary and Further Reading / 7.4：
Documenting a Software Architecture / 8：
What to Document / 8.1：
Uml 2.0 / 8.3：
More on Component Diagrams / 8.4：
Architecture Documentation Template / 8.6：
Case Study Design / 8.7：
ICDE Technical Issues / 9.1：
Large Data / 9.2.1：
Notification / 9.2.2：
Data Abstraction / 9.2.3：
Platform and Distribution Issues / 9.2.4：
Api Issues / 9.2.5：
Discussion / 9.2.6：
ICDE Architecture Requirements / 9.3：
Overview of Key Objectives / 9.3.1：
Architecture Use Cases / 9.3.2：
Stakeholder Architecture Requirements / 9.3.3：
Nonfunctional Requirements / 9.3.4：
Risks / 9.3.6：
ICDE Solution / 9.4：
Architecture Overview / 9.4.1：
Structural Views / 9.4.3：
Behavioral Views / 9.4.4：
Implementation Issues / 9.4.5：
Architecture Analysis / 9.5：
Scenario Analysis / 9.5.1：
Middleware Case Study: Medici / 9.5.2：
Medici Background / 10.1：
Medici Hello World / 10.2：
Implementing Modules / 10.3：
MifProcessor / 10.3.1：
MifObjectProcessor / 10.3.2：
MifMessageProcessor / 10.3.3：
Module Properties / 10.3.4：
Endpoints and Transports / 10.4：
Connectors / 10.4.1：
Supported Transports / 10.4.2：
Medici Example / 10.5：
Initialize Pipeline / 10.5.1：
Chat Component / 10.5.2：
Implementation code / 10.5.3：
Component Builder / 10.6：
Looking Forward / 10.7：
The Challenges of Complexity / 11.1：
Business Process Complexity / 11.2.1：
Agility / 11.3：
Reduced Costs / 11.4：
What Next / 11.5：
The Semantic Web / 12：
ICDE and the Semantic Web / 12.1：
Automated, Distributed Integration and Collaboration / 12.2：
Creating and Using Metadata for the Semantic Web / 12.3：
Putting Semantics in the Web / 12.5：
Semantics for ICDE / 12.6：
Semantic Web Services / 12.7：
Continued Optimism / 12.8：
Aspect Oriented Architectures / 12.9：
Aspects for ICDE Development / 13.1：
Introduction to Aspect-Oriented Programming / 13.2：
Crosscutting Concerns / 13.2.1：
Managing Concerns with Aspects / 13.2.2：
Aop Syntax and Programming Model / 13.2.3：
Weaving / 13.2.4：
Example of a Cache Aspect / 13.3：
Aspect-Oriented Architectures / 13.4：
Architectural Aspects and Middleware / 13.5：
State-of-the-Art / 13.6：
Aspect Oriented Modeling in Uml / 13.6.1：
Aop Tools / 13.6.2：
Annotations and Aop / 13.6.3：
Performance Monitoring of ICDE with AspectWerkz / 13.7：
Conclusions / 13.8：
Model-Driven Architecture / 13.9：
Model-Driven Development for ICDE / 14.1：
What is Mda? / 14.2：
Why Mda? / 14.3：
Portability / 14.3.1：
Interoperability / 14.3.2：
Reusability / 14.3.3：
State-of-Art Practices and Tools / 14.4：
AndroMda / 14.4.1：
ArcStyler / 14.4.2：
Eclipse Modeling Framework / 14.4.3：
Mda and Software Architecture / 14.5：
Mda and Nonfunctional Requirements / 14.5.1：
Model Transformation and Software Architecture / 14.5.2：
Soa and Mda / 14.5.3：
Analytical Models are Models Too / 14.5.4：
Mda for ICDE Capacity Planning / 14.6：
Software Product Lines / 14.7：
Product Lines for ICDE / 15.1：
Benefiting from Spl Development / 15.2：
Product Line Architecture / 15.2.2：
Find and Understand Software / 15.3.1：
Bring Software into the Development Context / 15.3.2：
Invoke Software / 15.3.3：
Software Configuration Management for Reuse / 15.3.4：
Variation Mechanisms / 15.4：
Architecture-Level Variation Points / 15.4.1：
Design-Level Variation / 15.4.2：
File-Level Variation / 15.4.3：
Variation by Software Configuration Management / 15.4.4：
Product Line Architecture for ICDE / 15.4.5：
Adopting Software Product Line Development / 15.5：
Product Line Adoption Practice Areas / 15.5.1：
Product Line Adoption for ICDE / 15.5.2：
Ongoing Software Product Line Development / 15.6：
Change Control / 15.6.1：
Architectural Evolution for Spl Development / 15.6.2：
Product Line Development Practice Areas / 15.6.3：
Product Lines with ICDE / 15.6.4：
Index / 15.7：
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
39.

電子ブック
ＥＢ
39. Essential Software Architecture
Ian Gorton
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2011
所蔵情報: loading…
目次情報: 続きを見る
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
Architecture Defines Structure / 1.2.1：
Architecture Specifies Component Communication / 1.2.2：
Architecture Addresses Nonfunctional Requirements / 1.3：
Architecture Is an Abstraction / 1.3.1：
Architecture Views / 1.3.2：
What Does a Software Architect Do? / 1.4：
Architectures and Technologies / 1.5：
Architect Title Soup / 1.6：
Summary / 1.7：
Further Reading / 1.8：
General Architecture / 1.8.1：
Architecture Requirements / 1.8.2：
Architecture Patterns / 1.8.3：
Technology Comparisons / 1.8.4：
Enterprise Architecture / 1.8.5：
Introducing the Case Study / 2：
Overview / 2.1：
The ICDE System / 2.2：
Project Context / 2.3：
Business Goals / 2.4：
Constraints / 2.5：
Software Quality Attributes / 2.6：
Quality Attributes / 3.1：
Performance / 3.2：
Throughput / 3.2.1：
Response Time / 3.2.2：
Deadlines / 3.2.3：
Performance for the ICDE System / 3.2.4：
Scalability / 3.3：
Request Load / 3.3.1：
Simultaneous Connections / 3.3.2：
Data Size / 3.3.3：
Deployment / 3.3.4：
Some Thoughts on Scalability / 3.3.5：
Scalability for the ICDE Application / 3.3.6：
Modifiability / 3.4：
Modifiability for the ICDE Application / 3.4.1：
Security / 3.5：
Security for the ICDE Application / 3.5.1：
Availability / 3.6：
Availability for the ICDE Application / 3.6.1：
Integration / 3.7：
Integration for the ICDE Application / 3.7.1：
Other Quality Attributes / 3.8：
Design Trade-Offs / 3.9：
An Introduction to Middleware Architectures and Technologies / 3.10：
Introduction / 4.1：
Middleware Technology Classification / 4.2：
Distributed Objects / 4.3：
Message-Oriented Middleware / 4.4：
Mom Basics / 4.4.1：
Exploiting Mom Advanced Features / 4.4.2：
Publish-Subscribe / 4.4.3：
Application Servers / 4.5：
Enterprise JavaBeans / 4.5.1：
Ejb Component Model / 4.5.2：
Stateless Session Bean Programming Example / 4.5.3：
Message-Driven Bean Programming Example / 4.5.4：
Responsibilities of the Ejb Container / 4.5.5：
Some Thoughts / 4.5.6：
Corba / 4.6：
Service-Oriented Architectures and Technologies / 4.7.2：
Background / 5.1：
Service-Oriented Systems / 5.2：
Boundaries Are Explicit / 5.2.1：
Services Are Autonomous / 5.2.2：
Share Schemas and Contracts, Not Implementations / 5.2.3：
Service Compatibility Is Based on Policy / 5.2.4：
Web Services / 5.3：
Soap and Messaging / 5.4：
Uddi, Wsdl, and Metadata / 5.5：
Security, Transactions, and Reliability / 5.6：
Restful Web Services / 5.7：
Conclusion and Further Reading / 5.8：
Advanced Middleware Technologies / 6：
Message Brokers / 6.1：
Business Process Orchestration / 6.3：
Integration Architecture Issues / 6.4：
What Is an Enterprise Service Bus / 6.5：
A Software Architecture Process / 6.6：
Process Outline / 7.1：
Determine Architectural Requirements / 7.1.1：
Identifying Architecture Requirements / 7.1.2：
Prioritizing Architecture Requirements / 7.1.3：
Architecture Design / 7.2：
Choosing the Architecture Framework / 7.2.1：
Allocate Components / 7.2.2：
Validation / 7.3：
Using Scenarios / 7.3.3：
Prototyping / 7.3.2：
Summary and Further Reading / 7.4：
Documenting a Software Architecture / 8：
What to Document / 8.1：
Uml 2.0 / 8.3：
More on Component Diagrams / 8.4：
Architecture Documentation Template / 8.6：
Case Study Design / 8.7：
ICDE Technical Issues / 9.1：
Large Data / 9.2.1：
Notification / 9.2.2：
Data Abstraction / 9.2.3：
Platform and Distribution Issues / 9.2.4：
Api Issues / 9.2.5：
Discussion / 9.2.6：
ICDE Architecture Requirements / 9.3：
Overview of Key Objectives / 9.3.1：
Architecture Use Cases / 9.3.2：
Stakeholder Architecture Requirements / 9.3.3：
Nonfunctional Requirements / 9.3.4：
Risks / 9.3.6：
ICDE Solution / 9.4：
Architecture Overview / 9.4.1：
Structural Views / 9.4.3：
Behavioral Views / 9.4.4：
Implementation Issues / 9.4.5：
Architecture Analysis / 9.5：
Scenario Analysis / 9.5.1：
Middleware Case Study: Medici / 9.5.2：
Medici Background / 10.1：
Medici Hello World / 10.2：
Implementing Modules / 10.3：
MifProcessor / 10.3.1：
MifObjectProcessor / 10.3.2：
MifMessageProcessor / 10.3.3：
Module Properties / 10.3.4：
Endpoints and Transports / 10.4：
Connectors / 10.4.1：
Supported Transports / 10.4.2：
Medici Example / 10.5：
Initialize Pipeline / 10.5.1：
Chat Component / 10.5.2：
Implementation code / 10.5.3：
Component Builder / 10.6：
Looking Forward / 10.7：
The Challenges of Complexity / 11.1：
Business Process Complexity / 11.2.1：
Agility / 11.3：
Reduced Costs / 11.4：
What Next / 11.5：
The Semantic Web / 12：
ICDE and the Semantic Web / 12.1：
Automated, Distributed Integration and Collaboration / 12.2：
Creating and Using Metadata for the Semantic Web / 12.3：
Putting Semantics in the Web / 12.5：
Semantics for ICDE / 12.6：
Semantic Web Services / 12.7：
Continued Optimism / 12.8：
Aspect Oriented Architectures / 12.9：
Aspects for ICDE Development / 13.1：
Introduction to Aspect-Oriented Programming / 13.2：
Crosscutting Concerns / 13.2.1：
Managing Concerns with Aspects / 13.2.2：
Aop Syntax and Programming Model / 13.2.3：
Weaving / 13.2.4：
Example of a Cache Aspect / 13.3：
Aspect-Oriented Architectures / 13.4：
Architectural Aspects and Middleware / 13.5：
State-of-the-Art / 13.6：
Aspect Oriented Modeling in Uml / 13.6.1：
Aop Tools / 13.6.2：
Annotations and Aop / 13.6.3：
Performance Monitoring of ICDE with AspectWerkz / 13.7：
Conclusions / 13.8：
Model-Driven Architecture / 13.9：
Model-Driven Development for ICDE / 14.1：
What is Mda? / 14.2：
Why Mda? / 14.3：
Portability / 14.3.1：
Interoperability / 14.3.2：
Reusability / 14.3.3：
State-of-Art Practices and Tools / 14.4：
AndroMda / 14.4.1：
ArcStyler / 14.4.2：
Eclipse Modeling Framework / 14.4.3：
Mda and Software Architecture / 14.5：
Mda and Nonfunctional Requirements / 14.5.1：
Model Transformation and Software Architecture / 14.5.2：
Soa and Mda / 14.5.3：
Analytical Models are Models Too / 14.5.4：
Mda for ICDE Capacity Planning / 14.6：
Software Product Lines / 14.7：
Product Lines for ICDE / 15.1：
Benefiting from Spl Development / 15.2：
Product Line Architecture / 15.2.2：
Find and Understand Software / 15.3.1：
Bring Software into the Development Context / 15.3.2：
Invoke Software / 15.3.3：
Software Configuration Management for Reuse / 15.3.4：
Variation Mechanisms / 15.4：
Architecture-Level Variation Points / 15.4.1：
Design-Level Variation / 15.4.2：
File-Level Variation / 15.4.3：
Variation by Software Configuration Management / 15.4.4：
Product Line Architecture for ICDE / 15.4.5：
Adopting Software Product Line Development / 15.5：
Product Line Adoption Practice Areas / 15.5.1：
Product Line Adoption for ICDE / 15.5.2：
Ongoing Software Product Line Development / 15.6：
Change Control / 15.6.1：
Architectural Evolution for Spl Development / 15.6.2：
Product Line Development Practice Areas / 15.6.3：
Product Lines with ICDE / 15.6.4：
Index / 15.7：
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
40.

電子ブック
ＥＢ
40. Agile Software Development
Thomas Stober, Uwe Hansmann
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2010
所蔵情報: loading…
目次情報: 続きを見る
The Flaw in the Plan / 1：
The Delusive Perception of Having Anticipated Everything / 1.1：
Accept the Uncertainty and Adapt / 1.2：
Involving the Teams / 1.3：
In Search of Structure / 1.4：
Agile Software Development / 1.5：
Further Readings
Traditional Software Development / 2：
History of Project Management / 2.1：
Waterfall Approach / 2.2：
Requirements / 2.2.1：
Design Phase / 2.2.2：
Implementation / 2.2.3：
Testing / 2.2.4：
Support / 2.2.5：
Advantages and Disadvantages / 2.2.6：
Project Management Triangle / 2.3：
Modified Waterfall Models / 2.4：
Milestone and Regular Integration / 2.4.1：
Incremental Development / 2.4.2：
Overview of Agile Software Development / 3：
Lean Software Development / 3.1：
Project Management 2.0 / 3.2：
Agile Manifesto / 3.3：
Scrum / 3.4：
Test Driven Development / 3.5：
Extreme Programming / 3.6：
Rational Unified Process / 3.7：
Best Practices / 3.7.1：
The Phases / 3.7.2：
The Process / 3.7.3：
Agile Unified Process / 3.8：
Agile Model Driven Development / 3.9：
Tooling / 4：
Project Management Tools / 4.1：
Microsoft Solutions Framework for Agile Development / 4.1.1：
Jazz and Rational Team Concert (RTC) / 4.1.2：
Collaboration Tools / 4.2：
Development Infrastructure and Environment / 4.3：
Source Control and Version Management / 4.3.1：
Automated Test Environment / 4.3.2：
"Code-Build-Test" / 4.3.3：
Considerations on Teaming and Leadership / 5：
A "Lean" Hierarchy / 5.1：
Selling the Directions: Management by Objectives / 5.2：
Defining the Goals / 5.3：
About Trust and Thrust: Culture and Climate / 5.4：
Cross-functional Teams / 5.5：
The Wisdom of Crowds / 5.6：
It Isn't that Easy / 5.7：
Skills / 5.8：
Considerations on Planning and Architecture / 6：
About Requirements, Resources, and Dates / 6.1：
Agile, a License for Chaos? / 6.2：
Balance Flexibility and Structure / 6.3：
Balance the Level of DetailError! Bookmark not defined / 6.3.1：
Balance the Timing of Decisions / 6.3.2：
Balance the Need for Commitment / 6.3.3：
Balance Between Autonomy and Guidance / 6.3.4：
Balance the Amount of Documentation / 6.3.5：
Disciplined Agile / 6.3.6：
Reducing Complexity / 6.4：
Simplify Prioritization and Planning / 6.4.1：
Simplify Team Setup and Dependencies / 6.4.2：
Simplify Tools and Processes / 6.4.3：
Simplify Daily Life / 6.4.4：
Architectural Considerations / 6.5：
Outside-In Design / 6.5.1：
Requirements, Use Cases, Scenarios, and Tasks / 6.5.2：
Architectural Attitude / 6.5.3：
Making Architecture Flexible / 6.5.4：
Considerations on Project Execution / 7：
The Big Bang / 7.1：
Continuous Integration / 7.2：
The Rhythm of the Project: Iterations / 7.3：
Integration Fest / 7.4：
Juggling Content Within an Iteration / 7.5：
Planning in an Agile Project / 7.6：
Estimating / 7.7：
Units often used in Agile Projects / 7.7.1：
Ways to get to Estimates / 7.7.2：
Metrics for an Agile Project / 7.8：
Defects / 7.9：
Independent Release Testing and Wrap-up / 7.10：
Involving Customers / 7.11：
Mix and Match / 8：
The Tragedy of Being Successful / 8.1：
About WebSphere Portal / 8.2：
Which Projects are suitable for Agile Software Development? / 8.3：
Scaling Agile / 8.4：
Moving Towards Agile / 8.5：
Tiger Teams in WebSphere Portal / 8.6：
Budget-based Prioritization / 8.6.1：
Cross-Organizational Teaming Structure / 8.6.2：
Evolving the Product in Iterations / 8.6.3：
Integrating Test and Development / 8.6.4：
Designs and Documentation / 8.6.5：
Managing Tiger Teams / 8.6.6：
The Benefits and Pain Points / 8.7：
Summary and Wrap-Up / 9：
The Essence of Agile / 9.1：
Building an Agile Community / 9.2：
Comparing once again / 9.3：
Index
The Flaw in the Plan / 1：
The Delusive Perception of Having Anticipated Everything / 1.1：
Accept the Uncertainty and Adapt / 1.2：
41.

電子ブック
ＥＢ
41. Agile Software Development
Thomas Stober, Uwe Hansmann
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2010
所蔵情報: loading…
目次情報: 続きを見る
The Flaw in the Plan / 1：
The Delusive Perception of Having Anticipated Everything / 1.1：
Accept the Uncertainty and Adapt / 1.2：
Involving the Teams / 1.3：
In Search of Structure / 1.4：
Agile Software Development / 1.5：
Further Readings
Traditional Software Development / 2：
History of Project Management / 2.1：
Waterfall Approach / 2.2：
Requirements / 2.2.1：
Design Phase / 2.2.2：
Implementation / 2.2.3：
Testing / 2.2.4：
Support / 2.2.5：
Advantages and Disadvantages / 2.2.6：
Project Management Triangle / 2.3：
Modified Waterfall Models / 2.4：
Milestone and Regular Integration / 2.4.1：
Incremental Development / 2.4.2：
Overview of Agile Software Development / 3：
Lean Software Development / 3.1：
Project Management 2.0 / 3.2：
Agile Manifesto / 3.3：
Scrum / 3.4：
Test Driven Development / 3.5：
Extreme Programming / 3.6：
Rational Unified Process / 3.7：
Best Practices / 3.7.1：
The Phases / 3.7.2：
The Process / 3.7.3：
Agile Unified Process / 3.8：
Agile Model Driven Development / 3.9：
Tooling / 4：
Project Management Tools / 4.1：
Microsoft Solutions Framework for Agile Development / 4.1.1：
Jazz and Rational Team Concert (RTC) / 4.1.2：
Collaboration Tools / 4.2：
Development Infrastructure and Environment / 4.3：
Source Control and Version Management / 4.3.1：
Automated Test Environment / 4.3.2：
"Code-Build-Test" / 4.3.3：
Considerations on Teaming and Leadership / 5：
A "Lean" Hierarchy / 5.1：
Selling the Directions: Management by Objectives / 5.2：
Defining the Goals / 5.3：
About Trust and Thrust: Culture and Climate / 5.4：
Cross-functional Teams / 5.5：
The Wisdom of Crowds / 5.6：
It Isn't that Easy / 5.7：
Skills / 5.8：
Considerations on Planning and Architecture / 6：
About Requirements, Resources, and Dates / 6.1：
Agile, a License for Chaos? / 6.2：
Balance Flexibility and Structure / 6.3：
Balance the Level of DetailError! Bookmark not defined / 6.3.1：
Balance the Timing of Decisions / 6.3.2：
Balance the Need for Commitment / 6.3.3：
Balance Between Autonomy and Guidance / 6.3.4：
Balance the Amount of Documentation / 6.3.5：
Disciplined Agile / 6.3.6：
Reducing Complexity / 6.4：
Simplify Prioritization and Planning / 6.4.1：
Simplify Team Setup and Dependencies / 6.4.2：
Simplify Tools and Processes / 6.4.3：
Simplify Daily Life / 6.4.4：
Architectural Considerations / 6.5：
Outside-In Design / 6.5.1：
Requirements, Use Cases, Scenarios, and Tasks / 6.5.2：
Architectural Attitude / 6.5.3：
Making Architecture Flexible / 6.5.4：
Considerations on Project Execution / 7：
The Big Bang / 7.1：
Continuous Integration / 7.2：
The Rhythm of the Project: Iterations / 7.3：
Integration Fest / 7.4：
Juggling Content Within an Iteration / 7.5：
Planning in an Agile Project / 7.6：
Estimating / 7.7：
Units often used in Agile Projects / 7.7.1：
Ways to get to Estimates / 7.7.2：
Metrics for an Agile Project / 7.8：
Defects / 7.9：
Independent Release Testing and Wrap-up / 7.10：
Involving Customers / 7.11：
Mix and Match / 8：
The Tragedy of Being Successful / 8.1：
About WebSphere Portal / 8.2：
Which Projects are suitable for Agile Software Development? / 8.3：
Scaling Agile / 8.4：
Moving Towards Agile / 8.5：
Tiger Teams in WebSphere Portal / 8.6：
Budget-based Prioritization / 8.6.1：
Cross-Organizational Teaming Structure / 8.6.2：
Evolving the Product in Iterations / 8.6.3：
Integrating Test and Development / 8.6.4：
Designs and Documentation / 8.6.5：
Managing Tiger Teams / 8.6.6：
The Benefits and Pain Points / 8.7：
Summary and Wrap-Up / 9：
The Essence of Agile / 9.1：
Building an Agile Community / 9.2：
Comparing once again / 9.3：
Index
The Flaw in the Plan / 1：
The Delusive Perception of Having Anticipated Everything / 1.1：
Accept the Uncertainty and Adapt / 1.2：
42.

電子ブック
ＥＢ
42. Model Driven Engineering and Ontology Development
Vladan Deved?ic, Vladan Deved?ic, Dragan Djuric, Dragan Ga#evic, Dragan Ga?evic
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2009
所蔵情報: loading…
目次情報: 続きを見る
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
Cognitive Science / 1.2：
Types of Human Knowledge / 1.3：
Knowledge Representation Techniques / 1.4：
Object-Attribute-Value Triplets / 1.4.1：
Uncertain Facts / 1.4.2：
Fuzzy Facts / 1.4.3：
Rules / 1.4.4：
Semantic Networks / 1.4.5：
Frames / 1.4.6：
Knowledge Representation Languages / 1.5：
Logic-Based Representation Languages / 1.5.1：
Frame-Based Representation Languages / 1.5.2：
Rule-Based Representation Languages / 1.5.3：
Visual Languages for Knowledge Representation / 1.5.4：
Natural Languages and Knowledge Representation / 1.5.5：
Knowledge Engineering / 1.6：
Open Knowledge Base Connectivity (OKBC) / 1.7：
The Knowledge Level / 1.8：
Ontologies / 2：
Definitions / 2.1：
What Do Ontologies Look Like? / 2.1.2：
Why Ontologies? / 2.1.3：
Key Application Areas / 2.1.4：
Examples / 2.1.5：
Ontological Engineering / 2.2：
Ontology Development Tools / 2.2.1：
Ontology Development Methodologies / 2.2.2：
Applications / 2.3：
Magpie / 2.3.1：
Briefing Associate / 2.3.2：
Quickstep and Foxtrot / 2.3.3：
Advanced Topics / 2.4：
Metadata, Metamodeling, and Ontologies / 2.4.1：
Standard Upper Ontology / 2.4.2：
Ontological Level / 2.4.3：
The Semantic Web / 3：
Rationale / 3.1：
Semantic Web Languages / 3.2：
XML and XML Schema / 3.2.1：
RDF and RDF Schema / 3.2.2：
DAML+OIL / 3.2.3：
OWL / 3.2.4：
SPARQL / 3.2.5：
GRDDL / 3.2.6：
RDFa / 3.2.7：
SKOS / 3.2.8：
The Role of Ontologies / 3.3：
Semantic Markup / 3.4：
Development Frameworks / 3.5：
Reasoning / 3.6：
Semantic Web Services / 3.7：
Open Issues / 3.8：
Quotations / 3.9：
Model Driven Engineering / 4：
Models and Metamodels / 4.1：
Models in General / 4.1.1：
Model-Driven Engineering Theory / 4.1.2：
Types of Software Models / 4.2：
The Model Driven Architecture / 4.3：
Metamodeling Languages / 4.4：
The Meta-Object Facility / 4.4.1：
Ecore Metamodeling Language / 4.4.2：
Standardized MDA Metamodels / 4.5：
Unified Modeling Language / 4.5.1：
Common Warehouse Metamodel (CWM) / 4.5.2：
Ontology Definition Metamodel / 4.5.3：
UML Profiles / 4.6：
Basics of UML Profiles / 4.6.1：
Examples of UML Profiles / 4.6.2：
Model Transformations / 4.7：
Classification of Model Transformation Languages / 4.7.1：
Model Transformation Languages / 4.7.3：
Model Transformation Tools and Implementations / 4.7.4：
Object Constraint Language / 4.8：
An XML for Sharing MDA Artifacts / 4.9：
The Need for Modeling Spaces / 4.10：
Modeling Spaces / 5：
Modeling the Real World / 5.1：
The Real World, Models, and Metamodels / 5.2：
The Essentials of Modeling Spaces / 5.3：
Modeling Spaces Illuminated / 5.4：
Modeling Spaces Applied / 5.5：
A Touch of RDF(S) and MOF Modeling Spaces / 5.6：
A Touch of the Semantic Web and MDA Technical Spaces / 5.7：
Instead of Conclusions / 5.8：
Model Driven Engineering and Ontologies / Part II：
Software Engineering Approaches to Ontology Development / 6：
A Brief History of Ontology Modeling / 6.1：
Networked Knowledge Representation and Exchange Using UML and RDF / 6.1.1：
Extending the Unified Modeling Language for Ontology Development / 6.1.2：
The Unified Ontology Language / 6.1.3：
UML for the Semantic Web: Transformation-Based Approach / 6.1.4：
The AIFB OWL DL Metamodel / 6.1.5：
NeOn Metamodels for the Semantic Web / 6.1.6：
The GOOD OLD AI ODM Proposal / 6.1.7：
Ontology Development Tools Based on Software Engineering Techniques / 6.2：
Protégé / 6.2.1：
DUET (DAML UML Enhanced Tool) / 6.2.2：
An Ontology Tool for IBM Rational Rose UML Models / 6.2.3：
Visual Ontology Modeler (VOM) / 6.2.4：
Summary of Relations Between UML and Ontologies / 6.3：
Summary of Approaches and Tools for Software Engineering-Based Ontology Development / 6.3.1：
Summary of Differences Between UML and Ontology Languages / 6.3.2：
Future Development / 6.3.3：
The MDA-Based Ontology Infrastructure / 7：
Motivation / 7.1：
Overview / 7.2：
Bridging RDF(S) and MOF / 7.3：
Design Rationale for the Ontology UML Profile / 7.4：
The Ontology Definition Metamodel (ODM) / 8：
ODM Metamodels / 8.1：
A Few Objections to the ODM Specification / 8.2：
The Resource Description Framework Schema (RDFS) Metamodel / 8.3：
The Web Ontology Language (OWL) Metamodel / 8.4：
The Ontology UML Profile / 9：
Classes and Individuals in Ontologies / 9.1：
Properties of Ontologies / 9.2：
Statements / 9.3：
Different Versions of the Ontology UML Profile / 9.4：
Mappings of MDA-Based Languages and Ontologies / 10：
Relations Between Modeling Spaces / 10.1：
Transformations Between Modeling Spaces / 10.2：
Example of an Implementation: An XSLT-Based Approach / 10.3：
Implementation Details / 10.3.1：
Transformation Example / 10.3.2：
Practical Experience / 10.3.3：
Discussion / 10.3.4：
Modeling Tools and Ontology Development / Part III：
MagicDraw / 11.1：
Starting with MagicDraw / 11.1.1：
Things You Should Know when Working with UML Profiles / 11.1.2：
Creating a New Ontology / 11.1.3：
Working with Ontology Classes / 11.1.4：
Working with Ontology Properties / 11.1.5：
Working with Individuals / 11.1.6：
Working with Statements / 11.1.7：
Poseidon for UML / 11.2：
Modeling Ontology Classes in Poseidon / 11.2.1：
Modeling Ontology Individuals and Statements in Poseidon / 11.2.2：
Sharing Models Between UML Tools and Protege / 11.3：
Atlas Transformation Language / 11.4：
ATL Integrated Development Environment / 11.4.1：
Support for Technical Spaces / 11.4.3：
ATL for Transforming Between ODM and UML / 11.4.4：
An MDA Based Ontology Platform: AIR / 12：
The Basic Idea / 12.1：
Metamodel-the Conceptual Building Block of AIR / 12.3：
The AIR Metadata Repository / 12.4：
The AIR Workbench / 12.5：
The Role of XML Technologies / 12.6：
Possibilities / 12.7：
Examples of Ontology / 13：
Petri Net Ontology / 13.1：
Organization of the Petri Net Ontology / 13.1.1：
The Core Petri Net Ontology in the Ontology UML Profile / 13.1.2：
An Extension Example: Upgraded Petri Nets / 13.1.3：
Educational Ontologies / 13.2：
Conceptual Solution / 13.2.1：
Mapping the Conceptual Model to Ontologies / 13.2.2：
Beyond the Ontology Definition Metamodel: Applications / 14：
Integrated Ontology Development Toolkit / 14.1：
TwoUse: UML and OWL Modeling / 14.2：
Model Driven Engineering of Ontology Reasoners / 14.3：
Model Driven Engineering and Semantic Web Rules / 14.4：
References
Index
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
43.

電子ブック
ＥＢ
43. Model Driven Engineering and Ontology Development
Vladan Deved¿ic, Vladan Deved¿ic, Dragan Djuric, Dragan Ga#evic, Dragan Ga¿evic, Jean Bézivin, Vladan Devedžic, Bran V. Selic
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2009
所蔵情報: loading…
目次情報: 続きを見る
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
Cognitive Science / 1.2：
Types of Human Knowledge / 1.3：
Knowledge Representation Techniques / 1.4：
Object-Attribute-Value Triplets / 1.4.1：
Uncertain Facts / 1.4.2：
Fuzzy Facts / 1.4.3：
Rules / 1.4.4：
Semantic Networks / 1.4.5：
Frames / 1.4.6：
Knowledge Representation Languages / 1.5：
Logic-Based Representation Languages / 1.5.1：
Frame-Based Representation Languages / 1.5.2：
Rule-Based Representation Languages / 1.5.3：
Visual Languages for Knowledge Representation / 1.5.4：
Natural Languages and Knowledge Representation / 1.5.5：
Knowledge Engineering / 1.6：
Open Knowledge Base Connectivity (OKBC) / 1.7：
The Knowledge Level / 1.8：
Ontologies / 2：
Definitions / 2.1：
What Do Ontologies Look Like? / 2.1.2：
Why Ontologies? / 2.1.3：
Key Application Areas / 2.1.4：
Examples / 2.1.5：
Ontological Engineering / 2.2：
Ontology Development Tools / 2.2.1：
Ontology Development Methodologies / 2.2.2：
Applications / 2.3：
Magpie / 2.3.1：
Briefing Associate / 2.3.2：
Quickstep and Foxtrot / 2.3.3：
Advanced Topics / 2.4：
Metadata, Metamodeling, and Ontologies / 2.4.1：
Standard Upper Ontology / 2.4.2：
Ontological Level / 2.4.3：
The Semantic Web / 3：
Rationale / 3.1：
Semantic Web Languages / 3.2：
XML and XML Schema / 3.2.1：
RDF and RDF Schema / 3.2.2：
DAML+OIL / 3.2.3：
OWL / 3.2.4：
SPARQL / 3.2.5：
GRDDL / 3.2.6：
RDFa / 3.2.7：
SKOS / 3.2.8：
The Role of Ontologies / 3.3：
Semantic Markup / 3.4：
Development Frameworks / 3.5：
Reasoning / 3.6：
Semantic Web Services / 3.7：
Open Issues / 3.8：
Quotations / 3.9：
Model Driven Engineering / 4：
Models and Metamodels / 4.1：
Models in General / 4.1.1：
Model-Driven Engineering Theory / 4.1.2：
Types of Software Models / 4.2：
The Model Driven Architecture / 4.3：
Metamodeling Languages / 4.4：
The Meta-Object Facility / 4.4.1：
Ecore Metamodeling Language / 4.4.2：
Standardized MDA Metamodels / 4.5：
Unified Modeling Language / 4.5.1：
Common Warehouse Metamodel (CWM) / 4.5.2：
Ontology Definition Metamodel / 4.5.3：
UML Profiles / 4.6：
Basics of UML Profiles / 4.6.1：
Examples of UML Profiles / 4.6.2：
Model Transformations / 4.7：
Classification of Model Transformation Languages / 4.7.1：
Model Transformation Languages / 4.7.3：
Model Transformation Tools and Implementations / 4.7.4：
Object Constraint Language / 4.8：
An XML for Sharing MDA Artifacts / 4.9：
The Need for Modeling Spaces / 4.10：
Modeling Spaces / 5：
Modeling the Real World / 5.1：
The Real World, Models, and Metamodels / 5.2：
The Essentials of Modeling Spaces / 5.3：
Modeling Spaces Illuminated / 5.4：
Modeling Spaces Applied / 5.5：
A Touch of RDF(S) and MOF Modeling Spaces / 5.6：
A Touch of the Semantic Web and MDA Technical Spaces / 5.7：
Instead of Conclusions / 5.8：
Model Driven Engineering and Ontologies / Part II：
Software Engineering Approaches to Ontology Development / 6：
A Brief History of Ontology Modeling / 6.1：
Networked Knowledge Representation and Exchange Using UML and RDF / 6.1.1：
Extending the Unified Modeling Language for Ontology Development / 6.1.2：
The Unified Ontology Language / 6.1.3：
UML for the Semantic Web: Transformation-Based Approach / 6.1.4：
The AIFB OWL DL Metamodel / 6.1.5：
NeOn Metamodels for the Semantic Web / 6.1.6：
The GOOD OLD AI ODM Proposal / 6.1.7：
Ontology Development Tools Based on Software Engineering Techniques / 6.2：
Protégé / 6.2.1：
DUET (DAML UML Enhanced Tool) / 6.2.2：
An Ontology Tool for IBM Rational Rose UML Models / 6.2.3：
Visual Ontology Modeler (VOM) / 6.2.4：
Summary of Relations Between UML and Ontologies / 6.3：
Summary of Approaches and Tools for Software Engineering-Based Ontology Development / 6.3.1：
Summary of Differences Between UML and Ontology Languages / 6.3.2：
Future Development / 6.3.3：
The MDA-Based Ontology Infrastructure / 7：
Motivation / 7.1：
Overview / 7.2：
Bridging RDF(S) and MOF / 7.3：
Design Rationale for the Ontology UML Profile / 7.4：
The Ontology Definition Metamodel (ODM) / 8：
ODM Metamodels / 8.1：
A Few Objections to the ODM Specification / 8.2：
The Resource Description Framework Schema (RDFS) Metamodel / 8.3：
The Web Ontology Language (OWL) Metamodel / 8.4：
The Ontology UML Profile / 9：
Classes and Individuals in Ontologies / 9.1：
Properties of Ontologies / 9.2：
Statements / 9.3：
Different Versions of the Ontology UML Profile / 9.4：
Mappings of MDA-Based Languages and Ontologies / 10：
Relations Between Modeling Spaces / 10.1：
Transformations Between Modeling Spaces / 10.2：
Example of an Implementation: An XSLT-Based Approach / 10.3：
Implementation Details / 10.3.1：
Transformation Example / 10.3.2：
Practical Experience / 10.3.3：
Discussion / 10.3.4：
Modeling Tools and Ontology Development / Part III：
MagicDraw / 11.1：
Starting with MagicDraw / 11.1.1：
Things You Should Know when Working with UML Profiles / 11.1.2：
Creating a New Ontology / 11.1.3：
Working with Ontology Classes / 11.1.4：
Working with Ontology Properties / 11.1.5：
Working with Individuals / 11.1.6：
Working with Statements / 11.1.7：
Poseidon for UML / 11.2：
Modeling Ontology Classes in Poseidon / 11.2.1：
Modeling Ontology Individuals and Statements in Poseidon / 11.2.2：
Sharing Models Between UML Tools and Protege / 11.3：
Atlas Transformation Language / 11.4：
ATL Integrated Development Environment / 11.4.1：
Support for Technical Spaces / 11.4.3：
ATL for Transforming Between ODM and UML / 11.4.4：
An MDA Based Ontology Platform: AIR / 12：
The Basic Idea / 12.1：
Metamodel-the Conceptual Building Block of AIR / 12.3：
The AIR Metadata Repository / 12.4：
The AIR Workbench / 12.5：
The Role of XML Technologies / 12.6：
Possibilities / 12.7：
Examples of Ontology / 13：
Petri Net Ontology / 13.1：
Organization of the Petri Net Ontology / 13.1.1：
The Core Petri Net Ontology in the Ontology UML Profile / 13.1.2：
An Extension Example: Upgraded Petri Nets / 13.1.3：
Educational Ontologies / 13.2：
Conceptual Solution / 13.2.1：
Mapping the Conceptual Model to Ontologies / 13.2.2：
Beyond the Ontology Definition Metamodel: Applications / 14：
Integrated Ontology Development Toolkit / 14.1：
TwoUse: UML and OWL Modeling / 14.2：
Model Driven Engineering of Ontology Reasoners / 14.3：
Model Driven Engineering and Semantic Web Rules / 14.4：
References
Index
Basics / Part I：
Knowledge Representation / 1：
Basic Concepts / 1.1：
44.

電子ブック
ＥＢ
44. Adoption-centric Usability Engineering
Ahmed Seffah, Eduard Metzker
出版情報: Springer eBooks Computer Science , Springer London, 2009
所蔵情報: loading…
目次情報: 続きを見る
Usability Engineering: Definitions, Methods, and Challenges for Integration / Part I：
On Usability and Usability Engineering / 1：
Interactive Systems and User Interface / 1.1：
Usability: A Quality Attribute of the Whole System, Not Just the User Interface / 1.2：
Usability in Traditional Software Quality Models / 1.3：
Other Specific Measurement Models / 1.4：
Cost-benefits of Usability Engineering / 1.5：
Involving the End-User is Central, but Not Enough / 1.6：
Usability Engineering Methods Plethora / 2：
Possible Theories for Usability Engineering / 2.1：
Pure Usability Engineering Methods / 2.2：
A Taxonomy of the Most Popular Usability Engineering (UE) Methods / 2.2.1：
Expert-Based Evaluation / 2.2.2：
Prototyping Techniques / 2.2.3：
Usability Testing / 2.2.4：
Subjective Assessment / 2.2.5：
UE Methods and the Development Lifecycle / 2.3：
Other Usability Engineering-Sensitive Methodologies / 2.4：
Scenario-Based Design / 2.4.1：
Contextual Design / 2.4.2：
Star Lifecycle / 2.4.3：
Usability Engineering Lifecycle / 2.4.4：
Usage-Centered Design / 2.4.5：
Extensions to Traditional Software Engineering Methods / 2.5：
Adding Usage Scenarios to Object-Oriented Analysis and Design / 2.5.1：
Task Analysis Versus Object-Oriented and Use Cases Models / 2.5.2：
UML Notation for User Interface Modeling / 2.5.3：
Enhancing Use Cases for User Interface Prototyping / 2.5.4：
Pitfalls and Obstacles in the Integration and Adoption Path / 3：
The Fallacious Dichotomy Between User Interface and System Functionality / 3.1：
The Cultural Gap Between Psychologists and Engineers / 3.2：
User-Centeredness is an Organizational Learning Process / 3.3：
The Usability of Usability Engineering Methods / 3.4：
The Lack of Process Support Tools / 3.5：
Collecting Best Practices in UE is Missing / 3.6：
Educational Gap Between Software Professionals and Usability Professionals / 3.7：
ACUE Fundamentals, Architecture and Components / Part II：
Usability Engineering Integration as an Adoption Problem / 4：
Key Milestones in the Adoption Process / 4.1：
On the Development of Adoption-Centric Usability Methods / 4.2：
Difficulties of Building an Empirical Driven Adoption Method / 4.3：
Adoption-Centric Usability Engineering - Key Principles / 4.4：
ACUE Architecture and Components / 5：
UE Method Kits / 5.1：
Project Context Profile / 5.2：
USEPacks: Knowledge About UE Methods / 5.3：
USEPack Textual Description / 5.3.1：
USEPack Reusable Artifacts / 5.3.2：
USEPack Context Profile / 5.3.3：
Acceptance Model / 5.3.4：
Context Model vs. Context Profile / 5.3.5：
Configuration of a Method Kit to a Specific Project / 5.4：
USEPack Assessment / 5.5：
ACUE Formal Description / 6：
Foundations for ACUE Formalization / 6.1：
Fuzzy Sets / 6.1.1：
Multi-Criteria Decision-Making / 6.1.2：
Modeling Context Profiles as Fuzzy Sets / 6.1.3：
Context-Based USEPack Selection as a MCDM Problem / 6.1.4：
USEPack Assessment Using the Acceptance Model / 6.2：
USEPack Context Profiles Adaptation / 6.3：
Alternative Approaches for Formalizing ACUE / 6.4：
Operationalization and Validation / Part III：
How Effective Is ACUE? An Empirical Case Study / 7：
Overview of the Study / 7.1：
Goals of the Study / 7.1.1：
Materials: The UE Method Kit / 7.1.2：
Subjects / 7.1.3：
Method / 7.1.4：
Results / 7.2：
Process Sketches / 7.3：
Matching of the Method Kit with Practiced Development Processes / 7.4：
Discussion / 7.5：
Putting it into Practice: The ProUse Tool / 8：
Constraints for Operationalizing the ACUE / 8.1：
Structure and Main Feature / 8.2：
ProUSE Portal / 8.3：
Method Kit Configuration / 8.4：
Method Guidance / 8.5：
Method Capturing and Maintenance / 8.6：
How Well do ACUE and ProUse Work? Overall Evaluation / 9：
Evaluation of ProUSE / 9.1：
Context of the Evaluation / 9.1.1：
Data Collection Techniques / 9.1.2：
Tasks / 9.1.5：
Procedure / 9.1.6：
Results of the Studies and Recommendations / 9.2：
Characteristics of the Subject Groups / 9.2.1：
Understandability of the Proposed ACUE / 9.2.2：
ACUE Perceived Usefulness / 9.2.3：
ACUE Perceived Ease-of-Use / 9.2.4：
Interviewee Statements on the Practiced Software Development Process / 9.3：
Overview / 9.3.1：
Knowledge About the Software Development Process / 9.3.2：
Process Models Used by Subjects / 9.3.3：
The Usability Engineering Process / 9.3.4：
Subjects' Roles as Project Team Members / 9.3.5：
ACUE in Software Engineering: Current Stage and Perspectives / Part IV：
ACUE and the Existing Software Engineering Methodologies / 10：
USEPacks Versus Other Approaches for Reusing UE Knowledge / 10.1：
ProUSE Versus Other Tools for Reusing UE Knowledge / 10.2：
Overall Comparisons Between ACUE and Software Engineering Approaches / 10.3：
ACUE in Relation to Process Improvement Approaches / 10.4：
ACUE as an Approach to Improve Research Utilization / 10.5：
ACUE and Agile Process Concepts / 10.6：
Conclusion and Perspectives / 11：
Conclusion and Limitations / 11.1：
Some Avenues to Explore / 11.2：
A Forum for Cross-Domain Discussion is Needed / 11.3：
References
Index
Usability Engineering: Definitions, Methods, and Challenges for Integration / Part I：
On Usability and Usability Engineering / 1：
Interactive Systems and User Interface / 1.1：
45.

電子ブック
ＥＢ
45. Essential Software Architecture
Ian Gorton
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2006
所蔵情報: loading…
目次情報: 続きを見る
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
Architecture Defines Structure / 1.2.1：
Architecture Specifies Component Communication / 1.2.2：
Architecture Addresses Non-functional Requirements / 1.2.3：
Architecture is an Abstraction / 1.2.4：
Architecture Views / 1.2.5：
What Does a Software Architect Do? / 1.3：
Architectures and Technologies / 1.4：
Summary / 1.5：
Further Reading / 1.6：
General Architecture / 1.6.1：
Architecture Requirements / 1.6.2：
Architecture Patterns / 1.6.3：
Technology Comparisons / 1.6.4：
Introducing the Case Study / 2：
Requirements Overview / 2.1：
Project Context / 2.2：
Business Goals / 2.3：
Constraints / 2.4：
Software Quality Attributes / 2.5：
Quality Attributes / 3.1：
Performance / 3.2：
Throughput / 3.2.1：
Response Time / 3.2.2：
Deadlines / 3.2.3：
Performance for the ICDE System / 3.2.4：
Scalability / 3.3：
Request Load / 3.3.1：
Simultaneous Connections / 3.3.2：
Data Size / 3.3.3：
Deployment / 3.3.4：
Some Thoughts on Scalability / 3.3.5：
Scalability for the ICDE Application / 3.3.6：
Modifiability / 3.4：
Modifiability for the ICDE Application / 3.4.1：
Security / 3.5：
Security for the ICDE Application / 3.5.1：
Availability / 3.6：
Availability for the ICDE Application / 3.6.1：
Integration / 3.7：
Integration for the ICDE Application / 3.7.1：
Other Quality Attributes / 3.8：
Design Trade-Offs / 3.9：
A Guide to Middleware Architectures and Technologies / 3.10：
Introduction / 4.1：
Technology Classification / 4.2：
Distributed Objects / 4.3：
Message-Oriented Middleware / 4.4：
Message-Oriented Middleware Basics / 4.4.1：
Exploiting Message Oriented Middleware Advanced Features / 4.4.2：
Publish-Subscribe / 4.4.3：
Application Servers / 4.5：
Enterprise JavaBeans / 4.5.1：
EJB Component Model / 4.5.2：
EJB Programming / 4.5.3：
Deployment Descriptors / 4.5.4：
Responsibilities of the EJB Container / 4.5.5：
Some Thoughts / 4.5.6：
Message Brokers / 4.6：
Business Process Orchestration / 4.7：
Integration Architecture Issues / 4.8：
CORBA / 4.9：
Integration Middleware / 4.10.2：
A Software Architecture Process / 5：
Process Outline / 5.1：
Determine Architectural Requirements / 5.1.1：
Identifying Architecture Requirements / 5.1.2：
Prioritizing Architecture Requirements / 5.1.3：
Architecture Design / 5.2：
Choosing the Architecture Framework / 5.2.1：
Allocate Components / 5.2.2：
Validation / 5.3：
Using Scenarios / 5.3.1：
Prototyping / 5.3.2：
Summary and Further Reading / 5.4：
Documenting a Software Architecture / 6：
What to Document / 6.1：
UML 2.0 / 6.3：
More on Component Diagrams / 6.4：
Architecture Documentation Template / 6.6：
Case Study Design / 6.7：
Overview / 7.1：
ICDE Technical Issues / 7.2：
Large Data / 7.2.1：
Notification / 7.2.2：
Data Abstraction / 7.2.3：
Platform and Distribution Issues / 7.2.4：
API Issues / 7.2.5：
Discussion / 7.2.6：
ICDE Architecture Requirements / 7.3：
Overview of Key Objectives / 7.3.1：
Architecture Use Cases / 7.3.2：
Stakeholder Architectural Requirements / 7.3.3：
Non-functional Requirements / 7.3.4：
Risks / 7.3.6：
ICDE Solution / 7.4：
Relevant Architectural Patterns / 7.4.1：
Architecture Overview / 7.4.2：
Structural Views / 7.4.3：
Behavioral Views / 7.4.4：
Implementation Issues / 7.4.5：
Architecture Analysis / 7.5：
Scenario Analysis / 7.5.1：
Looking Forward / 7.5.2：
The Challenges of Complexity / 8.1：
Business Process Complexity / 8.1.1：
Agility / 8.1.2：
Reduced Costs / 8.1.3：
What Next? / 8.2：
Software Product Lines / 9：
Product Lines for ICDE / 9.1：
Benefiting from SPL Development / 9.2：
Product Line Architecture / 9.3.1：
Resuse Mechanisms / 9.4.1：
SCM for Reuse / 9.4.2：
Variation Mechanisms / 9.4.3：
Product Line Architecture for ICDE / 9.4.4：
Adopting Software Product Line Development / 9.5：
Starting Points for Adopting SPL Development / 9.5.1：
Product Line Adoption Practice Areas / 9.6：
Product Line Adoption for ICDE / 9.6.1：
Ongoing Software Product Line Development / 9.7：
Change Control / 9.7.1：
Architectural Evolution for SPL Development / 9.7.2：
Product Line Development Practice Areas / 9.7.3：
Product Lines with ICDE / 9.7.4：
Conclusions / 9.8：
Aspect Oriented Architectures / 9.9：
Aspects for ICDE Development / 10.1：
Introduction to Aspect-Oriented Programming / 10.1.1：
Crosscutting Concerns / 10.1.2：
Managing Concerns with Aspects / 10.1.3：
AOP Syntax and Programming Model / 10.1.4：
Weaving / 10.1.5：
Example of a Cache Aspect / 10.1.6：
Aspect-Oriented Architectures / 10.2：
Architectural Aspects and Middleware / 10.2.1：
State-of-the-Art / 10.3：
Aspect Oriented Modeling in UML / 10.3.1：
AOP Tools / 10.3.2：
Annotations and AOP / 10.3.3：
Performance Monitoring of ICDE with AspectWerkz / 10.4：
Futhur Reading / 10.5：
Model-Driven Architecture / 11：
Model-Driven Development for ICDE / 11.1：
What is MDA / 11.2：
Why MDA? / 11.3：
Portability / 11.3.1：
Interoperability / 11.3.2：
Reusability / 11.3.3：
State-of-Art Practices and Tools / 11.4：
AndroMDA / 11.4.1：
ArcStyler / 11.4.2：
Eclipse Modelling Framework (EMF) / 11.4.3：
MDA and Software Architecture / 11.5：
MDA and Non-Functional Requirements / 11.5.1：
Model Transformation and Software Architecture / 11.5.2：
SOA and MDA / 11.5.3：
Analytical Models are Models too / 11.5.4：
MDA for ICDE Capacity Planning / 11.6：
Service-Oriented Architectures and Technologies / 11.7：
Service-Oriented Architecture for ICDE / 12.1：
Background / 12.2：
Service-Oriented Systems / 12.3：
Boundaries are Explicit / 12.3.1：
Services are Autonomous / 12.3.2：
Share Schemas and Contracts, not Implementations / 12.3.3：
Service Compatibility is Based on Policy / 12.3.4：
Web Services / 12.4：
SOAP and Messaging / 12.5：
UDDI, WSDL and Metadata / 12.6：
Security, Transactions and Reliability / 12.7：
Web Services and the Future of Middleware / 12.8：
ICDE with Web Services / 12.9：
Conclusion and Further Reading / 12.10：
The Semantic Web / 13：
ICDE and the Semantic Web / 13.1：
Adaptive, Automated, and Distributed / 13.2：
Metadata / 13.3：
Semantics / 13.3.2：
Ontologies in ICDE / 13.4：
Semantic Web Services / 13.5：
Cautious Optimism / 13.6：
Software Agents: An Architectural: Perspective / 13.7：
Agents in the ICDE Environment / 14.1：
What is an Agent? / 14.2：
Abstraction Revisited / 14.3：
An Example Agent Technology / 14.4：
Architectural Implications / 14.5：
Concurrency / 14.5.1：
Mobility / 14.5.2：
Agent Technologies / 14.6：
Concluding Thoughts / 14.7：
Challenges / 15.1：
Architecture Knowledge: Management / 15.1.1：
Adaptive Architectures / 15.1.2：
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
46.

電子ブック
ＥＢ
46. Essential Software Architecture
Ian Gorton
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2006
所蔵情報: loading…
目次情報: 続きを見る
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
Architecture Defines Structure / 1.2.1：
Architecture Specifies Component Communication / 1.2.2：
Architecture Addresses Non-functional Requirements / 1.2.3：
Architecture is an Abstraction / 1.2.4：
Architecture Views / 1.2.5：
What Does a Software Architect Do? / 1.3：
Architectures and Technologies / 1.4：
Summary / 1.5：
Further Reading / 1.6：
General Architecture / 1.6.1：
Architecture Requirements / 1.6.2：
Architecture Patterns / 1.6.3：
Technology Comparisons / 1.6.4：
Introducing the Case Study / 2：
Requirements Overview / 2.1：
Project Context / 2.2：
Business Goals / 2.3：
Constraints / 2.4：
Software Quality Attributes / 2.5：
Quality Attributes / 3.1：
Performance / 3.2：
Throughput / 3.2.1：
Response Time / 3.2.2：
Deadlines / 3.2.3：
Performance for the ICDE System / 3.2.4：
Scalability / 3.3：
Request Load / 3.3.1：
Simultaneous Connections / 3.3.2：
Data Size / 3.3.3：
Deployment / 3.3.4：
Some Thoughts on Scalability / 3.3.5：
Scalability for the ICDE Application / 3.3.6：
Modifiability / 3.4：
Modifiability for the ICDE Application / 3.4.1：
Security / 3.5：
Security for the ICDE Application / 3.5.1：
Availability / 3.6：
Availability for the ICDE Application / 3.6.1：
Integration / 3.7：
Integration for the ICDE Application / 3.7.1：
Other Quality Attributes / 3.8：
Design Trade-Offs / 3.9：
A Guide to Middleware Architectures and Technologies / 3.10：
Introduction / 4.1：
Technology Classification / 4.2：
Distributed Objects / 4.3：
Message-Oriented Middleware / 4.4：
Message-Oriented Middleware Basics / 4.4.1：
Exploiting Message Oriented Middleware Advanced Features / 4.4.2：
Publish-Subscribe / 4.4.3：
Application Servers / 4.5：
Enterprise JavaBeans / 4.5.1：
EJB Component Model / 4.5.2：
EJB Programming / 4.5.3：
Deployment Descriptors / 4.5.4：
Responsibilities of the EJB Container / 4.5.5：
Some Thoughts / 4.5.6：
Message Brokers / 4.6：
Business Process Orchestration / 4.7：
Integration Architecture Issues / 4.8：
CORBA / 4.9：
Integration Middleware / 4.10.2：
A Software Architecture Process / 5：
Process Outline / 5.1：
Determine Architectural Requirements / 5.1.1：
Identifying Architecture Requirements / 5.1.2：
Prioritizing Architecture Requirements / 5.1.3：
Architecture Design / 5.2：
Choosing the Architecture Framework / 5.2.1：
Allocate Components / 5.2.2：
Validation / 5.3：
Using Scenarios / 5.3.1：
Prototyping / 5.3.2：
Summary and Further Reading / 5.4：
Documenting a Software Architecture / 6：
What to Document / 6.1：
UML 2.0 / 6.3：
More on Component Diagrams / 6.4：
Architecture Documentation Template / 6.6：
Case Study Design / 6.7：
Overview / 7.1：
ICDE Technical Issues / 7.2：
Large Data / 7.2.1：
Notification / 7.2.2：
Data Abstraction / 7.2.3：
Platform and Distribution Issues / 7.2.4：
API Issues / 7.2.5：
Discussion / 7.2.6：
ICDE Architecture Requirements / 7.3：
Overview of Key Objectives / 7.3.1：
Architecture Use Cases / 7.3.2：
Stakeholder Architectural Requirements / 7.3.3：
Non-functional Requirements / 7.3.4：
Risks / 7.3.6：
ICDE Solution / 7.4：
Relevant Architectural Patterns / 7.4.1：
Architecture Overview / 7.4.2：
Structural Views / 7.4.3：
Behavioral Views / 7.4.4：
Implementation Issues / 7.4.5：
Architecture Analysis / 7.5：
Scenario Analysis / 7.5.1：
Looking Forward / 7.5.2：
The Challenges of Complexity / 8.1：
Business Process Complexity / 8.1.1：
Agility / 8.1.2：
Reduced Costs / 8.1.3：
What Next? / 8.2：
Software Product Lines / 9：
Product Lines for ICDE / 9.1：
Benefiting from SPL Development / 9.2：
Product Line Architecture / 9.3.1：
Resuse Mechanisms / 9.4.1：
SCM for Reuse / 9.4.2：
Variation Mechanisms / 9.4.3：
Product Line Architecture for ICDE / 9.4.4：
Adopting Software Product Line Development / 9.5：
Starting Points for Adopting SPL Development / 9.5.1：
Product Line Adoption Practice Areas / 9.6：
Product Line Adoption for ICDE / 9.6.1：
Ongoing Software Product Line Development / 9.7：
Change Control / 9.7.1：
Architectural Evolution for SPL Development / 9.7.2：
Product Line Development Practice Areas / 9.7.3：
Product Lines with ICDE / 9.7.4：
Conclusions / 9.8：
Aspect Oriented Architectures / 9.9：
Aspects for ICDE Development / 10.1：
Introduction to Aspect-Oriented Programming / 10.1.1：
Crosscutting Concerns / 10.1.2：
Managing Concerns with Aspects / 10.1.3：
AOP Syntax and Programming Model / 10.1.4：
Weaving / 10.1.5：
Example of a Cache Aspect / 10.1.6：
Aspect-Oriented Architectures / 10.2：
Architectural Aspects and Middleware / 10.2.1：
State-of-the-Art / 10.3：
Aspect Oriented Modeling in UML / 10.3.1：
AOP Tools / 10.3.2：
Annotations and AOP / 10.3.3：
Performance Monitoring of ICDE with AspectWerkz / 10.4：
Futhur Reading / 10.5：
Model-Driven Architecture / 11：
Model-Driven Development for ICDE / 11.1：
What is MDA / 11.2：
Why MDA? / 11.3：
Portability / 11.3.1：
Interoperability / 11.3.2：
Reusability / 11.3.3：
State-of-Art Practices and Tools / 11.4：
AndroMDA / 11.4.1：
ArcStyler / 11.4.2：
Eclipse Modelling Framework (EMF) / 11.4.3：
MDA and Software Architecture / 11.5：
MDA and Non-Functional Requirements / 11.5.1：
Model Transformation and Software Architecture / 11.5.2：
SOA and MDA / 11.5.3：
Analytical Models are Models too / 11.5.4：
MDA for ICDE Capacity Planning / 11.6：
Service-Oriented Architectures and Technologies / 11.7：
Service-Oriented Architecture for ICDE / 12.1：
Background / 12.2：
Service-Oriented Systems / 12.3：
Boundaries are Explicit / 12.3.1：
Services are Autonomous / 12.3.2：
Share Schemas and Contracts, not Implementations / 12.3.3：
Service Compatibility is Based on Policy / 12.3.4：
Web Services / 12.4：
SOAP and Messaging / 12.5：
UDDI, WSDL and Metadata / 12.6：
Security, Transactions and Reliability / 12.7：
Web Services and the Future of Middleware / 12.8：
ICDE with Web Services / 12.9：
Conclusion and Further Reading / 12.10：
The Semantic Web / 13：
ICDE and the Semantic Web / 13.1：
Adaptive, Automated, and Distributed / 13.2：
Metadata / 13.3：
Semantics / 13.3.2：
Ontologies in ICDE / 13.4：
Semantic Web Services / 13.5：
Cautious Optimism / 13.6：
Software Agents: An Architectural: Perspective / 13.7：
Agents in the ICDE Environment / 14.1：
What is an Agent? / 14.2：
Abstraction Revisited / 14.3：
An Example Agent Technology / 14.4：
Architectural Implications / 14.5：
Concurrency / 14.5.1：
Mobility / 14.5.2：
Agent Technologies / 14.6：
Concluding Thoughts / 14.7：
Challenges / 15.1：
Architecture Knowledge: Management / 15.1.1：
Adaptive Architectures / 15.1.2：
Understanding Software Architecture / 1：
What is Software Architecture? / 1.1：
Definitions of Software Architecture / 1.2：
47.

電子ブック
ＥＢ
47. An Approach to Modelling Software Evolution Processes
Tong Li
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2009
所蔵情報: loading…
目次情報: 続きを見る
Preface
List of Figures and Tables
Introduction / 1：
Motivation / 1.1：
Contributions / 1.2：
Research Methods / 1.3：
Success Criteria / 1.4：
Validation Methods / 1.5：
Outline / 1.6：
References
Overview of Software Processes and Software Evolution / 2：
Software Processes / 2.1：
Concepts of Software Process / 2.2.1：
Software Process Modelling and Descriptions / 2.2.2：
Software Process Modelling and Description Languages / 2.2.3：
Software Process Improvement and CMM / 2.2.4：
Software Process Reuse / 2.2.5：
Process-Centred Software Engineering Environments / 2.2.6：
Software Evolution / 2.3：
Concepts of Software Evolution / 2.3.1：
Software Reengineering / 2.3.2：
Summary / 2.3.3：
Related Work / 3：
Software Evolution Process / 3.1：
Concurrency in the Software Life Cycle / 3.3：
Petri Nets / 3.4：
Dependence Analysis / 3.5：
Formal Functional Decomposition / 3.6：
Software Evolution Process Meta-Model EPMM / 3.7：
Properties of Software Evolution Processes / 4.1：
Iteration in Software Evolution Processes / 4.3：
Concurrency in Software Evolution Processes / 4.4：
Version Concurrency / 4.4.1：
Process Concurrency / 4.4.2：
Sub-Process Concurrency / 4.4.3：
Phase Concurrency / 4.4.4：
Activity Concurrency / 4.4.5：
Task Concurrency / 4.4.6：
Static Component Definitions of EPMM / 4.5：
Task / 4.5.1：
Activity / 4.5.2：
Software Process / 4.5.3：
Example: Prototype Evolution Process Model / 4.5.4：
Global Model / 4.5.5：
Dynamic Component Definitions of EPMM / 4.6：
Supports for Software Evolution Processes / 4.7：
Software Evolution Process Description Language EPDL / 4.8：
Survey of EPDL / 5.1：
Design Goals / 5.2.1：
Characteristics / 5.2.2：
Program Structure / 5.2.3：
EPDL Program / 5.3：
Example / 5.8：
Framework of Software Evolution Processes / 5.9：
Steps for Modelling Software Evolution Processes / 6.1：
Designing Global Models / 6.4：
Evolution Process Descriptions / 6.5：
Designing Processes and Activities / 6.6：
Designing Processes / 7.1：
Basic Blocks / 7.2.1：
Software Process Package / 7.2.2：
Procedure for Modelling Processes / 7.2.3：
Designing Activities / 7.3：
Reuse of Software Evolution Processes / 7.4：
Reuse by Inheritance / 7.4.1：
Reuse of Basic Blocks / 7.4.2：
Reuse of Process Packages / 7.4.3：
Designing Tasks / 7.5：
Procedure of Designing Tasks / 8.1：
Structures of Functional Decomposition / 8.3：
Decomposition Rules / 8.4：
Sequence Decomposition / 8.4.1：
Selection Decomposition / 8.4.2：
Repetition Decomposition / 8.4.3：
Structure of the Knowledge Base / 8.5：
The Case Base / 8.5.1：
The Segment Base / 8.5.2：
The Rule Base / 8.5.3：
Decomposition / 8.6：
The Decomposition Tree / 8.6.1：
Match Between Two 2-Assertions / 8.6.2：
The Decomposition Process / 8.6.3：
Supports by Modellers / 8.6.4：
Efficiency Improvement of the Software Evolution Processes / 8.7：
Procedure of Efficiency Improvement / 9.1：
Dependence Analysis Between Entities / 9.3：
Constructing a Dependence Graph / 9.3.1：
Localising Dependences / 9.3.2：
Reconstructing Process Segments / 9.4：
Preprocessing an ADG / 9.4.1：
Transformation Rules / 9.4.2：
Transformation Algorithm / 9.4.3：
Examples / 9.4.4：
Capturing Concurrency within an Activity / 9.5：
Analysing Dependences Between Partition Blocks / 9.6：
Extending Concurrency / 9.7：
Reconstructing Software Processes / 9.8：
Support Environment EPT / 9.9：
Architecture of EPT / 10.1：
File Depository / 10.3：
Data Structures of EPDL Object Codes / 10.3.1：
Other Data Structures / 10.3.2：
Process Server / 10.4：
Modelling Manager / 10.4.1：
EPDL Compiler / 10.4.2：
Runtime Manager / 10.4.3：
User Interface and Message Server / 10.5：
Case Studies / 10.6：
First Case Study: The Waterfall Model / 11.1：
Second Case Study: Three Software Processes Involved in Evolution / 11.3：
Third Case Study: An Evolution Process of an Information Security System / 11.4：
Background / 11.4.1：
The Process of Modelling / 11.4.2：
White Box Approach / 11.4.3：
Black Box Approach / 11.4.5：
Efficiency Improvement / 11.4.6：
Fourth Case Study: The Maintenance Process of ISO/IEC 12207 / 11.5：
Activity: Process Implementation / 11.5.1：
Activity: Problem and Modification Analysis / 11.5.4：
Activity: Modification Implementation / 11.5.5：
Activity: Maintenance Review/Acceptance / 11.5.6：
Activity: Migration / 11.5.7：
Activity: Software Retirement / 11.5.8：
Conclusions / 11.6：
Success Criteria Revisited / 12.1：
Evaluations / 12.2：
Comparison with Osterweil's Approach / 12.2.1：
Comparison with Lehman's Approach / 12.2.2：
Future Work / 12.2.3：
Limitations / 12.4.1：
Directions for Future Work / 12.4.2：
Index
Preface
List of Figures and Tables
Introduction / 1：
48.

電子ブック
ＥＢ
48. An Approach to Modelling Software Evolution Processes
Tong Li
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2009
所蔵情報: loading…
目次情報: 続きを見る
Preface
List of Figures and Tables
Introduction / 1：
Motivation / 1.1：
Contributions / 1.2：
Research Methods / 1.3：
Success Criteria / 1.4：
Validation Methods / 1.5：
Outline / 1.6：
References
Overview of Software Processes and Software Evolution / 2：
Software Processes / 2.1：
Concepts of Software Process / 2.2.1：
Software Process Modelling and Descriptions / 2.2.2：
Software Process Modelling and Description Languages / 2.2.3：
Software Process Improvement and CMM / 2.2.4：
Software Process Reuse / 2.2.5：
Process-Centred Software Engineering Environments / 2.2.6：
Software Evolution / 2.3：
Concepts of Software Evolution / 2.3.1：
Software Reengineering / 2.3.2：
Summary / 2.3.3：
Related Work / 3：
Software Evolution Process / 3.1：
Concurrency in the Software Life Cycle / 3.3：
Petri Nets / 3.4：
Dependence Analysis / 3.5：
Formal Functional Decomposition / 3.6：
Software Evolution Process Meta-Model EPMM / 3.7：
Properties of Software Evolution Processes / 4.1：
Iteration in Software Evolution Processes / 4.3：
Concurrency in Software Evolution Processes / 4.4：
Version Concurrency / 4.4.1：
Process Concurrency / 4.4.2：
Sub-Process Concurrency / 4.4.3：
Phase Concurrency / 4.4.4：
Activity Concurrency / 4.4.5：
Task Concurrency / 4.4.6：
Static Component Definitions of EPMM / 4.5：
Task / 4.5.1：
Activity / 4.5.2：
Software Process / 4.5.3：
Example: Prototype Evolution Process Model / 4.5.4：
Global Model / 4.5.5：
Dynamic Component Definitions of EPMM / 4.6：
Supports for Software Evolution Processes / 4.7：
Software Evolution Process Description Language EPDL / 4.8：
Survey of EPDL / 5.1：
Design Goals / 5.2.1：
Characteristics / 5.2.2：
Program Structure / 5.2.3：
EPDL Program / 5.3：
Example / 5.8：
Framework of Software Evolution Processes / 5.9：
Steps for Modelling Software Evolution Processes / 6.1：
Designing Global Models / 6.4：
Evolution Process Descriptions / 6.5：
Designing Processes and Activities / 6.6：
Designing Processes / 7.1：
Basic Blocks / 7.2.1：
Software Process Package / 7.2.2：
Procedure for Modelling Processes / 7.2.3：
Designing Activities / 7.3：
Reuse of Software Evolution Processes / 7.4：
Reuse by Inheritance / 7.4.1：
Reuse of Basic Blocks / 7.4.2：
Reuse of Process Packages / 7.4.3：
Designing Tasks / 7.5：
Procedure of Designing Tasks / 8.1：
Structures of Functional Decomposition / 8.3：
Decomposition Rules / 8.4：
Sequence Decomposition / 8.4.1：
Selection Decomposition / 8.4.2：
Repetition Decomposition / 8.4.3：
Structure of the Knowledge Base / 8.5：
The Case Base / 8.5.1：
The Segment Base / 8.5.2：
The Rule Base / 8.5.3：
Decomposition / 8.6：
The Decomposition Tree / 8.6.1：
Match Between Two 2-Assertions / 8.6.2：
The Decomposition Process / 8.6.3：
Supports by Modellers / 8.6.4：
Efficiency Improvement of the Software Evolution Processes / 8.7：
Procedure of Efficiency Improvement / 9.1：
Dependence Analysis Between Entities / 9.3：
Constructing a Dependence Graph / 9.3.1：
Localising Dependences / 9.3.2：
Reconstructing Process Segments / 9.4：
Preprocessing an ADG / 9.4.1：
Transformation Rules / 9.4.2：
Transformation Algorithm / 9.4.3：
Examples / 9.4.4：
Capturing Concurrency within an Activity / 9.5：
Analysing Dependences Between Partition Blocks / 9.6：
Extending Concurrency / 9.7：
Reconstructing Software Processes / 9.8：
Support Environment EPT / 9.9：
Architecture of EPT / 10.1：
File Depository / 10.3：
Data Structures of EPDL Object Codes / 10.3.1：
Other Data Structures / 10.3.2：
Process Server / 10.4：
Modelling Manager / 10.4.1：
EPDL Compiler / 10.4.2：
Runtime Manager / 10.4.3：
User Interface and Message Server / 10.5：
Case Studies / 10.6：
First Case Study: The Waterfall Model / 11.1：
Second Case Study: Three Software Processes Involved in Evolution / 11.3：
Third Case Study: An Evolution Process of an Information Security System / 11.4：
Background / 11.4.1：
The Process of Modelling / 11.4.2：
White Box Approach / 11.4.3：
Black Box Approach / 11.4.5：
Efficiency Improvement / 11.4.6：
Fourth Case Study: The Maintenance Process of ISO/IEC 12207 / 11.5：
Activity: Process Implementation / 11.5.1：
Activity: Problem and Modification Analysis / 11.5.4：
Activity: Modification Implementation / 11.5.5：
Activity: Maintenance Review/Acceptance / 11.5.6：
Activity: Migration / 11.5.7：
Activity: Software Retirement / 11.5.8：
Conclusions / 11.6：
Success Criteria Revisited / 12.1：
Evaluations / 12.2：
Comparison with Osterweil's Approach / 12.2.1：
Comparison with Lehman's Approach / 12.2.2：
Future Work / 12.2.3：
Limitations / 12.4.1：
Directions for Future Work / 12.4.2：
Index
Preface
List of Figures and Tables
Introduction / 1：
49.

電子ブック
ＥＢ
49. The IT Measurement Compendium
Manfred Bundschuh, Carol Dekkers
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Preface
List of Figures
List of Tables
The Estimation Challenges / 1：
The Basics of Software Estimation / 1.1：
Measurement / 1.1.1：
Estimation / 1.1.2：
Estimation Precision / 1.1.3：
The Object of Estimation / 1.1.4：
Requirements (Scope) Creep / 1.1.5：
Measurement and Estimation / 1.1.6：
Measurement of Effort / 1.1.7：
Documentation / 1.1.8：
The Problem of Historic Data / 1.1.9：
Rules for Estimation / 1.2：
Basic Principles / 1.2.1：
Do's and Don'ts When Estimating / 1.2.2：
Estimation Errors / 1.2.3：
Political Estimates / 1.2.4：
Underestimation and Overestimation / 1.2.5：
The Estimation Conference / 1.2.6：
Estimation Honesty / 1.2.7：
Estimation Culture / 1.2.8：
Training for Estimation / 1.2.9：
A Checklist for Estimating / 1.3：
Internet Links for Software Measurement Associations and Estimation / 1.4：
Management Summary / 1.5：
Estimation Fundamentals / 2：
Estimation in a Project Controlling Environment / 2.1：
Adjusting the Estimate to Take into Account Project Environment Factors / 2.1.1：
Project Goals and the Devils Square of Project Management / 2.1.2：
Estimation and Quality / 2.1.3：
ISO/IEC 9126 Quality Attributes and IFPUG GSC / 2.1.4：
The Cybernetic Estimation Control Circuit / 2.1.5：
Determining Parameters of Estimation / 2.2：
The Purpose of Estimation / 2.2.1：
The Goals of Estimation / 2.2.2：
The Right Time for Estimation / 2.2.3：
Tracking of Estimates / 2.2.4：
Prerequisites for Estimation / 2.3：
The Information Basis of Estimation / 3.1：
Prerequisites for Estimation of Effort / 3.1.1：
Time Accounting / 3.1.3：
The Problem of Overtime Work / 3.1.4：
The Definition of the Application Boundary / 3.1.5：
The Type of Estimation / 3.1.6：
Customizing of Standard Software (Packages) / 3.1.7：
Documentation of the Development Environment / 3.1.8：
Validation of Estimates / 3.1.9：
The Process of Estimation / 3.2：
Distribution of Estimated Effort Across Project Phases / 3.2.1：
The Documentation of Project Estimates / 3.2.2：
The Implementation of Estimation / 3.3：
Report About a Successful Implementation / 4.1：
Positive and Negative Aspects of Software Measurement / 4.2：
Frequently Asked Questions / 4.3：
The Effort for Estimation / 4.3.1：
The Right Time to Implement a Formal Estimation Process / 4.3.2：
The Pros and Cons of a Competence Center / 4.3.3：
Acceptance Challenges / 4.4：
Counter the Counterarguments / 4.4.1：
Resistance / 4.4.2：
Information and Participation / 4.4.3：
Goals for an Estimation Process / 4.5：
Counting of Historical Projects / 4.6：
Estimation as an Early Warning System / 4.7：
Estimation Methods / 4.8：
The Challenges of Estimation Methods / 5.1：
Determination of the Effort / 5.2：
Estimation Based on an Experience Curve / 5.2.1：
Estimation Using an Estimation Equation / 5.2.2：
Estimation with an Expert System / 5.2.3：
Backfiring / 5.2.4：
Overview of Methods / 5.3：
Heuristic Methods / 5.3.1：
Size-Based Methods / 5.3.2：
Evaluation of an Estimation Method / 5.4：
User Comfort / 5.4.1：
Project Management / 5.4.2：
Quality of Result / 5.4.3：
Precision of Estimation Methods / 5.4.4：
Estimating Maintenance Effort / 5.5：
International Standards for Software Maintenance / 6.1：
ISO/IEC standards / 6.1.1：
FiSMA: Finnish Software Measurement Association / 6.1.2：
IFPUG: International Function Point Users Group / 6.1.3：
NESMA: Netherlands Software Metrieken Gebruikers Associatie / 6.1.4：
UKSMA: United Kingdom Software Metrics Association / 6.1.5：
Enhancement Projects / 6.2：
Software Metrics for Maintenance / 6.3：
Estimation of Maintenance Effort after Delivery / 6.4：
Estimation of Small Changes / 6.5：
Software Measurement and Metrics: Fundamentals / 6.6：
Terminology / 7.1：
Formal Definitions / 7.1.1：
Basic Measures (Measures) / 7.1.2：
Metrics / 7.1.3：
Indicators / 7.1.4：
Goals and Benefits of Metrics / 7.1.5：
Goals of Metrics / 7.2.1：
Benefits of Metrics / 7.2.2：
Start and Implementation of a Metrics Initiative / 7.3：
Establishing a Metrics Initiative / 7.3.1：
Establishing a Metrics Database / 7.3.2：
The Structure of a Metrics System / 7.3.3：
Product- and Process-Metrics / 7.4：
Product Metrics / 8.1：
Size of the Software Product / 8.1.1：
Source Code Metrics / 8.1.2：
Source Lines of Code / 8.1.3：
Functional Size / 8.1.4：
Project Size Categories / 8.1.5：
Software Quality / 8.2：
Defect Metrics / 8.2.1：
Function Points and Defects / 8.2.2：
System Complexity / 8.3：
Structural and Data Complexity / 8.4.1：
Halstead's Metrics / 8.4.2：
McCabe's Cyclomatic Complexity / 8.4.3：
Process Metrics / 8.5：
Work Effort / 8.5.1：
Productivity / 8.5.2：
PDR / 8.5.3：
Efficiency / 8.5.4：
Cost / 8.5.5：
Project Duration / 8.5.6：
Object-Oriented Metrics / 8.6：
Examples of Object-Oriented Metrics / 9.1：
Design metrics by Lorenz (1993) / 9.1.1：
The Metrics Suite from Chidamber and Kemerer, 1994 / 9.1.2：
Capers Jones' Object-Oriented Cost, Defect, and Productivity Metrics / 9.1.3：
The Survey of Xenos et al / 9.1.4：
Metrics for Defects and Size by Cartwright and Shepperd / 9.1.5：
Methods for Size from Catherwood et al / 9.1.6：
Class Metrics from Silvia Regina Vergilio and Chaves / 9.1.7：
Use Case Points / 9.1.8：
Further Examples of Object-Oriented Measures and Metrics / 9.1.9：
Projects that were Developed Using Object-Oriented Approaches in the ISBSG Benchmarking Database / 9.2：
Function Points and Object-Oriented System Development / 9.3：
IFPUG Function Points and OOA According to the Jacobsen Approach / 9.3.1：
IFPUG Function Points and UML / 9.3.2：
COSMIC and UML / 9.3.3：
Measurement Communities and Resources / 9.4：
The ISO Standards / 10.1：
The Capability Maturity Model Integration / 10.2：
The Goal Question Metric Method / 10.3：
The Balanced Scorecard / 10.4：
Important Software and Systems Measurement Organizations / 10.5：
Computer Measurement Group (CMG) / 10.5.1：
COSMIC Consortium / 10.5.2：
Finnish Software Measurement Association (FiSMA) / 10.5.3：
German Metrics Organization: DASMA / 10.5.4：
German GI Interest Group on Software Metrics / 10.5.5：
International Function Point Users Group (IFPUG) / 10.5.6：
International Software Benchmarking Standards Group / 10.5.7：
International Organization for Standardization / 10.5.8：
Metrics Association's International Network (MAIN) / 10.5.9：
Software Engineering Institute at Carnegie Mellon University in Pittsburgh, PA, USA / 10.5.10：
Standard Performance Evaluation Corporation (SPEC) / 10.5.11：
Transaction Processing Performance Council (TPC) / 10.5.12：
Internet Links to Measurement Communities / 10.6：
Benchmarking of IT Projects / 10.7：
Benchmarking Fundamentals / 11.1：
Practical Benchmarking Experiences / 11.2：
Benchmarking Databases / 11.3：
Academic Comparison of Measurement Databases / 11.3.1：
The ESA/INSEAD Database / 11.3.2：
ISBSG and Its Products / 11.4：
Demographics of ISBSG Repositories / 11.4.1：
ISBSG Products / 11.4.2：
Project Characteristics / 11.4.3：
Further Results of the ISBSG Research / 11.4.4：
Internet Links to Benchmarking Organizations / 11.5：
The IFPUG Function Point Counting Method / 11.6：
Functional Size Measurement Methods History / 12.1：
The Benefits of the IFPUG FPM / 12.2：
Leveraging the Use of Function Points (and the Analytical Approach) in Software Development / 12.2.1：
Function Points as Part of a Pricing Evaluation Process / 12.2.2：
Function Points as the Basis for Contract Metrics / 12.2.3：
Application Areas for Function Points / 12.3：
The Evaluation of Function Point-Based Estimation Methods / 12.4：
The Optimum Time to Count FPs / 12.5：
The Process of Function Point Counting / 12.6：
Step 1: Define the Type of Count / 12.6.1：
Step 2: Define the Scope of the Count and the Application Boundary / 12.6.2：
Step 3: Count Unadjusted FPs / 12.6.3：
Step 4: Calculate the VAF After Determining the 14 GSCs / 12.6.4：
Step 5: Calculate the Adjusted FPs / 12.6.5：
Step 6: Document the Count / 12.6.6：
Step 7: Quality Assurance of the Count by the Competence Center / 12.6.7：
The Process to Implement the IFPUG Function Point Counting Method / 12.7：
The Limitations of the IFPUG Function Point Counting Method / 12.8：
Functional Size Measurement Methods (FSMMs) / 12.9：
Short Characterizations of ISO/IEC-Conformant FSMMs / 13.1：
COSMIC / 13.2：
The COSMIC Counting Process / 13.2.1：
Software Layers in COSMIC / 13.2.2：
ISBSG Data with Respect to COSMIC / 13.2.3：
Comparison Between Counts Done Using COSMIC and IFPUG FPA / 13.2.4：
FiSMA 1.1 Functional Size Measurement Method / 13.3：
The FiSMA 1.1 Measurement Process / 13.3.1：
FiSMA 1.1 Components / 13.3.2：
Research Related to FiSMA 1.1 FSMM / 13.3.3：
Mark II Function Point Method / 13.4：
NESMA FPA / 13.5：
Similarities and Differences Between NESMA and IFPUG Function Point Standards / 13.5.1：
NESMA Function Points for Enhancements / 13.5.2：
Outlook for Functional Size Measurement Methods / 13.6：
Variants of the IFPUG Function Point Counting Method / 13.7：
The Data Point Method / 14.1：
Feature Points / 14.2：
Object Point Methods / 14.3：
SPR Function Points / 14.4：
3D Function Points / 14.5：
Unadjusted Use Case Weight (UUCW) / 14.6：
Unadjusted Actor Weight (UAW) / 14.6.2：
Unadjusted Use Case Points (UUCP) / 14.6.3：
Technical Complexity Factor / 14.6.4：
Environmental Complexity Factor / 14.6.5：
Calculate Adjusted Use Case Points / 14.6.6：
Outlook / 14.7：
Using Functional Size Measurement Methods / 14.8：
Function Point Prognosis / 15.1：
Function Point Proportions / 15.1.1：
Other Early Function Point Proposals / 15.1.2：
IFPUG General Systems Characteristics (GSC) / 15.1.3：
Benefits of Early Function Point Estimates / 15.1.4：
Estimation of Person Months of Work Effort Based on Function Points / 15.2：
Productivity Analysis / 15.3：
Typical Function Point Counting Experiences / 15.4：
Business Functions Overview / 15.4.1：
Internal Logical Files (ILF) / 15.4.2：
Preface
List of Figures
List of Tables
50.

電子ブック
ＥＢ
50. The IT Measurement Compendium
Manfred Bundschuh, Carol Dekkers
出版情報: SpringerLink Books - AutoHoldings , Springer Berlin Heidelberg, 2008
所蔵情報: loading…
目次情報: 続きを見る
Preface
List of Figures
List of Tables
The Estimation Challenges / 1：
The Basics of Software Estimation / 1.1：
Measurement / 1.1.1：
Estimation / 1.1.2：
Estimation Precision / 1.1.3：
The Object of Estimation / 1.1.4：
Requirements (Scope) Creep / 1.1.5：
Measurement and Estimation / 1.1.6：
Measurement of Effort / 1.1.7：
Documentation / 1.1.8：
The Problem of Historic Data / 1.1.9：
Rules for Estimation / 1.2：
Basic Principles / 1.2.1：
Do's and Don'ts When Estimating / 1.2.2：
Estimation Errors / 1.2.3：
Political Estimates / 1.2.4：
Underestimation and Overestimation / 1.2.5：
The Estimation Conference / 1.2.6：
Estimation Honesty / 1.2.7：
Estimation Culture / 1.2.8：
Training for Estimation / 1.2.9：
A Checklist for Estimating / 1.3：
Internet Links for Software Measurement Associations and Estimation / 1.4：
Management Summary / 1.5：
Estimation Fundamentals / 2：
Estimation in a Project Controlling Environment / 2.1：
Adjusting the Estimate to Take into Account Project Environment Factors / 2.1.1：
Project Goals and the Devils Square of Project Management / 2.1.2：
Estimation and Quality / 2.1.3：
ISO/IEC 9126 Quality Attributes and IFPUG GSC / 2.1.4：
The Cybernetic Estimation Control Circuit / 2.1.5：
Determining Parameters of Estimation / 2.2：
The Purpose of Estimation / 2.2.1：
The Goals of Estimation / 2.2.2：
The Right Time for Estimation / 2.2.3：
Tracking of Estimates / 2.2.4：
Prerequisites for Estimation / 2.3：
The Information Basis of Estimation / 3.1：
Prerequisites for Estimation of Effort / 3.1.1：
Time Accounting / 3.1.3：
The Problem of Overtime Work / 3.1.4：
The Definition of the Application Boundary / 3.1.5：
The Type of Estimation / 3.1.6：
Customizing of Standard Software (Packages) / 3.1.7：
Documentation of the Development Environment / 3.1.8：
Validation of Estimates / 3.1.9：
The Process of Estimation / 3.2：
Distribution of Estimated Effort Across Project Phases / 3.2.1：
The Documentation of Project Estimates / 3.2.2：
The Implementation of Estimation / 3.3：
Report About a Successful Implementation / 4.1：
Positive and Negative Aspects of Software Measurement / 4.2：
Frequently Asked Questions / 4.3：
The Effort for Estimation / 4.3.1：
The Right Time to Implement a Formal Estimation Process / 4.3.2：
The Pros and Cons of a Competence Center / 4.3.3：
Acceptance Challenges / 4.4：
Counter the Counterarguments / 4.4.1：
Resistance / 4.4.2：
Information and Participation / 4.4.3：
Goals for an Estimation Process / 4.5：
Counting of Historical Projects / 4.6：
Estimation as an Early Warning System / 4.7：
Estimation Methods / 4.8：
The Challenges of Estimation Methods / 5.1：
Determination of the Effort / 5.2：
Estimation Based on an Experience Curve / 5.2.1：
Estimation Using an Estimation Equation / 5.2.2：
Estimation with an Expert System / 5.2.3：
Backfiring / 5.2.4：
Overview of Methods / 5.3：
Heuristic Methods / 5.3.1：
Size-Based Methods / 5.3.2：
Evaluation of an Estimation Method / 5.4：
User Comfort / 5.4.1：
Project Management / 5.4.2：
Quality of Result / 5.4.3：
Precision of Estimation Methods / 5.4.4：
Estimating Maintenance Effort / 5.5：
International Standards for Software Maintenance / 6.1：
ISO/IEC standards / 6.1.1：
FiSMA: Finnish Software Measurement Association / 6.1.2：
IFPUG: International Function Point Users Group / 6.1.3：
NESMA: Netherlands Software Metrieken Gebruikers Associatie / 6.1.4：
UKSMA: United Kingdom Software Metrics Association / 6.1.5：
Enhancement Projects / 6.2：
Software Metrics for Maintenance / 6.3：
Estimation of Maintenance Effort after Delivery / 6.4：
Estimation of Small Changes / 6.5：
Software Measurement and Metrics: Fundamentals / 6.6：
Terminology / 7.1：
Formal Definitions / 7.1.1：
Basic Measures (Measures) / 7.1.2：
Metrics / 7.1.3：
Indicators / 7.1.4：
Goals and Benefits of Metrics / 7.1.5：
Goals of Metrics / 7.2.1：
Benefits of Metrics / 7.2.2：
Start and Implementation of a Metrics Initiative / 7.3：
Establishing a Metrics Initiative / 7.3.1：
Establishing a Metrics Database / 7.3.2：
The Structure of a Metrics System / 7.3.3：
Product- and Process-Metrics / 7.4：
Product Metrics / 8.1：
Size of the Software Product / 8.1.1：
Source Code Metrics / 8.1.2：
Source Lines of Code / 8.1.3：
Functional Size / 8.1.4：
Project Size Categories / 8.1.5：
Software Quality / 8.2：
Defect Metrics / 8.2.1：
Function Points and Defects / 8.2.2：
System Complexity / 8.3：
Structural and Data Complexity / 8.4.1：
Halstead's Metrics / 8.4.2：
McCabe's Cyclomatic Complexity / 8.4.3：
Process Metrics / 8.5：
Work Effort / 8.5.1：
Productivity / 8.5.2：
PDR / 8.5.3：
Efficiency / 8.5.4：
Cost / 8.5.5：
Project Duration / 8.5.6：
Object-Oriented Metrics / 8.6：
Examples of Object-Oriented Metrics / 9.1：
Design metrics by Lorenz (1993) / 9.1.1：
The Metrics Suite from Chidamber and Kemerer, 1994 / 9.1.2：
Capers Jones' Object-Oriented Cost, Defect, and Productivity Metrics / 9.1.3：
The Survey of Xenos et al / 9.1.4：
Metrics for Defects and Size by Cartwright and Shepperd / 9.1.5：
Methods for Size from Catherwood et al / 9.1.6：
Class Metrics from Silvia Regina Vergilio and Chaves / 9.1.7：
Use Case Points / 9.1.8：
Further Examples of Object-Oriented Measures and Metrics / 9.1.9：
Projects that were Developed Using Object-Oriented Approaches in the ISBSG Benchmarking Database / 9.2：
Function Points and Object-Oriented System Development / 9.3：
IFPUG Function Points and OOA According to the Jacobsen Approach / 9.3.1：
IFPUG Function Points and UML / 9.3.2：
COSMIC and UML / 9.3.3：
Measurement Communities and Resources / 9.4：
The ISO Standards / 10.1：
The Capability Maturity Model Integration / 10.2：
The Goal Question Metric Method / 10.3：
The Balanced Scorecard / 10.4：
Important Software and Systems Measurement Organizations / 10.5：
Computer Measurement Group (CMG) / 10.5.1：
COSMIC Consortium / 10.5.2：
Finnish Software Measurement Association (FiSMA) / 10.5.3：
German Metrics Organization: DASMA / 10.5.4：
German GI Interest Group on Software Metrics / 10.5.5：
International Function Point Users Group (IFPUG) / 10.5.6：
International Software Benchmarking Standards Group / 10.5.7：
International Organization for Standardization / 10.5.8：
Metrics Association's International Network (MAIN) / 10.5.9：
Software Engineering Institute at Carnegie Mellon University in Pittsburgh, PA, USA / 10.5.10：
Standard Performance Evaluation Corporation (SPEC) / 10.5.11：
Transaction Processing Performance Council (TPC) / 10.5.12：
Internet Links to Measurement Communities / 10.6：
Benchmarking of IT Projects / 10.7：
Benchmarking Fundamentals / 11.1：
Practical Benchmarking Experiences / 11.2：
Benchmarking Databases / 11.3：
Academic Comparison of Measurement Databases / 11.3.1：
The ESA/INSEAD Database / 11.3.2：
ISBSG and Its Products / 11.4：
Demographics of ISBSG Repositories / 11.4.1：
ISBSG Products / 11.4.2：
Project Characteristics / 11.4.3：
Further Results of the ISBSG Research / 11.4.4：
Internet Links to Benchmarking Organizations / 11.5：
The IFPUG Function Point Counting Method / 11.6：
Functional Size Measurement Methods History / 12.1：
The Benefits of the IFPUG FPM / 12.2：
Leveraging the Use of Function Points (and the Analytical Approach) in Software Development / 12.2.1：
Function Points as Part of a Pricing Evaluation Process / 12.2.2：
Function Points as the Basis for Contract Metrics / 12.2.3：
Application Areas for Function Points / 12.3：
The Evaluation of Function Point-Based Estimation Methods / 12.4：
The Optimum Time to Count FPs / 12.5：
The Process of Function Point Counting / 12.6：
Step 1: Define the Type of Count / 12.6.1：
Step 2: Define the Scope of the Count and the Application Boundary / 12.6.2：
Step 3: Count Unadjusted FPs / 12.6.3：
Step 4: Calculate the VAF After Determining the 14 GSCs / 12.6.4：
Step 5: Calculate the Adjusted FPs / 12.6.5：
Step 6: Document the Count / 12.6.6：
Step 7: Quality Assurance of the Count by the Competence Center / 12.6.7：
The Process to Implement the IFPUG Function Point Counting Method / 12.7：
The Limitations of the IFPUG Function Point Counting Method / 12.8：
Functional Size Measurement Methods (FSMMs) / 12.9：
Short Characterizations of ISO/IEC-Conformant FSMMs / 13.1：
COSMIC / 13.2：
The COSMIC Counting Process / 13.2.1：
Software Layers in COSMIC / 13.2.2：
ISBSG Data with Respect to COSMIC / 13.2.3：
Comparison Between Counts Done Using COSMIC and IFPUG FPA / 13.2.4：
FiSMA 1.1 Functional Size Measurement Method / 13.3：
The FiSMA 1.1 Measurement Process / 13.3.1：
FiSMA 1.1 Components / 13.3.2：
Research Related to FiSMA 1.1 FSMM / 13.3.3：
Mark II Function Point Method / 13.4：
NESMA FPA / 13.5：
Similarities and Differences Between NESMA and IFPUG Function Point Standards / 13.5.1：
NESMA Function Points for Enhancements / 13.5.2：
Outlook for Functional Size Measurement Methods / 13.6：
Variants of the IFPUG Function Point Counting Method / 13.7：
The Data Point Method / 14.1：
Feature Points / 14.2：
Object Point Methods / 14.3：
SPR Function Points / 14.4：
3D Function Points / 14.5：
Unadjusted Use Case Weight (UUCW) / 14.6：
Unadjusted Actor Weight (UAW) / 14.6.2：
Unadjusted Use Case Points (UUCP) / 14.6.3：
Technical Complexity Factor / 14.6.4：
Environmental Complexity Factor / 14.6.5：
Calculate Adjusted Use Case Points / 14.6.6：
Outlook / 14.7：
Using Functional Size Measurement Methods / 14.8：
Function Point Prognosis / 15.1：
Function Point Proportions / 15.1.1：
Other Early Function Point Proposals / 15.1.2：
IFPUG General Systems Characteristics (GSC) / 15.1.3：
Benefits of Early Function Point Estimates / 15.1.4：
Estimation of Person Months of Work Effort Based on Function Points / 15.2：
Productivity Analysis / 15.3：
Typical Function Point Counting Experiences / 15.4：
Business Functions Overview / 15.4.1：
Internal Logical Files (ILF) / 15.4.2：
Preface
List of Figures
List of Tables
文献の複写および貸借の依頼を行う
 文献複写・貸借依頼