On the selection of software demand analysis methods and tools-thesis 1: Application of Enterprise Personnel Information System

【Abstract]
This article discusses the requirements analysis methods and tools for the enterprise personnel information system project. The purpose of this system is to help the enterprise manage the activities of personnel and personnel in the enterprise. Personnel Information management refers to the entire process from recruitment interview to resignation and retirement, the main activities involved include interview, report, training, promotion, resignation, or other personnel changes, it also includes electronic attendance, calculation and distribution of payroll income, and records related to the use of resources of other companies (such as dormitory, insurance, and document handling ). In addition, the system also involves the personnel information management of enterprises throughout the country, the setting of the enterprise's organizational structure, level and position management, and the HR application and HR requirement report, this forms a truly useful personnel information management application system for enterprises. In this article, we first discuss the main reasons and strategies for using object-oriented methods and tools, and further use a simple example to illustrate the effects of this method and tool, also discussed the necessity of using a variety of tools and methods in demand analysis, and finally briefly summarized the significance and role of choosing the correct tools and methods.
During the project, I worked extensively on system analysis, system design, and database management.
[Body]
The personnel information management system is a practical system with a wide range of applications. However, each enterprise in China has its own system, mechanism, characteristics and different requirements. When developing such systems, system Requirement analysis is an extremely important part. Throughout the analysis process, we have adopted an object-oriented analysis method, because we have been convinced in practice in recent years that this method can more effectively express and describe the real world. To ensure the applicability and scalability of software, it must be closer to the development rules of the real world.
Taking a simple example, we assume that we need to design a system for evaluation of imported talents. Based on our past practices, we will first ask for a relevant evaluation form for imported talents, then, design the corresponding forms and Interfaces Based on Huludao. In the short term, this is simple and practical, but it cannot meet the long-term goal of the real world. This design method is not scalable, because the structure of any evaluation table may change a lot. The object-oriented method can be used to extract table types, table structures, scoring methods, and inheritance considerations. This ensures the versatility, configurability, and maintainability of the software.
During the selection of tools, we chose the popular rational series, including Rational Rose, RUP, and soda. Why did we choose this series of tools? This is based on our views on the purpose of analyzing software requirements. We believe that demand analysis should be able to answer the following key questions correctly:
(1) Have your needs been taken into account in detail?
(2) can users understand or understand what we describe?
(3) Will the analysis be out of touch with the design,
(4) can programmers understand our analysis and design requirements? And so on.
The following are some of the above issues:
(1) obtain the user's requirements in detail.
User requirements can be divided into explicit and implicit requirements. users' preferences tend to focus only on current and obvious requirements. To achieve a comprehensive understanding of the needs, not only rely on effective user conversations and surveys, because the user requirements we face are often somewhat one-sided, using Rational Rose (based on UML) the provided use cases and the combined use of multiple graphs can help us discover the omissions.
(2) enable users to fully understand our representation and what we describe.
Specification for Software Requirement Analysis is usually lengthy and boring, and it is not easy for general users to understand it in depth, which weakens the correctness of the analysis. By supporting Rational Rose in the object-oriented and UML language, you can better communicate with users, so that users can understand the operating methods and even detailed operations of the system.
(3) Link and link the analysis and design phases.
This is an important reason for choosing the object-oriented method and the Rational Rose tool. The system analysis should not only describe the user's needs, but also include the solution, of course, the solution should include design (Program), database and system configuration. We certainly do not want users to get a software that is different from the Requirement Specification Description, it is impossible for programmers to complete an incompetent task. However, we often find this type of scenario in our previous work, because the system analysis and design are out of touch, leading to a lack of design-related issues in the analysis.
The gap between analysis and design is not conducive to the evaluation of the current design, because the analysis is often out of reality, resulting in a lack of evaluation basis.
Because it is impossible to successfully complete the design and make the analysis need to be repeated, it will cause a huge waste and loss. A good tool can make the analysis and design more closely linked, even-a pair. The object-oriented analysis method makes objects relatively independent, which reduces any changes that affect the global structure and avoids the passive situation of full-scale changes due to changes in requirements.
(4) Let programmers understand our design.
A good design should make programmers feel clear and have fewer questions. A lot of questions about the design, coupled with poor communication, will definitely appear in the application environment does not need another software, so the design specification must be clear, image and clear, of course, rational Rose has enough graphics and other forms to make programmers more explicit and even fine-tuned to every statement (in fact, If VB is used, the program architecture may be directly generated ).
(5) Choosing UML may have more reasons.
For example, writing user documents and designing databases require continuity, automatic support, and quality assurance.
Therefore, we chose the above methods and tools.
In the analysis, in the face of the attendance shift problem, the paper card method has been used for attendance in the past, which makes the user a fixed concept for the shift, currently, many attendance software also uses multiple Card swiping methods to form a one-day record. Through object-oriented analysis, we can find that in fact, the daily work records are formed by multiple time periods, and the number of time periods varies by company, with different types of work and departments, each time period may have different attributes. The combination of time periods and time periods can form a shift, which is more suitable for the actual situation and makes it more flexible and scalable. In fact, there is also a relationship between days. At this point, we also found that the basic concepts of period (periods) similar to MRP must be added to attendance and salary, such as attendance period, you can easily set the attendance period for users, which may not necessarily be the same as the calendar year, month, and day.
Rational Rose makes it easier for us to implement the above ideas in the class and further design our highly efficient database.
Of course, it is impossible to use a single tool to analyze the requirements of a medium or large application system. Because society is developing and users' needs are changing, it takes time to grasp users' needs. object-oriented methods sometimes ignore external and superficial requirements, it is not only necessary to obtain key requirements, but more other requirements are often known to users after they are using them. However, it is unrealistic to wait until users use them, as a prototype in the prototype development model, it is also a type of effective method and tool that collects user requirements, describes and interprets requirements.
In our development process, in order to better help users understand our systems and our design solutions, and to make them more oriented and targeted at the meeting, we first use access to develop a prototype, let the user try it out first. In this way, we can better meet user requirements in real analysis and design.
In short, the use of software demand analysis methods and tools has a profound impact on our software development process. The right methods and tools with high performance are selected, this allows our software to better reflect actual needs, improve availability, scalability, and maintainability, and reduce the risks of software projects.
Commentary: (1) It has some special characteristics and clear points of view. (2) The summary is well written, reflecting both the project content and the main points of this article. (3) the example given in this article is simple but practical. (4) The use of various methods and tools is concise and concise. (5) richer content and more in-depth examples will make it more convincing. (6) There are too few descriptions of the entire process of requirement analysis. (This article mainly references the papers of Guangdong yanguoqing and others)