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 system of programming statements symbols and rules used to represent instructions to a computer.






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






3. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






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






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






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






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






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






10. Work carried out or on behalf of others.






11. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






14. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






15. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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






20. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






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






24. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






28. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






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






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






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






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






36. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






40. An analysis model describing the data structures and attributes needed by the system.






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






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






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






44. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






48. A temporary endeavor undertaken to create a unique product service or result.






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






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