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 higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






4. The degree to which a set of inherent characteristics fulfills requirements.






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






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






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






8. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






10. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






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






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






19. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






21. A stakeholder who uses products or services delivered by an organization.






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






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






24. A partial or preliminary version of the system.






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






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






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






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






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






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






31. A system trigger that is initiated by time.






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






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






34. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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. Metadata related to a requirement used to assist with requirements development and management.






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






39. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






40. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






42. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






43. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






44. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






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






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






47. The features and functions that characterize a product service or result.






48. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






49. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests