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 process of examining new business opportunities to improve organizational performance.






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






3. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






7. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






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






11. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






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






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






14. An informal solicitation of proposals from vendors.






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






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






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






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






19. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






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






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






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






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






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






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






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






31. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






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






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






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






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






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






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






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






40. A partial or preliminary version of the system.






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






42. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






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






45. The problem area undergoing analysis.






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






47. Any unique and verifiable work product or service that a party has agreed to deliver.






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






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






50. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.