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 set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






2. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






3. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






5. An informal solicitation of proposals from vendors.






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






7. A group or person who has interests that may be affected by an initiative or influence over it.






8. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






9. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






10. A partial or preliminary version of the system.






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






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






13. A system trigger that is initiated by humans.






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






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






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






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






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






19. The problem area undergoing analysis.






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






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






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






23. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






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






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






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






30. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






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






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






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






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






38. Work carried out or on behalf of others.






39. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






40. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






41. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






43. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






45. A system trigger that is initiated by time.






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






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






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






49. A description of the requirements management process.






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