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 team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






3. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






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






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






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






8. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






12. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






15. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






16. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






18. A link between two elements or objects in a diagram.






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






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






21. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






22. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






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






26. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






27. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






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






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






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






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






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






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






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






36. A fixed period of time to accomplish a desired outcome.






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






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






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






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






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






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






43. Software developed and sold for a particular market.






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






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






46. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






47. A description of the requirements management process.






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






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






50. Formal approval of a set of requirements by a sponsor or other decision maker.