Reducing the risk of development failure

with cost-effective capture and management of requirements

Cover from Reducing the risk of development failure

Date:
By:
Format: White Paper
Content Copyright © 2013 Bloor. All Rights Reserved.

Free Download (subject to terms)
To access this paper you must Register and Log In

Requirements management has been around for a long time as a systems engineering discipline, but it’s suddenly getting interesting again, in a wider field. With the rise of DevOps, mobile app development and Smarter Computing and with a new focus on Systems Engineering, Requirements Management is being recognised as an enabler for success with some exciting innovations in these areas. It also has a part to play in satisfying the emerging focus on regulatory requirements.

Requirements management starts with capturing and prioritising useful requirements. It’s not so much about developing automated business and embedded systems right (we have more-or-less formalised engineering processes and tools to help us do that), it’s about ensuring that the right systems are delivered (i.e. it’s all about ensuring that what is delivered is in line with business strategy, product vision etc.).

Reader reviews:

There are no published reviews.

Post a review?

Did you find this research interesting? Do agree, or disagree? Please share your thoughts.

All fields are required unless stated otherwise.

Star Rating 1-5 (low-high):

Please note: Your full name will appear against this review. Whilst your email address is never published, it may be used to contact you in response to your comment.