Enterprise information management system
User Demand Report Writing Guide
Document properties:
Document Number Document Version V1.0 Confidential Level Population Review Approved
Modify record:
Date modification chapter Modification Type * Modify Description Modify Version 03.8.10ALLA Create Zhang Wei 1.0
* Modify type is divided into A - Added M - Modified D - DELETED
guide
purpose:
"User Demand Report" is the output of the demand acquisition phase. The purpose of "User Demand Report" is a faithful description of user needs. It is the basis for the definition of demand specifications and project planning, but also the basis for the user's acceptance.
This document is a preparation guide for the User Demand Report.
content:
Document answer three questions:
What is the user's application background?
What is the current situation of the user?
What kind of application does the user need?
Methods and points:
1. Important activities in demand acquisition phases are demand research, the content of this document comes from the results of demand research.
2. For product items, this document comes from the results of user group adjustment to the product.
3. Documents use the language description of the user's domain to ensure that users and analysts can understand.
Document organization
The first part of the document is an overview, focusing on the application background of the user. The user's "purpose and target" of the user is the focus of this section, which should reflect the user's overall expectations and vision. "User Introduction" part should portray the user's application background from multiple dimensions. A unified term should be established between the project and the user to facilitate communication between the two parties, and the business glossary can also be the prototype of the data dictionary. References and related documents should be listed in the documentation, as well as their sources to facilitate users.
The second part of the document is a business description, focusing on the user's business process description. Before introducing business processes, first introduce the user's organizational structure and post definition, organizational structure, and post definitions are business process executors, and it also reflects the business philosophy and management ideas of the company. It has a good help for understanding business. . The document, the book, and the report are the carrier of business processes, which is an important basis for designing data entities in the analysis phase. Existing business processes and business handling modes often have various problems, and some of these issues can be solved in new systems, and some are not within the scope of new systems. Documents should also record various changes that may occur in the business in order to make elastic design.
The third part of the document is business needs, or functional requirements, which records which specific issues that users expect new systems can solve. They may be optimized for existing processes, and it is also possible to build some new business processing processes with the use of new systems. In any case, the user should be faithfully record the most direct business needs of the new system and the initial motivation.
The fourth part of the document is a non-functional requirement, from the system's appearance, ease of use, performance, security, external interface, etc. to give other needs other than business needs.
The fifth part of the document is assumptions and constraints.
1 Overview
guide
purpose:
Introduce the application background of the system.
content:
l The basic situation of the user.
l Users to the project's overall requirements and expectations.
l Business terminology.
l Resources.
l Related documents.
method:
Refer to the contents of each section.
1.1 User Introduction
guide
purpose
Introduce the basic situation of the user.
content
1. The nature of the user unit, such as state, private, foreign capital, joint venture, joint-stock enterprises, etc.
2. The industry of user units, such as manufacturing, textile, energy, transportation, pharmaceutical, finance, cultural education, health, government, etc.
3. The size of the user unit, including the number of employees, turnover, etc.
4. The location and layout of the user unit, including the geographical distribution of parent and molecular companies.
5. Products and Services species, briefly introduce the types, customers and characteristics of user products and services.
6. Management mode and management ideas of user units. 7. The approval method of the user unit.
8. The computer application foundation of the user unit, such as the number of computer desks, existing software systems, and the number of computer maintenance personnel.
......
Method and key points
1. The basic situation of the user can be obtained through the user's publicity information, media data and medium-level interviews.
2. Description of the user's basic situation as simple as possible, accurate, multi-purpose digital description.
3. Avoid public users to confidential information, so user comments should be solicited before texture.
4. For different types of items, the description of user information should be focused. For example, for financial accounting systems, users 'industry and accounting methods may be important, and for a manufacturing system, users' product characteristics and production methods may be more important.
5. For product development projects, the characteristics of product user groups are needed here.
1.2 purpose and goals
guide
purpose:
Revealing user investment and development of the true intent of this system, reflecting the true value of the system to the user.
content:
The project is summarized in the basic intention of the user investment system; the project goal is a specific description of the revenue of the project's purpose.
The goal of the project project is, for example,:
1. Through ..., it will increase the production capacity XX%.
2. Through ..., thereby increasing the ability to serve customers.
3. Through ..., complete artificial difficult problems.
4. Control the weak link in the XX business, reduce the cost XX%.
5. Through ..., reduce the investment of manual and equipment, reduce cost XX%.
6. Through ..., improve the processing speed XX% of the XX service.
7. Through ..., improve the transparency of business processing.
8. …...
method:
Project objectives and objectives are usually obtained by interviews on high-level - especially decision makers.
The project is summarized in the basic intention of user investment development. The project goal is to refine the detailed description of the purpose. Project purposes should be clear and summarized; project objectives should be clear, measurable, and achievable.
The goal of the project can be gradually refined, and the corresponding relationship is finally established with the needs of the system. It is recommended to numbered the details of the refinement to distinguish. It is recommended to establish a demand and refinement of the target of the target to check if the system function covers the target's goal. If the goals have been refined, it is recommended to manage.
Avoid using a word sentence such as "development of a system that makes users satisfactory", and it is often the main source of project risks.
1.3 business terms
guide
purpose:
Ensure that readers can accurately understand the concepts, terms and abbreviations of this document.
content:
Including business terms, such as safe stock, procurement, JIT, BOM, etc.
Includes computer terms, such as distributed, concurrency, and the like.
Methods and points:
Focus on important, frequent, uncommon, easy to make ambiguous nouns, terminology and abbreviations.
If more terms are more, the terminology is recommended.
For nouns, the interpretation of terms and abbreviations, try to use authority explanation, as indicated as much as possible.
Add chart auxiliary instructions if necessary.
1.4 Reference
guide
purpose:
Describe the reference information referenced in this document, making it easy for the reader to see.
content:
Business contract.
2. Book.
3. User requirements questionnaire.
4. Business information in the user's domain.
5. National Standards and Industry Standards.
6. ... ...
Methods and points:
Each file, the document must have title, index number or file number, release, or date, and publishing unit.
1.5 related documentation
guide
purpose:
The auxiliary material of this document is recorded.
content:
1. User book form.
2. User documents.
3. User report form.
4. ... ...
Methods and points:
Explain the auxiliary material of the user's demand report, if it is not possible.
2. User Business Description
guide
purpose:
The content of this chapter focuses on the business processing method and process of users being used.
content:
1. User's organizational structure and responsibilities.
2. The user's position is defined.
3. The user's business process.
4. Users' documents, books, and reports.
5. Problems exist during user business.
6. Changes that may occur during user business.
Methods and points:
Describe the existing business processing methods and processes of the user, to help analysts better grasp the needs, and better understand the characteristics of the user. These business processes and business processing methods are not the process of processing and methods of future systems, and also represent the range of future systems. The future business system will define a business management system that combines computer application technology based on the business needs of users to achieve the overall purpose and objectives of users.
2.1 Organizational Structure and Responsibility
guide
purpose:
Describe the user's organization structure and responsibilities.
content:
Organization structure diagram.
2. The list of departmental responsibilities.
Methods and points:
Organizational structure and responsibilities can be obtained through interviews in the human resources department. For small-scale companies, you can get through interviews with major operators.
"Organization" in the user unit reflects the user's business philosophy and management ideas as the nodes in the information flow in the business process. The organizational structure understands the business process for analysts, and determines the system boundaries play a good help. It is one of the basic works in the demand acquisition step.
It is recommended to describe the organizational structure of the user with the list of organizational structural maps and departmental responsibilities. It is recommended to describe the organizational structure with a tree structure diagram, which is recommended to use the list description of the department duties.
2.2 Post definition
guide
purpose:
Describe the job name and responsibility of the user involved in the system.
content:
1. Post definition list.
2. Other explanations.
Methods and points:
Like organizational institutions, post definitions are also the basis for analytical personnel understanding corporate business processes and delineating demand boundaries. Post definitions are also one of the basic works of demand acquisition.
Post definitions can be obtained from the interviews of the human resource department and the business unit.
If the position definition is less, it is recommended to use the form of forms directly using the form. If the position definition content is more, it is recommended to use the list as a general, summary description, and use text as a detailed description.
The user's position is also included in the system management personnel of the computer system.
The user's position definition should be linked with the department, and the position definition can be described in accordance with department classification.
2.3 Overall business process
guide
purpose:
Describe the user's business processing process from a high-level perspective.
content:
1. Overall business flow chart.
2. Overall business process description.
Methods and points:
The overall business process is derived from the summary and summary of the specific business process, and the overall business process needs to be repeatedly discussed, and constantly modify the formation.
The overall business process is to summarize and summarize the various business processes collected in the survey activities, and the general, summarized processes are obtained. It is very likely that the user itself doesn't have this picture. It is just that this concept is in the mind. Once we sort out this process once the user's help, we will inevitably understand the business to lay a solid foundation for the future.
The overall business process is too specific, too complicated, can be used in intuitive, summary, with simple, accurate text descriptions best.
2.4 Specific business processes
guide
purpose:
Describe the specific business processing procedures for the user.
content:
1. Business process list. 2. Business flow chart.
3. Business process description.
Methods and points:
The specific business process is derived from the interview of the grassroots business unit.
It is recommended to list the process list in the form of a list.
If there are more processes, it is recommended to classify the process.
You cannot describe the text in the flowchart.
It is recommended to describe business processes using straight flowcharts.
2.5 unusual, books, reports
guide
purpose:
Level the documents, books, and reports used by the user.
content:
1. A list of documents, books, and reports.
2. Documents, books, report sections (optional).
Methods and points:
1. Unicel, book, report is the carrier of information in the user system, which is the basis for performing system requirements analysis.
2. Sources of the document, books, and reports are grassroots business units.
3. You can classify documents, books, and reports.
4. It is recommended to numbered documents, books, and reports for managing.
5. If the document, the book, and the report is more, it is recommended to use the original material as an attachment.
6. For documents, books, and data items in the report, there should be a detailed description. These instructions include:
source
Types of
length
Decimal accuracy
Calculate relationship
Help rules (such as rounding, rounding, etc.)
......
2.6 Problems in existing systems
guide
purpose:
Problems or bottlenecks existing during existing business processing.
content:
1. Large business, and handling staff tasks.
2. There is a management vulnerability to give people a machine.
3. Find the data speed too slow.
4. The workload of the report on the end of the month is large.
5. Existing system is complex.
6. ......
Methods and points:
The problem and bottleneck of existing business systems are derived from interviews with users and roles of users. Since the information is derived from multiple calibers, it may be very messy and may have contradictions. Demanders should have extensive investigations and analysis to identify problems that have truly impact on user business goals, remove the misunderstandings and deviations from their own perspective.
It should be noted that these problems can be solved from future systems, and some can be solved with the introduction of computer applications, and some must be solved from the perspective of management specifications. From the perspective of investigation, all of the above problems and bottlenecks should be recorded.
2.7 Future possible changes
guide
purpose:
Record the business that may change in the future.
content:
It is prone to withdrawal and new sectors.
A process that is prone to changes.
It is easy to change the way.
Documents and reports that are prone to change.
......
Methods and points:
Changes in companies are eternal, especially growing SMEs. The surveyors must pay attention to those that may cause system changes in the research process, including the possibility of changes, and the frequency of changes.
3. User business needs
guide
purpose:
Use text to describe the specific problems that the user wants to solve. It is an important basis for defining use case and demand modeling.
content:
Used to directly record from the user's needs.
Methods and points:
The user should be faithfully record the most direct business needs of the new system and the initial motivation. These needs may be solved in a new system in a new system or may not be within the functional range of the new system. The functional range of the new system will be delineated in the demand specifications. Here is just a need for a user in a field.
The user's business needs can be described directly using a text description. (Program Statement)
The content of business needs comes from interviews with users, posts and roles.
For complex systems, it is recommended to give high-level business needs and then gradually refine, decompose to form more specific business needs. To facilitate management, you should minimize the particle size as much as possible.
It is recommended to numbate the requirements.
For easy trace, it is recommended to record the source of demand, including the sectors proposed, and the positions involved.
Sample: Wimbledon Tennis Competition Management
Below is a case from Java architect certification training courses:
The purpose of this system is to carry out the event management of Wembleton Tennis Open.
The competition is divided into men's singles, women's singles, male doubles, women and doubles and mixed double competitions.
The computer system must save the schedule before the game, including the date, time, venue of each game. Add the list of players and referers before each game. Add scores and game time after the game. To confirm that the double player comes from the same team.
Computer systems need to save each participant name, nationality and ranking.
The competition officially entered the basic information and events to the computer system.
The reporter can query the schedule and score through the computer system. The reporter is arranged in a dedicated room.
4. Non-functional demand
4.1 Demand
guide
purpose:
Describe the appearance of the product desired by the user.
content:
1. Display mode, such as 1024 * 768 or 640 * 480, etc.
2. Display style, such as graphical interface, console interface, web interface, etc.
3. The appearance is tendency, such as: appearance, the appearance is authoritative, the appearance is compatible with XX products, rich in color, attractive to children, and the product will be very expensive, and so on.
4. The appearance intent, such as: demand interactivity, demanding exciting, requires highlighting XX, etc.
5. ......
Methods and points:
The user's demand for the appearance of the product is often blurred, so it is often necessary to analyze the advice of the specific sample to seek the user, from the user's feedback to the real needs of the user's appearance.
4.2 Easy to use demand
guide
purpose:
Describe the specific requirements and expectations of the user's ease of use.
content:
1. Do you support multi-language.
2. Whether to support people with disabilities.
3. Whether there is a person who does not have computer operation experience.
4. The extent of the product on the training.
5. Understand whether the product needs a certain background knowledge.
6. ......
Methods and points:
Easy to use, it can be understood as three specific content: easy to understand, easy to operate, easy to learn.
The user's ease of use can be obtained by analyzing the user application background.
4.3 Performance requirements
guide
purpose:
Describe the specific requirements and expectations of users.
content:
1. Business processing time, such as: After using computer management, you will require a user payment service within 50 seconds.
2. Report query time, such as: After using computer management, the transaction report query time does not exceed xx seconds.
3. Precision of processing, such as: Require data processing accuracy to XX bit after decimal point.
4. Supported concurrent access quantities.
5. ......
Methods and points:
Try to explain the specific, quantized indicator.
4.4 Security Demand
guide
purpose:
Describe the specific requirements and expectations of the user's security.
content:
1. System permissions.
2. Security assurance for data transmission.
3. Database access control.
4. ......
Methods and points:
4.5 External Interface
guide
purpose:
Describe the interfaces with other systems.
content:
1. Possible external systems such as: monitoring systems, control systems, bank settlement systems, anti-counterfeiting tax control systems, government network systems, etc. 2. Interfaces with special peripherals, such as CT, magnetic resonance, teller machine (ATM), IC card, inventory machine, etc.
Methods and points:
All external interfaces, interface standards, and specifications should be listed here.
4.6 Others
guide
purpose:
Describe the other non-functional needs other than the above non-functional requirements.
content:
1. The size of the transaction.
2. Under normal conditions and peak conditions, the total number of services is required.
3. Special precision requirements during input, processing, transmission, and output.
4. Portability requirements.
5. Maintainability requirements.
6. Cultural policies and legal requirements.
7. ......
Methods and points:
5. Assumptions and constraints
guide
purpose:
Assumptions and the convention are expected to describe the system risk.
content:
1. Schedule, including the phase progress requirements of the system;
2. Funding restrictions, whether there is investment quota limit;
3. Running environmental restrictions, including platform, architecture, equipment requirements;
4. Training needs, including training, content requirements, etc .;
5. Promote demand, including the scope of promotion, special requirements in the promotion process;
6. Limits, regulations and policies;
7. Conditions and restrictions on hardware, software, operating environment, and development environment
8. Information and resources available;
9. ……
Methods and points:
