Journal articles: '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

11

KÖSE, Büşra Özdenizci. "RECENT AGILE REQUIREMENT ENGINEERING PRACTICES IN IT PROJECTS: A CASE ANALYSIS." Business & Management Studies: An International Journal 7, no. 4 (September 24, 2019): 1776–805. http://dx.doi.org/10.15295/bmij.v7i4.1214.

Full text

Abstract:

Today, the implementation of high quality and efficient Requirement Engineering (RE) practices in agile software development projects, is gaining great importance. Practitioners and researchers seeks for lighter RE practices that can handle the issues of abstract, unclear and changing requirements, and at the same time that can satisfy the Agile Manifesto philosophy. This study examines importance of RE practices in agile software development projects, and explores which aspects of the RE practices are perceived as most critical and how such aspects are adapted in practice today through two different agile software development projects of a case organization. This study aims to contribute agile RE literature by providing an interpretive analysis on perception of agile RE practices from different perspectives (agile team members, product owners, some top executives). Within this context, this study draws lessons from case studies and presents beneficial agile RE guidelines for practitioners and researchers.

APA, Harvard, Vancouver, ISO, and other styles

12

Cao, Lan, and Balasubramaniam Ramesh. "Agile Requirements Engineering Practices: An Empirical Study." IEEE Software 25, no. 1 (January 2008): 60–67. http://dx.doi.org/10.1109/ms.2008.1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Weston, R. H. "Integration infrastructure requirements for agile manufacturing systems." Proceedings of the Institution of Mechanical Engineers, Part B: Journal of Engineering Manufacture 212, no. 6 (June 1, 1998): 423–37. http://dx.doi.org/10.1243/0954405981515734.

Full text

Abstract:

Current approaches to the design and construction of enterprise systems lead to fixed interdependences between valuable resources. This constrains resource reuse and the agility of systems, often preventing close alignment between system behaviour and business process requirements. This paper describes the important role that software-based integration infrastructures and integration structures can play respectively in supporting and organizing system behaviour in a way that facilitates system extension and change. Also described are different types of reusable software component and their infrastructural needs. These components are likely to become common building blocks of next-generation agile manufacturing systems. The paper illustrates the concepts described by reporting on research in the MSI Research Institute which is producing proof-of-concept agile manufacturing systems in collaboration with UK end user and vendor companies.

APA, Harvard, Vancouver, ISO, and other styles

14

Schön, Eva-Maria, Jörg Thomaschewski, and María José Escalona. "Agile Requirements Engineering: A systematic literature review." Computer Standards & Interfaces 49 (January 2017): 79–91. http://dx.doi.org/10.1016/j.csi.2016.08.011.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Kunwar, Sundar. "Scenario Based Requirement Engineering (SBRE) in eXtreme Programming (XP) through Agile Modelling (AM)." SCITECH Nepal 13, no. 1 (September 30, 2018): 9–15. http://dx.doi.org/10.3126/scitech.v13i1.23496.

Full text

Abstract:

Software development methodologies have been enhancing significantly all the time and have drawn the attention of software professionals from past few years. The software development methodologies are expanding rigorously with wide range of diverse fields and have become more complex demanding the agility to rapidly changing needs of the customers. As a result, agile software development methodologies have evolved and gaining popularity day by day. Agile software development methodologies have come up with modifications demanded in traditional software development process to make them faster; more flexible, light weighted and productive. Extreme Programming (XP) is one of the well-known agile software development methodologies and is driven by a set of values including simplicity, communication, feedback and courage. Planning game, very short release stories and test first coding are some interesting extreme practices of XP; however, it is criticized for some deficiencies like light weight requirement, onsite customer, pair programming and so on. The study has only focused on only one of the most criticized extreme practice-lightweight requirement and has followed agile modelling approach to make improvement on requirement engineering process in XP. Requirements are the user stories that consist of a few sentences (1-3 sentences) written on an index card which describes the functionality given by single onsite customer in XP. There is lack of analysis of stakeholders and their roles in requirement process. Therefore, it is very difficult to know the specific requirements of the specific stakeholder in XP. This means that the requirement engineering process is incomplete in XP. This may result high chances of providing deficient requirements. Agile Modelling (AM) is the chaordic practice based methodology for effective modelling. The interesting part of AM is that it does not tell how to model, but tells about how to be effective as modellers. A Scenario Based Requirement Engineering (SERE) is proposed using AM as alternative to light weighted requirement which one of the most criticized extreme practice of XP. SERE is the implemented description of techniques that helps to understand the task related activities and also facilitates communication among stakeholders and experts. Stakeholders are analysed for understanding a system by identifying the stakeholders in the system and assessing their respective requirements and influence on the system. This will help to get better requirements for system development, but still needs to be validated.

