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 uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






3. A structured examination of an identified problem to understand the underlying causes.






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






5. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






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






8. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






10. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






11. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






12. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






13. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






18. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






20. A function of an organization that enables it to achieve a business goal or objective.






21. A stakeholder who uses products or services delivered by an organization.






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






23. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






27. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






31. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






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






35. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






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






39. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






42. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






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






46. An analysis model showing the life cycle of a data entity or class.






47. Creating working software in multiple releases so the entire product is delivered in portions over time.






48. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






49. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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