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 deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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






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






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






5. The problem area undergoing analysis.






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






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






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






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






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






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






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






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






14. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






17. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






18. A group or person who has interests that may be affected by an initiative or influence over it.






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






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






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






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






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






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






25. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






28. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






32. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






33. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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






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






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






38. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






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






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






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






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






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






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






45. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






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






48. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






50. A partial or preliminary version of the system.