Software Project Plan

Software Project Plan

A software project planning is the start-up phase of a software project, which includes: determine the detailed project implementation scope, define the submitted work results, evaluate the main risks in the implementation process, develop the project implementation time plan, cost and budget plan, and human resources plan.

Problem definition:

The problem is defined as the basis for software requirement analysis functions and performance.

1. Definition content

Including: Problem background, development system status, development conditions and reasons, general requirements: nature of the problem, type conversion, what goals, development conditions, environment requirements, etc.

2. Steps defined

System Analyst to problem site

Listen to users' requirements on the System

Investigate development background

View user reports

Process and organize

Repeated discussions with users and owners

Incorrect improvements

Write the problem definition report documents that both parties are satisfied

Feasibility study:

It is necessary to describe the feasibility of the project before system development, which is generally discussed in the following five aspects.

Economic Feasibility

Technical feasibility

Operational feasibility

Legal feasibility

Time feasibility

Feasibility study steps:

Review system scale and objectives

Study the systems currently in use

Export the high-level logic model of the new system

Recommended Methods

Recommend action guidelines and make a key German decision

Draft a development plan and write a feasibility study report

Submit for on-board and expert review

Content of the software plan:

The software plan is described by administrators and technicians immediately in terms:

Software scope:

Content: Software functional modules, hardware requirements for software capabilities, interface nature and complexity

Environment Resources:

Human resources: requirements for different personnel at different stages

Hardware: including the target machine and other machines

Software: including supporting software and Utility Software

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

Software Cost: as long as both parties can accept

Resource performance description: What kind of people are required, what kind of functional performance hardware and software

Software price estimates

Software productivity is the basis of software prices. The factors that affect software prices include population, product, engineering, and resource.

The estimation of software cost is the estimation of the cost of the whole process of software project development. Now there are some available models:

1. parameterization algorithm: c = f (VI)

C is the software Price

VI is an independent parameter that affects the software Price.

2. code line (LOC) Price Estimation Technology

Related Parameters: source code line, which is the measurement unit of software products, excluding comments and job commands

Labor volume: the length of labor time for one person to join

Software productivity: Number of software completed per unit labor time

Loc calculation method: first, the function of the designed system is decomposed. Then, the LOC price of each software function block is selected based on historical data and experience.

3. Task Decomposition Method

Idea: first, the software development project is divided into several relatively independent tasks, then the cost of each development task is estimated separately, and the total cost is accumulated.

4. Automatic Cost Estimation Method

Reducing human labor, but having a large amount of experience data as the foundation and good Database System Support

 

Cost/benefit analysis

Purpose of benefit analysis:

From an economic perspective, it is cost-effective to develop a new system, so that leaders can decide whether to develop a new system.

1. Cost Estimation

It is used to estimate the development cost and the benefits of the new system.

Top-down evaluation: First estimate the system and then estimate the subsystem

Bottom-up evaluation: First estimate the overall cost of merging each module in the system

2. Cost/benefit analysis

Operation fee: Depends on the system operation fee and maintenance fee

Economic benefits of the system: the new system increases revenue + the operation fee saved by the new system; the system economic benefits generally exist throughout the entire life cycle.

Software Development Plan

1. Introduction

1.1 writing purpose [clarify the purpose of writing a development plan and specify the target audience]

1.2 Project Background [A. Relationship between the project entrusting organization, development organization and competent department B and the software system and other systems]

1.3 Definition [list the definitions of specialized terms used in this document and the original acronyms]

1.4 references [. approved plans and tasks, contracts or approvals from higher authorities; B. the materials and specifications referenced in the document. The author, title, number, publication date, publisher, or data source of the materials are listed]

2. Project Overview

2.1 work content

[Briefly describe the main work of the project, and introduce the functions and performance of software development. If no feasibility study report is prepared, a detailed introduction should be provided in this section]

2.2 conditions and restrictions

[Clarify the conditions that should be met for the completion of the project, the conditions that the development organization has met, and the conditions that need to be created. When necessary, it shall also describe the work undertaken by users and subcontractors, the deadline for completion, and other conditions and restrictions]

 

2.3 Products

Program

[List the names, languages, and storage formats of the programs to be delivered .]

Document

[List documents to be delivered]

2.4 Runtime Environment

[Including hardware and software environments]

2.5 Service

[Clarify the services that a development organization can provide to users. Such as personnel training. Installation, warranty, maintenance, and other operation support]

2.6 Acceptance Criteria

 

For more information, see:

Software Program: http://baike.baidu.com/view/2235776.htm

Software Project plan format: http://hi.baidu.com/spiritlzp/blog/item/eaddab625c2d70d8e7113a5a.html