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 employees a manger is directly (or indirectly) responsible for.






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






3. A link between two elements or objects in a diagram.






4. A prototype that is continuously modified and updated in response to feedback from users.






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






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






7. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






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






9. A partial or preliminary version of the system.






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






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






12. A prototype that dives into the details of the interface functionality or both.






13. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






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






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






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






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






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






22. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






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






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






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






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






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






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






29. Information that is used to understand the context and validity of information recorded in a system.






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






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






32. A function of an organization that enables it to achieve a business goal or objective.






33. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






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






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






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






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






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






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






41. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






42. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






47. The work that must be performed to deliver a product service or result with the specified features and functions.






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






49. A group or person who has interests that may be affected by an initiative or influence over it.






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