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 shows user interface dialogs arranged as hierarchies.






2. A prototype developed to explore or verify requirements.






3. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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 graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






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






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






10. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






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






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






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






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






17. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






19. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






20. Influencing factors that are believed to be true but have not been confirmed to be accurate.






21. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






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






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






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






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






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






29. An informal solicitation of proposals from vendors.






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






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






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






33. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






36. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






38. The problem area undergoing analysis.






39. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






40. A partial or preliminary version of the system.






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






42. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






43. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






44. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






46. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






48. A solution or component of a solution that is the result of a project.






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






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