Based on the company’s existing development process, their own process summary!

Suddenly one day, a need was raised…

  1. Product requirements documentation;
  2. Product organization requirements FR (development, leader and other review requirements, to propose unreasonable places -> product modification requirements document);
  3. Develop and understand business requirements (communicate with products, clarify requirements -> product improvement requirements documentation);
  4. The requirement design document is presented in the development, which is roughly as follows:
    1. Requirements description [Background objectives, business flow diagrams, use case diagrams, etc.]
    2. System design [System architecture diagram, sequence diagram, state machine diagram, ER diagram, interface definition, external interface, MQ message, scheduled task, etc.]
    3. Release preparation [SQL, backend, forms, RBAC, etc.]
    4. Development plan [How many PD each needs for communication requirements, requirements design, table structure, interface definition, back-end interface development, testing, front-end and back-end joint tuning, release preparation, etc.]
  5. Development organization Design Review (Development colleagues review design)
  6. Clear interface definitions (front and back end clear interface definitions, MQ message definitions, external interface definitions)
  7. Back-end development;
  8. Back-end self-test;
  9. Code Review (development colleagues review your code -> cr changes);
  10. Front-end and back-end combined adjustment;
  11. Release online.

Note: Development above refers to Java backend development.