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 graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






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






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






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. Software requirements that limit the options available to the system designer.






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






9. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






10. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






11. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






12. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






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






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






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






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






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






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






21. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






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






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






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






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






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






29. A system trigger that is initiated by time.






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






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






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






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






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






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






36. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






37. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






40. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






41. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






43. A system trigger that is initiated by humans.






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






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






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






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






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






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






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