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 process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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






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






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






7. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






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






11. A partial or preliminary version of the system.






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






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






14. A group of related tasks that support a key function of business analysis.






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






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






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






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






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






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






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






22. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






23. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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






26. The problem area undergoing analysis.






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






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






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






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






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






32. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






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






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






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






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






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






40. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






43. A stakeholder with legal or governance authority over the solution or the process used to develop it.






44. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






45. A fixed period of time to accomplish a desired outcome.






46. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






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






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