Relevant bibliographies by topics / Software development methodology

Contents

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

Academic literature on the topic 'Software development methodology'

Author: Grafiati
Published: 4 June 2021
Last updated: 25 January 2023

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 'Software development methodology.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software development methodology"

1

Gidroets, M. O., and L. I. Grishanova. "SOFTWARE DEVELOPMENT METHODOLOGY." System analysis and logistics 4, no. 26 (December 17, 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

DESPA, Mihai Liviu. "Formalizing the ISDF Software Development Methodology." Informatica Economica 20, no. 2/2015 (June 30, 2015): 66–80. http://dx.doi.org/10.12948/issn14531305/19.2.2015.07.

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

Cort, G., J. A. Goldstone, R. O. Nelson, R. V. Poore, L. Miller, and D. M. Barrus. "A Development Methodology for Scientific Software." IEEE Transactions on Nuclear Science 32, no. 4 (1985): 1439–43. http://dx.doi.org/10.1109/tns.1985.4333629.

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

HUHNS, MICHAEL N. "INTERACTION-ORIENTED SOFTWARE DEVELOPMENT." International Journal of Software Engineering and Knowledge Engineering 11, no. 03 (June 2001): 259–79. http://dx.doi.org/10.1142/s0218194001000530.

Full text
Abstract:
This paper describes a new approach to the production of robust software. We first motivate the approach by explaining why the two major goals of software engineering — correct software and reusable software — are not being addressed by the current state of software practice. We then describe a methodology based on active, cooperative, and persistent software components, i.e., agents, and show how the methodology produces robust and reusable software. We derive requirements for the structure and behavior of the agents, and report on preliminary experiments on applications based on the methodology. We conclude with a roadmap for development of the methodology and ruminations about uses for the new computational paradigm.
APA, Harvard, Vancouver, ISO, and other styles
5

Xu, Peng, and Yurong Yao. "Methodology Fit in Offshoring Software Development Projects." Information Resources Management Journal 27, no. 4 (October 2014): 66–81. http://dx.doi.org/10.4018/irmj.2014100104.

Full text
Abstract:
Offshoring has become a viable alternative for companies to lower software development costs and leverage labor resources worldwide. To achieve success in offshoring software development projects, a vendor must choose appropriate development methodologies. This study aims to examine how methodology fit affects offshoring project performance. It proposes that methodology fit affects project performance through interfirm knowledge sharing between vendors and clients. In addition, the impact of methodology fit on knowledge sharing is dependent on relational capital between vendors and clients. A survey was conducted among software companies in China that provide offshoring services. 108 completed questionnaires were collected. The results confirm this article's hypotheses.
APA, Harvard, Vancouver, ISO, and other styles
6

Xu, Peng, and Yurong Yao. "Methodology Fit in Offshoring Software Development Projects." Information Resources Management Journal 28, no. 3 (July 2015): 42–58. http://dx.doi.org/10.4018/irmj.2015070104.

Full text
Abstract:
Offshoring has become a viable alternative for companies to lower software development costs and leverage labor resources worldwide. To achieve success in offshoring software development projects, a vendor must choose appropriate development methodologies. This study aims to examine how methodology fit affects offshoring project performance. The authors propose that methodology fit affects project performance through interfirm knowledge sharing between vendors and clients. In addition, the impact of methodology fit on knowledge sharing is dependent on relational capital between vendors and clients. A survey was conducted among software companies in China that provide offshoring services. 108 completed questionnaires were collected. The results confirm the authors' hypotheses.
APA, Harvard, Vancouver, ISO, and other styles
7

Hwang, Mansoo, Kwanwoo Lee, and Seonghye Yoon. "Software Development Methodology for SaaS Cloud Service." Journal of the Institute of Webcasting, Internet and Telecommunication 14, no. 1 (February 28, 2014): 61–67. http://dx.doi.org/10.7236/jiibc.2014.14.1.61.

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

Kim, tai-dal. "Software development project management using Agile methodology." Journal of the Institute of Internet Broadcasting and Communication 16, no. 1 (February 29, 2016): 155–62. http://dx.doi.org/10.7236/jiibc.2016.16.1.155.

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

Koizumi, Hisao, Akira Sugimoto, and Tetsyuki Tobiyama. "III. Software Development Methodology and New Technologies." IEEJ Transactions on Electronics, Information and Systems 114, no. 6 (1994): 627–35. http://dx.doi.org/10.1541/ieejeiss1987.114.6_627.

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

Roberts, Keith A. "Generic methodology for open source software development." ACM SIGSOFT Software Engineering Notes 30, no. 2 (March 2005): 1–5. http://dx.doi.org/10.1145/1050849.1050863.

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

Dissertations / Theses on the topic "Software development methodology"

1

Moland, Kathryn J. "An Effective Software Development Methodology for Quality Software Development in a Scheduling Department." NSUWorks, 1997. http://nsuworks.nova.edu/gscis_etd/731.

Full text
Abstract:
The research described in this document represents work performed in the area of software development methodologies as it applied to quality software development in a scheduling department. It addressed traditional methods in software development, current trends in software development, in addition to quality and software development at various companies. The literature suggested a correlation between using a software development methodology and quality software. However, there was limited literature that measured quantitatively the correlation between the effectiveness of the software development methodology and quality software. A software development methodology was developed for the scheduling department of a government contractor company in Aiken, South Carolina based on its needs and emerging technologies. An instrument was utilized to measure the effectiveness of the developed methodology. The methodology was compared with two other methodologies: a standard methodology from the literature and the current method of software development in the scheduling department. A population of computer professionals was divided into three equal groups. Each group was asked to apply the methodology to the case study. Individuals in each group were asked to review the case study and software development methodology. Then using the instrument, the individuals were asked to evaluate the effectiveness of the software development methodology, thereby providing a means for evaluated effectiveness, without conducting years of testing. The responses of the three groups were compared to one another. The results indicated a significantly higher level of approval for those methodologies that guided the development activities, standardized the development process, and identified the development phases and deliverables. It was concluded that utilizing a software development methodology that guides, standardizes, and defines the development phases and deliverables will result in an improved software development process and software quality. Further investigation could validate the findings of this research. The results actually achieved from utilizing the methodology developed for the scheduling department compared with the results achieved from utilizing some other methodology could further validate these research findings. Additional research could examine, over an extended time period, the success of the software development process and software quality of those projects utilizing the methodology described in this dissertation.
APA, Harvard, Vancouver, ISO, and other styles
2

Padilla, Robert F. "Object-oriented methodology for Marine Corps software development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1994. http://handle.dtic.mil/100.2/ADA285720.

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

Acar, Hayri. "Software development methodology in a Green IT environment." Thesis, Lyon, 2017. http://www.theses.fr/2017LYSE1256/document.

Full text
Abstract:
Le nombre de périphériques mobiles (smartphone, tablette, ordinateur portable, etc.) et les internautes augmentent continuellement. En raison de l'accessibilité du cloud computing, de l'Internet et de l'Internet des Objets (IdO), les utilisateurs utilisent de plus en plus d'applications logicielles qui provoquent un effet croissant sur les émissions de gaz à effet de serre. Ainsi, les TIC (Technologies de l'Information et de la Communication) sont responsables d'environ 2% des émissions mondiales de gaz à effet de serre qui sont équivalentes à celles émises par l'industrie aérienne. Selon des rapports récents, le Groupe d'experts Intergouvernemental sur l'Evolution du Climat (GIEC), les émissions de CO2 dus aux TIC augmentent rapidement. Néanmoins, les TIC, en permettant de résoudre des problèmes complexes dans d'autres secteurs, peuvent grandement et facilement participer pour réduire une partie importante des 98% restants des émissions mondiales de CO2. L'utilisation du logiciel implique des opérations matérielles qui sont physiquement responsables de la consommation d'énergie. Par conséquent, le logiciel est indirectement impliqué dans la consommation d'énergie. Ainsi, nous devons réduire la consommation d'énergie du logiciel tout en conservant les mêmes fonctionnalités pour le logiciel afin de créer des logiciels durables et verts. Premièrement, dans ce travail de thèse, nous définissons les termes «durable et vert» dans le domaine du logiciel afin de créer des logiciels respectant les critères de ces termes. Pour créer un produit logiciel, nous devons suivre un processus d'ingénierie logicielle. Par conséquent, nous décrivons des critères durables et verts à respecter après chaque étape de ce processus afin d'établir un processus d'ingénierie logicielle durable et écologique. En particulier, nous nous concentrons sur l'estimation de la consommation d'énergie du logiciel. De nombreux travaux ont essayé de proposer divers outils pour estimer la consommation d'énergie due aux logiciels afin de réduire l'empreinte carbone. Pendant longtemps, les solutions proposées se sont concentrées uniquement sur la conception du matériel, mais ces dernières années, les aspects logiciels sont également devenus importants. Malheureusement, ces études, dans la plupart des cas, ne considèrent que le CPU et négligent tous les autres composants. Les modèles de consommation d'énergie existants doivent être améliorés en tenant compte de plus de composants susceptibles de consommer de l'énergie pendant l'exécution d'une application. L'écriture d'un logiciel durable, performant et vert nécessite de comprendre le comportement de consommation d'énergie d'un programme informatique. L'un des avantages est que les développeurs, en améliorant leurs implémentations du code source, optimiseront la consommation d'énergie du logiciel. De plus, il existe un manque d'outil d'analyse pour surveiller dynamiquement la consommation d'énergie du code source de plusieurs composants. Ainsi, nous proposons GMTEEC (Méthodologie Générique d'Outil pour Estimer la Consommation Energétique) qui se compose de quatre couches aidant et guidant la construction d'un outil permettant d'estimer la consommation énergétique d'un logiciel. Ainsi, dans notre travail, en respectant les couches de GMTEEC, nous créons TEEC (Outil pour Estimer la Consommation Energétique) qui repose sur une formule mathématique établie pour chaque composant (CPU, mémoire, disque dur, réseau) susceptible de consommer de l'énergie afin d'estimer la consommation totale d'énergie du logiciel composée de la somme de chaque consommation d'énergie par composant. De plus, nous ajoutons à TEEC la capacité de localiser dynamiquement les points chauds qui sont les parties du code source consommant la plus grande quantité d'énergie afin d'aider et guider les développeurs à optimiser leur code source et à créer des logiciels efficaces, durables et verts... [etc]
The number of mobile devices (smartphone, tablet, laptop, etc.) and Internet users are continually increasing. Due to the accessibility provided by cloud computing, Internet and Internet of Things (IoT), users use more and more software applications which cause an increasing effect on gas emission. Thus, ICT (Information and Communication Technologies) is responsible of around 2% worldwide greenhouse gas emissions which is equivalent of that emitted by the airline industry. According to recent reports, the Intergovernmental Panel on Climate Change (IPCC), CO2 emissions due to ICT are increasing widely. Nevertheless, ICT, in allowing to solve complex problems in other sectors, can greatly and easily participate to reduce significant portion of the remaining 98% of global CO2 emissions. The use of software implies hardware operations which are physically responsible of energy consumption. Consequently, software is indirectly involved in the energy consumption. Thus, we need to reduce software energy consumption while maintaining the same functionalities for the software in order to build sustainable and green software. Firstly, in this thesis work, we define the terms sustainable and green in the area of software development. To build a software product, we need to follow a software engineering process. Hence, we define and describe sustainable and green criteria to be respected after each step of this process in order to establish a sustainable and green software engineering process. Then, we focus on the software energy consumption estimation. Many research works tried to propose various tools to estimate the energy consumption due to software in order to reduce carbon footprint. Unfortunately, these studies, in the majority of cases, consider only the CPU and neglects all others components. Existing power consumption methodologies need to be improved by taking into account more components susceptible to consume energy during runtime of an application. Writing sustainable, power efficient and green software necessitates to understand the power consumption behavior of a computer program. One of the benefits is the fact that developers, by improving their source code implementations, will optimize software power consumption. Moreover, there is a lack of analyzing tool to dynamically monitor source code energy consumption of several components. Thus, we propose GMTEEC (Generic Methodology of a Tool to Estimate Energy Consumption) which is composed of four layers assisting developers to build a tool estimating the software power consumption. Hence, in our work, respecting the layers of GMTEEC, we develop TEEC (Tool to Estimate Energy Consumption) which is based on mathematical formula established for each component (CPU, memory, hard disk, network) in order to estimate the total software energy consumption. Moreover, we add in TEEC the capacity to locate dynamically the hotpoints which are the parts of source code consuming the greater amount of energy in order to help and guide developers to optimize their source code and build efficient, sustainable and green software. We performed a variety of experiments to validate the accuracy and quality of the sustainable and green software engineering process and TEEC. The results demonstrate the possibility to save significant quantity of energy and time at limited costs with an important positive impact on environment
APA, Harvard, Vancouver, ISO, and other styles
4

Yacoub, Sherif M. "Pattern-oriented analysis and design (POAD) a methodology for software development /." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1026.

Full text
Abstract:
Thesis (Ph. D.)--West Virginia University, 1999.
Title from document title page. Document formatted into pages; contains xx, 343 p. : ill. (some col.). Vita. Includes abstract. Includes bibliographical references (p. 324-337).
APA, Harvard, Vancouver, ISO, and other styles
5

Sincharoenpanich, Puangpetch, and Nunthapin Chantachaimongkol. "Critical factors for implementing the Scrum software development methodology." Thesis, Mälardalens högskola, Akademin för ekonomi, samhälle och teknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-18203.

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

Ramsin, Raman. "The engineering of an object-oriented software development methodology." Thesis, University of York, 2006. http://etheses.whiterose.ac.uk/9898/.

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

Sadrieh, Afshin. "Applied novel software development methodology for process engineering application." Thesis, Sadrieh, Afshin (2017) Applied novel software development methodology for process engineering application. PhD thesis, Murdoch University, 2017. https://researchrepository.murdoch.edu.au/id/eprint/38742/.

Full text
Abstract:
Chemical processes are nonlinear continuous/discrete dynamic systems that are subject to considerable uncertainties and variations during their design and operation. These systems are designed to operate at an economically optimal steady-state. However, minor changes in process parameters’ values might cause deviations and elicit dynamic responses from processes. Controllability—defined as the ability of holding a process within a specified operating regime and the controllability assessment of each given process system—should be taken into account during the system design phase. This emphasises the necessity of effective software tools that could assist process engineers in their controllability evaluation. Although there are few multipurpose tools available for this task, developing software tools for controllability analysis is a tedious and sophisticated undertaking. It involves elaboration from multiple disciplines, and the requirements of controllability assessments are so vast that it is almost impossible to create general software that covers all controllability measures and cases. This thesis aims to systematically tackle the challenge of developing practical and high-quality software tools for controllability problems while reducing the required time and effort, regardless of the size and scale of the controllability problem. Domain-specific language (DSL) methodology is proposed for this purpose. DSLs are programming languages designed to address the programming problems of a specific domain. Therefore, well-designed DSLs are simple, easy to use and capable of solving any problem defined in their domains. Based on DSL methodology, this study proposes a four-element framework to partition the software system into decoupled elements, and discusses the design and implementation steps of each element as well as communication between elements. The superiority of the developed methodology based on DSL is compared with traditional programming techniques for controllability assessment of various case studies. Essentially, the major advantage of the proposed methodology is the performance of the software product. Performance measures used in this study are total time to develop (TD) the software tool and its modifiability. Total time and effort to implement and use the result products presents up to five times improvement. Moreover, the result product’s modifiability is assessed by applying modifications, which also demonstrates up to five times improvement. All measures are tested on continuous stirred-tank reaction (CSTR) and forced-circulation evaporator (FCE) case studies. In conclusion, this study significantly contributes to two fields. The first is DSL, since this thesis studies different types of DSLs and evaluates their applications in the controllability analysis. The second is the controllability evaluation, since this study examines a new methodology for software development in controllability assessment.
APA, Harvard, Vancouver, ISO, and other styles
8

CARVALHO, Fernando Ferreira de. "An embedded software component quality evaluation methodology." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2412.

Full text
Abstract:
Made available in DSpace on 2014-06-12T15:57:59Z (GMT). No. of bitstreams: 2 arquivo3240_1.pdf: 2429983 bytes, checksum: 9b9eff719ea26a708f6868c5df873358 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010
Universidade de Pernambuco
Um dos maiores desafios para a indústria de embarcados é fornecer produtos com alto nível de qualidade e funcionalidade, a um baixo custo e curto tempo de desenvolvimento, disponibilizando-o rapidamente ao mercado, aumentando assim, o retorno dos investimentos. Os requisitos de custo e tempo de desenvolvimento têm sido abordados com bastante êxito pela engenharia de software baseada em componentes (CBSE) aliada à técnica de reuso de componentes. No entanto, a utilização da abordagem CBSE sem as devidas verificações da qualidade dos componentes utilizados, pode trazer conseqüências catastróficas (Jezequel et al., 1997). A utilização de mecanismos apropriados de pesquisa, seleção e avaliação da qualidade de componentes são considerados pontos chave na adoção da abordagem CBSE. Diante do exposto, esta tese propõe uma Metodologia para Avaliação da Qualidade de Componentes de Software Embarcados sob diferentes aspectos. A idéia é solucionar a falta de consistência entre as normas ISO/IEC 9126, 14598 e 2500, incluindo o contexto de componente de software e estendendo-o ao domínio de sistemas embarcados. Estas normas provêem definições de alto nível para características e métricas para produtos de software, mas não provêem formas de usá-las efetivamente, tornando muito difícil aplicá-las sem adquirir mais informações de outras fontes. A Metodologia é composta de quatro módulos que se complementam em busca da qualidade, através de um processo de avaliação, um modelo de qualidade, técnicas de avaliação agrupadas por níveis de qualidade e uma abordagem de métricas. Desta forma, ela auxilia o desenvolvedor de sistemas embarcado no processo de seleção de componentes, avaliando qual componente melhor se enquadra nos requisitos do sistema. É utilizada por avaliadores terceirizados quando contratados por fornecedores a fim de obter credibilidade em seus componentes. A metodologia possibilita avaliar a qualidade do componente embarcado antes do mesmo ser armazenado em um sistema de repositório, especialmente no contexto do framework robusto para reuso de software, proposto por Almeida (Almeida, 2004)
APA, Harvard, Vancouver, ISO, and other styles
9

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.

Full text
Abstract:
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
APA, Harvard, Vancouver, ISO, and other styles
10

Tran, Quynh Nhu Information Systems Technology &amp Management Australian School of Business UNSW. "MOBMAS - A methodology for ontology-based multi-agent systems development." Awarded by:University of New South Wales. School of Information Systems, Technology and Management, 2005. http://handle.unsw.edu.au/1959.4/24254.

Full text
Abstract:
???Agent-based systems are one of the most vibrant and important areas of research and development to have emerged in information technology in the 1990s??? (Luck et al. 2003). The use of agents as a metaphor for designing and constructing software systems represents an innovative movement in the field of software engineering: ???Agent- Oriented Software Engineering (AOSE)??? (Lind 2000; Luck et al. 2003). This research contributes to the evolution of AOSE by proposing a comprehensive ontology-based methodology for the analysis and design of Multi-Agent Systems (MAS). The methodology is named MOBMAS, which stands for ???Methodology for Ontology-Based MASs???. A major improvement of MOBMAS over the existing agentoriented MAS development methodologies is its explicit and extensive support for ontology-based MAS development. Ontologies have been widely acknowledged for their significant benefits to interoperability, reusability, MAS development activities (such as system analysis and agent knowledge modelling) and MAS operation (such as agent communication and reasoning). Recognising these desirable ontology???s benefits, MOBMAS endeavours to identify and implement the various ways in which ontologies can be used in the MAS development process and integrated into the MAS model definitions. In so doing, MOBMAS has exploited ontologies to enhance its MAS development process and MAS development product with various strengths. These strengths include those ontology???s benefits listed above, and those additional benefits uncovered by MOBMAS, e.g. support for verification and validation, extendibility, maintainability and reliability. Compared to the numerous existing agent-oriented methodologies, MOBMAS is the first that explicitly and extensively investigates the diverse potential advantages of ontologies in MAS development, and which is able to implement these potential advantages via an ontology-based MAS development process and a set of ontology-based MAS model definitions. Another major contribution of MOBMAS to the field of AOSE is its ability to address all key concerns of MAS development in one methodological framework. The methodology provides support for a comprehensive list of methodological requirements, which are important to agent-oriented analysis and design, but which may not be wellsupported by the current methodologies. These methodological requirements were identified and validated by this research from three sources: the existing agent-oriented methodologies, the existing evaluation frameworks for agent-oriented methodologies and conventional system development methodologies, and a survey of practitioners and researchers in the field of AOSE. MOBMAS supports the identified methodological requirements by combining the strengths of the existing agent-oriented methodologies (i.e. by reusing and enhancing the various strong techniques and model definitions of the existing methodologies where appropriate), and by proposing new techniques and model definitions where necessary. The process of developing MOBMAS consisted of three sequential research activities. The first activity identified and validated a list of methodological requirements for an Agent Oriented Software Engineering methodology as mentioned above. The second research activity developed MOBMAS by specifying a development process, a set of techniques and a set of model definitions for supporting the identified methodological requirements. The final research activity evaluated and refined MOBMAS by collecting expert reviews on the methodology, using the methodology on an application and conducting a feature analysis of the methodology.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software development methodology"

1

Software release methodology. Upper Saddle River, N.J: Prentice Hall PTR, 1999.

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

Daniela, Rus, ed. Systems methodology for software. Singapore: World Scientific, 1993.

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

Managing software deliverables: A software development management methodology. Burlington, MA: Elsevier Digital Press, 2004.

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

McCluskey, Micheal. A methodology for AI software development. [S.l: The Author], 1990.

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

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

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

Crystal clear: A human-powered methodology for small teams. Boston: Addison-Wesley, 2005.

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

C, Patton Peter, ed. Design for trustworthy software: Tools, techniques, and methodology of developing robust software. Upper Saddle River, NJ: Prentice Hall, 2007.

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

Corporation, Digital Equipment. A methodology for software development using VMS tools. Maynard, Mass: D.E.C., 1988.

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

Padilla, Robert F. Object-oriented methodology for Marine Corps software development. Monterey, Calif: Naval Postgraduate School, 1994.

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

Elementary logic for software development. London: Springer, 2008.

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

Book chapters on the topic "Software development methodology"

1

Schnupp, Peter, Chau Thuy Nguyen Huu, and Lawrence W. Bernhard. "Software Development Methodology." In Springer Compass International, 227–51. Berlin, Heidelberg: Springer Berlin Heidelberg, 1989. http://dx.doi.org/10.1007/978-3-642-74303-0_11.

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

Duchowski, Andrew T. "System Software Development." In Eye Tracking Methodology: Theory and Practice, 77–95. London: Springer London, 2003. http://dx.doi.org/10.1007/978-1-4471-3750-4_7.

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

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

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

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

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

Gliwa, Peter. "Methodology During the Development Process." In Embedded Software Timing, 247–65. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-64144-3_9.

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

Gavras, Anastasius, Mariano Belaunde, Luís Ferreira Pires, and João Paulo A. Almeida. "Towards an MDA-Based Development Methodology." In Software Architecture, 230–40. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24769-2_20.

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

Vavpotič, Damjan, Marko Bajec, and Marjan Krisper. "Software Development Methodology Evaluation Model." In Constructing the Infrastructure for the Knowledge Economy, 141–53. Boston, MA: Springer US, 2004. http://dx.doi.org/10.1007/978-1-4757-4852-9_9.

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

Quemada, Juan, Arturo Azcorra, and Santiago Pavón. "The Lotosphere Design Methodology." In LOTOSphere: Software Development with LOTOS, 29–58. Boston, MA: Springer US, 1995. http://dx.doi.org/10.1007/978-1-4615-2203-4_2.

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

Traynor, Owen, Dan Hazel, Peter Kearney, Andrew Martin, Ray Nickson, and Luke Wildman. "The Cogito development system." In Algebraic Methodology and Software Technology, 586–91. Berlin, Heidelberg: Springer Berlin Heidelberg, 1997. http://dx.doi.org/10.1007/bfb0000505.

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

Bao, Yuyan, and Gary T. Leavens. "A Methodology for Invariants, Framing, and Subtyping in JML." In Principled Software Development, 19–39. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-98047-8_2.

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

Conference papers on the topic "Software development methodology"

1

Trussell, L. "Essential software development methodology." In IEEE Power Engineering Society. 1999 Winter Meeting (Cat. No.99CH36233). IEEE, 1999. http://dx.doi.org/10.1109/pesw.1999.747479.

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

Giunchiglia, Fausto, John Mylopoulos, and Anna Perini. "The tropos software development methodology." In the first international joint conference. New York, New York, USA: ACM Press, 2002. http://dx.doi.org/10.1145/544741.544748.

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

Mahdavi-Hezave, Rezvan, and Raman Ramsin. "FDMD: Feature-Driven Methodology Development." In 10th International Conference on Evaluation of Novel Software Approaches to Software Engineering. SCITEPRESS - Science and and Technology Publications, 2015. http://dx.doi.org/10.5220/0005384202290237.

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

Löwgren, Jonas. "Applying design methodology to software development." In the conference. New York, New York, USA: ACM Press, 1995. http://dx.doi.org/10.1145/225434.225444.

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

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

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

John, Santhosh, Nazaraf Shah, Craig Stewart, and Leon Samlov. "Software Centric Innovative Methodology for Ontology Development." In 9th International Conference on Knowledge Engineering and Ontology Development. SCITEPRESS - Science and Technology Publications, 2017. http://dx.doi.org/10.5220/0006482901390146.

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

He, Song, Huiyou Chang, and Qing Wang. "Component Library-Based ERP Software Development Methodology." In 2009 International Conference on Interoperability for Enterprise Software and Applications China (IESA). IEEE, 2009. http://dx.doi.org/10.1109/i-esa.2009.47.

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

Nuevo, Eva del, Mario Piattini, and Francisco J. Pino. "Scrum-based Methodology for Distributed Software Development." In 2011 6th IEEE International Conference on Global Software Engineering (ICGSE). IEEE, 2011. http://dx.doi.org/10.1109/icgse.2011.23.

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

"WORK PRODUCT-DRIVEN SOFTWARE DEVELOPMENT METHODOLOGY IMPROVEMENT." In 5th International Conference on Software and Data Technologies. SciTePress - Science and and Technology Publications, 2010. http://dx.doi.org/10.5220/0002898200050013.

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

Soundararajan, Shvetha, James D. Arthur, and Osman Balci. "A Methodology for Assessing Agile Software Development Methods." In 2012 Agile Conference. IEEE, 2012. http://dx.doi.org/10.1109/agile.2012.24.

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

Reports on the topic "Software development methodology"

1

Baca, L. S., J. F. Bouchard, E. W. Collins, M. Eisenhour, D. D. Neidigk, M. J. Shortencarier, and P. A. Trellue. Software development methodology for high consequence systems. Office of Scientific and Technical Information (OSTI), October 1997. http://dx.doi.org/10.2172/541928.

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

Yau, Stephen S., Doc-Hwan Bae, Pranshu K. Gupta, Sun I. Paek, and Thaddeus J. Thigpen. A Software Development Methodology for Parallel Processing Systems. Fort Belvoir, VA: Defense Technical Information Center, October 1995. http://dx.doi.org/10.21236/ada303063.

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

T. Hamilton. Prometheus Reactor I&C Software Development Methodology, for Action. Office of Scientific and Technical Information (OSTI), July 2005. http://dx.doi.org/10.2172/883391.

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

Colston, Sharon N. Implementation of Successful Practices Using an Iterative Development Methodology for an AEGIS Configuration Management Software Application. Fort Belvoir, VA: Defense Technical Information Center, September 1998. http://dx.doi.org/10.21236/ada363072.

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

Chapman, Raymond S., Terry K. Gerald, and Mark S. Dortch. Water Quality Research Program: Development of Unstructured Grid Linkage Methodology and Software for CE-QUAL-ICM. Fort Belvoir, VA: Defense Technical Information Center, August 1997. http://dx.doi.org/10.21236/ada329729.

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

Jayaraman, Sundaresan, Sambasivan Narayanan, Naveen Krishna, and S. Venkataraman. Design and Development of a Knowledge-based Framework for Trouser Procurement: Bid Evaluation Software Tool (BEST); Volume II: Research Methodology. Fort Belvoir, VA: Defense Technical Information Center, March 1996. http://dx.doi.org/10.21236/ada328727.

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

Tsidylo, Ivan M., Hryhoriy V. Tereshchuk, Serhiy V. Kozibroda, Svitlana V. Kravets, Tetiana O. Savchyn, Iryna M. Naumuk, and Darja A. Kassim. Methodology of designing computer ontology of subject discipline by future teachers-engineers. [б. в.], September 2019. http://dx.doi.org/10.31812/123456789/3249.

Full text
Abstract:
The article deals with the problem of the methodology of designing computer ontology of the subject discipline by the future teachers-engineers in the field of computer technologies. The scheme of ontology of the subject discipline is presented in which the set of concepts of the future computer ontology and the set of relations between them are represented. The main criteria of the choice of systems of computer ontologies for designing computer ontology of the subject discipline: software architecture and tools development; interoperability; intuitive interface are established. The selection of techniques for designing ontologies using computer ontology systems is carried out. The algorithm of designing computer ontology of the subject discipline by the future teachers-engineers in the field of computer technologies is proposed.
APA, Harvard, Vancouver, ISO, and other styles
8

Chamberlain, C. A., and K. Lochhead. Data modeling as applied to surveying and mapping data. Natural Resources Canada/CMSS/Information Management, 1988. http://dx.doi.org/10.4095/331263.

Full text
Abstract:
The Geodetic Survey Division of the Canada Centre for Surveying is replacing the National Geodetic Data Base (NGDB) with the National Geodetic Information System (NGIS). For the NGIS to be successful, it was recognized that a sound, well engineered data mode was essential. The methodology chosen to design the data mode! was Nijssen's Information Analysis Methodology (NIAM), a binary modeling technique that is supported by a Computer Aided Software Engineering (CASE) tool, PC-IAST. An NGIS prototype has also been developed using Digital Equipment of Canada's Relational Database (Rdb) management system and COGNOS Corporations POWERHOUSE 4th generation language. This paper addresses the need for, and the advantages of using a strong engineering approach to data modeling and describes the use of the NIAM methodology in NGIS development. The paper identifies the relationship between the data mode!, data structures, the design and development of a database and the use of automated tools for systems development. In conclusion, critical success factors for the continuation of the N.G.I.S. developments are identified and the benefits that will accrue are enumerated.
APA, Harvard, Vancouver, ISO, and other styles
9

Yevtuch, Mykola B., Vasyl M. Fedorets, Oksana V. Klochko, Mariya P. Shyshkina, and Alla V. Dobryden. Development of the health-preserving competence of a physical education teacher on the basis of N. Bernstein's theory of movements construction using virtual reality technologies. CEUR Workshop Proceedings, July 2021. http://dx.doi.org/10.31812/123456789/4634.

Full text
Abstract:
The article studies the results of the research aimed at the improvement of the methodology of develop- ment of the health-preserving competence of a Physical Education teacher in conditions of post-graduate education on the basis of Nikolai Bernstein’s theory of movement construction using virtual reality technologies. Based on the use of AR/VR technologies a software application “Virtual Model Illustrating Nikolai Bernstein’s Theory of Movement Construction” was developed. The stated model is one of the tools of the “Methodology of development of the health preserving competence of a Physical Educa- tion teacher on the basis of Nikolai Bernstein’s theory of the levels of movement construction”. The experimental study determines that the application of the virtual model within the stated methodology is an effective tool for the development of the health preserving competence of a Physical Education teacher. The application of the virtual model allows the actualization of the health preserving, conceptual, gnoseological, biomechanical, inclusive, corrective potentials of Nikolai Bernstein’s theory of movement construction. The use of the virtual model presents the ways of targeted and meaningful use of Nikolai Bernstein’s theory of the levels of movement construction by a Physical Education teacher and the improvement of physical and recreational technologies and concrete physical exercises and movement modes. Due to the application of virtual reality tools, health-preserving, preventative, corrective and developmental strategies are being formed among which the significant ones are: “Application of syner- gistic movements to adaptation to movement activity, and recreation”, “Application of spatial movements for actualization of the orientation and search activities and development of spatial thinking”, “Use of movements with a complicated algorithm for intellect development”.
APA, Harvard, Vancouver, ISO, and other styles
10

Holub, Oleksandr, Mykhailo Moiseienko, and Natalia Moiseienko. Fluid Flow Modelling in Houdini. [б. в.], November 2020. http://dx.doi.org/10.31812/123456789/4128.

Full text
Abstract:
The modern educational environment in the field of physics and information technology ensures the widespread use of visualization software for successful and deep memorization of material. There are many software for creating graphic objects for presentations and demonstrations, the most popular of which were analyzed. The work is devoted to the visualization of liquids with different viscosity parameters. The article describes the development of a fluid model in the form of a particle stream. The proposed methodology involves using the Houdini application to create interactive models. The developed model can be used in the educational process in the field of information technology.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software development methodology' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography