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. A visual model or representation of the sequential flow and control logic of a set of related activities or actions. A prototype that shows a shallow, and possibly wide, view of the system's functionality, but which does not generally support any actual use or interaction. 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. Words have power. Any unique and verifiable work product or service that a party has agreed to deliver. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business. A unit of work performed as part of an initiative or process. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps. Interfaces with other systems (hardware, software, and human) that a proposed system will interact with. An RFI is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options. A document or collection of notes or diagrams used by the business analyst during the requirements development process. 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. Here are 45 words and expressions to avoid. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality. For example, an iteration of requirements 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 planning how to elicit requirements from them, conducting elicitation techniques, documenting the requirements, and validating the requirements. See also technical constraint. These tests show only what the expected input and outputs will be. Most Annoying Business Jargon Just don’t say you’re doing it, because all that meaningless business jargon makes you sound like a complete moron. An indicator identifies a specific numerical measurement that indicates progress toward achieving an impact, output, activity or input. A higher level business rationale that, when addressed, will permit the organization to increase revenue, avoid costs, improve service, or meet regulatory requirements. Software developed and sold for a particular market. A stakeholder with legal or governance authority over the solution or the process used to develop it. 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. Any effort undertaken with a defined goal or objective. A non-proprietary modeling and specification language used to specify, visualize, and document deliverables for object-oriented software-intensive systems. A matrix used to track requirements' relationships. A collection of interrelated elements that interact to achieve an objective. A representation of requirements using text and diagrams. Stated requirements frequently reflect the desires of a stakeholder rather than the actual need. Developers are responsible for the construction of software applications. An assessment of the costs and benefits associated with a proposed initiative. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. © 1996-2018 TheStreet Inc. All rights reserved, Microsoft