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 requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






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






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






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






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






11. The human and nonhuman roles that interact with the system.






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






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






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






15. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






16. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






19. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






20. A use case composed of a common set of steps used by multiple use cases.






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






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






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






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






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






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






27. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






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






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






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






32. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






33. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






34. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






35. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






38. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






40. A prototype that is continuously modified and updated in response to feedback from users.






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






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






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






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






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






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






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






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






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






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