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 analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






3. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






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






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






8. The set of capabilities a solution must deliver in order to meet the business need.






9. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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






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






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






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






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






16. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






17. Software developed and sold for a particular market.






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






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






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






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






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






23. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






26. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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






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






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






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






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






33. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






35. The product capabilities or things the product must do for its users.






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






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






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






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






40. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






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






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






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






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






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






49. A model that defines the boundaries of a business domain or solution.






50. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.