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






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






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






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






5. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






7. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






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






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






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






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






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






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






14. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






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






20. A partial or preliminary version of the system.






21. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






23. Software developed and sold for a particular market.






24. Work carried out or on behalf of others.






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






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






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






28. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






30. A system trigger that is initiated by humans.






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






32. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






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






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






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






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






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






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






41. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






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






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






44. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests