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 analysis model that illustrates the architecture of the system's user interface.






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






3. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






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






8. The problem area undergoing analysis.






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






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






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






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






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






14. Ability of systems to communicate by exchanging data or services.






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






16. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






20. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






23. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






24. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






25. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






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






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






30. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






32. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






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






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






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






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






39. The work that must be performed to deliver a product service or result with the specified features and functions.






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






41. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






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






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






46. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






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






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