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 use case composed of a common set of steps used by multiple use cases.






2. Software developed and sold for a particular market.






3. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






6. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






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






10. A system trigger that is initiated by humans.






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






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






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






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






15. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






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






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






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






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






21. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






23. The problem area undergoing analysis.






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






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






26. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






27. Work carried out or on behalf of others.






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






29. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






31. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






34. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






35. A type of data model that depicts information groups as classes.






36. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






37. An analysis model that shows user interface dialogs arranged as hierarchies.






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






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






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






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






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






43. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






44. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






46. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






47. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






48. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






50. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.







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