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 function of an organization that enables it to achieve a business goal or objective.






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






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






4. A description of the requirements management process.






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






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






7. A system trigger that is initiated by time.






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






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






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






11. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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






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






15. A state or condition the business must satisfy to reach its vision.






16. A group of related tasks that support a key function of business analysis.






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






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






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






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






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






22. A data element with a specified data type that describes information associated with a concept or entity.






23. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






24. A system of programming statements symbols and rules used to represent instructions to a computer.






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






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






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






28. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






32. Any recognized association of people in the context of an organization or enterprise.






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






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






35. Software developed and sold for a particular market.






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






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






38. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






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






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






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






45. A fixed period of time to accomplish a desired outcome.






46. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests