Project requirement analysis Conceptual requirement analysis refers to a complex process of understanding user requirements, reaching an agreement with customers on software functions, estimating software risks and evaluating project costs, and finally forming a development plan. This is not quite the same as what I experienced at Microsoft. Most of Microsoft's demand analysis is evaluated by marketers and user support groups, which is understandable because the nature of the company is fundamentally different. In this process, users are really in a dominant position, and requirements analysis engineers and project managers are responsible for sorting out user requirements and laying the foundation for subsequent software design. After the requirement analysis stage, it is required to obtain: 1. SRS document (system requirement specification); 2.DRM documents; 3. Acceptance plan. Broadly speaking, requirements analysis includes a series of requirements engineering such as requirements acquisition, analysis, specification, change, verification and management.
Demand analysis in a narrow sense refers to the process of demand analysis and definition. First of all, why do we need demand analysis? Requirements analysis is to analyze what the needs of software users are. If a lot of manpower, material resources, financial resources and time are invested, but no one wants the developed software, then all the investment will be in vain. If you spend a lot of energy developing a software, but in the end it doesn't meet the requirements of users, then you should redevelop it. This kind of rework is heartbreaking. (I believe everyone knows) For example, users need a linux software, but in the early stage of software development, you neglected the running environment of the software and forgot to ask the user this question, taking it for granted that you were developing windows software. When you worked hard to complete the development and submit it to users, you found something was wrong. At that time, you were crying and died without finding a piece of tofu.
Demand analysis is very important because it plays a decisive, directional and strategic role. It plays an important role in software development. Everyone must pay enough attention to demand analysis. In the development of large-scale software systems, its role is far greater than programming. Second, the task of demand analysis In short, the task of demand analysis is to solve the problem of "what to do", that is, to fully understand the needs of users. And accurately express the accepted user needs. Third, the process of demand analysis The work in the stage of demand analysis can be divided into four aspects: problem identification, analysis and synthesis, specification formulation and review.
problem recognition
It is to understand the software from the system point of view, determine the comprehensive requirements for the developed system, and put forward the realization conditions of these requirements and the standards that the requirements should meet. These requirements include: functional requirements (what to do), performance requirements (what indicators to achieve), and environmental requirements (such as model and operating system). ), reliability requirements (failure probability), safety requirements, user interface requirements and resource usage requirements (software operation is
analysis and synthesis
Gradually refine all software functions, find out the relationship between system elements, interface characteristics and design constraints, analyze whether it meets the requirements, eliminate unreasonable parts and increase needed parts. Finally, the detailed logical model (what to do) of the system to be developed is given by synthesizing the system solution.
Formulate specifications
In other words, the document describing the requirements is called the software requirements specification. Please note that the result of the requirements analysis stage is the requirements statement (it seems that the soft exam passed this question), and it is submitted to the next stage.
evaluate
Evaluate the correctness, completeness and clarity of functions and other requirements. Only after passing the evaluation can the next stage of work be carried out, otherwise the demand analysis will be carried out again. There are many methods of demand analysis. Only the prototype method is emphasized here, and other methods, such as structural method and dynamic analysis (I don't think it is necessary for beginners to delve into these methods, but I have never used them) are not discussed here.
Prototyping is very important (it is a common knowledge point such as soft testing). Prototype is an early running version of the software, which realizes some or all functions of the target system.
Prototype method is to build a rough system as soon as possible to realize part or all of the functions of the target system, but this ......
How to write software requirements analysis?
1. Introduction
Writing purpose 1. 1: The purpose of writing this document is to further customize the details of software development, so as to facilitate the coordination between users and developers. The readers of this document are mainly the managers of the project entrusting unit, hoping to make this software development work more specific.
1.2 project background
1.2. 1 Project Entrusting Unit: * * Company
1.2.2 Developer: * * Company
1.3 definition
1.4 reference
2. Overview of tasks
2. 1 target:
& lt 1 & gt； Decision support: provide the required reports and documents in time according to the company's requirements, and prompt the leaders of various departments on sales and procurement in time.
& lt2> Improve efficiency: Use software for management to avoid mistakes and delays in manual management, so as to achieve efficient management.
2.2 Operating environment:
& lt 1 & gt； Hardware: Pentium processing chip
Compatible graphics card with 1 MB memory.
256 colors, compatible with 800*600 monitors.
Standard compatible printer
& lt2> software: WIN95 operating system
2.3 Conditions and restrictions:
Computer for programming
Completion date: July 2000 +0
No funds are available.
3. Data overview
The data flow chart is as follows:
3. 1 static data: including the system login password, the location of each database and the original data analyzed by the system.
3.2 Dynamic data: including various display data, user login information and system time in each database.
3.3 database description:
Personnel management database: personal details of company personnel, including file information.
Sales management database: the sales records of the day and previous sales statistics are used for sales analysis.
Financial management database: a detailed list of the company's internal accounts and revenues and expenditures.
Technical management database: detailed records (including documents) of various technical documents required by the company.
3.4 Data dictionary:
& lt 1 & gt； Description of data stream entry:
1. data stream name: login information
Source: user input
Destination: the internal inspection part of the system.
Composition: user name and password
Cycle: Enter once every time you log in.
2. Data stream name: login result
Source: system
Target: users
Composition: return information
Cycle: Return once every login.
3. Data stream name: enter modification information.
Source: user
Destination: system judgment part
Composition: It varies according to the content of each database.
Cycle: Depending on user input.
4. Data stream name: feedback information
Source: system judgment section
Target: users
Composition: character data sent back after system judgment.
Cycle: Depending on the current information of the system.
5. Data stream name: identification information
Source: internal inspection part of the system
Destination: system judgment part
Composition: identification information of each database in the system.
Cycle: the user enters a cycle at a time.
6. Name of data stream: Processing information
Source: system judgment section
Where to go: each database processing part
Composition: read/modify identifiers and read/modify variable names.
Cycle: the user enters a cycle at a time.
7. Data stream name: read and modify
Source: system judgment section
Destination: Every database in the system.
Writing: read/modify the logo, read/modify the content.
Cycle: the user enters a cycle at a time.
& lt2> data file entry description:
1. data file name: personnel data.
Description: Store personnel information.
Composition of data file: various information of personnel (mainly string type)
2. Data file name: sales data
Description: Stores current and previous sales records.
Composition of data file: sales information.
3. Data file name: financial data
Description: Store financial management information.
Composition of data file: financial management records.
4. Data file name: technical data
Description: Store the information of technical documents used inside the company.
Composition of data file: name and content of technical file.
& lt3> Description of processing logic entry:
1. Processing name: inspection
......
How to write the analysis of project objectives and task requirements?
Project objective and task requirement analysis = project objective and task. Write down your goals and tasks.
How to write the project demand report?
Listening to Tang's When Will Customer Demand Stop profoundly reveals the root of this problem. Demand analysis is not only to get the customer's demand, but more importantly, it also needs to analyze, understand the details and consult with customers on the details to get the most detailed information. Customers can only provide you with what they think are functional requirements, and many problems are beyond their consideration. If the project undertaker simply designs and plans according to the functional requirements without analysis, the final system will be difficult to fully meet the customer's business process. At this time, nature needs to change, which is regarded as a change in demand. In fact, it is all caused by insufficient analysis. It was not until the system came out that the problem was discovered, and such a system itself was inherently inadequate. After listening to Tang's words, I was deeply touched: "In fact, the problem lies in the beginning. Customer demand is only a part of software demand analysis. Although it is an important part, we should not just remember customer demand, but analyze customer demand. " There is a contradiction in the customer's demand itself (this contradiction refers to a logical point of view), and the customer himself does not know it. Only when analyzing and designing will we analyze the contradictions here and these problems. In the project requirements analysis report, when you understand the customer's needs, don't just use your head to say "I C". In fact, the superficial business may have more details, and you need to ask customers. Only if you ask more questions, the final demand will be the most specific and the project will be smoother. And there are many questions, all in your rhetorical question. Only when customers begin to think about problems that they haven't thought about before will customers find reasonable needs for you. Some people will find it too much trouble to understand customer needs in this way. As for some technical problems, you should also tell your customers. Don't think that the customer doesn't care about your technical details, but if you explain it to him, he will try his best to understand. The customer's demand itself is endless, because they are changing themselves, but when your initial analysis is reasonable, the subsequent changes will naturally change, and I believe the cost will not be so great. This actually reflects the expansibility of the system. Demand analysis is a process of communication between project proponents and undertakers. One party is the user of the system, and the other party is the manufacturer of the system. In the process of system manufacturing, only when both parties cooperate with each other and design the system together can the requirements of use be finally met. The customer is familiar with the business and has a very clear understanding of the business process, but does not understand the description of the software requirements. What they can provide is only the function they want to achieve in the end, but the business process involved is very complicated. After we get the customer's demand, we make a preliminary design according to the function and process, build a business flow chart, and then let the customer review and propose the mistakes in the business process for modification. This kind of back-and-forth communication can finally get more comprehensive requirements and reduce later revisions.
How to do demand analysis
With the continuous development of technology and the increasing demand of users for website functions, the design of website projects can no longer be simply realized by static Html files. Compared with previous years, the design and development of website project is more and more like a software project and more complicated. The design and development of website project has entered an era that needs to emphasize process and division of labor. Only by establishing a standardized, effective and robust development mechanism can we meet the changing needs of users.
Website project management (WPM) is Web-based project management, that is, project design and management based on web application framework. Web applications include browser, network and Web.
Key disciplines such as servers are mainly embodied in website design and web application development (such as information websites, online stores, virtual post offices and customer relationship management) with browsers as clients. ) and other project management.
According to the author's experience, website project management can be divided into the following six stages to control:
1. Requirements analysis and change management
2. Project model and business process analysis
3. System analysis and software modeling
4. Interface design, interaction design and program development
5. System testing and documentation
6. Customer training, technical support and after-sales service
It should be noted that although these stages are continuous to some extent, they are not completely separated. For example, requirements change management, testing and documentation all run through the whole project process, and many tasks are carried out alternately or simultaneously.
(A) how to do a good job in demand analysis and change management?
The communication between sales staff and customers and the writing of demand analysis report are the basis of project development. The project focuses on the needs of customers, rather than adapting to the needs of technology.
One: Let customers speak freely and list all their needs.
Let users explain all the ideas as clearly as possible and list all the requirements without omission. At this time, don't be afraid to "seduce" the potential needs of customers, increase the workload of design and development, and be dragged into the quagmire by the endless changes of future customers. We should directly and clearly list the problems and needs of customers one by one, put aside organizational induction and analysis, and accurately record the most primitive and complete needs of users to complete the first step.
Obviously, if the customer's demand is incomplete, unexpected changes may occur at any time, and even this change will destroy the model and structure that has been made, then the project is doomed to failure from the beginning; For example, all the functions of the site have been realized, and there is no problem with the local test, but you don't know that the customer's system has to bear 1 10,000 independent IP access every day, and what you thought was remarkable was the access flow of 1 10,000 independent IP access. A slightly experienced developer will understand that this design is a disaster, and all application servers, databases and programs have to be redeveloped!
Second, analyze the potential demand through the phenomenon.
Many times, customers are not professionals, and we can't expect them to help us sort out the key points and technical difficulties in endless descriptions. This requires us to analyze, summarize and sort out for customers, especially in places where customers don't talk much but have great technical difficulty and intensity.
The customer's concept of requirements is often vague, and the requirements given in many cases are general and difficult to control. This requires business personnel to help customers sort out and analyze after listening to the detailed instructions of customers, and at the same time predict the possible changes of customers in the development process and the potential requirements that may be modified and upgraded in future applications.
For example, when designing an office automation system for customers, it may be necessary to reserve channels for customers to interact with their business departments in the future; When designing the mail system, we should take into account the possible need for an advertising management server; When designing online electronic stores, we will increase the statistical analysis of inventory products in the future, and so on; Due to the consideration of time and financial resources, customers can usually accept the development process implemented in stages. When analyzing the requirements, it is not only to make the project development smoother, but also to lay the foundation for further business in the future. ......
How long does it usually take to make a plan and project demand analysis?
Many older generations in China simply don't pay attention to this point. But abroad, a small number of actual combat writing needs have begun. Because they always think that demand is very important. Before every project, there is a messy demand analysis, like a grass. Do it once in a while and change it. Change the requirements, then, the original framework and coding will also change. And my classmate, although doing the demand for more than a month, did it smoothly according to the demand. My question is: no matter how big or small the project is, we should write down the requirements clearly before doing it.
How to write the java project requirements document?
Requirements documents are generally divided into two categories.
Demand research report
Demand analysis report
Research report: it is the original demand of users recorded, which can basically be regarded as the original record of communication with users.
Analysis report: It is the result of classified analysis of research reports. A relatively comprehensive document generally includes the following contents:
Project background
Project objectives
scope of project
User characteristics
Relevant technologies, specifications and standards, etc.
Related constraints
User's organizational structure, role, etc.
Function points required by users, priorities of these functions, business processes, functional features, special requirements, etc.
In short, the next stop of the demand analysis report is the designer. When the designer sees the demand analysis report, he will know which function points, permission design and process design the system should contain, which can be obtained directly from the demand analysis report.