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. The area covered by a particular activity or topic of interest.






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






3. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






4. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






5. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






7. The human and nonhuman roles that interact with the system.






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






9. A system trigger that is initiated by humans.






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






11. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






12. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






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






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






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






19. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






21. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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






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






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






28. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






30. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






33. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






34. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






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






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






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






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






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






42. Limitations on the design of a solution that derive from the technology used in its implementation.






43. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






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






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






48. A stakeholder person device or system that directly or indirectly accesses a system.






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






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