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 team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






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






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






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






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






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






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






9. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






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






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






14. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






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






18. The human and nonhuman roles that interact with the system.






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






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






21. A partial or preliminary version of the system.






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






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






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






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






26. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






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






29. An informal solicitation of proposals from vendors.






30. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






33. A system trigger that is initiated by humans.






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






35. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






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






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






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






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






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






43. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






45. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






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






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






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