Relevant bibliographies by topics / Agile system development methodology

Contents

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

Academic literature on the topic 'Agile system development methodology'

Author: Grafiati
Published: 4 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 system development methodology.'

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 system development methodology"

1

Buchalcevova, Alena. "Application of Methodology Evaluation System on Current IS Development Methodologies." International Journal of Information Technologies and Systems Approach 11, no. 2 (July 2018): 71–87. http://dx.doi.org/10.4018/ijitsa.2018070105.

Full text
Abstract:
This article focuses on IS development methodologies, especially on new agile scaling frameworks. A significant need for large-scale agile is presented together with the evidence of its usage in companies. The aim of this article is to examine selected agile scaling methodologies and frameworks, and compare them to each other and with other IS development methodologies. To do so, the Methodology Evaluation System METES is utilized for the assessment and comparison. Assessed IS development methodologies can be then used by companies for the selection of the appropriate methodology. Furthermore, presenting the results of the assessment especially in the graphical form supports better understanding of these methodologies.
APA, Harvard, Vancouver, ISO, and other styles
2

Riesener, Michael, Christian Doelle, Stefan Perau, Philipp Lossie, and Guenther Schuh. "Methodology for iterative system modeling in agile product development." Procedia CIRP 100 (2021): 439–44. http://dx.doi.org/10.1016/j.procir.2021.05.101.

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

Rathore, Manvender, and Deepa Jose. "Software Upgradation Model Based on Agile Methodology." Oriental journal of computer science and technology 10, no. 2 (April 6, 2017): 352–58. http://dx.doi.org/10.13005/ojcst/10.02.14.

Full text
Abstract:
Agile software development work on twelve principle for software development which implies requirements and solutions evolved through the combined teamwork of disciplined and interdisciplinary teams. The objective of this paper is to connect agile methodology with Version Control System for more efficient and effective utilization of resources. In this proposed model based on agile methodology, the Version Control System plays a vital role to make work done faster as compared to SCRUM. This paper compares various existing agile methodologies. The efficiency of the proposed model is proved through comparative analysis with existing agile methods and using ANOVA mathematical model. Bitbucket as Version Control System is used as web based hosting service and the proposed model is compared by maintaining similar sprints in SCRUM and VSprint model. VCS and previous SRS documents are the important components of this proposed model which helps in increasing the work speed at different phases of software development which the existing models does not consider.
APA, Harvard, Vancouver, ISO, and other styles
4

Binsaleh, Muazzan, and Shahizan Hassan. "Systems Development Methodology for Mobile Commerce Applications." International Journal of Online Marketing 1, no. 4 (October 2011): 33–47. http://dx.doi.org/10.4018/ijom.2011100103.

Full text
Abstract:
There are several systems development methodologies including traditional and agile methodologies being utilized in current systems development. However, it could be argued that when developing mobile commerce applications, suitable development framework should be investigated as these applications are utilized in different contexts from fixed ecommerce applications. This study identifies suitable system development methodology framework for mobile commerce applications. In order to achieve this aim, the practitioners from seven organizations were asked to provide information about their development methodologies by answering the questions regarding mobile commerce application development. The questions were opened and aimed to explore practitioner’s perspectives on the development methodologies. From the practitioner’s perspectives, it was found that there were several development methodologies being used in mobile commerce application development and these can be classified into two different development frameworks which are heavyweight/traditional and lightweight/agile methodologies. The suitable methodology framework for mobile commerce application development thus was identified.
APA, Harvard, Vancouver, ISO, and other styles
5

Fateev, Nikolai, and Iryna Zaporozhets. "AGILE-METHODOLOGY IN SHIPBUILDING PROJECT MANAGEMENT IN CONDITIONS OF CLUSTER INTEGRATION." Scientific Journal of Polonia University 43, no. 6 (June 18, 2021): 307–11. http://dx.doi.org/10.23856/4339.

Full text
Abstract:
The aim of the article is to study the features of the development of cluster systems for the construction of transport vessels and develop on this basis recommendations for the use of agile methodology in the mechanisms of effective management in cluster integrations. The characteristic features of a project-oriented operating system with a matrix organizational structure have been determined. The principles of the agile methodology have been adapted to the management mechanisms of the shipbuilding cluster system. The examples of the use of agile approaches that complement and strengthen the existing matrix management structure in the shipbuilding cluster system are given. The agile approaches are implemented through: maintaining stable links in the supply chain at all stages of the life cycle of the cluster; focusing the cluster system as a whole on customer needs; creation of cross-functional teams for support and development of human resources; creation of a logistics center in accordance with the agile methodology, which is implemented through short feedback cycles and regular adaptation of supply processes; lean production ‒ from design to production at all stages. It is proposed to develop a corporate information system in business processes and supply chains of the shipbuilding cluster. Information flows connect cluster members, functions, supply chain management tasks, as well as different levels of management decision-making. Team cooperation between representatives of project organizations and the project management office of shipbuilding enterprises will ensure the development of the information system as a whole, as well as the integrity and consistency of individual elements. This confirms that the agile methodology provides flexibility in management and operational adaptation to changes in order to achieve the main goal ‒ the competitiveness of cluster integration and its elements.
APA, Harvard, Vancouver, ISO, and other styles
6

