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 characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






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






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






6. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






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






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






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






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






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






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






16. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






17. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






18. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






22. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






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






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






26. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






27. An informal solicitation of proposals from vendors.






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






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






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






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






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






33. A group or person who has interests that may be affected by an initiative or influence over it.






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






35. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






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






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






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






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






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






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






45. A group of related tasks that support a key function of business analysis.






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






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






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






49. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






50. A partial or preliminary version of the system.