Cargando…
Requirements modelling and specification for service oriented architecture /
Many software developers often confuse requirements engineering with software specification and, as a result, build unusable systems, despite meeting specifications. Bringing together all the techniques needed by the modern software developer, here is a practical handbook to requirements engineering...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Chichester, England ; Hoboken, N.J. :
Wiley,
©2008.
|
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Requirements Modelling and Specification for Service Oriented Architecture; Contents; Foreword by Mark McGregor; Foreword by Professor Neil Maiden; Preface; 1 Principles of SOA; 1.1 Why Projects Fail; 1.2 Aligning IT with Business
- Speaking a Common Language; 1.2.1 Models; 1.3 What is Service Oriented Architecture?; 1.3.1 The Real User; 1.4 Business Drivers for SOA; 1.5 Technology Drivers; 1.6 Benefits, Pitfalls and Prospects; 1.6.1 Pitfalls; 1.6.2 Post-SOA Benefits; 1.7 Migration Strategies; 1.8 Summary; 1.9 Bibliographical Notes; 2 Architecture
- Objects, Components, Services
- 2.1 What is Architecture?2.1.1 Architecture as High Level Structure; 2.1.2 Architecture as Design Rationale or Vision; 2.1.3 Architecture and Reuse; 2.2 Architecture through the Ages; 2.3 Objects and Components; 2.3.1 Components for Flexibility; 2.3.2 Large-Scale Connectors; 2.3.3 How Services Relate to Components; 2.4 Architecture and SOA; 2.5 Stateless Services; 2.6 Practical Principles for Developing, Maintaining and Exploiting SOA; 2.7 Summary; 2.8 Bibliographical Notes; 3 Approaches to Requirements Engineering; 3.1 Conventional Approaches; 3.1.1 Approaches Based on Human Factors
- 3.2 Classic Requirements versus Use Cases3.2.1 UML Basics; 3.2.2 Use Case Models; 3.2.3 Formulating Requirements; 3.3 Problem Frames; 3.4 Requirements and Business Rules; 3.5 Establishing and Prioritizing the Business Objectives; 3.6 Soft Techniques for Requirements Elicitation; 3.6.1 Using Interviewing Techniques; 3.6.2 Repertory Grids; 3.6.3 Hierarchical Task Analysis; 3.6.4 Object Discovery Techniques; 3.7 Summary; 3.8 Bibliographical Notes; 4 Business Process Modelling; 4.1 The Origins of and Need for Business Process Modelling; 4.2 Business Process Modelling in a Nutshell
- 4.3 UML Activity Diagrams4.4 BPMN; 4.4.1 Fundamental Business Process Modelling Patterns; 4.4.2 A Practical Example; 4.5 WS-BPEL; 4.6 Orchestration and Choreography; 4.7 Process Algebra and Petri Nets; 4.8 The Human Side of Business Process Management; 4.9 Summary; 4.10 Bibliographical Notes; 5 Catalysis Conversation Analysis; 5.1 What is a Business Process?; 5.2 Conversations; 5.3 Conversation Stereotypes and Scripts; 5.3.1 Handling Exceptions; 5.4 Conversations as Components; 5.5 Contracts and Goals; 5.6 Conversations, Collaborations and Services; 5.7 Checking Model Consistency; 5.8 Summary
- 5.9 Bibliographical Notes6 Models of Large Enterprises; 6.1 Business Process Modelling and SOA in the Large; 6.2 Business Rules in the Mission Grid; 6.3 The Mission Grid as a Roadmap for SOA; 6.4 Other Approaches; 6.5 Summary; 6.6 Bibliographical Notes; 7 Specification Modelling; 7.1 From Requirements to Specification; 7.2 Some Problems with the Conventional Approach to Use Cases; 7.2.1 Overemphasis on Functional Decomposition; 7.2.2 Lack of Clear Definition; 7.2.3 Controller Objects; 7.2.4 Use Cases and Scenarios; 7.2.5 Essential or Generic Use Cases; 7.2.6 Atomicity