【Summary】
This article discusses the demand analysis methods and tools of "Enterprise Personnel Information System" project. The construction goal of the system is to help the company to manage people and personnel within the enterprise. Personnel information management refers to the whole process of enterprise employees from recruitment interviews to retirement, including interviews, report, training, rising Duty, separation or other personnel changes, including electronic attendance, payability, and related records of other company resources (such as dormitories, insurance, documents, etc.). In addition, the system also involves the management of personnel information management across the country, the organization's organizational architecture setting, level and job management, and human application until human demand reports, thereby forming a person's information management application system that is truly useful to the company. In this paper, the main reason and strategy of selecting object-oriented methods and tools is discussed, further illustrating the effects of this method and tools through a special example, and discussing the necessity of using multiple tools and methods in demand analysis, final Briefly summarize the meaning and role of selecting the correct tool and method.
During the project development, I served as a large amount of work such as systematic analysis, system design and database management.
【text】
Personnel Information Management System is a practical system with wide application, however, my country has its own system, mechanism, characteristics and different requirements; when developing such systems, system demand analysis is an extremely important ring. In the entire analysis process, we have adopted object-oriented analysis methods because we have convinced that this approach can be more effectively expressing and describing the real world in recent years. Software should have applicability and scalability, it must be closer to the law of the real world itself.
From a simple example, assume that the design requires a system that introduces talent assessment, according to our past practice, first request to provide us with a relevant introduction talent assessment table, then design the corresponding form in the gourd painting With the interface. In the short term, this is simple and practical, but it does not meet the long-term goals of the real world. This design method does not have scalability because there may be many changes in the structure of any assessment table. Using object-oriented methods, you can extract elements of the table, table structure, score method, and various aspects of the inheritance, so that software can be guaranteed, configurable, and maintainability.
During the selection of tools, we have chosen the Rational series, including Rational Rose, RUP, SODA, etc., why do you choose this series of tools? This is based on our views on the analysis of software requirements. We believe that the analysis should correctly answer several key issues:
(1) Does the user's demand is detailed?
(2) Can users understand or understand what we describe?
(3) Analyze if it will segment with the design,
(4) Can programmers understand our analysis and design requirements? and many more.
The following is a brief description of the above problems one by one.
(1) Acquisition of users in detail.
User needs can be divided into explicit demand and hidden demand, and users' tendency often take into account current and obvious needs. To achieve the comprehensiveness of demand, it is not only to rely on effective user conversations and investigations, because users we face often have some side, using Rational Rose (based on UML), and multiple pictures Union use, you can find out what to miss.
(2) User can fully understand our representation method, can truly understand what we described.
Software demand analysis specifications are usually lengthy and boring, and the general users are not easy to understand, which weakens the correctness of the analysis. By supporting an object-oriented and UML language, it can communicate with users, allowing users to understand the operation of the system and even details of the system. (3) Contact and penetrate the analysis and design of two stages.
This is an important reason why we choose object-oriented methods and Rational Rose tools. The system analysis should describe the user's needs, but also the solution, and the solution should of course include design (program), database and system configuration. We certainly do not want the user to get a software that does not have the same requirements, and it is impossible to request a programmer to complete an indispensable task. However, we often discover such circumstances in the previous many work, as systematic analysis and design are out of the analysis, causing a one-to-analyzer that is related to the design.
Analysis and design is not conducive to the design of the description of the current instructions, because analysis often will be separated from reality, leading to the lack of assessment.
Because it is impossible to successfully complete the design, it will cause huge waste and loss. A good tool allows the analysis and design more closely, even - one correspondence. Object-oriented analytical methods reduce the relative independence between objects, reducing any changes in global changes, avoiding passive waves due to changes in demand.
(4) Let the programmer understand our design.
A good design should make the programmer feel clear, less questions. A lot of designs plus communication is not smooth, and there will be another software that is not needed in the application environment, so design specifications must be clear, image and clear, of course, Rational Rose has sufficient graphics and other forms, energy Make the programmer more clear, even fine to each statement (in fact, if you use VB, the programming architecture can be generated directly).
(5) Selecting UMLs may have more reasons.
For example, the writing of user documents, database design, we need to do continuity, automated support and quality assurance.
Therefore, we choose the above methods and tools.
In the analysis, in the face of the problem of attendance, the user has formed a fixed concept because of the use of a paper card, and many attendance software now use multiple credit cards to form a day record. Object-oriented analysis, it can be found that in fact, it is formed by a number of time-based records, and how much is in various companies, each type of work is not the same, and each time period may have different attributes, time periods The time period combination can be formed as a class, which is more suitable for reality, making it more flexible and more scalable. In fact, there is also a relationship between heavens and days. At this point, we have found that we must add the basic concepts of the period (Periods) similar to the MRP and the salary salary, such as that can be called the attendance period, allowing users to set the intermedial period, It may not be the same as the natural day and the day.
Rational Rose makes us more convenient to implement the above ideas on the class, further designing our high efficiency database.
Of course, it is impossible to use a single tool to complete the demand analysis of a large-scale application system. Because social development, users' demand is also changing, how to grasp the needs of users is time, object-oriented methods, sometimes ignore the external requirements, not only to get critical needs, others Many demands often wait until the user knows after use, but the user is not realistic, as the prototype in the prototype development model is also a class of comparable effective methods and tools that describe user needs, describing and explaining demand. During our development, in order to better let users know our system and our design, let users get more direction and targeted on the meeting, we first use Access to develop prototypes, allowing users to try first. In this way, we can more in line with users in real analysis and design.
In short, the software needs analysis method and tool use, the impact of our software development process is far-reaching, selecting high-efficiency correct methods and tools, allowing our software to more correctly reflecting real demand, more availability, scalable Sex and maintainability; reduce the risk of software projects.
Comment: (1) Write some characteristics and distinct views. (2) Abstract is written, reflecting the contents of the project, and is also summarized. (3) Although the examples mentioned in the article are simple, they are actually practical. (4) A variety of methods and tools are described in the narrative. (5) The content can be more abundant, and more in-depth examples can also increase more, it will be more convincing. (6) There is too little description of the whole process of demand analysis. (This article mainly refers to the papers of Guangdong Yan National Day and others)
