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 set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






2. A model that defines the boundaries of a business domain or solution.






3. A person with specific expertise in an area or domain under investigation.






4. A partial or preliminary version of the system.






5. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






6. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






8. Work carried out or on behalf of others.






9. A function of an organization that enables it to achieve a business goal or objective.






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






11. An analysis model describing the data structures and attributes needed by the system.






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






13. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






14. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






15. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






19. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






20. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






23. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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






28. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






30. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






31. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






33. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






34. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






35. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






36. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






39. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






41. A prototype developed to explore or verify requirements.






42. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






45. Any effort undertaken with a defined goal or objective.






46. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






47. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






48. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






49. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






50. An analysis model showing the life cycle of a data entity or class.