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 prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






3. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






4. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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






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






10. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






12. The problem area undergoing analysis.






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






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






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






16. A function of an organization that enables it to achieve a business goal or objective.






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






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






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






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






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






22. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






24. An analysis model describing the data structures and attributes needed by the system.






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






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






27. A group or person who has interests that may be affected by an initiative or influence over it.






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






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






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






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






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






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






34. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






36. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






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






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






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






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






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






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






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






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






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






48. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






49. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






50. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.