Ten minutes of brain mapping and explanation, complete the absolute core of system analysts – Requirements Engineering


Ten minutes of brain mapping and explanation, complete the absolute core of system analysts – Requirements Engineering


Analyst series, I haven’t written it for a long time.
Because there are many overlapping parts between the test content of system analyst and that of system architecture designer. Therefore, I emphasized the difference between the two at the beginning of system analyst software proficiency test (Advanced), so I didn’t spend too much time in this aspect.

Recently, several private letters have been sent to me asking me about system analysts. Therefore, I plan to share the previous summary of system analysts, and add some practical thinking in the past year.

In the previous system architecture designer part, there has been a theoretical summary of requirements – system architecture designer – software proficiency test (Advanced) – Theory – requirements. However, on the one hand, the summary was somewhat fragmented, on the other hand, the demand part of system analysts was more comprehensive and systematic. So this time I’m sharing the requirements for system analysts.


The old rules. Go straight to XMIND. It’s crisp, it’s not hidden.


The picture must be clear. If you can’t see clearly, the display resolution is not enough. Please download the picture or open the picture separately in the new page for easy enlargement.

The UML part of the above picture is not expanded because it is relatively large. When I have a chance, I will open a chapter on this. If you are more urgent, you can leave me a message, then I will raise the priority of this article.


If you look at the previous requirements blog of the architect, you will find that this requirement blog has the following three advantages:

  • More systematic: the original scattered parts are organically formed into a whole.
  • Invalid elimination: remove the soft system methods that are no longer investigated and cannot be used in daily life.
  • More abundant: the content is more abundant, which improves the requirements definition, requirements verification, requirements management and other contents.

In addition, the amount of content reflects the strength of the investigation.

In practice, requirement analysis is one of the core of system analyst. System analysts tend to focus on the establishment of business analysis model. The architect’s focus is on the design model of the system. The correlation and difference between analysis model and design model will be discussed in other blogs. But here you can recommend a Book – system analysis and design methods.

At this time, you may be more curious about what is the analytical model. In fact, there are several explanations for the analysis model. In addition to the requirement analysis model which is most concerned about in the examination, there is also the business analysis model. The advantages and disadvantages of the analysis model determine the upper limit of the design model of the system, even the upper limit and direction of the business. The real system analyst has many abilities such as epistemology, methodology, management, economics and so on. To put it bluntly, system analyst is to complete the transformation of existing production relations through information technology.

All right. Let’s get back to the core of demand. After all, if you can’t even adjust the demand, it’s just a reflection on other things.

In terms of examination, requirement engineering has 10 + ‘content in objective questions, which has been regarded as the core chapter of investigation. And in the follow-up case analysis also has a pivotal position, is also the content of the regular examination. Demand engineering is a frequent visitor in the thesis. It has been tested almost every year in the last five years. For example, the status of requirements engineering in the system analyst examination is the position of architecture style in the architecture designer examination, but the score ratio is not so exaggerated. The main reason is that the examination content of system analysts is too much, which dilutes the score ratio of requirement engineering.


As the absolute core of system analyst, requirement engineering needs to be treated carefully. In particular, requirements engineering is an important part of our development career, so I hope you can know what it is and why it is.

If you really encounter some content temporarily unable to understand, then recite it first, maybe it is a good choice, and then you will understand it gradually.

At this point, the absolute core of the system analyst examination – Requirements Engineering, is done.

I wish to make progress with you.