APA, Harvard, Vancouver, ISO, and other styles

16

Ferreira Martins, Hugo, Antônio Carvalho de Oliveira Junior, Edna Dias Canedo, Ricardo Ajax Dias Kosloski, Roberto Ávila Paldês, and Edgard Costa Oliveira. "Design Thinking: Challenges for Software Requirements Elicitation." Information 10, no. 12 (November 28, 2019): 371. http://dx.doi.org/10.3390/info10120371.

Full text

Abstract:

Agile methods fit well for software development teams in the requirements elicitation activities. It has brought challenges to organizations in adopting the existing traditional methods, as well as new ones. Design Thinking has been used as a requirements elicitation technique and immersion in the process areas, which brings the client closer to the software project team and enables the creation of better projects. With the use of data triangulation, this paper brings a literature review that collected the challenges in software requirements elicitation in agile methodologies and the use of Design Thinking. The result gave way to a case study in a Brazilian public organization project, via user workshop questionnaire with 20 items, applied during the study, in order to identify the practice of Design Thinking in this context. We propose here an overview of 13 studied challenges, from which eight presented strong evidence of contribution (stakeholders involvement, requirements definition and validation, schedule, planning, requirement details and prioritization, and interdependence), three presented partial evidence of contribution and two were not eligible for conclusions (non-functional requirements, use of artifacts, and change of requirements). The main output of this work is to present an analysis of the use of Design Thinking to see if it fits properly to be used as a means of solving the challenges of elicitation of software requirements when using agile methods.

APA, Harvard, Vancouver, ISO, and other styles

17

Levy, Meira, Irit Hadar, and Itzhak Aviv. "Agile-Based Education for Teaching an Agile Requirements Engineering Methodology for Knowledge Management." Sustainability 13, no. 5 (March 6, 2021): 2853. http://dx.doi.org/10.3390/su13052853.

Full text

Abstract:

The importance of the role that knowledge management (KM) plays in the success of knowledge-intensive organizations has long been acknowledged. However, requirements engineering (RE) methods for KM solutions still lack maturity, as do the educational programs in this domain. In this paper, an agile-based educational method for teaching RE for KM solutions, specifically an agile KM RE methodology (AKM-REM), is proposed. The paper reports a teaching experience, in which 17 teams of graduate students learned and implemented AKM-REM, each in a different real-life case study. Data were collected via class observations and from the students’ submitted projects and underwent qualitative content analysis. The findings demonstrate the manner in which AKM-REM creates a culture of collaboration, trust, and reflection, fostering the dynamic and flexible organization that is required in today’s competitive business environment. The contribution of this paper is fourfold. First, it presents an extension of the research on agile-based RE for KM solutions as a specialized area. Second, it presents an extension of an existing method KM-REM along the agile principles. Third, it provides means for agile-based education for analyzing and addressing KM challenges effectively. Finally, it describes the importance of agile KM RE in the context of sustainability.

APA, Harvard, Vancouver, ISO, and other styles

18

Rahman, Nayem, Dale Rutz, and Shameem Akhter. "Agile Development in Data Warehousing." International Journal of Business Intelligence Research 2, no. 3 (July 2011): 64–77. http://dx.doi.org/10.4018/jbir.2011070105.

Full text

Abstract:

Traditional data warehouse projects follow a waterfall development model in which the project goes through distinct phases such as requirements gathering, design, development, testing, deployment, and stabilization. However, both business requirements and technology are complex in nature and the waterfall model can take six to nine months to fully implement a solution; by then business as well as technology has often changed considerably. The result is disappointed stakeholders and frustrated development teams. Agile development implements projects in an iterative fashion. Also known as the sixty percent solution, the agile approach seeks to deliver more than half of the user requirements in the initial release, with refinements coming in a series of subsequent releases which are scheduled at regular intervals. An agile data warehousing approach greatly increases the likelihood of successful implementation on time and within budget. This article discusses agile development methodologies in data warehousing and business intelligence, implications of the agile methodology, managing changes in data warehouses given frequent change in business intelligence (BI) requirements, and demonstrates the impact of agility on the business.

APA, Harvard, Vancouver, ISO, and other styles

19

Et.al, Mohammed Saleh. "Critical Success Factors and Challenges in Agile Requirements Engineering." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 11, 2021): 1670–82. http://dx.doi.org/10.17762/turcomat.v12i3.989.

Full text

Abstract:

Nowadays, the requirements of the software are changing rapidly in order to meet clients’ needs, which increases the complexity of developing software. Thus, Agile requirements engineering has arisen and it focuses on how to deal with the increasing changes in software requirements by gathering requirements iteratively and collaboratively with the clients. Thus, the clients’ satisfaction could be met more easily. On the other side, researchers have tried to improve agile requirements engineering from time to time, however, there are still limitations and challenges faced, which need more attention. Thus, this study is conducted by performing a systematic literature review technique to investigate the challenges, critical success factors, and the topics that need more attention in the agile requirements engineering field. In the beginning, the study obtained 178 articles related to this topic which were published from 2002 until 2019. After a thorough analysis of the articles, the study reviewed the ten (10) challenges and the proposed solutions that mentioned in the previous studies. Besides that, the study found six (6) critical success factors, and highlighted four (4) topics that need more attention from the researchers in future studies in agile requirements engineering.

APA, Harvard, Vancouver, ISO, and other styles

20

Thomas, Meetu, and Mali Senapathi. "Agile Requirements Engineering: An Empirical Analysis and Evidence from a Tertiary Education Context." Issues in Informing Science and Information Technology 16 (2019): 097–112. http://dx.doi.org/10.28945/4286.

Full text

Abstract:

Aim/Purpose: The study describes empirical research into agile Requirements Engineering (RE) practices based on an analysis of data collected in a large higher education organization. Background: Requirements Engineering (RE) in agile development contexts is considerably different than in traditional software development. The field of agile RE is still nascent where there is a need to evaluate its impact in real-world settings. Methodology: Using a case study methodology, the study involved interviewing nine experienced software practitioners who reflected on the use and implementation of various agile RE practices in two software development projects of a student management system. Contribution: The primary contribution of the paper is the evaluation of agile RE practices in a large tertiary educational organization. Based on the analysis of the data, it provides valuable insights into the practice of agile RE in a specific context (i.e., education), but just as importantly, the ones that were omitted or replaced with others and why. Findings: While the evolutionary and iterative approach to defining requirements was followed in general, not all agile practices could be fully adhered to in the case organization. Although face-to-face communication with the customers has been recognized as one the most important agile RE practices, it was one of the most difficult practices to achieve with a large and diverse customer base. Addressing people issues (e.g., resistance to change, thinking, and mindset) was found to be a key driver to following the iterative RE process effectively. Contrary to the value-based approach advocated in the literature, the value-based approach was not strictly adhered to in requirements prioritization. Continuous integration was perceived to be a more beneficial practice than prototyping, as it allows frequent integration of code and facilitates delivering working software when necessary. Recommendations for Practitioners: Our study has important implications for practitioners. Based on our empirical analysis, we provide specific recommendations for effective implementation of agile RE practices. For example, our findings suggest that practitioners could address the challenges associated with limited face-to-face communication challenges by producing flexible, accessible, and electronic documentation to enable communication. Recommendations for Researchers: Researchers can use the identified agile RE practices and their variants to per-form in-depth investigations into agile requirements engineering in other educational contexts. Impact on Society: There are a number of new technologies that offer exciting new opportunities that can be explored to maximize the benefits of agile and other requirements techniques. Future Research: Future research could conduct case studies in different contexts and thus con-tribute to developing bundles or collections of practices to improve software development processes in specific contexts.

APA, Harvard, Vancouver, ISO, and other styles

21

Kumari, Uma. "Agile Practices in Indian Organizations." Oriental journal of computer science and technology 10, no. 2 (May 30, 2017): 422–28. http://dx.doi.org/10.13005/ojcst/10.02.24.

Full text

Abstract:

Agile software development is a conceptual framework that promotes development using iterations throughout the project development. In software development Agile means quick moving. For the satisfaction of customer and to cope up customer frequent changed requirements, heavyweight methodology is being kicked. Two major challenges in software development are high quality software production and stakeholder requirement meeting. An independent online web based survey; interview survey and questionnaire survey were conducted. Motive was to find the total percentage of users in India, who are using Agile and it was tried to find out “does it increase the productivity, quality and cost of software?” Hypothesis has been proved using statistical one way ANOVA method. Different Hypothesis that are designed

APA, Harvard, Vancouver, ISO, and other styles

22

Caballero, Leydi, Ana M. Moreno, and Ahmed Seffah. "How Agile Developers Integrate User-Centered Design Into Their Processes: A Literature Review." International Journal of Software Engineering and Knowledge Engineering 26, no. 08 (October 2016): 1175–201. http://dx.doi.org/10.1142/s0218194016500418.

Full text

Abstract:

The lack of user engagement, the absence of user feedback, incomplete and continuously changing user requirements are among the critical concerns that cause projects to fail. User-centered design (UCD) and agile software development are two iterative approaches that have been proposed to overcome such concerns. UCD is a design process focusing on user research, user interface design and usability evaluation. Introduced by software engineering practitioners, agile refers to a number of iterative and incremental software development practices that emphasize people’s needs, communication between developers and stakeholders and the ability to adapt to change. In both the agile and UCD communities, however, a full understanding of user requirements is often seen as incompatible with early and quick development iterations. We performed a literature review aiming to identify how agile teams have integrated UCD tools into their agile software development process to a better understanding of the user requirements without losing sight of the agile values and principles. UCD tools adaptations and minimal-up-front design applied in agile development are among the approaches discovered in this study. The findings could lead to a comprehensive user-centric software engineering that will overcome inherent problems faced by agile teams to understand user needs, priorities and goals.

APA, Harvard, Vancouver, ISO, and other styles

23

Young, K. W., R. Muehlhaeusser, R. S. H. Piggin, and P. Rachitrangsan. "Agile control systems." Proceedings of the Institution of Mechanical Engineers, Part D: Journal of Automobile Engineering 215, no. 2 (February 1, 2001): 189–95. http://dx.doi.org/10.1243/0954407011525575.

Full text

Abstract:

To cope with unpredictable demand and a wide variety of products, future production systems require agility. To realize manufacturing agility, the control system has to respond and adapt to variations in real-world, dynamic production environments. The control system has to promote requirements such as reduced complexity, increased flexibility, adaptation in real time, extensibility, heterogeneity and autonomous operation. A control system architecture is proposed ensuring manufacturing agility by adapting quickly and cheaply to changes in the production environment.

APA, Harvard, Vancouver, ISO, and other styles

24

White, A. S. "An Agile Project System Dynamics Simulation Model." International Journal of Information Technologies and Systems Approach 7, no. 1 (January 2014): 55–79. http://dx.doi.org/10.4018/ijitsa.2014010104.

Full text

Abstract:

This paper compares established Systems Dynamics (SD) models of software projects with models of agile development. A new minimal SIMULINK™ agile project model was created and compared to a Waterfall model of a NASA project. Results are presented to enable project managers to predict the performance of future agile project processes. The model includes the time to generate the requirements and a function to provide requirements volatility. These models show that for the same productivity and fraction of errors that are satisfactory, the overall development staff costs are similar for agile and waterfall projects and the undiscovered rework is less for the agile project. This model generally supports empirical observations that shorter time-box iterations yield a shorter overall project completion.

APA, Harvard, Vancouver, ISO, and other styles

25

Abidin, Nor Hidayah Zainal, and Pathiah Abdul Samat. "Requirements identification for distributed agile team communication using high level carotene." Bulletin of Electrical Engineering and Informatics 10, no. 1 (February 1, 2021): 249–57. http://dx.doi.org/10.11591/eei.v10i1.2031.

Full text

Abstract:

Communication plays an important role to deliver the correct information. However, the communication became challenging especially for agile software teams, which are in geographical distributed. The problem arise when there are exchanging information using unstructured communication platform, misunderstanding on the information communicated and lack of documentation. The aim of this study is to propose a text classification technique for requirements identification in text messages. In this study, we adopted the cascade and cluster classification concept of Carotene that relies on the hash tag function. It classifies the text messages into requirements types instead of job title. This technique called as high-level carotene (HLC) technique that embedded into the tool to identify the functional requirement and non-functional requirements. The result shows that most of criterias evaluated have achieved more than 85% of effectiveness in identifying both of requirement in text messaging by using this technique.

APA, Harvard, Vancouver, ISO, and other styles

26

Azevedo, Américo, and Jorge Pinho de Sousa. "Agile Supply-Chain Management: Challenges, Requirements and Solutions." IFAC Proceedings Volumes 33, no. 17 (July 2000): 917–22. http://dx.doi.org/10.1016/s1474-6670(17)39526-5.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

AL-Ta’ani, Rami Hasan, and Rozilawati Razali. "Prioritizing Requirements in Agile Development: A Conceptual Framework." Procedia Technology 11 (2013): 733–39. http://dx.doi.org/10.1016/j.protcy.2013.12.252.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Jia, Jingdong, Xiaoying Yang, Rong Zhang, and Xi Liu. "Understanding software developers' cognition in agile requirements engineering." Science of Computer Programming 178 (June 2019): 1–19. http://dx.doi.org/10.1016/j.scico.2019.03.005.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Mugridge, Rick. "Managing Agile Project Requirements with Storytest-Driven Development." IEEE Software 25, no. 1 (January 2008): 68–75. http://dx.doi.org/10.1109/ms.2008.11.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Shull, Forrest. "Engineering Values: From Architecture Games to Agile Requirements." IEEE Software 30, no. 2 (March 2013): 2–6. http://dx.doi.org/10.1109/ms.2013.27.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Sikri, Monika, and Rajkumar Gell. "Derivation of agile SOA requirements using collaborative QFD." International Journal of Collaborative Enterprise 4, no. 4 (2014): 234. http://dx.doi.org/10.1504/ijcent.2014.066992.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Ann Rosser, Larri. "The Role of Requirements In Agile System Realization." INCOSE International Symposium 25, no. 1 (October 2015): 1438–51. http://dx.doi.org/10.1002/j.2334-5837.2015.00141.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Obidat, Laith. "Selecting Stakeholders for Requirements Elicitation in Agile Approach." International Journal of Computer Applications 183, no. 1 (May 19, 2021): 20–23. http://dx.doi.org/10.5120/ijca2021921272.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Elshandidy, Heba, and Sherif Mazen. "A Survey of Agile and Traditional Requirements Engineering." International Journal of Scientific & Engineering Research 4, no. 9 (September 25, 2013): 473–82. http://dx.doi.org/10.14299/ijser.2013.09.002.

Full text

Abstract:

In the past few years, there has been an increasing awareness of the important role of requirements engineering (RE) in a project’s success, in both research and industry. Developing consistent requirements specifications that meet the customers’ needs, in traditional development, is likely to be infeasible. For one reason, customers do not usually have a clear picture of what they really want. Secondly, the business domain could be changing quickly, especially if it heavily depends on technologies. Agile software development (ASD), on the other hand, supports iterative and incremental development and emphasises customers’ involvement in the development process. We argue that adopting ASD in RE overcomes the limitations of the traditional development. ASD, however, is no silver bullet and its adoption comes at a price. This paper helps the reader to: (1) get a quick yet a comprehensive grasp of RE in traditional and ASD; (2) understand the synergies/commonalities between the two approaches in handling RE; (3) recognise the associated challenges of adopting ASD; and (4) identify the current prominent agile RE research areas.

APA, Harvard, Vancouver, ISO, and other styles

35

