Chapter 3 Summary of "soft engineer video"

"When we build a project, the customer may verbally tell you what he wants to do, or give you some documents to tell you that this is the requirement. It is difficult to know what to do based on a few oral statements or some documents. At this time, we need to mine the requirements to get a list of functions, or use case diagrams, and analyze the software requirements ." In this section, I think that although straightforward, the software requirement analysis is clear. Below is my mind map for Chapter 3:

 

In fact, this video chapter describes two aspects: task process and analysis method. Their results are all for a document, that is, the software requirement specification.

I. Tasks and processes 1. Task

1) identify problems, analyze data, and establish an analysis model.

Our analysis here requires the ability to describe functionality and performance, and determine design constraints and interfaces and define effective requirements.

2) Prepare the Software Specification

2. Process

The process here is actually a step.

 

Of course, the data requirements statement (technical information about the data processing description and data collection requirements) will also be formed here ), preliminary completion of the user manual (detailed description of the features, performance and user interface of the software, so that users can understand how to use the software), the modification and improvement of the project development plan.

Ii. Analysis Methods 1. Principles

To put it simply, the principle of Software Requirement Analysis is abstraction, decomposition, and simplification. Of course, the Guiding Principles are also described in the video.

2. Three Analysis Methods

1) Structured Analysis Method

To understand this method, we first need to figure out what the DFD graph is, and then look at the steps.

DFD is a graphical technology used to describe the information flow and data transformation from data to output. In software requirement analysis, a group of DFD is often used to indicate the functions of the same software at different abstract levels from rough to precise, which is hierarchical DFD. Below are the basic DFD forms and components:

 

For details, see "DFD diagram of software requirements".

Then you can analyze and draw images. The steps are also relatively simple, which can be roughly divided into two parts: drawing a hierarchical data flow diagram and determining data definitions and processing policies.

2) Rapid Prototyping

The biggest feature of this method is the rush to build software and then append it. It needs to be discarded when a fundamental error occurs.

 

3) Dynamic Analysis

In fact, dynamic analysis is not an analysis method. The most common analysis methods listed in the video are: Status migration diagram, sequence diagram, and Petri net.

Therefore, in the second part, we should focus on the structural analysis methods and dynamic analysis methods.

Conclusion

This chapter introduces a lot of content. I feel that I am not sure about it, but I have also gained a lot and I have some preliminary understanding of the flowchart.

Chapter 3 Summary of "soft engineer video"