Software engineering best practices - project requirements analysis

Have you ever met such a client （ Yes , And it's very common ）

1、 My need is just one word ,XXXX

2、 Don't you understand enough

3、 You need to dig and analyze by yourself , How could I know

4、 You should learn from the Internet , See what others do , Just copy it

After analysis （ Customers become masters of understanding ）

1、 You should do this .

2、 It shouldn't be , This should be changed .

3、 This thing you copied , Not enough soul , To add this feature .

----------------------------------------------------

technological process ：

1、 Original requirements

2、 Demand collection research （ Benchmarking 、 questionnaire 、 interview 、 Brainstorming, etc ）

3、 Outline design （ relevant UML chart ）

4、 Prototype sketch design

5、 Customer confirmation 《--》 Repair and adjust the prototype , loop

6、UI beautify

7、 Detailed design （ Interface 、 surface 、 Class etc. ）

8、 code

9、 test

....

1、 Original requirements

Provided orally or on paper by the customer

2、 Demand collection research

2.1 Benchmarking ： Applicable to industry reference , For example, building a real estate system , Then you have to refer to the famous system in the industry

2.2 questionnaire ： For customer facing groups , For example, do some online 、 Offline questionnaire distribution , Collection, etc

2.3 interview ： It is applicable to the situation that the requirements are in the hands of several key relevant personnel or the final decision-making power is in the hands of the customer , What the customer doesn't know

2.4 Brainstorming ： Meeting and collision through the team , Come to the conclusion , formation

3、 Outline design

Such as ： flow chart 、 Activity diagrams 、 If you don't understand the use case diagram, please Baidu , You can use this to draw online UML chart  https://www.processon.com/i/56c6d9abe4b0362f22cc4c82

4、 Prototype sketch design

By drawing tools （ The system has its own drawing 、Balsamiq Mockups、 Sharpening knife, etc ）、 Draw a simple layout on paper , Key function items

5、 Customer confirmation

according to 3、4、 Two products to communicate with customers , Finally, modify and adjust through the conclusion , So again and again 3、4、5、

6、UI beautify

After confirming the final sketch UI Prototype beautification , Then hand it over to the front-end students for cut-off development

7、 It is not the content of this outline , Let's talk about it next time