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 responsible for assessing the quality of and identifying defects in a software application.






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






3. Software developed and sold for a particular market.






4. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






5. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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






8. Formal approval of a set of requirements by a sponsor or other decision maker.






9. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






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






12. A data element with a specified data type that describes information associated with a concept or entity.






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






14. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






15. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






18. A system trigger that is initiated by time.






19. An informal solicitation of proposals from vendors.






20. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






21. A temporary endeavor undertaken to create a unique product service or result.






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






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






24. The problem area undergoing analysis.






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






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






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






29. A solution or component of a solution that is the result of a project.






30. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






34. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






36. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






38. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






40. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






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






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






45. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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. Work carried out or on behalf of others.






50. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.