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






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






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






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






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






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






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






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






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






10. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






11. An informal solicitation of proposals from vendors.






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






13. A system trigger that is initiated by time.






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






15. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






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






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






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






21. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






22. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






23. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






24. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






27. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






29. Something that occurs to which an organizational unit system or process must respond.






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






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






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






33. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






34. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






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






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






39. A partial or preliminary version of the system.






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






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






42. The features and functions that characterize a product service or result.






43. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






44. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






45. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






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






50. The work that must be performed to deliver a product service or result with the specified features and functions.