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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






2. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






3. Any unique and verifiable work product or service that a party has agreed to deliver.






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 fixed period of time to accomplish a desired outcome.






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






7. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






8. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






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






12. A stakeholder with legal or governance authority over the solution or the process used to develop it.






13. The degree to which a set of inherent characteristics fulfills requirements.






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






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






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






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






18. Software developed and sold for a particular market.






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






20. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






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






24. A prototype developed to explore or verify requirements.






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






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






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






28. An analysis model showing the life cycle of a data entity or class.






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






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






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






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






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






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






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






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






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






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






39. A data element with a specified data type that describes information associated with a concept or entity.






40. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






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






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






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






46. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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