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. Software developed and sold for a particular market.






2. An analysis model that illustrates the architecture of the system's user interface.






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






4. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






8. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






10. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






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






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






14. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






15. A partial or preliminary version of the system.






16. The problem area undergoing analysis.






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






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






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






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






21. A specific actionable testable directive that is under the control of the business and supports a business policy.






22. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






24. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






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






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






28. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






31. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






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






36. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






37. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






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






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






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






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






44. The number of employees a manger is directly (or indirectly) responsible for.






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. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






48. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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