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






2. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






5. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






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






10. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






12. A model that defines the boundaries of a business domain or solution.






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






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






15. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






19. A measure of the profitability of a project or investment.






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






21. A practitioner of business analysis.






22. A partial or preliminary version of the system.






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






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






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






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






27. A non-actionable directive that supports a business goal.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






47. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests