Gotowe bibliografie tematyczne / Software development methodologies

Gotowa bibliografia na temat „Software development methodologies”

Autor: Grafiati

Data publikacji: 4 czerwca 2021

Data aktualizacji: 13 lutego 2022

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych

Wybierz rodzaj źródła:

Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł naukowych na temat „Software development methodologies”.

Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.

Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.

Artykuły w czasopismach na temat "Software development methodologies"

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

Pełny tekst źródła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

Kacmar, Charles J., Denise J. McManus, Evan W. Duggan, Joanne E. Hale i David P. Hale. "Software Development Methodologies in Organizations". Information Resources Management Journal 22, nr 3 (lipiec 2009): 16–39. http://dx.doi.org/10.4018/irmj.2009070102.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Soobia.et.al., Saeed. "Analysis of Software Development Methodologies". International Journal of Computing and Digital Systems 8, nr 5 (9.01.2019): 445–60. http://dx.doi.org/10.12785/ijcds/080502.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Conger, Sue. "Software Development Life Cycles and Methodologies". International Journal of Information Technologies and Systems Approach 4, nr 1 (styczeń 2011): 1–22. http://dx.doi.org/10.4018/jitsa.2011010101.

Pełny tekst źródła

Streszczenie:

Information Systems as a discipline has generated thousands of research papers, yet the practice still suffers from poor-quality applications. This paper evaluates the current state of application development, finding practice wanting in a number of areas. Changes recommended to fix historical shortcomings include improved management attention to risk management, testing, and detailed work practices. In addition, for industry’s move to services orientation, recommended changes include development of usable interfaces and a view of applications as embedded in the larger business services in which they function. These business services relate to both services provided to parent-organization customers as well as services provided by the information technology organization to its constituents. Because of this shift toward service orientation, more emphasis on usability, applications, testing, and improvement of underlying process quality are needed. The shift to services can be facilitated by adopting tenets of IT service management and user-centered design and by attending to service delivery during application development.

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Streszczenie:

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

Style APA, Harvard, Vancouver, ISO itp.

Kumar, Rakesh, Priti Maheshwary i Timothy Malche. "Inside Agile Family Software Development Methodologies". International Journal of Computer Sciences and Engineering 7, nr 6 (30.06.2019): 650–60. http://dx.doi.org/10.26438/ijcse/v7i6.650660.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Chandra, Vishal. "Comparison between Various Software Development Methodologies". International Journal of Computer Applications 131, nr 9 (17.12.2015): 7–10. http://dx.doi.org/10.5120/ijca2015907294.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Jovanovic, Aca, Filip Jovanovic, Ljiljana Miletic i Ivana Beric. "Application of agile methodologies in software development". Tehnika 71, nr 6 (2016): 896–900. http://dx.doi.org/10.5937/tehnika1606896j.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Al-Zewairi, Malek, Mariam Biltawi, Wael Etaiwi i Adnan Shaout. "Agile Software Development Methodologies: Survey of Surveys". Journal of Computer and Communications 05, nr 05 (2017): 74–97. http://dx.doi.org/10.4236/jcc.2017.55007.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Zakrzewski, Pawel, Janusz Narkiewicz i Darren Brenchley. "Safety Critical Software Development Methodologies in Avionics". Transactions on Aerospace Research 2020, nr 2 (1.06.2020): 59–71. http://dx.doi.org/10.2478/tar-2020-0011.

Pełny tekst źródła

Streszczenie:

AbstractThis article summarizes avionics safety-critical software development methodologies and implications of the DO-178C standard from an Agile application perspective. We explain the safety-critical software categorization. It also outlines the main differences and advantages of different approaches to the development process, from Waterfall through the V-model to Iterative and Incremental. Agile principles are explained as well as a Scrum – which is a popular framework in the non-safety-critical software industry. The application of Agile, for safety-critical software considerations, is based on the practical knowledge of the authors, and looks at the potential solution from a DO-178C standard, size of the project, scalability, and organizational culture points of view. Definition of the Agile type of framework, consistent with the certification process and existing standards, has been highlighted as a potential game-changer for the avionics industry.

