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 system trigger that is initiated by time.






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






3. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






8. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






9. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






12. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






13. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






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






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






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






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






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






21. A function of an organization that enables it to achieve a business goal or objective.






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






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






24. Information that is used to understand the context and validity of information recorded in a system.






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






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






27. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






28. A prototype developed to explore or verify requirements.






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






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






31. A group or person who has interests that may be affected by an initiative or influence over it.






32. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






38. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






39. An actor who participates in but does not initiate a use case.






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






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






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






43. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






46. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






47. Any recognized association of people in the context of an organization or enterprise.






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






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






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