Chapter 3: Software plans

 

The figure above shows the major items of the software plan. I will detail them one by one:

 

I. Problem definition: 1. Definition content: Problem background, development system status quo, development conditions and reasons, overall requirements, problem nature, type conversion, goal, development conditions, environment requirements, etc.; 2. defined steps: the system analyst needs to go to the problem site; 1. Listen to the user's requirements on the system; 2. Investigate the reasons for development background; 3, view the user's report; 4. Process and organize; 5. Discuss with the User Manager repeatedly; 6. Make improvements incorrect; 7. Write the report documents that both parties are satisfied with. 8, determine whether the parties can conduct in-depth research on system feasibility.

Let me take a simple example!

 

 

 

Ii. Feasibility Study: 1. five aspects: economic feasibility, technical feasibility, operational feasibility, Legal feasibility, and time feasibility; 2. Approach: identify the problems to be studied, conduct market research, analysis preparation, environment analysis, physical analysis, function analysis, information analysis, dynamic analysis, establish system solutions, make various estimates, and conduct model reviews. 3. steps: 1. Review the system scale and objectives; 2. Study the currently used system; 3. Export the high-level logic model of the new system; 4. Recommend methods to users; 5. Recommend the action policy and make a key decision. 6. Draft a development plan and write a feasibility study report. 7. submit the report to the superior and expert for review.
All in all, the purpose of the feasibility study is to check whether the system software meets the development conditions and whether it is worth developing.

 

Iii. Content of the software plan: 1. Scope: software function scale, Software Capability Requirements for hardware, interface nature and complexity; 2. Environment Resources: 1, human resources requirements for different personnel at different stages; 2. hardware, including target machines and other machines; 3. software, including supporting software and utility software; 4. Development of schedules, including the delivery date, how to organize the distribution of power; 5. Software costs, as long as both parties accept.

 

4. Software price estimation: software productivity is the foundation of software prices. Factors that affect software prices include: 1. Human resources, product factors, engineering factors, and resource factors. We can 1. Estimate the price based on these factors; 2. estimate the number of code lines; 3. estimate the number of small tasks by decomposing the tasks and accumulating them; these price estimation methods all have a necessary condition, that is, we need to have a wealth of experience to do the foundation, so that the estimation will be more accurate!

 

5. Cost/benefit analysis: this project can be implemented only from the economic perspective. Therefore, benefit analysis is very important. Cost Estimation, you can use either top-down or bottom-up methods to estimate the cost of a software throughout its lifecycle. Benefit refers to the cumulative difference within the entire life cycle! All in all, we need to analyze the cost and benefit well, which involves the interests of many people.

 

6. Software plan report: Here I will give you an outline of the general content. Of course, you can delete the content based on the actual situation. All in all, the report is to organize our work at this stage to facilitate leadership review. Of course, this is also an important document in the entire software engineering cycle. We need to write it well!

 

 

 

 

 

The software plan is to solve the problem of whether the software can be put into design for various research and analysis, through the study of many aspects, to ensure the implementation of software projects, so that we can enter, analysis and Research on system software.

 

Finally, let me give you an easy-to-understand example to illustrate this: in fact, just like building a house somewhere, the task of software planning is, it seems uncomfortable to build the house. Of course, this includes location, employees, resources, and economics. Simply put, it is the decision analysis before building a house!