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 problem area undergoing analysis.






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






3. Limitations on the design of a solution that derive from the technology used in its implementation.






4. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






5. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






6. A structured examination of an identified problem to understand the underlying causes.






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






8. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






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






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






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






15. A system trigger that is initiated by time.






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






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






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






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






20. A practitioner of business analysis.






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






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






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






24. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






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






29. Metadata related to a requirement used to assist with requirements development and management.






30. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






31. A system trigger that is initiated by humans.






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






33. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






34. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






35. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






36. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






39. A partial or preliminary version of the system.






40. An analysis model showing the life cycle of a data entity or class.






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






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






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






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






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






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






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






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






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






50. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.







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