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 fixed period of time to accomplish a desired outcome.






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






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






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






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






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






7. A link between two elements or objects in a diagram.






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






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






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






11. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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. A solution or component of a solution that is the result of a project.






14. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






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






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






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






21. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






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






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






28. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






30. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






31. Work carried out or on behalf of others.






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






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






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






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






36. A type of data model that depicts information groups as classes.






37. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






38. A shared boundary between any two persons and/or systems through which information is communicated.






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






40. A stakeholder who uses products or services delivered by an organization.






41. A partial or preliminary version of the system.






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






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






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






45. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






47. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






48. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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