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






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






3. A prototype that is continuously modified and updated in response to feedback from users.






4. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






7. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






10. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






12. An informal solicitation of proposals from vendors.






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






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






15. A non-actionable directive that supports a business goal.






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






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






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






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






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






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






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






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






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






25. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






29. A state or condition the business must satisfy to reach its vision.






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






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






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






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






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






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






36. Information that is used to understand the context and validity of information recorded in a system.






37. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






39. A description of the requirements management process.






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






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






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






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






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






45. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






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






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






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