Ghai, Sunaina, and Jagpuneet Kaur. "Analysis of User Requirements Gathering Practices in Agile and Non-Agile Software Development Team." International Journal of Computer Applications 58, no. 8 (November 15, 2012): 13–18. http://dx.doi.org/10.5120/9301-3519.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Marques, Johnny, and Adilson Marques da Cunha. "ARES: An Agile Requirements Specification Process for Regulated Environments." International Journal of Software Engineering and Knowledge Engineering 29, no. 10 (October 2019): 1403–38. http://dx.doi.org/10.1142/s021819401950044x.

Full text

Abstract:

Agile methods have provided significant contributions to Software Engineering. This work presents a new process for Software Requirements Specification, integrating Agile Properties and regulated environments, such as aviation, medical, nuclear and automotive, among others. The Software in Regulated Environments (SRE) involves plan-driven methods with needed documentation to ensure safety, reliability, security, and discipline. This paper proposes a balance between agile and plan-driven methods. We define a new process, which explores and investigates the usage of agile methods in SRE. The scope of this paper is Requirements Engineering, which is considered as a set of activities involved in the management, elicitation, documentation, and maintenance of requirements. The Adile Requirements Specification (ARES) process contains four methods, 13 activities, and some required artifacts to ensure compliance with the following six relevant Software Standards for regulated environments: RTCA DO-178C, IEC 62304:2015, ECSS-E-ST-40C, IEC 61508-3, ISO/IEC/IEEE 12207, and IAEA SSG-39. The process evaluation was performed using two experiments: a Cockpit Display System (CDS) and a Healthcare Information System (HIS). These experiments were measured with appropriate metrics to ensure improvements in Software Requirements Specification and traceability among artifacts. The experimental results revealed that the ARES process works better than the original Scrum for Software in Regulated Environments. The ARES process can also be integrated with traditional software life cycles (Waterfall, V, and Incremental and Iterative), when applied in the Requirements Engineering phase.

APA, Harvard, Vancouver, ISO, and other styles

37

Tøndel, Inger Anne, and Martin Gilje Jaatun. "Towards a Conceptual Framework for Security Requirements Work in Agile Software Development." International Journal of Systems and Software Security and Protection 11, no. 1 (January 2020): 33–62. http://dx.doi.org/10.4018/ijsssp.2020010103.

Full text

Abstract:

Security requirement work plays a key role in achieving cost-effective and adequate security in a software development project. Knowledge about software companies' experiences of security requirement work is important in order to bridge the observed gap between software security practices and security risks in many projects today. Particularly, such knowledge can help researchers improve on available practices and recommendations. This article uses the results of published empirical studies on security requirement work to create a conceptual framework that shows key concepts related to work context, this work itself and the effects of this work. The resulting framework points to the following research challenges: 1) Identifying and understanding factors important for the effect of security requirements work; 2) Understanding what is the importance of the chosen requirements approach itself, and; 3) Properly taking into account contextual factors, especially factors related to individuals and interactions, in planning and analysis of empirical studies on security requirements work.

APA, Harvard, Vancouver, ISO, and other styles

38

Kramer, Jeremy, and Torrey Wagner. "Developmental Test and Requirements: Best Practices of Successful Information Systems Using Agile Methods." Delivering Performance at the Speed of Relevance: Agile Aquisition Approaches 26, no. 88 (April 1, 2019): 128–50. http://dx.doi.org/10.22594/dau.19-819.26.02.

Full text

Abstract:

This article provides insights into the current state of developmental testing (DT) and requirements management in Department of Defense information systems employing Agile development. The authors describe the study methodology and provide an overview of Agile development and testing. Insights are described for requirements, detailed planning, test execution, and reporting. This work articulates best practices related to DT and requirements management strategies for programs employing modernized Software Development Life Cycle practices.

APA, Harvard, Vancouver, ISO, and other styles

39

Al-Refai, Mohammed, Basem Zughoul, Yousef Al-Raba’nah, Mohammad Alauthman, and Ahmad Muraish. "Software Development by Merging Prototyping and Agile Approaches." International Journal of Advanced Research in Computer Science and Software Engineering 7, no. 9 (October 31, 2017): 47. http://dx.doi.org/10.23956/ijarcsse.v7i9.410.

Full text

Abstract:

during the past four decades, new software development approaches were presented to going with new trends of the software development companies and developers. Nowadays most software companies search to customise short period and minimal costs to produce valuable software products. These productions are within unstable, changing environments. Agile Methodologies were thus introduced to achieve the new requirements of the software development companies. Agile development invented for handling change. The key benefit of agile methodology is used to simplify the change-oriented software engineering process, but agile methodology needs to take more consideration to user point of view. Although the weaknesses of prototyping approach have, it can be used effectively by end users to describe requirements that developers may not have considered. This paper presents a proposed framework based on merge prototyping and agile approaches not only to cure the weaknesses of agile development and prototype methodology but to enrol the user in every single step, which will lead to faster and much accepted overall results.

APA, Harvard, Vancouver, ISO, and other styles

40

Et.al, Rosnani Shuib. "Towards Adopting Software Quality Assurance in Agile Development Methodology." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 10, 2021): 2152–57. http://dx.doi.org/10.17762/turcomat.v12i3.1158.

Full text

Abstract:

In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product. However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology. Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.

APA, Harvard, Vancouver, ISO, and other styles

41

Shahzeb Hussain, Namrata Bhadri, and Syed Razauddin Shahlal. "Factors Influencing the Efficacy of Agile Usage." International Journal of Engineering and Management Research 10, no. 5 (October 5, 2020): 1–4. http://dx.doi.org/10.31033/ijemr.10.5.1.

Full text

Abstract:

Agile techniques that utilize iterative development are broadly used in various industry projects as a lightweight development technique which can satisfy the continuous changes of requirements. Short repetitions are used that are required for efficient product delivery. Traditional and old software development methods are not much efficient and effective to control the rapid change in requirements. Despite the benefits of Agile, criticism on agile methodology states that it couldn’t succeed to pay attention to architectural and design issues and therefore is bound to produce small design-decisions. The past decade has observed numerous changes in systems development with many organizations accepting agile techniques as a viable methodology for developing systems. An increase in the number of research studies reveals the growing demand and acceptance of agile methodologies. While most research has focused on acceptance rate and adaptation of agile practices, there is very limited knowledge of their post-adoption usage and incorporation within organizations. Several factors explain the effective usage of agile methodologies. A combination of previous research in Agile Methodologies, Diffusion of Innovations, Information Systems implementation, and Systems Development has been carried out to develop a research model that identifies the main factors relevant to the propagation and effective usage of agile methodologies in organizations.

APA, Harvard, Vancouver, ISO, and other styles

42

Bławucki, Tomasz, Siarhei Ramanovich, and Maria Skublewska-Paszkowska. "Applications supporting utilization of agile methods in software development process." Journal of Computer Sciences Institute 14 (March 30, 2020): 8–13. http://dx.doi.org/10.35784/jcsi.1566.

Full text

Abstract:

The article presents a comparison in terms of hardware requirements of applications that supports the agile software development processes. For research purposes, popular mobile and internet applications supporting agile software development were chosen. In order to determine the significance of individual technical requirements for end-users, a series of research experiments, based on scenarios of typical and boundary use was conducted. In addition to research, the application supporting agile software development process was implemented. The results of research were recorded by specialized monitoring and profiling tools. The results of performed work are presented in tabular form.

APA, Harvard, Vancouver, ISO, and other styles

43

Dhir, Saru, Deepak Kumar, and V. B. Singh. "Requirement Paradigms to Implement the Software Projects in Agile Development Using Analytical Hierarchy Process." International Journal of Decision Support System Technology 9, no. 3 (July 2017): 28–41. http://dx.doi.org/10.4018/ijdsst.2017070102.

Full text

Abstract:

The primary focus of a successful organization is to deliver the high quality product to fulfil the client's needs. In the software industry, quality requirements play a major role for the projects to be successful. Quality requirements are influenced by the users, clients and stakeholders analysis to reduce the burden of requirement engineering process. So it is essential to select only the appropriate requirements that could be associated with the final product. This empirical research presents a framework by using Analytical Hierarchy Process to calculate the critical attributes that are influencing from the requirement selection to requirement prioritization in an uncertain environment. The experiment was accomplished by calculating the relative importance of those attributes, through the survey carried out with the help of agile experts. The utility measure is obtained from these attributes demonstrating the improvement in the performance. Consistency ratio is also evaluated for the comparison matrix.

