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 person device or system that directly or indirectly accesses a system.






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






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






4. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






7. A prototype that dives into the details of the interface functionality or both.






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






9. The product capabilities or things the product must do for its users.






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






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






12. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






15. A stakeholder who uses products or services delivered by an organization.






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






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






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






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






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






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






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






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






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






25. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






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






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






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






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






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






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






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






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






35. A state or condition the business must satisfy to reach its vision.






36. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






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






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






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






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






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






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






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






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






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






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






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






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