Relevant bibliographies by topics / Agile model

Contents

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

Academic literature on the topic 'Agile model'

Author: Grafiati
Published: 29 June 2021
Last updated: 3 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 model.'

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 model"

1

Masood Butt, Saad, Shahid Masood Butt, Azura Onn, Nadra Tabassam, and Mazlina Abdul Majid. "Usability Evaluation Techniques for Agile Software Model." Journal of Software 10, no. 1 (January 2015): 32–41. http://dx.doi.org/10.17706/jsw.10.1.32-41.

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

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
3

Kastelec, Patricija. "Model EFQM in agilnost organizacij." Revija za univerzalno odličnost 10, no. 2 (June 10, 2021): 155–79. http://dx.doi.org/10.37886/ruo.2021.034.

Full text
Abstract:
Research question (RV): What is the contribution of an organization that follows the EFQM model and reorganizes its organization into an agile organization? Purpose: The purpose of the research is to examine the interrelationship between the EFQM model, agility and agile organization, and consequently faster adaptability, greater performance and competitiveness of the agile organization. Method: The article was based on a review of foreign and domestic literature. We reviewed the professional literature on agility and the EFQM model. We searched a link between agility and the EFQM model. Results: We will find that there are differences between agile management and organizational culture in organizations that are agile aware from those that are not. It is essential for successful agile organization leaders to develop effective communication and interaction skills that are unique to the leader and organization. It is important that individuals in the organization adopt a shared vision, participate in a culture of trust and inclusion, while leaders encourage creativity and experimentation. Organization: An agile organization is considered to be fast (innovative, agile, adaptable) and that it is necessary to constantly renew its business. The research will draw attention to the importance and necessity of management awareness that by creating a certain organizational culture and agile management of the organization, they will achieve faster and more efficient adaptation to changes in the environment. Society: The lack of agile management and the creation of an inappropriate organizational culture has a negative impact on the satisfaction of all involved in the process (employees, customers, suppliers) and consequently on adapting to the needs of the environment. Originality: The originality of the article lies in breaking down the myths about the concept of agility and agile organization, and presenting or evaluating the obtained results with the result of differences between agile and not agile or traditional organizations. Limitations / further research: The limitation represents a small number of articles and literature selected for comparison. Based on a larger sample of articles, we would get more relevant results. We also found a few articles in Slovenian.
APA, Harvard, Vancouver, ISO, and other styles
4

Aoyama, Mikio. "Agile software process model." Computer Standards & Interfaces 21, no. 2 (June 1999): 177. http://dx.doi.org/10.1016/s0920-5489(99)92220-1.

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

Russo, Daniel. "The Agile Success Model." ACM Transactions on Software Engineering and Methodology 30, no. 4 (July 2021): 1–46. http://dx.doi.org/10.1145/3464938.

Full text
Abstract:
Organizations are increasingly adopting Agile frameworks for their internal software development. Cost reduction, rapid deployment, requirements and mental model alignment are typical reasons for an Agile transformation. This article presents an in-depth field study of a large-scale Agile transformation in a mission-critical environment, where stakeholders’ commitment was a critical success factor. The goal of such a transformation was to implement mission-oriented features, reducing costs and time to operate in critical scenarios. The project lasted several years and involved over 40 professionals. We report how a hierarchical and plan-driven organization exploited Agile methods to develop a Command & Control (C2) system. Accordingly, we first abstract our experience, inducing a success model of general use for other comparable organizations by performing a post-mortem study. The goal of the inductive research process was to identify critical success factors and their relations. Finally, we validated and generalized our model through Partial Least Squares - Structural Equation Modelling, surveying 200 software engineers involved in similar projects. We conclude the article with data-driven recommendations concerning the management of Agile projects.
APA, Harvard, Vancouver, ISO, and other styles
6

Henriques, Vaughan, and Maureen Tanner. "A Systematic Literature Review of Agile Maturity Model Research." Interdisciplinary Journal of Information, Knowledge, and Management 12 (2017): 053–73. http://dx.doi.org/10.28945/3666.

