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






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






3. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






4. Work carried out or on behalf of others.






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






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






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






8. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






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






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






13. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






14. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






15. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






16. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






17. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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 deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






20. A partial or preliminary version of the system.






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






22. Software developed and sold for a particular market.






23. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






26. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






27. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






28. Any recognized association of people in the context of an organization or enterprise.






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






30. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






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






35. 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).






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






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






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






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






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






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






42. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






43. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






44. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






47. A system trigger that is initiated by humans.






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






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






50. A solution or component of a solution that is the result of a project.