System analyst Morning test notes software Engineering II

Requirements Development content:
1, determine the desired user category for the product.
2, get the requirements for each user class.
3, understand the actual user tasks and goals and the business requirements that these tasks support.
4, the analysis originates from the user's information to differentiate the user task demand, the function demand, the business rule, the quality attribute, the suggestion solution and the additional information.
5, the system-level requirements are divided into several subsystems, and a portion of the requirements are assigned to the software components.
6, understand the importance of the relevant quality attributes.
7, to discuss the implementation of priority division.
8, write the collected user requirements into documents and models.

The fanout of a module refers to the number of subordinate modules that the module calls directly.
The fan-in of a module refers to the number of ancestor modules that call this module directly.
Good software structure usually: the top fan out of the larger, the middle fan out of the small, the bottom of a large fan out.
User interface design Three principles: As for the user's control, reduce the user's memory burden, maintain the consistency of the user interface.

Dynamic characteristics of data: Fixed value attribute, fixed individual change attribute, random change attribute.
Fixed value properties: Their values generally do not change over time.
Fixed individual change properties: a fairly fixed set of individuals for the general population.
Random variable attribute: The individual is randomly appearing, and its value is also variable.

System analyst Morning test notes software Engineering II