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 measure of the profitability of a project or investment.






2. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






4. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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






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






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






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






11. A stakeholder who uses products or services delivered by an organization.






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






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






14. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






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






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






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






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






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






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






24. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






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






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






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






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






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






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






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






35. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






36. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






40. A use case composed of a common set of steps used by multiple use cases.






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






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






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






44. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






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






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






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






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






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