【Summary】
This article discusses the main features of the project and the work as the work as the work, and focusing on the specific methods and tools used in the project demand analysis process.
Due to the particularity of the project's professional field, divided into two types of different needs discuss the problems and solutions encountered in demand analysis; the description of the effects of the specific tools and methods for the selected use are given during this process. Then, some ideas and specific implementation processes for improvements in the use method are discussed herein. Finally, I proposed some views on demand analysis, emphasizing the importance of communicating with customers.
【text】
In recent years, I have been engaged in the development of IT projects in an enterprise. There is a system for computer auxiliary circuit designs, including all processes from the uplift to the downflow design, such as logic gate for designing millions of gates. Circuit. In terms of respecting the path extraction, filtration, and a software development task in the circuit in the circuit to our company, I have been fortunate to have a demand analysis and design of the part.
The part I have designated is a separately canable software, mainly the linkage path in the parsed file, which is displayed in a list view and a histogram, etc., and functions such as finding and filtration can also be performed.
The principal provides a preliminary demand for this, and describes some basic functions and performance requirements. I have two main points in demand analysis: First, detailed demand for the interface of the software must re-analyze the analysis. Second, the required function requires deepening and refinement to form a true and complete demand analysis document.
After receiving the requirements analysis task, I analyzed the work you're done. Found that due to software in the special field, it is quite high in the professional field, so it is ready to divide this project into two parts:
(1) There is almost no impact on the domain of the interface, but because there is no requirement, it will feel that risks and changes may be the largest.
(2) Functional aspects can be called for the corresponding modules due to many of the functions of the principal, and the simple needs of the corresponding written, it is only completed. For the interface, I used some RUP ideas and gradual. The functional demand has taken layered refinement, and each layer is required to confirm, modify, and supplement the debt.
First of all, the larger partial part is completed, which is the basic common sense of modern software development. I chose to analyze the demand for the interface. The first step is to extract the logic model according to the functional description, and the logical model corresponds to the interface element and function, which determines the functionality of the interface, and then determines the specific control according to the interface function, at this time, I will refer to the interface layout and control of the principal, which have been initially completed, and then the function of the control is used as needed, and the Windows and UNIX dual platforms must be supported, so the control library uses QT) class library to select the appropriate Control. When extracting and abstract logic models, I use the case map in Rose 2000, that is, the relationship with the outside is described in the Use-Case diagram. The reason why Rose is used, I am based on the following reasons: First, in the developed part, the principal is unified to use ROSE to create design and code generation of class and sequential diagrams. Second, ROSE provides a standard map to describe the relationship between the system and the outside, a standard structure in a global scale. Third, the convenience of use is used. I use rose's use-case graph to clarify the interrelationship between our software window and the principal window and external role (operator).
After determining the interface element, considering the understandability of the document is not very strong, I use Visio 2000 to draw the appearance of the interface, write the basic control role, then give the entrust party review, fortunately, in addition to several The modification of small features, the client basically approves my solution.
The following work is to develop a corresponding state migration diagram for the behavior and status change of the control. I use the tool is still ROSE. I use the status map and timing chart to describe the status of important control status and corresponding sequence, then subsequent A few days, the corresponding DOC document is completed, and basically the interface design is completed. The following needs are for functional requirements. Although the principal's technical department has a preliminary demand document, because of the specialization of the field, I don't know that the complex path extraction relationships and deeper professional terms have always had a difficult feeling. Only the principle of layered refinement, from the initial deeper into a more than ten articles. In this case, it will not encounter too deep professional problems, and you can continue to learn from the entrustment party and the reply, deepen your understanding of the professional field, so that you are always laying in the design, not A professional obstacle that cannot be miser.
In this stage of development, since it has been dealing with your unfamiliar field, I think some auxiliary design tools seem to play the features that should have. During this time, the maximum of me to me is the company's E-mail system, all the unclear issues, and the answers to the problem are turned around. In other words, in the demand analysis phase, it has played an extraction of the exchange of communications and customer needs. So, in this stage, the E-mail system is the tool for me, followed by Excel, I use it to establish a problem tracking chart, and I need to record each of the issues, put the problem result ( It can be divided into clear, not clear, unclear, have not answered), according to these tables, I can understand the core problems in my work, and have a solution to it, improve work efficiency. .
Every refinement of the first layer, I will deliver the issuance of the entrustment party, and when they make it to terminate refinement, after approximately eight layers, the other party believes that the effect has been achieved and confirmed to end. At this point, the analysis work is complete, and the demand analysis of the project is basically successful.
In this analysis, I think the reason for success is mainly the method and tool selection. In interface design, popular auxiliary tools, providing a lot of help in the establishment of demand and logical model, making it more convenient to help yourself clear thinking. The iterative method is selected, and some errors are corrected in the continuous iteration of functional analysis and interface analysis. In the later stage, when the functional demand is mainly, I mainly dependent on communication tools and table tools. This also shows that the auxiliary tool is not the key to the key, demand analysis, should be communicated with customers.
Through this case, I believe that in the demand analysis of software, the importance of the method should far exceed the use of the tool, and should first determine the risk of the analysis, classify the risk, and solve the various risks in different methods, and tools The choice is not only to see influence and fame, but to truly use it for me, you should grasp the essence, that is, what help can help to develop, not only to use it. I think the role of tools in demand analysis is no more than two: First, the actual system and environment model, etc., the second is the demand expression tool. The representatives of the first category are ROSE, and the second type of representative is Word, WPS, Visio et al, in which the communication tool is used in this project, the web browsing and the E-mail service system.
Finally, I still concluded that the tool methods in the demand analysis are just the factors for the success of the auxiliary project, and the real decision factor is still - a "communication with customers".
comments;
