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






2. Any unique and verifiable work product or service that a party has agreed to deliver.






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






4. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






5. A prototype developed to explore or verify requirements.






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






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






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






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






10. An informal solicitation of proposals from vendors.






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






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






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






14. A system trigger that is initiated by humans.






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






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






17. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






20. A stakeholder who provides products or services to an organization.






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






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






23. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






25. Any effort undertaken with a defined goal or objective.






26. A group or person who has interests that may be affected by an initiative or influence over it.






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






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






29. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






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






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






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






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






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






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






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






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






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






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






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






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






42. A link between two elements or objects in a diagram.






43. Something that occurs to which an organizational unit system or process must respond.






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






45. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






48. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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