"PM" Information system software development process

 Reprint Please specify the Source: Jiq ' s technical Blog
Software Development Life cycle

Iterative approach is recommended, that is, a detailed design-and-test iteration, the summary design phase extracts all the function points that need to be developed, which will be divided into 3-4 stages according to priority, each iteration phase will be detailed design, coding and testing, and then meet with the user to fix.

After all iterations are completed, the integration test, implementation, and the final maintenance phase are entered.

1 Demand Research and analysis

The final issue of the demand research report. Requirements research Steps at a glance:

Overall knowledge of outputs: Demand research Report, supplementary chapter I

Research plan development output: Demand research plan

Specific work Research output: Demand research report, complete complement, and confirm

Demand outcome review output: Requirements specification

Demand output input: requirements for input to requirements management tools

The first step: overall situation understanding

The goal is to have an overall understanding of the customer, the research content includes:

U system goals and the expectations of major leaders: the overall grasp of the system's positioning, the future will probably be made what to look like.

U already have the construction of the system : Look at what the system was made of before, why do customers want to do it again, where good can draw lessons from, which place is bad to avoid

U Department organizational structure and personnel role: know who to look for in the next step to understand the specific work.

the work items that are involved in each role: Learn about the scope of questions that you will need to ask about the next and specific person's business work.

In general, the organization chart is used to describe the role of organization and personnel, and the work contents of various roles are described in two-dimensional form, and the results are added to the demand research report. docx.

The overall situation is understood to take a number of ways:

1 to the Marketing department or product department to understand, access and read the relevant materials,

2 Call and communicate with users;

3 Project initiation meetings with the user;

If it is the best choice to communicate with users middle-level leadership, they tend to the front-line staff more understanding, but also about the intention of the above leadership, the positioning and expectations of the system. Clearly dividing the department or role, figuring out the work of each department or role, is to find the right person in the future needs survey, so that the future research work will be more effective.

The overall information is entered into the corresponding "demand research report." Docx, supplemental document Chapter I.

Step Two: Research plan development

After understanding the overall situation of the system, that is, the organization, user roles and other information, we need to develop a next in the user site will be carried out the demand research plan, see the "Demand research program." Docx, and the "Demand research report." The overall situation supplemented in red bold font shows up against out.

Send these two documents to the user and inform the user about the planned schedule of the upcoming field survey.

Step three: Specific work research

Step 1: Overall condition Confirmation

Prior to understanding the overall situation of the system, this time the main purpose of the user site is to input to the "Demand research report." The overall situation in the "docx" is further deepened and confirmed.

Step 2: Business Process Research

According to the previous research, has mastered the system involved in the role, as well as the main work of each role, followed by a variety of roles of the front-line staff to communicate the detailed work, to complement the "Demand research report." In the second and three or four chapters of docx. If there are multiple front-line staff for each type of role, as much as possible, the communication between the general and frontline staff needs to be repeated several times:

U First step: Start the communication, understand the process

Two ways to start:

Mode 1: If you have been clear in the previous step of the work involved, you can actively ask each, such as "How do you in the actual work of the purchase of products into storage?" ”

Mode 2: Do not clear the other party involved in the specific work content, you can collect the statements and documents they use, inquire about the use of reports and documents, in this way to start the exchange.

The first communication must be recorded on the paper, drawing the corresponding flowchart sketch, this method is more efficient.

Once you have an accurate understanding of the work involved in the process, it is important to suspend communication, the understanding of the process and processes involved in all documents, reports of the situation recorded, filled in the "Demand research report." The second chapter of the work item describes the "original process" and "document Report" two, and chapter III, recommended " The original process is described in words, separated by steps, and thinking about the initial questions that need to be asked and recorded in the question list.

Note: The relevant documents, reports as far as possible to one in hand, in the above Memo field input requirements, default values, unique constraints, optional range, document status and other details.

U Second Step: Process confirmation, start quiz

This will require the final confirmation of the process and document statements that were previously recorded.

Then question and answer the questions you want to know, and record them in the question list.

Ask the user what are the most desirable issues for the system to solve their work? What are the main concerns? Recorded in the "User concerns" item. Note that when asked the user most want to solve the problem, to see the nature of the problem, such as the user said "I want a steamed bread", "Why do you want a steamed bread?" "Because I am hungry", so how to fill the belly is the user's most core problem, we should ask more in this link why, mining users the most real idea.

U step three: Process optimization

So far the user's most primitive requirements have been largely documented, that is, helping users to comb their business processes is over, and the next step is to help users optimize their business processes and establish corresponding specifications.

Process optimization includes the following scenarios:

1 Combine the user's actual work flow with our system, propose a new business process;

More than 2 departments and role-like processes can be abstracted, and a unified specification is proposed;

Whether there are more than 3 departments and roles where the interface can be regulated or optimized through the system.

This process can be considered privately, and can also be discussed with the relevant users, and finally the optimized results recorded in the sixth chapter, through the use case diagram, activity diagram and with text to describe.

