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






2. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






3. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






5. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






8. A partial or preliminary version of the system.






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






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






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






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






13. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






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






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






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






20. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






22. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






23. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






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






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






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






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






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






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






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






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






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






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






36. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






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






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






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






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






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






44. Software developed and sold for a particular market.






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






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






47. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






49. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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.