Software Engineering Fundamentals icon (the third chapter needs analysis)

learning target:

1) needs analysis related concepts

2) needs analysis tasks and procedures

3) requirements change management

4) the question: process-oriented analysis, focus: a data flow graph

5) the title: the object-oriented analysis, focus: with FIG Example

Requirements: clear, concise, unambiguous

Task: analysis model, writing requirements specifications

1) needs to confirm: requirements elicitation - needs refining (modeling) - Description of Requirement - needs verification

2) the demand for change <changing requirements must be mentioned Party>

3) requirements elicitation

Types of:
- (1) functional requirements
- (2) non-functional requirements: limited selection solutions to the problems of range (platform, language, etc.)　　
Demand access to technology:
- Interview, setting the scene (play), prototype, meetings, observe business processes and workflows　　
face the challenge:
- Customer demand can not tell　　
  - - distinguish what is a steady demand, the core on which to build　　　　
  - - say clearly "what" and "don'ts"　　　　
Demand induced ten principles
- (1) Listen　　
- (2) those who are prepared to communicate (table)　　
- (3) need someone to push　　　　
- (4) the best face to face communication　　
- (5) record all decisions (signature)　　
- (6) to maintain full cooperation　　
- (7) focus and coordination topic　　
- (8) The graphical representation　　
- (9) move on principle　　
- (10) the principle of win-win negotiation

4) refining needs (requirements analysis)

5) Description of Requirement

6) demand verification (third party)

1) From the structural analysis: top to bottom, gradually refined hierarchical data flow graph

(1) name　　

(2) determining the input and output streams

(3) the top-level data flow diagram (Layer 0)

Source (4) of the main data stream input and output end

2) The main graphic elements

(1) data processing (data conversion) - Round

(2) a data source or a key (external entities) - Rectangular

(3) data flow - arrow

(4) data storage file

(5) File - bis transverse / horizontal single file name +

3) Data flows and data processing in conjunction with FIG.

4) Note: (1) the data stream! = Control flow (2) is not excited condition Standard