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 system trigger that is initiated by time.






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






3. Software requirements that limit the options available to the system designer.






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






5. A person with specific expertise in an area or domain under investigation.






6. Creating working software in multiple releases so the entire product is delivered in portions over time.






7. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






8. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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 comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






13. Any recognized association of people in the context of an organization or enterprise.






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






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






16. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






17. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






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






22. A description of the requirements management process.






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






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






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






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






27. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






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






33. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






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






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






38. The problem area undergoing analysis.






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






40. A fixed period of time to accomplish a desired outcome.






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






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






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






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






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






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






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






48. A system trigger that is initiated by humans.






49. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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