Tips for using the system during System Development

 

First, the design of requirements and the selection of solutions

When there is a business demand, there can be two or more solutions to achieve this, the overall trade-off Principle

Such as the Barrel Principle, whether or not the complexity of each component of the system is average, and resolutely cancel a scheme with a particularly high complexity.

2. Functional priority during development

In the development process, the system has two core functions: one core function, and the other is convenient for users.

In the process of system development, pay attention to the core functions of the system, and users can conveniently operate functions with as much latency as possible.

Just like when we develop a system, there are a lot of non-core functional points at the beginning of the launch, Business Information Statistics, a series of special cases on non-core functions. (It may be convenient for users to reduce the number of features) will be gradually abolished in the subsequent use process.

For developers, there is an unnecessary increase in costs. (This is a pure profit)

Disadvantages: It is hard for system users.

The entire system is rejected.

3. Implementation of the development process

Design Scheme Review before implementation (especially for complex businesses)

1. Improve the software developer's understanding of the business

2. Reduce software risks (collective wisdom is powerful)

 

Unit test implementation of system functions (the following content is my own unit test ideas)

Unit 1 testing is completed before the system is implemented, which helps developers to verify functional interfaces from the user's perspective.

2. Reduce debugging time and System bugs