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

This article mainly introduces the relevant knowledge of the problems in the process of web design and development, the content is detailed and easy to understand, the operation is simple and fast, and it has a certain reference value. I believe you will gain something after reading this web design and development process. Let's take a look at it.

(1) how well does the detailed design coincide with the code?

Suppose that in a project, the code is modified after testing and submitted, and the detailed design is not modified, then the detailed design does not match with the code, and to a large extent, the degree of coincidence will be very low.

If the detailed design does not match the final code, then such a detailed design will not be of any help to future maintenance.

If detailed design doesn't help the follow-up, why write it?

Because-- detailed design is used to guide code writing.

(2) what is the guiding significance of detailed design to the code?

Class diagrams are designed in detail to define relationships between class frameworks; timing diagrams (and sometimes flowcharts) are used to define invocation relationships between methods.

If that's how detailed design is defined, why not just code it in IDE?

Because-- the detailed design process needs to be documented for later reference.

(3) how is the detailed design reviewed and modified?

The review of the detailed design is through reading and reviewing the written detailed design documents, and pointing out the possible errors and omissions.

Then make changes to the questions raised until the modification is complete.

Why do we have to review and modify it in this way? Because the improvement of the quality of the detailed design is conducive to the early detection of problems.

(4) since the detailed design is used to guide code writing, why do you need subsequent testing?

In other words, why the detailed design is not 100% correct.

This question does not require that the detailed design be written 100% correctly-because it is an impossible task.

Detailed design is a conjecture process, and its review and modification are also completed in conjecture.

What kind of detailed design can guide code writing more effectively?

(5) how is the completion of detailed design defined?

The completion target of the detailed design is: the number of pages of the detailed design reaches several pages, and how many problems are found by reviewing each page.

Detailed design is used to guide code writing. Why not define indicators in terms of guiding code writing?

How do you start writing code when there are still problems in the detailed design?

The reality is: the completion of detailed design is determined by the preferences of the project manager-often determined by time pressure, continue to write if there is still time; if there is no time, it is finished.

(6) Why do you think detailed design is a necessary process?

Because it's a rule. Because that's what everyone else does. That's not the answer, is it?

So how on earth should the detailed design be written? The answer is: no! The reasons are as follows:

(1) the responsibility of detailed design is not clear.

The detailed design name refines the outline design and guides code writing. However, in contrast, the end time of the phase is not clear, and the criteria for the end of the phase do not define how to guide code writing, so it is difficult to say whether the detailed design is really used to guide code writing or refine the outline design.

(2) the detailed design does not produce valuable products.

According to statistics, the man-hours consumed by detailed design in the process of project development basically account for half of the coding and unit testing. But its product, the UML diagram, can be generated by writing code directly and then exporting it from IDE, a process that takes only a few seconds.

But detailed design still needs to be done. Isn't this contradictory to the previous one? No, no!

What is said above is written, and what is said here is to do.

There are many conditions for some processing, which cannot be clearly explained in a few words, so detailed design is needed at this time.

For example: a process determined by two sets of conditions. From the point of view of demand, the behavior under each combination of conditions can be clearly described by drawing a two-dimensional table.

A b c

1 a1 b1 c1

2 a2 b2 c2

3 a3 b3 c3

In this case, if you write a flowchart, the code will also be written according to the flowchart, and the code will become very lengthy. So the flow chart is not suitable for detailed design. This can be done through the writing of the class.

Suppose the line condition is a time range (TimeScope), which represents the past (Past), the present (Present) and the future (Future), while the column condition is State, which represents the application (Apply), approval (Approval), and Decline, respectively.

When designing a class, taking the time range as the principal axis and the state as the secondary axis, then the class is defined as:

Interface TimeScope {public void apply (); public void approval (); public voi decline ();}

Then Past,Present and Future implement the corresponding methods respectively to implement the matrix defined by the above requirements.

This method is called bridging mode (Bridge Pattern)

There is no need to leave documentation for this process.

Similarly, in most cases, code can be generated directly according to the requirements. Detailed design is a process that can be simplified to a few minutes. And, from a quality point of view, there is no loss.

Imagine how much savings a project can bring if it can omit the detailed design process.

What if the customer has to ask for a detailed design?

Hire documentation people who are cheaper than software engineers to reverse the detailed design according to the code-- because class diagrams can be generated through tools-- so there are very few documentation staff and few man-hours.

This is the end of the article on "what are the problems in the process of web design and development?" Thank you for reading! I believe that everyone has a certain understanding of the knowledge of "what are the problems in the process of web design and development". If you want to learn more knowledge, you are welcome to follow the industry information channel.

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.