Demand analysis

Turn  https://www.cnblogs.com/syw20170419/p/8640609.html

Case  "Mining Management Value: Enterprise Software Project Management combat" a needs analysis process 2.3

1. What is the testing requirements analysis

 

        Requirements Analysis: Writing of the requirements specification, analysis of business needs at the time of writing, according to the business needs to be written

                                                                                                               

         Testing Requirements Analysis: 1, the feasibility analysis needs

                              2, test points Analysis: The needs analysis split into a number of feature points

 

         Analysis of test requirements to get the demand ---- ----- write test plans / write test cases executed test ----- ----- preparation of test reports

 

2, needs analysis test point

 

            1, functional requirements:

                      The system occupies about 80% of the content, the main software. The dominant point needs analysis

 

            2, business needs:

                       Implicit demand, the software does not directly see all of the business show, through what steps into what page, what page shows what kind of content, analysis of business

　　　　　　 Importance: the actual business of each business system to solve the problem, to what purpose, business performance in function, relying on the performance of the business function.

 

             3, performance requirements: there is a clear demand for properties (explicit demand), such as Taobao 0:08 5:07 assigned to user 500, no performance requirements (implicit demand)

 

              4, environmental needs: the needs of the operating environment analysis system

 

              5, security requirements: User login (rights), password encryption, non-sensitive sectors, implicit demand

 

              6, interface requirements: user interaction, UI

 

               7, reliability requirements: data accuracy during operation the risk of error, software, process integrity

 

3, the test requirements analysis skills

 

            1, familiar with the needs, clear test range: Define the test range

            2, the definition of the process: the process is to determine what it was like to analyze the business, the core function detects the first test

            3, the second communication: communication and demand Analyst / Product Manager

            4, refinement: software process, the distinction between core and non-core module

            5, according to the scenario generation process model

            6, in conjunction with test data design scene: the means test is based are reasonable and effective. Reduce unnecessary waste of time

 

Testers when reading or watching the requirements document demo, to be able to check it back the following questions:

　　1, the system functions to achieve what, what these functions are input, output, operation step Yes.

　　2, the system business process, business rule is clear, whether it be performed in a normal flowchart, there are no missing nodes.

　　3, the user's system involves what, users have what kind of privileges.

　　4. What are the system requirements for non-functional? These requirements describe is complete, there are clear indicators.

　　5, the operating environment of the system described is complete, according to whether the environment can set up a test environment.

　　6, a typical user operating behavior What? What common feature is that the operation and long.

　　The answers to these questions above If you can not find the answer in the document or demo, you need to communicate with the project manager to understand the information.

　　When the project is tight, you can not write requirements documents, our approach is : from the Internet to find a similar project with the sort some information, we need help to understand the business, and then organize meetings to discuss project managers what made the system to which features implementation, testing personnel to fully participate in the exchange, to express their own understanding of the situation, not just passively listen.