Business Systems ("incremental iterations") development process Management

As a set of B/s lightweight rapid development engine, Noahweb can help you quickly realize the development of website and information system. For some large scale, slightly longer cycle, especially the system of frequent changes in demand, using the Noahweb engine with the "incremental iteration" of the development model, you can multiply shorten the project cycle, improve efficiency, save costs.

You can experience the use of noahweb for a system with frequent changes in requirements (such as: Web site Content Management system, business System, OA). The development process was developed for 2 full-time developers, 1 project managers (about 20%), one art (workload of 1 weeks), and the entire project cycle at 1-2 months.

[view big picture]

Requirements Analysis Phase :

At this stage, your needs analyst's focus is on functional analysis. Designers Draw UML use case diagrams and Analysis database structures, and use a way that is very close to the description of behavior in natural language-"action" to show the operating process of the system, the system designers do not need to consider system integrity. Only the main functions of the system are planned. and lists the action breakdown list according to actions. (Note: The concept of a class does not exist in Noahweb, so there is no need to consider the program structure)

The document to be exported for this output document is as follows:

A, UML use case diagram:

B, Action Breakdown list:

C, database structure diagram:

prototype development phase:

At this stage, your coders need to generate the various resources of the code content, because the noahweb in the various resources are used in XML format code description and save, the XML file is ultimately resolved by the Noahweb engine, the logic and description in XML is not related to the final rendering effect. This allows your coders to not consider the interface and final rendering at this stage, allowing your team to develop prototypes in a relatively short period of time based on the upfront design. Using XML encoding also provides a very good support for your and your team's rapid response to requirements changes that occur in subsequent development.

Implementation phase:

With the features of loose coupling of Noahweb program, you can develop the project in horizontal "incremental iteration" and multi-person parallel cooperation in this phase.

Incremental iterations allow your end users to feel the system from different points of view and understand the details at multiple stages of coding. Use the iteration to guide you through the real needs of your users. Your users will still have access to at least four experience systems throughout the implementation phase, respectively, for the entire system's 1, process. 2, data input, data echo. 3, process integrity. 4, permissions and system integrity to get experience, to give you feedback on the real needs.

At this stage, the coding staff to write a variety of resources are still XML-formatted code, you can allow the coder to take advantage of the various advantages of XML format and follow the "Noahweb Resource naming Specification" easy to achieve multiple concurrent cooperative development. In order to improve efficiency again, you can also allow a number of parallel development of the coder between the line of the Division of Labor, the Division of labor, your coders will be in the adjacent time to write similar functions of code, these code to write similar, can greatly shorten the coding cycle, and can reduce the entire system bug generation possibility, To the late stage of the project, it also makes it easier for testers to find system bugs that are caused by similar causes.

Release phase:

At this stage, the system enters the trial run, the development is nearing the end, the end user will actually use the system you developed, because of the previous "incremental iterations", this time the system is very close to the user's real needs, At this stage, your coders and testers focus on debugging and scheduling the entire system through error logs that are automatically collected by the Noahweb engine, enhancing system stability. The requirements changes that occur at this stage are usually the result of end-user human causes, and Noahweb can still make it easy for you to deal with these unexpected changes at this stage. noahweb-let change always be part of your plan.