Software Development Proposal Template

Software development proposal

Project Name:

Participating persons:

Directory

1 Introduction---------------------------------------------------------------------------------3-

1.1 Purpose of preparation---------------------------------------------------------------------3-

1.2 Background--------------------------------------------------------------------------3-

1.3 Definition--------------------------------------------------------------------------3-

1.4 References---------------------------------------------------------------------4-

1.5 System Motivation--------------------------------------------------------------------4-

1.6 WBS for writing documents------------------------------------------------------------4-

2 Project Overview----------------------------------------------------------------------------5-

2.1 Job Content---------------------------------------------------------------------5-

2.2 Main participants----------------------------------------------------------------5-

2.3 Products and Results------------------------------------------------------------------6-

2.3.1 Program--------------------------------------------------------------------6-

2.3.2 File--------------------------------------------------------------------7-

2.3.3 Service--------------------------------------------------------------------7-

2.3.4 non-hand-over products------------------------------------------------------------7-

2.4 Acceptance Criteria--------------------------------------------------------------------8-

Acceptance of 2.4.1 Code------------------------------------------------------------8-

2.4.2 Document Acceptance--------------------------------------------------------------8-

2.4.3 Service Acceptance--------------------------------------------------------------8-

2.5 deadline for completion of the project-------------------------------------------------------8-

2.6 Reviewers and approvers of the plan--------------------------------------------------8-

3 Implementation Master Plan-------------------------------------------------------------------------9-

3.1 Development Process---------------------------------------------------------------------9-

3.1.1 Demand Analysis------------------------------------------------------------10-

3.1.2 System Design------------------------------------------------------------10-

3.1.3 Coding and testing phase----------------------------------------------------10-

3.1.4 documentation, product deployment----------------------------------------------------10-

3.1.5 Project Summary------------------------------------------------------------10-

3.2 Decomposition of work tasks-------------------------------------------------------------9-

3.3 Interface Personnel--------------------------------------------------------------------10-

3.4 Progress-------------------------------------------------------------------------10-

3.5 Budget-------------------------------------------------------------------------11-

3.6 Key issues--------------------------------------------------------------------11-

4 Support Conditions--------------------------------------------------------------------------11-

4.1 Computer system Support------------------------------------------------------------11-

4.2 Jobs required of users------------------------------------------------------12-

4.3 Conditions to be provided by an external unit----------------------------------------------------12-

5 Thematic plan Highlights---------------------------------------------------------------------12-

5.1 Developer Communication Plan--------------------------------------------------------12-

5.2 Test Plan------------------------------------------------------------------12-

5.3 Quality Assurance Program-------------------------------------------------------------12-

5.4 Personnel configuration Plan-------------------------------------------------------------12-

6 Appendices

Feasibility Analysis Report

Demand Analysis proposal

Database design

Overview design

Detailed design

1 Introduction 1.1 Purpose of writing

In order to ensure the project team to complete the project objectives on time and quality, it is easy for the project team members to better understand the project situation, so that the process of the project is carried out in a reasonable and orderly manner, it is necessary to document the scope of the work within the project life cycle, the task breakdown of the work, the project team organizational structure, The responsibilities of each team member, communication and collaboration within and outside the team, development progress, internal and external environmental conditions, risk countermeasures, etc. are described in writing, as a consensus and agreement between project team members and project stakeholders, the basis of action for all project activities within the project life cycle, The project team conducts and examines the basis of the project work.

The project development plan is used to guide the project product that the data analysis System project is carried out smoothly and is finally approved. The project development program is intended for all members of the project team.

1.2 Background

Data analysis system is a statistical product and service solution software, the main functions of data entry, collation, analysis, mathematical calculation and other functions. is a similar to the SPSS Software Web version, the project period of 3 months, project background planning as shown in Table 1.1.

Table 1.1 Project Background planning

Project name	Project Entrusting Unit	Task-Presenting person
	No	Mr. Ho

1.3 Definitions

Special terms:

Oracle: The database relational system used by the system server.

SQL: A language for accessing the query database

Transaction flow: There may be multiple paths for processing after data enters the module.

Primary key: A key field in a database table. Values differ.

External PRIMARY key: The domain in the database table that is associated with the other table's primary key.

ROLLBACK: The error recovery mechanism of the database.

Abbreviation:

System: If not specifically stated, the system refers to the data analysis systems.

sql:structured Query Language (Structured Query language).

Atm:asynchronous Transfer mode (Asynchronous transfer modes).

UML: A unified Modeling language, a standard modeling language used to design software blueprints, is a standardized modeling language from software analysis and design to programming specifications.

1.4 References

The document format request according to our country gb/t8567-1988 national standards and the IEEE/ANSI830-1993 Standard specification request carries on. Include the following files:

• SPSS Baidu Encyclopedia
• Specification for writing Software Requirement specification

Books include:

