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 business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






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






4. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






6. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






8. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






11. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






15. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






18. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






21. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






23. A group or person who has interests that may be affected by an initiative or influence over it.






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






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






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






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






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






29. The degree to which a set of inherent characteristics fulfills requirements.






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






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






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






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






34. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






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






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






37. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






38. Software developed and sold for a particular market.






39. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






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






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






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






45. A practitioner of business analysis.






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






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






48. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






49. A group of related tasks that support a key function of business analysis.






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