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. An informal solicitation of proposals from vendors.






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






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






4. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






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






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






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






9. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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. Metadata related to a requirement used to assist with requirements development and management.






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






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






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






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






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






17. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






21. The product capabilities or things the product must do for its users.






22. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






25. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






27. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






28. The process of examining new business opportunities to improve organizational performance.






29. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






30. An analysis model that shows user interface dialogs arranged as hierarchies.






31. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






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






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






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






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






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






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






39. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






41. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






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






45. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






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






50. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.