Lee, Yong-Hee, and Gun-Ho Lee. "Development Process Improvement of Open-market System by using Agile Methodology." KIPS Transactions:PartD 17D, no. 3 (June 30, 2010): 203–8. http://dx.doi.org/10.3745/kipstd.2010.17d.3.203.

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

Hassan, Ali, Soayba Younas, and Amiya Bhaumik. "Agile Methodology in an SaaS Deployment Project." International Journal of Information Technology Project Management 12, no. 2 (April 2021): 1–29. http://dx.doi.org/10.4018/ijitpm.2021040101.

Full text
Abstract:
Agile manifesto has proven its ability in managing and execution of projects in multiple industry sectors. Many researches have been conducted on the advantages and applicability of agile practices in software development and information technology industry. In this paper, empirical research has been conducted to identify the differences in agile management practices between software development and software as a service (SaaS) deployment projects. Case studies of a payment card industry (PCI) organization have been presented to identify key characteristics, tools, and methods of agile project management practices practically followed while implementing and managing of SaaS-based projects. Moreover, best suited agile management practices for pre- and post-deployment projects have also been discussed.
APA, Harvard, Vancouver, ISO, and other styles
8

Rodríguez-Hernández, V., M. C. Espino-Gudiño, J. L. González-Pérez, J. Gudiño-Bazaldúa, and Victor Castano. "Assessing quality in software development: An agile methodology approach." Journal of Advanced Computer Science & Technology 4, no. 2 (June 9, 2015): 225. http://dx.doi.org/10.14419/jacst.v4i2.4173.

Full text
Abstract:
<p>A novel methodology, result of 10 years of in-field testing, which makes possible the convergence of different types of models and quality standards for Engineering and Computer Science Faculties, is presented. Since most software-developing companies are small and medium sized, the projects developed must focuson SCRUM and Extreme Programming (XP), opposed to a RUP, which is quite heavy, as well as on Personal Software Process (PSP) and Team Software Process (TSP), which provide students with competences and a structured framework. ISO 90003:2004 norm is employed to define the processes by means of a quality system without new requirements or changing the existing ones. Also, the model is based on ISO/IEC 25000 (ISO (IEC 9126 – ISO/IEC 14598)) to allow comparing software built by different metrics.</p>
APA, Harvard, Vancouver, ISO, and other styles
9

Stormi, Kati Tuulikki, Teemu Laine, and Tuomas Korhonen. "Agile performance measurement system development: an answer to the need for adaptability?" Journal of Accounting & Organizational Change 15, no. 2 (June 3, 2019): 231–56. http://dx.doi.org/10.1108/jaoc-09-2017-0076.

Full text
Abstract:
Purpose The purpose of this study is to reflect upon the feasibility of agile methodologies, Scrum in particular, to supplement the procedural design and implementation of performance measurement systems (PMS). Design/methodology/approach The study is an interventionist case study that applied agile methodologies in the PMS development. Researchers actively participated in the PMS development, e.g. researchers designed some of the performance measurement prototypes in order to facilitate the agile development. Findings The study outlines an agile approach suitable for PMS development. The paper answers the topical needs for adaptability and agility in management accounting, by applying agile methodologies into PMS development. PMS development does not take place only as a project or process that systematically progresses from the measure selection to measure implementation. Instead, as the requirements for the PMS change during the development project, management may reject some measures and new measures emerge as the understanding about changing situations increase. Agile methodologies are a methodological way to respond to the inevitable change and to enhance management accounting adaptability. Research limitations/implications This study contributes to the PMS literature by proposing that agile development methodologies can advance organizational features that increase management accounting adaptability. As a result, the study proposes a new approach for PMS development to supplement existing ones. Agile methodologies are especially suitable for extending the PMS in new, yet relatively immature areas of performance measurement. The new approach applies Scrum principles in PMS development. By drawing from the theories of performance measurement (system) development and enabling PMS, the paper furthers academic understanding about agile development of accounting information systems. Practical implications Companies can use the proposed approach in PMS development, particularly after the initial system implementation in redesigning the system. The approach may increase the PMS impact in organizations and prevent PMS implementation failures. Originality/value The paper identifies the potential of using agile methodologies to enhance PMS adaptability and provides preliminary evidence of the potential of such approach in supplementing processual PMS development frameworks.
APA, Harvard, Vancouver, ISO, and other styles
10

Hanan Yulianto and Aries F. Firman. "Agile Project Management: Implementattion of Agile Working System in Bank Daya Usaha Sharia." Jurnal Indonesia Sosial Teknologi 2, no. 2 (February 21, 2021): 171–85. http://dx.doi.org/10.36418/jist.v2i2.91.

Full text
Abstract:
Bank Daya Usaha Sharia as one of player in banking industry, experiencing with intense competition along with digitalization trend in banking industry so that competitor not only came from other bank but also come from internet and telecommunication industry. Bank Daya Usaha Sharia internally have treat which is slow to access or penetrate the market so that selected agile project management as working system because the methodology or approach already proven. Research questions related to condition Bank Daya Usaha Sharia are which working unit can implementation agile project management, what kind of agile methodology that is relevance and how agile project management can be implemented or what kind of factor influenced. Based on those questions, this research have objective to find out which working unit can implemented agile project management with relevance agile methodology and find out factors influenced that implementation. This research using qualitative research approach through interview, interview has conducted for eight (8) respondents, which is employee at Bank Daya Usaha Sharia at many level of position from department head, division head and director. With this interview, expected discover information about type project, project characteristic, project strategy and factors influenced in implementation agile project management. To determine type of project and project characteristic, use an approach Project Characteristic Quadrants by Goal and Solution Uncertainty, while to determine project strategy using approach Project Management Strategies Based on Complexity and Uncertainty. This research only conducted for four (4) working unit, among others Human Capital, Internal Audit, Business Risk & Development and Business Planning. Based on interview result and analysis, there are conclusions, such as working unit that possible implemented Agile Project Management are Human Capital, Business Risk & Development and Business Planning with Agile Methodology SCRUM, while Internal Audit more appropriate to implemented traditional project management. Thirteen (13) factors influenced in Agile Project Management implementation such as requirement, goals, solutions, team members, collaborative, directions, adapt to change, empowerment, agile mindset and organization drive. While reason why Bank Daya Usaha Sharia selected Agile Project Management as working system and implemented at current are competition, investment and best practice.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Agile system development methodology"

1

Tabrez, Shams, and Islam Jan. "Documentation and Agile Methodology." Thesis, Uppsala universitet, Institutionen för informatik och media, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-212653.

Full text
Abstract:
Computer science in general and software engineering in specific is changing very fast. Software engineers are constantly using more innovative and more efficient ways to develop new software than in the past. This continuous evolution of software development methodologies has a great impact on both the software developed and the environment that the developers work-in. Agile software development methodologies are used to overcome many issues in the software development processes. One of the issues which still exists and needs to be addressed is the preparation of proper documentation along with the software. The work presented in this dissertation focuses on software documentation. The work starts by a thorough literature review which focuses on different aspects of software documentation and different agile methodologies. The thesis focuses on finding out the challenges that the developers faces during their development process. Two major questions addressed in the thesis. First one is to find the motivation to document in agile envirionment, whih is based on the hypothesis that there do exist a motivation. The second question is that how should documentation be produced such that we could avoid maximum possible potential problems. These questions are addressed with the help of different perspectives of the stockholders (i.e. developers and users) and the existing methods for documentation. A questionnaire was developed based on the nine categories of documentation, like user documents and system documents etc.. It included different questions related to the types of documents created in software development processes, the software development stage at which the documents are created and the importance of the documents. Questions from this questionnaire are then posted on agile specific discussion forums. Where many experienced and fresh practitioners participated in the discussion. We had a detailed discussion on every component of documentation and problems were identified by the practitioners. The questionnaire was also sent to different companies practicing agile methodology. we received about 14 responses as it was detailed questionnaire with about 34 questions. The responses of the discussion forum and survey are then analyzed and conclusions were drawn. The conclusions include that all the participants consider software documentation very important to the success of a software development project. the question of motivation is answered from the literature and opinions we received from experienced practitioners. While seven factor are identified that affect your documentation, to help solve the question of how should documentation be done.
APA, Harvard, Vancouver, ISO, and other styles
2

Grey, Johannes. "The development of a hybrid agile project management methodology / Grey, J." Thesis, North-West University, 2011. http://hdl.handle.net/10394/7004.

Full text
Abstract:
The aim of this study is to investigate whether a combination of agile system development methodologies (ASDMs) and project management methodologies (PMMs) can be used to develop a hybrid APMM that will have the ability to deliver information technology (IT) projects successfully in a constantly changing business and project environment. To achieve this objective, a literature review was conducted on the relatively well–established ASDMs by firstly defining a SDM and an ASDM. Each ASDM and its effectiveness are described, after which ASDMs in general are evaluated by considering their area of application, advantages and disadvantages. A comparison is then done of the seven different ASDMs using the four elements of an SDM (Huisman & Iivari, 2006:32) to emphasise some of the main similarities and differences amongst the different ASDMs. The seven ASDMs investigated in this study are Dynamic System Development Methodology, Scrum, Extreme Programming, Feature Driven Development, Crystal ASDMs ? Crystal Clear and Crystal Orange in particular, Adaptive Software Development and Lean Development. A literature review was also conducted on two structured and relatively well–established PMMs, PMBOK and PRINCE2, and a relatively new PMM called Agile Project Management. Each PMM is evaluated by considering their area of application, advantages, disadvantages and integration with other methodologies, after which a comparison is made of the different PMMs. The research was conducted by following a mixed methods research plan, which included the mixed methods research paradigm (combination of the interpretive research paradigm and the positivistic research paradigm), research methods (design science, case study and survey), quantitative and qualitative data–collection techniques (interviews and questionnaires), and dataanalysis techniques (cross–case and statistical). The reasons that projects fail and critical project success factors were studied and summarised to form the critical project success criteria, which were used to create the agile project success criteria. The ASDM best practice and PMM best practice frameworks were created by identifying whether a certain ASDM or PMM would satisfy a specific agile project success factor (APSF) of the agile project success criteria. The findings of each APSF in the respective frameworks were used as a foundation to develop a hybrid APMM (ver. 0) that would address the agile project success criteria. The hybrid APMM (ver. 0) was developed interpretively using design science (research approach) and constructivism by combining the strengths, addressing the weaknesses and bridging the gaps identified in the frameworks. The hybrid APMM (ver. 0) was then evaluated and improved by conducting an interpretive case study, which entailed interviewing participants from large and small organisations. Once the qualitative data collected had been analysed using cross–case analysis, the findings were incorporated in order to create an improved hybrid APMM (ver. 1). The hybrid APMM (ver. 1) too was evaluated and improved by conducting a survey, which entailed administering questionnaires to various respondents in order to collect quantitative and qualitative data. The findings of the statistical analysis of the data were also used to improve the hybrid APMM (ver. 1), resulting in the final hybrid APMM (ver. 2). This study demonstrates that a combination of ASDMs and PMMs can be used to develop a hybrid APMM with the ability to deliver IT projects in a constantly changing project and business environment.
Thesis (Ph.D. (Computer Science))--North-West University, Potchefstroom Campus, 2012.
APA, Harvard, Vancouver, ISO, and other styles
3

Schtein, Igor A. "Management Strategies for Adopting Agile Methods of Software Development in Distributed Teams." ScholarWorks, 2018. https://scholarworks.waldenu.edu/dissertations/5417.

Full text
Abstract:
Between 2003 and 2015, more than 61% of U.S. software development teams failed to satisfy project requirements, budgets, or timelines. Failed projects cost the software industry an estimated 60 billion dollars. Lost opportunities and misused resources are often the result of software development leaders failing to implement appropriate methods for managing software projects. The purpose of this qualitative multiple case study was to explore strategies software development managers use in adopting Agile methodology in the context of distributed teams. The tenets of Agile approach are individual interaction over tools, working software over documentation, and collaboration over a contract. The conceptual framework for the study was adapting Agile development methodologies. The targeted population was software development managers of U.S.-based companies located in Northern California who had successfully adopted Agile methods for distributed teams. Data were collected through face-to-face interviews with 5 managers and a review of project-tracking documentation and tools. Data analysis included inductive coding of transcribed interviews and evaluation of secondary data to identify themes through methodological triangulation. Findings indicated that coaching and training of teams, incremental implementation of Agile processes, and proactive management of communication effectiveness are effective strategies for adopting Agile methodology in the context of distributed teams. Improving the efficacy of Agile adoption may translate to increased financial stability for software engineers across the world as well as accelerate the successful development of information systems, thereby enriching human lives.
APA, Harvard, Vancouver, ISO, and other styles
4

Ispir, Mustafa. "Test Driven Development Of Embedded Systems." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/12605630/index.pdf.

Full text
Abstract:
In this thesis, the Test Driven Development method (TDD) is studied for use in developing embedded software. The required framework is written for the development environment Rhapsody. Integration of TDD into a classical development cycle, without necessitating a transition to agile methodologies of software development and required unit test framework to apply TDD to an object oriented embedded software development project with a specific development environment and specific project conditions are done in this thesis. A software tool for unit testing is developed specifically for this purpose, both to support the proposed approach and to illustrate its application. The results show that RhapUnit supplies the required testing functionality for developing embedded software in Rhapsody with TDD. Also, development of RhapUnit is a successful example of the application of TDD.
APA, Harvard, Vancouver, ISO, and other styles
5

Knublauch, Holger [Verfasser]. "An agile development methodology for knowledge-based systems including a Java framework for knowledge modeling and appropriate tool support / Holger Knublauch." Ulm : Universität Ulm. Fakultät für Informatik, 2002. http://d-nb.info/1015324703/34.

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

Rangevik, Alexander. "Software Development across Time Zones : A Study of Globally Distributed Software Development in Small Enterprises." Thesis, Uppsala universitet, Informationssystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-203325.

Full text
Abstract:
Globally distributed software development has become an important topic for small and medium enterprises. However, the distinct requirements of small and medium enterprises (SMEs) are still not fullyunderstood. To contribute to this growing discussion, I will present an ethnographical field study of a Swedish software company engaged in a distributed development practice with its American branch. By applying a theoretical view based on communication, coordination and control over time, space and socio/cultural difference, I show to what extent a distributed software development model affects SMEs. Whereproblems related to formal and informal communication, knowledge sharing, articulation work and programming methodologies are discussed. My findings suggest that organizational adjustments are needed for SMEs in order to take advantage of distributed software development (DSD), that specialized tools supporting coordination and articulation work is not so common in practice and that certain adjustment to agile methodologies could be made in order to better support DSD.
APA, Harvard, Vancouver, ISO, and other styles
7

Krajíček, Michal. "Systém pro podporu komunikace agilního řízení projektů." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2013. http://www.nusl.cz/ntk/nusl-412884.

Full text
Abstract:
The thesis deals with problems of agile methodologies in the settings of virtual teams. It begins with the description of virtual teams and their models and deals with both theoretical and practical aspects of mutual communication of their team members. The thesis follows with general characteristics of agile approach and their demonstration on representative methodologies. One of them (methodology Scrum) is described in detail in the next chapter and linked with possibilities of its deployment within virtual teams. Practical part of the thesis deals with the design and implementation of a software application that is focused on effective communication support of virtual teams that utilize Scrum. Deployment of this application is discussed within a case study of a real project which team faced problems of agile software development in the settings of virtual team on a daily basis.
APA, Harvard, Vancouver, ISO, and other styles
8

Hollar, Ashby Brooks. "Cowboy : an agile programming methodology for a solo programmer /." VCU Scholars Compass, 2006. http://hdl.handle.net/10156/1400.

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

Šilinskaitė, Viktorija. "Agile požiūrio taikymas internetinių svetainių kūrime." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2008. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2008~D_20080128_140321-87884.

Full text
Abstract:
Greitas internetinių svetainių skaičiaus padidėjimas per paskutinius keletą metų rodo informacijos, pasiekiamos internetu, svarbą. Daug įmonių kuria internetines svetaines, bet jie susiduria su problemomis, susijusiomis su reikalavimų pasikeitimais kūrimo eigoje. Šiame darbe nagrinėjama Agile požiūrio pritaikymo galimybės internetinėms svetainėms kurti. Darbe atlikta jau esamų metodų analizė, kuri parodė, kad internetinių svetainių kūrimui nėra visiškai tinkamo metodo, todėl darbo uždavinys - sukurti metodą, paremtą Scrum ir FDD savybėmis internetinių svetainių kūrimui.
A fast increase in the number of web sites the last years, shows the importance of information existing in web sites giving the possibility for users to have access to it. Many companies create websites, but they face problems related with requirements changing until the developing process completes. In this work you will find analysis of software development methods. Agile approach allows changing requirements even in last phase of the developing process. Creating a web site does not follow one single path and there is no ideal method creating a web site. In this dissertation will be analyzed a method for web sites development based on Agile approach.
APA, Harvard, Vancouver, ISO, and other styles
10

King, Gary R. "Using the agile development methodology and applying best practice project management processes." Thesis, Monterey, California: Naval Postgraduate School, 2014. http://hdl.handle.net/10945/44596.

Full text
Abstract:
Approved for public release; distribution is unlimited
There are many SOFtware development life-cycle models. Each one has its own advantages and disadvantages, forcing program management to select carefully before embarking on a full-scale development effort. A popular choice today is the Agile development model, due to its more informal processes and ability to adapt easily to changes. However, one of these positive elements is also one of its negative aspects. These less formal processes can lead developers to use the Agile model as authorization to avoid any process efforts, leading to a difficult project management problem. This thesis explores the manner by which the Agile development model may be executed in a disciplined manner. The thesis also describes the application of various techniques to create a robust development environment while still maintaining the value the methodology brings. In addition, it also highlights the importance of selecting each practice carefully and applying that practice uniquely to each project to ensure maximum performance.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Agile system development methodology"

1

Agile for project managers. Boca Raton, Florida: CRC Press, Taylor & Francis Group, 2015.

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

Deuff, Dominique. User-centered agile method. London, UK: ISTE Ltd., 2013.

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

James, Newkirk, ed. Visual studio team system: Better software development for agile teams. Upper Saddle River, NJ: Addison-Wesley, 2007.

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

Agile IT security implementation methodology: Plan, develop, and execute your organization's robust agile security with IBM's Senior IT Specialist. Birmingham: Packt Publishing, 2011.

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

Hice, G. F. System development methodology for technical information systems. Rijswijk, The Netherlands: Pandata, 1988.

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

The prototyping methodology. Englewood Cliffs, N.J: Prentice-Hall, 1985.

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

Jane, Wood. Joint application development. 2nd ed. New York: Wiley, 1995.

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

Schrönen, Michael. Methodology for the development of microprocessor-based safety-critical systems. Aachen: Shaker, 1998.

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

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

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

Borutzky, Wolfgang. Bond graph methodology: Development and analysis of multidisciplinary dynamic system models. London: Springer, 2010.

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

Book chapters on the topic "Agile system development methodology"

1

Bustard, D., and F. Keenan. "Soft Systems Methodology: An Aid to Agile Development?" In Information Systems Development, 25–38. Boston, MA: Springer US, 2008. http://dx.doi.org/10.1007/978-0-387-68772-8_3.

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

Staykova, Kamenka, and Danail Dochev. "Development of Lexico-Grammar Resources for Natural Language Generation (Experience from AGILE Project)." In Artificial Intelligence: Methodology, Systems, and Applications, 242–51. Berlin, Heidelberg: Springer Berlin Heidelberg, 2000. http://dx.doi.org/10.1007/3-540-45331-8_23.

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

Dhir, Saru, Deepak Kumar, and V. B. Singh. "Success and Failure Factors that Impact on Project Implementation Using Agile Software Development Methodology." In Advances in Intelligent Systems and Computing, 647–54. Singapore: Springer Singapore, 2018. http://dx.doi.org/10.1007/978-981-10-8848-3_62.

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

Broy, Manfred, Wolfgang Böhm, and Bernhard Rumpe. "Advanced Systems Engineering." In Model-Based Engineering of Collaborative Embedded Systems, 353–64. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-62136-0_19.

Full text
Abstract:
AbstractAdvanced systems engineering (ASE) is a new paradigm for agile, efficient, evolutionary, and quality-aware development of complex cyber-physical systems using modern digital technologies and tools. ASE is essentially enabled by smart digital modeling tools for specifying, modeling, testing, simulating, and analyzing the system under development embedded in a coherent and consistent methodology.The German Federal Ministry of Education and Research (BMBF) projects SPES2020, SPES_XT, and CrESt offer such a methodology and framework for model-based systems engineering (MBSE). The framework provides a comprehensive methodology for MBSE that is independent of tools and modeling languages. The framework also offers a comprehensive set of concrete modeling techniques and activities that build on a formal, mathematical foundation. The SPES framework is based on four principles that are of paramount importance: (1) Functional as well as non-functional requirements fully modeled and understood at system level. (2) Consistent consideration of interfaces at each system level. (3) Decomposition of systems into subsystems and their interfaces. (4) Models for a variety of cross-sectional topics (e.g., variability, safety, dynamics).
APA, Harvard, Vancouver, ISO, and other styles
5

Hofer, Marvin, Sebastian Hellmann, Milan Dojchinovski, and Johannes Frey. "The New DBpedia Release Cycle: Increasing Agility and Efficiency in Knowledge Extraction Workflows." In Semantic Systems. In the Era of Knowledge Graphs, 1–18. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-59833-4_1.

Full text
Abstract:
Abstract Since its inception in 2007, DBpedia has been constantly releasing open data in RDF, extracted from various Wikimedia projects using a complex software system called the DBpedia Information Extraction Framework (DIEF). For the past 12 years, the software received a plethora of extensions by the community, which positively affected the size and data quality. Due to the increase in size and complexity, the release process was facing huge delays (from 12 to 17 months cycle), thus impacting the agility of the development. In this paper, we describe the new DBpedia release cycle including our innovative release workflow, which allows development teams (in particular those who publish large, open data) to implement agile, cost-efficient processes and scale up productivity. The DBpedia release workflow has been re-engineered, its new primary focus is on productivity and agility, to address the challenges of size and complexity. At the same time, quality is assured by implementing a comprehensive testing methodology. We run an experimental evaluation and argue that the implemented measures increase agility and allow for cost-effective quality-control and debugging and thus achieve a higher level of maintainability. As a result, DBpedia now publishes regular (i.e. monthly) releases with over 21 billion triples with minimal publishing effort .
APA, Harvard, Vancouver, ISO, and other styles
6

Peroni, Silvio. "A Simplified Agile Methodology for Ontology Development." In Lecture Notes in Computer Science, 55–69. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-54627-8_5.

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

Singh, Neeraj Kumar. "Critical System Development Methodology." In Using Event-B for Critical Device Software Systems, 61–77. London: Springer London, 2013. http://dx.doi.org/10.1007/978-1-4471-5260-6_4.

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

Torrecilla-Salinas, C. J., J. Sedeño, M. J. Escalona, and M. Mejías. "Using Agile Methods for Infrastructure Projects: A Practical Experience." In Information System Development, 459–71. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-07215-9_37.

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

Duchowski, Andrew T. "Table-Mounted System Software Development." In Eye Tracking Methodology, 105–20. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-57883-5_10.

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

Duchowski, Andrew T. "Head-Mounted System Software Development." In Eye Tracking Methodology, 67–84. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-57883-5_7.

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

Conference papers on the topic "Agile system development methodology"

1

Aiello, G., M. Alessi, M. Bruccoleri, C. D'Onofrio, and G. Vella. "An Agile methodology for Manufacturing Control Systems development." In 2007 5th IEEE International Conference on Industrial Informatics. IEEE, 2007. http://dx.doi.org/10.1109/indin.2007.4384879.

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

Al-azawi, Rula, Aladdin Ayesh, and Mohaned Al Obaidy. "Towards Agent-based Agile approach for Game Development Methodology." In 2014 World Congress on Computer Applications and Information Systems (WCCAIS). IEEE, 2014. http://dx.doi.org/10.1109/wccais.2014.6916626.

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

Tanveer, Binish, Anna Maria Vollmer, and Stefan Braun. "A hybrid methodology for effort estimation in Agile development." In ICSSP '18: International Conference on the Software and Systems Process 2018. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3202710.3203152.

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

Chaudhari, Ashvini R., and Shashank D. Joshi. "Study of effect of Agile software development Methodology on Software Development Process." In 2021 Second International Conference on Electronics and Sustainable Communication Systems (ICESC). IEEE, 2021. http://dx.doi.org/10.1109/icesc51422.2021.9532842.

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

Rai, Anand Kumar, Shalini Agarwal, and Abhishek Kumar. "A Novel Approach for Agile Software Development Methodology Selection Using Fuzzy Inference System." In 2018 International Conference on Smart Systems and Inventive Technology (ICSSIT). IEEE, 2018. http://dx.doi.org/10.1109/icssit.2018.8748767.

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

Cordeiro, Lucas, Raimundo Barreto, Rafael Barcelos, Meuse Oliveira, Vicente Lucena, and Paulo Maciel. "Agile Development Methodology for Embedded Systems: A Platform-Based Design Approach." In 14th Annual IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'07). IEEE, 2007. http://dx.doi.org/10.1109/ecbs.2007.16.

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

Ilyés, Enikő. "Create your own agile methodology for your research and development team." In 2019 Federated Conference on Computer Science and Information Systems. IEEE, 2019. http://dx.doi.org/10.15439/2019f209.

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

Riesener, Michael, Christian Doelle, Sebastian Schloesser, and Guenther Schuh. "Prototype Design in Agile Product Development Processes for Technical Systems." In ASME 2019 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. American Society of Mechanical Engineers, 2019. http://dx.doi.org/10.1115/detc2019-97008.

