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 evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






2. Something that occurs to which an organizational unit system or process must respond.






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






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






5. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






8. A unit of work performed as part of an initiative or process.






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






10. A stakeholder who provides products or services to an organization.






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






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






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






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






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






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






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






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






19. Software developed and sold for a particular market.






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






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






22. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






23. The process of examining new business opportunities to improve organizational performance.






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






25. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






26. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






30. A stakeholder person device or system that directly or indirectly accesses a system.






31. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






33. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






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






38. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






40. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






44. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






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






50. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.