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. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






2. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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






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






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






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






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






10. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






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






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






17. An informal solicitation of proposals from vendors.






18. Software developed and sold for a particular market.






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






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






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






22. The problem area undergoing analysis.






23. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






24. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






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






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






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






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






32. A shared boundary between any two persons and/or systems through which information is communicated.






33. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






35. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






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






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






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






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






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






44. Any unique and verifiable work product or service that a party has agreed to deliver.






45. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






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