The OPEN Process Specification
Addison-Wesley Professional (Verlag)
978-0-201-33133-2 (ISBN)
- Titel ist leider vergriffen;
keine Neuauflage - Artikel merken
The OPEN Process Specification describes a tailorable software development process (part of the OPEN methodological framework) that has been formulated to take account of the differing requirements of projects and provide a flexible framework into which project-specific factors may be incorporated. Here the reader will find a genuinely object-oriented, complete, detailed model of the whole process involved in developing both object-oriented and hybrid systems. The model may be used in conjunction with any object-oriented method or notation, such as Coad, Firesmith, Odell, SOMA, or UML. This book shows how to use the OPEN process to organize, plan and manage both large- and small-scale object-oriented software development projects. The framework for the OPEN process consists of interconnecting activities, which are represented as objects whose methods are the tasks needing to be accomplished. This model provides a strategy that enables professional software developers, project managers and students of software engineering to approach all kinds of software development projects and succeed in achieving timely delivery and high quality products.As well as an in-depth description of the important activities associated with a project, and comprehensive coverage of the kinds of tasks which need to be achieved for different projects, this book also contains: *an extensive reference section containing a detailed description of each tas *recommended techniques that provide support for accomplishing each tas *a summary of the COMN Light Notation *a foreword by Ed Yourdon
Foreword Preface List of Abbreviations 1 Introduction to OPEN 1.1 Why object orientation? 1.2 What is a methodology? 1.3 What is OPEN? 1.3.1 A tailorable lifecycle model 1.3.2 Tasks and techniques 1.3.3 OO principles 1.3.4 COMN - OPEN's recommended notation 1.4 Who are the people involved in OPEN? 1.5 About this book References 2 Process as the keystone 2.1 The need for process 2.2 What is a process? 2.3 Clarification of terminologies 2.4 The software process 2.5 Process models 2.6 The contract-driven lifecycle 2.6.1 Programmes and projects References 3 Seamlessness 3.1 The need for seamlessness 3.2 OOAD terminology 3.2.1 Analysis 3.2.2 Design 3.2.3 An alternative to 'analysis' and 'design' 3.2.4 Implementation and testing 3.3 'Analysis' and 'design' in OPEN References 4 OPEN activities 4.1 Timeboxes 4.2 Project initiation 4.3 Requirements engineering 4.4 Analysis and model refinement 4.5 Project planning 4.6 Build 4.6.1 Evolutionary Development 4.6.2 User review 4.6.3 Consolidation 4.7 Evaluation 4.8 Implementation planning 4.9 Programme planning 4.10 Resource planning 4.11 Domain modeling 4.11.1 Hairies and conscripts: making reuse work in the organization 4.12 Other projects 4.12.1 Rewarding reuse 4.13 Bug fixing 4.14 Use of system References 5 OPEN tasks 5.1 User interactions and business issues 5.2 Large-scale architectural issues 5.3 Project management issues 5.3.1 Business and large-scale project planning 5.3.2 Project management 5.3.3 Testing and quality 5.3.4 The ongoing review process 5.4 Database issues 5.5 Distribution issues 5.6 Modeling/building the system 5.6.1 Analysis of requirements 5.6.2 CIRT identification 5.6.3 Building the object model 5.6.4 User interface design 5.6.5 Role modeling 5.6.6 Design optimization 5.6.7 Usability design 5.6.8 OOPLs 5.6.9 Documentation 5.7 Reuse issues 5.7.1 Optimize reuse ('with reuse') 5.7.2 Create new reusable components ('for reuse') 5.7.3 Manage library of reusable components References 6 OPEN Techniques References 7 OPEN Deliverables References Appendix A OPEN tasks in alphabetical order Task: Analyze user requirements Task: Code Task: Construct the object model Task: Create and/or identify reusable components ('for reuse') Subtask: Construct frameworks Subtask: Optimize for reuse Task: Deliver product to customer Task: Design and implement physical database Subtask: Distribution/replication design Subtask: Operational and performance design Subtask: Performance evaluation Task: Design user interface Task: Develop and implement resource allocation plan Subtask: Choose hardware Subtask: Choose project team Subtask: Choose toolset Subtask: Decompose programme into projects Subtask: Develop education and training plan Subtask: Develop iteration plan Subtask: Develop timebox plan Subtask: Identify project roles and responsibilities Subtask: Manage subsystems Subtask: Set up metrics collection programme Subtask: Specify individual goals Subtask: Specify quality goals Subtask: Use dependencies in the BOM to generate Task: Develop business object model Task: Develop software development context plans and strategies Subtask: Develop capacity plan Subtask: Develop contingency plan Subtask: Develop security plan Subtask: Establish change management strategy Subtask: Establish data take-on strategy Subtask: Integrate with existing, non-OO systems Subtask: Tailor the lifecycle process Task: Evaluate quality Subtask: Analyze metrics data Subtask: Evaluate usability Subtask: Review documentation Task: Identify CIRTs Subtask: Determine initial class list Subtask: Identify persistent classes Subtask: Identify roles. Subtask: Refine class list Task: Identify context Task: Identify source(s) of requirements Task: Identify user requirements Subtask: Define problem and establish mission and Subtask: Establish user requirements for distributed system Subtask: Establish user database requirements Task: Maintain trace between requirements and design. Task: Manage library of reusable components. Task: Map logical database schema Task: Map roles on to classes Task: Model and re-engineer business process(es) Subtask: Build context (i.e. business process) model Subtask: Build task object model Subtask: Convert task object model to business object model Subtask: Do user training Subtask: Prepare ITT Task: Obtain business approval Task: Optimize reuse ('with reuse') Task: Optimize the design Task: Test Subtask: Acceptance testing Subtask: Class testing Subtask: Cluster testing Subtask: Regression testing Task: Undertake architectural design Subtask: Develop layer design Subtask: Establish distributed systems strategy Subtask: Select database/storage strategy Task: Undertake feasibility study Task: Undertake in-process review Task: Undertake post-implementation review Task: Undertake usability design Task: Write manuals and prepare other documentation References Appendix B The COMN Light notation B.1 COMN's core notational elements B.2 Basic relationships in COMN B.2.1 Definitional relationships B.2.2 Referential relationships B.2.3 Transitional and scenario relationships References Appendix C The OPEN-MeNtOR project References Appendix D Migration strategies References Bibliography Index
| Erscheint lt. Verlag | 13.10.1997 |
|---|---|
| Reihe/Serie | ACM Press |
| Sprache | englisch |
| Maße | 178 x 242 mm |
| Gewicht | 615 g |
| Themenwelt | Informatik ► Software Entwicklung ► Objektorientierung |
| ISBN-10 | 0-201-33133-0 / 0201331330 |
| ISBN-13 | 978-0-201-33133-2 / 9780201331332 |
| Zustand | Neuware |
| Haben Sie eine Frage zum Produkt? |
aus dem Bereich
