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. Any recognized association of people in the context of an organization or enterprise.






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






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






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






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






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






7. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






9. A system of programming statements symbols and rules used to represent instructions to a computer.






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






11. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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 shared boundary between any two persons and/or systems through which information is communicated.






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






15. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






16. A system trigger that is initiated by time.






17. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






18. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






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






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






24. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






27. A description of the requirements management process.






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






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






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






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






32. The degree to which a set of inherent characteristics fulfills requirements.






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






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






35. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






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






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






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






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






42. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






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






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






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






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






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






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