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 shared boundary between any two persons and/or systems through which information is communicated.






2. A partial or preliminary version of the system.






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






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






5. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






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






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






10. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






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






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






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






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






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






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






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






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






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






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






24. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






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






28. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






31. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






35. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






42. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






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






46. A system trigger that is initiated by humans.






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






48. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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 visual model or representation of the sequential flow and control logic of a set of related activities or actions.