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 error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






3. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






5. A type of data model that depicts information groups as classes.






6. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






7. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






10. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






13. A system trigger that is initiated by humans.






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






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






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






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






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






19. A prototype that is continuously modified and updated in response to feedback from users.






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






21. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






22. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






23. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






24. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






26. Work carried out or on behalf of others.






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






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






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






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






31. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






34. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






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






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






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






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






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






45. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






46. Something that occurs to which an organizational unit system or process must respond.






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






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






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






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