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






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






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






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






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






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






7. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






8. The quality attributes design and implementation constraints and external interfaces that the product must have.






9. A specific actionable testable directive that is under the control of the business and supports a business policy.






10. An analysis model describing the data structures and attributes needed by the system.






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






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






13. A system trigger that is initiated by humans.






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






15. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






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






18. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






20. The problem area undergoing analysis.






21. An assessment of the costs and benefits associated with a proposed initiative.






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






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






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






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






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






27. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






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






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






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






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






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






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






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






37. The features and functions that characterize a product service or result.






38. Work carried out or on behalf of others.






39. A system trigger that is initiated by time.






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






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






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






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






44. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






47. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






50. A link between two elements or objects in a diagram.