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






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






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






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






5. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






6. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






8. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






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






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






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






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






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






16. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






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






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






22. A person with specific expertise in an area or domain under investigation.






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






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






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






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






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






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






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






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






31. A group of related tasks that support a key function of business analysis.






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






33. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






37. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






38. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






40. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






44. The process of examining new business opportunities to improve organizational performance.






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






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






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






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






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






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