Style APA, Harvard, Vancouver, ISO itp.

Więcej źródeł

Rozprawy doktorskie na temat "Software development methodologies"

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.

Pełny tekst źródła

Streszczenie:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 157-158).
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.
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.
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.
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.
by Yuqing Ke.
S.M. in Engineering and Management
S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program

Style APA, Harvard, Vancouver, ISO itp.

Moratilla, Temprado Enrique, i 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.

Pełny tekst źródła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Streszczenie:

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.
Ph. D.

Style APA, Harvard, Vancouver, ISO itp.

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.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

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.

Pełny tekst źródła

Streszczenie:

The purpose of this qualitative, multi-case study was to explain Tuckman’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’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’s team development. Future research should explore additional ways that software development teams satisfy a more significant number of Tuckman’s team development stages.

Style APA, Harvard, Vancouver, ISO itp.

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.

Pełny tekst źródła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

Dandekar, Ashok V. "A procedural approach to the evaluation of software development methodologies". Thesis, Virginia Polytechnic Institute and State University, 1987. http://hdl.handle.net/10919/94502.

Pełny tekst źródła

Streszczenie:

This thesis presents a procedural approach to evaluating software development methodologies. The evaluation procedure adopts a unique approach based on the fundamental assumption that the requirements govern the process by which software is constructed. To begin with, this research partitions desirable software characteristics into three categories, viz., objectives, principles and attributes. The thesis claims (claims are substantiated with literature references) that there exist definitive relationships (or linkages) among the software objectives, principles and attributes. These linkages form the foundation of the evaluation procedure. The procedure constitutes two processes, top-down process and bottom-up process. These processes are used to assess the software product and the employed software development methodology. The top-down process begins by identifying the objectives and travels down through principles and product attributes; thus, evaluating the adequacy of the methodology. The bottom-up process, on the other hand, starts at the attribute level and goes up through principles and objectives. The bottom-up process highlights the effectiveness of the methodology. Attributes are identified in the product via properties. This research establishes several properties (called factors in the report) for each attribute. A measurement approach is also presented to help assess the extent to which attributes are present. The feasibility and validity of the evaluation procedure are illustrated through the analysis of two real life methodologies.
M.S.

Style APA, Harvard, Vancouver, ISO itp.

Ramnath, Vishal. "The level of adoption and effectiveness of software development methodologies in the software development industry in South Africa". Diss., University of Pretoria, 2010. http://hdl.handle.net/2263/30536.

Pełny tekst źródła

Streszczenie:

The purpose of this study was to describe the software development industry in South Africa by determining the current and future trends in adopting software development methodologies. The main objective was to determine which factors influence the selection of software development methodologies and whether they are effective in delivering projects successfully within the South African context. This study found that the Agile method is the most dominant methodology adopted in the software development industry in South Africa and is also the preferred methodology to be used in the future. It is common practice for companies to adopt more than one software development methodology and the Waterfall method is the next methodology most widely used. There is little adoption of CMMI. All identified factors influence the selection of software development methodologies, however, the distinguishing factors influencing the selection of Agile methods over the Waterfall method in the South African context is team size of between one and five members, project duration of less than three months, iteration length of between two and four weeks and the use of new technology. The most important measurement of project success within the South African context is the delivery of projects on time. The majority of respondents believe that their current dominant methodology is effective in delivering projects successfully. Copyright
Dissertation (MBA)--University of Pretoria, 2011.
Gordon Institute of Business Science (GIBS)
unrestricted

Style APA, Harvard, Vancouver, ISO itp.

Caissy, Gerald Laurent. "Impact of distance/distributed project management on different software development methodologies /". View document on the Internet, 2005. http://library.athabascau.ca/drr/download.php?filename=scis/GeraldCaissy.PDF.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Więcej źródeł

