Software project development process and key points

graph LR
A[需求分析] --> B[系统设计]
B --> C[编码开发]
C --> D[测试验证]
D --> E[部署上线]
E --> F[运维支持]

In the project development process, the first step is to conduct a needs analysis to clarify the project goals and functional requirements. Next is system design, formulating the overall architecture and specific implementation plan of the project. Then carry out coding development and implement coding according to the design plan. After completing the coding, conduct testing and verification to ensure that the functionality and quality of the project meet the requirements. After passing the test, deploy and go online and put the project into use. Finally, there is operation and maintenance support, which provides real-time monitoring and maintenance of the project to ensure the stable operation of the project.

Requirements analysis: At this stage, it is necessary to have an in-depth understanding of the business requirements, communicate and discuss with stakeholders, and clarify the goals and functional requirements of the project.

System design: Based on the requirements analysis stage, formulate the overall structure and specific implementation plan of the project. Modular design, good architecture design, database design, interface design, security design, etc. are required.

Coding development: Coding implementation according to the design plan. It is necessary to follow coding standards, modular design, code reuse, error handling, input validation, memory management, asynchronous programming, debugging and logging, etc.

Test verification: Conduct software testing to ensure that the function and quality of the project meet the requirements. Including test strategy formulation, test case design, execution of tests, error handling, etc.

Deploy and go online: Put the project into use. Automated deployment, environment isolation, security, monitoring and logging, rollback planning, comprehensive testing, etc. are required.

Operation and maintenance support: Real-time monitoring and maintenance of the project to ensure the stable operation of the project. Including monitoring and alerting, fault handling, security and vulnerability management, backup and recovery, performance optimization, change management, and more.

1. When conducting demand analysis, you need to pay attention to the following points:

Deep understanding of the business: Understand the specific needs of the business, including business processes, goals, issues and challenges, as well as user expectations and pain points. Communicate and discuss with relevant stakeholders to ensure a comprehensive understanding of the business.
Define clear goals: Clarify the goals and scope of the project, including requirements for functionality, performance, security, etc. Refine requirements and transform high-level requirements into actionable specific requirements.
Feasibility assessment: Conduct a feasibility assessment of the requirements and analyze whether the requirements can be realized with existing technology and resources. Evaluate the feasibility and implementability of the project, taking into account the project's time, resource and cost constraints.
Refined requirements: Refine the requirements and clarify the detailed requirements for each requirement in terms of function, performance, user interface, data requirements, etc. Ensure all requirements are accurately understood and implemented.
Determine priorities and lead times: Prioritize requirements, determine which requirements are most important, and schedule their lead times. Taking into account resource and time constraints, ensure that limited resources are used on the most valuable needs.
Communicate with stakeholders: Maintain close communication and cooperation with project stakeholders to ensure understanding and consensus of requirements. Process and respond to their feedback and change requests in a timely manner, ensuring that the needs of the project are aligned with stakeholder expectations.
Continuous iteration and improvement: Requirements analysis is an iterative process that is conducted at different stages and levels of the project. As the project progresses and requirements change, make timely adjustments and improvements to maintain the accuracy and adaptability of requirements.

All in all, requirements analysis is the basis for project success. It requires an accurate understanding of business requirements, reasonable planning and refinement, and close cooperation with stakeholders to ensure that project requirements are consistent with user expectations.

2. When designing the system, you need to pay attention to the following points:

Clarify system goals: The first task of system design is to clarify the goals of the system and the problems to be solved. Carefully research and analyze requirements to ensure a full understanding and grasp of business requirements to ensure that the system can meet user expectations and needs.
Modular design: Split the system into independent modules, each module is responsible for specific functions or tasks. Through modular design, the complexity of the system can be reduced, making the system easier to understand, maintain and expand.
Good architectural design: Choose appropriate architectural patterns, such as client-server architecture, distributed architecture, etc., to support the scalability, maintainability and performance requirements of the system. At the same time, ensure that the system's architectural design can meet the system's reliability, security and availability requirements.
Database design: Reasonably design the database structure, including table design, field definition and relationship establishment. Consider the consistency and integrity of the data, as well as the efficiency and performance requirements of the system's read and write operations on the data.
Interface design: Design the interfaces and protocols between systems to ensure the accuracy and reliability of data transmission and communication between systems. At the same time, consider the ease of use and compatibility of the interface to facilitate integration and interaction with other systems.
Security design: Security should be considered in system design, including data security and system security. Take appropriate security measures, such as authentication, permission control, data encryption, etc., to protect the system from security threats.
Performance considerations: In system design, the performance requirements and constraints of the system should be considered, including response time, concurrency performance, load balancing, etc. Improve system performance and scalability through reasonable design and optimization.
Design for testability: When designing a system, consider the testability of the system, that is, whether the system is easy to test and debug. Adopt modular design and appropriate testing tools and techniques to improve system quality and stability.
Documentation and comments: Record system design-related documents and comments in a timely manner to facilitate subsequent maintenance and communication. Clearly and accurately record all aspects of system design, including design principles, interface definitions, data structures, etc.
Continuous improvement: System design is a process of continuous iteration and improvement. As the project advances and requirements change, system design adjustments and improvements are made in a timely manner to adapt to changing requirements and technical environment.

