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






2. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






6. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






8. A prototype that is continuously modified and updated in response to feedback from users.






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






10. The problem area undergoing analysis.






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






12. An informal solicitation of proposals from vendors.






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






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






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






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






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. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






19. A prototype developed to explore or verify requirements.






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






21. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






22. A measure of the profitability of a project or investment.






23. A person with specific expertise in an area or domain under investigation.






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






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






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






27. A system trigger that is initiated by humans.






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






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






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






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






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






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






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






35. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






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






40. An actor who participates in but does not initiate a use case.






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






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






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






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






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






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






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






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






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






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