Soft work Video-chapter II __ Computer Learning

I. Feasibility STUDY REPORT

1. Defining the problem

(1) Definition content

① problem background, development system status, development conditions and reasons, general requirements

② the nature of the problem, type conversion, objectives, development conditions, environmental requirements, etc.

(2) Steps

2. Feasibility Study

(1) Discussion from five aspects

① Economic Feasibility

② Technical Feasibility

③ Operation Feasibility

④ Legal Feasibility

⑤ Time Feasibility

(2) The steps of the feasibility study

Ii. content of software plan

1. Software proposal: Use the terminology that administrators, technicians and users can understand to describe specific

Including:

① Software scope: The content must have: the SOFTWARE function scale, the software ability to the hardware request, the interface interface nature and the complexity

② Environmental Resources:

Human resources, requirements for different people at different stages

Hardware, including target machines, and other machines

Software, including support software and utility software

Make a schedule, including delivery date, how to organize the distribution of power

Software costs, as long as both sides can accept

2. Software Requirements Analysis

(1) The task of software requirement analysis

① deeply describes the function and performance of the software

② determine the constraints of software design and the interface details of software with other system elements

③ defines other validity requirements for software

PS: The task of requirement analysis is to derive the logic model of the target system with the help of the logic model of the current system, and solve the problem of "what to do" in the target system.

(2) The requirements of the software include

(3) Common methods of analysis

①-oriented Data flow structured analysis Method (SA)

②-oriented data structure of the Jackson Method (JSD)

③ structured Data System development method (DSSD)

④ Object-Oriented Analysis method (OOA), etc.

(4) The principle of software requirement analysis

① need to be able to express and understand the problem of the information domain and the functional domain

② should be able to analyze and refine the problem in a hierarchical way

(5) The principle of software Requirement specification

① separates functions from reality by describing what to "do" rather than "how to do It"

② requires the use of a processing-oriented specification language

(6) Software requirements method

The ① requirement Analysis method consists of the information domain and the functional domain system analysis process and the representation method of the software problem.

② Most of the requirements analysis methods are driven by information

(7) Structural analysis method

① method of demand analysis oriented to data flow

② Structural analysis method is suitable for data processing type software requirement analysis