All in all, system design is a key stage to ensure system quality and maintainability. It requires comprehensive consideration of the system's goals, needs, security, performance requirements, etc., to ensure that the system can meet user needs and expectations.

3. System design needs to pay attention to the following points:

Understand the problem in detail before designing. Don’t rush into designing a complex solution, but make sure you fully understand the requirements and constraints of the problem.
Design a system that is simple enough to meet your needs. Don’t over-engineer and only pursue system complexity while ignoring actual needs.
Solve the problem first, then optimize. Start by designing a basic system that works, then optimize and improve it over time.
Analysis is more important than solutions. There is no standard answer to system design, and it is useless to memorize the answer. The key is to demonstrate your knowledge through the analysis process and weigh the pros and cons of various design approaches.

4. When developing coding, you need to pay attention to the following points:

Coding standards: Follow unified coding standards and styles to maintain code consistency and readability. Choose appropriate naming conventions, indentation methods, comment formats, etc. to facilitate collaborative development and code maintenance among team members.
Modular design: Split the code into modules and functions, each module and function is responsible for a single function or task. Modular design can improve code reusability, maintainability and testability.
Code reuse: Rational use of existing code libraries and tools to avoid repeated development of code with the same functions. Improve development efficiency and code quality by introducing appropriate third-party libraries, frameworks and components.
Error handling: Consider various possible errors and exceptions during the coding process, and perform appropriate error handling. Reasonably use the exception handling mechanism to catch and handle exceptions in a timely manner to ensure the robustness and stability of the program.
Input validation: Validate and filter the entered data for legality to prevent potential security holes and errors. Avoid using untrusted data to directly splice SQL queries or execute system commands to avoid security issues such as injection.
Memory management: Pay attention to the rational use of memory resources to avoid memory leaks and excessive consumption. Release unused memory in a timely manner and avoid frequent memory allocation and release to improve system performance and stability.
Asynchronous programming: For codes involving long-term tasks and IO operations, consider using asynchronous programming to avoid blocking the main thread and improve the concurrency performance of the system.
Debugging and logging: Write detailed and reliable log information to facilitate tracking and troubleshooting problems. Properly use debugging tools and techniques to debug and test the code to ensure the correctness and stability of the code.
Version Control: Use a version control system to manage versions and change records of your code. Reasonable use of branches and tags facilitates team collaboration and management of different versions of the code.
Documentation and comments: Record the relevant documents and comments of the code in a timely manner to facilitate subsequent maintenance and communication. Clearly and accurately record the function, design ideas, interface description, etc. of the code.

All in all, coding development is the process of converting designs into actual code, which requires good coding habits, specifications and tool usage skills. Consider factors such as code quality, performance, security, and maintainability to ensure writing high-quality code and improve development efficiency.

5. When conducting testing and verification, you need to pay attention to the following best practices:

Develop a software testing and quality assurance plan: Careful planning is essential for a successful testing process.
Test early and often: Getting involved in testing early and testing frequently can identify and fix problems early.
Don’t let programmers write tests: Writing tests by programmers may lead to a limited perspective on testing, and it is better to have tests written by an independent testing team or testing experts.
Conduct regression testing: Every time a change is made or a new feature is developed, regression testing is performed to ensure the stability of the existing functionality.
Use a combination of in-person and cloud-based testing: In-person testing can better simulate real-life user usage, while cloud-based testing can provide testing at a larger scale.
Plan post-launch testing: Post-launch testing is equally important. It is necessary to plan post-launch testing activities and find and solve problems in a timely manner.
Record and record all test results: record the test process and results in detail for subsequent analysis and improvement.

These are some best practices to note when doing test validation. To learn more about best practices for test validation, please refer to the following resources:

6. When deploying and going online, you need to pay attention to the following points:

