Publication

SEAM in Business: A Systemic Method for Understanding Stakeholders’ Needs in Value Networks

Alain Wegmann
2006
Reports

Abstract

Understanding stakeholders’ needs is necessary to design requirements for organizations and IT systems. We present a systemic modeling method to identify and categorize stakeholders within value networks, to analyze the relationships between these value networks and to infer IT requirements from this analysis. We illustrate the approach with an association who needs a web site. Thanks to this method, requirements that closely support the business strategy can be identified.

Official source

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

Alain Wegmann
2006
Reports

Abstract

Official source

Related concepts (32)

Requirements analysis

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.

Business requirements

Business requirements, also known as stakeholder requirements specifications (StRS), describe the characteristics of a proposed system from the viewpoint of the system's end user like a CONOPS. Products, systems, software, and processes are ways of how to deliver, satisfy, or meet business requirements. Consequently, business requirements are often discussed in the context of developing or procuring software or other systems. Three main reasons for such discussions: A common practice is to refer to objectives, or expected benefits, as 'business requirements.

Requirement

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder.

Related publications (32)

SEAM in Business: A Systemic Method for Understanding Stakeholders’ Needs in Value Networks

Chat with Graph Search

Decision-support platform for transparent and modular design of sustainable waste management systems

Detection and characterisation of resident space objects in wide field astronomical surveys

Recursive Causal Discovery (Abstract Reprint)