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 stakeholder who provides products or services to an organization.






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






3. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






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






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






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






10. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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 business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






14. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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. A prototype that is continuously modified and updated in response to feedback from users.






17. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






19. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






23. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






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






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






29. A system trigger that is initiated by humans.






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






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






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






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






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






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






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






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






38. Any unique and verifiable work product or service that a party has agreed to deliver.






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






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






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






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






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






44. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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






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






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






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






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