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






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






3. Ability of systems to communicate by exchanging data or services.






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






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






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






7. A description of the requirements management process.






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






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






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






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






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






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






14. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






15. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






16. A prototype developed to explore or verify requirements.






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






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






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






20. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






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






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






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






26. A measure of the profitability of a project or investment.






27. A use case composed of a common set of steps used by multiple use cases.






28. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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






31. A temporary endeavor undertaken to create a unique product service or result.






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






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






34. The set of capabilities a solution must deliver in order to meet the business need.






35. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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






37. A link between two elements or objects in a diagram.






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






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






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






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






42. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






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






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






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






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






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






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