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. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






2. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






3. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






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






8. A structured examination of an identified problem to understand the underlying causes.






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






10. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






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






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






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






15. Software requirements that limit the options available to the system designer.






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






17. The features and functions that characterize a product service or result.






18. A state or condition the business must satisfy to reach its vision.






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






20. A partial or preliminary version of the system.






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






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






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






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






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






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






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






28. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






31. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






34. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






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






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






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






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






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






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






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






44. An informal solicitation of proposals from vendors.






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






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






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






48. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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







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