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. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






3. A structured examination of an identified problem to understand the underlying causes.






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






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






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






7. A fixed period of time to accomplish a desired outcome.






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






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






10. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






11. A stakeholder who provides products or services to an organization.






12. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






13. The quality attributes design and implementation constraints and external interfaces that the product must have.






14. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






16. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






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






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






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






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






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






27. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






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






33. A temporary endeavor undertaken to create a unique product service or result.






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






35. A measure of the profitability of a project or investment.






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






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






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






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






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






41. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






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






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






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






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






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






47. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






48. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






49. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






50. An analysis model that shows user interface dialogs arranged as hierarchies.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests