Relevant bibliographies by topics / Methodologies of flexible software development

Contents

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

Academic literature on the topic 'Methodologies of flexible software development'

Author: Grafiati
Published: 4 June 2025
Last updated: 23 June 2025

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 'Methodologies of flexible software development.'

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 "Methodologies of flexible software development"

1

Gidroets, M. O., and L. I. Grishanova. "SOFTWARE DEVELOPMENT METHODOLOGY." System analysis and logistics 4, no. 26 (2020): 45–53. http://dx.doi.org/10.31799/2007-5687-2020-4-45-53.

Full text
Abstract:
This article discusses the main methodologies for developing software products. The most common cascading and flexible methodologies are characterized. Considered the pros and cons of each methodology. The situations of expedient application of cascade and flexible approaches to software product development are determined. Key words: development methodologies, waterfall model, agile model, project management, planning, software product development.
APA, Harvard, Vancouver, ISO, and other styles
2

Lytvynov, V. V., I. V. Bogdan, A. О. Zadorozhnyi, and I. V. Bilous. "Task prioritization methods in flexible software development methodologies." Mathematical machines and systems 2 (2020): 70–78. http://dx.doi.org/10.34121/1028-9763-2020-2-70-78.

Full text
Abstract:
The modern task prioritization methods that are used in flexible software development methodologies are discussed in the paper. Very flexible development methodologies such as Scrum, Kunban and others are currently the most popular because they allow making adjustments to it at any stage of a project, to improve the quality of the created product through daily monitoring of its creation and quickly release the first versions of the software. All task prioritization methods that are used in software projects de-velopment including flexible methodologies are divided into those that take into account the point of view of the development team and those that are based on various quantitative assessments, among which various metrics, expert opinions, points of view of those who are interested in the project, availa-ble classifications etc. Among the considered prioritization methods, which take into account the opin-ion of the development team, there are such popular and actively used nowadays methods, as MoSCoW, story map (User story mapping) and proactive improvement. Among the considered methods, based on quantitative assessment, is Kano's model, the method based on the creation of evaluation sheets, the method for estimating relative priorities for a set of functions offered by Carl Wigers and the method of structuring quality functions (Quality Function Deployment). Depending on the features of the project, customer requirements, the wishes of the development team and the other objective or subjective fac-tors, the project can use one or several prioritization methods at the same time or the combination of them. In addition, some of the considered methods can be used in short-term planning, the others – in the long-term, but there are those that can be used at each stage.
APA, Harvard, Vancouver, ISO, and other styles
3

РУДНИЧЕНКО, Н. Д. "FLEXIBLE METHODOLOGIES EFFICIENCY RESEARCH IN PRACTICE OF MODERN SOFTWARE DEVELOPMENT COMPANIES." Transport development, no. 1(1) (September 27, 2017): 171–77. http://dx.doi.org/10.33082/td.2017.1-1.20.

Full text
Abstract:
The results of research on the effectiveness of the use of flexible software development methodologies in the practice of modern companies are presented. The results of the survey on the use of project management methodologies, as well as the results of the cost analysis of 9 different projects are presented. The peculiarities of various agile development methodologies are revealed at their practical application.
APA, Harvard, Vancouver, ISO, and other styles
4

Ganoje, Prayag. "Applying Agile Methodologies in Regulated Medical Device Software Development." Applied Medical Research 9, no. 1 (2022): 1–5. http://dx.doi.org/10.47363/amr/2022(9)245.

Full text
Abstract:
This research paper explores the application of Agile methodologies in the highly regulated field of medical device software development. As the healthcare industry continues to evolve rapidly, there is an increasing need for efficient and flexible software development processes that can meet stringent regulatory requirements while delivering high-quality, innovative medical device software. This study examines the challenges of implementing Agile practices in a regulated environment, proposes strategies for adapting Agile methodologies to meet regulatory standards, and presents case studies of successful implementations. The paper also discusses best practices, potential pitfalls, and future trends in Agile medical device software development.
APA, Harvard, Vancouver, ISO, and other styles
5

Il'chenko, E. "FLEXIBLE METHODOLOGIES IN MANAGING AN IT PROJECT DEVELOPMENT TEAM." Management of the Personnel and Intellectual Resources in Russia 12, no. 6 (2024): 24–28. http://dx.doi.org/10.12737/2305-7807-2024-12-6-24-28.

Full text
Abstract:
One of the important issues in the implementation of the strategy for the socio-economic development of the country and regions is the problem of managing the intellectual resources of companies. In modern conditions of economic development, the intellectual resources of companies are becoming increasingly important. The key task of enterprises in the IT field is to increase the efficiency of ongoing business processes. Problems related to the organization and management of teamwork are becoming increasingly important. Choosing the optimal approach to team management in a certain situation plays a significant role in the development of companies. [1]. The performance of software development companies largely depends on the correctness of the chosen software development methodology.
 
 The purpose of the study is to study approaches to managing the intellectual resources of companies, as well as choosing the optimal approach to managing a team of IT project developers. The article presents the results of a study of existing methodologies, and also makes an attempt to form an optimal and adequate model for managing a team of IT project developers.
APA, Harvard, Vancouver, ISO, and other styles
6

Anisimov, Alexander Yu, Elena N. Tokmakova, and Alexander E. Trubin. "Comparative Analysis of Flexible Software Development Methodologies in Modern Highly Competitive Markets." Journal of Modern Competition 18, no. 5 (2024): 111–23. https://doi.org/10.37791/2687-0657-2024-18-5-111-123.

Full text
Abstract:
The problem of choosing an effective project management methodology is one of the key tasks in the field of information systems development. In the modern world, software development is one of the most demanded types of project activities, and in almost every field of production specialized software (software) is used, which plays a central role in the functioning of enterprises. In this regard, the creation of an effective development process becomes the most important condition for the successful implementation of the project. Despite the existence of a large number of modern management methodologies, choosing the most appropriate one remains a difficult task that requires a detailed analysis of goals and criteria. The success of the project, both for the contractor and for the customer, largely depends on the correct choice of the management model. The purpose of the study is to analyze key aspects of software development management methodologies in highly competitive modern markets. The main objective of the study includes a comparative analysis of flexible software development management methodologies. The article presents the results of a comparative analysis of existing flexible methodologies. The expediency of using the Kanban methodology as a software development management tool is substantiated, and potential risks associated with choosing the optimal methodology are identified. The results obtained have both theoretical and practical significance, contributing to the informed choice of the most appropriate project management methodology in the field of IP development in modern highly competitive markets.
APA, Harvard, Vancouver, ISO, and other styles
7

