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. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






2. A system of programming statements symbols and rules used to represent instructions to a computer.






3. A non-actionable directive that supports a business goal.






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






5. The problem area undergoing analysis.






6. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






7. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






8. A data element with a specified data type that describes information associated with a concept or entity.






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






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






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






12. All materials used by groups within an organization to define tailor implement and maintain their processes.






13. The area covered by a particular activity or topic of interest.






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






15. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






16. A stakeholder who provides products or services to an organization.






17. A prototype developed to explore or verify requirements.






18. A practitioner of business analysis.






19. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






21. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






22. A state or condition the business must satisfy to reach its vision.






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






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






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






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






27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






29. A system trigger that is initiated by humans.






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






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






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






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






34. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






35. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






37. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






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






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 requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






44. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






48. The work that must be performed to deliver a product service or result with the specified features and functions.






49. The quality attributes design and implementation constraints and external interfaces that the product must have.






50. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.