Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






2. A measure of the profitability of a project or investment.






3. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






4. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






5. A structured examination of an identified problem to understand the underlying causes.






6. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






7. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






8. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






9. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






10. Software requirements that limit the options available to the system designer.






11. The problem area undergoing analysis.






12. Formal approval of a set of requirements by a sponsor or other decision maker.






13. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






14. A link between two elements or objects in a diagram.






15. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






16. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






17. Limitations on the design of a solution that derive from the technology used in its implementation.






18. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






19. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






20. Metadata related to a requirement used to assist with requirements development and management.






21. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






22. A unit of work performed as part of an initiative or process.






23. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






24. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






25. A prototype that dives into the details of the interface functionality or both.






26. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






27. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






28. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






29. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






30. An actor who participates in but does not initiate a use case.






31. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






32. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






33. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






34. The features and functions that characterize a product service or result.






35. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






36. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






37. The set of capabilities a solution must deliver in order to meet the business need.






38. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






39. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






40. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






41. A stakeholder who uses products or services delivered by an organization.






42. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






43. An informal solicitation of proposals from vendors.






44. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






45. An analysis model that shows user interface dialogs arranged as hierarchies.






46. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






47. A use case composed of a common set of steps used by multiple use cases.






48. The degree to which a set of inherent characteristics fulfills requirements.






49. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






50. A stakeholder with legal or governance authority over the solution or the process used to develop it.