4 Key Users Needs

List the key problems with existing solutions as perceived by the stakeholder. Clarify the following issues for each problem:

• What are the reasons for this problem?

• How is it solved now?

• What solutions does the stakeholder want?

It is important to understand the relative importance the stakeholder or user places on solving each problem. Ranking and cumulative voting techniques indicate problems that must be solved versus issues they would like addressed.

5 Alternatives and Competition

Identify alternatives the stakeholder perceives as available. These can include buying a competitor’s product, building a homegrown solution or simply maintaining the status quo. List any known competitive choices that exist, or may become available. Include the major strengths and weaknesses of each competitor as perceived by the stakeholder.

6 Project Overview

6.1 System Scheme

6.2 Summary of Capabilities and Features Attributes

6.2.1 Features Attributes

Each feature of the system list in following chapters has some attributes assigned to it. These attributes are Importance, Difficulty and Risk Level. The tables below describe possible attributes values and their means.

The Importance Level attribute describes the degree of necessity of the feature in system implementation.

Table 1 – Feature Importance Levels

Importance Level	Description
Critical	The feature marked as critical has high importance and is MUST for implementation in closest system version.
Important	The feature marked as important is necessary for product and has an influence on product success so it is to be developed as high priority function. The implementation of the feature can be delayed for next product version release
Desirable	The feature marked as desirable has lower importance level and may be not implemented in product versions

The Difficulty Level attribute describes the degree of feature programming and implementation process complexity.

Table 2 – Feature Difficulty Levels

Difficulty Level	Description
High	The feature requires a lot of people or hardware resources for implementation or supposes usage of complex solutions or technologies
Medium	The feature requires a lot of people or hardware resources for implementation
Low	The feature supposes usage of small amount of resources and supposes short development term

The Risk Level shows the possibility of implementation success and budget exceeding when programming the feature.

Table 3 – Feature Risk Levels

Risk Level	Description
High	The feature supposes using of new or unknown technology or algorithm that may cause budget exceeding or additional resources involving
Medium	The feature supposes usage of technology or algorithms that are rather understood and may be precisely estimated
Low	The feature supposes usage of known or easy technology or algorithms that are rather understood and may be precisely estimated