Standard Japanese software development process

The development progress of software projects in Japan is very strict, and projects are rarely postponed. Once the project is postponed, a large amount of fines will be incurred. Therefore, Japanese software projects place great importance on regular delivery. The software phase definition plays a key role in the progress control of software projects in Japan.
Japanese software projects are divided into project proposal, Element Definition, outline design, detailed design, and preparation Code , Standalone testing, Combined testing, system testing, and writing. Project proposal refers to the feasibility analysis and project initiation of a project. It is the formal proposal stage of user requirements. A project proposal is issued at this stage. Definition of requirements refers to the detailed determination of business requirements and the detailed determination of system requirements. system requirements mainly include software security, operating speed, network environment, operating environment, platform, architecture and other requirements, and technical selection survey, this phase issued the Business Requirements Definition) and the system requirements definition. Summary Design refers to the functional design, system architecture design, interface design and database design. The interface design and database design involve the most content and require the most details, in this phase, a summary design definition book, (Database Design definition book and interface design definition book are issued. The detailed design mainly refers to the class design Before encoding, the method attribute design in the class, and the call relationship design between classes. This stage is issued (detailed design definition book). Writing code refers to writing the relevant code by the module owner. Before coding, you need to write a standalone test style book. Program Source code and ("standalone test style book". Single test means that the coding personnel of each module completes the single test of each module. The single test completion requires that all defects in each module should be eliminated during independent operation. This stage is issued (single test ticket). Combined testing refers to the testing of the running status between modules when each module is running simultaneously after a single test is completed, including the business flow, load, running speed, stability, consistency, and so on, in this phase, a test ticket is issued. System testing means to simulate the testing process of running the user environment after all the defects of the system modules are eliminated. In this phase, we should simulate the actual user platform, number of users, hardware environment, and software environment as much as possible, network Conditions and user data are used for system testing. A system test ticket is issued in this phase. Compile the manual for hand-directed writing. In this phase, the "install hand-directed", "Use hand-directed", and "maintain hand-directed" are issued.
The basic process of development for Japan includes the above one phase, each of which is a milestone, and each milestone sets a clear deadline for completion in plan arrangement, these milestones are the progress of the project. Key. After each stage is completed, the stage I r e v I e w must be carried out. This stage r e v I E W plays a role in phase acceptance and summarization. Phase r e v I E W is the core of Phase Control for projects in Japan.
There are also some shortcomings in the acceptance only by using the stage r e v I E W. All the acceptance work is completed in the stage before proceeding. The subsequent enlargement of errors in the stage cannot be controlled. In addition, there are many problems in phase r e v I e w, which will be modified after r e v I E W. it takes a long time and a large number of modifications, resulting in a large amount of repetitive work. In addition, the schedule and acceptance of tasks in the phase during the software development process are compared with those during the software development process. In disorder, many problems will be intentionally postponed until r e v I E W.