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






2. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






3. A practitioner of business analysis.






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






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






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






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






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






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






10. A data element with a specified data type that describes information associated with a concept or entity.






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






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






13. A description of the requirements management process.






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






15. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






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






19. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






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






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






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






25. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






30. A partial or preliminary version of the system.






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






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






33. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






34. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






36. Software requirements that limit the options available to the system designer.






37. A type of data model that depicts information groups as classes.






38. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






39. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






41. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






43. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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






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






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






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






50. Any unique and verifiable work product or service that a party has agreed to deliver.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests