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. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






6. A system trigger that is initiated by humans.






7. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






8. An analysis model that illustrates the architecture of the system's user interface.






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






10. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






13. A unit of work performed as part of an initiative or process.






14. The problem area undergoing analysis.






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






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






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






18. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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






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






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






25. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






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






29. An analysis model describing the data structures and attributes needed by the system.






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






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






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






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






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






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 matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






38. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






41. The area covered by a particular activity or topic of interest.






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






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






44. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






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






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






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






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.