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 group or person who has interests that may be affected by an initiative or influence over it.






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






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






4. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






6. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






9. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






10. Information that is used to understand the context and validity of information recorded in a system.






11. A person with specific expertise in an area or domain under investigation.






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






13. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






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






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






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






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






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






22. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






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






24. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






27. An analysis model that illustrates the architecture of the system's user interface.






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






29. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






30. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






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






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






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






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






38. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






39. Any unique and verifiable work product or service that a party has agreed to deliver.






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






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






42. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






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






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 measure of the profitability of a project or investment.






49. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






50. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe