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 list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






3. A partial or preliminary version of the system.






4. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






5. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






21. An informal solicitation of proposals from vendors.






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






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






24. The process of examining new business opportunities to improve organizational performance.






25. Work carried out or on behalf of others.






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






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






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






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






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






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






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






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






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






35. Software developed and sold for a particular market.






36. The problem area undergoing analysis.






37. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






38. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






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






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






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






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






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






45. A function of an organization that enables it to achieve a business goal or objective.






46. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






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