Identify Estimation Input (Process Notes 7.3.1)


Each of your requirements that has passed through the Quality Gateway will contain a measurement. You can use your measurable requirements as input to estimating the effort needed to do the project.

If your requirements specification includes events or use cases, then you have manageable chunks that you can use as the input to your effort estimation.

For each event/use case you should have the following items:

  • Event name.

  • All functional requirements that are connected by this event.

  • All nonfunctional requirements that are connected by this event. If you have not identified the nonfunctional requirements, then you can still make an estimate based on events. However, you will have to use an estimated weighting to assess the impact of the nonfunctional requirements.

  • A definition of all data that is input to or output from the event. This might come from the world outside the system or it might be stored data.

If you have an event description or specification, it will make the estimate more accurate.

If your requirements specification does not include events or use cases, then you can use the individual requirements as input to your effort estimation.

Use the functional requirements to estimate the effort based on the essential functions and data within your context of study. The nonfunctional requirements provide input to help you weight the estimates depending on the number and difficulty of the nonfunctional requirements that relate to each functional requirement.




Mastering the Requirements Process
Mastering the Requirements Process (2nd Edition)
ISBN: 0321419499
EAN: 2147483647
Year: 2006
Pages: 371

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