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 showing the life cycle of a data entity or class.






2. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






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






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 description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






7. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






10. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






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






13. Something that occurs to which an organizational unit system or process must respond.






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






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






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






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






18. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






22. A description of the requirements management process.






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






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






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






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






27. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






30. The area covered by a particular activity or topic of interest.






31. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






32. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






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






37. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






41. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






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






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






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






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






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






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







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