Software Project Development position settings

Position: Project Manager

 

Main responsibilities:

1. Plan:

A) confirm the project scope, project quality, project time, and project cost.

B) Standardize and standardize project processes/activities.

C) conduct the overall planning and phase planning of the project based on the comprehensive factors of the project scope, quality, time and cost. (Demand analysis plan and plan...)

D) various plans are recognized by superior leaders, clients, and project team members.

2. Organization:

A) organize various resources required by the project.

B) set various roles in the project team and assign their responsibilities and permissions.

C) customize the communication plans inside and outside the project team. (If necessary, you can write the project communication plan in the project planning directory according to the configuration management requirements.)

D. Arrange communication and communication between the Group's demand analysts, customer contacts, and other roles with the customer.

E) process the relationship between the project team and other stakeholders.

F) process the relationships between roles in the project team and members in the project team.

G) Arrange customer training.

3. Leaders:

A) Ensure that the project team's objectives are clear and understandable.

B) create a development environment and atmosphere for the project team, and ensure that the project team members are not affected by other aspects of the project within the project scope.

C) improve the morale of the project team and enhance the cohesion of the project team.

D) Reasonably arrange the work of all members of the project team so that the work of all members can reach a certain level of fullness.

E) develop plans for recruiting or training personnel required by the project team.

F) regularly organizes project team members to conduct technical training and project-related industry training.

G) promptly discover problems in the project team.

H) handle issues in the project team in a timely manner.

4. Control

A) Ensure that the project meets the project objectives according to the specified quality and progress within the scope of budget and cost.

B) follow up and check the quality of work of the project team members at all stages of the project life cycle;

C) report the project progress and difficulties in the project development process to the leaders on a regular basis.

D) configure, manage, and plan the project.

E) control the progress of each member of the project team, understand the working conditions of the members of the project team, and quickly solve the difficulties encountered by the members of the project team.

F) Organize project team members from time to conduct short-term activities outside of the project to cultivate team spirit.

Conclusion:

The project manager is the person in the project team who makes the final decision on all important non-technical matters throughout the project development process.

Position: System Architect (Technical Director)

Main functions and responsibilities:

1. The System Architect is the overall designer of the software project and the creator of the new product development and integration and new technology system of the software organization.

2. The System Architect is a technical person who makes decisions on all important things. (System Architects play an important role in the entire software development process, and their responsibilities or concerns keep changing as the development process progresses .)

3. In the demand phase, the software architect is responsible for understanding and managing non-functional system requirements, such as Software maintainability, performance, reusability, reliability, effectiveness, and testability. Reviews the requirements raised by customers and market personnel, confirms the design proposed by the development team, and organizes the definition of development team members and development processes; assists the demand analyst in completing the user demand manual and demand change manual.

4. In the design phase, the architect is responsible for designing the entire software architecture, key components, and interfaces. Assists system analysts in completing the system summary Design Manual

5. In the coding stage, the architect becomes a consultant for programmers and regularly holds technical seminars and technical training courses;

6. In the testing and implementation phase, as the software starts testing, integration and delivery, integration and testing support will become the focus of the software architect;

Conclusion:

The System Architect can also be understood as the technical director. The System Architect is the person who makes decisions on all important technical matters in all software projects within the Department.

Position: Demand Analyst

Main responsibilities:

1. Conduct customer demand survey according to the demand survey plan in the early stage of the project.

2. Collect and sort out customer requirements and write the user requirements manual.

3. On behalf of the project team and the user, communicate all matters related to the project requirements.

4. communicate all matters related to project requirements on behalf of the customer and the project team members.

5. Be responsible for the approval and signature of the user requirement manual.

6. demonstrates the completed project module to the customer and collects opinions on the completed module.

7. Complete the requirement change statement and obtain the user's approval and signature.

8. Assists System Architects and system analysts in understanding requirements.

Conclusion:

The demand analyst is the person who has the most dealings with the customer in the early stage of the project. For the customer, he can represent the entire project team. For the project team member, his opinion can represent the customer's opinion, all matters related to customer requirements within the project team must be recognized by him.

Position: System Analyst

Main responsibilities:

1. Assists demand analysts in demand research.

2. Analyze and parse the user requirement specification, and organize system requirements into the software requirement specification;

3. resolves issues found after the software requirement specification is reviewed;

4. Before analyzing the system, explain the content of the Software Requirement Specification to the architecture designer.

5. Assists the architect in architectural design and completes the system architecture specification.

6. model the system according to the system architecture specification;

7. After system analysis and modeling are completed, the modeling results are converted into system outline design.

8. Assists database designers in database logic design and physical design in accordance with the system summary Design Manual, completes the database CDM and PDM diagram, and completes the database design manual.

9. Assist the software designer in carrying out the detailed system design statement in accordance with the system summary Design Manual.

