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 data element with a specified data type that describes information associated with a concept or entity.






2. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






3. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






5. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






7. Limitations on the design of a solution that derive from the technology used in its implementation.






8. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






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






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






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






14. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






16. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






19. A system trigger that is initiated by time.






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






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






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






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






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






25. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






27. An analysis model that shows user interface dialogs arranged as hierarchies.






28. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






30. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






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






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






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






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






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






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






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






44. A prototype developed to explore or verify requirements.






45. A system trigger that is initiated by humans.






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






47. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






48. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






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