Shulou(Shulou.com)06/03 Report--

Often hear leadership teachings, development colleagues should take a step forward to make products? To do pre-sales? That's one way, but it's a big step. Personally, I feel that before taking this big step, I need to take a small step: from writing good code to doing good design.

The following diagram is a standard design guide that has been combed out according to common practices in software engineering. It has clearly defined the phases and activities of software design, product specifications, documentation requirements, and training required to cooperate. It is suitable for large scale of people, high degree of productization and outsourcing service mode. Following this standard design guideline to get things done at each stage is a practical guide to standard development methodology.

Some people will say that now is the era of mobile Internet, our product development requirements short, frequent, fast online, this standard design method is no longer suitable, I think it is not completely correct. My practice is to make some customized tailoring according to the standard design guidelines according to the vision and market situation of the product. Even if the documents are all cut out, the corresponding activities should still be carried out according to these stages in my mind, because this is not only a guide, but also a methodology. For the activities carried out in these stages, the following is to sort out my design experience.

The first is the requirements capture and analysis stage, always feel that the requirements are constantly changing, always blame the market and product managers, in fact, many cases we do not understand the requirements in place. There are both inaccurate business understanding and unreasonable support methods. Another point is that there is no distinction between prototypes and requirements. Prototypes do not represent requirements. Divide requirement analysis into two stages: business requirement and system requirement. Only by doing domain analysis well can we fundamentally adapt to the continuous changes of requirements.

Next, let's talk about how to do system analysis well. At this stage, it is generally called domain model construction, conceptual model, and analysis object model. It focuses on analyzing the problem domain itself, discovering important business domain concepts, and establishing relationships between business domain concepts. Domain model design is a key step in requirements analysis. It helps users and requirements analysts to establish business concepts, determine the problem domain of the user's business, the business scope involved in the system, and so on.

The general steps for domain model design are:

1. Extract nouns from business descriptions

2. Summarize the business entities from the extracted nouns, distinguish the attributes, roles, entities and instances in the nouns, and form a set of operational entities in the problem domain;

3. Abstract business model from business entity set and establish concept of problem domain.

4. Design domain model and determine the relationship between models with UML method and legend. Note: The relationship between entities mainly includes generalization, dependence and association, and association is divided into general association, aggregation and combination.

In short, model entities are analyzed first, and then relationships between model entities are found.

Relationship between domain model and real data model: domain model is an important tool for communicating with users, a concept that requirements analysts and users understand together, and a language for communicating with each other. It is an analytical model describing the entities involved in the business and their relationships. It is the product of requirements analysis and is related to the problem domain. At the same time, it provides us with a certain expanded vision of requirements analysts and system functions, and sees possible changes in future requirements or possible problems. The data model is a part of system design and implementation, describing the realization of user requirements in data structure. Of course, the conceptual model design in the data model is similar to the domain model, and what is lacking is a broader description of relationships between entities.

Take the open platform business management as an example, the domain model drawings designed are welcome.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.