Help | Advanced Search

Computer Science > Software Engineering

Title: a multi-case study of agile requirements engineering and the use of test cases as requirements.

Abstract: Context: It is an enigma that agile projects can succeed 'without requirements' when weak requirements engineering is a known cause for project failures. While agile development projects often manage well without extensive requirements test cases are commonly viewed as requirements and detailed requirements are documented as test cases. Objective: We have investigated this agile practice of using test cases as requirements to understand how test cases can support the main requirements activities, and how this practice varies. Method: We performed an iterative case study at three companies and collected data through 14 interviews and two focus groups. Results: The use of test cases as requirements poses both benefits and challenges when eliciting, validating, verifying, and managing requirements, and when used as a documented agreement. We have identified five variants of the test-cases-as-requirements practice, namely de facto, behaviour-driven, story-test driven, stand-alone strict and stand-alone manual for which the application of the practice varies concerning the time frame of requirements documentation, the requirements format, the extent to which the test cases are a machine executable specification and the use of tools which provide specific support for the practice of using test cases as requirements. Conclusions: The findings provide empirical insight into how agile development projects manage and communicate requirements. The identified variants of the practice of using test cases as requirements can be used to perform in-depth investigations into agile requirements engineering. Practitioners can use the provided recommendations as a guide in designing and improving their agile requirements practices based on project characteristics such as number of stakeholders and rate of change.
Subjects: Software Engineering (cs.SE)
Cite as: [cs.SE]
  (or [cs.SE] for this version)
  Focus to learn more arXiv-issued DOI via DataCite
Journal reference: Inf. Softw. Technol. 77: 61-79 (2016)
: Focus to learn more DOI(s) linking to related resources

Submission history

Access paper:.

  • Other Formats

license icon

References & Citations

  • Google Scholar
  • Semantic Scholar

BibTeX formatted citation

BibSonomy logo

Bibliographic and Citation Tools

Code, data and media associated with this article, recommenders and search tools.

  • Institution

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs .

case study requirements engineering

  • Open positions
  • Software quality career paths
  • Software testing and quality assurance
  • Quality strategy
  • Test management and planning
  • Test automation
  • Test automation evaluation
  • Continuous delivery
  • Quality driven software development

Requirements Engineering: User Stories vs. Use Cases

case study requirements engineering

Have you ever been in a situation where you are looking at your Jira backlog and think that you have no idea what the title of the ticket means or what is supposed to be implemented in the scope of the ticket? Read on to learn about key requirements engineering tools: user stories and use cases.

Requirements engineering is a tricky business. Software requirements should be written in a concise manner but overly detailed requirements can also be a hindrance and an undue burden for the development process if applied every time. User stories and use cases are essential tools that, when applied correctly, can produce the most favorable outcome.

A user story describes a software feature from the perspective of the end user. Let’s look at an example: “As an Author, I want to be able to edit a post, so that I can make necessary changes.”

The user story follows a structure: As a [persona], I [want to], [so that]. The structure can also be summarized as “Who, What, Why”. A properly defined user story can convey a lot of information for the reader in a very tight package.

A use case describes an interaction of a user with a system. It captures the details of a user, their goals, and the required steps to accomplish those goals. Use case is best described as a table. There is no one correct way to define a use case table, but let’s take a look at an example below.

case study requirements engineering

If we compare this use case description to the user story in the chapter before, we can see that it contains a lot more details for all stakeholders interested in the requirements. It also forces us to think about the actual implementation of the feature and the systems that are required to complete it.

Different Usages for User Stories and Use Cases

So what is the difference between user stories and use cases?

  • User story : a short and simple description of a feature of a system from a user point of view answering the questions: Who, What, and Why.
  • Use case : detailed description of a user interaction with a system.

User stories can be utilized in many ways. Below I will list two examples. Firstly, user stories are great as Jira story ticket titles. The short “Who, What, Why” approach is very good for summarizing the intent of the ticket. Let’s first take a traditional ticket title that can often be seen on a backlog: “Add user to a register”. Can you guess who is adding a user to a register and why? Let’s fix this by using a user story: “As a Customer Admin, I want to be able to add a user to a register, so that I can comply with regulations”. The who and the why immediately become clearer. It is best to keep the user stories short, so they can be easily digested by the user. More detailed descriptions and acceptance criteria can be defined in the ticket description.

Secondly, user stories are a good way to outline and plan the upcoming work. Even if it is not completely clear how the user stories are going to be implemented, there is a lot of value in describing the work in the short “Who, What, Why” format. It is not always necessary, or even beneficial, to try to go into all the details of the implementation of each user story. Sometimes it is necessary to just see the scope of the upcoming work in multiple user stories that are still to be prioritized, planned and implemented.

Let’s move on to use cases. Use cases are a great way for the development team members trying to understand, verify, document, and implement business requirements. If you look at the use case table in the previous chapter, you can rarely see product owners providing such detailed explanation of the requirements. With such a use case table, the team can verify from a product owner that they have understood the business requirements correctly and provide an implementable solution suggestion.

Sometimes there can be UI sketches already done by a designer before the detailed use case is written. However, many times, the design does not take into account different situations and UI states that can arise in using the software. For example, the exceptions row in the use case table in the previous chapter defines an UI state that few designers or even product owners might think of. Thus, a detailed use case table can provide additional value in most situations for getting the implementation right the first time.

case study requirements engineering

Conclusions

User stories and use cases have their own place in requirements engineering. User stories are fast and simple for general descriptions of a system functionality from the user point of view, even when there are no detailed specifications available. When detailed specifications are required, use cases are invaluable tools to describe the user flow and interaction with a system.

  • Software development
  • Software testing
  • Company culture

case study requirements engineering

Double interview – What does family-friendliness mean at VALA

case study requirements engineering

Efficiency gains of AI assisted testing in 2024 and near future

case study requirements engineering

What are the benefits of QA when using only off the shelf software?

Privacy overview.

CookieDurationDescription
_lfa2 yearsThis cookie is set by the provider Leadfeeder to identify the IP address of devices visiting the website, in order to retarget multiple users routing from the same IP address.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
CookieDurationDescription
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
langsessionLinkedIn sets this cookie to remember a user's language setting.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
pll_language1 yearThe pll _language cookie is used by Polylang to remember the language selected by the user when returning to the website, and also to get the language information when not available in another way.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
CookieDurationDescription
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_DXHYWY32G02 yearsThis cookie is installed by Google Analytics.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
CookieDurationDescription
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
CookieDurationDescription
_dc_gtm_UA-54427192-11 minuteNo description
_lfa_test_cookie_storedpastNo description
AnalyticsSyncHistory1 monthNo description
li_gc2 yearsNo description
  • Corpus ID: 37176316

Requirements Engineering with Use Cases - a Basis for Software Development

  • Published 1999
  • Computer Science

38 Citations

Requirements engineering with interrelated conceptual models and real world scenes.

  • Highly Influenced

MASRML - A Domain-Specific Modeling Language for Multi-Agent Systems Requirements

An integrated metamodel-based approach to software model refactoring, a reference architecture for the logistics service map: structuring and composing logistics services in logistics networks, integrating process modeling and simulation with benchmarking using a business process management system for local government, uml model refactoring: a systematic literature review, semántica oculta en modelos de requisitos, improving software requirement elicitation using q-use case, refactoring uml diagrams and models with model-to-model transformations, validating software requirements with enactable use case descriptions, 48 references, towards integration of use case modelling and usage-based testing, scenario usage in system development: a report on current practice, scenarios in system development: current practice, requirements engineering: frameworks for understanding, a hierarchical use case model with graphical representation, use case maps for object-oriented systems, case studies for method and tool evaluation, comparing detection methods for software requirements inspections: a replicated experiment, improving the use case driven approach to requirements engineering, scenarios-an industrial case study and hypermedia enhancements, related papers.

Showing 1 through 3 of 0 Related Papers

Academia.edu no longer supports Internet Explorer.

To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to  upgrade your browser .

Enter the email address you signed up with and we'll email you a reset link.

  • We're Hiring!
  • Help Center

paper cover thumbnail

Software Requirement Engineering For Small and Medium Enterprise: A Case Study

Profile image of Erik Borglund

2011, rapport nr.: Report/Department of Applied Information …

Related Papers

Romi Satria Wahono

case study requirements engineering

Communications on Applied Electronics

Rajshree Pandey

Information and Software Technology

Hossein Saiedian

Anthony Finkelstein

Abstract This paper reviews the area of requirements engineering. It outlines the key concerns to which attention should be devoted by both practitioners, who wish to “reengineer” their development processes, and academics, seeking intellectual challenges. It presents an assessment of the state-of-the-art and draws conclusions in the form of a research agenda

Abdul Ghani

This paper presents about a study conducted to investigate the current state of Requirements Engineering (RE) problems and practices amongst the software development companies in Malaysia. The main objective of the study is to determine areas in RE process that should be addressed in future research in order to improve the process. Information required for the study was obtained through

Armash Abbasi

Linda Macaulay

IRJET Journal

Present complexities and higher level of client's expectations from an application leads to software development process to be more alignment towards technical specialists and managerial techniques. Software progression is incessantly put into practice by practitioners in order to meet up the dynamic stakeholder's requirements. Due to globalization, software and technology both become a fragment of any automated entity. Every organization body supposes to build a decent and reliable working software. It has also been inspected that for successful software system, requirements engineering is very crucial phase. This makes a growth in the scope of the requirements engineering process, apart with new challenges of gathering, prioritizing and preprocessing the requirements. Requirements Engineering is well-thought-out as a collection of processes that functions on different levels, which includes organizational, product and project level. In any field, building an application is a thought-provoking task due to the absence of right requirements engineering technique and due to developer's understandability of the actual needs of the client. There are various tools are available to gather requirements from the clients. The major faults are occurred in choosing the right requirements engineering technique which is considered a delicate task, any faults or wrong selection may lead to major catastrophic for the final product. In this paper, we have proposed a requirement engineering process model that produce quality requirements for software development. The proposed framework tries to bridge the gap between theoretical and practical aspects of requirements engineering process. It helps the software experts and analyst to choose a right technique for selected requirements engineering phase. We have thoroughly comprehended and evaluate all the existing requirements engineering techniques with respect to analyst preferences, client experiences, project attributes, software process model characteristics. The successful implementation of proposed requirements engineering process can have a good impression on the creation of qualitative software product.

Alcides Quispe

Loading Preview

Sorry, preview is currently unavailable. You can download the paper by clicking the button above.

RELATED PAPERS

Uolevi Nikula

Lemai Nguyen

Requirements Engineering

Alistair Sutcliffe

Alexei Lapouchnian

Proceedings of the Conference on the …

sarila rana

International Journal of Information Technology and Computer Science

Naveed riaz

Kituyi Mayoka

Neil Calabroso

Software, IEEE

mayank sohani

Abreham Menker

Edward Kabaale

Engr Waqas Ali , Nadeem Majeed , Muhammad Nadeem Majeed Choudhary , Adeel Rafiq

Anil Kumara

Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering - EASE '14

The Journal of Object Technology

Donald Firesmith

Tony Gorschek

Revista Eletrônica de Sistemas de Informação

PAULO CEZAR STADZISZ

2011 Ninth International Conference on Software Engineering Research, Management and Applications

Dr-Muhammad Suhaib

ACM SIGSOFT Software Engineering Notes

Anne Persson , Nazim Madhavji

Basharat Jehan , shakeel Ahmed

Alejandro Hossian

SDIWC Organization

Virendra Singh

  •   We're Hiring!
  •   Help Center
  • Find new research papers in:
  • Health Sciences
  • Earth Sciences
  • Cognitive Science
  • Mathematics
  • Computer Science
  • Academia ©2024

Search USA

  • FAFSA Updates
  • Interactive
  • JagTran Tracker
  • JagMail Login
  • Faculty & Staff
  • Directories
  • Faculty/Staff

Search USA

  • College of Engineering
  • College of Engineering News

Winners Recognized for Defense Data Grand Prix 2024

Derik Wolfe

Winners Recognized for Defense Data Grand Prix 2024 data-lightbox='featured'

The University of South Alabama was recognized for winning third place at the Defense Data Grand Prix 2024. Led by Dr. Kari Lippert (Systems), South students competed against other universities and institutes around the world. The DDGP connects faculty-led teams with real-world problems posed by a Department of Defense (DoD) organization.

Read the entire story here.

Winners Recognized for Defense Data Grand Prix 2024   July 2, 2024

Lawrence Stoudemire showing his graduation cap he designed to reflect engineering and mortar board.

A Feat of Engineering -- and Design   May 8, 2024

Dr. Edmund Spencer, Associate Professor of Electrical and Computer Engineering, whose space plasma research led to the development of a new Time Domain Impedance Probe.

New Space Plasma Measuring Instrument is a Result of Dr. Edmund Spencer's Research   April 22, 2024

University of South Alabama students, from left, Devon Edinburgh, Paige Palazzo, Matthew Crump, Reed Turner and Luke Andress run though a series of tests on their senior research project at a firing range north of Mobile.

Case Study: South Seniors Design a Safer Way To Transport Batteries   April 16, 2024

IEEE Account

  • Change Username/Password
  • Update Address

Purchase Details

  • Payment Options
  • Order History
  • View Purchased Documents

Profile Information

  • Communications Preferences
  • Profession and Education
  • Technical Interests
  • US & Canada: +1 800 678 4333
  • Worldwide: +1 732 981 0060
  • Contact & Support
  • About IEEE Xplore
  • Accessibility
  • Terms of Use
  • Nondiscrimination Policy
  • Privacy & Opting Out of Cookies

A not-for-profit organization, IEEE is the world's largest technical professional organization dedicated to advancing technology for the benefit of humanity. © Copyright 2024 IEEE - All rights reserved. Use of this web site signifies your agreement to the terms and conditions.

The performance of transmission pipelines on february 6th, 2023 Kahramanmaras earthquake: a series of case studies

  • Original Article
  • Open access
  • Published: 01 July 2024

Cite this article

You have full access to this open access article

case study requirements engineering

  • E. Uckan 1 ,
  • M. Aksel 1 , 2 ,
  • O. Atas 1 ,
  • S. Toprak 3 &
  • E. S. Kaya   ORCID: orcid.org/0000-0002-1098-6534 1 , 4  

The M w 7.8 earthquake that struck Kahramanmaras on February 6, 2023, caused significant damage to hydrocarbon and water transmission lines due to permanent ground deformations. Explosions occurred in the Kahramanmaras–Gaziantep Natural Gas transmission pipeline causing disruption of gas in the cities of Gaziantep and Hatay Fault Displacement Hazard. Water transmission pipelines were also damaged due to extreme fault offsets. This paper presents the findings from the earthquake affected zones. Particular attention was given to the performance of the 2600 mm diameter Duzbag–Gaziantep water transmission pipeline due to three reported challenges: (#1) The behavior of the pipe in the Duzbag tunnel, (#2) The pipe bend behavior at the fault crossing, and (#3) The pull-out of the pipe at valve room. Based on field observations, extreme damage forms at pipes were presented. A three-dimensional nonlinear numerical analysis was performed to simulate the observed damage of the reoriented water pipe at the fault crossing for Case #2. The nonlinear finite element model was able to capture the complex nature of the post-yield behavior of steel pipe as well as the damage locations along the pipe and their sequence of occurrences. As a mitigation measure for new pipes, the need for using flexible connections at critical crossings was highlighted. For existing pipes, the importance of developing secondary (by-pass) lines was emphasized.

Similar content being viewed by others

case study requirements engineering

Investigation of damage to the water network of Uki City from the 2016 Kumamoto earthquake: derivation of damage functions and construction of infrastructure loss scenarios

case study requirements engineering

Stress and displacement analysis of aerial oil & gas pipelines: A case study of Lantsang tunnel crossing project

Analysis of pipeline installation in unplanned flooding condition.

Avoid common mistakes on your manuscript.

1 Introduction

On February 6, 2023, a M w  = 7.8 earthquake struck near Pazarcik City, Kahramanmaras, in south-central Türkiye causing extensive damage in the pipeline infrastructure in the earthquake affected region. A second earthquake (M w  = 7.5) which was probably triggered by the first one, struck the nearby city Elbistan on the same day. The first earthquake was associated with a left lateral strike slip, and it was ruptured bi-laterally for about 350.0 kms along the East Anatolian Fault (EAF). Maximum fault offset was 10.0 m. The recorded Peak Ground Acceleration (PGA) and Peak Ground Velocity (PGV) were 1.4 g and 1.8 m/s, respectively, due to the soil amplification, fault directivity and basin effects (Erdik 2023 ). Figure  1 shows the hydrocarbon and water transmission pipeline routes overlaid on the PGV map and the surface rupture line. The geology and the areas of interest ( zones 1–3) of the Golbasi basin are also shown in the same figure.

figure 1

The routes of the hydrocarbon and water transmission pipelines, the EAF line, the epicenter of the earthquake, PGV map and geological map of the Golbasi Basin including geomorphology (Yönlü et al. 2017 ) Zone 1: Hydrocarbon damage, Zone 2: Water line damages Zone 3: Manhole floats due to liquefaction

The main focus of this research article is to investigate the performance of hydrocarbon and water transmission pipes under FDH in the M w  = 7.8 earthquake. The results of the reconnaissance survey, case studies, design philosophy of buried steel pipes and numerical simulation of a large diameter pipeline due fault displacement hazard (FDH) are also presented. Possible causes of damage to buried pipelines are elaborated.

Hydrocarbon transmission pipelines in the earthquake-affected region consisted of Natural Gas (NG), Crude Oil (CO) and Fuel Oil (FO) pipes. As seen in Fig.  1 , the NG pipeline was closely spaced and laid almost parallel to the EAF. It suffered extensive damage due to fault offsets at different points. Two explosions occurred in the K. Maras-Gaziantep and as a result, gas outages occurred in the cities of Gaziantep and Hatay.

Unlike water lines, exact digital data was not available for hydrocarbon lines. Therefore, they were reconstructed using available low-resolution raster images. Approximate routes of hydrocarbon lines, explosion locations, fault crossing points and critical zones (1) are shown in the same figure.

On the other hand, the exact routes of the water line were available. As seen in the figure, Duzbag–Gaziantep water transmission line was crossing the EAF at a single point near Sogutlu village ( Zone 2). Due to excessive fault offset, the pipeline ruptured and was therefore out of service for several weeks. There were two other functional lines feeding the city. Therefore, the water system remained almost operational, hence water was provided within two days in the city of Gaziantep.

Based on data provided from NASA (National Aeronautics and Space Administration 2023a , b ) the variation of the FDH along the EAF is shown in Fig.  2 . As can be seen in the map, surface ruptures were observed to be up to 10.0 m in some off-site areas. Considering that the slip rate of the EAF is 5.5 mm per year, the average Failure Displacement Hazard (FDH) during the 900-year return period can be estimated to be 5.0 m. This was consistent with field observations (Yönlü et al. 2017 ) in zone 2, shown in the Fig.  1 . Besides FDH, the region was also prone to spatial PGDs due to liquefaction induced lateral spreading and landslides. Widespread ground failures occurred in the earthquake effected region due to liquefaction hazard.

figure 2

The FDH map provided from NASA and the routes of transmission pipelines

In Fig.  3 , the liquefaction potential map obtained from NASA satellite data (National Aeronautics and Space Administration 2023b ), the routes of transmission pipelines (National Aeronautics and Space Administration 2023a ) and pipe damages due to PGD are shown. It is seen that liquefaction hazard concentrated in the southern regions of the fault line, nearby Hatay and Turkoglu. The field reconnaissance survey was mainly conducted in the northern region. Pipe damages were also observed due to liquefaction hazard in the Golbasi region. Detailed information about these damages is provided in the following section.

figure 3

Liquefaction potential around the EAF line (National Aeronautics and Space Administration 2023a ) manhole floating and NG damage due to liquefaction lateral spreading in Golbasi

2 Design philosophy of buried steel pipes under earthquakes and faulting action (FDH)

Under the influence of earthquakes, buried pipes can be subjected to large bending stresses and tensile loads. Potential earthquake hazards to buried pipelines include transient wave propagation (WP) and permanent ground displacement (PGD). Ground deformations caused by WP are generally lower than deformations caused by PGD so that damage rates are lower than PGD but are generally effective over larger areas, such as distribution networks in urban areas. Such approaches are frequently used in earthquake urban master planning to estimate spatial variation of damage rates in distribution networks for post-earthquake recovery efforts, mostly in urban areas. Empirical fragility relationships for buried pipes are defined in terms of the expected number of damages (damage rate) per km of Maximum Ground Velocity (PGV) or Peak Ground Strain (PGS). The axial strain, ε a , induced in a buried pipe by wave propagation can be approximated using the following equation (ALA 2001):

where V g : peak ground velocity generated by shaking. C S : apparent propagation velocity for seismic waves (conservatively to be 2 km per second). α : 2.0 for Cs associated with shear waves, 1.0 otherwise.

Considering that the maximum PGV recorded in the K. Maras earthquake was approximately 1.8 m/s, assuming that in the near-fault body waves dominate ( α  = 2.0), pipe axial strain can be calculated as 0.0005, which is well below the buckling strain of steel pipe. On the other hand, long and buried structures such as pipelines and tunnels are prone to damage mainly due to permanent ground deformation (PGDs) caused by liquefaction or fault displacement hazard (FDH). PGDs can usually cause localized damage to pipelines but with higher damage rates compared to the WP hazard (Nowicki Jessee et al. 2018 ; Toprak et al. 2015 ; Uckan 2014 ; Banushi et al. 2018 ; O’Rourke et al. 2015 ). Among these, the fault displacement hazard (FDH) can be considered one of the most critical one since it might result in large axial and bending strains along buried pipelines hence can cause damage in high quality transmission lines as well. Since the possible locations of surface ruptures are generally known, one can precisely estimate the post elastic response of the pipes by utilizing FE models, hence, the application of rational damage mitigation measures can be possible.

The design philosophy of buried pipes under faulting action is based on promoting tension failure. This is due to the fact that the tensile strain capacity of steel pipe is larger than compressive strain capacity. To meet this criterion, the first step is to maintain nominal tension in the pipe by adjusting the orientation angle of the pipe with respect to the fault line.

Depending on the crossing angle between the pipe axis, fault line and slip direction (left or right lateral a strike slip fault) can cause either nominal tension or nominal compression in the pipeline (Fig.  4 ). For example, when the angle ( β ) between the pipe normal and fault line is less than 90 degrees the left lateral fault slip cause shortening in the pipe whereas the same fault offset would result in nominal tension in case of a right lateral fault offset (negative crossing angle). It is important to mention that maintaining the nominal tension does not necessarily guarantee tension failure in steel pipe. This is because the pipe will also be distressed due to bending as a result of the transverse component of the fault displacement that will impose compressive strains in pipe.

figure 4

Schematic representation of strike slip fault and crossing pipe axis

Considering a pipe with a crossing angle of 90 degrees, under the progressive application of the fault displacement, compressive strains increase in small fault displacements. Whereas they tend to decrease in large displacements due to the stretching (second order effects) of the pipe (O’Rourke et al. 2015 ). Therefore, soil backfill material, D / t ratio, burial depth, steel grade and pipe wall thickness and etc. should be arranged such that the maximum compressive strain does not exceed the buckling strain of the pipe.

ALA ( 2001 ), Eurocode 8 (Standard British 2005 ) and the recent Turkish guidelines (Turkish Standardization Institute (TSE) 2019 ) address the performance criteria and damage limit states of buried pipes. The tensile strain limits of the pipes are usually considered to be 2% and 5% for 10% and 90% probabilities of failure, respectively. Limit conditions for performance-based design of buried pipes are also mentioned in the recent Turkish guidelines.

As observed in recent earthquakes, it may not be possible to avoid premature damage to steel pipes with conventional design due to the combined effects of fault mapping uncertainty, forced route selection, and excessive fault offsets. For this reason, despite its high ductility, wall fractures, wrinkling and reductions in pipe diameter may inevitably occur in the pipe. For such critical situations, it is of great importance to develop special solutions such as flexible connections that will compensate for the axial displacement and rotation demands that will occur at plastic joint locations.

3 Field reconnaissance

An exploration team from Alanya Alaaddin Keykubat University, with the support of TUBITAK (Scientific and Technological Research Council of Türkiye), contacted representatives of municipalities, public service companies and related organizations to investigate the seismic performances of water and hydrocarbon facilities (TUBITAK Field Survey Report 2023 ). The primary objective of the field trip was to identify critical regions of fault crossings. Prior to the trip, actual fault maps were overlaid on hydrocarbon lines to identify potential areas of compression zones that could create unfavorable conditions for pipes (Fig.  5 ).

figure 5

Fault crossings of natural gas, crude oil and water pipes overlaid on the PGD map provided from NASA

3.1 Hydrocarbon transmission pipes

The hydrocarbon pipeline inventory in the earthquake effected region consist of natural gas (NG), crude oil (CO) and fuel oil pipelines. Limited information could be obtained from pipe operators in terms of both pipe route and pipe damage. Based on available data, it can be seen that NE-SW oriented NG lines along the Golbasi–Turkoglu and Turkoglu–Hatay fault segments run almost parallel to the EAF line for about 100.0 kms. The NG pipelines cross the fault line several times with positive or negative orientation angles as can be seen in Fig.  5 . The approximate locations of fault crossings and explosions that caused disruption of NG in Gaziantep were also marked.

Figure  5 shows that the CO pipelines intersect the NE-SW oriented EAF at a single point near Nurdagi. In addition, the two NG lines namely, K. Maras-Gaziantep and K. Maras-Kilis cross the EAF and DAF at two points being consistent with reported explosions.

3.2 Observed pipeline damage

Due to PGDs major damage observed in NG pipelines. In many cases, especially under high compressive and tensile loads, wall tears, local buckling, wrinkles and reductions in pipe diameter occurred in the pipe wall despite of the high ductility of pipes as shown in Fig.  6 . Pipe damage was also observed in smaller diameter steel NGs transmission pipes due to liquefaction induced lateral spreading in Golbasi (Fig.  7 ). Lateral spreads were measured up to 60 cm and caused damage mainly to the smaller diameter steel NG pipes in Golbasi region. Some pipes were buckled, broken, or separated due to weld failures as shown in Fig.  8 .

figure 6

Buckling and ovalization of the NG transmssion pipelines collected from different fault crossing locations (See lidar file #SF1see lidar video file named NG_Main_Pipes)

figure 7

Liquefaction induced lateral spreading observed in Golbasi (see Fig.  1 — zone 3 and Fig.  3 )

figure 8

Weld failure and buckling of small diameter steel NG pipes due to liquefaction induced lateral spreading observed in Golbasi (see Figs. 1 , 3 and 7 ). (See lidar files #SF2 and #SF3 see lidar video files named N G1 & N G2 )

When the compressive strains exceeded the limit state of the pipe, wall wrinkling (i.e. local buckling) occur. In such cases, even though the structure becomes unstable due to formation of plastic joints, the ductile pipelines might still be able to function. However, due to the possibility of fatigue failure during the operational safety of the pipeline may not be maintained in the long term.

In addition to continuous steel lines, segmented wastewater pipelines were also seriously damaged due to sand boils as shown in Fig.  9 . Due to excessive pore water pressure, upheavelling of sewege pipeline and floating manholes were observed in Golbasi. Their locations are shown in Figs. 1 and 3 .

figure 9

Upheavelling of sewege pipeline and floating manholes due to sand boils in Golbasi (See Figs. 1 and 3 )

4 A series of case studies: the Duzbag–Gaziantep water transmission line

The 80 km long and 2600 mm of diameter steel water pipeline was one of the three main transmission lines of Gaziantep. It was consisting of support units such as pump rooms, storage tanks, valve rooms and a tunnel passage. During the earthquake, the pipe was exposed to faulting, landslide, and liquefaction hazards at different points along its route from Duzbag to the city of Gaziantep.

The locations of all three cases are shown in Fig.  10 . Case #1 refers to the Duzbag Tunnel Passage whereas Case #2 refers to the Sogutlu fault crossing and Case #3 refers to the pullout of the water pipe at the valve room#5.

figure 10

Damage locations of the Duzbag–Gaziantep transmission line (GASKI xxxx)

4.1 Case 1: the Duzbag–Gaziantep tunnel passage

The 3520.0 m long Duzbag tunnel, seen in Fig.  11 , is located near Caglayacerit Village of Kahmanmaras. The inner diameter of the tunnel which consists of reinforced concrete lining is 6.3 m. The average depth of the tunnel is 150.0 m, and the deepest part is 300.0 m. As seen in the figure, it is approximately 5.0 km away from the DAF fault and it was under the influence of secondary normal faults that cut its axis perpendicularly as shown in Fig.  11 .

figure 11

Damage locations of the Duzbag Tunnel overlaid on secondary normal faults crossing the tunnel axis (background data from MTA ( 2023 ))

The fault lines and damaged locations of the pipeline with profiles and cross-sectional views of the Duzbag tunnel were shown in Figs. 12 , 13 and 14 , respectively (GASKI xxxx).

figure 12

Soil profile at the tunnel site including the cross sectional view

figure 13

The water transmission pipeline inside the tunnel including flexible expansion joints (GASKI xxxx)

figure 14

Displaced rollers and the damaged lining of the R/C tunnel (See lidar files #SF4 and #SF5 Links for the videos named “Tunnel 1 & 2 ”)

The water transmission pipeline is placed inside the tunnel. It has been converted into a segmented line by flexible couplings and placed freely on the rollers at the bottom of the tunnel. The tunnel-pipe system was exposed to extension due to normal faulting. The axial displacement demand caused by tectonic movement was compensated by sliding supports placed along the axis (Fig.  13 ).

After the earthquake, the rollers were seen to display about 15.0 cm due to extension of the pipe. However, no damage was observed in the pipeline. On the other hand, the R/C lining, while protecting the pipeline from the tectonic action, was damaged at three points as shown in Fig.  14 .

4.2 Case 2: the Sogutlu fault crossing

The Sogutlu fault crossing can be considered one of the most critical one among all cases mentioned in the previous sections. Figure  15 shows the sketch of pipeline orientations (water and NG) in accordance with the fault line. It was crossing the EAF fault line that ruptured 4.0–5.0 m with an angle of 25 degrees with respect to the pipe axis. Hence the pipeline was subjected to compressive forces due to left lateral slip movement. The NG transmission pipe was also extending parallel to the water pipeline. The pipe was reoriented before the fault crossing by using two pipe bends.

figure 15

a The fault-pipe crossing, b the orientations of the water (blue), NG pipe (green) and fault line (red), c the layout of the pipeline with respect to the fault line (K. Maras, Sogutlu)

Due to excessive soil deformation (Fig.  16 ) caused by fault rupture, high compression loads mainly governed the circular cross-sectional shape, resulting in a change in the pipe’s geometry to an oval shape (Fig.  17 ).

figure 16

a The fault shear zone of the EAF in Sogutlu, b 4.0–5.0 m of fault offset nearby the Sogutlu fault crossing (Courtesy of GASKI)

figure 17

a Cross sectional distortion and ovalization and b wrinkling of the water transmission pipe

The overburden soil has been removed following the earthquake event in order to observe buckles and pipe damages (Fig.  18 ). According to the initial reconnaissance, there were four major wrinkles reported at the pipe bend which are two wrinkles at pipe bends, one in between these elbows and one another on the other side of the pipe. After the overburden soil had been removed, the pipeline was cut out and replaced by a new one (Fig.  20 ). Detailed lidar views (Fig.  19 ) of the damaged sections are also provided.

figure 18

a Major (wrinkle) and b minor (local buckling) damages in the water pipeline (Courtesy of GASKi)

figure 19

The 3D Lidar views of the damaged pipe wrinkling (See lidar files #SF6 and #SF7 video links named DamagePipe 1 & DamagedPipe 2 )

These damages can be seen in three-dimensional Lidar scans in Fig.  19 , which show severe changes in the pipe wall, including wrinkling and ovalization damage states. Lidar measurements have also been made in other studies (Van Ballegooy et al. 2018 ). The replacement of the pipes took a couple of weeks. However no water shortage happened in Gaziantep as there were two more transmission lines that were operational (Fig.  20 ).

figure 20

Replacement of the damaged sections of the water pipe crossing the NG pipe (Courtesy of Gaski)

4.2.1 Numerical modeling of the pipe-soil-fault system at Sogutlu fault crossing

A three-dimensional numerical model is employed to estimate the response of the pipe-soil system to faulting action. The model consists of soil-pipe interaction algorithm including shell elements (S4R) for the pipe and solid elements (C3DR8) for the surrounding soil. The pipe is subjected to net compressive force due to the orientation of the pipeline. The fault slip deformation was given to the model as quasi-static analysis. The results of the numerical analysis are compared with the observed damage forms. Mohr–Coulomb friction law is employed between the outer surface of the pipe and surrounding soil as in similar literature studies (Banushi et al. 2018 ; Vazouras et al. 2012 , 2010 ; Kaya et al. 2017 ).

Pipe operators confirmed that the undeformed water pipe had 70 degrees of pipe angle before it subjected to the fault motion (depicted using meshed finite element model) and then became around 85 degrees due to permanent ground deformation (Fig.  21 ). Numerical model has also employed with a ST44 steel grade with 14.0 mm of wall thickness as per field observations whereas stiff soil parameters were adopted as for surrounding soil conditions. The elastic module and cohesion for the surrounding soil conditions are assumed to be E  = 16 MPa and c  = 40 kPa, respectively whereas the poison’s ratio and the density for the soil are taken as ν  = 0.3 and γ  = 1.85 tons/m 3 , respectively.

figure 21

a Rupture of the Gaski–Duzbag water pipe (meshed pipe depicts the original route) b soil-pipe (detached) model used for numerical analyses

Two major wrinkle points (#1 and #2) were observed with a complete pipe wall tears at elbows as well as two minor wrinkles (#3 and #4) without any wall tearing phenomena (Fig.  22 ). As these buckles formed, the portion of pipe between wrinkles became a mechanism hence, unloaded. As observed from the figure, the axial displacement and rotation demands are accommodated primarily at the two buckles.

figure 22

Rupture of the elbow sections and the nolinear numerical model results (von-misses and plastic strain) in comparison with the observed damages of the Gaski–Duzbag water pipe line

4.3 Case 3: the pull-out of the pipe at the valve room (VR#3)

The third case corresponds to the leakage occurring in the valve room. Valve rooms are important support units used to evacuate the air that will occur during filling, emptying and operation of pipelines. They consist of solid concrete blocks partially buried in the ground and contain hydraulic valves to which the inlets and outlets of the pipe are connected. They are usually designed to be partially flexible in order to compensate for axial stresses that may occur due to operational and/or thermal effects. After the earthquake, a pressure drop in the pipeline was detected in the SCADA system by Gaziantep Municipality water systems operators.

The NASA remote sensing data revealed, liquefaction and faulting effects on the downhill side, about 1 km north of the valve room#5. Since those hazards were far from the area, it is more likely that the pull-out action was caused by the landslide action which took place approximately 200.0 m away from the site as shown in Fig.  23 .

figure 23

a Potential land slide zones around b the valve room #5 provided from NASA

Field investigations by GASKI revealed leakage at the outlet connection of valve chamber #5 (VR#5), located in an uphill area approximately 1.0–1.5 km south of the fault pipe crossing presented in case #2 (Fig.  23 ). Data provided by NASA revealed potential landslide zones within 200.0 m of the valve chamber. The 3D views, topography and potential landslide areas are also shown in the same figure.

Due to relative movement between the pipe inlet and the valve chamber, axial deformations occurred in the pipe. However, the deformation capacity of the pipe-valve connection (pipe removal joint unit) was insufficient to meet the demand. Initially, the stress in the bolted connections was released. However, it was not sufficient to release the excessive tensile force developed in the pipe. Therefore, the GASKI team decided to relieve the elastic stress accumulated in the pipeline by cutting the pipe at a point close to the valve room as shown in Fig.  24 . After the elastic energy in the pipe was released, a 40.0 cm opening in the axial direction occurred in the pipe. This gap was then filled by welding a piece of pipe as shown in Fig.  24 .

figure 24

The pull-out phenomenon at the valve room and replacement (stress releasing) of the pipe followed by cutting and welding process

5 Conclusion and discussion

The M w  = 7.8 K. Maras earthquake caused extensive damage to the pipeline infrastructure. Water and hydrocarbon lines were either severely damaged or ruptured due to PGD caused by FHD. Explosions occurred at two points of the NG transmission line due to surface ruptures causing gas outage in Gaziantep and Hatay. Although the earthquakes had negative effects on pipeline systems, they also provided us with valuable data about the post elastic behavior of the pipes. In this study, first the routes of these pipelines were overlaid on the actual fault lines provided by NASA. After determining the critical points, more detailed studies were carried out to understand the causes of damage.

More specifically the following conclusions were drawn:

NG pipelines were crossing EAF line at many points. Major damages experienced at about 18 points mainly due to FDH.

Both field surveys and remote sensing data (NASA) revealed that the mapped faults can deviate from the actual fault line. Considering that such uncertainties were quite high in recent earthquakes, FMU is thought to play an important role in the high damage rates observed in steel transmission pipes.

The east west oriented CO pipeline was crossing the EAF at a single point, close to the Nurdagi region. No serious damages were reported, and no data was available for fuel oil pipes.

The 80 km long (Duzbag–G.antep) water transmission pipeline was damaged at 3 points due to PGDs. Damaged/ruptured parts of the pipeline were repaired and made operational shortly after the earthquake. There were two other functional lines feeding the city. Therefore, the water system remained almost operational, hence water was provided within two days in the city of Gaziantep.

The pipeline in the Duzbag tunnel survived the earthquake with minor damages. Flexible joints and rollers moving in the axial direction favorable effects on the response of the pipeline. On the other hand, the tunnel lining sacrificed itself to prevent damage to the inner pipe.

The Sogutlu fault crossing was an interesting case study to understand the complex nature of the response of a large diameter pipe with elbow to extreme fault offsets. As a result of 3D nonlinear numerical model analysis, all four damage points observed in the field were able to be predicted.

It is particularly important to design smart infrastructures that include integrated systems consisting of SHM and FE modelling of pipeline systems to estimate earthquake damages after the earthquake.

In order to increase the resilience of the water systems of mega cities it is important to have alternative transmission lines as in the case of Gaziantep water system.

The best way to improve pipe behavior is rerouting. However, this may not always happen due to operational reasons. Another option is to use flexible connections at critical crossings. Such a work is also underway.

One option to improve the earthquake safety of existing critical pipeline lines is the development of specially designed bypass or secondary lines to be laid parallel to the existing line. It will be activated in case of failure of the main line and will provide controlled water flow during the repair period of the main line.

ALA (2001) Seismic fragility formulations for water systems, American Society of Civil Engineers ASCE and Federal Emergency Management Agency FEMA. www.americanlifelines.org . Accessed Jan 2002

Banushi G, Squeglia N, Thiele K (2018) Innovative analysis of a buried operating pipeline subjected to strike-slip fault movement. Soil Dyn Earthq Eng 107:234–249

Article   Google Scholar  

Erdik M et al. (2023) A preliminary report on the February 6, 2023 earthquakes in Türkiye. Research Briefs. https://temblor.net/temblor/preliminary-report-2023-turkey-earthquakes-15027/

GASKI Gaziantep water and sewerage administration archive

Kaya ES, Uckan E, O’Rourke MJ, Karamanos SA, Akbas B, Cakir F, Cheng Y (2017) Failure analysis of a welded steel pipe at Kullar fault crossing. Eng Fail Anal 71:43–62

MTA General Directorate of Mineral Research and Exploration (2023). https://www.mta.gov.tr/v3.0/hizmetler/yenilenmis-diri-fay-haritalari . Accessed Mar 2023

National Aeronautics and Space Administration (2023) About Landslides. https://gpm.nasa.gov/landslides/index.html . Accessed Mar 2023

National Aeronautics and Space Administration (2023) About surface ruptures. https://worldview.earthdata.nasa.gov/ . Accessed Mar 2023

NowickiJessee MA, Hamburger MW, Allstadt K, Wald DJ, Robeson SM, Tanyas H et al (2018) A global empirical model for near-real-time assessment of seismically induced landslides. J Geophys Res Earth Surf 123:1835–1859

O’Rourke M, Filipov E, Uckan E (2015) Towards robust fragility relations for buried segmented pipe in ground strain areas. Earthq Spectra 31(3):1839–1858

Standard British (2005) Eurocode 8: design of structures for earthquake resistance. Part 1: 1998-1

Toprak S, Nacaroğlu E, Koç AC (2015) Seismic response of underground lifeline systems. Perspect Eur Earthq Eng Seismol 2:245–263

Google Scholar  

TUBITAK Field Survey Report, Project No: 123D057; 1002-C Doğal Afetler Odaklı Saha Çalışması Acil Destek Programı

Turkish Standardization Institute (TSE) (2019) Structural design of buried pipelines under various conditions of loading—part 1: general requirements. Turkiye: Acceptance date: 30.09.2019, TS EN 1295-1

Uckan E (2014) Lifeline damage caused in the 23 October (Mw= 7.2) 2011 and 9 November (M= 5.6) 2011, Van earthquakes in eastern Turkey. In: International efforts in Lifeline earthquake Engineering, pp 51–58

Van Ballegooy S, Hamada MH, Toprak ST, Cubrinovski MC, Koç ACK, Nacaroglu EN, O’Rourke TDR (2018) Christchurch from air photo LiDAR and satellite measurements regarding. Bull Earthquake Eng. https://doi.org/10.1007/s10518-018-0317-9

Vazouras P, Karamanos SA, Dakoulas P (2010) Finite element analysis of buried steel pipelines under strike-slip fault displacements. Soil Dyn Earthq Eng 30(11):1361–1376

Vazouras P, Karamanos SA, Dakoulas P (2012) Mechanical behavior of buried steel pipelines under strike-slip and normal/reverse fault displacements. Soil Dyn Earthq Eng 41:164–180

Yönlü Ö, Altunel E, Karabacak V (2017) Geological and geomorphological evidence for the southwestern extension of the East Anatolian Fault Zone, Turkey. Earth Planet Sci Lett 469:1–14

Download references

Acknowledgements

This project was supported by the TUBITAK project No: 123D057. The authors express their gratitude to the directorate of the Gaziantep Municipality Water Systems (GASKI) for providing all necessary information and logistic support during the field visits.

Open access funding provided by the Scientific and Technological Research Council of Türkiye (TÜBİTAK). Funding was provided by TUBITAK project No: 123D057.

Author information

Authors and affiliations.

Department of Civil Engineering, Alanya Alaaddin Keykubat University, Antalya, Turkey

E. Uckan, M. Aksel, O. Atas & E. S. Kaya

Department of Civil and Mechanical Engineering, Technical University of Denmark, Lyngby, Denmark

Department of Civil Engineering, Gebze Technical University, Kocaeli, Turkey

Department of Civil and Environmental Engineering, University of California Los Angeles, Los Angeles, USA

You can also search for this author in PubMed   Google Scholar

Corresponding author

Correspondence to E. S. Kaya .

Ethics declarations

Conflict of interest.

The authors have no conflicts of interest to declare that are relevant to the content of this article. All authors certify that they have no affiliations with or involvement in any organization or entity with any financial interest or non-financial interest in the subject matter or materials discussed in this manuscript.

Additional information

Publisher's note.

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Supplementary Information

Below is the link to the electronic supplementary material.

Supplementary file1 (MP4 10436 KB)

Supplementary file2 (MP4 14413 KB)

Supplementary file3 (MP4 13083 KB)

Supplementary file4 (MP4 17834 KB)

Supplementary file5 (MP4 17223 KB)

Supplementary file6 (MP4 17998 KB)

Supplementary file7 (MP4 9205 KB)

Rights and permissions

Open Access This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons licence, and indicate if changes were made. The images or other third party material in this article are included in the article's Creative Commons licence, unless indicated otherwise in a credit line to the material. If material is not included in the article's Creative Commons licence and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this licence, visit http://creativecommons.org/licenses/by/4.0/ .

Reprints and permissions

About this article

Uckan, E., Aksel, M., Atas, O. et al. The performance of transmission pipelines on february 6th, 2023 Kahramanmaras earthquake: a series of case studies. Bull Earthquake Eng (2024). https://doi.org/10.1007/s10518-024-01957-2

Download citation

Received : 09 December 2023

Accepted : 10 June 2024

Published : 01 July 2024

DOI : https://doi.org/10.1007/s10518-024-01957-2

Share this article

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

  • Kahramanmaras earthquake
  • Hydrocarbon
  • Transmission pipelines
  • Fault crossings
  • Fault displacement hazard
  • Find a journal
  • Publish with us
  • Track your research

ACM Digital Library home

  • Advanced Search

A home hospitalization assignment and routing problem with multiple time windows, mandatory returns and perishable biological samples: : A Chilean case study

New citation alert added.

This alert has been successfully added and will be sent to:

You will be notified whenever a record that you have chosen has been cited.

To manage your alert preferences, click on the button below.

New Citation Alert!

Please log in to your account

Information & Contributors

Bibliometrics & citations, view options, recommendations, a set-covering based heuristic algorithm for the periodic vehicle routing problem.

We present a hybrid optimization algorithm for mixed-integer linear programming, embedding both heuristic and exact components. In order to validate it we use the periodic vehicle routing problem (PVRP) as a case study. This problem consists of ...

Lagrangian matheuristics for the Quadratic Multiple Knapsack Problem

The Quadratic Multiple Knapsack Problem (QMKP) is a challenging combinatorial optimization problem combining the well-known Quadratic Knapsack Problem with the Multiple Knapsack Problem. After a long stream of research devoted to ...

  • First matheuristic for the Quadratic Multiple Knapsack Problem.
  • Competitive ...

A fix-and-optimize heuristic for the high school timetabling problem

The high school timetabling is a classical combinatorial optimization problem that takes a large number of variables and constraints into account. Due to its combinatorial nature, solving medium and large instances to optimality is a challenging task. ...

Information

Published in.

Pergamon Press, Inc.

United States

Publication History

Author tags.

  • Home care services
  • Staff allocation
  • Visit routing
  • Matheuristics
  • Research-article

Contributors

Other metrics, bibliometrics, article metrics.

  • 0 Total Citations
  • 0 Total Downloads
  • Downloads (Last 12 months) 0
  • Downloads (Last 6 weeks) 0

View options

Login options.

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Share this publication link.

Copying failed.

Share on social media

Affiliations, export citations.

  • Please download or close your previous search result export first before starting a new bulk export. Preview is not available. By clicking download, a status dialog will open to start the export process. The process may take a few minutes but once it finishes a file will be downloadable from your browser. You may continue to browse the DL while the export process is in progress. Download
  • Download citation
  • Copy citation

We are preparing your search results for download ...

We will inform you here when the file is ready.

Your file of search results citations is now ready.

Your search export query has expired. Please try again.

COMMENTS

  1. PDF A Case Study in Requirements Engineering in Context of Agile

    Requirements Engineering (RE) in agile is an evolutionary process which involves active customer involvement, continuous planning, requirement reprioritization and validation through incremental product delivery. This paper describes a case study in requirements engineering in the context of agile.

  2. Requirements engineering challenges and practices in large-scale agile

    In a case study by the same authors at Ericsson, the flow of requirements in large-scale agile is studied (Heikkilä et al., 2017). Perceived benefits include increased flexibility, increased planning efficiency, and improved communication effectiveness. ... We distinguish therefore between agile requirements engineering as covered in most of ...

  3. PDF A Multi-Case Study of Agile Requirements Engineering and the Use of

    ] We performed an iterative case study at three companies and collected datathrough 14 interviews and 2 focus groups. [Results] The use of test cases as requirements poses both benefits and challenges when eliciting, validating, verifying, and managing requirements, and when used as a documented agreement. e have identified W five variants of

  4. Part 2: Developing Software Requirements, A Case Study

    Target. Timely. Velocity. This is Part 2 of a 4 part series. Part 1: Why Software Requirements In The Real World Are Hard discusses the challenges of developing requirements and what good ones might look like. This post looks at the requirements development process and its outputs on a real-world project.

  5. Emotion-oriented requirements engineering: A case study in developing a

    Case study of using emotion-oriented requirements engineering. This section introduces our case study example of a smart home technology, SofiHub, and describes our case study of using Emotion-oriented Requirements Engneering for SofiHub's analysis, feature design and validation using human trials.

  6. Requirements Engineering in Agile Software Startups

    This research employs the case study protocol as given in (Runeson and Höst 2009). Runeson and Höst presented the guidelines to conduct and report the case studies in software engineering which suggest executing five steps, i.e. case study design, data collection procedures, collecting evidence, analysis of collected data and reporting. Case ...

  7. [2308.11747] A multi-case study of agile requirements engineering and

    Context: It is an enigma that agile projects can succeed 'without requirements' when weak requirements engineering is a known cause for project failures. While agile development projects often manage well without extensive requirements test cases are commonly viewed as requirements and detailed requirements are documented as test cases. Objective: We have investigated this agile practice of ...

  8. Agile requirements engineering with prototyping: A case study

    The rise of agile software development methods has led to the abandonment of many traditional practices especially in requirements engineering (RE). Agile RE is still a relatively new research area and the growing use of agile methods in large projects is forcing companies to look for more formal practices for RE. This paper describes experiences gained from a case study of a large agile ...

  9. A case study on benefits and side-effects of agile practices in large

    A multi-case study of agile requirements engineering and the use of test cases as requirements. ContextIt is an enigma that agile projects can succeed 'without requirements' when weak requirements engineering is a known cause for project failures. While agile development projects often manage well without extensive requirements test cases are ...

  10. Requirements Engineering Process Improvement: An Industrial Case Study

    An industrial study of immediate benefits of requirements engineering process improvement at the australian center for unisys software. Empirical Software Engineering 9, 45-75 (2004) Article Google Scholar Palyagar, B.: A framework for validating process improvement in requirements engineering.

  11. CASE STUDY RESEARCH IN SOFTWARE ENGINEERING

    For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002. Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may ...

  12. A case study in requirements engineering in context of agile

    Requirements Engineering (RE) in agile is an evolutionary process which involves active customer involvement, continuous planning, requirement reprioritization and validation through incremental ...

  13. Requirements Engineering: User Stories vs. Use Cases

    User story: a short and simple description of a feature of a system from a user point of view answering the questions: Who, What, and Why. Use case: detailed description of a user interaction with a system. User stories can be utilized in many ways. Below I will list two examples. Firstly, user stories are great as Jira story ticket titles.

  14. Using ontology-based concept maps for requirements engineering: A case

    The biggest challenge that faces requirements engineering come with information representation and communication between stakeholders. This research provides a case study for applying a framework that deals with these problems by using concept maps as informal requirements representation based on ontology as formal and explicit requirements ...

  15. PDF A Case Study on Software Requirements Engineering using the ...

    A Case Study on Software Requirements Engineering using the FBI Virtual Case File Project Report N. Devadiga [email protected] Abstract—Virtual Case File (VCF) was a case management software to be developed by the United States Federal Bureau of Investigation (FBI) to replace the existing Automated Case Support (ACS) software system.

  16. Case studies in just-in-time requirements analysis

    Many successful software projects do not follow the commonly assumed best practice of engineering well-formed requirements at project inception. Instead, the requirements are captured less formally, and only fully elaborated once the implementation begins, known as `just-in-time' requirements. Given the apparent disparity between best practices and actual practices, several questions arise ...

  17. An Industrial Case Study of the Impact of Requirements Engineering on

    Downstream Development. Abstract. Requirements management is being rec ognized as one of. the most important albeit difficult phases in software. engineering. The literature repeatedly cites the ...

  18. (PDF) A Requirements Specification Case Study with ...

    Get and set requirements in the early stages of a software project is a complex task, so that several studies have been proposed to assist in the various activities of requirements engineering.

  19. Requirements Engineering with Use Cases

    B. Regnell. Published 1999. Computer Science. TLDR. This thesis investigates the role of use case modelling in requirements engineering and its relation to system verification and validation and provides further support for how to successfully apply requirements engineering with use cases as an important basis for software development. Expand.

  20. Software Requirement Engineering For Small and Medium Enterprise: A

    Case study will provide them baseline and insight about advantages and disadvantages of techniques used. ... Thousand Oaks, CA: Sage, 1995 [13] - Houdek, F. and Pohl, K. (2000): Analyzing requirements engineering processes: a case study Proceedings of the 11th International Workshop on Database and Expert Systems Applications, Greenwich, UK, 6 ...

  21. Requirements for Human-Machine-Interaction Applications in Production

    Through a literature review, the research identifies and investigates general requirements for HMIs in I5.0. Findings include ethical principles, ergonomics, adaptability, human-centered design, intuitive interaction, and effective collaboration. It also uses a case study approach to highlight potential strategies and discuss challenges.

  22. A multi-case study of agile requirements engineering and the use of

    Our case study provides insights into how this practice of using test cases as requirements (TCR) supports the main requirements activities (RQ1). The results suggest that the direct and frequent communication enforced by this practice supports eliciting, validating and managing new and changing customer requirements.

  23. Psychologically-Driven Requirements Engineering: A Case Study in

    Developing software that is accepted by its intended users can be a challenge. It is not only important to facilitate peoples tasks or achieve their functional goals, but also such technology has to meet their values, satisfy their expectations, and encourage them to accept and trust the software. In this paper, we propose a novel psychologically-driven requirements engineering approach that ...

  24. An Implementation of Integrated Approach in Product Life ...

    This research follows the design research methodology framework presented by Blessing and Chakrabarti [].The prescriptive study is based on the actual implementation of the approach to evaluate how to keep requirements in loop during complex product development using the modified V-model of product development.

  25. Processes, methods, and tools in model-based engineering—A qualitative

    Mayer G., Spieckermann S., Life-cycle of simulation models: requirements and case studies in the automotive industry, J. Simul. 4 (2010) 255-259,. Crossref. ... Guidelines for conducting and reporting case study research in software engineering, Empir. Softw. Eng. 14 (2) (2008) 131-164,. Digital Library. Google Scholar

  26. Winners Recognized for Defense Data Grand Prix 2024

    A Feat of Engineering -- and Design May 8, 2024 A Feat of Engineering -- and Design... New Space Plasma ... Case Study: South Seniors Design a Safer Way To Transport Batteries... Facebook Twitter Youtube Instagram UNIVERSITY OF SOUTH ALABAMA (251) 460-6101

  27. Analyzing requirements engineering processes: a case study

    Thorough process improvement starts with an analysis of the current situation. This is also true for requirements engineering processes. The goal of cooperation between DaimlerChrysler and the department of Software Systems Engineering at the University of Essen is to establish a framework for such RE process analysis in the area of car manufacturing. In this paper, we report on our first ...

  28. The performance of transmission pipelines on february 6th ...

    The main focus of this research article is to investigate the performance of hydrocarbon and water transmission pipes under FDH in the M w = 7.8 earthquake. The results of the reconnaissance survey, case studies, design philosophy of buried steel pipes and numerical simulation of a large diameter pipeline due fault displacement hazard (FDH) are also presented.

  29. A home hospitalization assignment and routing problem with multiple

    Therefore, for solving large instances, we design a heuristic procedure composed of a constructive heuristic coupled with an improvement heuristic, which builds on a local branching scheme. To test the applicability of our approach, we conduct a case study focusing on the actual operations of Hospital Padre Hurtado of Santiago, Chile.

  30. Numerical Study on the Dynamics of a Liquid Nitrogen Droplet Impacting

    Yu Hou received the BS and PhD degrees in Refrigerating and Cryogenic Engineering from Xi'an Jiaotong University in 1994 and 1999, respectively. From 1999 to present, he has been with the School of Energy and Power Engineering, Xi'an Jiaotong University, where he is currently a full professor and associate chair of the School of Energy and Power Engineering, Xi'an Jiaotong University.