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. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






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






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






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






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






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






8. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






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






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






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






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






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






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






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






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






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






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






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






22. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






24. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






28. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






30. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






31. The problem area undergoing analysis.






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






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






34. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






36. A system trigger that is initiated by time.






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






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






39. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






43. A unit of work performed as part of an initiative or process.






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






45. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






46. A stakeholder who uses products or services delivered by an organization.






47. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






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







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