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 subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






3. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






7. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






8. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






9. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






10. A prototype developed to explore or verify requirements.






11. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






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






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






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






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






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






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






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






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






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






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






23. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






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






28. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






29. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






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






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






34. A partial or preliminary version of the system.






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






36. Work carried out or on behalf of others.






37. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






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






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






40. A prototype that is continuously modified and updated in response to feedback from users.






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






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






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






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






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






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






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






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






49. A system trigger that is initiated by time.






50. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.