External entity: (Choose best answer.) A condition that must be satisfied or a state the system must be in before a use case can begin. A software package purchased from a vendor and either used as a self- contained solution to a problem or integrated, customized, and/or extended to satisfy customer needs. A person performing a specific role, a software system, or a hardware device that interacts with a system to achieve a useful goal. Also called a user role. A defect, open question, or decision regarding a requirement. Examples include items flagged as TBD, pending decisions, information that is needed, and conflicts awaiting resolution. An object in a context diagram or a data flow diagram that represents a user class, actor, software system, or hardware device that is external to the system being described but interfaces to it in some fashion. Also called a terminator. Risk. (Choose best answer.) A condition that could cause some loss or otherwise threaten the success of a project. A sequence of activities by which a software product is defined, designed, built, and verified A set of information that describes a business need that leads to one or more projects to deliver a solution and the desired ultimate business outcomes. The business requirements include business opportunities, business objectives, success metrics, a vision statement, and scope and limitations. None of these An analysis model that visually depicts the various states in which a system or an object in the system can exist, the permitted transitions that can take place between states, and the conditions and/or events that trigger each transition. Similar to a state machine or statechart diagram. Which of these is operational profile? (Choose best answer.) A fully functional prototype created as a skeleton or an initial increment of the final product, which is fleshed out and extended incrementally as requirements become clear and ready for implementation. A person performing a specific role, a software system, or a hardware device that interacts with a system to achieve a useful goal. Also called a user role. A description of a specific interaction between a user and a system to accomplish some goal. Alternatively, an instance of usage of the system, or a specific path through a use case. The process of apportioning system requirements among various architectural subsystems and components. A suite of scenarios that represents the expected usage pattern of a software product Issue, requirement? (Choose best answer.) An uninterrupted development period, typically one to four weeks in duration, during which a development team implements a defined set of functionality selected from the product backlog or baselined requirements for the product. Also called a Sprint. A statement that is believed to be true in the absence of proof or definitive knowledge. None of these An analysis model in the form of a matrix that shows all combinations of values for a set of conditions and indicates the expected system action in response to each combination. o A policy, guideline, standard, regulation, or computational formula that defines or constrains some aspect of the business