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 group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






2. A system trigger that is initiated by time.






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






4. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






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






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






10. Any effort undertaken with a defined goal or objective.






11. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






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






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






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






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






19. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






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






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






22. The problem area undergoing analysis.






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






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






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






26. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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






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






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






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






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






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






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






34. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






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






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






37. Software requirements that limit the options available to the system designer.






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






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






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






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






42. A non-actionable directive that supports a business goal.






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






44. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






45. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






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






49. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






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