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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






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






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






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






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






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






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






12. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






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






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






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






17. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






19. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






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






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






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






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






25. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






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






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






30. A shared boundary between any two persons and/or systems through which information is communicated.






31. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






34. A system trigger that is initiated by humans.






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






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






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






38. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






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






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






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






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






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






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






46. All materials used by groups within an organization to define tailor implement and maintain their processes.






47. A state or condition the business must satisfy to reach its vision.






48. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






50. A practitioner of business analysis.