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. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






6. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






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






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






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






13. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






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






18. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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






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






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






24. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






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






28. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






32. A prototype developed to explore or verify requirements.






33. A description of the requirements management process.






34. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






35. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






36. A specific actionable testable directive that is under the control of the business and supports a business policy.






37. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






39. A system trigger that is initiated by humans.






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






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






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






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






44. A state or condition the business must satisfy to reach its vision.






45. A system trigger that is initiated by time.






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






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






48. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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