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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






22. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






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






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






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






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






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






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






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






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






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






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






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. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






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 deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






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






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






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






50. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests