Use caseIn software and systems engineering, the phrase use case is a polyseme with two senses: A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful. A potential scenario in which a system receives an external request (such as user input) and responds to it. This article discusses the latter sense. A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal.
Software requirements specificationA software requirements specification (SRS) is a description of a software system to be developed. It is modeled after the business requirements specification (CONOPS). The software requirements specification lays out functional and non-functional requirements, and it may include a set of use cases that describe user interactions that the software must provide to the user for perfect interaction.
Requirements traceabilityRequirements traceability is a sub-discipline of requirements management within software development and systems engineering. Traceability as a general term is defined by the IEEE Systems and Software Engineering Vocabulary as (1) the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or primary-subordinate relationship to one another; (2) the identification and documentation of derivation paths (upward) and allocation or flowdown paths (downward) of work products in the work product hierarchy; (3) the degree to which each element in a software development product establishes its reason for existing; and (4) discernible association among two or more logical entities, such as requirements, system elements, verifications, or tasks.
Stakeholder theoryThe stakeholder theory is a theory of organizational management and business ethics that accounts for multiple constituencies impacted by business entities like employees, suppliers, local communities, creditors, and others. It addresses morals and values in managing an organization, such as those related to corporate social responsibility, market economy, and social contract theory. The stakeholder view of strategy integrates a resource-based view and a market-based view, and adds a socio-political level.
Information systemAn information system (IS) is a formal, sociotechnical, organizational system designed to collect, process, store, and distribute information. From a sociotechnical perspective, information systems are composed by four components: task, people, structure (or roles), and technology. Information systems can be defined as an integration of components for collection, storage and processing of data of which the data is used to provide information, contribute to knowledge as well as digital products that facilitate decision making.
Organizational behaviorOrganizational behavior or organisational behaviour (see spelling differences) is the: "study of human behavior in organizational settings, the interface between human behavior and the organization, and the organization itself". Organizational behavioral research can be categorized in at least three ways: individuals in organizations (micro-level) work groups (meso-level) how organizations behave (macro-level) Chester Barnard recognized that individuals behave differently when acting in their organizational role than when acting separately from the organization.
Stakeholder (corporate)In a corporation, a stakeholder is a member of "groups without whose support the organization would cease to exist", as defined in the first usage of the word in a 1963 internal memorandum at the Stanford Research Institute. The theory was later developed and championed by R. Edward Freeman in the 1980s. Since then it has gained wide acceptance in business practice and in theorizing relating to strategic management, corporate governance, business purpose and corporate social responsibility (CSR).
Management information systemA management information system (MIS) is an information system used for decision-making, and for the coordination, control, analysis, and visualization of information in an organization. The study of the management information systems involves people, processes and technology in an organizational context. In a corporate setting, the ultimate goal of using management information system is to increase the value and profits of the business.
Goal orientationGoal orientation, or achievement orientation, is an "individual disposition towards developing or validating one's ability in achievement settings". In general, an individual can be said to be mastery or performance oriented, based on whether one's goal is to develop one's ability or to demonstrate one's ability, respectively. A mastery orientation is also sometimes referred to as a learning orientation. Goal orientation refers to how an individual interprets and reacts to tasks, resulting in different patterns of cognition, affect and behavior.
Software requirementsSoftware requirements for a system are the description of what the system should do, the service or services that it provides and the constraints on its operation. The IEEE Standard Glossary of Software Engineering Terminology defines a requirement as: A condition or capability needed by a user to solve a problem or achieve an objective. A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.
