msaad

Ingredients of a Problem Statement

A good problem statement describes 

A-Current situation:

The Problem to be solved // target of system.

Description of one or more scenarios //have 2 or 3 scenario to be describe.

B-Requirements
(Elicitation)

Functional and Nonfunctional requirements
//you must
to define Function and Quality attribute.

Constraints (”pseudo requirements”) // if customer need specific tool.

Project Schedule

Major milestones that involve interaction with the client //what is the first deliver to Customer.

including deadline for delivery of the system

Deliverables expected by the client // all component of system (Training-Source code).

Target environment

The environment in which the delivered system has to perform a specified set of system tests.

// system environment (HW, SW)

Client Acceptance Criteria

Criteria for the system tests. //we need to know exactly what and when is needed from system

(Deliver information from system to user).

//Like IBM web site Sport that have delay in result after play game