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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






2. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






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






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






6. Software developed and sold for a particular market.






7. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






11. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






12. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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 requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






15. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






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






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






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






21. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






22. Work carried out or on behalf of others.






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






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






25. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






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






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






29. A type of data model that depicts information groups as classes.






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






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






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






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






34. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






35. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






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






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






41. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






42. A stakeholder who uses products or services delivered by an organization.






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






44. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






46. Any unique and verifiable work product or service that a party has agreed to deliver.






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






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






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






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