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. The set of capabilities a solution must deliver in order to meet the business need.






2. An informal solicitation of proposals from vendors.






3. Formal approval of a set of requirements by a sponsor or other decision maker.






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






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






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






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






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






9. Software developed and sold for a particular market.






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






11. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






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






13. A non-actionable directive that supports a business goal.






14. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






17. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






18. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






21. The human and nonhuman roles that interact with the system.






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






23. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






25. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






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






30. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






34. A type of data model that depicts information groups as classes.






35. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






36. A model that defines the boundaries of a business domain or solution.






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






38. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






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






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






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






45. The number of employees a manger is directly (or indirectly) responsible for.






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






47. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






48. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






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