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. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






5. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






8. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






9. The problem area undergoing analysis.






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






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






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






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






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






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






16. The set of processes templates and activities that will be used to perform business analysis in a specific context.






17. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






18. The product capabilities or things the product must do for its users.






19. The set of capabilities a solution must deliver in order to meet the business need.






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






21. An informal solicitation of proposals from vendors.






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






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






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






25. An analysis model describing the data structures and attributes needed by the system.






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






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






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






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






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






31. An analysis model that illustrates the architecture of the system's user interface.






32. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






34. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






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






38. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






39. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






40. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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






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






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






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






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






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






48. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






49. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






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