Publication

Emergence of RE in Large Corporations: Lessons Learned From an RE Project at P&G

Alain Wegmann, Gil Regev
2006
Reports

Abstract

In this paper we describe the successful use of RE methods in a project at Procter and Gamble UK. We identify two main elements for this success. The first element is the combination of methods from P&G and academia (Adoption Methodology and Lightswitch). The second element is a new focus of the IT department of P&G on providing business solutions and is reflected in the name change from IT to IDS (Information and Decision Solutions). This shift is accompanied by a move from writing specifications of IT systems towards defining business requirements. We discuss how these elements explain the success of the RE phase of the project and propose research directions that may ease the introduction and use of RE methods in organizations.

Official source

https://infoscience.epfl.ch/entities/publication/8df975af-8d58-4a99-b3f8-6cfde125f50b

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

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, Gil Regev
2006
Reports

Abstract

Official source

https://infoscience.epfl.ch/entities/publication/8df975af-8d58-4a99-b3f8-6cfde125f50b

About this result

Related concepts (25)

Business analysis

Business analysis is a professional discipline focused on identifying business needs and determining solutions to business problems. Solutions may include a software-systems development component, process improvements, or organizational changes, and may involve extensive analysis, strategic planning and policy development. A person dedicated to carrying out these tasks within an organization is called a business analyst or BA. Business analysts are not found solely within projects for developing software systems.

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 (14)

Emergence of RE in Large Corporations: Lessons Learned From an RE Project at P&G

Chat with Graph Search

A System Engineering Approach to Antenna Design in Secure and Sensing Systems

Experimental Validation of a PMU Prototype Resilient Against DC Offsets and with Attenuated Self-Interference

Chromatic scheduling