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






2. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






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






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






6. Influencing factors that are believed to be true but have not been confirmed to be accurate.






7. Limitations on the design of a solution that derive from the technology used in its implementation.






8. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






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






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. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






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






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






20. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






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






25. A prototype that dives into the details of the interface functionality or both.






26. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






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






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






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






32. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






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






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






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






38. A prototype developed to explore or verify requirements.






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






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






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






42. Work carried out or on behalf of others.






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






44. A partial or preliminary version of the system.






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






46. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






47. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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