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. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






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






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






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






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






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






8. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






9. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






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






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






14. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






15. A description of the requirements management process.






16. A system trigger that is initiated by time.






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






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






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






20. Software developed and sold for a particular market.






21. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






24. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






27. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






42. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






44. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






45. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






46. A practitioner of business analysis.






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






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






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






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







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