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. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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. The degree to which a set of inherent characteristics fulfills requirements.






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






5. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






6. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






8. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






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






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






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






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






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






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






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






16. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






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






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






19. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






21. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






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






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






26. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






32. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






33. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






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






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






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






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






38. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






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






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






46. A unit of work performed as part of an initiative or process.






47. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






48. A partial or preliminary version of the system.






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






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