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 requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






2. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






4. Software requirements that limit the options available to the system designer.






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






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






7. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






8. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






11. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






12. A function of an organization that enables it to achieve a business goal or objective.






13. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






14. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






15. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






18. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






19. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






21. Information that is used to understand the context and validity of information recorded in a system.






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






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






24. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






27. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






28. Any effort undertaken with a defined goal or objective.






29. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






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






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






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






35. A group or person who has interests that may be affected by an initiative or influence over it.






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






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






38. An analysis model that illustrates the architecture of the system's user interface.






39. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






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






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






45. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






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






49. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






50. A fixed period of time to accomplish a desired outcome.