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. An analysis model that shows user interface dialogs arranged as hierarchies.






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






3. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






4. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






8. Creating working software in multiple releases so the entire product is delivered in portions over time.






9. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






11. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






13. A partial or preliminary version of the system.






14. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






17. Work carried out or on behalf of others.






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






19. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






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






23. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






27. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






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






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






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






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






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






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






36. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






37. A description of the requirements management process.






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






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






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






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






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






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






44. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






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






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






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






50. An actor who participates in but does not initiate a use case.