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






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






3. Work carried out or on behalf of others.






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






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






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






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






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






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






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






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






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






13. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






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






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






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






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






21. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






22. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






24. A use case composed of a common set of steps used by multiple use cases.






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






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






27. A description of the requirements management process.






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






29. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






31. Any recognized association of people in the context of an organization or enterprise.






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






33. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






35. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






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






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






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






40. A prototype developed to explore or verify requirements.






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






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






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






44. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






45. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






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






48. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






49. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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