Full text
Abstract:
Background/Aim/Purpose: A commonly implemented software process improvement framework is the capability maturity model integrated (CMMI). Existing literature indicates higher levels of CMMI maturity could result in a loss of agility due to its organizational focus. To maintain agility, research has focussed attention on agile maturity models. The objective of this paper is to find the common research themes and conclusions in agile maturity model research. Methodology: This research adopts a systematic approach to agile maturity model research, using Google Scholar, Science Direct, and IEEE Xplore as sources. In total 531 articles were initially found matching the search criteria, which was filtered to 39 articles by applying specific exclusion criteria. Contribution:: The article highlights the trends in agile maturity model research, specifically bringing to light the lack of research providing validation of such models. Findings: Two major themes emerge, being the coexistence of agile and CMMI and the development of agile principle based maturity models. The research trend indicates an increase in agile maturity model articles, particularly in the latter half of the last decade, with concentrations of research coinciding with version updates of CMMI. While there is general consensus around higher CMMI maturity levels being incompatible with true agility, there is evidence of the two coexisting when agile is introduced into already highly matured environments. Future Research: Future research direction for this topic should include how to attain higher levels of CMMI maturity using only agile methods, how governance is addressed in agile environments, and whether existing agile maturity models relate to improved project success.
APA, Harvard, Vancouver, ISO, and other styles
7

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
8

Higuchi, Marcelo Makoto, and Davi Noboru Nakano. "Agile Design: A Combined Model Based on Design Thinking and Agile Methodologies for Digital Games Projects." Revista de Gestão e Projetos 08, no. 02 (August 1, 2017): 109–26. http://dx.doi.org/10.5585/gep.v8i2.528.

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

Singh, Monika, and Ruhi Saxena. "Risk Management in Agile Model." IOSR Journal of Computer Engineering 16, no. 5 (2014): 43–46. http://dx.doi.org/10.9790/0661-16564346.

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

Gray, Jeff, and Bernhard Rumpe. "Agile model-based system development." Software & Systems Modeling 17, no. 4 (August 24, 2018): 1053–54. http://dx.doi.org/10.1007/s10270-018-0694-1.

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

Dissertations / Theses on the topic "Agile model"

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

Deekonda, Rahul, and Prithvi Raj Sirigudi. "Assessment of Agile Maturity Models : A Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13230.

Full text
Abstract:
Context. In recent years Agile has gained lots of importance in the fieldof software development. Many organization and software practitioners hasalready adopted agile practice due to its flexibility in nature. Hence, agiledevelopment methodologies have been replaced to traditional developmentmethods. Agile is a family of several methodologies namely Scrum. eXtremeprogramming (XP) and several others. These several methods areembedded with different set of agile practices for the organizations to adoptand implement for their development process. But there is still a need forempirical research to understand the benefits of implementing the Agilepractices which contributes to the overall success of accomplishment of thesoftware project. Several agile maturity models have been published over adecade but not all of the models have been empirically validated. Hence,additional research in the context of agile maturity is essential and needed. Objectives. This study focus on providing a comprehensive knowledgeon the Agile Maturity Models which help in guiding the organizations regardingthe implementation of Agile practices. There are several maturitymodels published with different set of Agile practices that are recommendedto the industries. The primary aim is to compare the agile maturity maturitymodels and to investigate how the agile practices are implemented inthe industry Later the benefits and limitations faced by the software practitionersdue to implementation of agile practices are identified. Methods. For this particular research an industrial survey was conductedto identify the agile practices that are implemented in the industry. Inaddition, this survey aims at identifying the benefits and limitations of implementingthe agile practices. A literature review is conducted to identifythe order of agile practices recommended from the literature in agile MaturityModels. Results. From the available literature nine Maturity Models have beenextracted with their set of recommended agile practices. Then the resultsfrom the survey and literature are compared and analyzed to see if thereexist any commonalities or differences regarding the implementation of agilepractices in a certain order. From the results of the survey the benefitsand limitations of implementing the Agile practices in a particular order areidentified and reported. Conclusions. The findings from the literature review and the survey resultsin evaluating the agile maturity models regarding the implementationof agile practices.
APA, Harvard, Vancouver, ISO, and other styles
3

Bodicherla, Saikumar, and Divyani Pamulapati. "Knowledge Management Maturity Model for Agile Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17659.

Full text
Abstract:
Context: Knowledge is the major aspect of an organization which enables the enterprise to be more productive and to deliver the high complexity services. Knowledge management plays a key role in agile software development because it supports cultural infrastructure esteems like collaboration, communication, and knowledge transfer. This research aims to explore how organizations that adopts Agile Software Development (ASD) implement knowledge management utilizing practices that supports the key process areas. Several knowledge management maturity models have been proposed over a decade ago but not all of the models that is specially stated knowledge Management Maturity Model (KMMM) for Agile software development. To fulfil this research gap, we introduce the maturity model which emphasize knowledge management in ASD among the practitioners. This maturity model helps to assess their knowledge management in organization and provides a road map to the organizations for any further improvement required in their processes.  Objectives: In this thesis, we investigate the key process areas of knowledge management maturity models that could support agile software development. Through investigation about the key process areas, we found that the organizations should emphasis on key process areas and its practices in order to improve the software process. The objectives of this research include: Explore the key process areas and practices of knowledge management in the knowledge management maturity models.  Identify the views of practitioners on knowledge management practices and key process areas for Agile software development. To propose the maturity model for Knowledge management in Agile software development among the practitioner’s opinions.  Methods: In this research, we conducted two methods: Systematic mapping and Survey to fulfil our aim and objectives. We conducted Systematic mapping study through the snowballing process to investigate empirical literature about Knowledge management maturity models. To triangulate the systematic mapping results, we conducted a survey. From the survey results, we obtained the responses and were analyzed statistically using descriptive statistics. Results: From Systematic mapping, we identified 18 articles and analyzed 24 practices of Knowledge management maturity models. These practices are indicated in key process areas such as process, people, technology. Through the systematic mapping results, 9 KM practices that were found from KMMM literature were listed in the survey questionnaire and answered by software engineering practitioners. Moreover, 5 other new practices for agile have suggested in the survey that was not found in KMMM literature. To address the systematic mapping and survey results, we propose the maturity model which emphasize knowledge management practices in ASD among the practitioners. Conclusions: This thesis lists the main elements of practices that are utilized by the organization and also show the usage of maturity levels at each practice in detail. Furthermore, this thesis helps the organization's to assess the current levels of maturity that exist to each practice in a real process. Hence, the researchers can utilize the model from this thesis and further they can improve their Km in organizations.
APA, Harvard, Vancouver, ISO, and other styles
4

Naughton, S. H. "Developing an agile supply chain model for SMEs." Thesis, University of Liverpool, 2016. http://livrepository.liverpool.ac.uk/3006560/.

Full text
Abstract:
Rising worldwide competition is making it increasingly difficult for SME organisations to compete in the marketplace as traditional means of manufacture, and modes of delivery are being changed through technological advancements. In line with these factors, organisations are ever more capable of producing goods that are more bespoke and personalised than in the past and within the price ranges and affordability levels of demanding markets. Whilst large organisations have the power to enforce supply chain compliance in order to meet these changes, it is not always the case for SMEs. The agile supply chain philosophy moves away from traditional methods under which large organisations enforce supply chain compliance, and embraces the concept of supply chain agility that allows the supply chain as a whole to move forward as one and share the benefits as a developed and cohesive unit. Such a philosophy should be to the advantage of all organisations, but ought to be of particular interest to SMEs as its use could assist in improving their competitiveness. This thesis is primarily concerned with the development of agile supply chains within SME organisations. The research sets out to develop the means through which SMEs can develop their agile supply chains so as to make them more efficient and competitive both now and in the future. The research is set upon existing theories and models, particularly following the works of Sharifi et al. (2006), Ismail and Sharifi (2006), Ismail et al., (2006) and Ismail et al., (2011) so as to contribute further to their concepts theoretically and to also present the practical means by which such frameworks can be utilised in industry. The research provides a link between manager perceptions and underlying factors that affect their organisations and how they relate to the markets served. This has been achieved through the development of a model through which SMEs can analyse their present operating position, consider new product features, potential supply chain partners and the means through which to develop their agile supply chains as a complete unit. Using case study methodology, some extensive fieldwork has been undertaken to examine the ideas and extend our understanding of the approaches to build and sustain agile networks for organisations introducing products into markets. The study has assisted in reforming and developing the initial models into practical tools. Further to this, the research offers a series of developmental roadmaps that can be followed by SMEs to assist in the progress of developing agility into their supply chains. The outcomes from the research provide a contribution to academic theory and practice and build upon previous research, taking it forward with practical tools that organisations can utilise. The findings provide evidence for the benefits that can be derived from the developed models such that their application could be realistically considered within a practical setting.
APA, Harvard, Vancouver, ISO, and other styles
5

Sivander, Fredrik. "An Agile Procurement Model that Facilitates Agile Execution of Projects : A Case Study at Telia Company." Thesis, Mittuniversitetet, Avdelningen för informations- och kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-28647.

Full text
Abstract:
Since agile execution of projects has become more frequently used the discovery that the surroundings of the projects are not always compatible has been made. The problematic within the area is traditional accounting restrictions and cost estimation. The purpose with this research is to develop a procurement method that facilitates for agile execution of projects. Previous research proves that the agile principles can be used in a procurement process successfully, but with focus on facilitating on the procurement itself and not on the agile execution. This research includes theories about the agile estimation models and requirement prioritizing methods. The method used to complete this research is design science, which includes six steps to ensure reproducibility and validity. This research resulted in a procurement method that includes three methods and two phases with focus on minimizing the pre-study, with focus on only the most important requirements only. The procurer will then attend the agile execution and both procurer and executer enter the project with the mindset that the initial budget- and time estimation will be increased. Both procurer and executor works together towards the same goal, maximum customer value for minimum cost. The method is tested beside two projects conducted by Telia Company and the test result is that the generated solution reduces the total cost of the project and time to generate project result and facilitates for an agile execution. This research concludes that an agile procurement can facilitate agile execution of project but before agile procurement can be a recommendation more tests are needed.
APA, Harvard, Vancouver, ISO, and other styles
6

Anderzon, Samuel, and Filip Davidsson. "Agile Practices in Production Development : Investigation of how agile practices may be applied in a production development context and what the expected effects are." Thesis, Jönköping University, JTH, Produktionsutveckling, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-53736.

Full text
Abstract:
Globalization has continuously brought an increased competition among companies, which entails a need for faster and more frequent deliveries of new products. Traditional project management methods, such as stage-gate and waterfall, are commonly used in production development projects and builds on a sequential approach. These methods have proven to have some disadvantages in flexibility, long lead times and it often creates communication barriers between the actors at each stage. The software industry has already encountered these obstacles and responded by introducing agile project management. Which improves the adaptability and allow changes to be made, due to new requirements from stakeholders or customers, throughout the entire development process. However, it remains unknown how agile models can improve production development. The purpose of this study was therefore to investigate how agile models can be applied to production development and what the effects are.  The authors have performed a case study at eight different companies within the automotive industry. The purpose of it has been to gain a deeper understanding about the case companies current production development processes and review how familiar the organizations are with the concept of agile project management. The extraction of the empirical data was conducted by questionnaires, interviews, and document reviews. An analyzation was done by comparing the empirical findings with the theoretical background out of eleven different categories that relates to project management (e.g., project goals, process, customer integration etc.). The analyzation concluded that the case company exclusively conducts their production development project by using a sequential approach.  The analyzation and the eleven categories where, together with the theoretical background about agile project management, later used to create the result by brainstorming different practices to become more agile. The results are presented out of three different scenarios, depending how agile the companies would like to be. For instance, are two process models suggested, one that is completely agile and one that is a hybrid of an agile and a stage-gate. Furthermore, are the implementation of self-organized teams, holistic approach towards internal and external partners, and reduced demand for documentation some of the practices that are suggested. Additionally, are three considerable aspects for the implementation presented.  The expected outcome and effects of applying these practices are discussed in the final chapter. Some of these outcomes are a company culture that will attract and retain talented personnel, where shared responsibilities and authorities triggers the employees to an increased commitment and sense of ownership towards their projects. Furthermore, are the companies expected to experience a more flexible and responsive approach towards conducting production development projects with a high focus on customer requirements and creating customer value.
APA, Harvard, Vancouver, ISO, and other styles
7

