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






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






3. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






4. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






9. The set of capabilities a solution must deliver in order to meet the business need.






10. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






11. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






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






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






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






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






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






18. An actor who participates in but does not initiate a use case.






19. An analysis model describing the data structures and attributes needed by the system.






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






21. A system trigger that is initiated by humans.






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






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






24. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






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






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






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






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






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






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






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






33. A stakeholder person device or system that directly or indirectly accesses a system.






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






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






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






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






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






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






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






41. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






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






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






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






46. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






47. A unit of work performed as part of an initiative or process.






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






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






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