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 defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






3. A system trigger that is initiated by humans.






4. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






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






8. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






9. Limitations on the design of a solution that derive from the technology used in its implementation.






10. A prototype developed to explore or verify requirements.






11. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






13. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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






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






18. A shared boundary between any two persons and/or systems through which information is communicated.






19. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






20. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






22. A measure of the profitability of a project or investment.






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






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






25. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






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






30. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






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






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






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






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






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






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






42. A use case composed of a common set of steps used by multiple use cases.






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






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






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






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






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






48. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






49. Software developed and sold for a particular market.






50. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.