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. Any effort undertaken with a defined goal or objective.






2. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






3. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






6. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






7. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






9. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






10. An analysis model that illustrates the architecture of the system's user interface.






11. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






12. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






14. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






15. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






16. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






17. Any unique and verifiable work product or service that a party has agreed to deliver.






18. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






19. Information that is used to understand the context and validity of information recorded in a system.






20. A description of the requirements management process.






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






22. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






23. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






24. The process of examining new business opportunities to improve organizational performance.






25. 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.






26. 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.






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






28. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






29. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






30. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






31. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






32. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






33. The product capabilities or things the product must do for its users.






34. 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






35. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






36. The number of employees a manger is directly (or indirectly) responsible for.






37. 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






38. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






39. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






42. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






43. A fixed period of time to accomplish a desired outcome.






44. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






45. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






46. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






48. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






49. Software developed and sold for a particular market.






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