About this product

Product Identifiers

PublisherAddison Wesley Professional

ISBN-100201178893

ISBN-139780201178890

eBay Product ID (ePID)888350

Product Key Features

Number of Pages192 Pages

LanguageEnglish

Publication NameDynamic Systems Development Method

Publication Year1997

SubjectSoftware Development & Engineering / General, Software Development & Engineering / Systems Analysis & Design

TypeTextbook

AuthorPeter Constable, Jennifer Stapleton

Subject AreaComputers

FormatHardcover

Dimensions

Item Height0.6 in

Item Weight14.9 Oz

Item Length9.4 in

Item Width6.4 in

Additional Product Features

Intended AudienceScholarly & Professional

LCCN97-014396

IllustratedYes

Table Of ContentIntroduction. Background. Some definitions. A bit of history. Overview of the method. Why is DSDM more rapid than the waterfall? About this book. I. THE METHOD. 1. DSDM process overview. Introduction. The feasibility study. The business study. Functional model iteration. Design and build iteration. Implementation. Key points. 2. The underlying principles. Key points. 3. The process in action. When to use DSDM. The reality of iteration and incremental delivery. Analysis and design techniques. Key points. 4. Time versus functionality. Fitting quarts into pint pots. Timeboxes. MoSCow rules. Controlling timebox activity. To timebox or not? The disaster scenario. Key points. 5. The RAD project manager in action. What is different? Planning a DSDM project. The project roles. Project structures. Monitoring progress. Workload. Key points. 6. Impact on the organization. Making decisions. User involvement. Better communication. Joint application design (JAD) workshops. Training users. Key points. 7. Never mind the quality? ''Good enough'' software. Building in quality. Testing. DSDM and TicklT. New procedures for old. The capability maturity model. Key points. 8. The RAD professional. 'No more quick and dirty''. Skills and attributes. Self-management. Key points. 9. Prototyping is not a waste of time. Bridging the language barriers. But the users keep changing their minds! Categories of prototypes. Getting effective feedback. Keeping control. Key points. 10. Technology support. The need for technology support. DSDM support environments. Testing tools. Configuration management tools. Effective tool usage. Key points. II. CASE STUDIES. 11. A measured DSDM project--BT. The approach to DSDM. Quality and testing. Training and team building. Project roles and planning. External relationships--managing critical interactions. The project diary. Project data. Effort and resource data. The team''s perceptions of the project. The unit''s perception of DSDM and the project. Conclusions and lessons learnt. Appendix: Results of the project review meeting. What worked well. What worked less well--lessons, issues, questions. 12. How not to do RAD. The project. What had gone wrong? So what did he do? 13. A customer view--Scottish Natural Heritage. The project. 14. Project support--PGT Consultants. Background. The project. Briefing for workshop participants. Initial workshop. The project reviews. Summary. 15. An early adopter case study--Sysdeco. Introduction. The project. 16. Assessing the quality aspects of DSDM--Sema Group. Introduction. Background. British Midland. Diamond Club redevelopment. How DSDM was applied. User involvement. Feasibility study. Estimating. Business study. Project management. Functional model iteration. Prototype management. Testing. Design and build iteration. Configuration management. Quality assurance. Implementation. The business benefit for BM. What Sema Group has learned. 17. Applying DSDM to a batch and online system upgrade--Orange. Introduction. Lifecycle/process framework. Orange design process. User involvement. Orange development process. Orange testing process. Conclusions. Appendix. 18. A pre-DSDM RAD project. Introduction. Background. Technical environment. System description. Project planning and organization. Compare and contrast with DSDM. End users. Compare and contrast with DSDM. Phase 1--initial fact-finding, first design and prototype. Compare and contrast with DSDM. Phase 2--iterative prototyping, further design. Compare and contrast with DSDM. Phase 3--delivery and documentation. Compare and contrast with DSDM. Lessons learnt. Conclusion. III. INFORMATION. 19. Where do I go from here? Contact the DSDM Consortium. Get trained. A mentor is essential.</di

SynopsisDSDM is about people, not tools. It is about truly understanding the needs of a business, delivering software solutions that work and delivering them as quickly and as cheaply as possible.The Dynamic Systems Development Method provides a framework of controls and best practice for Rapid Application Development. It was created by a consortium of organisations and it has been proved, since its publication in January 1995, to be extremely effective in delivering maintainable systems which match the needs of the business better than those produced using traditional lifecycles.This book, commissioned by the DSDM Consortium and written by the chairman of the Technical Committee which developed the method, explores the day-to-day realities of implementing the method. It is a practitioner's guide, dealing with issues such as how to get people from different disciplines to work together as a team, how to gain commitment and how to manage projects within normal business constraints.In this book you will find: practical guidelines on the implementation of key elements of the method such as timeboxes and the MOSCOW Rules clear recommendations for the roles and responsibilities of the members, DSDM is about people, not tools. It is about truly understanding the needs of a business, delivering software solutions that work and delivering them as quickly and as cheaply as possible. The Dynamic Systems Development Method provides a framework of controls and best practice for Rapid Application Development. It was created by a consortium of organisations and it has been proved, since its publication in January 1995, to be extremely effective in delivering maintainable systems which match the needs of the business better than those produced using traditional lifecycles. This book, commissioned by the DSDM Consortium and written by the chairman of the Technical Committee which developed the method, explores the day-to-day realities of implementing the method. It is a practitioner's guide, dealing with issues such as how to get people from different disciplines to work together as a team, how to gain commitment and how to manage projects within normal business constraints. Do you want to cut the development time and increase the fitness-for-use of screen based business applications, by orders of magnitude? This book will enable those in organisations which develop or purchase tailored IT systems, to gain a clear understanding of the benefits of the incremental and iterative approach embodied in the DSDM.

LC Classification NumberQA76.76.D47S7 1997