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 description of the requirements management process.






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






3. Influencing factors that are believed to be true but have not been confirmed to be accurate.






4. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






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






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






9. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






10. The set of processes templates and activities that will be used to perform business analysis in a specific context.






11. The problem area undergoing analysis.






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






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






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






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






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






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






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






19. An assessment of the costs and benefits associated with a proposed initiative.






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






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






22. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






24. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






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






28. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






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






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






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






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






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






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






38. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






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






42. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






44. Software developed and sold for a particular market.






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






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






47. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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







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