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 software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






2. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






3. Something that occurs to which an organizational unit system or process must respond.






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






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






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






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






8. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






9. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






10. Software developed and sold for a particular market.






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






12. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






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






15. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






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






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






21. A description of the requirements management process.






22. A shared boundary between any two persons and/or systems through which information is communicated.






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






24. A prototype developed to explore or verify requirements.






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






26. A model that defines the boundaries of a business domain or solution.






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






28. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






34. A practitioner of business analysis.






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






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






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






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






39. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






40. A partial or preliminary version of the system.






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






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






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






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






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






46. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






47. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






48. The problem area undergoing analysis.






49. Work carried out or on behalf of others.






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