Ramadoss, Balaji. "Ontology Driven Model for an Engineered Agile Healthcare System." Scholar Commons, 2014. https://scholarcommons.usf.edu/etd/5110.

Full text
Abstract:
Healthcare is in urgent need of an effective way to manage the complexity it of its systems and to prepare quickly for immense changes in the economics of healthcare delivery and reimbursement. Centers for Medicare & Medicaid Services (CMS) releases policies affecting inpatient and long-term care hospitals policies that directly affect reimbursement and payment rates. One of these policy changes, a quality-reporting program called Hospital Inpatient Quality Reporting (IQR), will effect approximately 3,400 acute-care and 440 long-term care hospitals. IQR sets guidelines and measures that will contain financial incentives and penalties based on the quality of care provided. CMS, the largest healthcare payer, is aggressively promoting high quality of care by linking payment incentives to outcomes. With CMS assessing each hospital's performance by comparing its Quality Achievements and Quality Improvement scores, there is a growing need and demand to understand these quality measures under the context of patient care, data management and system integration. This focus on patient-centered quality care is difficult for healthcare systems due to the lack of a systemic view of the patient and patient care. This research uniquely addresses the hospital's need to meet these challenges by presenting a healthcare specific framework and methodology for translating data on quality metrics into actionable processes and feedback to produce the desired quality outcome. The solution is based on a patient-care level process ontology, rather than the technology itself, and creates a bridge that applies systems engineering principles to permit observation and control of the system. This is a transformative framework conceived to meet the needs of the rapidly changing healthcare landscape. Without this framework, healthcare is dealing with outcomes that are six to seven months old, meaning patients may not have been cared for effectively. In this research a framework and methodology called the Healthcare Ontology Based Systems Engineering Model (HOB-SEM) is developed to allow for observability and controllability of compartmental healthcare systems. HOB-SEM applies systems and controls engineering principles to healthcare using ontology as the method and the data lifecycle as the framework. The ontology view of patient-level system interaction and the framework to deliver data management and quality lifecycles enables the development of an agile systemic healthcare view for observability and controllability
APA, Harvard, Vancouver, ISO, and other styles
8

Léauté, Thomas. "Coordinating agile systems through the model-based execution of temporal plans." Thesis, Massachusetts Institute of Technology, 2005. http://hdl.handle.net/1721.1/34681.

