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 activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






2. An informal solicitation of proposals from vendors.






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






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






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






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






7. A use case composed of a common set of steps used by multiple use cases.






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






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






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






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






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






13. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






15. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






16. The human and nonhuman roles that interact with the system.






17. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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






22. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






23. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






26. Metadata related to a requirement used to assist with requirements development and management.






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






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






29. A partial or preliminary version of the system.






30. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






32. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






35. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






38. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






41. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






42. The degree to which a set of inherent characteristics fulfills requirements.






43. Work carried out or on behalf of others.






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






45. A practitioner of business analysis.






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






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






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






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






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







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