• "Software project Management" Zhu Shaomin, Han Ying, People's post and telecommunications press.
• "SPSS is very simple" Ronald · D., Professor at the University of California, USA.
• "Data analysis based on SPSS" by Shirwey, published by Renmin University Press in 2006

1.5 System motives

The system is a statistical analysis software, and mathematics is a complex subject, it has to deal with a great amount of information, the operation is cumbersome. Many calculations must require professional software, students in the use of the cumbersome installation to use, the system can facilitate the vast number of students, direct use.

2 Project Overview

With the development of science and technology, people increasingly rely on computers, while data processing is also popular, the web version of the data analysis system came into being, processing mainly includes descriptive statistics, mean comparison, general linear model, correlation analysis, regression analysis, logarithmic linear model, clustering, data simplification, survival analysis, Time series analysis, multiple responses, and several other categories.

The data analysis system adopts the current popular B/S model, myeclipse as the development tool, the background database management system for Oracle, the system operating platform for Windows7. This data analysis system mainly implements the following functions:

The system does not require authentication and can be used directly.

Users can perform mathematical calculations and statistics as needed.

Users can import, export, and so on the data on the page.

Users can register their account and change their password.

Users can log in to upload data.

Project development time: 90 days

Development tools: MyEclipse2013

2.1 Job Description

1, make and revise the project development plan;

2, to carry out planning tracking and monitoring;

3, with the SQA quality assurance work;

4, work products in a timely manner controlled management;

5, according to the plan to draw the stage review;

6, submit the test Department to evaluate the development of products;

7. Delivery of final work products.

8. Summary of project implementation

9. Project Acceptance

2.2 Main participants

In order to complete the project development of the data analysis system, a project team was formed, consisting of the group leader and crew members, as shown in 2.1.

Table 2.1 Division of Personnel

 

TD width= ">

name	role	job description
 	leader	responsible for planning, assigning tasks, implementing decisions
 	crew
	crew	responsible for collecting material
crew	responsible for collecting material

2.3 Products and Results 2.3.1 procedure

Software Name: Data analysis System

Programming Language: Java

Function: Data analysis system is a web system based on SPSS software, which consists of data analysis, data statistics, personal management and other modules.

2.3.2 File

• User manual: This manual describes the software's functionality, performance, and user interface in detail, giving the user a specific understanding of how to use the software, and providing the operator with knowledge of the various operating conditions of the software, particularly the details of the operating methods.
• Software Maintenance Manual: mainly includes software system description, program module description, operating environment, support software Description, maintenance process description, easy to maintain the software.

2.3.3 Service

The program provides the following services:

Training: Users are trained to use the software correctly.

Consulting: Users can ask questions and get answers to the technician during working hours.

Maintenance: Get problems with software use and provide patches.

2.3.4 Non-handover products

• Feasibility Analysis Report: To illustrate the feasibility of the implementation of the Software development project in technical, economic and social factors, and to explain and justify the selected embodiments in order to reasonably meet the various possible implementation options for the development objectives.
• Project development plan: to develop a specific plan for the implementation of the software project, which should include the responsible personnel of each part, the progress of development, the budget of development funds, the required hardware and software resources, etc.
• Software Requirements Specification (software specification): The development of software features, performance, user interface and operating environment, etc. to make a detailed description. The specification should give the data logic and the requirements of the collection, in order to generate and maintain the system data files ready.
• Summary Design Specification: This manual is a summary of the actual stage of the work, it should explain the function allocation, module division, the overall structure of the program, input and output and interface design, operation design, data structure design and error processing design, to provide a basis for detailed design.
• Detailed design specification: emphatically describes how each module is implemented, including the implementation of algorithms, logic flow and so on.
• Test plan: In order to do the integration test and acceptance test, we need to develop an implementation plan for how to organize the test. The plan should include the content of the test, progress, conditions, personnel, the selection of test cases, the allowable deviation range of the test results, etc.
• Test Analysis Report: After the completion of the test work, the test plan should be submitted a description of the implementation of the test results are analyzed, and put forward the test concluding comments.
• SOURCE program: All the code and comments in the software development process.

Acceptance of 2.4 acceptance standard 2.4.1 Code

Finally, in-group review before delivery, consistent with document description, code writing style unified, using standard specification, no following errors: Due to software defects caused by loss of data, not meet the design requirements, response time is too long unacceptable problems.

2.4.2 Document Acceptance

Finally, before the delivery of the customer in the group review, the document format conforms to the HB6465 standard, the function conforms to, the document clear easy to read, does not have the faulty wordings and the ambiguity.

2.4.3 Service Acceptance

Service hardware to meet the requirements of the document description, has the corresponding function, personnel technical assessment qualified.

2.5 deadline for completion of project

Delivery date