Full text
Abstract:
Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Aeronautics and Astronautics, 2005.
Includes bibliographical references (p. 149-155).
Agile autonomous systems are emerging, such as unmanned aerial vehicles (UAVs), that must robustly perform tightly coordinated time-critical missions; for example, military surveillance or search-and-rescue scenarios. In the space domain, execution of temporally flexible plans has provided an enabler for achieving the desired coordination and robustness, in the context of space probes and planetary rovers, modeled as discrete systems. We address the challenge of extending plan execution to systems with continuous dynamics, such as air vehicles and robot manipulators, and that are controlled indirectly through the setting of continuous state variables. Systems with continuous dynamics are more challenging than discrete systems, because they require continuous, low-level control, and cannot be controlled by issuing simple sequences of discrete commands. Hence, manually controlling these systems (or plants) at a low level can become very costly, in terms of the number of human operators necessary to operate the plant. For example, in the case of a fleet of UAVs performing a search-and-rescue scenario, the traditional approach to controlling the UAVs involves providing series of close waypoints for each aircraft, which incurs a high workload for the human operators, when the fleet consists of a large number of vehicles.
(cont.) Our solution is a novel, model-based executive, called Sulu, that takes as input a qualitative state plan, specifying the desired evolution of the state of the system. This approach elevates the interaction between the human operator and the plant, to a more abstract level where the operator is able to "coach" the plant by qualitatively specifying the tasks, or activities, the plant must perform. These activities are described in a qualitative manner, because they specify regions in the plant's state space in which the plant must be at a certain point in time. Time constraints are also described qualitatively, in the form of flexible temporal constraints between activities in the state plan. The design of low-level control inputs in order to meet this abstract goal specification is then delegated to the autonomous controller, hence decreasing the workload per human operator. This approach also provides robustness to the executive, by giving it room to adapt to disturbances and unforeseen events, while satisfying the qualitative constraints on the plant state, specified in the qualitative state plan. Sulu reasons on a model of the plant in order to dynamically generate near-optimal control sequences to fulfill the qualitative state plan. To achieve optimality and safety, Sulu plans into the future, framing the problem as a disjunctive linear programming problem.
(cont.) To achieve robustness to disturbances and maintain tractability, planning is folded within a receding horizon, continuous planning and execution framework. The key to performance is a problem reduction method based on constraint pruning. We benchmark performance using multi-UAV firefighting scenarios on a real-time, hardware-in-the-loop testbed.
by Thomas Léauté.
S.M.
APA, Harvard, Vancouver, ISO, and other styles
9

Gena, Kriti. "Suitability of Model Based Systems Engineering for Agile Automotive Product Development." The Ohio State University, 2020. http://rave.ohiolink.edu/etdc/view?acc_num=osu1595500667122794.

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

Jedyk, Marcin. "Using Feature Models For Reusability In Agile Methods." Master's thesis, METU, 2011. http://etd.lib.metu.edu.tr/upload/12613338/index.pdf.

Full text
Abstract:
The approach proposed in this thesis contributes to implementing source code reuse and re-engineering techniques for agile software development. This work includes an introduction to feature models and some of the Feature Oriented Software Development (FOSD) practices to achieve a lightweight way of retrieving source code. A Feature model created during the course of following FOSD practices serves as an additional layer of documentation which represents the problem space for the developed application. This thesis proposes linking source code with such a feature model for the purpose of identifying and retrieving code. This mechanism helps with accessing the code segment corresponding to a feature with minimal effort, thus suits agile development methods. At the moment, there is a gap between feature oriented approaches and agile methods. This thesis tries to close this gap between high-level approaches for software modelling (feature modelling) and agile methods for software development.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Agile model"

1

Integrating CMMI and agile development: Case studies and proven techniques for faster performance improvement. Upper Saddle River, NJ: Addison-Wesley, 2011.

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

Ita, Richardson, and Ó. hAodha Mícheál 1969-, eds. Agile development in the Irish software industry: Models for change. Newcastle upon Tyne, UK: Cambridge Scholars Pub., 2009.

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

Scherer, Eric. Shop Floor Control - A Systems Perspective: From Deterministic Models towards Agile Operations Management. Berlin, Heidelberg: Springer Berlin Heidelberg, 1998.

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

Lankhorst, Marc. Agile Service Development: Combining Adaptive Methods and Flexible Solutions. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012.

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

Lano, Kevin. Agile Model-Based Development Using UML-RSDS. Taylor & Francis Group, 2017.

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

Agile Model-Based Development Using UML-RSDS. Taylor & Francis Group, 2016.

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

Lano, Kevin. Agile Model-Based Development Using UML-RSDS. Taylor & Francis Group, 2017.

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

Lano, Kevin. Agile Model-Based Development Using UML-RSDS. Taylor & Francis Group, 2017.

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

Lano, Kevin. Agile Model-Based Development Using UML-RSDS. Taylor & Francis Group, 2017.

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

Agile Service Development Enterprise Engineering. Springer, 2012.

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

Book chapters on the topic "Agile model"

1

Dalton, Jeff. "Kano Model." In Great Big Agile, 189–90. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-4206-3_37.

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

Freedman, Rick. "The Agile Consulting Model." In The Agile Consultant, 167–76. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4302-6053-0_13.

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

Moreira, Mario E. "Ready, Implement, Coach, and Hone (RICH) Deployment Model." In Being Agile, 59–67. Berkeley, CA: Apress, 2013. http://dx.doi.org/10.1007/978-1-4302-5840-7_7.

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

Costa, Raone, Raphael Rodrigues, and Alessandra Costa Smolenaars Dutra. "Application of Scrum Maturity Model in SoftDesign Company." In Agile Methods, 39–49. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-55907-0_4.

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

Slogar, Andreas. "Das Viable System Model (VSM)." In Die agile Organisation, 62–75. München: Carl Hanser Verlag GmbH & Co. KG, 2020. http://dx.doi.org/10.3139/9783446463967.004.

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

Slogar, Andreas. "Das Viable System Model (VSM)." In Die agile Organisation, 58–71. München: Carl Hanser Verlag GmbH & Co. KG, 2018. http://dx.doi.org/10.3139/9783446456150.004.

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

Rumpe, Bernhard. "Model-Based Tests." In Agile Modeling with UML, 185–216. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-58862-9_7.

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

Corrêa Rodrigues, Adriana, and Rafaela Mantovani Fontana. "Evaluation of an Agile Maturity Model: Empirical Evidences for Agility Assessments." In Agile Methods, 49–62. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-14310-7_4.

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

Bergel, Alexandre. "The Perceptron Model." In Agile Artificial Intelligence in Pharo, 3–35. Berkeley, CA: Apress, 2020. http://dx.doi.org/10.1007/978-1-4842-5384-7_1.

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

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

Conference papers on the topic "Agile model"

1

Peres, Angela Lima, Tiago Da Silva, Fernando Selleri Silva, Felipe Furtado Soares, Carlos Rosemberg, and Silvio Romero. "AGILEUX Model: Towards a Reference Model on Integrating UX in Developing Software Using Agile Methodologies." In 2014 Agile Conference (AGILE). IEEE, 2014. http://dx.doi.org/10.1109/agile.2014.15.

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

Ide, Masahiro, Yukio Amagai, Mikio Aoyama, and Yasuhiro Kikushima. "A Lean Design Methodology for Business Models and Its Application to IoT Business Model Development." In 2015 Agile Conference (AGILE). IEEE, 2015. http://dx.doi.org/10.1109/agile.2015.8.

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

Washizaki, Hironori, Kiyoshi Honda, and Yoshiaki Fukazawa. "Predicting Release Time for Open Source Software Based on the Generalized Software Reliability Model." In 2015 Agile Conference (AGILE). IEEE, 2015. http://dx.doi.org/10.1109/agile.2015.19.

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

Giese, Holger, Leen Lambers, and Christian Zöllner. "From classic to agile." In MODELS '20: ACM/IEEE 23rd International Conference on Model Driven Engineering Languages and Systems. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3417990.3418743.

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

Shinkle, Christopher M. "Applying the Dreyfus Model of Skill Acquisition to the Adoption of Kanban Systems at Software Engineering Professionals (SEP)." In 2009 Agile Conference (AGILE). IEEE, 2009. http://dx.doi.org/10.1109/agile.2009.25.

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

Mairon, Klaus, Martin Buchheit, Martin Knahl, and Shirley Atkinson. "Making MDD Agile : The Agile Model-Driven Method." In 4th International Conference on Image Processing and Pattern Recognition (IPPR 2018). Academy & Industry Research Collaboration Center (AIRCC), 2018. http://dx.doi.org/10.5121/csit.2018.80508.

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

