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






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






3. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






6. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






9. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






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






14. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






15. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






17. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






19. An informal solicitation of proposals from vendors.






20. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






25. Ability of systems to communicate by exchanging data or services.






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






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






28. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






29. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






30. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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






34. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






40. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






44. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






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






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






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






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