1. Overview According to the statistics of authoritative departments, the current success rate of software is about 25%, and 75% of software is failed. In this 75% failure, about 50% of software is caused by the cause of the demand. As the design and developers often complain that users are not clear, demand is often in a change state. New demand is often proposed by the user during the development phase. The completion date of the software is constantly ending. General software companies often only pay attention to user needs. However, because there is no scientific management method, the user needs they describe is messy, only words. It is not possible to effectively and system design, and the development of software products that maintain synchronous final development has greatly varied. Resulting in the failure of the software. There is evidence that in the demand phase, the wrong workload is a 1/10 in the system design phase correcting the wrong 1/10; 1/100 in the development phase correction error is 1/1000 in the release of the product phase. Of course, this is different for large systems, for different systems, the ratio with the complexity of the system will vary. The increase in the demand for users has gradually, incrementally characterized. With demand analysts and users, users are constantly organizing and regulating their needs. Demand analysts must keep in mind that users cannot give a complete, clear and standardized user needs. Demand analysts need to have the desired needs from being intensified from communicating with users. Demand analysis is generally a need for a team of demand analysis, such as user representatives, system analysts, developers, demand management, and more, their divisionaries have different focuses. For small or medium-sized projects, you can work. Based on the above reasons, it is necessary to standardize the collection and finishing of user needs. In this paper, the general method of demand analysis is given in conjunction with system modeling. It contains two aspects: 1. Technical level gives a system framework for demand analysis. It contains demand items, and users involved in demand analysis, users are subject to the needs of the needs (security), etc. 2, the operating level gives a general method for collecting, finishing, and analyzing the needs. It introduces the interrelationship between system modeling and demand analysis, and finally introduces several popular demand analysis products and their characteristics. Second, the purpose analysis of the basic concept of demand analysis is to completely and accurately describe the user's needs, track the changes in user requirements, accurately reflect the user's needs into the system analysis and design, and make the system analysis, design, and The user's needs are consistent. Demand analysis is characterized by the integrity, consistency, and traceability of demand. Integrity: It is accurate and comprehensive to describe the needs of users. Consistency: By analyzing, the user needs are regulated in terms of user demand contradictions. Traceability: There are two meanings, sorting and standardization requirements, one, requires continuous communication, maintenance and user's latest demand unanimous; second, and systematic analysis (design). Therefore, we must establish the basic framework of the technical level of the demand analysis, from the technical guarantees of demand analysis, on this basis, the demand analysis we have to meet the requirements of the project on demand analysis. Third, System Architecture of Demand Analysis This section describes a system architecture that establishes demand analysis before the technical level is performed before demand analysis. Demand analysis requires software for demand analysis. The above figure briefly describes the architecture of demand analysis software. Demand analysis software generally uses C / S structures, demand analysts operate as customers, mainly by four aspects: system management (including user creation and authorization, definition items, etc.), project view (involved Project Related operations), demand type view (related to related operations related to requirement), demand view (related to requirements involving requirements). The project contains one or more requirements types, and the demand type contains one or more requirements.
Milestones are a collection of specific versions (requirement analysis software contains simple configuration management features), which is based on the functional basis of software products. Automatic documentation is to automatically generate related documents through document templates. 3.1 Project projects generally define an application and a range involved in the needs and requirements involved in the system. It contains people, demand types, demand types, demand types, and needs in the demand type during the demand analysis process. In addition, it also contains the following information: Project information (such as creative person) Milestones of the project External traceability Security framework, etc. 3.2 User / User Group Users refer to personnel involved in demand analysis, generally consisting of end users, software developers, system designers, testers, etc. of software products. In a demand analysis product, the user includes the basic description and contact information (such as email), etc. personnel. User group refers to one or more users with the same operation permissions. User groups can be assigned to a particular item or requirement (the user in the user group has the corresponding operation permission). 3.3 Security Security refers to the user's operational permissions of the user during the demand analysis process. Security prevents unauthorized users from operating on critical needs. Security is a relationship between user / user groups and needs. Generally, there are three meanings of security: System management system maintenance (system data backup, etc.), user management, user group management, etc. The security framework defines the basic operation permission of the user. This kind of operational permissions and specific projects, project demand have nothing to do. If the need to add by a user can only be deleted by this user. The security framework can be divided into two categories: Access level (Access Level) creation, view, and maintenance requirements. Delete Level Delete the requirements. The security of specific needs is established to associate the user / user group and a specific requirement to determine this user / user group on the needs of the needs. 3.4 Demand Type / Demand Demand Type is usually a higher level of demand, such as a user interface. Demand is a description of the system or application to be constructed, and demand can be obtained by business rules, processing processes, and personnel organization. Demand is included in the type of demand. Demand Type / Demand is generally described by text, and it is also possible to describe demand through the needs of the needs. 3.5 Property Properties Used to describe the related features of the demand, attributes can generally be divided into two categories. System Attribute: Describe the system characteristics of the needs, such as whether the requirements are confirmed. Custom properties: Customize the properties used to describe the needs. Such as described by the person's phone number, etc. 3.6 Requirements Grid Demand Grid is a set of associated demand mesh formations, mainly for analysis of demand. Generally speaking, it can be defined, such as displaying the needs he created for a user, showing related needs for a certain function. 3.7 Demand Mapping Considering this background, in a real-time system, the acquisition and transmission of digital signals use the same implementation in different control systems, and their needs are the same. In this case we can use the technical map of the demand map, the demand mapping is the same needs in different projects. There are three items in the figure, the demand R3 in the project A is shared, and the demand of R3 in project B is mapped to the demand of R3.3.8 traceability (Traceability) traceability is a consistent expression of demand. . It mainly includes the following meanings: 保 Keep and user requirements must keep in mind that user needs are constantly changing. Demand analysis requires adaptation of the continuous change of demand. 保 Maintenance and consistent users from all levels, often contain considerable contradictions, an important aspect of demand analysis is to eliminate these contradictions and regulate users' needs. The dependence between the demands can also be represented by traceability.
保 Synchronization between maintenance requirements and system design In most projects, demand analysis and system design have an inevitable connection, the consequences of this situation are far from software products and practical demands. For example, a manual method can be made to maintain the demand and system design. But this method is insecure because there is no corresponding mechanism to force relevant personnel to comply with the rules. Therefore, it is necessary to ensure the consistency of demand and design, and most demand analysis tools have a synchronous plug-in and system design tools, such as Borland's CaliberRM, IBM Rose, Telelogic's DOORS, etc. 3.9 Report Report The report can be understood that the needs of the needs are described from different levels, and the reports can be filtered as needed, such as reports of a certain type of demand, reports for unclear demand. The report can generally be divided into: Detail report describes the details of the needs. Status report describes the status of the demand, the status of the demand can be divided into acceptance, not clear, rejected. Responsible reports to participate in demand analysis reports on their responsible demand. 3.10 Discussion Discussion is a collaborative mechanism between demand analysis team members during a demand analysis process. This mechanism allows the relevant person to discuss the definition, description, status, priority, consistency, integrity, etc. of the needs, and the correct conclusions. Discussion Generally, divided into two levels, project levels, and demand levels. 3.11 Document Reference The description of a requirement may require an external document, and the document reference is an additional information to describe the relevant requirements with an external file. The current demand analysis product supports the maximum document type is MS Word, and the excel, image file, HTML, and OLE, etc. are also supported according to the product. 3.12 Milestones are constantly changing, software products have different versions of changing demand, each version of software except for the software itself, is to meet newly added needs, and software products need their implementation It has stability. Milestone is a phase of the demand analysis process, which is fixed unchanged. 3.13 Documentation Automatic Generation Participating in Software Development has such an experience. It is a variety of documents to give the software before the software product is completed, and there is also a variety of contradictions between documents. This is a shortage of demand, design, and lack of synchronization. If we are in the development of software, strictly follow the development specifications of the software, using corresponding software engineering tools, the above situation can be avoided. In demand analysis, the demand analysis products can automatically generate corresponding documents according to the results of the analysis, and the format of the document can have MS Word, PowerPoint, HTML, etc. Here we mainly introduce the way of generating the Office Word document. We need to define document templates before you automatically generate documents. Create a document template in Office Word based on the relevant commands of the format and demand analysis software to generate. After the document template is created, select the milestone in the demand analysis software to automatically generate the Office Word document. Fourth, the demand collection and finishing requirements analysis is a process of describing users' data, activity, location (location), personnel organization, plan, business logic (business target), etc. from the perspective of users, involving how to collect users Demand, and how to standardize these demand. The first step of demand analysis is to define the boundary of demand, mainly describe the project, project business requirements, and the basic characteristics of the project to meet. In the third quarter, we briefly describe how to standardize the process of demand analysis from the technical level, this section mainly elaborated how to collect and organize demand. 4.1 Data data refers to the relevant static information involved in the demand. During the demand analysis process, the data is described from the user's perspective; during the system design, the data is organized and specified with object-oriented methods, and finally forms Class Diagram. 4.2 Event activities is the business logic and rules to meet the project.
