3 P and 1A in software development (II)-Relationship between 3 P and 1A in development management used in this development

As a virtual team, we primarily aim to study, because we do not consider survival issues, so we are allowed to experiment and try according to our ideal ideas.
We research development management, the main method is to identify the key points in development management, and study how to deal with these key points.
In recognition, we basically adopt the top-down approach.

Currently, the key points we have identified are architecture; product; process; project. Service is not considered for the moment.

3 P, 1A and Their Relationships:
1. Relationship: Under the unified architecture command, follow a certain process,
Produce the product by creating a project,
Maintain the product through multiple activities (project or other activities.
2. prodcut
The team will produce a large number of products. We can conduct comparative research from multiple aspects, Source code /Execution Code, baseline version/custom version ,...
Whether to extract the concept of product line is also to be studied.
3. Architecture
The common components abstracted from multiple products are organically linked to become the architecture.
You can also conduct comparative research from multiple aspects, such as technology/business, development/operation, logic/physics...
The architecture can be further divided into layers, which need further research.
4. Process
Process is the process of our activities. The common practice is to ensure the quality of the product and to effectively control the project through standardization.
Process can be represented in verbal, written, and tools. The key lies in the degree of execution.
5. Project
Here we define it as: Project;
To a certain extent, any activity is worth our close attention and supervision and becomes a project.
In development activities, R & D and engineering are the main activities. They share the commonality of projects. However, due to the introduction of new technologies/businesses, there are great differences,
This is worth studying.

Our research activities also fall into the scope of development management. This time we adopted the opposite process of the company, a process of supremacy.
Architecture-> benchmark product-> custom product.

the general process is as follows:
1. determine target customers and target markets
2. product Planning
3. establish an architecture and assess whether the architecture meets the needs of the product line.
4. Develop tools supporting architecture.
5. Develop the product according to the product plan.
during this period, the development of each product is managed as a project.
6. Sell the product and make it custom
7. Summarize and revise the standardized process throughout the process.
if there is no relevant standard process, a preliminary process is set, corrected in the process of doing the work, and summarized after the work is done.

advertisement:
1. welcome to try our new product, address:
http://msse.cnblogs.com/archive/2006/01/10/314523.html
2. welcome to join our team, address:
http://msse.cnblogs.com/archive/2006/01/10/314886.html
3. welcome to a survey we initiated, address:
http://msse.cnblogs.com/archive/2006/01/16/317835.html