Software Scope Estimation

What is Software scope estimation?

Software scope estimation
Software scope describes the data and control to be processed, function, performance, constraints, interfaces,
and reliability. Determination of the software scope is a prerequisite of all sorts of estimates, including,
resources, time, and budget. In order to understand the scope, a meeting with the client should be arranged.
The analyst should start with developing a relationship with the client representative and start with contextfree
questions. An understanding of the project background should also be developed. This includes
understanding:
• Who is behind the request (sponsor)?
• Who will use the solution (users)?
• What are the economic benefits (why)?
Now is the time to address the find out the more about the product. In this context, the following questions
may be asked:
• How would you characterize good output?
• What problems will the solution address?
• Can you show me the environment in which the solution will be used?
• Will any special performance issues or constraints affect the way the solution is approached?
• Are you the right person to answer these questions? Are answers ―official‖?
• Are my questions relevant to the problem that you have?
• Am I asking too many questions?
• Can anyone else provide additional information?
• Should I be asking you anything else?
In this regards, a technique known as Facilitated Application Specification Techniques or simply FAST
can be used. This is a team-oriented approach to requirement gathering that is used during early stages of
analysis and specification. In this case joint team of customers and developers work together to identify the
problem, propose elements of the solution, negotiate different approaches, and specify a preliminary set of
requirements.