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 set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






3. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






7. An informal solicitation of proposals from vendors.






8. Something that occurs to which an organizational unit system or process must respond.






9. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






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






11. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






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






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






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






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






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






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






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






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






23. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






25. The work that must be performed to deliver a product service or result with the specified features and functions.






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






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






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






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






30. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






32. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






34. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






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






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






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






40. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






41. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






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






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






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






45. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






46. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






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






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