Requirements (5) (ii)

Demand practice (5) detailed demand period (II)
What is different from the business modeling period is that I don't spend any time discussing what needs to be done, because there is no big difference between practice, attention, and business modeling. In terms of the complete process, methodologies such as RUP and XP are much better than I have mentioned. Therefore, I will focus on some puzzles and thoughts in my actual work.
1. rethink the relationship with other stages.
At the end of the previous article, we briefly discussed the relationship between the detailed requirement stage and other stages. For each stage of the software process, the difference is that the focus is different. In the business modeling stage, we focus on the overall requirements of the system. In the detail requirement stage, we focus more on the requirements details. The same is true for other stages. The architecture stage focuses on how to design a suitable architecture. at the design stage, the focus is on how to design the architecture.
Of course, different focal points lead to different skills and tools required for each stage. In the business modeling stage, you need to have the overall grasp ability. You can use simple use case diagrams, basic user materials, and other tools. The detailed requirement stage requires you to be able to fully explore the requirements and communicate well. Correspondingly, there will be different needs in the architecture, analysis, design, and other stages.
The essence of each stage is to focus on different points, which is the same for most software development. Whether the process you adopt is traditional or iterative.
2. Architecture
Martin Fowler wrote in his ISA:
I'm using architecture to mean the important design decisions, the ones that shape most aspects of a software system. these are often the harder decisions to change later on in the project (although often not as hard as people think ). as a result these are ones where it's useful to start in the right ction, and thus knowing about architecture is a valuable skill for any software developer.
The architecture is not mysterious, it is nothing more than a decision, but this decision is especially important to the software. Software developers may not take the initiative to design the architecture at all, but their behavior has been carried out in a subtle way. Some people are always talking about the architecture, but does not understand the meaning of this word.
The Spring Festival is approaching, and students are about to rush home. It is an important decision to choose the transportation means for returning home. The distance and price of different transportation tools are explicit and easy to know. Previous experiences tell you that train tickets are cheap, but they are relatively tight, take a long time, and the whole process is uncomfortable. Airline tickets are expensive but easy to buy and take less time, the entire process is quite comfortable. At this time, you need to make the right decision and choose a correct architecture for the home. What factors may you consider? The following lists some possible factors: congestion. We all know the situation during the Spring Festival; the difficulty of buying tickets, the ticket needs to be booked very early; whether there are additional channels, for example, if you can buy a student ticket for an airplane, how much living expenses do you have after one semester of economic strength;