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 work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






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






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






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






7. A person with specific expertise in an area or domain under investigation.






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






9. A system trigger that is initiated by time.






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






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






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






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






14. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






15. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






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






21. The area covered by a particular activity or topic of interest.






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






23. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






24. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






25. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






27. A link between two elements or objects in a diagram.






28. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






29. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






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






32. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






34. A stakeholder who provides products or services to an organization.






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






36. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






38. The human and nonhuman roles that interact with the system.






39. Metadata related to a requirement used to assist with requirements development and management.






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






41. Something that occurs to which an organizational unit system or process must respond.






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






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






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






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






46. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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