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. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






3. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






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






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






9. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






11. An analysis model describing the data structures and attributes needed by the system.






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






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






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






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






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






17. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






18. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






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






23. An assessment of the costs and benefits associated with a proposed initiative.






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






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






26. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






28. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






29. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






32. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






35. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






36. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






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






41. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






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






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






47. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






50. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.