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. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






4. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






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






8. An assessment of the costs and benefits associated with a proposed initiative.






9. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






12. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






13. A fixed period of time to accomplish a desired outcome.






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






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






16. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






18. The process of examining new business opportunities to improve organizational performance.






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






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






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






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






23. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






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






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






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






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






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






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






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






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






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






35. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






38. An informal solicitation of proposals from vendors.






39. The problem area undergoing analysis.






40. The area covered by a particular activity or topic of interest.






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






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






43. A use case composed of a common set of steps used by multiple use cases.






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






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






46. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






47. Formal approval of a set of requirements by a sponsor or other decision maker.






48. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






49. The features and functions that characterize a product service or result.






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