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 temporary endeavor undertaken to create a unique product service or result.






2. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






4. A system trigger that is initiated by time.






5. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






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






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






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






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






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






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






14. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






15. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






17. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






18. A type of data model that depicts information groups as classes.






19. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






20. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






21. A practitioner of business analysis.






22. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






23. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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






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






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






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






29. The set of capabilities a solution must deliver in order to meet the business need.






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






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






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






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






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






35. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






36. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






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






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






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






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






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






44. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






46. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






48. A person with specific expertise in an area or domain under investigation.






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






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