U Third step: Optimization result confirmation

The optimized results are confirmed by the relevant roles.

Step 4: Confirmation of demand research results

After the "Step 2" iteration for each department/role, it has been communicated with each of the front-line workers in each category of roles. The next thing to do is to be able to make basic decisions, but also understand the ideas and ideas of the upper echelons of the middle-level leadership and previously communicated with the front-line users to focus together, the original process, concerns, especially the optimization of the process of final revision confirmation, the leadership of the resolution and focus on the corresponding record. This requirement research report is complete, print out to leave a copy, if can sign the best, convenient after change management.

Output: "Demand research Report"

Fourth Step: Demand Results review

According to the Demand research report issued "demand specification", requirements specification according to different companies, different projects may not be the same, but the core ideas are similar, probably involves the following aspects of the content:

n operating environment, Context, constraints (duration, operating environment, technology, etc.)

n roles and their corresponding use cases

n Refinement of a single use case, including a detailed textual description of the use case, which can be used as an auxiliary description of the activity diagram

N-Class diagrams or e-r diagrams that describe system data objects and their relationships

n Test Cases (more abstract, focused on whether the requirements are met)

Note that before you write the requirements specification, you need to analyze the system roles, the general principle is to analyze the roles that are involved from the common operation scenarios, then list all the scenarios and the function permissions and data permissions of each role in the scenario, verify that the roles are properly divided, and then write the requirements specification. As the requirements specification is written, drawing use case diagrams and activity diagrams need to be taken as participants in the analyzed roles.

In fact, according to my experience, the requirements of the specification of a lot of content in fact in the requirements of the research phase has been completed, but may not be very focused on the form, such as system roles, use cases, operating environment, constraints, object entity relationships in the needs of the research phase has to be analyzed at the same time. Therefore, the requirements of the specification to a certain extent will be the preliminary requirements of research and analysis of the results reflected.

The final completion of the requirements specification requires the following steps:

1, the project manager according to the demand investigation report, carries out "The requirement specification" the preparation;

2, in the project team or even a larger scope of the review meeting, this step is critical, need the relevant research and development staff and project managers and other experienced role in the joint participation;

3, according to the review results to modify, and then issued to the user final confirmation.

The output is: specification of requirements.

Fifth step: Input of demand results

All requirements identified by the user have been included in the final formation of the demand Research report. docx, the next thing to do is to put these requirements into the requirements management tool for tracking management.

Here you can download my own written non-related requirements research documents:http://pan.baidu.com/s/1nq4cm

2 Overview Design

The outline design consists of four areas:

N Technical Architecture Design. Includes logical and physical architectures and detailed descriptions

n Function Module organization and division, give a functional module diagram or mind map (brain map)

n function point refinement, priority determination. The first phase of the function point should be as small as possible, covering the key business can be completed in the first phase of functional point after the development of the user immediately meet, so as not to create a greater deviation from the demand. We can assume that we are using iterative development to iterate over the functional points divided by this phase.

N Follow-up start-up planning, such as when the need to complete detailed design, preparation, the first phase of functional point development, the first phase of the output system and users meet and revise.

The output is: "Summary design Document".

3 Detailed design

Detailed design includes the following three aspects:

N detailed design of each function point

N Database Detail Design

n Navigation, data permissions detailed design

Output: "XXX function point detailed design", Database PDM file, "authority design".

4 encoding

5 Testing

Before the test is formally launched, the project owner will need to develop a controlled test plan based on the environment and personnel, such as who will be responsible for the test environment, who will refine or write the test case, who will perform the specific tests, and who will perform the system product work. Then the objectives of each of these tasks, the scope of the work involved, the division of the stage, time constraints, etc. must be stipulated well. Then assign a responsible person to each section, perform task assignments and progress control, and report the progress directly to the project owner.

Then request all System Module unit test pass, put forward the last source code submission period, prohibit the source code environment source submission permission, prohibit the test environment personnel outside the deployment of the test environment for the submission of permissions, the test environment and the outside world, the specific reasons can refer to another article.

After the test target is presented, the test task is assigned, and the test phase is divided, the system integration test can be started. It is possible to divide the integration test of information system into the following stages:

(1) System development Complete, develop the overall test plan (test target, test scope, personnel assignment)

(2) Deployment personnel to deploy the system to the test environment, the product of personnel assistance. For example, the database initialization script and so on needs to provide the product personnel, this stage first does not have the database, the service, the client and so on packaging.

(3) The requirements of the personnel to write test cases (reference to the original requirements research report and demand analysis report);

(4) The tester performs the first round of tests;

(5) First round test bug fix, regression test to bug fix complete.

(6) Write the test report and start the product packaging work.

(7) Testing of the product installation package.

(8) System installation documentation, user manual written.

(9) Final finalized version, System, documentation, source file.

6 implementation

7 Maintenance

After the completion of the system development, the most critical issue in the subsequent version iterations, code, and system maintenance process is versioning.

Author: Jiyichin, Welcome to Exchange

"PM" Information system software development process