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 shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






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






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






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






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






11. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






13. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






16. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






18. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






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






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






25. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






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






30. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






32. A system of programming statements symbols and rules used to represent instructions to a computer.






33. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






36. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






37. A system trigger that is initiated by time.






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






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






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






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






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






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






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






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






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






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






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






49. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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.