Full text
Abstract:
Abstract Agile development processes such as Scrum have been successfully applied in the software industry for many years. Based on experience, industrial practitioners indicate three predominant benefits of agile development processes compared to traditional software development processes. First of all, development results better fit customers’ and other stakeholders’ needs. That is because they are intensively involved in the development process by receiving, applying and assessing functional software increments in a defined cadence throughout the development process. Secondly, agile development processes better cope with unexpected changes in the development process due to the built-in process flexibility. Lastly, development speed has significantly increased in most of the agile software development projects, resulting in a shorter time-to-market. Especially in the context of radical innovations for technical systems, manufacturing companies are striving for approaches to optimize their development processes in a similar direction. Traditional plan-oriented development approaches such as VDI 2221 or Cooper’s Stage-Gate Process turn out to be insufficiently customer oriented, too inflexible and project duration is usually too long to reach an adequate time-to-market. For that reason, a large community in academia and industrial practice is developing and implementing approaches to adapt agile software development practices for the development of technical systems. However, a current study in industrial practice reveals that out of 23 objectives, that are expected when introducing agile development processes to technical systems, the three objectives mentioned above, show the largest negative deviations from expected benefit to realized benefit. Therefore, the overall goal of this research is to address these gaps by developing an explicit methodological approach for an agile development of technical systems. It turns out, that mainly the role of prototyping and the way product specifications are handled during the development process change significantly in the course of introducing agility to development of technical systems. Agile practitioners strive to not necessarily define product specifications comprehensively upfront, as it is postulated in plan-oriented development processes. In contrast, product specifications, which are of major importance to the overall development project, are specified and validated with customers and other stakeholders in early prototypes. Therefore, prototypes are realized in a defined cadence throughout the development process to gradually specify and validate the product. However, the way product specifications are prioritized and selected in the development of technical systems has to differ substantially from the general way Scrum or other existing agile development processes propose. That is because technical systems are characterized by multiple technical interrelations, resulting in informational dependencies for the development process. For that reason, a prioritization along criteria such as customer value, development effort and risk seems too narrow in the context of technical systems. In fact, the prioritization of product specifications has to consider both, the value being generated by their realization as well as the informational dependencies towards other specifications. Furthermore, when designing a prototype, time constraints need to be particularly considered due to lead times in parts delivery and prototype production. Therefore, this paper introduces a methodology to prioritize and select technical design parameters in agile development processes. The methodology can be applied in the cyclical sprint planning that aims at defining the scope of the next prototype to be developed. As outlined above, the major paradigms of value generation, informational dependencies as well as lead-time and effort are crucial when adapting agile for technical systems and are consequently implemented in the methodology. These paradigms are operationalized to explicitly address the mentioned major objectives of agile development processes, which are currently showing are large gap between expected benefit and realized benefit in industrial practice. The methodology is applied to the real development process of an RGB laser light source for digital cinema projectors, which is summarized as a case study in the paper. Insights from this application are equally discussed as the resulting next steps in further developing and aligning the methodology to the needs of industrial practice.
APA, Harvard, Vancouver, ISO, and other styles
9

dos Santos, Vinicius Salustiano Alves, and Edna Dias Canedo. "Agile methodology in the software development: Case study: Electoral justice of Brazil." In 2014 9th Iberian Conference on Information Systems and Technologies (CISTI). IEEE, 2014. http://dx.doi.org/10.1109/cisti.2014.6876981.

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

Krishna, Arun B., and Sunil E. Abraham. "Statistical analysis of memory and performance non functional requirements in real time embedded system development for agile methodology." In 2015 International Conference on Industrial Instrumentation and Control (ICIC). IEEE, 2015. http://dx.doi.org/10.1109/iic.2015.7150757.

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

Reports on the topic "Agile system development methodology"

1

Savacool, Ed, and Stanley Wheatley. Agile Port System Transition Support Transition Plan Development. Fort Belvoir, VA: Defense Technical Information Center, July 2013. http://dx.doi.org/10.21236/ada589378.

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

Hayhoe, G. F. ISE System Development Methodology Manual. Office of Scientific and Technical Information (OSTI), February 1992. http://dx.doi.org/10.2172/10179000.

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

Wise, Larry. Methodology Investigation, Aviation Test Management System Concept Development. Fort Belvoir, VA: Defense Technical Information Center, November 1990. http://dx.doi.org/10.21236/ada237349.

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

Mavris, Dimitri N. Design Methodology Development and Education for Naval System Affordability. Fort Belvoir, VA: Defense Technical Information Center, October 2002. http://dx.doi.org/10.21236/ada406812.

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

Li, Zongzhi, and Kumares Sinha. Methodology for the Development of a Highway Asset Management System for Indiana. West Lafayette, IN: Purdue University, 2004. http://dx.doi.org/10.5703/1288284313267.

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

Jupiter, David L., and Lisa J. Reuter. The Development of a Business Case Analysis for the Acquisition of the Agile Rapid Global Combat Support System Used for the United States Marine Corps' Ground Equipment. Fort Belvoir, VA: Defense Technical Information Center, December 2006. http://dx.doi.org/10.21236/ada460324.

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

