文章目录
- 一、The requirements process
- 二、Requirements elicitation
- 三、Types of requirement
-
- 1.Functional requirements功能需求
- 2.Quality requirements/nonfunctional requirements质量需求/非功能需求
- 3.Design constraint
- 4.Process constraint
- 四、Resolving conflicts – priority
- 五、Two kinds of requirements documents
- 六、Modeling notations
-
- 1.Entity-relationship diagrams(E-R图)
-
- (1)Definition
- (2)Three elements
- (3)Properties/application
- (4)UML class diagrams类图
- 2.Event traces事件踪迹
-
- (1)Definition
- (2)Properties/application
- (3)UML sequence diagrams序列图
- 3.State machines状态机
-
- (1)Definition
- (2)Two elements
- (3)Properties/application
- (4)UML statechart diagrams状态图
- 4.Data-flow diagrams (DFD)数据流图
-
- (1)Definition
- (2)Four elements
- (3)Properties/application
- (4)UML use case diagrams用例图
- 5.Functions and relations
- 七、Prototyping requirements
-
- 1.Rapid prototyping
- 2.Prototyping vs. modeling
- 八、Requirements documentation需求文档
一、The requirements process
What is a requirement?
【选择题】
- The requirements are ( testable ) if they could clearly demonstrate whether the eventual product meets the requirement.
- “The system should be constructed so that it will be easy to add new functionality in the future.” This requirement is ( unverifiable )
二、Requirements elicitation
三、Types of requirement
1.Functional requirements功能需求
【选择题】
- “This book managing system provides the functions of book registration,student lending,and book searching” is a ( Functional requirements )
2.Quality requirements/nonfunctional requirements质量需求/非功能需求
【选择题】
“The system shall respond in less than 2 seconds with the answer.(快速响应)” belongs to (quality requirement)
3.Design constraint
4.Process constraint
四、Resolving conflicts – priority
五、Two kinds of requirements documents
Requirements definition
Requirements specification
六、Modeling notations
记住各自Modeling notation和对应UML notation的。
【选择题】
- The UML notation --( use case diagram ) is similar to a top-level data-flow diagram that depicts observable, user-initiated functionality in terms of interactions between the system and its environment.
1.Entity-relationship diagrams(E-R图)
(1)Definition
【简答题】
- describe Entity-relationship diagrams
E-R图:表示概念模型的一种方法,包含实体、联系和属性三个要素
(2)Three elements
- 实体:矩形
- 联系:菱形
- 属性:标注
(3)Properties/application
(4)UML class diagrams类图
2.Event traces事件踪迹
(1)Definition
【简答题】
- describe the event trace
事件踪迹:关于现实世界实体之间交换的事件序列的图形描述。
(2)Properties/application
(3)UML sequence diagrams序列图
3.State machines状态机
(1)Definition
【简答题】
- describe the State machines
状态机:描述了系统与环境之间的所有对话。
(2)Two elements
(3)Properties/application
(4)UML statechart diagrams状态图
4.Data-flow diagrams (DFD)数据流图
(1)Definition
【简答题】
- describe the data-flow diagram(DFD)
数据流图:对功能以及从一个功能到另一个功能的数据流建模。
(2)Four elements
(3)Properties/application
(4)UML use case diagrams用例图
5.Functions and relations
Decision table
题:
【应用题】
七、Prototyping requirements
1.Rapid prototyping
Throwaway prototyping
Evolutionary prototyping
2.Prototyping vs. modeling
八、Requirements documentation需求文档
【选择题】
( Programmers )are NOT direct users of a requirement documents.