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






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






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






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






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






6. A measure of the profitability of a project or investment.






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






8. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






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






12. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






13. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






15. A practitioner of business analysis.






16. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






19. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






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






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






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






25. An analysis model that illustrates the architecture of the system's user interface.






26. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






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






31. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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






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






35. The process of examining new business opportunities to improve organizational performance.






36. Information that is used to understand the context and validity of information recorded in a system.






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






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






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






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






41. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






42. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






43. A group of related tasks that support a key function of business analysis.






44. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






45. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






46. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






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






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






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