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. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






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






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






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






7. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






9. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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






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






14. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






15. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






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






18. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






20. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






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






26. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






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






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






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






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






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






32. A partial or preliminary version of the system.






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






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






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






36. An informal solicitation of proposals from vendors.






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






38. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






40. The problem area undergoing analysis.






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






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






43. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






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






45. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






46. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






47. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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