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. Software developed and sold for a particular market.






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






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






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






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






6. The human and nonhuman roles that interact with the system.






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






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






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






10. A description of the requirements management process.






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






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






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






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






15. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






16. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






18. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






19. A practitioner of business analysis.






20. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






21. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






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






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






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






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






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






31. The problem area undergoing analysis.






32. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






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






36. A specific actionable testable directive that is under the control of the business and supports a business policy.






37. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






39. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






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






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






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






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






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






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






49. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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