OOAD Reading Notes (6): How to solve big problems

If you want to write only a few hundred linesCodeOfProgramYou can write it out quickly without designing it.

But what do you do if you want to write a code program with several million lines and tens of thousands of lines?

The level of programmers may only pass the big problem and the test of big projects can be seen.

The following is an analysis of how to solve big problems (large projects) from an object-oriented perspective)

 

1. fully communicate with customers and analyze what systems they really want. Future systems, such as CRM and HR, are not like ERP ).
2. Write the functions required by the user in a language that ordinary users can understand (for future confirmation) to form a basic URS
3. Create a blueprint for the system according to the requirements in section 2. Generally, use case divisor of UML is used.
4. In fact, major problems are caused by many small problems. The so-called Roman Empire was not built in one day. It is easy to understand and solve small problems (modules, classes, interfaces, pages ...)
5. Use the OO design mode to organize small problems (modules, classes, interfaces, pages.
6. Apply the OO design principles and use the code to reflect the details of each module.

The major problem is solved.