To see the other types of publications on this topic, follow the link: Software development methodology.
Dissertations / Theses on the topic 'Software development methodology'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research 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.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
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 textAbstract:
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.
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
3
Acar, Hayri. "Software development methodology in a Green IT environment." Thesis, Lyon, 2017. http://www.theses.fr/2017LYSE1256/document.
Full textAbstract:
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
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 textAbstract:
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).
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
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
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 textAbstract:
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.
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 textAbstract:
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: 2010Universidade 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)
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 textAbstract:
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. CopyrightDissertation (MBA)--University of Pretoria, 2011.
Gordon Institute of Business Science (GIBS)
unrestricted
10
Tran, Quynh Nhu Information Systems Technology & 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 textAbstract:
???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.
11
Sulemani, Kashif Ali, and Muhammad Nadeem Nasir. "Communication Support to Scrum Methodology in Offshore Development." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2815.
Full textAbstract:
In today world, the software companies are expanded above the continents. The software development work span continents and the distributed team work together over the borders. The agile development methodology demands close collaboration with client, rapid requirements change and an iterative development of fixed length. When this way of agile approach is applied in a distributed project, it requires frequent communication and knowledge exchange among the dispersed team members and need collaboration with customer over distance. Besides the geographical, the linguistic and the different time zone barriers in a distributed project, the computer mediated tools suppose being useful media in connecting and to coordinating among dispersed colleague in a project. Though, these tools depict variant effectiveness in communication exchange, however, there efficient use connects peoples at the two sites. The aim of this thesis study is to explore the communication channel support to the Scrum practices in a distributed project. The purpose of the research is to analyse collaboration and communication in distributed teams working together through computer mediated technology. For this purpose, a company case is studied doing a distributed agile project. The author’s insight the communication and information exchange through the ICT in an agile project. Based on the case analysis, the authors suggest the recommendations for implementing and establishing agile practices in a distance project.Mobil: +46700381303
12
Al-Azawi, Rula K. "Agent Oriented Software Engineering (AOSE) approach to game development methodology." Thesis, De Montfort University, 2015. http://hdl.handle.net/2086/11120.
Full textAbstract:
This thesis investigates existing game development methodologies, through the process of researching game and system development models. The results indicate that these methodologies are engineered to solve specific problems, and most are suitable only for specific game genres. Different approaches to building games have been proposed in recent years. However, most of these methodologies focus on the design and implementation phase. This research aims to enhance game development methodologies by proposing a novel game development methodology, with the ability to function in generic game genres, thereby guiding game developers and designers from the start of the game development phase to the end of the implementation and testing phase. On a positive note, aligning development practice with universal standards makes it far easier to incorporate extra team members at short notice. This increased the confidence when working in the same environment as super developers. In the gaming industry, most game development proceeds directly from game design to the implementation phase, and the researcher observes that this is the only industry in which this occurs. It is a consequence of the game industry’s failure to integrate with modern development techniques. The ultimate aim of this research to apply a new game development methodology using most game elements to enhance success. This development model will align with different game genres, and resolve the gap between industry and research area, so that game developers can focus on the important business of creating games. The primary aim of Agent Oriented Agile Base (AOAB) game development methodology is to present game development techniques in sequential steps to facilitate game creation and close the gap in the existing game development methodologies. Agent technology is used in complex domains such as e-commerce, health, manufacturing, games, etc. In this thesis we are interested in the game domain, which comprises a unique set of characteristics such as automata, collaboration etc. Our AOAB will be based on a predictive approach after adaptation of MaSE methodology, and an adaptive approach using Agile methodology. To ensure proof of concept, AOAB game development methodology will be evaluated against industry principles, providing an industry case study to create a driving test game, which was the problem motivating this research. Furthermore, we conducted two workshops to introduce our methodology to both academic and industry participants. Finally, we prepared an academic experiment to use AOAB in the academic sector. We have analyzed the feedbacks and comments and concluded the strengths and weakness of the AOAB methodology. The research achievements are summarized and proposals for future work outlined.
13
Hsu, Yung-Kao. "A methodology for refining formal software specification using transformation-based tools." Diss., Georgia Institute of Technology, 1991. http://hdl.handle.net/1853/8185.
Full text
14
BARBOSA, Pedro Yóssis Silva. "Privacy by evidence: a software development methodology to provide privacy assurance." Universidade Federal de Campina Grande, 2018. http://dspace.sti.ufcg.edu.br:8080/jspui/handle/riufcg/1613.
Full textAbstract:
Submitted by Lucienne Costa (lucienneferreira@ufcg.edu.br) on 2018-08-30T21:18:48Z
No. of bitstreams: 1
PEDRO YÓSSIS SILVA BARBOSA – TESE (PPGCC) 2018.pdf: 5191620 bytes, checksum: bf226ff6b5409b6330fd126cc2677503 (MD5)Made available in DSpace on 2018-08-30T21:18:48Z (GMT). No. of bitstreams: 1 PEDRO YÓSSIS SILVA BARBOSA – TESE (PPGCC) 2018.pdf: 5191620 bytes, checksum: bf226ff6b5409b6330fd126cc2677503 (MD5) Previous issue date: 2018-02
Capes
Em um mundo cada vez mais conectado, uma diversidade de softwares e sensores coletam dados dos ambientes e seus habitantes. Devido à riqueza das informações coletadas, privacidade se torna um requisito importante. Aplicações estão sendo desenvolvidas, e, apesar de existirem princípios e regras para lidar com a privacidade dos indivíduos, faltam metodologias para guiar a integração das diretrizes de privacidade em um processo de desenvolvimento. Metodologias existentes como o Privacidade desde a Concepção (do inglês Privacy by Design – PbD) ainda são vagas e deixam muitos questionamentos em aberto sobre como aplicá-las na prática. Neste trabalho, nós propomos o conceito de Privacidade por Evidência (do inglês Privacy by Evidence – PbE), uma metodologia de desenvolvimento de software para prover privacidade. Dada a dificuldade em prover privacidade total, propomos que as documentações das mitigações sejam em formas de evidências de privacidade, objetivando aumentar a confiança no projeto. Para validar a eficácia, PbE tem sido utilizada durante o desenvolvimento de quatro aplicações que servem como estudos de caso. O primeiro estudo de caso considerado é uma aplicação de medição inteligente de energia; o segundo considera uma aplicação de contagem e monitoramento de pessoas; o terceiro considera um sistema de monitoramento de eficiência energética; e o quarto considera um sistema de autenticação de dois fatores. Para estas aplicações, os times proveram sete,cinco,cinco e quatro evidências de privacidade, respectivamente, e concluimos que a PbE pode ser efetiva em ajudar a entender e a tratar as necessidades de proteção à privacidade quando se está desenvolvendo software.
In anincreasinglyconnectedworld,adiversityofsoftwareandsensorscollectdatafromthe environmentanditsinhabitants.Becauseoftherichnessoftheinformationcollected,privacy becomes animportantrequirement.Applicationsarebeingdeveloped,and,althoughthere are principlesandrulesregardingtheprivacyofindividuals,thereisstillalackofmethod- ologies toguidetheintegrationofprivacyguidelinesintothedevelopmentprocess.Existing methodologies likethe Privacy byDesign (PbD) arestillvagueandleavemanyopenques- tions onhowtoapplytheminpractice.Inthisworkweproposetheconceptof Privacy by Evidence (PbE), asoftwaredevelopmentmethodologytoprovideprivacyassurance.Given the difficultyinprovidingtotalprivacyinmanyapplications,weproposetodocumentthe mitigationsinformofevidencesofprivacy,aimingtoincreasetheconfidenceoftheproject. Tovalidateitseffectiveness, PbE has beenusedduringthedevelopmentoffourapplications that serveascasestudies.Thefirstconsideredcasestudyisasmartmeteringapplication; the secondconsidersapeoplecountingandmonitoringapplication;thethirdconsidersan energyefficiencymonitoringsystem;andthefourthconsidersatwofactorauthentication system. Fortheseapplications,theteamswereabletoprovideseven,five,five,andfour evidencesofprivacy,respectively,andweconcludethat PbE can beeffectiveinhelpingto understand andtoaddresstheprivacyprotectionneedswhendevelopingsoftware.
15
Court, Cliff. "A new estimation methodology for reusable component-based software development projects." Master's thesis, University of Cape Town, 1999. http://hdl.handle.net/11427/9708.
Full textAbstract:
Bibliograhy: leaves 118-121.Estimating the duration of software development projects is a difficult task. There are many factors that can derail software projects. However, estimation forms the fundamental part of planning and costing any project and is therefore very necessary. While several formal estimation methodologies exist, they all exhibit weaknesses in one form or another. The most established methodologies are based on early software development methods and it is questionable as to whether they can still address more modern development methods such as reusable component-based programming. Some researchers believe not and have proposed new methodologies that attempt to achieve this. Thus what is needed is a methodology that takes into account modern component-based development practices and, as a result, provides acceptable accuracy for the software organisation. This dissertation attempts to uniquely satisfy both of these requirements.
16
Hu, Xiaolin. "A simulation-based software development methodology for distributed real-time systems." Diss., The University of Arizona, 2004. http://hdl.handle.net/10150/280514.
Full textAbstract:
Powered by the rapid advance of computer, network, and sensor/actuator technologies, distributed real-time systems that continually and autonomously control and react to the environment have been widely used. The combination of temporal requirements, concurrent environmental entities, and high reliability requirements, together with distributed processing make the software to control these systems extremely hard to design and difficult to verify. In this work, we developed a simulation-based software development methodology to manage the complexity of distributed real-time software. This methodology, based on discrete event system specification (DEVS), overcomes the "incoherence problem" between different design stages by emphasizing "model continuity" through the development process. Specifically, techniques have been developed so that the same control models that are designed can be tested and analyzed by simulation methods and then easily deployed to the distributed target system for execution. To improve the traditional software testing process where real-time embedded software needs to be hooked up with real sensor/actuators and placed in a physical environment for meaningful test and analysis, we developed a virtual test environment that allows software to be effectively tested and analyzed in a virtual environment, using virtual sensor/actuators. Within this environment, stepwise simulation methods have been developed so that different aspects, such as logic and temporal behaviors, of a real-time system can be tested and analyzed incrementally. Based on this methodology, a simulation and testing environment for distributed autonomous robotic systems is developed. This environment has successfully supported the development and investigation of several distributed autonomous robotic systems. One of them is a "dynamic team formation" system in which mobile robots search for each other, and then form a team dynamically through self-organization. Another system is a scalable robot convoy system in which robots convoy and maintain a line formation in a coordinated way.
17
Chen, Xin. "Towards an integrated methodology for the development of hybrid information systems." Thesis, University of Sunderland, 1998. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.263000.
Full textAbstract:
Our modern information society has produced many sophisticated requirements for the development of information systems. A new challenge is the study of hybrid information systems that combine traditional information systems with knowledge-based systems. This new generation information system is considerably more powerful than a simple extrapolation of existing system concepts. It is easy to imagine the advantages of powerful knowledge-based systems with efficient access to several large databases, and of large traditional information systems with added intelligence. Due to the complex nature of hybrid information systems, it is umealistic to expect that they can be developed using one standard method. The use of several independently developed methods has a number of drawbacks, such as inconsistency, redundancy, amount of effort required and possible loss of information. In an attempt to provide at least a partial solution to this problem. this thesis describes a new integrated methodology for developing hybrid information systems. This methodology combines the method for developing traditional information systems with the method for developing knowledge-based systems. The new methodology provides a hybrid lifecycle process model to combine the conventional waterfall process with rapid prototyping and model-based approaches. The proposed methodology integrates four eXlstmg methods using two integration approaches: intra-process and inter-process. In the requirements analysis phase. a structured method is applied to function analysis, an information modelling method is applied to data analysis, and a knowledge acquisition method is applied to knowledge analysis. An intraprocess approach is then used to integrate these techniques using consistency rules. In the design phase. the new methodology uses an inter-process approach to transform requirements analysis to object-oriented design by a transformation algorithm. Finally, an object-oriented method is applied to the design and implementation of hybrid information systems. Using the new methodology, a hybrid medical information system for dizziness (HMISD) was developed, which combines components of traditional medical information systems with components of medical expert systems. The construction and development of this software are described in detail. The system can support activities in hospitals including registration, diagnosis, investigations, drug management and clinical research. It provides assistance to hospital doctors and general practitioners. The performance of HMISD is evaluated by testing ninety three real patient cases and taking two investigations from medical staff and patients. The evaluation results show that HMISD is of good quality and that most of its users are satisfied. Three approaches are used to evaluate the proposed methodology: analysis of the development of HMISD, comparison with existing methodologies using CMD and expert evaluations. The evaluation conclusions indicate that this new integrated methodology can take advantage of the four existing methods and also remove some of the limitations of each individual method. It is applicable to the development of traditional information systems, knowledge-based systems, and large and complex hybrid information systems.
18
Thompson, Carla L. "Scaling the Zachman Framework a software development methodology for non-enterprise applications /." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/CThompson2006.pdf.
Full text
19
Stevens, Andrew. "An improved method for the mechanisation of inductive proof." Thesis, University of Edinburgh, 1990. http://hdl.handle.net/1842/19316.
Full text
20
Booth, Alan Edward. "A methodology for the development of embedded knowledge-based procedures." Thesis, University of East Anglia, 1995. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.361719.
Full text
21
Rangevik, Alexander. "Software Development across Time Zones : A Study of Globally Distributed Software Development in Small Enterprises." Thesis, Uppsala universitet, Informationssystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-203325.
Full textAbstract:
Globally distributed software development has become an important topic for small and medium enterprises. However, the distinct requirements of small and medium enterprises (SMEs) are still not fullyunderstood. To contribute to this growing discussion, I will present an ethnographical field study of a Swedish software company engaged in a distributed development practice with its American branch. By applying a theoretical view based on communication, coordination and control over time, space and socio/cultural difference, I show to what extent a distributed software development model affects SMEs. Whereproblems related to formal and informal communication, knowledge sharing, articulation work and programming methodologies are discussed. My findings suggest that organizational adjustments are needed for SMEs in order to take advantage of distributed software development (DSD), that specialized tools supporting coordination and articulation work is not so common in practice and that certain adjustment to agile methodologies could be made in order to better support DSD.
22
Tabrez, Shams, and Islam Jan. "Documentation and Agile Methodology." Thesis, Uppsala universitet, Institutionen för informatik och media, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-212653.
Full textAbstract:
Computer science in general and software engineering in specific is changing very fast. Software engineers are constantly using more innovative and more efficient ways to develop new software than in the past. This continuous evolution of software development methodologies has a great impact on both the software developed and the environment that the developers work-in. Agile software development methodologies are used to overcome many issues in the software development processes. One of the issues which still exists and needs to be addressed is the preparation of proper documentation along with the software. The work presented in this dissertation focuses on software documentation. The work starts by a thorough literature review which focuses on different aspects of software documentation and different agile methodologies. The thesis focuses on finding out the challenges that the developers faces during their development process. Two major questions addressed in the thesis. First one is to find the motivation to document in agile envirionment, whih is based on the hypothesis that there do exist a motivation. The second question is that how should documentation be produced such that we could avoid maximum possible potential problems. These questions are addressed with the help of different perspectives of the stockholders (i.e. developers and users) and the existing methods for documentation. A questionnaire was developed based on the nine categories of documentation, like user documents and system documents etc.. It included different questions related to the types of documents created in software development processes, the software development stage at which the documents are created and the importance of the documents. Questions from this questionnaire are then posted on agile specific discussion forums. Where many experienced and fresh practitioners participated in the discussion. We had a detailed discussion on every component of documentation and problems were identified by the practitioners. The questionnaire was also sent to different companies practicing agile methodology. we received about 14 responses as it was detailed questionnaire with about 34 questions. The responses of the discussion forum and survey are then analyzed and conclusions were drawn. The conclusions include that all the participants consider software documentation very important to the success of a software development project. the question of motivation is answered from the literature and opinions we received from experienced practitioners. While seven factor are identified that affect your documentation, to help solve the question of how should documentation be done.
23
Ceng, Jianjiang [Verfasser]. "A methodology for efficient multiprocessor system-on-chip software development / Jianjiang Ceng." Aachen : Hochschulbibliothek der Rheinisch-Westfälischen Technischen Hochschule Aachen, 2011. http://d-nb.info/1014458064/34.
Full text
24
Al-Harbi, Fahhad. "Development of a methodology and an expert system for disaster recovery." Thesis, University of Newcastle Upon Tyne, 1997. http://hdl.handle.net/10443/2077.
Full textAbstract:
The number of organisations that rely on computerised systems to perform their day-today operations and to help them in making decisions has grown rapidly over the last few years and continues to expand. On the other hand, the destruction or loss of these systems can be a nightmare and, in many cases, may leed to an end of providing services or trading for the organisation. Thus, the growing dependence on computer systems and the fear of being out of business have increased management awareness and understanding of the importance of plans to prevent or recover from a computer failure. Although senior management and IT directors have begun to appreciate the need for Disaster Recovery Plans (DRPs), they often raise common questions, such as. How long the organisation can tolerate the failure of its computer systems? Are we spending too much or too little on a recovery strategy? What type of recovery strategy is most appropriate for our IT centre? To look more closely at the effects of disasters on organisations and the importance of adopting DRPs, the researcher carried out a case study involving III organisations in Kuwait to examine their DRPs before and after the Iraqi Invasion in 1990 and to identify major problems facing IT managers on disaster recovery issues The literature review and the case study show that there is a lack of a comprehensive methodology and of a computerised intelligent system to guide organisations in selecting the most appropriate recovery strategy for their computer centres. Therefore, this research has developed a methodology and delivered an expert system that would assist IT directors to obtain answers to the above-mentioned questions and perform fast recovery from any type of computer disaster. The methodology consists of five phases that provide a step-by-step approach to ensure that the entire recovery strategy selection process is covered. The phases are: Threats Assessment, Business Impact Assessment, Recovery Strategy Analysis, Cost Analysis, and Recommendations.
25
Plant, Robert T. "A methodology for knowledge acquisition in the development of expert systems." Thesis, University of Liverpool, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.240378.
Full text
26
Ramaswamy, Arunkumar. "A model-driven framework development methodology for robotic systems." Thesis, Université Paris-Saclay (ComUE), 2017. http://www.theses.fr/2017SACLY011/document.
Full textAbstract:
La plupart des applications robotiques, telles que les véhicules autonomes, sont développées à partir d’une page blanche avec quelques rares réutilisations de conceptions ou de codes issus d’anciens projets équivalents. Qui plus est, les systèmes robotiques deviennent de plus en plus critiques, dans la mesure où ils sont déployés dans des environnements peu structurés, et centrés sur l’humain. Ces systèmes à fort contenu logiciel qui utilisent des composants distribués et hétérogènes interagissent dans un environnement dynamique, et incertain. Or, il s’agit là d’étapes indispensables pour la mise en place de méthodes d’évaluation extensibles, ainsi que pour permettre la réutilisation de composants logiciels pré-existants. Le développement de structures logicielles et d’outils de conception d’architectures, orientés pour la robotique, coûte cher en termes de temps et d’effort, et l’absence d’une approche systématique pourrait conduire à la production de conceptions adhoc, peu flexibles et peu réutilisables. Faire de la meta-structure de l’architecture un point de convergence offre de nouvelles possibilités en termes d’interopérabilité, et de partage de la connaissance, au sein des communautés dédiées à la mise en place d’architectures et de structures. Nous suivons cette direction, en proposant un modèle commun, et en fournissant une approche méthodologique systématique aidant à spécifier les différents aspects du développement d’architectures logicielles, et leurs relations au sein d’une structure partagéeMost innovative applications having robotic capabilities like self-driving cars are developed from scratch with little reuse of design or code artifacts from previous similar projects. As a result, work at times is duplicated adding time and economic costs. Absence of integrated tools is the real barrier that exists between early adopters of standardization efforts and early majority of research and industrial community. These software intensive systems are composed of distributed, heterogeneous software components interacting in a highly dynamic, uncertain environment. However, no significant systematic software development process is followed in robotics research. The process of developing robotic software frameworks and tools for designing robotic architectures is expensive both in terms of time and effort, and absence of systematic approach may result in ad hoc designs that are not flexible and reusable. Making architecture meta-framework a point of conformance opens new possibilities for interoperability and knowledge sharing in the architecture and framework communities. We tried to make a step in this direction by proposing a common model and by providing a systematic methodological approach that helps in specifying different aspects of software architecture development and their interplay in a framework
27
West, Daune. "Towards a subjective knowledge elicitation methodology for the development of expert systems." Thesis, University of Portsmouth, 1991. https://researchportal.port.ac.uk/portal/en/theses/towards-a-subjective-knowledge-elicitation-methodology-for-the-development-of-expert-systems(d63c460a-f71c-492d-9150-15c31becdb5b).html.
Full text
28
Hilal, Daoud Kassem. "The circumstantial occurrence methodology : a proposed way forward in strategic knowledge engineering." Thesis, Cranfield University, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.282178.
Full text
29
Gröner, Markus K. "Capturing Requirements Meeting Customer Intent: A Methodological Approach." Diss., Virginia Tech, 2002. http://hdl.handle.net/10919/27857.
Full textAbstract:
Product quality is directly related to how well that product meets the customerâ s needs and intents. It is paramount, therefore, to capture customer requirements correctly and succinctly. Unfortunately, most development models tend to avoid, or only vaguely define the process by which requirements are generated. Other models rely on formalistic characterizations that require specialized training to understand. To address such drawbacks we introduce the Requirements Generation Model (RGM) that (a) decomposes the conventional â requirements analysisâ phase into sub-phases which focus and refine requirements generation activities, (b) constrains and structures those activities, and (c) incorporates a monitoring methodology to assist in detecting and resolving deviations from process activities defined by the RGM. We present an empirical study of the RGM in an industrial setting, and results derived from this study that substantiate the effectiveness of the RGM in producing a better set of requirements.Ph. D.
30
Kivci, Erdem Turker. "Development Of A Methodology For Geospatial Image Streaming." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12612570/index.pdf.
Full textAbstract:
Serving geospatial data collected from remote sensing methods (satellite images, areal photos, etc.) have become crutial in many geographic information system (GIS) applications such as disaster management, municipality applications, climatology, environmental observations, military applications, etc. Even in today&rsquos highly developed information systems, geospatial image data requies huge amount of physical storage spaces and such characteristics of geospatial image data make its usage limited in above mentioned applications. For this reason, web-based GIS applications can benefit from geospatial image streaming through web-based architectures. Progressive transmission of geospatial image and map data on web-based architectures is implemented with the developed image streaming methodology. The software developed allows user interaction in such a way that the users will visualize the images according to their level of detail. In this way geospatial data is served to the users in an efficient way. The main methods used to transmit geospatial images are serving tiled image pyramids and serving wavelet based compressed bitstreams. Generally, in GIS applications, tiled image pyramids that contain copies of raster datasets at different resolutions are used rather than differences between resolutions. Thus, redundant data is transmitted from GIS server with different resolutions of a region while using tiled image pyramids. Wavelet based methods decreases redundancy. On the other hand methods that use wavelet compressed bitsreams requires to transform the whole dataset before the transmission. A hybrid streaming methodology is developed to decrease the redundancy of tiled image pyramids integrated with wavelets which does not require transforming and encoding whole dataset. Tile parts&rsquo
coefficients produced with the methodlogy are encoded with JPEG 2000, which is an efficient technology to compress images at wavelet domain.
31
Andersson, Tim, Gustav Arnesson, Pontus Brengdahl, Anna Ekelund, Claes Kallström, Kalle Olsson, Julia Thudén, and Erik Wallvik. "Experiences from the Development of a Webshop Using Scrum Methodology." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-107109.
Full textAbstract:
This is a report concerning the software development project Eldflugan, a system developed by eight students at Linköping University. It addresses experience from developing a web-based e-commerce using Scrum, an agile development method, which was used throughout the project. The teams work, how Scrum was applied with both advantages and disadvantages is being lifted. Different development environments have been used due to separate issues and opportunities, which is described. The database management systems, MySQL, and the local version, SQLite, are discussed as well as AJAX and PJAX, tools for giving the users a better and faster experience. To prepare Eldflugan for entering the e-commerce market, a marketing plan including environmental scanning, a SWOT analysis and a STP, has been made. Ethical aspects such as legal, use and handling of personal information and how it is communicated are also being addressed. Finally the report discusses product weaknesses, future opportunities, implementation difficulties and how those could have been prevented. It was found that Scrum is best used when it is utilized fully and a risk analysis can prevent unexpected problems to surface.
32
Lau, Y. K. H. "Towards a unified methodology for the design and development of distributed control system software." Thesis, University of Oxford, 1991. http://ora.ox.ac.uk/objects/uuid:a392a13b-f05f-4cb4-8c93-2d9c6eed5918.
Full textAbstract:
A unified approach to the design and development of distributed control software is presented. This method is the result of a 'tight' integration between a formal method for concurrent systems (CSP) and a structured method for distributed control system (DARTS). The work presented in this thesis does not seek to extend the semantic model of CSP nor to design a specific control algorithm, rather, efforts are made to apply the existing specification and verification techniques to enhance the formality of the well established and case-proven structured counterparts that benefits are captured from both methods. As a methodology is the central aim, the suggested approach is a first step towards a complete unified software development environment, which engineers can follow from organising design ideas to system implementation with proven correctness. The thesis develops a set of parameterised CSP predicates for expressing concurrency and communication together with a corresponding set of generic processes to reflect these specified behaviours. These generic processes are formal building blocks for generating system implementations at different levels of abstraction. Utilisation of DARTS criteria and the parameterised CSP objects frame the refinement strategies. Also, mappings of generic processes to pictorial representations are suggested which enable easy assimilation of the evolving designs. Applicability of the approach is demonstrated through a high level software design of a highperformance robot control system where its suitability is shown via requirement specifications, properties verification and implementation of salient behaviours using generic building blocks. Although verification often means rigorous mathematical reasoning, the thesis presents a proof assistant the Causality Diagram Evaluation Tool to automate the manipulation of CSP processes according to the defined algebraic laws. It is shown to be of value in reasoning with designs and implementations of the robot system. It is found that the analysis facility and the graphical interpretation of communication provided by the tool allow effective analysis and manipulation of early designs. The results derived from specifying essential design details, from transforming highly abstracted implementation models, and from investigation of system behaviours through formal reasoning and simulation conclude that formal methods, in particular CSP, has a niche value in enhancing software reliability at the sub-system level as well as providing a better underpinning to the structured method DARTS. The end product is a method to generate a correct and unambiguous document of the system concerned that is amenable to a direct implementation.
33
Gray, Peter Andrew. "A Petri net-occam based methodology for the development of dependable distributed control software." Thesis, Sheffield Hallam University, 1995. http://shura.shu.ac.uk/19716/.
Full textAbstract:
Analysis of flexible manufacturing cells (FMCs) shows their requirement for flexible, correct, reliable, safe and distributed control. A comparison of the state of the art in software engineering for parallel systems, and an examination of safety related systems, reveal a need for formal and rigorous techniques at all stages in the software life cycle. However, parallel software, safety related software and formal techniques are complex. It is better to avoid faults rather than eliminate or tolerate them, and although less flexible, avoidance is often simpler to implement. There is a need for a tool which overcomes many of these complexities, and this thesis discusses and defines such a tool in the form of a methodology. The novelty of the work is in the combination of the core goals to manage these issues, and how the strategies guide the user to a solution which will not deadlock and which is comprehensible. Place-transition Petri nets are an ideal representation for designing and modelling the interaction of concurrent (and distributed) processes. Occam is a high level real time parallel language designed to execute on one or a network of transputers. Transputers are processing, memory and communication building blocks, and, together with occam, are shown to be suitable for controlling and communicating the control as the DCS in FMCs. The methodology developed in this thesis adopts the mathematically based tools of Petri nets, occam and transputers, and, by exploiting their structural similarities, incorporates them in a steps and tasks to improve the development of correct, reliable and hence safe occam code. The four steps: identify concurrent and sequential operations, produce Petri net graphs for all controllers, combine controller Petri net graphs and translate Petri net graphs into occam; are structured around three core goals: Petri net/occam equivalence, comprehensibility and pro-activity; which are manifest in four strategies: output-work-backwards, concurrent and sequential actions, structuralise and modularise, and deadlock avoidance. The methodology assists in all stages of the software development life cycle, and is applicable to small DCSs such as an FMC. The methodology begins by assisting in the creation of DCS requirements from the manufacturing requirements of the FMC, and guides the user to the production of dependable occam code. Petri nets allow the requirements to be specified as they are created, and the methodology's imposed restrictions enable the final Petri net design to be translated directly into occam. Thus the mathematics behind the formal tools is hidden from the user, which should be attractive to industry. The methodology is successfully applied to the example FMC, and occam code to simulate the FMC is produced. Due to the novelty of the research, many suggestions for further work are given.
34
Rajalingham, Kamalasen. "The development of a structured methodology for the construction and integrity control of spreadsheet models." Thesis, University of Greenwich, 2002. http://gala.gre.ac.uk/6276/.
Full textAbstract:
Numerous studies and reported cases have established the seriousness of the frequency and impact of user-generated spreadsheet errors. This thesis presents a structured methodology for spreadsheet model development, which enables improved integrity control of the models. The proposed methodology has the potential to ensure consistency in the development process and produce more comprehensible, reliable and maintainable models, which can reduce the occurrence of user-generated errors. An insight into the nature and properties of spreadsheet errors is essential for the development of a methodology for controlling the integrity of spreadsheet models. An important by-product of the research is the development of a comprehensive classification or taxonomy of the different types of user-generated spreadsheet errors based on a rational taxonomic scheme. Research on the phenomenon of spreadsheet errors has revealed the need to adopt a software engineering based methodology as a framework for spreadsheet development in practical situations. The proposed methodology represents a new approach to the provision of a structured, software engineering based discipline for the development of spreadsheet models. It is established in this thesis that software engineering principles can in fact be applied to the process of spreadsheet model building to help improve the quality of the models. The methodology uses Jackson structures to produce the logical design of the spreadsheet model. This is followed by a technique to derive the physical model, which is then implemented as a spreadsheet. The methodology’s potential for improving the quality of spreadsheet models is demonstrated. In order to evaluate the effectiveness of the proposed framework, the various features of the proposed structured methodology are tested on a range of spreadsheet models through a series of experiments. The results of the tests provide adequate evidence of the methodology’s potential to reduce the occurrence of user-generated errors and enhance the comprehensibility of the models.
35
Yunten, Tamer. "Supervisory methodology and notation (SUPERMAN) for human-computer system development." Diss., Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/49969.
Full textAbstract:
The underlying goal of SUPERvisory Methodology And Notation (SUPERMAN) is to enhance productive operation of human-computer system developers by providing easy-to-use concepts and automated tools for developing high-quality (e.g., human-engineered, cost-effective, easy-to-maintain) target systems. The supervisory concept of the methodology integrates functions of many modeling techniques, and allows complete representation of the designer's conceptualization of a system's operation. The methodology views humans as functional elements of a system in addition to computer elements. Parts of software which implement human-computer interaction are separated from the rest of software. A single, unified system representation is used throughout a system lifecycle. The concepts of the methodology are notationally built into a graphical programming language. The use of this language in developing a system leads to a natural and orderly application of the methodology.Ph. D.
incomplete_metadata
36
Wilson, Susan April. "Product development in the leisure software industry : a design methodology for the development of inclusive interactive digital media." Thesis, University of Kent, 2005. http://www.research.ucreative.ac.uk/id/eprint/1082.
Full textAbstract:
The goal of this research project was to develop a methodology for designers that assists and quantifies concept design decisions so designers can; enable increase user access; widen the user demographic of interactive digital media; and improve participation and competence with technolgy through play.
37
Van, Der Merwe Ruan. "Development of tailorable mechanical design support software." Thesis, Stellenbosch : Stellenbosch University, 2013. http://hdl.handle.net/10019.1/85664.
Full textAbstract:
Thesis (MScEng)-- Stellenbosch University, 2013.ENGLISH ABSTRACT: A wide variety of design methodologies exist in literature and the methodologies employed may differ among companies and even among design teams. Therefore a software tool, called DiDeas II, is being developed for the early phases of mechanical engineering design. DiDeas II is customisable to accommodate various design methodologies. An approach for customisability which allows the user interface and data structure to be customised without changing the source code has been implemented in previous developments via an approach combining ontology and conceptual graphs. This approach is expanded in this thesis to allow for the implementation of various design methodologies through the use of tables for the display of information with inheritance of data among these tables. During groupwork, communication is both asynchronous and synchronous. DiDeas II has been developed in this thesis to facilitate and capture both asynchronous and synchronous communication between team members. Capturing such communications has the potential to provide insight into design decisions. The communication functionality was assessed in case studies in an academic environment. DiDeas II proved to be effective at recording “soft” information during design and placing the information into context for future reference. The degree to which DiDeas II could be customised to suit the design process at different companies was assessed through discussions with engineers in industry. These discussions showed that it was possible to customise DiDeas II according to the design processes followed by the participants.
AFRIKAANSE OPSOMMING: „n Wye verskeidenheid ontwerpsmetodologieë bestaan in die literatuur en die metodologieë wat gebruik word kan tussen maatskappye en selfs tussen ontwerpspanne verskil. Daarom word „n sagteware-hulpmiddel, genaamd DiDeas II, ontwikkel vir die vroeë fases van meganiese ingenieursontwerp. DiDeas II is pasbaar om voorsiening te maak vir verskeie ontwerpsmetodologieë. „n Benadering vir pasbaarheid wat toelaat dat die gebruikerskoppelvlak en datastruktuur aangepas kan word sonder om veranderings aan die bron-kode te maak, is geïmplementeer in vorige ontwikkelings deur „n benadering wat ontologie en konseptuele grafieke kombineer. Hierdie benadering is in hierdie tesis uitgebrei om voorsiening te maak vir die implementering van verskeie ontwerpsmetodologieë d.m.v. tabelle vir die vertoon van informasie, met data wat “oorgeërf” word tussen hierdie tabelle. Kommunikasie is beide asinkroon en sinkroon tydens groepwerk. DiDeas II is in hierdie tesis verder ontwikkel om beide asinkrone en sinkrone kommunikasie metodes te bemiddel en daarvan rekord te hou. Die rekordhouding van sulke kommunikasie het die potensiaal om insig te bied aangaande ontwerpbesluite. Die kommunikasie funksionaliteit is geassesseer in gevallestudies in „n akademiese omgewing. DiDeas II was effektief in die rekordhouding van “sagte” informasie tydens ontwerp, sowel as om sulke informasie binne konteks te plaas vir latere verwysing. Die mate waartoe DiDeas II aangepas kan word om voorsiening te maak vir die ontwerpsprosesse van verskillende maatskappye, is geassesseer deur gesprekke met ingenieurs in industrie. Hierdie gesprekke het getoon dat dit moontlik is om DiDeas II aan te pas volgens die ontwerpsprosesse wat die deelnemers gebruik.
38
Beagley, Nicholas I. "A longitudinal study to formalise a lifecycle methodology for small scale in-house software development." Thesis, Loughborough University, 1997. https://dspace.lboro.ac.uk/2134/33093.
Full textAbstract:
Continuing technological advances have brought in-house software development within the reach of small organisations. This study investigates the issues relating to bespoke software development for this emerging user population. It presents a lifecycle methodology, iteratively tailored to the characteristics of small scale in-house development, as a guide to future development. The study reports the development of the Database Application in Vehicle Ergonomics (DAVE), an information system which was designed to support the specific requirements of a small group of experts. An action research approach was taken through the planning, implementation and evaluation of the project's development methodology. The principles and techniques considered to suit the development scenario were adopted and applied within the framework of a defined lifecycle. The lifecycle directed user centred prototype evolution from a minimal specification to explore and deliver a range of novel applications. Taking a longitudinal approach, the study guided the iterative design of the lifecycle methodology over a series of development and maintenance case studies. The resulting 'modular system' lifecycle successfully managed the limited resources of small scale in-house software development to deliver and support a modular information system that was both usable and used.
39
Maeurer, Theodore R. (Theodore Robert) 1967. "Implementation of the critical chain project management methodology in IBM's S/390 software development environment." Thesis, Massachusetts Institute of Technology, 1999. http://hdl.handle.net/1721.1/9766.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, February 1999."December 1998."
Includes bibliographical references (p. 91-92).
Software Development projects have a long history of being notoriously difficult to manage. From early experiences with the IBM OS/360 Operating System over 20 years ago to more recent experiences with the IBM OS/390 Operating System, the Project Management challenges remain. This phenomenon exists despite the wide spread availability of well-developed Project Management techniques such as the Critical Path Method (CPM) and the Project Evaluation and Review Technique (PERT). The challenges also transcend the introduction of ever more powerful programming tools and techniques such as structured programming, high-level languages, source-level debuggers, and object-oriented programming. As in many industries, a key challenge in the Software industry is the reliable delivery of products in an environment of ever decreasing product cycle times. Recent work by Eliyahu M. Goldratt suggests that the struggle with on-time delivery may well lie with the underlying Project Management techniques that have become so widely accepted. These techniques foster behavior patterns that are counter-productive to the shortening of product cycle times. They fail to focus the organization on the Project Management system at large and can encourage dysfunctional decision making [l ]. Work in the field of System Dynamics has independently reached similar conclusions. The traditional Project Management techniques offer little to help the Project Manager cope with issues at the strategic level. Without strategic guidance, the Project Manager is left to make poor, informal judgments and may not make adequate allowances for factors that negatively impact project performance [2]. Goldratt offers a new, alternative project scheduling approach called Critical Chain as a mechanism for improving an organization's underlying Project Management structure. Critical Chain is based on principles developed a decade earlier in Goldratt's Theory of Constraints. The Theory of Constraints changed the way organizations think about Manufacturing processes. Likewise, Critical Chain requires that organizations reformulate their approach to managing development projects. This thesis will study the successful results of applying Critical Chain on two actual Software Development projects in IBM's System 390 Division. Each of these projects achieved commitments on time. Critical Chain's contribution to these results will be discussed. The experiences gained along with potential pitfalls of Critical Chain will also be considered. In particular, the issues involved with applying this approach to a Software Development environment in which traditional methods are in widespread use will be emphasized. A discussion of the potential limitations of the Critical Chain approach will also be provided.
by Theodore R. Maeurer.
S.M.
40
Sutharshan, Anuradha. "Human factors and cultural influences in implementing agile philosophy and agility in global software development." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 2013. https://ro.ecu.edu.au/theses/587.
Full textAbstract:
As software becomes increasingly important to all aspects of industry, developers should be encouraged to adopt best practice and hence improve the quality of the processes used, and achieve targets relating to time, budget and quality. In the software industry, several software methodologies have been used to address software development problems; however some of these processes may be too bureaucratic. The Agile Alliance formed in 2001, sought to address this problem; accordingly, they developed a manifesto and twelve principles, to which all agile software methods adhere. The purpose of the manifesto and its principles is to uncover better ways of developing software.
Agile software development methods seem to address the software development industry’s need for more agile processes that are responsive to changes during software development. Agile values and principles require a major cultural change for software managers, e.g. collective team responsibility and self-organisation, especially in large organisations with a strong culture of planning and centralised power. In large global organisations, this issue is likely to be exacerbated by cultural diversity. The objective of this thesis is to analyse the possibility, of using agile methods or practices in different cultures, and study what changes are required, to adapt agile approaches to different global application development issues. The study found that certain agile practices can be useful in different cultures and some practices required major cultural adaptation. A study of suitable practices for different cultures such as Australia, India and the United Kingdom and the associated suggested changes required are the main areas of study.
Human factors have been identified by researchers and practitioners to impact on software development projects. Similarly, cultural differences may also be influential in a global market. The principles of agile software development focus on iterative adaptation and improvement of the activities of individual software development teams to increase effectiveness. This research programme focused specifically on national culture based on Hofstede’s cultural dimensions, Hall’s cultural dimensions and the relationships between different aspects of national culture and the implementation of agile methods. To investigate this aspect of software development, a set of cultural dimensions and consolidated cultural agile attributes were developed, that are considered necessary for implementing agile methods. Based on relevancy, cultural dimensions such as Individualism/Collectivism, Power distance index, Uncertainty avoidance index, Time and Context were selected and studied. Some of cultural agile attributes studied include Transparency, Dedicated team, Decision making, Tolerance for change, Time keeping and Authoritative. This set was identified from a literature review on culture for agile methods, a detailed analysis of relevant commonly used agile methods and from feedback from agile experts. This thesis involves qualitative interviews conducted in Australia, India, and the UK using an interpretive paradigm and aims to identify cultural dimensions to implement agile methods in the software engineering community.
The results of this research programme provide an analytical comparative framework for implementing agile methods in different cultures, and insight into how cultural differences may affect a software project and how these challenges can be addressed through agile principles.
41
Schtein, Igor A. "Management Strategies for Adopting Agile Methods of Software Development in Distributed Teams." ScholarWorks, 2018. https://scholarworks.waldenu.edu/dissertations/5417.
Full textAbstract:
Between 2003 and 2015, more than 61% of U.S. software development teams failed to satisfy project requirements, budgets, or timelines. Failed projects cost the software industry an estimated 60 billion dollars. Lost opportunities and misused resources are often the result of software development leaders failing to implement appropriate methods for managing software projects. The purpose of this qualitative multiple case study was to explore strategies software development managers use in adopting Agile methodology in the context of distributed teams. The tenets of Agile approach are individual interaction over tools, working software over documentation, and collaboration over a contract. The conceptual framework for the study was adapting Agile development methodologies. The targeted population was software development managers of U.S.-based companies located in Northern California who had successfully adopted Agile methods for distributed teams. Data were collected through face-to-face interviews with 5 managers and a review of project-tracking documentation and tools. Data analysis included inductive coding of transcribed interviews and evaluation of secondary data to identify themes through methodological triangulation. Findings indicated that coaching and training of teams, incremental implementation of Agile processes, and proactive management of communication effectiveness are effective strategies for adopting Agile methodology in the context of distributed teams. Improving the efficacy of Agile adoption may translate to increased financial stability for software engineers across the world as well as accelerate the successful development of information systems, thereby enriching human lives.
42
Carlshamre, Pär. "A usability perspective on requirements engineering : from methodology to product development." Doctoral thesis, Linköpings universitet, MDALAB - Human Computer Interfaces, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-4976.
Full textAbstract:
Usability is one of the most important aspects of software. A multitude of methods and techniques intended to support the development of usable systems has been provided, but the impact on industrial software development has been limited. One of the reasons for this limited success is the gap between traditional academic theory generation and commercial practice. Another reason is the gap between usability engineering and established requirements engineering practice. This thesis is based on empirical research and puts a usability focus on three important aspects of requirements engineering: elicitation, specification and release planning. There are two main themes of investigation. The first is concerned with the development and introduction of a usability-oriented method for elicitation and specification of requirements, with an explicit focus on utilizing the skills of technical communicators. This longitudinal, qualitative study, performed in an industrial setting in the first half of the nineties, provides ample evidence in favor of a closer collaboration between technical communicators and system developers. It also provides support for the benefits of a task-oriented approach to requirements elicitation. The results are also reflected upon in a retrospective paper, and the experiences point in the direction of an increased focus on the specification part, in order to bridge the gap between usability engineering and established requirements management practice. The second represents a usability-oriented approach to understanding and supporting release planning in software product development. Release planning is an increasingly important part of requirements engineering, and it is complicated by intricate dependencies between requirements. A survey performed at five different companies gave an understanding of the nature and frequency of these interdependencies. This knowledge was then turned into the design and implementation of a support tool, with the purpose of provoking a deeper understanding of the release planning task. This was done through a series of cooperative evaluation sessions with release planning experts. The results indicate that, although the tool was considered useful by the experts, the initial understanding of the task was overly simplistic. As a result, a number of design implications are proposed.On the day of the public defence the status of article VI was: Submitted.
43
Mittner, Jan. "Metodika pro vývoj webových aplikací." Master's thesis, Vysoká škola ekonomická v Praze, 2009. http://www.nusl.cz/ntk/nusl-76276.
Full textAbstract:
This work deals with methodologies of software development, particularly web applications. Its main objective is to propose a methodology that helps ensure quality web development and prevents a number of frequently recurring problems. The first chapter deals with characteristics of current state and defines the need for process and discipline, the need for team development and the importance of appropriate tools. The second chapter describes the specifics of the web development. It defines the quality criteria in relation to web applications, particularly the aspects of accessibility, usability and security are concerned. It deals with web frameworks and the benefits and risks arising from their usage. It also outlines requirements for the chosen methodology for web development and describes types of projects to be applied to the methodology. The third chapter analyzes the suitability of the selected life cycle models and methodologies in software development for web applications. The life cycle models consider a model of "program and repair", the waterfall model and incremental model. It also deals with the assumptions of agile methodologies and their level of satisfaction for web development. For the analysis is used the methodology evaluation system METES with which is examined Rational Unified Process, Open Unified Process, Extreme Programming, Scrum and Feature Driven Development. The fourth chapter deals with the characteristic of Open Unified Process methodology. It describes the principles, features and development process. The main chapter deals with the proposal of methodology for web development. As the basis is chosen Open Unified Process methodology, whose elements are supplemented and adapted for web development. As the elements of the methodology are elaborated principles, practices, roles, work products, tasks, delivery process, manuals and guidelines and tools. Each element is adapted to fit the specific needs of web applications. In order to achieve greater control over the quality of web applications there are also included detailed checklists as an integral part of products which are aimed at preventing the most frequently occurring errors and problems. The chapter concludes with an overview of tools that have been validated in web development.
44
Aslan, Serdar. "Digital Educational Games: Methodologies for Development and Software Quality." Diss., Virginia Tech, 2016. http://hdl.handle.net/10919/73368.
Full textAbstract:
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.
45
Erharuyi, Edison. "Combining eXtreme Programming with ISO 9000:2000 to Improve Nigerian Software Development Processes." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5616.
Full textAbstract:
The aim of this research work is to study how eXtreme programming could be combined with ISO 9000:2000 standards to improve Nigerian software development processes. The combination of these models will enable organizations take advantage of models strengths and compensate for their weaknesses in enhancing continuous software process improvement and rapidly responding customer’s changing needs. This was achieved by adopting a model in balancing ISO and eXtreme programming in software projects. This allows organization to determine whether to choose a pure method (eXtreme programming or ISO) or mixed methods (eXtreme programming and ISO) that will be most successful in executing software projects. Also developed was another strategy in modifying eXtreme programming practices to reflect ISO 9001:2000 standard requirements.The aim of this research work is to study how eXtreme programming could be combined with ISO 9000:2000 standards to improve Nigerian software development processes
C/o Patrick O. Nordkapsgatan 8,Kista, 164 36, Stockholm Tel:+46-704214035, e- mail address: edisonerhas@yahoo.com
46
Ozercan, Sertac. "Adapting Feature-Driven Software Development Methodology to Design and Develop Educational Games in 3-D Virtual Worlds." Ohio University / OhioLINK, 2010. http://rave.ohiolink.edu/etdc/view?acc_num=ohiou1271449120.
Full text
47
Mikula, Jan. "Návrh metodiky vývoje softwaru se zaměřením na oblast UX." Master's thesis, Vysoká škola ekonomická v Praze, 2013. http://www.nusl.cz/ntk/nusl-197005.
Full textAbstract:
The main objective of this work is to propose a software development methodology which will reflect both issues -- design of User Experience (UX) and its implementation. The second objective is to compare the current software development methodologies. The third objective is to describe the work environment and the principles of that environment to fully implement this methodology. The fourth objective is to test the methodology in practice and validate its performance on my own startup. The fifth objective is to analyze companies which are focusing on similar product as my startup and their approach to UX development. First I will take look at waterfall methodology and then at modern agile methodologies such as Scrum, Kanban and Lean management, which are now becoming standard in software development. I will describe issues with the integration of UX into software development. The next section will introduce my own methodology, which is based on Scrum. The methodology consists of general principles of Lean and Agile management and the management, which is sometimes called "freedom at work". Then I will use the proposed methodology on my own startup project and will evaluate its use in practice. In last part I will analyze development process with focus on UX in projects Medium and Facebook. Thesis combines knowledge from Lean and agile management, economy and cognitive science to show the way to succeed in today services with great UX.
48
Warrington, Andrew David. "The development of an implementation methodology for computer aided production management in small, make-to-order manufacturing businesses." Thesis, Leeds Beckett University, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.387811.
Full text
49
Varanasi, Panchajanya. "A Perspective of Leadership Requirement in Scrum Based Software Development - A Case Study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17793.
Full textAbstract:
Context. Software Development has been witnessing great innovations over past few years with good number of technologies, tools and practices invading the industry. Client demands and collaboration in the development process are also seen increasing. So many new practices and methodologies are coming up and Agile is one of prominent practices adopted by many. Even in Agile, Scrum methodology is picking up more demand presently. As Software Development process and practices are changing so are the leadership styles in the same. Leadership is critical for success of any team. This study intended to explore this model and requirement of leadership in Scrum based Software Development in a practical scenario. Objectives. Leadership, which is essential in any Software project, differs from Traditional Methodology to Scrum Methodology of Agile practices in Software Development. Through a case study, the author attempted to investigate and explore the perspective of Leadership requirement in Scrum based Software Development in a practical scenario. The study aimed to gather and analyze the Leadership model implemented in two domestic projects in an Indian company, involved in two distinctive domains, and sum up the impressions gained in the same. The study aimed to assess whether the gathered knowledge adds up to the existing body of knowledge on the phenomenon or on the contrary whether any suggestions for improvement can be given to the case units. Methods. Case Study method was chosen for undertaking this explorative study. A literature review was conducted prior to the case study to gain knowledge on the phenomenon, which also answered one of the Research Questions and helped partially the other. A multiple case study was conducted through semi structured personal interviews, tools analysis and direct observation in the case units. Qualitative data analysis was made using Grounded Theory on this three orders of collected data. The results were compared with the Literature and conformity or variance analyzed. This comparative analysis is used for making recommendations to the case units for improvement or for additions to the existing body of knowledge. Results. Through the results of Literature Review, Leadership models in Software Development including Agile Scrum were summed up. And through the results of the case study, the leadership models and features implemented in the case units have been identified. These results are further validated and contrasted with the results of the literature review. How the literature models and the case unit models of leadership differed is studied. The justification for the implemented leadership model in the practical situation is also analyzed. Following, a review of the models employed at the case environments, the perspective of leadership in the two Scrum based Software Development projects is summed up. At the end, it is assessed what effect the case study would have on the existing body of knowledge on the phenomenon and modifications that can be proposed to the case units based on the results and analysis. Conclusion. It is concluded that the Case Units are implementing Situational Leadership and Transformational Leadership in a mixed way. Telling and Selling models in Situational Leadership are prominent while Participating and Delegating are ranking less. Some of the important features of Transformational Leadership like Self Management, Organizational Consciousness, Adaptability and Proactive are in implementation but not all features of the model are assumed. Even Scrum is implemented in a modified way, extending only controlled autonomy with higher monitoring and it had a direct effect on the leadership. On the whole it is directive leadership that is in play with co-existence of collaborative one situationally.
50
Hollar, Ashby Brooks. "Cowboy : an agile programming methodology for a solo programmer /." VCU Scholars Compass, 2006. http://hdl.handle.net/10156/1400.
Full text