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 person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






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






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






7. Software developed and sold for a particular market.






8. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






9. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






12. A prototype that is continuously modified and updated in response to feedback from users.






13. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






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






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






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






19. A fixed period of time to accomplish a desired outcome.






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






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






22. A group of related tasks that support a key function of business analysis.






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






24. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






26. A link between two elements or objects in a diagram.






27. A partial or preliminary version of the system.






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






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






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






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






32. Work carried out or on behalf of others.






33. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






37. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






38. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






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






45. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






48. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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







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