1 Introduction
The demand analysis phase is the most important phase of the management information system (MIS) development. The demand phase developed by MIS is first to understand and clarify the needs of users and then strictly define the demand specifications of the developed software system [1]. Common software demand analysis methods have a structured analysis method for data streams, a Jackson method for data structures, and object-oriented methods and prototypes. The prototype method has changed the point of view of the system's analysis, design and implementation of the three order [2], changing the traditional auto-top development model, reducing the risk of software demand, so a wide range of applications, especially Software companies dedicated to MIS development in a field, such as companies committed to electricity MIS. However, in the long-term MIS demand analysis process, the authors found that prototypes have the following flaws:
1) The design and modification of the prototype is large, and the development cost of the system is increased;
2) Since the user does not care or not understand the concept and implementation of the prototype, and there is a large expectation, it has increased the difficulty of the demand analyst and the user's communication with the actual system; whether the horizontal prototype is, or the vertical prototype Can't reflect the whole picture of the actual system;
3) Software demand mainly includes: functional requirements, interface requirements, performance requirements, environmental requirements, reliability requirements, security and security requirements, resource usage, software cost consumption and development progress requirements and target requirements [3]. The prototypes in the prototype are difficult to express the post-seven needs of the software;
4) Prototyping Method emphasizes that users and developers continue to revise and supplement prototypes until users are satisfied. In a large MIS project with a key time and task, this situation is actually difficult to guarantee, especially when the user unit and the development unit are farther away.
This paper combines the practice of management information system project implementation, proposes a new demand analysis method - Simplified prototype. According to the characteristics of the database application, this method is divided into two phases and simplifies the system prototype as a demand analysis tool.
2 Simplify the first stage of the analysis of prototyping
The management information system belongs to the database application. Database application requirements analysis should surround data, not functional, so you should first solve "What", and then "what" [4]. The first stage is to solve "What is", that is, negotiates with the project manager to determine the technical protocol of the system, so it can be called the technical protocol phase. The technical protocol requires the development side's project manager to sign and block the technical supervisor of the user unit, and exists in the form of the contract attachment. The main contents of the technical protocol are: the boundary, system processing of the system, the interface, the progress control of the project, the progress control, training arrangement and technical service commitment.
2.1 Border of the system
The boundary of the system specifies the system coverage, mainly with geographic boundaries (departments, branches, etc.), operator scope (all operator identity, distribution and general permissions of the operating system) and business scope The processed business is particularly clear about the non-processed edge business).
2.2 System processing business
The system processed business covers all services processing, including various services, data sources, and implementation requirements. However, the business regulations do not require too thin, and can correspond to one of the actual systems. Such as: Line Equipment Management in Transmission Facilities Management Subsystem in Power MIS, does not describe all functions in line device management.
2.3 Interfaces with other systems
The interface of the interface is clearly specified in the interface of the interface with other systems. In the implementation unit of the interface, it is clearly completed by the development partner or by the development side to assist the third party.
2.4 Project progress control
The progress control of the project is the beginning of the project, the end date and the name of the specific project project, the completion time, location, completion mark and responsibility division. Specific projects generally include: procurement equipment to reach the site, procurement equipment installation and commissioning, complete network wiring, development preparation stage, business needs survey, system analysis, design, software preparation, on-site debugging, data preparation and entry, function confirmation, trial operation and system acceptance. Responsible division of labor requires both parties to work content and mating methods for specific projects. In the mating method, the personnel organization, the quality requirements, the equipment and places provided by the personnel are provided. Complete the logo specifies the file name and requirements of the specific project to complete, such as: Network wiring acceptance report and hardware device acceptance report. 2.5 Training Arrangement
Training includes the training of operators and system maintenance personnel. Training arrangements include the number, training content, training time, location, organization method and textbooks for each training, and stipulate the quality requirements of instructors and students, and the level of trainees reached.
3 Simplify the second stage of analysis of prototyping
If the first phase solves the "What" problem, then the second phase solves the problem of "what". The main task has a demand survey, to the user unit to investigate and analyze the needs review.
3.1 Requirements Survey Preparation
Demand survey preparation work, after signing the system's technical agreement, strictly follow the technical agreement, mainly there is a business questionnaire to the user unit, establish a demand analysis document prototype and establish system simplified prototype. After the business survey is signed after the system's technical protocol, the business survey is signed immediately, and it is sent to the user unit by fax, requiring the user unit to complete before the needs investigators arrive. The content of the business questionnaire includes: the name of the specific business, superior service, subordinate business, conditional, processing data, and detailed processes (handling post, processing methods, and audit details, etc.). The demand analysis document prototype is based on the requirements of the demand analysis specification prepared by the technical agreement, and its format is the same as the standard demand analysis manual. Among them, the state migration diagram and the unclear content such as various votes are used, and the similar system or by system analyst is designed according to technical agreements and previous experience.
The simplified model of the system is designed according to the requirements of the technical protocol. The simplified model uses visual database programming language design, generally using the database application developers familiar with PowerBuilder (PB) or Delphi. The main design requirements of the simplified model are: 1) The design and implementation of the system can not be detached from the actual system; 2) Try to simulate the operation interface of the actual system, identical to the actual system's operation; 3) can be run alone, Not connected to the actual database; 4) Sample stored data window can be given by text files, single-machine database, or PB external data source data window; 5) For operations that are easy to misunderstood or understand in the interface, the function help button is given in the function help button. 6) The function is difficult to implement or have a large amount of work, in detail; 7) Operation is stable and lower than the actual system.
3.2 Request investigation and analysis
Demand Survey Analysis After the completion of the three work preparations for confirmation of demand surveys, the system analysts from the development unit go to the user unit. The business supervisor of system analysts and user units jointly discusses business investigations and system simplified prototypes, and constantly modifying the simplified prototypes and document prototypes, and finally forms a consensus, and requires business executives signing on demand analysis instructions. The final system simplifies prototype and source code to stay in the user, which is convenient for the system's operator to further understand the analysis until the final master; and conducive to further improvement. Improvement opinions can be sent directly to the development unit via email or fax, or after modifying the simplified prototype by the system maintenance personnel of the user unit, it is easy to send to the development unit, thus facilitating the development of the system design and encoding the system.
3.3 Review of demand
Demand reviews are generally organized by user units, and members of the jury consist of peers experts, system analysis, design and testers. The basis of the review not only has a need for analysis instructions, but also a simplified prototype; while the system simplifies prototypes continue to optimize during the review process. The goal of the review is to require the demand analysis instructions with the correctness, feasibility, necessity, priority properties, verifiable, and no meaning [5]. The demand review report serves as a supplementary and correction of demand analysis, signed by the person in charge of the two sides, exists in the form of an attachment to the needs analysis, and also guides the next system design. 4 description
1. This method is suitable for various MIS projects, especially suitable for software companies that are committed to MIS development in a field. This method is used to develop similar items, the higher the efficiency of demand analysis.
2. During the demand analysis process, due to the need to simplify the prototype and document prototypes, it is sufficiently considered that the system is designed and implemented, and the requirements for the analysis analysts are improved, and the requirements for demand analysts are improved. In practical work, general software analysis and designers are generally performed.
3, this method is not only suitable for MIS software engineering, but also suitable for other large software projects.
4. Due to the difficulty and importance of the demand analysis, this method also requires user units and demand analysts to analyze all work content, causing enough attention; scientific arrangements analysis work steps, some steps can be carried out simultaneously; all work The steps should not be negligent or negligent.
5 Conclusion
At present, the prototype method has been applied in multiple power MIS projects, which greatly improves the efficiency of demand analysis. Practice has shown that simplified prototypes have the following features: 1) Simplified system prototype development efforts have greatly reduced, modified and supplemented; Strengthened the understanding of the system and the business executive to the system, which is conducive to discovering and solving problems; The operator's understanding of the actual system greatly simplifies the operation training of the project after the implementation of the system; 5) Simplify the prototype to directly guide the design and encoding of the project, which is easy to organize the system. This method can also be used in other software engineering, and has guiding significance for other reforms of other needs analysis.
