Computer Science and Software Engineering 371

Software Requirements and Specification

Fall 2005

Exam 1 Review Solution

1. Function:

What Eboda would like is something called a Feature Tracker, which would track and organize all the features to be put into each of the company’s line of software products.

Form:

Specifically, Feature Tracker must log and organize features planned and delivered as part of the company’s 20 different consumer products.

Economy:

It would help Eboda understand strategically the mix of features being put into somewhat similar-looking products, in order to keep them distinguished and individually marketable.

Time:

We need the solution in 6 months, because this is when half of the development work is being moved to Eboda’s new facility in North Carolina.

2. The problem statement captures the perceived problem of the stakeholders in a specific format. It therefore is a reflection of the stakeholders’ needs. On the other hand, the vision statement states how the company envisions solving the perceived problem. Items contained in the vision document because of this include cost estimates; a risk assessment (low, medium or high) for each feature; and exemplary use cases.

3. In an ongoing project, the users already have an idea of the basic way to use the system, so a storyboard may actually be a step back from the more polished user interface of the current system, while for a new system, no such user interface currently exists, and the storyboard can help with its formulation.

4. ● Do not allow criticism or debate. This is to keep the ideas flowing without people being concerned about reaction to them.

· Let your imagination soar. This is because “thinking outside of the box” will allow a greater chance of finding the best solution.

· Generate as many ideas as possible. Once again, that will allow a greater chance of finding the best solution.

· Mutate and combine ideas. This is in order to not have similar but competing ideas when starting idea reduction.

5.