Książki na temat "Software development methodologies"

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

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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. Amsterdam: IOS Press, 2008.

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Khosrow-Pour, Mehdi. Systems and software development, modeling, and analysis: New perspectives and methodologies. Hershey, PA: Information Science Reference, an imprint of IGI Global, 2014.

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Znajdź pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Więcej źródeł

Części książek na temat "Software development methodologies"

Pranam, Aswin. "Software Development Methodologies". W Product Management Essentials, 65–74. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3303-0_9.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Vavpotič, Damjan, Marko Bajec i Marjan Krisper. "Scenarios for Improvement of Software Development Methodologies". W Advances in Information Systems Development, 277–88. Boston, MA: Springer US, 2006. http://dx.doi.org/10.1007/978-0-387-36402-5_24.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Aitchison, Alastair, i Adam Machanic. "Software Development Methodologies for the Database World". W Expert SQL Server 2008 Development, 1–22. Berkeley, CA: Apress, 2009. http://dx.doi.org/10.1007/978-1-4302-7212-0_1.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Harris, Michael D. S. "Appendix: Waterfall and Agile Software Development Methodologies". W The Business Value of Software, 205–11. Boca Raton : Taylor & Francis, a CRC title, part of the Taylor & Francis imprint, a member of the Taylor & Francis Group, the academic division of T&F Informa, plc, [2017]: Auerbach Publications, 2017. http://dx.doi.org/10.1201/9781315155456-13.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Zykov, Sergey V. "Software Methodologies: Are Our Processes Crisis-Agile?" W Crisis Management for Software Development and Knowledge Transfer, 51–68. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-42966-3_3.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Streszczenia konferencji na temat "Software development methodologies"

GRABOW, P., i W. NOBLE. "Reusable software concepts and software development methodologies". W 5th Computers in Aerospace Conference. Reston, Virigina: American Institute of Aeronautics and Astronautics, 1985. http://dx.doi.org/10.2514/6.1985-5070.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Bacher, R. "Software development methodologies for network algorithms". W IEEE Power Engineering Society. 1999 Winter Meeting (Cat. No.99CH36233). IEEE, 1999. http://dx.doi.org/10.1109/pesw.1999.747555.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Moyo, Sibonile, i Ernest Mnkandla. "A Metasynthesis of Solo Software Development Methodologies". W 2019 International Multidisciplinary Information Technology and Engineering Conference (IMITEC). IEEE, 2019. http://dx.doi.org/10.1109/imitec45504.2019.9015867.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Lenarduzzi, Valentina, Maria Ilaria Lunesu, Michele Marchesi i Roberto Tonelli. "Blockchain applications for agile methodologies". W XP '18 Companion: 19th International Conference on Agile Software Development. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3234152.3234155.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Keramati, Hossein, i Seyed-Hassan Mirian-Hosseinabadi. "Integrating software development security activities with agile methodologies". W 2008 IEEE/ACS International Conference on Computer Systems and Applications (AICCSA). IEEE, 2008. http://dx.doi.org/10.1109/aiccsa.2008.4493611.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Potdar, V. "Open source and closed source software development methodologies". W "Collaboration, Conflict and Control: The 4th Workshop on Open Source Software Engineering" W8S Workshop - 26th International Conference on Software Engineering. IEE, 2004. http://dx.doi.org/10.1049/ic:20040275.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Mushashu, Edwin T., i Joel S. Mtebe. "Investigating Software Development Methodologies and Practices in Software Industry in Tanzania". W 2019 IST-Africa Week Conference (IST-Africa). IEEE, 2019. http://dx.doi.org/10.23919/istafrica.2019.8764884.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Yakovyna, Vitaliy, Maksym Seniv i Ivan Symets. "The Relation between Software Development Methodologies and Factors Affecting Software Reliability". W 2020 IEEE 15th International Conference on Computer Sciences and Information Technologies (CSIT). IEEE, 2020. http://dx.doi.org/10.1109/csit49958.2020.9321937.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Klopper, Riaan, Stefan Gruner i Derrick G. Kourie. "Assessment of a framework to compare software development methodologies". W the 2007 annual research conference of the South African institute of computer scientists and information technologists. New York, New York, USA: ACM Press, 2007. http://dx.doi.org/10.1145/1292491.1292498.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Njegus, Angelina, i Goran Milanov. "Qualitative comparison of agile and iterative software development methodologies". W 2011 19th Telecommunications Forum Telfor (TELFOR). IEEE, 2011. http://dx.doi.org/10.1109/telfor.2011.6143783.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Raporty organizacyjne na temat "Software development methodologies"

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

