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






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






3. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






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






7. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






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






11. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






12. Limitations on the design of a solution that derive from the technology used in its implementation.






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






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






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






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






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






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






19. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






21. A system trigger that is initiated by humans.






22. The human and nonhuman roles that interact with the system.






23. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






25. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






27. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






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






33. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






37. A prototype developed to explore or verify requirements.






38. A type of data model that depicts information groups as classes.






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






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






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






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






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






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






45. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






48. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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