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 number of employees a manger is directly (or indirectly) responsible for.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






20. A partial or preliminary version of the system.






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






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






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






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






25. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






26. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






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






30. A practitioner of business analysis.






31. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






32. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






33. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






36. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






37. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






40. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






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






44. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






46. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






50. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.