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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






5. A prototype developed to explore or verify requirements.






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






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






8. Work carried out or on behalf of others.






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






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






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






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






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






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






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






16. A system trigger that is initiated by humans.






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






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






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






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






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






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






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






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






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






26. The product capabilities or things the product must do for its users.






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






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






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






30. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






32. A system trigger that is initiated by time.






33. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






34. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






36. Software developed and sold for a particular market.






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






38. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






43. A non-actionable directive that supports a business goal.






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 small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






46. The set of processes templates and activities that will be used to perform business analysis in a specific context.






47. A partial or preliminary version of the system.






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






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






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