Why do requirements matter? Experience has shown that insufficient attention is paid to requirements. The price paid for this lack of focus and applied practices is systems that don't meet customer needs; take longer to develop than planned; and cost more than customers are willing to pay.

 

Are we ready to change? Are you willing to spend some time and effort involved in practical exercises to experience how better requirements should evolve? If yes, commit to digesting the counsel of two experienced practitioners and to changing current practices to ones that will produce better results.

 

Alexander and Stevens have described how to identify stakeholders and capture requirements, how to write good requirements, how to structure and organize requirements for system developers, and how to review requirements informally and formally. They have provided a set of useful references to further support your efforts.

 

Experience has shown us that investment in the requirements process saves time, money, and effort. Yet, development efforts consistently charge ahead without investing sufficiently in the requirements process. We are so intent to develop the technical solutions that we are unwilling to take the time and effort to understand and meet the real customer needs.

 

Gathering requirements is the most critical activity in providing a new system or capability. How many of us are willing to invest the time, effort, and money in identifying the real customer needs before we start off spending technical resources in developing a system? The pressure to start writing code and produce "working" software is great - accentuated by our managers' quest for "results" and everyone "being busy!"

 

Ian Alexander and Richard Stevens are interested in helping you to evolve requirements that meet real customer needs. They have provided an approach that is based on experience and lessons learned from decades in "the school of practical experience."

 

Your software and system development efforts and activities will benefit from their advice. Take the time to digest their sage advice and make the effort to respond to the exercises. Apply these concepts and lessons to your own development efforts.

 

In short, Ian Alexander and Richard Stevens have provided a practical guide for those who endeavor to satisfy customers.

You would..
Share
Related Documents
  1. một ví dụ về spec mô tả màn hình (1474)
  2. [Ebook] Essential CVS (Manual) (2354)
  3. Continuing to Meet User Expectations with Requirements Traceability (465)
  4. Webinar : Requirements with User Stories (498)
  5. CPRE Certificate : Sylllabus (Requirement) (1887)
  6. Does Tester care about configuration management (CM)? (776)
  7. Agile Requirements: Not an Oxymoron (472)
  8. Managing Requirment & use case (579)
  9. When the requirements fail (1098)
  10. [Free] Revision Control System (RCS) (889)
  11. Software Requirements Spec for Project Manager (1266)
  12. Art of writing the Use cases (1414)
  13. Use Case Template (3732)
  14. Use case document for fountain pen (2455)
  15. Requirement Traceability Matrix (2783)
  16. Software Requirements Specification (Tài liệu đặc tả yêu cầu) (4173)
  17. Silk Central Requirement Management (2676)
  18. Role of the Business Analyst (1077)
  19. [Ebook] Business Analysis Body of Knowledge (BABOK) (10251)
  20. Requirements Traceability Matrix (2122)

Thanks and best regards

Nguyen Hoang Lam

Manager of Quality & Process Management Department

LacViet Computing Corporation

YahooID : lamnh70@yahoo.com