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. The features and functions that characterize a product service or result.






2. Any recognized association of people in the context of an organization or enterprise.






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






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






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






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






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






8. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






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






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






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






14. A partial or preliminary version of the system.






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






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






17. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






18. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






22. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






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






25. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






27. A state or condition the business must satisfy to reach its vision.






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






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






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






31. Any effort undertaken with a defined goal or objective.






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






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






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






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






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






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






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






39. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






40. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






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






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






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






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






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






48. Something that occurs to which an organizational unit system or process must respond.






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






50. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.







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