How to prototype the separation of interfaces and business logic

Home Back

How to prototype development I. Comparison of advantages and disadvantages of Structured System Development and prototype development   Structured Method) Prototype Method) Basic Ideas The information can be fully understood before the system is established. It requires a strict division of the development phase, with standard methods and chart tools to complete the work of each stage step, each stage is based on standard documents and materials as their results, and ultimately meet the needs of usersAdvanceRequired System. Because it needs to be pre-determined and the development stage no longer accepts new requirements, developers are like shutting up and following the steps for development, so this method is often calledClosedDevelopment Method. After developers summarize the issues raised by users and reach consensus on the main requirements of the system, they develop a prototype, which is developed by developers in collaboration with users, jointly determine the basic requirements and main functions of the system, and develop an experimental, easy-to-use small system in a short period of time. The prototype should beCan runAnd can be modified. Run the prototype and perform the "Supplemental requirement-modify" process repeatedly until the user is satisfied with the system. Optimization (1) Separate logical design from physical design (2) A set of standardized documents are formed during the development process to facilitate later modification and maintenance. (3) modern system design means can be used to reduce the development cycle, improve the system stability, and coordinate various functions and parts so as not to conflict with each other. (1) clearly stated requirements, high user participation, and high user satisfaction (2) reduce risks in the startup phase (3) the Bata test time of the final product is shortened by modifying the system while running. Missing points (1) long development cycle (2) The system may have very powerful functions for the industry, but it is difficult to adapt to the most personalized needs. (3) complicated and cumbersome Development Process (1) The prototype method is not applicable to the development of large systems with a large number of known requirements. (2) requirement capturing is easy to ignore record sorting and change history, and other tools are required (3) Documents are relatively scattered, and each function and part of the coordination is poor, so it is difficult to maintain (4) If the user's cooperation is poor and the error is corrected blindly, the development process will be delayed. Applicability This method is applicable to the development of large and complex systems with relatively stable organizations, standardized business processes, clear requirements, and no major changes in a certain period of time. (1) Unclear user requirements, unstable management and business, and frequent changes in requirements (2) small scale, not complex (3) Develop the end user interface of the Information System 2. Rare pure System Development and prototype development In the complex and changing MIS development process, the above method is rarely used, because the cost to overcome their respective shortcomings is still very high, system development is often used for the parts with standardized business processing procedures and clear requirements, while maintenance is required for frequently changed functions. Among the MIS development vendors that have gained long-term benefits, the results of the phase of "crossing the river by feeling the stones" can be considered as a prototype product in the development process) in the hope that all functions and parts of the system can be more coordinated during prototype development, so that the system can be more stable and the parts of the existing requirements can be more easily maintained. Therefore, in the composition of the entire MIS, new requirements are basically prototype development. After a long period of maintenance, it is often re-designed to use the system development method. As a result, many systems have gone through the cyclical process of "partial prototype development-system development. Iii. Key Points of Prototype Development 1. Develop a prototype The entire prototype may be a simple system or a simple addition part of a complex system. As an introduction, I think the first thing to do is to create a new form, and then place some related controls as needed, such: 2. fully communicate with customers, record requirements, and form documents At this time, the response to the button1 click event is generally empty. However, if requirements can be entered at this time, it will greatly facilitate communication with users. In this context, users can accurately express business requirements, reflect their respect for users, and collect more smoothly. Of course, it is better for developers to enter the requirement text or process description by themselves. So we Write the response code for the click event of button1: Void _ fastcall tform1: button1click (tobject * sender) { Unternimatedfunction (dobject) This ,__ func __, l "TBD function", l "001", l "001 "); } The unternimatedfunction can specify the description, number, and subnumber of this function to facilitate archiving management. As you can see, writing can also separate the interface from the business. After such a simple writing, developers can click this button when communicating with users. The following dialog box is displayed: Click the "original description" button to enter a text description of your needs. After entering the information, press the "generate document" button to generate the document and save the history. If you need to use a flowchart to describe the requirement, you can also click the "flowchart" button and call dd to draw a picture: 3. Save the history and sort it out in due time Keep the history of the generated documents in a timely manner and coordinate other functions. Otherwise, conflicts between various functions may occur.   [Appendix] Magic Lamp display Download Prototype Development Kit Runtime Environment Composite Bridges