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 description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






4. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






6. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






7. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






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






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






12. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






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






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






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






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






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






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






19. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






20. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






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






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






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






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






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






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






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






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






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






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






32. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






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






34. A group or person who has interests that may be affected by an initiative or influence over it.






35. A state or condition the business must satisfy to reach its vision.






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






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






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






39. A system trigger that is initiated by time.






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






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






42. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






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






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






46. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






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






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






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






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







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