Coulson, Saskia, Melanie Woods, Drew Hemment i Michelle Scott. Report and Assessment of Impact and Policy Outcomes Using Community Level Indicators: H2020 Making Sense Report. University of Dundee, 2017. http://dx.doi.org/10.20933/100001192.

Pełny tekst źródła

Streszczenie:

Making Sense is a European Commission H2020 funded project which aims at supporting participatory sensing initiatives that address environmental challenges in areas such as noise and air pollution. The development of Making Sense was informed by previous research on a crowdfunded open source platform for environmental sensing, SmartCitizen.me, developed at the Fab Lab Barcelona. Insights from this research identified several deterrents for a wider uptake of participatory sensing initiatives due to social and technical matters. For example, the participants struggled with the lack of social interactions, a lack of consensus and shared purpose amongst the group, and a limited understanding of the relevance the data had in their daily lives (Balestrini et al., 2014; Balestrini et al., 2015). As such, Making Sense seeks to explore if open source hardware, open source software and and open design can be used to enhance data literacy and maker practices in participatory sensing. Further to this, Making Sense tests methodologies aimed at empowering individuals and communities through developing a greater understanding of their environments and by supporting a culture of grassroot initiatives for action and change. To do this, Making Sense identified a need to underpin sensing with community building activities and develop strategies to inform and enable those participating in data collection with appropriate tools and skills. As Fetterman, Kaftarian and Wanderman (1996) state, citizens are empowered when they understand evaluation and connect it in a way that it has relevance to their lives. Therefore, this report examines the role that these activities have in participatory sensing. Specifically, we discuss the opportunities and challenges in using the concept of Community Level Indicators (CLIs), which are measurable and objective sources of information gathered to complement sensor data. We describe how CLIs are used to develop a more indepth understanding of the environmental problem at hand, and to record, monitor and evaluate the progress of change during initiatives. We propose that CLIs provide one way to move participatory sensing beyond a primarily technological practice and towards a social and environmental practice. This is achieved through an increased focus in the participants’ interests and concerns, and with an emphasis on collective problem solving and action. We position our claims against the following four challenge areas in participatory sensing: 1) generating and communicating information and understanding (c.f. Loreto, 2017), 2) analysing and finding relevance in data (c.f. Becker et al., 2013), 3) building community around participatory sensing (c.f. Fraser et al., 2005), and 4) achieving or monitoring change and impact (c.f. Cheadle et al., 2000). We discuss how the use of CLIs can tend to these challenges. Furthermore, we report and assess six ways in which CLIs can address these challenges and thereby support participatory sensing initiatives: i. Accountability ii. Community assessment iii. Short-term evaluation iv. Long-term evaluation v. Policy change vi. Capability The report then returns to the challenge areas and reflects on the learnings and recommendations that are gleaned from three Making Sense case studies. Afterwhich, there is an exposition of approaches and tools developed by Making Sense for the purposes of advancing participatory sensing in this way. Lastly, the authors speak to some of the policy outcomes that have been realised as a result of this research.

Style APA, Harvard, Vancouver, ISO itp.

Oferujemy zniżki na wszystkie plany premium dla autorów, których prace zostały uwzględnione w tematycznych zestawieniach literatury. Skontaktuj się z nami, aby uzyskać unikalny kod promocyjny!