Lano, Kevin, S. Fang, H. Alfraihi, and S. Kolahdouz-Rahimi. "Simplified Specification Languages for Flexible and Agile Modelling." In 2019 ACM/IEEE 22nd International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C). IEEE, 2019. http://dx.doi.org/10.1109/models-c.2019.00074.

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

Power, Ken. "Stakeholder Identification in Agile Software Product Development Organizations: A Model for Understanding Who and What Really Counts." In 2010 AGILE Conference. IEEE, 2010. http://dx.doi.org/10.1109/agile.2010.17.

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

Silva, Fernando Selleri, Felipe Santana Furtado Soares, Angela Lima Peres, Ivanildo Monteiro de Azevedo, Pietro Pereira Pinto, and Silvio Romero de Lemos Meira. "A Reference Model for Agile Quality Assurance: Combining Agile Methodologies and Maturity Models." In 2014 9th International Conference on the Quality of Information and Communications Technology (QUATIC). IEEE, 2014. http://dx.doi.org/10.1109/quatic.2014.25.

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

Lazwanthi, M. R. R., Abeer Alsadoon, P. W. C. Prasad, S. Sager, and Amr Elchouemi. "Cultural impact on agile projects: Universal agile culture model (UACM)." In 2016 7th International Conference on Information and Communication Systems (ICICS). IEEE, 2016. http://dx.doi.org/10.1109/iacs.2016.7476067.

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

Reports on the topic "Agile model"

1

Sapp, Brandon, Melissa Harvey, Marion Toussaint, Sylvere Krima, Allison Barnard Feeney, and Herve Panetto. Agile for Model-Based-Standards Development. National Institute of Standards and Technology, March 2021. http://dx.doi.org/10.6028/nist.ams.100-40.

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

Kjeldgaard, E. A., D. A. Jones, G. F. List, and M. A. Tumquist. Planning and scheduling for agile manufacturers: The Pantex Process Model. Office of Scientific and Technical Information (OSTI), February 1998. http://dx.doi.org/10.2172/645535.

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

Mallon, Lawrence G. Strategic Mobility 21: Southern California Agile Supply Network Simulation Model, Architecture Report. Fort Belvoir, VA: Defense Technical Information Center, September 2006. http://dx.doi.org/10.21236/ada458514.

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

Willenbring, James M., Roscoe Ainsworth Bartlett, and Michael Allen Heroux. TriBITS lifecycle model. Version 1.0, a lean/agile software lifecycle model for research-based computational science and engineering and applied mathematical software. Office of Scientific and Technical Information (OSTI), January 2012. http://dx.doi.org/10.2172/1038225.

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

Thayer, Patrick M. Integration of the Munitions Agile Combat Support Model (MACSM) into LOGCAT and the JFACC Logistics Planning (JLP) Tools. Fort Belvoir, VA: Defense Technical Information Center, April 2000. http://dx.doi.org/10.21236/ada377161.

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

Zhang, Fumin. YIP: Generic Environment Models (GEMs) for Agile Marine Autonomy. Fort Belvoir, VA: Defense Technical Information Center, September 2013. http://dx.doi.org/10.21236/ada602485.

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

Zhang, Fumin. YIP: Generic Environment Models (GEMs) for Agile Marine Autonomy. Fort Belvoir, VA: Defense Technical Information Center, September 2012. http://dx.doi.org/10.21236/ada590320.

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

Rowley, Clarence W. Unsteady Aerodynamic Models for Flight Control of Agile Micro Air Vehicles. Fort Belvoir, VA: Defense Technical Information Center, August 2010. http://dx.doi.org/10.21236/ada547432.

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

Rowley, Clancy. Unsteady Aerodynamic Models for Flight Control of Agile Micro Air Vehicles. Fort Belvoir, VA: Defense Technical Information Center, January 2008. http://dx.doi.org/10.21236/ada476708.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Agile model' for particular source types:
Journal articles Dissertations / Theses Books
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