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 stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






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






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






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






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






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






10. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






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






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






15. A description of the requirements management process.






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






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






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






19. Work carried out or on behalf of others.






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






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






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






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






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






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






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






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






28. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






32. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






37. An informal solicitation of proposals from vendors.






38. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






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






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






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






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






46. An analysis model showing the life cycle of a data entity or class.






47. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






50. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.