close
1.

電子ブック

EB
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:
2.

電子ブック

EB
Sebastian Nanz, Sebastian Nanz
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2011
所蔵情報: loading…
目次情報: 続きを見る
Some Future Software Engineering Opportunities and Challenges / Barry Boehm
Seamless Method- and Model-based Software and Systems Engineering / Manfred Broy
Logical Abstract Domains and Interpretations / Patrick Cousot ; Radhia Cousot ; Laurent Mauborgne
Design Patterns - Past, Present & Future (Abstract) / Erich Gamma
Evidential Authorization / Andreas Blass ; Yuri Gurevich ; Michat Moskal ; Itay Neeman
Engineering and Software Engineering / Michael Jackson
Tools and Behavioral Abstraction: A Direction for Software Engineering / K. Rustan M. Leino
Precise Documentation: The Key to Better Software / David Lorge Parnas
Empirically Driven Software Engineering Research (Abstract) / Dieter Rombach
Component-based Construction of Heterogeneous Real-time Systems in BIP (Abstract) / Joseph Sifakis
Computer Science: A Historical Perspective and a Current Assessment (Abstract) / Niklaus Wirth
Internet Evolution and the Role of Software Engineering / Pamela Zave
Mining Specifications: A Roadmap / Andreas Zeller
Afterword
Greetings to Bertrand on the Occasion of his Sixtieth Birthday / Tony Hoare
Some Future Software Engineering Opportunities and Challenges / Barry Boehm
Seamless Method- and Model-based Software and Systems Engineering / Manfred Broy
Logical Abstract Domains and Interpretations / Patrick Cousot ; Radhia Cousot ; Laurent Mauborgne
3.

電子ブック

EB
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:
4.

電子ブック

EB
V.S Alagar, K. Periyasamy
出版情報: Springer eBooks Computer Science , Springer London, 2011
所蔵情報: loading…
5.

電子ブック

EB
Jos? Bacelar Almeida, Jos? Bacelar Almeida, Maria Jo?o Frade, Maria Jo?o Frade, Sim?o Melo de Sousa, Jorge Sousa Pinto
出版情報: Springer eBooks Computer Science , Springer London, 2011
所蔵情報: loading…
6.

電子ブック

EB
Gerard O'Regan
出版情報: Springer eBooks Computer Science , Springer London, 2011
所蔵情報: loading…
7.

電子ブック

EB
Sarnath Ramnath, Brahma Dathan
出版情報: Springer eBooks Computer Science , Springer London, 2011
所蔵情報: loading…
8.

電子ブック

EB
Ozgur Akan, Paolo Bellavista, Jeffrey S. Chase, Jeffry S. Chase, Anastasius Gavras, Athanasius Gavras, Thomas Magedanz, Huu Thanh Nguyen
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2011
所蔵情報: loading…
9.

電子ブック

EB
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:
10.

電子ブック

EB
Alexander L. Wolf Peri L. Tarr, Peri L. Tarr, Alexander L. Wolf
出版情報: Springer eBooks Computer Science , Springer Berlin Heidelberg, 2011
所蔵情報: loading…
文献の複写および貸借の依頼を行う
 文献複写・貸借依頼