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 work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






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






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






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






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






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






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






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






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






12. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






17. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






18. A prototype that is continuously modified and updated in response to feedback from users.






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






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






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






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






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






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






26. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






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






31. A temporary endeavor undertaken to create a unique product service or result.






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 function of an organization that enables it to achieve a business goal or objective.






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






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






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






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






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






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






40. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






42. A model that defines the boundaries of a business domain or solution.






43. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






44. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






46. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






48. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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







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