10. Instruct the software engineer to implement the Code in accordance with the detailed system design manual.

11. Responsible for checking key code;

12. Assists the project manager in configuration management and provides optimization and improvement suggestions;

13. Conduct regular technical training for project team members.

Conclusion:

The system analyst is the Chief Executive Officer of the project team. He is involved in all aspects of the project, the promoter of the project progress, and the key to project success.

Position: Database Designer

Main responsibilities:

1. perform database modeling with System Architects and system analysts in accordance with the system architecture specification.

2. Draw the CDM and PDM diagrams of the database based on the database modeling results.

3. Create a database based on the database PDM diagram.

4. Maintain, back up, recover, and synchronize databases.

5. Import and export customer data.

6. initialize the database.

7. Assist the software designer in completing the database-related part in the detailed system design manual.

8. Compile the corresponding views, stored procedures, functions, and triggers according to the detailed system design manual.

9. Provide SQL guidance to other members of the project team.

10. Regularly train other members of the project team on database knowledge.

11. Create test data for test managers and test engineers.

Conclusion:

The Database Designer, also known as dBA, is the only person in the project team who can perform direct operations on the database. The person who makes the final decision on all important matters related to the database in the project.

Position: Software Designer (module)

1. According to the system summary Design Manual, compile the module detailed manual.

2. The software engineer is responsible for explaining the system detailed design instruction.

3. Assist the software engineer in implementing the Code in accordance with the detailed system design manual.

4. Control the development progress of this module.

Conclusion:

The software designer, also known as the module designer, assists the system analyst in the detailed design of the module and directly controls the progress of the module. The software designer makes the final decision on all the important things in the module.

Position: Software Engineer

Main responsibilities:

1. Implement the code according to the detailed system design manual;

2. Review your code and perform a simple test;

Conclusion:

The software engineer is a member of the final implementation code.

Position: test Manager

Main responsibilities:

1. Write test plans independently;

2. Write test cases independently;

3. Coordinate the internal work of the test team and work with the development team;

4. Complete the "test execution;

5. Master in-depth testing methods, testing technologies and complicated business processes;

6. Researches, promotes, and maintains testing tools, and maintains testing databases;

7. prepares the user manual, Operation Manual, and relevant training materials;

8. reviews the quality of the project.

Conclusion:

The test Manager should be the person most concerned about the quality of the project. His main task is to find the unreasonable and unqualified part of the project, other project members are required to complete the project based on the quality of the given project.

Position: Test Engineer

Main responsibilities:

1. Write test cases under the arrangement and guidance of the test Manager;

2. Complete "test execution" under the arrangement and guidance of the test Manager;

3. test according to the test plan under the guidance of the test Manager;

4. perform tests based on test cases.

5. Audits the quality of assigned projects.

6. Understand the basic process of the project and be able to perform operations in various processes of the project.

Conclusion:

The test engineer is a member of the final project test to ensure the quality of the project.

Position: Implementation Manager

Main responsibilities:

1. formulates the project implementation plan;

2. coordinate resources of the project team and complete system implementation (including system installation, user training, system launch, and system trial run) under the constraints of the project implementation plan );

3. Follow up and check the quality of work of implementers during the project implementation phase;

5. assists users in "user validation test" and prepares the validation test report.

Position: Implementation Engineer

Main responsibilities:

1. execute the project user's on-site implementation tasks under the arrangement and guidance of the implementation manager;

2. Participate in the compilation of user manual and operation manual and relevant training materials;

3. participate in "user validation test" and prepare the validation test report.

Position: Art Engineer

Main responsibilities:

1. complete functional interface design arranged by the software designer.

2. allocates the overall color of the project.

3. propose project beautification suggestions to system analysts.

4. Provides one or more sets of CSS style sheets and HTML structure tables for BS projects.

5. provide static and dynamic images that match the project content for the CS project.

6. Provide interface guidance for software designers.

★Position: Account Manager (when a developed project is a customized project, it can be set up by the Project Manager or department manager)

Main responsibilities:

1. Plan and independently complete visits and communications between target customers;

2. Analyze and sort out customer requirements on a regular basis, and formulate targeted solutions;

3. Maintain relationships among key customers, understand and sort out the needs of key customers, and provide valuable market information for developing products that better meet user needs;

4. participate in product positioning discussions and offer suggestions for product planning.

★Position: Product Manager (the product manager can be a member of the marketing department when the project to be developed is a product project)

Main responsibilities:

1. Plan and manage the products in charge;

2. conduct market research and analysis on the products in charge, and promptly propose countermeasures;

3. Internally manages product implementation to ensure smooth implementation of product functions and to meet market demands;

4. publicize and promote the products, explore the market, and improve the product brand awareness and recognition;

5. Work with sales personnel to develop product sales strategies and support marketing.

Software Project Development position settings