Shulou(Shulou.com)06/02 Report--

This article is about determining exactly what the software system must do in the software life cycle. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

In the software life cycle, the stage of solving "what the software does" is: requirements analysis. Requirements analysis is an in-depth and specific understanding of the needs of users, in the development of the system to do what this issue is completely consistent with the users' ideas; clear what the target system must do, determine what functions the target system must have.

In the software life cycle, the stage that can accurately determine "what the software system must do" is requirements analysis.

Tasks at all stages of the software lifecycle:

1. Problem definition

Determine what the problem is to solve (what). Through the interview and survey of the customer, the system analyst writes a brief written report on the nature of the problem, the project goal and the scale of the project, which should be confirmed by the customer after discussion and necessary modifications.

2. Feasibility study

Determine if there is a solution to the problem. The results of the feasibility study are an important basis for the client's decision on whether or not to proceed with the project. generally speaking, only those projects that may achieve greater benefits from investment are worth continuing.

3. Demand analysis

In-depth and specific understanding of the needs of users, in the development of the system to do this issue is completely consistent with the user's ideas. Identify what the target system must do and determine what functions the target system must have. The logical model of the system is usually represented by data flow diagrams, data dictionaries and brief algorithms. Use the specification to record the requirements for the target system.

4. Outline design (overall design)

Generally speaking, how to achieve the target system, design several possible schemes to achieve the target system, and design the architecture of the program, that is, to determine which modules the program consists of and the relationship between the modules.

5. Detailed design

To achieve the specific work of the system, write detailed specifications, programmers can write the actual program code according to them. Detailed design is also called module design. At this stage, each module will be designed in detail to determine the algorithm and data structure needed to achieve the module function.

6. Coding and unit testing (coding accounts for 10% and 20% of the total development effort)

7. Comprehensive testing (testing accounts for 40% of the total development workload, 50%)

8. Software maintenance

Through a variety of necessary maintenance activities to make the system to meet the needs of users for a long time. Mainly divided into corrective maintenance, adaptive maintenance, perfect maintenance, preventive maintenance.

Extended data

Software life cycle baseline

1. Functional baseline (functional baseline)

The functional baseline refers to the specification for the development system in the formally reviewed and approved system design specification at the end of the system analysis and software definition phase; or refers to the specification for the development software system as stipulated in the agreement or contract signed by both the project entrusting unit and the project contractor

Or the lower level applies for the specification of the development software system as stipulated in the project task statement approved by the superior or directly issued by the superior. The feature baseline is the initially approved feature configuration identity.

2. Assign baseline (allocated baseline)

The assignment baseline refers to the specification of the software requirements that have been formally reviewed and approved at the end of the software requirements analysis phase. The assignment baseline is the initially approved assignment configuration identity.

3. Product baseline (product baseline)

The product baseline refers to the specification of all configuration items of the developed software product after formal review and approval at the end of the software assembly and system testing phase. The product baseline is the initial approved product configuration identification.

Thank you for reading! This is the end of the article on "accurately determining what the software system must do" in the software life cycle. I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.