1. Multiple-choice questions (number of questions: 7, totaling 35.0 points)
1
The standard for measuring module independence is ().
(5.0 points)
A.
Type of coupling
B.
Types of cohesion
C.
The concealment of module information
D.
Coupling and cohesion
My answer: The purpose of the D
2
summary design is to determine the entire system ().
(5.0 points)
A.
Scale
B.
Function and module structure
C.
Fee
D.
Test plan
My answer: B
3
software design is the process of converting () to software representation.
(5.0 points)
A.
Software needs
B.
System analysis
C.
Database
D.
Software code
My answer: The main result of A
4
summary design is ().
(5.0 points)
A.
User interface requirements
B.
User's analysis plan
C.
Summary design specification
D.
Overall system plan
My answer: C
5
data structure design is also an important part of summary design, mainly for data () design.
(5.0 points)
A.
Logic
B,
access
C,
user view
D.
Index
My answer: A
6
The following is not the principle of software design ().
(5.0 points)
A.
Abstract
B.
Modular
C,
bottom to bottom
D.
Information hiding
My answer: The graphic tool that connects C
7's
summary design and detailed design is ().
(5.0 points)
A,
DFD chart
B,
SC picture
C.
Program flow chart PFD
D,
PAD picture
My answer: B
2. Judgment questions (number of questions: 5, total 25.0 points)
1
The scope of a module should be greater than the control scope of the module.
(5.0 points)
My answer: ×
2
The stronger the coupling between modules, the weaker the independence of the modules.
(5.0 points)
My answer: √
3
When designing a module, one module should include as many functions as possible.
(5.0 points)
My answer: ×
4
Software structure diagrams can be mapped out using data flow diagrams.
(5.0 points)
My answer: √
5
In the structured design process, first confirm the DFD.
(5.0 points)
My answer: √
3. Short answer questions (number of questions: 2 of 10.0 points in total)
1
What are the principles that software design should follow?
(5.0 points)
My answer
Answer: The following principles are generally followed in software design: modularity, abstraction, information hiding and localization, consistency, integrity, and verifiability.
2
What are the design rules for heuristics?
(5.0 points)
My answer
Answer: (1) Improvement of module functions; (2) Elimination of duplicate functions and improvement of software structure; (3) Module size should be moderate;
(4) The depth, width, fan-in and fan-out of the module should be appropriate; (5) The scope of the module should be within the control range;
(6) Strive to reduce the complexity of the module interface; (7) Design a single-entry and single-exit module; (8) The module function should be predictable.
