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. The process of examining new business opportunities to improve organizational performance.






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






3. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






5. Software developed and sold for a particular market.






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






7. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






10. A data element with a specified data type that describes information associated with a concept or entity.






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






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






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






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






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






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






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






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






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






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






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






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






23. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






30. A fixed period of time to accomplish a desired outcome.






31. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






32. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






33. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






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






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






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. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






42. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






43. The problem area undergoing analysis.






44. A system trigger that is initiated by humans.






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






46. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






47. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






49. A system trigger that is initiated by time.






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