13.2 REQUIREMENTS SPECIFICATION

 < Day Day Up > 



13.2 REQUIREMENTS SPECIFICATION

Once you get past the Initiation stage you can adopt a formal project lifecycle, Figure 13.5. First, find out what is required. If at all possible, obtain a customer authority, that is someone to whom you will deliver and who will decide what is to be delivered.

start figure

Obtain Customer Authority

Identify customers and customer groupings

Set up liaison mechanisms- e.g. MCG

Obtain requirements - standard systems/business analysis

Group requirements - identify subproject streams

Prepare and review requirements specification

SPECIFY TOR

end figure

Figure 13.5: Requirements Specification

Look to your customers—these are usually internal to the organization, rarely external, although it is the business needs of the end customers that provides the context of the metrics program.



 < Day Day Up > 



Software Metrics. Best Practices for Successful It Management
Software Metrics: Best Practices for Successful IT Management
ISBN: 1931332266
EAN: 2147483647
Year: 2003
Pages: 151
Authors: Paul Goodman

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net