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. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






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






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






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






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






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






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






12. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






13. Work carried out or on behalf of others.






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






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






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






17. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






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






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






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






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






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






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






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






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






27. The number of employees a manger is directly (or indirectly) responsible for.






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






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






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






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






32. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






34. A stakeholder with legal or governance authority over the solution or the process used to develop it.






35. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






39. Software developed and sold for a particular market.






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






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






42. A system trigger that is initiated by humans.






43. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






44. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






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






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






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






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






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