From April 15, 2015 to July 15, 2015, complete the entire system Feasibility report analysis, requirements analysis, development plan description, System design book, Project test, project summary, conceptual model, storage mode, integrity control, access rights, etc. are defined, The module of the system function is designed in detail, and the general structure of the database, the code naming specification are defined and completed. The delivery date is July 15, 2015.

2.6 Reviewer and approver of the program

Why do the examiners, the teachers, and the people who approve them?

3 decomposition of the implementation master plan 3.1 work tasks

Job description	Head	Participating personnel
Feasibility analysis of the project (Project Feasibility analysis Report)
Project Development Report (report)
Requirements Analysis (Requirement Analysis specification)		All personnel
Overview design (outline design and instructions)		All personnel
Detailed design (detailed design instructions)		All personnel
Database setup		All personnel
Interface design
User operation manual (report)		All personnel
Use Visio to draw graphs such as flow diagrams, e-r diagrams, etc.		All personnel
Software Installation, testing
User training
Post-Maintenance

3.2 Development process 3.2.1 Requirements Analysis

Requirement analysis is an important part of the whole design, when the feasibility analysis is completed, the project is set up, the development role has been determined, from April 20 to April 28, the relevant design and development staff and related business personnel to the business process, management method analysis, and data collection, collation. After the completion of the collection, induction and analysis of the relevant data information, the user needs are determined, the functions that the software must complete are defined, the data definition is completed, and the data dictionary is established.

3.2.2 Overview Design

From April 28 to May 15, complete the analysis of the whole system design, the concept model, storage mode, integrity control, access rights, etc. are defined,

3.2.3 Detailed Design

The module of system function is designed in detail, and the general structure of database and code naming specification are defined.

3.2.4 Coding and testing phase

From May 16 to May 30, completed the program design and system testing, completed the establishment of the database and the compilation and commissioning of the program. In order to avoid the accumulation of errors, using the basic mode of edge development side test, each module is assigned a special person to test, system and system test, the system processing logic, exception handling ability, fault tolerance and other large-scale testing, the problem of the discovery of a thorough correction.

3.2.5 Project Summary

After the completion of the project with a week or so time, the project development, deployment and other development process issues, lessons learned summary record, in order to facilitate the accumulation of project experience and shorten the development.

3.3 Interface Personnel

Responsible for the project with the user interface personnel for the Zheng Zehui, by the software to send a special person, according to customer requirements, designated location installation, commissioning, operation and to customer demonstrations, in the later responsible for maintenance and update.

3.4 Progress

Methods: Using structured development

Set module Development priority: Through the analysis of the characteristics of data processing and information flow, to determine the sequence of development of each module.

The specific development schedule is as follows:

Note: There are four milestones, namely when the requirement is complete, when the detailed design is complete, when the system code is complete, and when the whole project is completed.

Table 3.2 Milestone Events

Milestone name	Product Name	Date submitted	Responsible person
Feasibility	Feasibility Analysis Manual
End of Demand interview	Requirements Analysis Manual
End of system analysis	System Analysis Manual
End of system design	Database Design Manual
End of Project	Project Summary

3.5 Budget

No

3.6 Key Issues

Table 3.6 Project Risk Factors

/thead>

risk sequencing	risk entry name	risk description	risk mitigation Plan
1	Professional Fundamentals not secure	This project development process involved in a lot of knowledge, to the project developers to bring some difficulties	for corresponding learning
2	inexperienced	member development experience is not enough to ensure project quality is difficult	Only through constant practice
3	Effects of software performance	Some software may be prone to freezing during this development	Select the appropriate software, Build a good Configuration development environment

The main issues affecting the completion of the plan are:

• Unclear user needs, misunderstanding and ambiguity
• First time software development, developers have no practical experience
• Time is limited and there is not enough development time

4 Support Conditions 4.1 computer system support

Support conditions required for development:

• Hardware: Win7 System

Server: Tomcat7.0 Server

LAN using the TCP/IP protocol

• Software:

Operating system is WINDOW7, using integrated development tools MYECLIPSE2013, database with Oracle, project operating environment is JDK7.0.

Other development tools include: Dreamweaver, Plsql, TomCat7.0 CVSNT2.5.03

4.2 User-borne work required

No

4.3 Conditions to be provided by external units

This system is independent development, does not need outside the unit to provide the condition.

5 Thematic Plan Essentials 5.1 developer Communication Plan

From April 18, 2015 onwards, to April 28, 2015, a week, the morning of the Software Engineering project development of the content of the communication; PM development design.

Content: Clear Responsibilities

5.2 Test Plan

June 22, 2015-July 1, 2015 the software testing work;

5.3 Quality Assurance Program

In strict accordance with the various steps in the project development process, from project establishment, feasibility study report, demand analysis report, project development plan, etc., concrete implementation;

5.4 Staffing Plan

The project development team a total of 4 people: Team Leader:

Crew:

Software Development Proposal Template