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






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






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






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






5. The problem area undergoing analysis.






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






7. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






8. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






10. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






11. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






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






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






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






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






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






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






20. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






21. A prototype developed to explore or verify requirements.






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






23. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






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






26. A practitioner of business analysis.






27. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






29. A data element with a specified data type that describes information associated with a concept or entity.






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






31. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






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






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






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






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






38. An assessment of the costs and benefits associated with a proposed initiative.






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






40. A description of the requirements management process.






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






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






43. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






46. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






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






49. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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