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 stakeholder who uses products or services delivered by an organization.






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






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






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






5. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






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






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






11. A fixed period of time to accomplish a desired outcome.






12. A system trigger that is initiated by time.






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






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






15. A link between two elements or objects in a diagram.






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






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






18. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






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






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






24. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






25. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






27. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






28. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






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






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






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






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






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






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






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






40. A partial or preliminary version of the system.






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






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






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






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






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests