Relevant bibliographies by topics / Agile Requirements

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Agile Requirements'

Author: Grafiati
Published: 4 June 2021
Last updated: 13 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Agile Requirements.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Agile Requirements"

1

Hołodnik-Janczura, Grażyna. "Priority of requirements in Agile." Ekonomiczne Problemy Usług 122 (2016): 259–68. http://dx.doi.org/10.18276/epu.2016.122-24.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Botaschanjan, Jewgenij, Markus Pister, and Bernhard Rumpe. "Testing agile requirements models." Journal of Zhejiang University-SCIENCE A 5, no. 5 (May 2004): 587–93. http://dx.doi.org/10.1631/jzus.2004.0587.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Orr, K. "Agile requirements: opportunity or oxymoron?" IEEE Software 21, no. 3 (May 2004): 71–73. http://dx.doi.org/10.1109/ms.2004.1293075.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Alruwaili, Fatimah, Muna Alrajhi, and Kawther Saeedi. "How Agile Development and Its Tools Support Digital Transformation." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 18 (February 1, 2019): 7440–50. http://dx.doi.org/10.24297/ijct.v18i0.8060.

Full text
Abstract:
Digital transformation is the enabler for new reform of businesses, socialites and governments. It is also the platform to the 2030 Vision in Saudi Arabia and in many other countries. Agile Manifesto succeeded to manage software development in a rapid and reliable fashion. Furthermore, incremental delivery of software release ensure that software audiences are engaged while delivering the product, their comments are considered in every function and any changes in requirements are based on imperial use of the software. This ensure the delivery of functionalities matching customer demands as well as reduce project failure risk. For this reason, Agility has been adopted in most software companies as a guaranteed and easy way to implement the digital solutions for their companies. This paper examines the characteristics of agile frameworks, such as Scrum and XP, and Agile tools, such as Jira, Agilo, and others, that facilitate digital transformation. Then compare productivity and efficacy of agile frameworks with traditional SDLC methods. The paper is concluded with the features of agile framework that enable digital transformation such as incremental development, flexible requirements and customer engagement.
APA, Harvard, Vancouver, ISO, and other styles
5

Schön, Eva-Maria, Jorge Sedeño, Manuel Mejías, Jörg Thomaschewski, and María José Escalona. "A Metamodel for Agile Requirements Engineering." Journal of Computer and Communications 07, no. 02 (2019): 1–22. http://dx.doi.org/10.4236/jcc.2019.72001.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Schön, Eva-Maria, Jorge Sedeño, Manuel Mejías, Jörg Thomaschewski, and María José Escalona. "A Metamodel for Agile Requirements Engineering." Journal of Computer and Communications 07, no. 02 (2019): 85–106. http://dx.doi.org/10.4236/jcc.2019.72007.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Ernst, Neil A., Alexander Borgida, Ivan J. Jureta, and John Mylopoulos. "Agile requirements engineering via paraconsistent reasoning." Information Systems 43 (July 2014): 100–116. http://dx.doi.org/10.1016/j.is.2013.05.008.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Rasheed, Aqsa, Bushra Zafar, Tehmina Shehryar, Naila Aiman Aslam, Muhammad Sajid, Nouman Ali, Saadat Hanif Dar, and Samina Khalid. "Requirement Engineering Challenges in Agile Software Development." Mathematical Problems in Engineering 2021 (May 8, 2021): 1–18. http://dx.doi.org/10.1155/2021/6696695.

Full text
Abstract:
Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.
APA, Harvard, Vancouver, ISO, and other styles
9

Vernickel, Kilian, and Kevin Burger. "Agile Weiterentwicklung durch Produktinkremente/Agile Further Development through Product Increments – Procedure Model for the Continuous Development of Mechatronic Products." wt Werkstattstechnik online 111, no. 06 (2021): 469–73. http://dx.doi.org/10.37544/1436-4980-2021-06-113.

Full text
Abstract:
Neue Technologien kommen mit zunehmender Geschwindigkeit auf den Markt, während Kundenanforderungen unbeständiger und weniger vorhersehbar werden. Diese VUCA-Bedingungen erfordern eine zunehmende Reaktions- und Anpas- sungsfähigkeit von Entwicklern und Prozessen. Das in diesem Beitrag präsentierte „Procedure Model for Agile Further Development“ (PM4AFD) ist hierfür ein agiler Ansatz zur Weiterentwicklung von Produkten mithilfe von Minimum Viable Product Increments (MVPIs).   New technologies are evolving rapidly, while customer requirements are becoming more volatile and less predictable. These VUCA conditions require developers and development processes to be increasingly responsive and adaptive. The Procedure Model for Agile Further Development (PM4AFD) is an agile approach for further developing products using Minimum Viable Product Increments (MVPIs).
APA, Harvard, Vancouver, ISO, and other styles
10

Naicker, Nalindren, and Manoj Maharaj. "Investigating Agile Requirements Engineering Practices in the South African Software Development Market." Journal of Computing and Information Technology 28, no. 1 (July 13, 2020): 33–58. http://dx.doi.org/10.20532/cit.2020.1004868.

Full text
Abstract:
The aim of this research study was to assess Agile RE practices in the South African software development industry and investigate secure Agile RE initiatives towards developing secure products. This qualitative research study was contextualized in seventeen South African software development companies. The researchers used structured interviews and document reviews as the primary data collection instruments. Qualitative data was analyzed inductively using content analysis. Emanating from the research were recommendations to guide a regular software developer on good Agile RE practices. The study concluded that although Agile Software Development is practiced in the South African software industry, there needs to be stricter adherences to the Agile Manifesto and Agile Security Manifesto in requirements engineering.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Agile Requirements"

1

Soundararajan, Shvetha. "Agile Requirements Generation Model: A Soft-structured Approach to Agile Requirements Engineering." Thesis, Virginia Tech, 2008. http://hdl.handle.net/10919/34511.

Full text
Abstract:
The agile principles applied to software engineering include iterative and incremental development, frequent releases of software, direct stakeholder involvement, minimal documentation and welcome changing requirements even late in the development cycle. The Agile Requirements Engineering applies the above mentioned principles to the Requirements Engineering process. Agile Requirements Engineering welcomes changing requirements even late in the development cycle. This is achieved by using the agile practice of evolutionary requirements which suggests that requirements should evolve over the course of many iterations rather than being gathered and specified upfront. Hence, changes to requirements even late in the development cycle can be accommodated easily. There is however, no real process to the agile approach to Requirements Engineering. In order to overcome this disadvantage, we propose to adapt the Requirements Generation Model (a plan-driven Requirements Engineering model) to an agile environment in order to structure the Agile Requirements Engineering process. The hybrid model named the Agile Requirements Generation Model is a soft-structured process that supports the intents of the agile approach. This model combines the best features of the Requirements Generation Model and Agile Software Development.
Master of Science
APA, Harvard, Vancouver, ISO, and other styles
2

Kola, Abhinav Ram. "Customer communication challenges in Agile Requirements Engineering." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20645.

Full text
Abstract:
Context and background: Requirements engineering(RE) is a first and a very important phase in any software development which helps in building a suitable and customer satisfactory product. In the past few years, the use of Agile software development has become popular in the industry. Customer communication plays an important role in any software development life cycle. Customers state the requirements needed to develop a product in the Requirements Engineering phase. A project is likely to fail due to problems in customer communication during the RE phase. Objective: This thesis aims to study the Customer communication challenges in Agile requirements engineering, prioritize these challenges, and also find out the mitigation strategies to overcome these challenges. Research Method: A systematic mapping study is conducted to find out the customer communication challenges. Based on the data collected from the systematic mapping study, a survey is conducted to find out the mitigation strategies to overcome the customer communication challenges faced in the RE phase and also prioritize these challenges. Results: Based on the data collected from the systematic mapping study, a total of 18 customer communication challenges are identified. In the second step, a survey is conducted based on the identified challenges. The prioritization of these challenges is done by calculating the risk analysis of the challenges from the survey data. And finally, mitigation strategies are mentioned to overcome all the identified 18 challenges.
APA, Harvard, Vancouver, ISO, and other styles
3

Zhu, Yunyun. "Requirements Engineering in an Agile Environment." Thesis, Uppsala University, Department of Information Technology, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-108027.

Full text
Abstract:

The Requirements Engineering (RE) process often dominates the quality of a project.The requirement practices in a project team are supposed to be an important part ofthe whole software development process. Today lean and agile development isbecoming more and more popular in industry. Many project teams work in an agileenvironment in order to have rapid delivery of high-quality software. Usually the workof the teams adopting an agile methodology is flexible and changeable. This indicatesthat the requirements of the projects might also be frequently changed, which is avariation to the traditional RE that relies on long and detailed documentation.

This thesis investigates how to conduct a RE process under an agile environment – sothat there exist relatively formal but agile and changeable requirements within aproject. The methods planned to be used are literature study, a case study carriedout in two software development teams in the Test Tool & Support Section at SonyEricsson Mobile Communications AB, and one pilot in each team based on the casestudy. There were 11 employees interviewed, including eight developers, two productowners and one scrum master. The evaluation on the pilots was mainly based on thefeedback from the interviewees on the pilot.

The outcome of the evaluation was that one of the teams (BRAT team) should adoptuser stories for user-related requirements, “done criteria” and non-functionalrequirements, and have the product owner to do the demonstration during the sprintreview in the future. Also, when budget allows, they should have one or morefull-time testers in the team and formal documentation of the requirements. Besidesthe suggestion for the BRAT team, QC team was suggested to have a glossary,formalize the defect description and have the product owner to ask the customersfor the feedbacks on the developers’ thoughts about the uncertain requirements.

APA, Harvard, Vancouver, ISO, and other styles
4

Rantanen, E. (Eetu). "Requirements engineering in agile software projects." Bachelor's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201705091721.

Full text
Abstract:
Many software projects are failed due to the delivery decisions that were made without adequate requirements information. In addition, the project management process including agile-oriented requirement management process has been identified as one of the four success factors in the agile software projects. Having the clear rules for requirements engineering is, therefore, an important thing for agile software projects from their success point of view. In this study, the objective is to analyze agile requirements engineering and to find out practices that are used in it. The goal is to define a continuous process to identify customer needs and translate them into software requirements in the agile software development. This goal is going to be achieved by a systematic literature review on the agile requirements engineering. For the agile software development and the traditional requirements engineering, the theory has been gathered from some basic books of the theme. The primary research question for this study is: How the customer needs will be translated into requirements in the agile software project as a continuous process? There are also two secondary research questions: 1. What are the customer needs and how can they be identified? 2. What kind of practices are used in the agile requirements engineering? Generally, the requirements engineering process includes four separate steps. First, the business usefulness of the system should be evaluated (feasibility study). After that, the requirements are discovered (elicitation and analysis)and converted into some standard form (specification). Last phase includes checking that the requirements define the system as customer wants (validation). Agile requirements engineering includes four major practices. The high-level interaction between the development team and the customer, iterative approach for the requirements engineering, prioritizing the requirements based on their business value for the customer, and eliciting also the non-functional requirements. In addition, the documentation of requirements is minimalistic in agile approaches. Results of this study can generally be applied and the model created can be utilized as a guideline when doing requirements engineering in the agile software projects
Monet ohjelmistoprojektit epäonnistuvat, koska tieto vaatimuksista on riittämätöntä toimituspäätöksiä tehdessä. Lisäksi projektinhallinnan prosessi, johon sisältyy ketterä vaatimustenhallinnan prosessi, on tunnistettu yhdeksi neljästä ketterien ohjelmistoprojektien menestystekijästä. Tämän takia ketterien ohjelmistoprojektien onnistumiseksi on tärkeää, että vaatimusmäärittelylle on selkeät ohjeet. Tämän tutkimuksen tarkoituksena on analysoida ketterää vaatimusmäärittelyä ja löytää siinä yleisesti käytettyjä tapoja. Tavoitteena on määrittää jatkuva prosessi, jossa asiakkaan tarpeet tunnistetaan ja käännetään ohjelmiston vaatimuksiksi ketterässä ohjelmistokehityksessä. Tavoitteeseen pyritään tekemällä systemaattinen kirjallisuuskatsaus ketterään vaatimusmäärittelyyn. Ketterää ohjelmistokehitystä sekä perinteistä vaatimusmäärittelyä käsitellään muutaman perusteoksen pohjalta. Tutkimuksen ylätason tutkimuskysymys on: Kuinka asiakkaan tarpeet käännetään vaatimuksiksi jatkuvana prosessina ketterissä ohjelmistoprojekteissa? Lisäksi tutkimuksella on kaksi alatason tutkimuskysymystä: 1. Mitä asiakkaan tarpeet ovat ja kuinka ne tunnistetaan? 2. Minkälaisia tapoja ketterässä vaatimusmäärittelyssä käytetään? Yleinen vaatimusmäärittelyprosessi sisältää neljä vaihetta. Ensin arvioidaan järjestelmän liiketoiminnallinen tarpeellisuus (kannattavuusselvitys). Tämän jälkeen etsitään vaatimuksia (selvitys ja analyysi) ja käännetään ne johonkin standardimuotoon (spesifikaatio). Viimeisessä vaiheessa tarkistetaan, että vaatimukset määrittävät järjestelmän juuri asiakkaan haluamalla tavalla (validointi). Ketterässä vaatimusmäärittelyssä on neljä yleistä käytäntöä. Korkean tason kanssakäyminen asiakkaan ja kehitystiimin välillä, iteratiivinen eli toistava lähestymistapa vaatimusmäärittelyyn, vaatimusten priorisointi perustuen asiakkaalle syntyvään arvoon ja myös ei-funktionaalisten vaatimusten tunnistus. Lisäksi voidaan sanoa, että vaatimusten dokumentointi ketterissä menetelmissä on vähäistä. Tämän tutkimuksen tuloksia voidaan yleisesti ottaen hyödyntää ja kehitettyä mallia voidaan käyttää vaatimusmäärittelyn ohjenuorana ketterissä ohjelmistoprojekteissa
APA, Harvard, Vancouver, ISO, and other styles
5

Lagré, Mårten. "Varför arbetar vissa utvecklingsteam agilt med kravhantering och vissa inte? : En fallstudie på Lantmäteriet." Thesis, Högskolan Dalarna, Informatik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:du-25514.

Full text
Abstract:
Kravhantering inom systemutveckling utgör basen för vad som ska utvecklas. Agila systemutvecklingsmetoder blir vanligare för varje dag som går. Det har dock ofta visat sig finnas utmaningar med hur man anpassar just kravhanteringen till de agila metoderna. Verksamheter har olika förutsättningar för att arbeta agilt. Lantmäteriet i Gävle uttryckte ett behov att undersöka varför den agila praxis man hade inte följdes av alla utvecklingsteam i samband med kravhanteringen. Syftet med denna uppsats var därför att undersöka varför vissa utvecklingteam i en verksamhet arbetade agilt med sin kravhantering medan vissa inte gjorde det. För att undersöka detta utförde jag en fallstudie där jag med hjälp av enkäter och intervjuer samlade in data från både utvecklare och personer på verksamhetssidan som var inblandade i kravhanteringen. Resultaten visade att orsakerna till att en agil kravhantering fungerade så olika var flera. Genom att använda en tematisk analys kunde jag urskilja några framträdande orsaker. Kommunikation och flexibilitet samt kunskap och förståelse för olika perspektiv var teman som utgjorde positiva faktorer. De teman som istället utgjorde negativa faktorer var bland andra otydliga roller, brist på direktiv, en övertro till metoder och processer, osynk mellan verksamhet och IT, prioriteringsproblem, förvaltningsplaner, attityder och IT-arkitektur.
Requirements engineering within software development is the foundation of what needs to be developed. Agile methods in software development become more common every day. It has however often been shown that there are certain challenges with how to adopt the requirements engineering to the agile methodology. Businesses have different preconditions for agile methods. Lantmäteriet in Gävle had a need to examine why not all the developing teams followed agile methods within the requirements engineering process. The purpose with this thesis was thus to examine why some developing teams in an organization worked in an agile manner with the requirements engineering, and some did not. To do this I performed a case study where I collected data through questionnaires and interviews from both developers and people from the business side. The results showed that the reasons for these differences were multiple. Communication and flexibility, and knowledge and understanding for different perspectives were the positive factors. The themes that hindered an agile way of working were, among others, unclear roles, lack of direction, too much reliance on methods and processes, discrepancy between business and IT, prioritizing issues, management plans, attitudes and IT architecture.
APA, Harvard, Vancouver, ISO, and other styles
6

Robles, Luna Esteban. "Agile managing of web requirements with WebSpec." Tesis, Universidad de Alicante, 2011. http://hdl.handle.net/10915/4197.

Full text
Abstract:
Web application development is a complex and time consuming process that involves di erent stakeholders (ranging from customers to developers); these applications have some unique characteristics like navigational access to information, sophisticated interaction features, etc. However, there have been few proposals to represent those requirements that are speci c to Web applications. Consequently, validation of requirements (e.g. in acceptance tests) is usually informal, and as a result troublesome. To overcome these problems, this PhD Thesis proposes WebSpec, a domain speci c language for specifying the most relevant and characteristic requirements of Web applications: those involving interaction and navigation. We describe WebSpec diagrams, discussing their abstraction and expressive power. As part of this work, we have created a test driven model based approach called WebTDD that gives a good framework for the language. Using the language with this approach we have test several of its features such as automatic test generation, management of changes in requirements, and improving the understanding of the diagrams through application simulation. This PhD Thesis is composed of a set of published and submitted papers. In order to write this PhD Thesis as a collection of papers, several requirements must be taken into account as stated by the University of Alicante. With regard to the content of the PhD Thesis, it must speci cally include a summary which is devoted to the description of initial hypotheses, research objectives, and the collection of publications itself, thus justifying its coherence. It should be underlined that this summary of the PhD Thesis must also include research results and nal conclusions. This summary corresponds to part I of this PhD Thesis (chapter 1 has been written in Spanish while chapter 2 is in English). This work has been partially supported by the following projects: MANTRA (GV/2011/035) from Valencia Ministry, MANTRA (GRE09-17) from the University of Alicante and by the MESOLAP (TIN2010-14860) project from the Spanish Ministry of Education and Science.
Este trabajo ha sido parcialmente financiado por los siguientes proyectos: Mantra (GV/2011/035), Ministerio de Valencia, MANTRA (GRE09-17) de la Universidad de Alicante y por el MESOLAP (TIN2010-14860) proyecto del Ministerio de Educación y Ciencia de España.
APA, Harvard, Vancouver, ISO, and other styles
7

Al-kfairy, Mousa. "Toward Agile development methods & Non-functional requirements." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-54656.

Full text
Abstract:
In this thesis, we tried to solve those problems by adapting agile development methods with Non-functional requirements-framework (NFR-Framework). In this thesis, we have inspected many research papers, and we have met industrial experts for feedback regarding our theoretical results. As a result of the inspection, we have been able to adapt agile development methods (extreme programming (XP)) with NFR-framework. We use XP since it is more practically oriented process than other agile development methods. In the first try for this process model, we got three alternatives for applying it. The first one is based on collecting all NFRs from the beginning of the development process. The second one is based on updating the SIG (software interdependency graph) every time we have new functional requirements (FR) and the third one is based on the incremental nature of agile development methods. Each one of these alternatives has it is own advantages and disadvantages. We tried to extract those advantages and disadvantages by brainstorming and reading research papers. The most important issue in all of the three alternatives is the applicability. Finally we got industrial feedback regarding all of them. As a result of the industrial feedback, we were able to find another alternative of how to apply the process model which is presented in 7.2.
APA, Harvard, Vancouver, ISO, and other styles
8

Karlsson, Josefine. "Agile in a small project : A refinement of a framework for agile requirements engineering." Thesis, Örebro universitet, Handelshögskolan vid Örebro Universitet, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-37681.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Farid, Weam Mohamed. "The NORMAP Methodology: Non-functional Requirements Modeling for Agile Processes." NSUWorks, 2011. http://nsuworks.nova.edu/gscis_etd/147.

Full text
Abstract:
Agile software development methodologies, such as Scrum, have gained tremendous popularity and proven successful in quickly delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately identified, modeled, and linked Non-Functional Requirements (NFRs) with FRs in early development phases. Researchers agree that NFRs have been generally ignored in conventional methodologies, especially ignored in agile environments. This dissertation develops a conceptual framework for NFR modeling in agile processes. The proposed Non-functional Requirements Modeling for Agile Processes (NORMAP) Methodology investigated the feasibility of identifying, linking, and modeling Agile Loose Cases (ALCs) with Agile Use Cases (AUCs) and Agile Choose Cases (ACCs). AUCs are newly proposed hybrid of use cases and agile user stories. ALCs are proposed—loosely—defined agile NFRs. ACCs are proposed potential solutions (operationalizations) for ALCs. A lightweight adapted version of the NFR Framework was developed including 25 important NFRs selected out of 161 for this study. Further, an enhanced risk-driven agile requirements implementation sequence (NORPLAN) was developed and visualized as a tree-like view (NORVIEW). The NORMAP Methodology was validated through developing NORMATIC--a Java-based agile visual modeling simulation tool and two case studies. NORMATIC utilized Natural Language Processing (NLP) tools to parse requirement sentences and identify potential ALCs. The first case study utilized the Predictor Models in Software Engineering (PROMISE) dataset used in NFRs classification. NORMAP successfully parsed and classified ALCs for 529 out of 607 (87.15%) independent user requirements. The second case study utilized the European Union eProcurement System’s 26 functional requirements. NORMAP successfully parsed and classified ALCs for 50 out of 57 sentences that included possible ALCs (87.71%). Furthermore, requirements quality and project management metrics were used to calculate a risk-driven requirements implementation sequence using three priority schemes. Results showed that Riskiest-Requirements-First priority scheme planned requirements in 17 sprints--two months earlier than the Highest-Business-Value-First scheme (21 sprints) and one month earlier than the Riskiest-Requirements-Last scheme (19 sprints). Agile communities can potentially benefit from the NORMAP Methodology by utilizing a systematic and risk-driven lightweight engineering process to visually model and plan NFRs as first-class artifacts in agile environments.
APA, Harvard, Vancouver, ISO, and other styles
10

Knudsen, Anders Nordli. "Agile Security Requirements : A master study into their application." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2014. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-26763.

Full text
Abstract:
Agile is the contemporary development practice of choice but security has been claimed as a challenge for it. This thesis investigates whether agile methods can be used for security-critical software and if the reason why the majority of Norwegian companies deviate from the agile methodology in their development is linked to security, by looking at the security requirements. A questionnaire and interviews of Norwegian companies were undertaken, and while the questionnaire did not yield any results the data from the interview indicate that the reasons for not conforming to the methodology appear to be related to security work and assurance. Agile is implied by the limited sample size to not only be useable for security-critical software but may be the best option in projects with uncertainty to the system and changing security requirements.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Agile Requirements"

1

Agile software requirements: Lean requirements practices for teams, programs, and the enterprise. Upper Saddle River, NJ: Addison-Wesley, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

author, Harrington Lisa M., Terry Tara L. author, Massey H. G. author, and Project Air Force (U.S.), eds. Air Force manpower requirements and component mix: A focus on agile combat support. Santa Monica, Calif: RAND Corporation, 2014.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Tripp, Robert S. A framework for evolving agile combat support concepts to meet NATO Reaction Air Force operational requirements. Santa Monica, CA: RAND, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Frantzen, Trond. Rapid Agile Business System Analysis: The PowerStart Approach -- how to complete business system requirements faster than ever before. [Overland Park, KS]: The Institute for Systems Analysis, 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Katsuyama, Kōtarō. Jōhō shisutemu ni taisuru yōkyū shiyō no henka ni taiōsuru sofutowea gijutsu: Software technologies for adapting requirement changes of information systems. Tōkyō: Kenkyū Kaihatsu Senryaku Sentā, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Blokdyk, Gerardus. Agile Communication Environment: Standard Requirements. CreateSpace Independent Publishing Platform, 2018.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Beyond Requirements: Analysis with an Agile Mindset. Addison-Wesley Professional, 2015.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Executable Specifications With Scrum A Practical Guide To Agile Requirements Discovery. Pearson Education (US), 2013.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Molnar, Louis. Agile Requirements & User Stories: Extreme Programming Practices for Project Managers and Business Analysts. Multi-Media Publications Inc., 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Agile Project Management: How to Succeed in the Face of Changing Project Requirements. AMACOM/American Management Association, 2003.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Agile Requirements"

1

Carter, Eric, and Matthew Hurst. "Changing Requirements." In Agile Machine Learning, 25–58. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5107-2_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Croitoru, Haniel. "Information Requirements." In Agile Office 365, 243–48. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-4081-6_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Pflüger, André, and Stefan Queins. "Agile und andere Vorgehensweisen." In Requirements-Engineering und -Management, 51–69. München: Carl Hanser Verlag GmbH & Co. KG, 2014. http://dx.doi.org/10.3139/9783446443136.004.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Moreira, Mario E. "Establishing Your Requirements Tree." In The Agile Enterprise, 175–83. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2391-8_15.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mirtalebi, Mohsen. "Requirements Model." In Embedded Systems Architecture for Agile Development, 91–123. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3051-0_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Cline, Alan. "Requirements Thread." In Agile Development in the Real World, 165–95. Berkeley, CA: Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-1679-8_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Sim, S. E., and R. E. Gallardo-Valencia. "Performative and Lexical Knowledge Sharing in Agile Requirements." In Managing Requirements Knowledge, 199–219. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-34419-0_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Cursino, Rodrigo, João Farias, Maria Lancastre, and Wylliams Santos. "Agile Requirements Validation in Brazilian Software Development Companies: A Survey." In Agile Methods, 3–18. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-14310-7_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Carniel, Carlos Andrei, and Raquel Aparecida Pegoraro. "Metamodel for Requirements Traceability and Impact Analysis on Agile Methods." In Agile Methods, 105–17. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-73673-0_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Gaikwad, Vandana, Prasanna Joeg, and Shashank Joshi. "AgileRE: Agile Requirements Management Tool." In Advances in Intelligent Systems and Computing, 236–49. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-67618-0_22.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Agile Requirements"

1

Brataas, Gunnar, and Tor Erlend Fægri. "Agile Scalability Requirements." In ICPE '17: ACM/SPEC International Conference on Performance Engineering. New York, NY, USA: ACM, 2017. http://dx.doi.org/10.1145/3030207.3030240.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Zajac-Woodie, Diane. "Beyond Requirements Dictator: How Agile Helped a Business Analyst Discover Her Real Value." In 2013 Agile Conference (AGILE). IEEE, 2013. http://dx.doi.org/10.1109/agile.2013.14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Connolly, David, Frank Keenan, and Brendan Ryder. "Tag Oriented Agile Requirements Identification." In 2008 15th Annual IEEE International Conference on Engineering of Computer Based Systems (ECBS). IEEE, 2008. http://dx.doi.org/10.1109/ecbs.2008.26.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Albuquerque, Danyllo, Everton Guimaraes, Mirko Perkusich, Alexandre Costa, Emanuel Dantas, Felipe Ramos, and Hyggo Almeida. "Defining agile requirements change management." In SAC '20: The 35th ACM/SIGAPP Symposium on Applied Computing. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3341105.3374095.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Ghanam, Yaser, and Frank Maurer. "Using Acceptance Tests for Incremental Elicitation of Variability in Requirements: An Observational Study." In 2011 AGILE Conference. IEEE, 2011. http://dx.doi.org/10.1109/agile.2011.21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Dalpiaz, Fabiano, and Sjaak Brinkkemper. "Agile Requirements Engineering with User Stories." In 2018 IEEE 26th International Requirements Engineering Conference (RE). IEEE, 2018. http://dx.doi.org/10.1109/re.2018.00075.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Elghariani, Kaiss, and Nazri Kama. "Review on Agile requirements engineering challenges." In 2016 3rd International Conference on Computer and Information Sciences (ICCOINS). IEEE, 2016. http://dx.doi.org/10.1109/iccoins.2016.7783267.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Boness, Kenneth, and Rachel Harrison. "Goal Sketching: Towards Agile Requirements Engineering." In International Conference on Software Engineering Advances (ICSEA 2007). IEEE, 2007. http://dx.doi.org/10.1109/icsea.2007.36.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Blasquez, Isabelle, and Hervé Leblanc. "A guideline to teach agile requirements." In ITiCSE '18: 23rd Annual ACM Conference on Innovation and Technology in Computer Science Education. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3197091.3205838.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Santos, Nuno, Jaime Pereira, Francisco Morais, Júlio Barros, Nuno Ferreira, and Ricardo J. Machado. "Incremental architectural requirements for agile modeling." In XP '18 Companion: 19th International Conference on Agile Software Development. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3234152.3234166.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Agile Requirements"

1

Nidiffer, Kenneth E., Suzanne M. Miller, and David Carney. Potential Use of Agile Methods in Selected DoD Acquisitions: Requirements Development and Management. Fort Belvoir, VA: Defense Technical Information Center, April 2014. http://dx.doi.org/10.21236/ada609864.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Frantz, Frederick K., and John Sallustio. National Institute of Justice Center Requirements Definition, Technical Assistance, Agile Test and Evaluation and Cyber Science Analysis. Fort Belvoir, VA: Defense Technical Information Center, December 2003. http://dx.doi.org/10.21236/ada420882.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

DeCarlo, Robert L., and Jr. National Institute of Justice (NIJ) Requirements Definition, Advanced Generation Interoperability for Law Enforcement (AGILE) Program Development, and Technical Assistance. Fort Belvoir, VA: Defense Technical Information Center, February 2001. http://dx.doi.org/10.21236/ada387258.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

TEAM (Technologies Enabling Agile Manufacturing) macro planner requirements guide: Version 1.0. Office of Scientific and Technical Information (OSTI), March 1995. http://dx.doi.org/10.2172/161469.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

TEAM (Technologies Enabling Agile Manufacturing) shop floor control requirements guide: Version 1.0. Office of Scientific and Technical Information (OSTI), March 1995. http://dx.doi.org/10.2172/161468.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Agile Requirements' for particular source types:
Journal articles Dissertations / Theses
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography