Pei Li (reprinted from China System Analyst) February 01, 2003 [Abstract] This article combines its own experience, from the perspective of practice, the analysis of the project software is elaborated from 7 aspects, and points out some easy mistakes. practice. I hope to have a reference to colleagues engaged in analytical work. Software can be divided into project software and product software from the perspective of the scope of use. Project software: that is, for a particular customer request, only software used. Also known as the engineering software, it is characterized by a clear contract, strict construction period, the agreed maintenance period, etc. Such as "XXX XXX System". Product Software: Software developed for a common demand for customers in a certain field. Features is common, rich and redundant, obtained by one-time purchase behavior. Such as operating system software, database software, CAD software, etc. This article provides some views and suggestions for the needs of the demand for project software. 1. It is important to determine the appropriate customer-part in accordance with the analysis phase. This is very important for obtaining real user requirements. Typically, the client is organized to organize the above-level person or a small-owned computer can cooperate with the developer's analyst, and jointly organize demand. The customer party should be classified, hierarchically, and each phase of the analysis should be made. The initial stage of analysis, that is, the overall analysis phase, it is necessary to obtain the overall contour demand. At this time, it should be exchanged with the personnel of the customer's leaders. This level of people will have a complete depiction of the future system. It can be divided into a subsystem, and the relationship between it is also the expectation of the advanced management to the system. It can be further analyzed as a document, and constrain subsequent analysis processes, avoiding the demand scope and has no margin; professional system analysis stage, usually, the client unit will have professional division of labor, and each other is independent of each other, and will Contact occurs at some point. This stage should be discussed in-depth discussion with the personnel of the client. This level of people are quite familiar with their majors. It will be very in place for the needs of the professional, and the rich experience is strong, with considerable experience and understanding, even they can draw business flow maps, summarize business function points. I should fully encourage them, try to mobilize their enthusiasm; the system-related analysis stage, based on the professional system, it is necessary to clarify the relationship between them, this is a key stage of improving the demand grade, and is also advanced The leadership and special work are concerned. Typically, there are some scattered software, such as financial software, deputy software, etc., these professional software have played an important role, but they are some information. The customer will naturally integrate this information to the whole. In the system, you are shared for more people. At the same time, it also hopes that the data can flow smoothly in various professional systems, thereby reducing labor and improving working efficiency. At this stage, the total worker layer and the lattice should be collected together to jointly clarify the interface between the system. After these three phases, the description of the needs will be more accurate and complete. 2, multi-faceted description Some needs have some requirements run through the leadership from the grassroots personnel to the high-level leadership, and the demand should be described from all angles, each orientation to the description, so that some information may be missed. This is also based on subsequent design work. For example, in the device management software, there is a concept called "defect", which means that the equipment is in an abnormal operating state, but it has not been immediately produced, but if It may be possible to check it out in time.
For equipment defects, it involves itself to the leadership from the team. It is very concerned about this, but the focus of each level is not the same: Leaders care "消 消 rate" (ie defect cancellation rate) , "Timely, timely rate"; specialist care type and processing method; team personnel care about the staff arrangement and time location. The defective business processing process depends on "device defect list" (for recording defects and elimination), if only limited to data structures on defects obtained from the base layer (device name, defect finder, discovery time, two Level unit confirmation time, defect nature, arrangement time, defect person, elimination date, handling method), unable to meet the analysis requirements of the special work layer: the defects of the equipment are classified according to type, component, model, manufacturer, etc. Statistics, for equipment procurement as a selection reference, adjustment equipment, and its components to reduce the frequency of defects, etc., therefore needs to add some relevant information on the original equipment lack. 3, clearing each data item Since the demand will be the foundation of the design, it is essential for the destruction of all data items. There is no confidential place. At the same time, through the analysis of data item sources, you can make analysts see the flow of data more clearly, and some new demand points will be found. 4, full mining potential demand Since the analyst is very familiar with software technology, some potential demand brought about by technology is generally difficult to discover. Do not achieve these needs, there is no substantial impact on the entire system; to achieve these demands, it will add flowers on the brocade. There are two ways to handle these potential demands: telling customers that customers will be inspired, may further put forward new needs, there will be some more bold ideas, thereby expand demand, increase workload, and even affect During the period; do not tell customers, wait for the customer to say. These requirements can be a selling point if the product software can be used as much as possible. But for project software, consider various risks, sometimes avoided, or concealed against customers. I think, no matter whether it tells customers, the analyst should still take it, and at least be accumulated as its own knowledge. 5. After using the scientific analysis report template analysis, it is necessary to form a "demand analysis report". It should adopt the report template for normally scientific science. The template is very detailed, not only as a report template, but also guidance Analysis process. For example, in addition to the regulatory demand analysis report to prepare a guide, report template, and "demand analysis matrix" and "demand change report" for administrative requirements and control changes. 6. The knowledge field knowledge in the field is important for analysts. The breadth and depth of these knowledge affect the accuracy and analysis schedule of analysis results. Analysts should get these through various ways, constantly accumulate, and compare and summarize. 7. When the attitude of learning and guidance is facing a new customer, the analyst must first hold the attitude of modest learning, regard this as a chance to enrich the domain knowledge. However, any level of non-client unit has something worth learning. As the analysts have increasing the increasing fields, the analysts will become deeper and deeper, gradually grow into a field expert, there will be Many places exceed the understanding of the world, at this time, to guide customers, persuade customers, and even correct customers' misunderstanding, and respect the customer's trust and respect, this for the rapid successful completion of demand analysis It is very helpful.
