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 temporary endeavor undertaken to create a unique product service or result.






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






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






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






5. A partial or preliminary version of the system.






6. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






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






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






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






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






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






13. Any recognized association of people in the context of an organization or enterprise.






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






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






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






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






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






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






20. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






22. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






25. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






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






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






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






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






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






33. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






36. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






40. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






45. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






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






49. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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