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 point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






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






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






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






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 quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






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






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






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






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






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






15. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






16. A shared boundary between any two persons and/or systems through which information is communicated.






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






18. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






19. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






22. A prototype that dives into the details of the interface functionality or both.






23. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






28. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






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






31. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






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






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






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






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






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






39. A practitioner of business analysis.






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






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






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






43. The problem area undergoing analysis.






44. A system of programming statements symbols and rules used to represent instructions to a computer.






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






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






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






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






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






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







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