Jain, Parita, Arun Sharma, and Laxmi Ahuja. "Software Maintainability Estimation in Agile Software Development." International Journal of Open Source Software and Processes 9, no. 4 (2018): 65–78. http://dx.doi.org/10.4018/ijossp.2018100104.

Full text
Abstract:
Agile methodologies have gained wide acceptance for developing high-quality products with a quick and flexible approach. However, until now, the quality of the agile process has not been validated quantitatively. Quality being important for the software system, there is a need for measurement. Estimating different quality factors will lead to a quality product. Also, agile software development does not provide any precise models to evaluate maintainability. Therefore, there is a need for an algorithmic approach that can serve as the basis for estimation of maintainability. The article proposes an adaptive neuro-fuzzy inference system (ANFIS) model for estimating agile maintainability. Maintainability is one of the prominent quality factors in the case of agile development. The proposed model has been verified and found to be effective for assessing the maintainability of agile software.
APA, Harvard, Vancouver, ISO, and other styles
8

Vavilenkova, Anastasiia. "ANALYSIS OF FLEXIBLE METHODOLOGIES OF SOFTWARE DEVELOPMENT FOR IMPLEMENTATION IN TEAM PROJECTS." Bulletin of the National Technical University «KhPI» Series: New solutions in modern technologies, no. 1(7) (April 23, 2021): 39–46. http://dx.doi.org/10.20998/2413-4295.2021.01.06.

