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






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






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






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






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






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






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






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






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






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






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






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






13. A system trigger that is initiated by humans.






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






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






16. An analysis model describing the data structures and attributes needed by the system.






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






18. An analysis model that shows user interface dialogs arranged as hierarchies.






19. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






20. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






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






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






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






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






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






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






33. The area covered by a particular activity or topic of interest.






34. A stakeholder who provides products or services to an organization.






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






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






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






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






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






40. An informal solicitation of proposals from vendors.






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






42. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






43. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






44. A partial or preliminary version of the system.






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






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






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






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






49. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






50. A type of diagram that shows objects participating in interactions and the messages exchanged between them.