C2010-636 無料問題集「IBM Requirements Management with Use Cases - Part 1」

（A）Obtain status information about the requirements

（B）Assign resources to requirements

（C）Enforce keywords such as "shall" and "must" in the requirement text

（D）Reduce the ambiguity of the requirements

（A）Identify constraints

（B）Avoid customer misunderstandings

（C）Understand the stakeholder's needs

（D）Understand the root causes of a problem

（A）Important to the customer

（B）Is the system's principle purpose

（C）Easy to implement

（D）Includes the architecturally significant interfaces

（A）Data values

（B）Non-functional requirements

（C）Sub-components

（D）Testing procedures

（A）Limiting the number of subflows in each use case

（B）Supplementary requirements

（C）Requirement attributes and their values

（D）Relationships between actors and use cases

（A）Actor

（B）Stakeholder

（C）Manager

（D）Customer

（A）Construction

（B）Transition

（C）Inception

（D）Elaboration

（A）Communicate the primary features of the proposed system

（B）Detail software requirements

（C）Identify stakeholders

（D）Specify the flow of events in each use case

（A）Accommodates simultaneously entry of information from up to 100 installers

（B）Runs on the Windows 95 operating system

（C）Includes a Phone Installer class

（D）Produces status reports about telephone installations

（A）How to fulfill stakeholder requests

（B）Quality attributes of the system

（C）Process used to build the system

（D）How the solution interacts with the outside world