9 replies
by trmweb
by jg
by sdw5177
The CAB should really be CBA for Cost Benefit Analysis.
Darn fingers!
Thanks for the feedback.
Scott
by esb_us
Requirements Process needs more content -
a. Emphasis on Business Goals & Objectives. Business objectives must be enumerated and all functional and non-functional requirements should be cross-referenced to the enumerated business objectives. Business objectives should be stated by stakeholders.
b. Scope document should tally with business objectives. Any changes in scope should be done with a change management process and tallied with enumerated business objectives. Therefore, any change in requirements would be reflected as a change in business objectives.
c. 'Phase 5 - Managment' should also include an 'Alignment' chapter. This would describe alignment of the system being built with the business objectives - this can be done viakey metrics (scorecard-type mapping).
Over 70% of failed systems (developed, overbudget, overdue, cancelled, etc) are attributed to a failure in Requirements process.
The Requirements Process is a human communication & collaboration process and has very little to do with the system's technology. It is a reflectance of the management process, good or bad.
S.B. Chatterjee
Manager, Business Tech Services
KeyTech, LLC
Hartford, CT
I think a really big point to make is that a purpose of requirements management is to avoid unrealistic expectations.
In web development, I frequently (more like *always*) find that the customer is shocked at how much designing has to go on before even one line of production code gets written, much less dealing with the tiered data management that every app needs.
by sdw5177
Definitely. Hopefully if we do our Requirments process correctly we can delivery this message as well.
Great insight.
Scott
by tdean2000
by kevinh
Requirements Management that has been employed successfully in aerospace systems (including software)involves generally four phases: Identification, Analysis, Implementation and Verification. Analysis considers the clarity, accuracy, achievability,ownership and verifiability of each requirement, and very well may result in splitting a single (or several) requirements into many, consolidating several into into less, or spawning the creation or of completely new requirements or deletion of requirements. Requirements Analysis incorporates the elements of mapping (to system entities, owners, etc.), allocation, and negotiation. Requirements Verification is the process of determining the compliance of the system to the set of requirements thathas been levied on it. It involves identifying and mapping verification methods (similarity, inspection, analysis, demonstration, test, etc.) to each requirement, and determining compliance by executing those methods.
Those interested can find information on disciplined requirements management processes at the International Council on System Engineering at www.incose.com, the Software Engineering Institute at www.cmu.edu, and the Software Productivity Consortium at www.software.org).
by kfp36
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending