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 diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






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






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






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






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






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






8. The problem area undergoing analysis.






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






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






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






12. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






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






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






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






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






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






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






20. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






24. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






25. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






28. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






29. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






32. An analysis model describing the data structures and attributes needed by the system.






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






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






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






36. A structured examination of an identified problem to understand the underlying causes.






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






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






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






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






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






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






43. Any effort undertaken with a defined goal or objective.






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






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






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






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






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






49. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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