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 graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






2. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






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






6. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






9. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






10. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






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






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






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






16. The human and nonhuman roles that interact with the system.






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






18. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






21. The product capabilities or things the product must do for its users.






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






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






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






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






26. An analysis model showing the life cycle of a data entity or class.






27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






29. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






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






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






34. A stakeholder who provides products or services to an organization.






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






36. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






38. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






40. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






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






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






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






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






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






47. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






48. A practitioner of business analysis.






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






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