Full text
Abstract:
The materials of the article analyze the main models of the software life cycle, which underlie the flexible methodologies of software development to identify the features of its application during the implementation of team projects. It was found that the use of classical life cycle models, in particular, cascade, spiral, incremental, V-shaped and iterative, is not effective in implementing all modern aspects of software development based on the use of new information technologies. It was conducted the comparative analysis of the most popular flexible methodologies of software development Agile, Scrum, Kanban, RUP, DSDM, RAD on such indicators as life cycle model, number of iterations, purpose of project creation and types of projects for implementation, priorities, possibility of interaction with the customer, adaptation to change. The advantages and disadvantages of flexible software development methodologies made it possible to single out the MSF methodology, which is based on the harmonization of cascading, spiral and iterative models of the software development lifecycle and allows you to choose the Scrum template as the most successful for implementing and demonstrating work in team development projects. MSF uses an approach that involves the gradual creation of a working product with some functionality that reflects the requirements for the final product at this stage. It is proposed to use Microsoft solutions based on Visual Studio and Team Foundation Server for centralized management of team project elements, use of visual architecture modeling tools, code quality management capabilities and obtaining all project team members up-to-date information on project status. This is because the MSF model combines five following main models: team model; process model (sequence of actions required to build a team project); discipline of project management (provides comprehensive planning of all stages of the team project, budget management, resources, costs, scheduling); risk management disciplines and readiness management disciplines (assessment of team project members' knowledge for further distribution of team roles). The article demonstrates an example of creating a training team project based on the use of the Scrum flexible methodology template in Visual Studio based on Team Foundation Server.
APA, Harvard, Vancouver, ISO, and other styles
9

Kordunova, Yuliia, Olga Smotr, Igor Kokotko, and Romanna Malets. "ANALYSIS OF THE TRADITIONAL AND FLEXIBLE APPROACHES TO CREATING SOFTWARE IN DYNAMIC CONDITIONS." Management of Development of Complex Systems, no. 47 (September 27, 2021): 71–77. http://dx.doi.org/10.32347/2412-9933.2021.47.71-77.

Full text
Abstract:
The success of the project depends on the quality of management, in particular, the management methodology chosen for the project. When it comes to developing new software, the development team and the customer are faced with the methodology choice and approach to the development of this software. The purpose of this work is to explore and analyze two completely different approaches to software development – the traditional (Waterfall) and the flexible (Agile). In the article are described implementation principles, advantages, and disadvantages of traditional (Waterfall) and flexible (Agile) methodology. It is made an emphasis on using these methodologies on real projects are made. Also, we analyzed the so-called “Project Management Triangle” and its role in project formation using different management methodologies. A visual representation of the software development process using these two methodologies was embedded to better understanding the specifics of each. During the analysis, conclusions were made regarding the relevance of methodologies in a modern, dynamic environment. Detailed description and analyze of Manifesto of Flexible Software Development, which changed people's perception of the process of developing and creating new projects not only in the field of IT but also in all other spheres of life, were conducted. As a result, were made conclusions about the inability of traditional methodologies (including the Waterfall model) to meet modern market requirements and was preferred Agile methodology, which enables customer requirements to be met in a dynamic environment, ready to changes and promote them.
APA, Harvard, Vancouver, ISO, and other styles
10

Onokoy, L. S. "Flexible approaches to the development of software: evolution and prospects of development." Quality. Innovation. Education, no. 1 (2021): 57–67. http://dx.doi.org/10.31145/1999-513x-2021-1-56-66.

Full text
Abstract:
The article is devoted to the study of fiexible approaches (Agile) to the design of information systems software. Much attention is paid to the comparative analysis of currently popular fiexible methodologies, including the DevOps (Development and Operation) methodology [4], [5], which covers the entire life cycle of creating a software product. In conclusion, based on the conducted research, the author reveals the global and Russian trends in the development of Agile and formulates their development prospects.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Methodologies of flexible software development"

1

Ke, Yuqing S. M. Massachusetts Institute of Technology. "Assessing various software development methodologies and matching software development methodologies with projects." Thesis, Massachusetts Institute of Technology, 2019. https://hdl.handle.net/1721.1/122438.

Full text
Abstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019<br>Cataloged from PDF version of thesis.<br>Includes bibliographical references (pages 157-158).<br>As the software industry evolves, various software development methodologies have become widely used in the industry. Most commonly used methodologies are Waterfall and Agile, along with less known alternatives, such as spiral and hybrid methodologies. When deciding on the methodologies, program managers tend to choose one based on the team preference or historical pattern. However, each software project is unique in its own way and has characteristics that are distinct from the previous projects the team has worked on. For each project, it is crucial to adopt a suitable methodology that help teams to produce the software that meets customer needs within schedule and budget constraints. Therefore, a practical question for every program manager is "How to find a suitable methodology for a specific project?" This thesis is aimed to help program managers answer this question.<br>We first explore how to evaluate each software development methodology based on the two-level decomposition of software development methodology, then analyze the project characteristics based on the situational inputs in three categories: scope, schedule and budget. Thereafter, the thesis proposes a framework to match software development methodology with a specific project. This thesis extends West's work in [1] by introducing a systems approach to assess a software project and a framework to determine the degree of compatibility between a methodology and a software project. The benefits of leveraging the systems approach are: ** The decomposition of methodologies highlights which elements in a methodology play key roles of providing the advantageous ilities over other methodologies. ** The decomposition of a project enables a program manager to evaluate the input elements of a project and gain a systems view on the project characteristics.<br>The framework allows program managers to compare several candidate methodologies and choose the most compatible one using the mismatch scores, weighted summations that indicate the incompatibilities between the candidate methodologies and the project based on the ilities ranking decided by the program managers. To demonstrate how to use this framework for a real world project, an example project is given. The detailed steps of calculating the mismatch scores between three methodologies and the project are shown. The proposed framework can be used as a guideline for program managers to find methodologies for different projects with the information gathered from project stakeholders. This framework has some limitations. A major one is that, since the framework is quantitative based, induvial experience is used to evaluate the elements of methodologies and factors of projects.<br>Further work can be done to improve the objectivity of the evaluation through the surveys of industrial experts and members of teams adopting this framework.<br>by Yuqing Ke.<br>S.M. in Engineering and Management<br>S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program
APA, Harvard, Vancouver, ISO, and other styles
2

Moratilla, Temprado Enrique, and Bendito Enrique Ruz. "Lean Software Development and Agile Methodologies for a small Software development organization." Thesis, Högskolan i Borås, Institutionen Ingenjörshögskolan, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-20077.

Full text
Abstract:
Lean Software Development is a new approach to provide a quality philosophy in software development companies. Lean offers a set of principles that helps companies to identify inefficient processes and waste. Therefore, by applying these principles, we can reduce costs, by shorting development time, incrementing productivity.In this study a software company with seven employees is analyzed. The company develops software and wants to increase its maturity and the quality of its processes. Currently, it has few documented processes. Furthermore, the company want a common way of working for every project. The challenge relies in adapting the set of principles provided by Lean to this particular case of study.We seek to analyze the current situation of the company to find out about the problems and limitations of the current way of working. After that we will state recommendations about the use of Lean combined with Agile practices such as Scrum and XP.As a result we present a proposal for implementation adapted from these philosophies to the needs and characteristics of the company.We have found that there are several ways in which the company can benefit from the implementation of Lean practices in combination with Scrum and XP. The result is a new framework that can be applied for other small software development companies in a similar situation.
APA, Harvard, Vancouver, ISO, and other styles
3

MANNARO, KATIUSCIA. "Adopting agile methodologies in distributed software development." Doctoral thesis, Università degli Studi di Cagliari, 2008. http://hdl.handle.net/11584/265978.

Full text
Abstract:
From the second half of the '90s, some software engineering practitioners introduced a new group of software development methodologies called Agile Methodologies (Ams): they have been developed to overcome the limits of the traditional approaches in the software development. FLOSS (Free Libre Open Source Software) has been proposed as possible different solution to the software crisis that is afflicting the ICT worldwide business. If the AMs improve the quality code and allow to respond quickly to requirement changes, FLOSS approach decreases the development costs and increases the spreading of competences about the software products. A debate is shaping about the compatibility of these two approaches. Software development teams have been spreading around the world, with users in Europe, management in the USA and programmers in the USA and India. The scattering of team members and functions around the world introduces barriers to productivity, cultural and languages differences can lead to misunderstanding of requirements, time zone differences can delay project schedules. Agile methods can provide a competitive advantage by delivering early, simplifying communication and allowing the business to respond more quickly to the market by changing the software. Trying to distribute a development project in an agile way isn't easy and will involve compromises. The goal of this thesis is to determine the application of the AMs in several contexts so to define which of these can be used effectively in non traditional software projects as the distributed development.
APA, Harvard, Vancouver, ISO, and other styles
4

Jones, Susan M. "An investigation of methodologies for software development prototyping." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 1993. https://ro.ecu.edu.au/theses/1150.

Full text
Abstract:
The computer industry has a poor record of system development using the traditional life-cycle approach. The main cause of user dissatisfaction is the unacceptably large amount of time between specification and delivery of a system. In addition, users have limited opportunity to influence how the system will look when implemented once development has commenced. With the advent of 4GLs, system development using a prototyping approach has become a viable option. This has reduced the development tlme significantly and, together with the use of prototyping, has allowed users to become more involved in the development process. However, this change in the development process has meant that often the use of an accepted methodology/system life cycle has been ignored or altered. This has resulted in systems where the definition-of-requirements phase was often fast-tracked or omitted totally and the system documentation is insufficient for effective maintenance. Thus, this approach has not proved to be as successful as expected. However, the opportunities that prototyping offers should not be discarded because of the use of inappropriate software development methodologies, languages or tools. This study seeks to identify factors that may influence the success or failure of a prototyping project and to assess the importance of any developmentmethodologies being used. Information was gathered via interviews, questionnaires and, where deemed necessary, the reviewing of development procedures used. Conclusions have been drawn from data gathered from various organisations in Western Australia that have used prototyping for a number of projects, thus, suggesting a refinement of the development process. Two main areas appeared to affect the success of a software development project. The first is the lack of flexibility in the methodology used and inappropriateness of the development tools and languages. The second is insufficient requirements analysis. The results indicate that a methodology is required that provides a good framework, but is flexible enough to handle different types and sizes of project. It should specifically address prototyping and include guidelines as to how to select the most suitable prototyping approach for each project. It should contain examples of different deliverables and various development cycles appropriate for each type of prototyping. There should be automated tools available to handle documentation and code generation where possible. The development of a methodology with the above characteristics is required if the advantages of prototyping are to be maximised in the future.
APA, Harvard, Vancouver, ISO, and other styles
5

Nesbitt, Brian E. "Integration and deployment techniques in combination with development methodologies." [Denver, Colo.] : Regis University, 2009. http://adr.coalliance.org/codr/fez/view/codr:141.

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

Martin, Timothy Patrick. "Flexible manufacturing system software development using simulation." Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/101236.

Full text
Abstract:
This paper presents a hierarchical modeling method that can be used to simulate a Flexible Manufacturing System (FMS) at all levels of detail. The method was developed specifically to aid the software development needed for the hierarchy of computers that are present in an FMS. The method was developed by modeling an existing FMS. The models developed of the existing FMS are described in detail to provide an example of how to model other FMSs. The basic building blocks needed for designing other FMSs with this modeling method are provided. The models were written in the SIMAN simulation language. SIMAN was found to be an easy language to use for the hierarchical modeling of FMSs.<br>M.S.
APA, Harvard, Vancouver, ISO, and other styles
7

Crunk, John. "Examining Tuckman's Team Theory in Non-collocated Software Development Teams Utilizing Collocated Software Development Methodologies." Thesis, Capella University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10929105.

Full text
Abstract:
<p> The purpose of this qualitative, multi-case study was to explain Tuckman&rsquo;s attributes within software development when using a collocated software designed methodology in a non-collocated setting. Agile is a software development methodology that is intended for use in a collocated setting; however, organizations are using it in a non-collocated setting, which is increasing the software errors in the final software product. The New Agile Process for Distributed Projects (NAPDiP) was developed to fix these software errors that arise when using Agile in a non-collocated setting but have not been effective. This research utilized Tuckman's team theory to explore the disparity related to why these errors still occur. The research question asked is how software development programmers explain Tuckman's attributes (i.e., forming, storming, norming, performing) on software development projects. The study adopted a qualitative model using nomothetic major and minor themes in the exploration of shared expressions of sentiments from participants. The study&rsquo;s population came from seven participants located in the United States and India who met the requirement of using the Agile development methodology and work for organizations on teams with a size of at least thirty individuals from various organizations. A total of seven participants reached saturation in this multi-case study supporting the research question explored. The findings of the research demonstrated that development teams do not meet all stages and attributes of Tuckman&rsquo;s team development. Future research should explore additional ways that software development teams satisfy a more significant number of Tuckman&rsquo;s team development stages.</p><p>
APA, Harvard, Vancouver, ISO, and other styles
8

Aslan, Serdar. "Digital Educational Games: Methodologies for Development and Software Quality." Diss., Virginia Tech, 2016. http://hdl.handle.net/10919/73368.

Full text
Abstract:
Development of a game in the form of software for game-based learning poses significant technical challenges for educators, researchers, game designers, and software engineers. The game development consists of a set of complex processes requiring multi-faceted knowledge in multiple disciplines such as digital graphic design, education, gaming, instructional design, modeling and simulation, psychology, software engineering, visual arts, and the learning subject area. Planning and managing such a complex multidisciplinary development project require unifying methodologies for development and software quality evaluation and should not be performed in an ad hoc manner. This dissertation presents such methodologies named: GAMED (diGital educAtional gaMe dEvelopment methoDology) and IDEALLY (dIgital eDucational gamE softwAre quaLity evaLuation methodologY). GAMED consists of a body of methods, rules, and postulates and is embedded within a digital educational game life cycle. The life cycle describes a framework for organization of the phases, processes, work products, quality assurance activities, and project management activities required to develop, use, maintain, and evolve a digital educational game from birth to retirement. GAMED provides a modular structured approach for overcoming the development complexity and guides the developers throughout the entire life cycle. IDEALLY provides a hierarchy of 111 indicators consisting of 21 branch and 90 leaf indicators in the form of an acyclic graph for the measurement and evaluation of digital educational game software quality. We developed the GAMED and IDEALLY methodologies based on the experiences and knowledge we have gained in creating and publishing four digital educational games that run on the iOS (iPad, iPhone, and iPod touch) mobile devices: CandyFactory, CandySpan, CandyDepot, and CandyBot. The two methodologies provide a quality-centered structured approach for development of digital educational games and are essential for accomplishing demanding goals of game-based learning. Moreover, classifications provided in the literature are inadequate for the game designers, engineers and practitioners. To that end, we present a taxonomy of games that focuses on the characterization of games.<br>Ph. D.
APA, Harvard, Vancouver, ISO, and other styles
9

Tegegne, E. (Esubalew). "Software development methodologies and practices in startups:systematic literature review." Master's thesis, University of Oulu, 2018. http://urn.fi/URN:NBN:fi:oulu-201804041421.

Full text
Abstract:
Startups are newly created companies with little or no operating history and with limited resources and markets. Software startup are aiming to develop cutting edge software products under highly uncertain conditions, overcoming fast-growing markets under multiple influences. The significance of startups for economic development is growing in software business due to their ability to quickly create innovative technologies and their potential to scale to a wide market. The objective of this thesis is to identify and analyze existing scientific literature regarding software development methodologies and practices used in startup companies published between Jan 2006 and Dec 2016. A systematic literature review was conducted to explore the previous research on software development methods and practices in startups. A review protocol was developed and used as a procedure to conduct the review. The data was collected from three databases i.e. IEEE Xplore, Scopus, ISI Web of Science. This research identified 30 relevant primary studies out of a total 1249 papers to answer defined research questions. The result show that agile and Lean Startup methodologies are the most used methodologies across startup companies. Due to the flexible nature of startups, tailoring specific methodology is a common practice among startup companies. Additionally, a total of 95 software development work practices are extracted from primary studies. This thesis concludes that software development methodologies in startups are informal, customized, and highly dependent on the experience of project managers. It is also noted that principles related to these development methodologies are not strictly followed due to limited resources and uncertainty in the market. Furthermore, the results shows that software startups choose development methodologies and practices which are flexible, light-weight and allow rapid changes.
APA, Harvard, Vancouver, ISO, and other styles
10

Igou, Amy. "Evolving Software Development Methodologies: The Search for Accounting Clarity." OpenSIUC, 2014. https://opensiuc.lib.siu.edu/dissertations/953.

Full text
Abstract:
For many years, most IT departments used the same software development methodology called waterfall. This methodology outlines distinct phases for project completion; each phase needing to be completed prior to the start of the next. The primary accounting standard for allocating costs for software development is written in the language of waterfall. Costs are either capitalized or expensed depending on the type of activity that was performed. IT departments have been moving toward a new group of software development methodologies called agile. These methodologies do not follow the phases of waterfall. This makes the current accounting standard for software development difficult to interpret and determine the appropriate transaction. This further hinders IT organizations attempts to better quantify business value of software projects. To examine this issue, a new construct called accounting clarity is introduced in this research. Accounting clarity is an agreement between IT and accounting regarding the treatment of software development costs. This study shows that it is essential for both IT and accounting to work together to determine a solution. The accounting clarity construct is developed from the “ilities” of software quality models and the Capability Maturity Model (CMM) Level 3 key process area (KPA) of intergroup coordination. Intergroup coordination provides the concepts for accounting clarity as the two groups must coordinate to determine the appropriate accounting treatment. The “ilities” are characteristics that should be followed and measured throughout a software development project to ensure long term maintainability of software. This study proposes that accounting clarity should be one of the "ilities" in the software quality model. A portion of the study of accounting clarity examines the relationship between accounting clarity and project control, proposing a positive relationship between the two variables. Then the study examines factors that help to increase accounting clarity. These factors were derived from teamwork and coordination literature. To test the hypothesized relationships, a survey methodology was used. Individuals working on agile software development projects were participants in the survey. This study contributes to both the IT and accounting literature. The research provides a framework to examine other contexts in which the current accounting standards are unclear. As changes happen more frequently in business, this is more likely to occur on a frequent basis. The study has practical implication for software development as it highlights the importance of understanding the accounting implications prior to the project and continuously throughout the lifespan of the software. Adding accounting clarity to the “ilities” of software quality helps software development teams include this in project plans with any software development methodology.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Methodologies of flexible software development"

1

Association, Information Resources Management. Software design and development: Concepts, methodologies, tools, and applications. Information Science Reference, an imprint of IGI Global, 2014.

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

Christensen, Henrik B. Flexible, reliable software: Using patterns and agile development. Chapman & Hall/CRC, 2010.

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

1946-, Brandon Dan, ed. Software engineering for modern Web applications: Methodologies and technologies. Information Science Reference, 2008.

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

1946-, Brandon Dan, ed. Software engineering for modern Web applications: Methodologies and technologies. Information Science Reference, 2008.

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

FitzSimons, Deirdre. Developing software in Ireland: Methodologies, tools and project management practices. University College Dublin, 1996.

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

Alor-Hernandez, Giner. Frameworks, methodologies, and tools for developing rich Internet applications. Information Science Reference, an imprint of IGI Global, 2015.

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

Purba, Sanjiv. How to manage a successful software project: Methodologies, techniques, tools. J. Wiley, 1995.

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

International Conference on New Trends in Software Methodologies, Tools and Techniques (6th 2007 Rome, Italy). New trends in software methodologies, tools and techniques. IOS Press, 2007.

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

International Conference on New Trends in Software Methodologies, Tools and Techniques (7th 2008 Sharjah, United Arab Emirates). New trends in software methodologies, tools and techniques. IOS Press, 2008.

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

International Conference on New Trends in Software Methodologies, Tools and Techniques (7th 2008 Sharjah, United Arab Emirates). New trends in software methodologies, tools and techniques. IOS Press, 2008.

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

Book chapters on the topic "Methodologies of flexible software development"

1

Dillon, Clare. "Bridging Silos: Amplifying InnerSource Adoption Using an Activity Theory Perspective." In Lecture Notes in Business Information Processing. Springer Nature Switzerland, 2025. https://doi.org/10.1007/978-3-031-72781-8_20.

Full text
Abstract:
AbstractMy research explores the adoption of InnerSource, a practice that integrates open source methodologies within organizations to foster collaboration and overcome the traditional silo mentality. InnerSource and Agile implementations share many values such as transparency, employee empowerment, and a flexible response to change. InnerSource adoption can come before, after, or in parallel with Agile transformations. Despite the increasing recognition of InnerSource as a pivotal driver for developer productivity and its growing presence in industry discussions, academic research on the subject remains in its infancy. Leveraging my involvement with the InnerSource Commons community and drawing from Activity Theory, my research aims to fill critical gaps in our understanding of InnerSource adoption. Specifically, it investigates the activities organizations engage in to enable InnerSource, identifies blockers hindering its implementation, and proposes effective strategies to counteract these challenges. At the XP 2024 PhD Symposium, I intend to share some preliminary findings of my research, derived from a Systematic Literature Review and a pilot study with an InnerSource practitioner working group. My research not only seeks to advance theoretical knowledge in the field but also offers practical insights for organizations striving to change software development practices, contributing to a more collaborative and efficient software development environment.
APA, Harvard, Vancouver, ISO, and other styles
2

Pranam, Aswin. "Software Development Methodologies." In Product Management Essentials. Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3303-0_9.

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

Crookshanks, Edward. "Development Methodologies and SDLC." In Practical Software Development Techniques. Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0728-4_6.

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

Crookshanks, Edward. "Development Methodologies and SDLC." In Practical Enterprise Software Development Techniques. Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-0620-1_4.

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

Lee, Sang Joon, Minkyung Oh, and Shein-Chung Chow. "Equivalence Test with Flexible Margin." In Methodologies in Biosimilar Product Development. Chapman and Hall/CRC, 2021. http://dx.doi.org/10.1201/9781003205807-6.

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

Filipova, Olga, and Rui Vilão. "Roles, Responsibilities, and Methodologies." In Software Development From A to Z. Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-3945-2_2.

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

Nerur, Sridhar, Alan Cannon, VenuGopal Balijepally, and Philip Bond. "Towards an Understanding of the Conceptual Underpinnings of Agile Development Methodologies." In Agile Software Development. Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12575-1_2.

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

Maurer, Frank, and Theodore D. Hellmann. "People-Centered Software Development: An Overview of Agile Methodologies." In Software Engineering. Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-36054-1_7.

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

Hung, Phan Duy, Le Hoang Nam, and Hoang Van Thang. "Flexible Development for Embedded System Software." In Intelligent Computing in Engineering. Springer Singapore, 2020. http://dx.doi.org/10.1007/978-981-15-2780-7_93.

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

Harris, Michael D. S. "Appendix: Waterfall and Agile Software Development Methodologies." In The Business Value of Software. Auerbach Publications, 2017. http://dx.doi.org/10.1201/9781315155456-13.

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

Conference papers on the topic "Methodologies of flexible software development"

1

Antsifrov, Nikita S., Nekoula Haddad, and Konstantin S. Myshenkov. "Evolution of the Software Development Methodologies." In 2025 7th International Youth Conference on Radio Electronics, Electrical and Power Engineering (REEPE). IEEE, 2025. https://doi.org/10.1109/reepe63962.2025.10970991.

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

Sugiarti, Yuni, Sumanto, Normaliza Firdia, et al. "Tracing the Development Methodologies of Software Engineering: A Systematic Literature Review." In 2024 12th International Conference on Cyber and IT Service Management (CITSM). IEEE, 2024. https://doi.org/10.1109/citsm64103.2024.10775806.

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

Fawareh, Hamed, Yazan Al-Smadi, Rania Saadeh, Faid AlNoor Fawareh, Ali Elrashidi, and Hazim M. Al-Shdaifat. "A Comparative Study between Agile and Waterfall Methodologies during Software Development Process." In 2024 25th International Arab Conference on Information Technology (ACIT). IEEE, 2024. https://doi.org/10.1109/acit62805.2024.10877239.

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

Mendoza, Aldren John M., Norman Alexiz D. Nacilla, Charles Sherwin B. San Gabriel, et al. "iTaskDev: A Software as a Service with Adaptive Algorithm for Optimized Software Development Planning Across Methodologies." In 2024 International Conference on Intelligent Cybernetics Technology & Applications (ICICyTA). IEEE, 2024. https://doi.org/10.1109/icicyta64807.2024.10913136.

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

Patchkaew, Punyakon, Haris Kirdpakdee, Chanut Kidwat, and Anon Sukstrienwong. "Adaptive CI/CD: A Flexible Architecture for Software Development." In 2024 8th International Conference on Information Technology (InCIT). IEEE, 2024. https://doi.org/10.1109/incit63192.2024.10810646.

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

Rahman, Md Shahinur, and Emon Ahmed. "Integrating PRINCE2 and Agile Methodologies in Software Development: Unveiling Opportunities and Addressing Challenges." In 2024 International Conference on Electrical, Communication and Computer Engineering (ICECCE). IEEE, 2024. https://doi.org/10.1109/icecce63537.2024.10823492.

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

Pereira e Silva, Ricardo, and Roberto Tom Price. "Suporte ao Desenvolvimento e Uso de Componentes Flexíveis." In Simpósio Brasileiro de Engenharia de Software. Sociedade Brasileira de Computação, 1999. http://dx.doi.org/10.5753/sbes.1999.23911.

Full text
Abstract:
Component-oriented development is being stimulated by the availability of devices allowing component interoperability, regardless of programming language, running platform and executing location. However, there are some unsolved problems concerning search and selection, functionality understanding and adaptation of components. Flexibility is an important feature for increasing component reusability. Some approaches like wrappers, help in adapting actual components to systems not fully compatible. In this paper we propose to develop components as object-oriented frameworks. This leads to flexible components, much more suitable to reuse. On the other hand, this approach makes more complex the development and the use of components. SEA is an environment supporting development and use of reusable software artifacts. It employs a describing approach like those used in OOAD methodologies. The environment supports development, semantic checking and semi-automatic translation of design specifications. In this paper we describe how SEA supports the development and the use of flexible components.
APA, Harvard, Vancouver, ISO, and other styles
8

J Kampa, Anthony, and Christine Bakke. "Integrating Agile Software Development Practice in a Classroom Setting." In InSITE 2023: Informing Science + IT Education Conferences. Informing Science Institute, 2023. http://dx.doi.org/10.28945/5159.

Full text
Abstract:
Aim/Purpose . This paper explores how best to implement Agile style courses into university curriculum. It is a starting point for teachers who are unsure how to structure their classes in an Agile way. Background. This paper explores the researcher’s experiences with Agile in the classroom, outside the classroom and in a professional setting. Recommendations are made on how to best introduce students to Agile concepts and prepare them for their careers. Methodology. This paper is an exploratory case study in determining whether or not students are properly equipped for their careers. Information was gathered through a qualitative interview administered virtually. The sample is taken from students who are recent graduates from public universities in the Midwest. Contribution. This study provides tangible and practical suggestions to best utilize Agile methodologies in an academic setting. Findings. A project-based learning class taught using the agile methodology would provide a beneficial and flexible class for students no matter where their careers take them. This style of class can be offered to any level of undergraduate student but more advanced students will likely get more out of it. Advanced students should be encouraged to work across disciplines to foster communication skills and provide valuable experience working with non-developers. Recommendations for Practitioners. Agile is not a silver bullet. Not all classes will be a good fit for this style of teaching. Practitioners should consider a blend of classes with different teaching styles. Recommendations for Researchers. Researchers are encouraged to explore different methodologies for including Agile development into a classroom environment. Impact on Society. This study will help to better prepare the next generation of software developers for eventual careers. Future Research. Practitioners and researchers can expand on this study by exploring a multi-year study following students who had Agile curriculum and students who received traditional class methods as they graduate and join the workforce. Researchers can explore other methods of implementing Agile in the classroom to further refine suggestions provided in this paper.
APA, Harvard, Vancouver, ISO, and other styles
9

Pinheiro, Eduardo, and Paulo Meirelles. "Understanding Group Maintainership Model in the Linux Kernel Development." In Workshop de Visualização, Evolução e Manutenção de Software. Sociedade Brasileira de Computação - SBC, 2024. http://dx.doi.org/10.5753/vem.2024.3912.

Full text
Abstract:
Software development has evolved over decades, transitioning from traditional models such as the waterfall approach and the unified process to more flexible methodologies like agile methods and collaborative development strategies of Free/Libre/Open Source Software (FLOSS) projects. Alongside this trend, the global distribution of software development work has increased. This phenomenon is particularly evident in the development of FLOSS projects, where contributors from various regions worldwide collaborate asynchronously on projects. In this context, the organization of interactions among developers can significantly influence a project success or failure. An example is the Linux kernel community, which has been actively discussing the models and workload of project maintainers – a topic that has received limited attention in scientific literature. This study investigated the new maintenance methods used in the Linux kernel project. With over 30 years of development, the Linux kernel has become a benchmark for FLOSS development. We discuss how the maintainers’ workload is addressed in academic literature and by practitioners in the Linux kernel community. To achieve this, we conducted a multivocal literature review to examine the evolution of maintenance models over the years.
APA, Harvard, Vancouver, ISO, and other styles
10

Choudhary, Mukund Kumar. "Analysis on Test Case Assortment and Priortization Strategy." In 11th SAEINDIA International Mobility Conference (SIIMC 2024). SAE International, 2024. https://doi.org/10.4271/2024-28-0177.

Full text
Abstract:
&lt;div class="section abstract"&gt;&lt;div class="htmlview paragraph"&gt;Agile software development aims to create high-quality products while minimizing waste, reducing project costs. Nevertheless, costs are not decreasing despite shorter project cycles and more compact, flexible teams. One area where consideration is being given to reevaluating the stages in software product development is RT. Regression testing is a form of testing done to assure that changes done in Model do not adversely affect the software's functionality. As software develops, test suites typically expand and may become too expensive to run through in their entirety The initial application might have good set of test cases, and running the entire test suite could make testing more expensive. Three ways for reducing the cost of RT include test instance prioritization, test suite minimizing, and regression test selection. In order to verify that software satisfies customer requirements, identify faults or bugs in the code, and determine how to fix these issues to make the software more beneficial, regression testing is essential to software development. In addition to being prepared for testing, test cases and test suites should be completed as quickly as possible when using Test Case Assortment and Prioritization (TCAAP) techniques. TCAAP's primary goal is to test software as quickly and expertly as possible. This paper presents an empirical investigation of TCAAP methodologies in software real-time analysis. This research focuses on studies that are beginning and intermediate.&lt;/div&gt;&lt;/div&gt;
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Methodologies of flexible software development"

1

Suryanarayana Ravi, Megha. Comparative analysis of Scrum and Kanban methodologies in agile software development. Iowa State University, 2023. http://dx.doi.org/10.31274/cc-20240624-389.

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

Dunleavy, G. J. System Considerations and Methodologies in Support of Software Development and Maintenance in the Information System Resource. Defense Technical Information Center, 1988. http://dx.doi.org/10.21236/ada218300.

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

Li, Baisong, and Bo Xu. PR-469-19604-Z01 Auto Diagnostic Method Development for Ultrasonic Flow Meter. Pipeline Research Council International, Inc. (PRCI), 2022. http://dx.doi.org/10.55274/r0012204.

Full text
Abstract:
The objectives of this research are to develop methods for performing ultrasonic flow meter (USM) diagnostic evaluation automatically and a software tool with all necessary attachments. USM-based diagnostics have been established and thirteen categories of knowledge rules of existing cases have been learned and integrated. A search engine for relevant standards, specifications, and other documents of the measurement system has been developed, which enables the free search of text content. Further, with the assistance of modern reasoning techniques, the authorized user only needs to configure an EXCEL file or scripts to activate the rules of the knowledge base by using Drools technology. Therefore, the integration of any potential knowledge rules is convenient and requires no professional skills or changing of the internal source code of the software. Secondly, a new flow meter diagnostic method is proposed based on multiple information methodologies and it is based on the real-time measurement data, operation data, and video data if applicable. The method is intended to identify abnormal states of the measurement system on a real-time basis with the assistance of the knowledge rules and to provide a strategy for mitigating the meter error of components within the measurement system. Thirdly, the applications of Gaussian quadrature diagnostics in daily acquisition nomination change situations and compressor-induced pulsating flow scenarios have been investigated and results are shown in the document. Based on the results, it can be concluded that the measurement uncertainty caused by compressor-induced pulsating flows is obvious, while the measurement uncertainty caused by daily acquisition nomination change is relatively smaller. The software is then developed based on the knowledge, the idea of multiple information methods, and applications of the Gaussian quadrature diagnostics method with all necessary attachments. The architecture, the algorithm, and a few examples are introduced.
APA, Harvard, Vancouver, ISO, and other styles
4

Wayant, Nicole. Adapting agile philosophies and tools for a research environment. Engineer Research and Development Center (U.S.), 2022. http://dx.doi.org/10.21079/11681/45442.

Full text
Abstract:
There exist myriad project management methodologies, but none is focused solely on scientific research. Research projects are unique compared to other types of projects, including software development, manufacturing, and drug trials; research projects inherently have unplanned risks. These risks provide a challenge to managing resources, developing schedules, and providing team ownership while still achieving project goals. To help mitigate the risks and the challenges associated with scientific research, a methodology to manage research projects needs to be developed.
APA, Harvard, Vancouver, ISO, and other styles
5

Kirk. L51768 Pipeline Free Span Design-Volume 1 Design Guideline. Pipeline Research Council International, Inc. (PRCI), 1997. http://dx.doi.org/10.55274/r0011298.

Full text
Abstract:
Vol. 1, Design Guideline The first phase of the project was dedicated to the testing and calibration of a numerical model. The model is capable of predicting the dynamic cross-flow response of a pipeline span caused by vortex shedding. The numerical model was originally developed by Exxon Production Research Co. (EPRCo), Lambrakos (1991) and has been made available to the project. This project results in minimization of intervention work in relation to submarine pipeline design without jeopardizing pipeline safety. The main objective of the Guideline is to present procedures and methodologies for evaluating free spans in submarine pipeline systems. The Guideline addresses specifically vortex-induced vibrations caused by wave and current action. A force model describing the cyclic lift force generated by vortex shedding has been tested and calibrated as part of the Guideline preparation work. This model is adequate to use for calculating the hydrodynamic response of a free spanning pipeline. Vol. 2, Software and User Guide The second phase of the project concentrated on the development of the Guideline document itself and the associated software and how to operate the software, FREESPAN, used for assessing free spanning submarine pipelines. �
APA, Harvard, Vancouver, ISO, and other styles
6

Spencer. PR-185-084501-R01 Technologies and Methodology for Automated Ultrasonic Testing Systems Quantification. Pipeline Research Council International, Inc. (PRCI), 2011. http://dx.doi.org/10.55274/r0010725.

Full text
Abstract:
For automated ultrasonic testing (AUT) detection and sizing accuracy, this program developed a methodology for quantification of AUT systems, advancing and quantifying AUT systems image-capture capabilities, quantifying the performance of multiple AUT systems, establishing a guidance document, conducting field tests, and delivering a guidance document for future inclusion in reliability-based design and assessment (RBDA) standards. Improvements for AUT of pipeline girth welds were identified by investigating: imaging techniques for AUT data, modeling and simulation tools for AUT technique development and validation, and quantification methodologies for measuring the performance of AUT systems. Throughout the course of the project, many AUT scans were conducted using both zonal and non-zonal inspection techniques. The quantification methodology provides guidance for quantifying the performance of AUT systems with respect to probability of detection (POD) and accuracy of flaw sizing. Field trials and lab trials demonstrated that a sector sweep of beam angles provides alternative imaging capabilities that may enhance current zonal techniques. Current methodologies used for quantifying detection and sizing limits for AUT systems vary and produce great variability in detection and sizing results. Consequently, a standardized quantification approach is recommended to reduce this variability. This investigation evaluated six AUT systems; flaw heights were detected between 2 and 4 mm with a 90% probability and a confidence level of 95% (a90/95). The use of ultrasonic modeling and inspection simulation software provided a good tool for developing and evaluating AUT procedures; and can be used to evaluate changes in essential variables.
APA, Harvard, Vancouver, ISO, and other styles
7

Francis, Andrew, Chas Jandu, and Mike Taylor. PR-408-124500-R01 Mechanical Damage Instantaneous Failure Model Numerical Simulation of Physical Tests. Pipeline Research Council International, Inc. (PRCI), 2013. http://dx.doi.org/10.55274/r0010819.

Full text
Abstract:
The overall objective was to develop two models for determining the effect of mechanical damage on the structural integrity of buried pipelines. The models that are to be developed are the instantaneous failure model (MD4-3) and the delayed failure model (MD4-4). The subject of this report is part of the work that has been undertaken in support of the development of the instantaneous failure model which is being undertaken within the remit of MD4-3. The overall objective of MD4-3 to produce a closed form expression that will be used as: (i) A Limit State Function in structural reliability and risk assessment methodologies and associated software. (ii) A means of determining the safety margin associated with known existing damage to establish whether immediate repair is required (iii) An initial condition for the delayed failure model (MD4-4) which is being developed separately. The objective of this report is to present the outcomes of detailed numerical simulation of physical tests that have been performed as part of MD4-1. The development is progressing based on a combination of physical testing and numerical simulation and analysis. The objective of this report is to present the outcomes of detailed numerical simulation of physical tests that have been performed as part of MD4-1.
APA, Harvard, Vancouver, ISO, and other styles
8

Tayeb, Shahab. Intelligent Blind Crossings for Suburban and Rural Intersections. Mineta Transportation Institute, 2025. https://doi.org/10.31979/mti.2024.2351.

Full text
Abstract:
Blind intersections in suburban and rural areas pose significant safety challenges due to limited visibility and inadequate infrastructure. This project proposes an innovative solution leveraging the Internet of Vehicles (IoV) paradigm, utilizing connected and autonomous vehicles (CAVs) for seamless communication to enhance safety at these intersections. The research focuses on developing a specialized Road-Side Unit (RSU) system equipped with a Virtual Traffic Light Algorithm implemented on a Field-Programmable Gate Array (FPGA). Key stakeholders, including transportation authorities, vehicle manufacturers, and local communities, stand to benefit from this initiative. The RSU system acts as a critical infrastructure component, facilitating efficient intersection management and mitigating visibility challenges. Methodologies involve adapting the Virtual Traffic Light Algorithm, integrating it into the FPGA-based RSU system, and demonstrating RSU communication operability through software-defined radios. Additionally, a novel solar-powered system is designed for lightweight RSUs to enhance sustainability and energy efficiency. The project's findings indicate the feasibility and practicality of the proposed RSU solution in enhancing safety at blind intersections. Successful implementation of the Virtual Traffic Light Algorithm on the FPGA demonstrates its potential for real-world deployment. The operability demonstration of RSU communication validates the effectiveness of the proposed communication system. Overall, this research contributes to advancing safety measures in transportation infrastructure, with potential implications for future urban planning and policy development.
APA, Harvard, Vancouver, ISO, and other styles
9

Popel, Maiia V., and Mariya P. Shyshkina. The Cloud Technologies and Augmented Reality: the Prospects of Use. [б. в.], 2018. http://dx.doi.org/10.31812/123456789/2662.

Full text
Abstract:
The article discusses the prospects of the augmented reality using as a component of a cloud-based environment. The research goals are the next: to explore the possibility of the augmented reality using with the involvement of the cloud-based environment components. The research objectives are the next: to consider the notion of augmented reality; to analyze the experience the augmented reality using within the cloud environment / system; to outline the prospects of the augmented reality using in educational institutions; to consider the technical conditions of the augmented reality use. The object of research is: the educational process in educational institutions of Ukraine of different levels of accreditation. The subject of research is: the educational process in a cloud-based environment in educational institutions of Ukraine. The research methods used are the next: analysis of scientific publications, observations. The results of the research are the next: on the basis of the analysis of scientific works, it has been established that the experience of the augmented reality using in the systems based on cloud technologies already exists. However, the success of such a combination has not yet been proven. Currently, laboratory tests are known, while the experiment was not carried out under natural conditions in control and experimental groups. It is revealed that the attraction of the augmented reality for the educators requires the development of new methodologies, didactic materials, updating and updating of the curriculum. The main conclusions and recommendations: the main principles of augmented reality use in the learning process are: designing of the environment that is flexible enough, attention should be paid to the teaching and didactic issues; adjusting the educational content for mastering the material provided by the curriculum; the research methods that can be used in training along with the elements of augmented reality are to be elaborated; development of adaptive materials; training of teachers, which will include augmented reality in educational practice.
APA, Harvard, Vancouver, ISO, and other styles
10

Raja, Rameez Ali, Vidushi Toshniwal, and Rodrigo Salgado. GIS-Based Geotechnical Database for Collaborative GIS. Purdue University, 2023. http://dx.doi.org/10.5703/1288284317637.

Full text
Abstract:
INDOT spends at least 8 million dollars annually on geotechnical site investigations, not including the amounts spent by contractors. The laborious and costly job of data collection in geotechnical practice requires the efficient storing and organizing of this valuable data to develop correlations and trends in spatially varying geotechnical data. INDOT currently uses gINT software for managing geotechnical data and ArcGIS for storing boring logs and geotechnical reports. The INDOT geotechnical office is pursuing means to improve the efficiency of their operations by developing a GIS-based geotechnical database for secure storage, easy retrieval, and flexible sharing of geotechnical data to enhance decision making. SPR-4616 is the first step towards the development of a geotechnical data management system in which important decisions on the components and structure of the database were made. The report presents a detailed conceptual layout for the development of a geotechnical database following an object-oriented programming approach. The report discusses in detail the geotechnical applications, the field, laboratory, and verification tests that will be included in the database. The geotechnical variables required to perform the engineering analysis in designing specific applications are logically linked with the geotechnical tests from which they are obtained. Lastly, a detailed layout of the proposed database structure and a user workflow example is provided in the report and can serve as a guide during the development of the database system.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Methodologies of flexible software development' 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