APA, Harvard, Vancouver, ISO, and other styles

44

Alsaqqa, Samar, Samer Sawalha, and Heba Abdel-Nabi. "Agile Software Development: Methodologies and Trends." International Journal of Interactive Mobile Technologies (iJIM) 14, no. 11 (July 10, 2020): 246. http://dx.doi.org/10.3991/ijim.v14i11.13269.

Full text

Abstract:

<p>Software engineering is a discipline that undergone many improvements that aims to keep up with the new advancements in technologies and the modern business requirements through developing effective approaches to reach the final software product, agile software development is one of these successful approaches. Agile software development is a lightweight approach that was proposed to overcome the convolutional development methods’ limitations and to reduce the overhead and the cost while providing flexibility to adopt the changes in requirements at any stage, this is done by managing the tasks and their coordination through a certain set of values and principles.</p><p>In this work, a comprehensive review that outlines the main agile values and principles, and states the key differences that distinguish agile methods over the traditional ones are presented. Then a discussion of the most popular agile methodologies; their life cycles, their roles, and their advantages and disadvantages are outlined. The recent state of art trends that adopts agile development especially in cloud computing, big data, and coordination are also explored. And finally, this work highlights how to choose the best suitable agile methodology that must be selected according to the task at hand, how sensitive the product is and the organization structure.</p>

APA, Harvard, Vancouver, ISO, and other styles

45

Ochodek, Mirosław, and Sylwia Kopczyńska. "Perceived importance of agile requirements engineering practices – A survey." Journal of Systems and Software 143 (September 2018): 29–43. http://dx.doi.org/10.1016/j.jss.2018.05.012.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Jung, Mooyoung, Min Kenn Chung, and Hyunbo Cho. "Architectural requirements for rapid development of agile manufacturing systems." Computers & Industrial Engineering 31, no. 3-4 (December 1996): 551–54. http://dx.doi.org/10.1016/s0360-8352(96)00223-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Ramesh, Balasubramaniam, Lan Cao, and Richard Baskerville. "Agile requirements engineering practices and challenges: an empirical study." Information Systems Journal 20, no. 5 (November 13, 2007): 449–80. http://dx.doi.org/10.1111/j.1365-2575.2007.00259.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Kovitz, Ben. "Hidden skills that support phased and agile requirements engineering." Requirements Engineering 8, no. 2 (July 1, 2003): 135–41. http://dx.doi.org/10.1007/s00766-002-0162-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Alsahli, Abdulaziz, Hameed Khan, and Sultan Alyahya. "Toward an Agile Approach to Managing the Effect of Requirements on Software Architecture during Global Software Development." Scientific Programming 2016 (2016): 1–16. http://dx.doi.org/10.1155/2016/8198039.

Full text

Abstract:

Requirement change management (RCM) is a critical activity during software development because poor RCM results in occurrence of defects, thereby resulting in software failure. To achieve RCM, efficient impact analysis is mandatory. A common repository is a good approach to maintain changed requirements, reusing and reducing effort. Thus, a better approach is needed to tailor knowledge for better change management of requirements and architecture during global software development (GSD).The objective of this research is to introduce an innovative approach for handling requirements and architecture changes simultaneously during global software development. The approach makes use of Case-Based Reasoning (CBR) and agile practices. Agile practices make our approach iterative, whereas CBR stores requirements and makes them reusable. Twin Peaks is our base model, meaning that requirements and architecture are handled simultaneously. For this research, grounded theory has been applied; similarly, interviews from domain experts were conducted. Interview and literature transcripts formed the basis of data collection in grounded theory. Physical saturation of theory has been achieved through a published case study and developed tool. Expert reviews and statistical analysis have been used for evaluation. The proposed approach resulted in effective change management of requirements and architecture simultaneously during global software development.

APA, Harvard, Vancouver, ISO, and other styles

50

Qasaimeh, Malik, and Alain Abran. "Design and Assessment for Agile Auditing Model: The Case of ISO 9001 Traceability Requirements." Lecture Notes on Software Engineering 3, no. 3 (2015): 189–94. http://dx.doi.org/10.7763/lnse.2015.v3.188.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Agile Requirements'

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