The Rational Unified Process (RUP) is a software engineering process, which captures many of best practices in modern software development. The notions of 3 and scenarios have been proven to be an excellent way to capture function requirements. RUP can be described in two dimensions - time and content. In the time dimension, the software lifecycle is broken into cycles. Each cycle is divided into four consecutive 4 which is concluded with a well-defined 5 and can be further broken down into 6 - a complete development loop resulting in a release of an executable product, a subset of the final product under development, which grows incrementally to become the final system. The content structure refers to the disciplines, which group 7 logically by nature.
A. rounds
B. loops
C. iterations
D. circularities
查看答案
原型化(Prototyping)方法是一类动态定义需求的方法, 42 不是原型化方法所具有的特征。与结构化方法相比,原型化方法更需要 43 。衡量原型开发人员能力的重要标准是 44 。
A. 提供严格定义的文档
B. 加快需求的确定
C. 简化项目管理
D. 加强用户参与和决策
The Rational Unified Process (RUP) is a software engineering process, which captures many of best practices in modern software development. The notions of 3 and scenarios have been proven to be an excellent way to capture function requirements. RUP can be described in two dimensions - time and content. In the time dimension, the software lifecycle is broken into cycles. Each cycle is divided into four consecutive 4 which is concluded with a well-defined 5 and can be further broken down into 6 - a complete development loop resulting in a release of an executable product, a subset of the final product under development, which grows incrementally to become the final system. The content structure refers to the disciplines, which group 7 logically by nature.
A. milestone
B. end-mark
C. measure
D. criteria
原型化(Prototyping)方法是一类动态定义需求的方法, 42 不是原型化方法所具有的特征。与结构化方法相比,原型化方法更需要 43 。衡量原型开发人员能力的重要标准是 44 。
A. 熟练的开发人员
B. 完整的生命周期
C. 较长的开发时间
D. 明确的需求定义
The Rational Unified Process (RUP) is a software engineering process, which captures many of best practices in modern software development. The notions of 3 and scenarios have been proven to be an excellent way to capture function requirements. RUP can be described in two dimensions - time and content. In the time dimension, the software lifecycle is broken into cycles. Each cycle is divided into four consecutive 4 which is concluded with a well-defined 5 and can be further broken down into 6 - a complete development loop resulting in a release of an executable product, a subset of the final product under development, which grows incrementally to become the final system. The content structure refers to the disciplines, which group 7 logically by nature.
A. artifacts
B. use-cases
C. actors
D. workers