3 P and 1A (3)-Process in software development

The following is a summary of what we have done and the process.
I. Product Planning
Process:
1. Determine target customers and target markets.
2. Determine the products to be developed.
3. determine the development sequence
4. initially develop sales and pricing strategies
Results: Product Plan
2. Establish an architecture and assess whether the architecture meets the needs of the product line.
The architecture we created is named sea.
Process:
1. Create a logical operation View
2. Create a logical development view
3. Create a physical operation View
4. Create a Physical Development View
5. Develop the basic sea database.
5.1 pre-Research
It is mainly to learn new technologies and research special technologies.
Learning C #; Learning Web services; researching or/map; studying workflow engines; researching obfuscators; studying security measures;

Results: pspl pre-Research Report
5.2 Development
5.3 Test

Results: Sea architecture system
Basic SEA database;

3. Develop SPL
Process:
1. Pre-Research
Personnel: Business Group
Method: Collect and analyze existing similar products on the market.
Objective: To analyze the advantages and disadvantages of competing products.
Results: SPL pre-Research Report
2. Requirements
Personnel: Business Group
Method: Collect your own requirements as the main requirement, and pre-research results as the auxiliary requirement.
Objective: To determine the SPL business model and user view.
Results: SPL white paper
SPL business requirements manual
SPL form description
SPL User Manual
3. Design
Personnel: Design Team
Method: manual analysis and design.
Objective: To design a design model that meets the needs of the sea to facilitate conversion to the runtime environment file and automatic Code ;
Guidance Program The transaction design document developed by the developer.
Results: SPL General Design Manual
SPL Detailed Design Instruction
SPL design library;
4. Encoding
Personnel: encoding group
Method: Code the interface according to the form section in the form instruction manual and detailed design instruction manual;
Encode the business logic according to the transaction section in the detailed design manual;
Use tools such as vs for local coding, debugging, and unit testing;
Use SPL for encoding and submission.
Results: Unit Testing Services Source code ;
Unit test code;
Note:
Currently, encoding units are divided by package. The interface encoding and business logic encoding in the same package are completed by the same person.
You can consider dividing the Interface part into dedicated persons to ensure that the interface style is completely unified.
Or you can consider using tools.
5. Build
Personnel: Build Group
Method: Use SPL for building and publishing.
Results: SPL Installation Package
6. Test
Personnel: Test Group
Method: Install SPL for interface testing;
Perform regression tests (not done) on manually encoded transactions );
Result: SPL Installation Package B.
7. Trial
Personnel: User
Method: Trial Run
Result: the official version of the SPL installation package.
Note:
In SPL development, it is handed over to the SPL project team as its work platform.

Results: pspl/SPL;
Verify the sea architecture;
Verify pspl;

Note:
Basically, we adopt an iterative model based on the waterfall model. We first develop pspl1 and then use pspl1 to develop spl1,
Then use spl1 to develop spl2,..., Spl (n ). Obtain feedback on the one hand, and verify on the other hand.
This can be used as a template process for new product development.

At present, we have done this step, and the next step will be to develop in SPL in accordance with the Product Plan.