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. An informal solicitation of proposals from vendors.






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






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






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






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






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






7. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






10. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






11. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






12. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






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






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






17. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






19. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






22. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






25. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






26. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






28. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






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






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






34. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






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






39. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






40. A system trigger that is initiated by time.






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






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






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






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






45. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






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






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