Shabana, Ahmed A. Integration of Computational Geometry, Finite Element, and Multibody System Algorithms for the Development of New Computational Methodology for High-Fidelity Vehicle Systems Modeling and Simulation. ADDENDUM. Fort Belvoir, VA: Defense Technical Information Center, November 2013. http://dx.doi.org/10.21236/ada593312.

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

Tabinskyy, Yaroslav. VISUAL CONCEPTS OF PHOTO IN THE MEDIA (ON THE EXAMPLE OF «UKRAINER» AND «REPORTERS»). Ivan Franko National University of Lviv, March 2021. http://dx.doi.org/10.30970/vjo.2021.50.11099.

Full text
Abstract:
The article is devoted to the analysis of the main forms of visualization in the media related to photo. The thematic visual concepts are described in accordance with the content of electronic media, which consider the impact of modern technologies on the development of media space. The researches of the Ukrainian and foreign educational institutions concerning the main features of modern photo is classificate. Modifications and new visual forms in the media are singled out. The main objective of the article is to study the visual concepts of modern photo and identify ideological and thematic priorities in photo projects. To achieve the main objective in the article a certain methodology were used. Due to the historical-theoretical description it was possible to substantiate the study of visual concepts. The conceptual-system method was used to study the subject of media photo projects. The main results of the research are the definition of visual concepts of photo on the example of electronic media and the identification of the main thematic features in the process of visual filling of the media space. Based on the study, we can conclude that today the information field needs quality visual content. For successful creation of visual concepts it is necessary to single out thematic features of modern photo and to carry out classifications on ideological and semantic signs. Given the rapid development of digital technologies, the topic of the scientific article we offer is relevant for scientists, journalists, media researchers, visual journalism experts and photojournalists. Modern space is filled with a large number of pictorial materials, which in most cases form specific images, patterns or stereotypes in the mind of the reader (viewer). Also important is the classification of photo used in journalistic publications. That is why there is a need to explore the content and principles of distribution of ideological priorities of photo in the media. The substantiation of scientists about the important place of photography in the modern media space and the future development of visual technologies, which already use artificial intelligence, is relevant.
APA, Harvard, Vancouver, ISO, and other styles
9

Methodology of sports working capacity level increase in basketball players on the basis of stimulation and rehabilitation means. Viktor V. Andreev, Igor E. Konovalov, Dmitriy S. Andreev, Aleksandr I. Morozov, March 2021. http://dx.doi.org/10.14526/2070-4798-2021-16-1-5-11.

Full text
Abstract:
The increased level of modern sport development increases the demands claimed on different aspects of the training process with further rehabilitation organization and realization. That is why we still have the problem of an adequate and effective integral system creation. The mentioned direction has a direct connection with the activity of scientists, coaches- practitioners and sports clubs. They have to work within one mechanism of interaction. Materials. Studying the level of working capacity influence stimulation and organism rehabilitation means on an organism of basketball players from higher educational establishments on the basis of a wildgrowing plant root “snowdon rose” (Rhodiola rosea), classical massage with special oils and contrast shower application. Research methods. The following methods were used in the experiment: scientific-methodical sources analysis concerning the level of working capacity and athletes’ functional rehabilitation increase; functional tests; the received video material with the indices analysis; mathematical statistics. The research realization was on the basis of N.F. Katanov State University, Khakassia and Khakassia Technical Institute (branch) of Siberian Federal University in Abakan. Results. During the research work we stated qualitative and quantitative indices of athletes’ coordinating endurance with the help of video together with other mentioned above rehabilitation means; the received results were handled and we revealed positive changes in the studied information values of basketball players’ motor sphere and respiratory system. Conclusion. The results analysis, received after the research, helped to come to the following conclusion: out of the presented components the biological factor in a form of a wild-growing plant root “snowdon rose” (Rhodiola rosea) has the main influence on the working capacity and functional rehabilitation of basketball players’ organisms.
APA, Harvard, Vancouver, ISO, and other styles
10

National report 2009-2019 - Rural NEET in Romania. OST Action CA 18213: Rural NEET Youth Network: Modeling the risks underlying rural NEETs social exclusion, December 2020. http://dx.doi.org/10.15847/cisrnyn.nrro.2020.12.

Full text
Abstract:
This report describes a particular situation of young population in Romania: the population of NEETs, with a focus on rural NEETs.Based on a complex methodology which uses data from different national sources (INS) and international sources (Eurostat, EU Labour Force Survey-EU-LFS, OECD),this report gives an overview of the evolution and particularities of NEETs in Romania during the previous deca-de, namely 2009-2019.Within the last ten years, the population of NEETs in Romania has grown rapidly, placing Ro-mania in first place in the EU-28 in terms of the share of this population among the young population. Thus, in 2009 Romania with a NEET rate of 13.9%, occupied first places in the EU, along with Bulgaria (19.5%), Italy (17.5%), Latvia (17.5%) (Eurostat, 2020). A decade later, in Bulgaria and Latvia, the NEET rate decreased significantly to 13.7% and 7.9%, respectively, but in Romania and Italy it increased by more than 1pp: 14.7% in Romania and 18.1% in Italy. (Eurostat, 2020). The causes for this are both individual (way of life, socio-familial origin, expectations and aspirations) and socio-economic (accessibility of the education system, development of lifelong learning, correspondence between education and labour market demand, particu-larities of the Romanian labour market, socio-economic policies supported by central and local authorities, etc.)
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Agile system development methodology' 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