Automated deployment: Use automated tools and scripts for deployment to increase efficiency and reduce human error. Automated deployment can be achieved through build tools, configuration management tools, etc.
Environment isolation: Ensure isolation between different environments (development, testing, production, etc.) to avoid conflicts and data leaks. Using containerization technology or virtualization to isolate environments is a common approach.
Security: Ensure the security of deployed applications and environments. Use the latest security patches and firewalls, conduct vulnerability scans and security audits, and follow security best practices.
Monitoring and logging: Establish a complete monitoring and logging system to detect and handle errors and exceptions in a timely manner. Monitor your application's performance metrics, log output, and exception reports to quickly identify and resolve issues.
Rollback plan: During the deployment process, consider possible problems and develop an appropriate rollback plan. Back up the current stable version of your applications and data so you can quickly restore to a previous state if necessary.
Comprehensive testing: Conduct comprehensive testing before deployment, including integration testing, functional testing, performance testing, etc. Ensure that the application functions properly in the new environment and can withstand the expected load.
Documentation and training: Timely record and update documentation on the deployment process, including configuration information, deployment steps, and troubleshooting methods. Provide training and support to relevant team members so they can understand and perform deployment tasks.
Communication and Collaboration: Maintain good communication and collaboration with relevant team members and stakeholders during the deployment process. Share progress, risks, and decisions to ensure everyone understands and supports the deployment plan.
Performance optimization: Perform performance testing and tuning before deployment to ensure the application can respond quickly and handle high loads in a production environment. Optimize database queries, caching strategies, network transmission, etc.
Continuous integration and continuous deployment: Apply continuous integration and continuous deployment workflow to the deployment process to achieve a fast and reliable deployment process. Ensure every change is automated tested and verified.

These are some key points to note when going live. Of course, specific deployment procedures and considerations may vary based on different applications and environments. Tailor it to your specific situation to ensure a safe and successful deployment.

7. When providing operation and maintenance support, you need to pay attention to the following points:

Monitoring and alerting: Establish an effective monitoring system to monitor the operating status of applications and infrastructure in real time. Set alert rules to promptly notify relevant personnel and take necessary measures.
Troubleshooting: Respond and handle faults quickly to minimize business impact. Establish a troubleshooting process and ensure team members have the skills and knowledge to handle incidents.
Security and Vulnerability Management: Ensure system and application security. Conduct regular vulnerability scans and security audits, handle vulnerabilities in a timely manner and update security patches. Monitor security events and take appropriate measures to address potential risks.
Backup and recovery: Back up data and configuration files regularly and test the reliability of the recovery process. Make sure your backups are stored securely and document your backup strategy and recovery steps.
Performance Optimization: Monitor and optimize system performance, identify system bottlenecks and bottlenecks, and take appropriate actions to improve performance. Optimize database queries, caching strategies, network transmission, etc.
Change management: Manage the change process to ensure the reliability and stability of the change. Plan changes, test and validate them to avoid unintended and unnecessary impacts.
Documentation and knowledge management: Record operation and configuration information in detail, and establish documents and knowledge base. Ensure that team members can access and use this information to improve problem-solving and decision-making capabilities.
Collaboration with Development Team: Work closely with the development team to solve problems and improve the system. Provide necessary support and feedback to ensure system reliability and stability.
Continuous improvement: Regularly evaluate and improve the operation and maintenance process to find potential improvement points and efficiency improvements. Use automated tools and processes to reduce manual work and errors.
Duty and emergency response: Establish a 24/7 duty system to ensure timely response to emergencies. Develop emergency response plans and test and validate response processes.

Most importantly, continue to learn and stay aware of new technologies and trends. Operations support is an area that is constantly evolving and changing, and through learning and continuous improvement, better support and services can be provided.

Operation and maintenance support requires attention to the following points:

Communication skills and teamwork skills: Operation and maintenance work involves cross-department and cross-type cooperation, which requires good communication and teamwork skills.
Be bold and careful: Operation and maintenance work requires an innovative spirit, but also caution to avoid major mistakes.
Stress resistance: Operation and maintenance work often faces time constraints and urgent tasks, which require strong pressure resistance and execution capabilities.
Flexible thinking and logical thinking ability: Operation and maintenance work requires flexible response to various problems and strong logical thinking ability.
Be modest, steady, approachable, and willing to help others: As an operation and maintenance personnel, you must have good personal qualities. When working with others, you must be modest, steady, approachable, and willing to help others.

references:

3. What does IT operation and maintenance/operation and maintenance development do? What abilities are required? What are the prospects?

Briefly describe the 8 stages of software development - Zhihu: Link
A brief description of a complete software project development process - Zhihu: Link
How to answer system design questions in interviews? - Zhihu: link
Software life cycle - Zhihu: link
What is the product development process? - Home of Wiring Harness Engineers: Link