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 brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






3. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






4. A measure of the profitability of a project or investment.






5. Software developed and sold for a particular market.






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






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






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






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






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






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






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






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






14. Ability of systems to communicate by exchanging data or services.






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






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






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






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






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






20. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






25. The problem area undergoing analysis.






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






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






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






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






30. A system trigger that is initiated by time.






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






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






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






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






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






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






37. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






40. The set of capabilities a solution must deliver in order to meet the business need.






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






42. A description of the requirements management process.






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






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






45. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






46. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






49. A prototype developed to explore or verify requirements.






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