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. Creating working software in multiple releases so the entire product is delivered in portions over time.






2. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






4. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






7. A prototype developed to explore or verify requirements.






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






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






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






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






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






13. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






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






17. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






18. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






19. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






22. A description of the requirements management process.






23. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






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






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






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






31. The quality attributes design and implementation constraints and external interfaces that the product must have.






32. The number of employees a manger is directly (or indirectly) responsible for.






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






34. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






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






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






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






40. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






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






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






46. The problem area undergoing analysis.






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






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






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






50. Software requirements that limit the options available to the system designer.







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