Dissertations / Theses on the topic 'Software engineering'
To see the other types of publications on this topic, follow the link: Software engineering.
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 engineering.'
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
Le, Gal Thierry. "Re-engineering software for integration using computer aided software engineering." Thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-06232009-063016/.
2
CHRISTOPH, ROBERTO DE HOLANDA. "SOFTWARE ENGINEERING FOR OPEN SOURCE SOFTWARE." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2004. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=4854@1.
Abstract:
Software livres têm despertado bastante atenção, não apenas
devido a popularidade obtida por alguns destes como o Linux
e o Apache, mas também pela forma singular como estes
sistemas são desenvolvidos e sua quantidade de
adeptos. No entanto, em alguns projetos de software livre,
a documentação existente dificulta a entrada de novos
participantes, já que devido a informalidade do
processo de desenvolvimento deste tipo de software, é comum
que a documentação do sistema não receba muita atenção.
Este trabalho colabora para um melhor entendimento do
desenvolvimento de software livres, relacionando-o com as
questões de evolução de software. Será apresentada uma
proposta utilizada no software livre C e L para documentar em
termos da aplicação o código do sistema, utilizando-se do
conceito de cenários. Será mostrado através de um protótipo
que um software seguindo esse padrão proposto pode produzir
uma documentação que torna mais fácil seu entendimento
para novos participantes do projeto.This thesis presents an introduction on the use of the thermal desorption technique that is based on the direct heating of the soil, for the remediation of contaminated areas. Heat propagation through soils can be mathematically simulated using coupled heat-moisture transfer theories. In order to make this simulation possible it is necessary to identify the required parameters: hydraulic conductivity as a function of volumetric water content, thermal conductivity as a function of volumetric water content, volumetric heat capacity, and soil-water characteristic curve. One technical description of such parameters is presented. Two different kinds of soils were used, one clay- sand (CH) and one sandclay (SC). A study physico-chemical was done talking into consideration the temperature effect on the soils with X-Ray, electron microscopic investigation, CTC, Atterberg Limits and at the particle size distribution. The study was done on pre-heated soils with temperatures ranging from 20 Celsius Degrees to 300 Celsius Degrees. Equipments and methodologies have been especially developed for the study of the thermo-hydraulics proprieties. The laboratory tests program consisted of hydraulic conductivity, retention curves and deformability, taking into account the temperature effects. During the tests it was observed that all parameters were temperature dependent. The thermal parameters, thermal conductivity and heat capacity were studied for both soils.
3
Bondesson, Tobias. "Software Engineering Education Improvement : An Assessment of a Software Engineering Programme." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5891.
Abstract:
An assessment of a software engineering program has been carried out by reviewing state-of-the-art literature pertaining to software engineering education. Six surveys have been adopted and the result implies that the balance of the curriculum should be revised, and that software engineering education ought to expand the technical oriented knowledge areas somewhat. Relevant curriculum data have been derived hereby, which also confirms other studies in the area. This data, along with a benchmark of the software engineering program to the Software Engineering Body of Knowledge (SWEBOK), is very constructive to universities as it assists educators, trainers, and software engineering practitioners in evaluating, designing, and recommending existing and proposed curricula.This is the final revision of the thesis. Author may be contacted on +464458038. See also paper at the 18th Conference on Software Engineering Education and Training (CSEE&T), Ottawa, Canada.
4
Riehle, Richard D. "An engineering context for software engineering." Monterey, Calif. : Naval Postgraduate School, 2008. http://edocs.nps.edu/npspubs/scholarly/theses/2008/Sept/08Sep%5FRiehle%5FPhD.pdf.
Abstract:
Dissertation (Ph.D. in Software Engineering)--Naval Postgraduate School, September 2008.Dissertation Supervisor(s): Michael, J. Bret. "September 2008." Description based on title screen as viewed on November 4, 2008. Includes bibliographical references (p. 111-120). Also available in print.
5
Lim, Edwin C. "Software metrics for monitoring software engineering projects." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 1994. https://ro.ecu.edu.au/theses/1100.
Abstract:
As part of the undergraduate course offered by Edith Cowan University, the Department of Computer Science has (as part of a year's study) a software engineering group project. The structure of this project was divided into two units, Software Engineering l and Software Engineering 2. ln Software Engineering 1, students were given the group project where they had to complete and submit the Functional Requirement and Detail System Design documentation. In Software Engineering 2, students commenced with the implementation of the software, testing and documentation. The software was then submitted for assessment and presented to the client. To aid the students with the development of the software, the department had adopted EXECOM's APT methodology as its standard guideline. Furthermore, the students were divided into groups of 4 to 5, each group working on the same problem. A staff adviser was assigned to each project group. The purpose of this research exercise was to fulfil two objectives. The first objective was to ascertain whether there is a need to improve the final year software engineering project for future students by enhancing any aspect that may be regarded as deficient. The second objective was to ascertain the factors that have the most impact on the quality of the delivered software. The quality of the delivered software was measured using a variety of software metrics. Measurement of software has mostly been ignored until recently or used without true understanding of its purpose. A subsidiary objective was to gain an understanding of the worth of software measurement in the student environment One of the conclusions derived from the study suggests that teams who spent more time on software design and testing, tended to produce better quality software with less defects. The study also showed that adherence to the APT methodology led to the project being on schedule and general team satisfaction with the project management. One of the recommendations made to the project co-ordinator was that staff advisers should have sufficient knowledge of the software engineering process.
6
Sezer, Bulent. "Software Engineering Process Improvement." Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12608338/index.pdf.
Abstract:
This thesis presents a software engineering process improvement study. The literature on software process improvement is reviewed. Then the current design verification process at one of the Software Engineering Departments of
the X Company, Ankara, Türkiye (SED) is analyzed. Static software development process metrics have been calculated for the SED based on a recently proposed approach. Some improvement suggestions have been made based on the metric values calculated according to the proposals of that study. Besides, the author'
s improvement suggestions have been discussed with the senior staff at the department and then final version of the improvements has been gathered. Then, a discussion has been made comparing these two approaches. Finally, a new software design verification process model has been proposed. Some of the suggestions have already been applied and preliminary results have been obtained.
7
Boriani, Dario V. "Software engineering for control." Thesis, University of Oxford, 1989. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.253293.
8
Arciniegas-Mendez, Maryi. "Regulation in Software Engineering." Thesis, Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering, 2015. http://hdl.handle.net/1828/7524.
Abstract:
Collaboration has become an integral part of software engineering. The widespread availability and adoption of social channels has led to a culture where developers participate and collaborate more frequently with one another. While collaboration in software engineering has been studied extensively, models and frameworks do not adequately capture how development team members “regulate” themselves, one another, and their projects. I borrow the term “regulate” from the learning sciences to refer to mindful processes developers engage in to determine what tasks they need to complete and who should be involved, what their goals are relative to those tasks, how they should meet their goals, what domain knowledge needs to be manipulated, and why they use a particular approach or tool.
This research starts by borrowing constructs from the theory of regulated learning in the learning science domain, adapting and extending them as a model of collaboration for software engineering: the Model of Regulation. This model was composed to capture how individuals self-regulate their tasks, knowledge and motivation, how they regulate one another, and how they achieve a shared understanding of project goals and required tasks. The model provides a vocabulary for comparing and analyzing collaboration tools and processes. In this thesis, I present the Model of Regulation as a new and complementary theoretical model of collaboration for software engineering and showcase its potential by using the model to analyze features of a collaborative tool, gain insights into an open-source software development community and to create an instrument that investigates about collaboration practices and tool support in units of collaboration (e.g., group, project, community).Graduate
9
Loomes, Martin James. "Software engineering curriculum design." Thesis, University of Surrey, 1991. http://epubs.surrey.ac.uk/844417/.
Abstract:
Software engineering design is a vital component of modern industry, unfortunately, the processes involved are still poorly understood. This poses a major problem for teachers of the subject, who are under constant pressure to improve the quality of education, but are unsure how to bring this about, or even how to detect such improvement. This thesis attempts to start the process of clarifying what we mean by "software engineering design", and apply the insights gained to the activity of curriculum design. First, we establish a method for the research, by constructing a framework to constrain and guide the process of seeking new insights. This leads to a decidedly eclectic approach to the problem, as software engineering design is viewed, and reviewed, from a number of different perspectives. Next, these views are synthesised into a model of the software engineering design process, and new insights are sought to refine the model. The central theme of this model is the idea that the design process can be considered as a one of theory building. Finally, we bring this model into direct contact with the task of curriculum design, both in a general sense, and also by providing illustrations of some of the consequences of its use.
10
Alrabghi, Leenah O. "QFD IN SOFTWARE ENGINEERING." Kent State University / OhioLINK, 2014. http://rave.ohiolink.edu/etdc/view?acc_num=kent1385046526.
11
Zamli, Kamal Zuhairi. "Supporting software processes for distributed software engineering teams." Thesis, University of Newcastle Upon Tyne, 2003. http://hdl.handle.net/10443/2118.
Abstract:
Software processes relate to the sequence of steps that must be carried out by humans to pursue the goals of software engineering. In order to have an accurate representation of what these steps actually are, software processes can be modelled using a process modeling language (PML). Some PMLs simply support the specification of the steps, while others enable the process to be executed (or enacted). When enacted, software processes can provide guidance, automation and enforcement of the software engineering practices that are embodied in the model. Although there has been much fruitful research into PMLs, their adoption by industry has not been widespread. While the reasons for this lack of success may be many and varied, this thesis identified two areas in which PMLs may have been deficient: human dimension issues in terms of support for awareness and visualisation; and support for addressing management and resource issues that might arise dynamically when a process model is being enacted. In order to address some of these issues, a new visual PML called Virtual Reality Process Modelling Language (VRPML) has been developed and evaluated. Novel features have been introduced in VRPML to include support for the integration of a virtual environment, and dynamic creation and assignment of tasks and resources at the PML enactment level. VRPML serves as a research vehicle for addressing our main research hypothesis that a PML, which exploits a virtual environment, is useful to support software processes for distributed software engineering teams.
12
Karvonen, T. (Teemu). "Continuous software engineering in the development of software-intensive products:towards a reference model for continuous software engineering." Doctoral thesis, Oulun yliopisto, 2017. http://urn.fi/urn:isbn:9789526216560.
Abstract:
Abstract Continuous software engineering (CSE) has instigated academic debate regarding the rapid, parallel cycles of releasing software and customer experimentation. This approach, originating from Web 2.0 and the software-as-a-service domain, is widely recognised among software-intensive companies today. Earlier studies have indicated some challenges in the use of CSE, especially in the context of business-to-business and product-oriented, embedded systems development. Consequently, research must address more explicit definitions and theoretical models for analysing the prerequisites and organisational capabilities related to the use of CSE. This dissertation investigates various approaches to conducting empirical evaluations related to CSE. The study aims to improve existing models of CSE and to empirically validate them in the context of software companies. The study also aims to accumulate knowledge regarding the use of CSE, as well as its impacts. The case study method is applied for the collection and analysis of empirical data. Twenty-seven interviews are conducted at five companies. In addition, a systematic literature review is used to synthesise the empirical research on agile release engineering practices. Design science research is used to portray the model design and the evaluation process of this dissertation. Three approaches for evaluating CSE are constructed: (1) LESAT for software focuses on enterprise transformation using an organisational self-assessment approach, (2) STH+ extends the “Stairway to Heaven” model and evaluates company practices with respect to evolutionary steps towards continuous experimentation-driven development, and (3) CRUSOE defines 7 key areas and 14 diagnostic questions related to the product-intensive software development ecosystem, strategy, architecture, and organisation, as well as their continuous interdependencies. This dissertation states the relevance of CSE in the context of product-intensive software development. However, more adaptations are anticipated in practices that involve business and product development stakeholders, as well as company external stakeholdersTiivistelmä Jatkuva ohjelmistotuotanto on herättänyt keskustelua nopeasta, samanaikaisesta ohjelmistojulkaisemisesta ja asiakaskokeiluista. Toimintatapa on peräisin Web 2.0 ja software-as-a-service yhteydestä, mutta se tunnetaan nykyään yleisesti ohjelmistoja kehittävissä yrityksissä. Aiemmat tutkimukset ovat osoittaneet haasteita jatkuvan ohjelmistotuotannon käytössä. Erityisesti haasteita on havaittu yritykseltä yritykselle liiketoiminnassa ja tuotepainotteisten sulautettujen järjestelmien yhteydessä. Näin ollen on havaittu tarve tutkimuksen avulla kehittää täsmällisempiä määritelmiä ja teoreettisia malleja, joilla voidaan analysoida jatkuvan ohjelmistotuotannon käyttöön liittyviä edellytyksiä ja organisaatioiden kyvykkyyksiä. Tässä väitöskirjassa tutkitaan malleja, joilla voidaan empiirisesti arvioida jatkuvaa ohjelmistotuotantoa. Tutkimuksella pyritään parantamaan nykyisiä malleja ja arvioimaan niiden käyttöä ohjelmistoyrityksissä. Lisäksi tutkimuksella pyritään kasvattamaan tietoa jatkuvasta ohjelmistotuotannosta ja sen vaikutuksista. Tiedon keräämiseen ja analysointiin käytettiin tapaustutkimus menetelmää. Kaksikymmentäseitsemän haastattelua tehtiin viidessä yrityksessä. Lisäksi tehtiin ketterään ohjelmistojulkaisuun keskittyvä systemaattinen kirjallisuuskatsaus. Väitöskirjassa käytetään Design Science Research menetelmää kuvaamaan tutkimuksen eri vaiheita, joissa malleja suunniteltiin ja arvioitiin. Tutkimuksessa rakennettiin kolme tapaa jatkuvan ohjelmistotuotannon arvioimista varten: (1) LESAT for Software keskittyy organisaation muutoskyvykkyyden arviointiin käyttäen itsearviointimenetelmää, (2) STH+, laajentaa ”Stairway to Heaven” mallia ja arvioi yrityksen käytäntöjä eri evoluutioaskelmilla matkalla kohti kokeilupainotteista tuotekehitystä, (3) CRUSOE määrittelee seitsemän pääaluetta ja 14 kysymystä liittyen tuotekehityksen ekosysteemiin, strategiaan, arkkitehtuuriin, organisointiin sekä näiden välisiin jatkuviin riippuvuuksiin. Väitöskirja osoittaa jatkuvan ohjelmistokehityksen olevan merkityksellinen myös tuotepainotteisessa ohjelmistokehityksessä. Nähtävissä kuitenkin on, että useita nykykäytäntöjä on tarvetta muokata. Erityisesti muokkaustarvetta on tuotekehityksen ja liiketoiminnan sidosryhmiin ja yrityksen ulkoisiin sidosryhmiin liittyvissä käytännöissä
13
Pawar, Sourabh A. "A Common Software Development Framework For Coordinating Usability Engineering and Software Engineering Activities." Thesis, Virginia Tech, 2004. http://hdl.handle.net/10919/33023.
Abstract:
Currently, the Usability Engineering (UE) and Software Engineering (SE) processes are practiced as being independent of each other. However, several dependencies and constraints exist between the interface specifications and the functional core, which make coordination between the UE and the SE teams crucial. Failure of coordination between the UE and SE teams leads to software that often lacks necessary functionality and impedes user performance. At the same time, the UE and SE processes cannot be integrated because of the differences in focus, techniques, and terminology. We therefore propose a development framework that incorporates SE and UE efforts to guide current software development.
The framework characterizes the information exchange that must exist between the UE and SE teams during software development to form the basis of the coordinated development framework. The UE Scenario-Based Design (SBD) process provides the basis for identifying UE activities. Similarly, the Requirements Generation Model (RGM), and Structured Analysis and Design are used to identify SE activities. We identify UE and SE activities that can influence each other, and identify the high-level exchange of information that must exist among these activities. We further examine these interactions to gain a more in-depth understanding as to the precise exchange of information that must exist among them.
The identification of interacting activities forms the basis of a coordinated development framework that incorporates and synchronizes the UE and SE processes. An examination of the Incremental and Spiral models as they relate to the SBD is provided, and outlines how our integration framework can be composed. Using the results of and insights gained from our research, we also suggest additional avenues for future work.
Master of Science
14
Hanssen, Geir Kjetil. "From Agile Software Product Line Engineering Towards Software Ecosystems." Doctoral thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2010. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-11890.
Abstract:
Development and evolution of software products is a challenging endeavor and a significant subfield of software engineering. One of the commonly applied approaches to control and manage this process is software product line engineering (SPLE). There exist a few process frameworks where the development of lines of related software products is basically a sum of two processes: the development of reusable assets and the rapid construction of software applications using predeveloped assets. Agile software development (ASD) is another major paradigm, which also has been widely adopted by the industry over the past decade. SPLE and ASD seek to achieve the same goal i.e. rapid and efficient construction of software. However, the former emphasizes extensive up-front investment in the development of assets for later re-use in contrast to ASD, which emphasizes a reactive approach, avoiding up-front planning and development Even though these two approaches may seem to oppose each other, the industry has lately showed great interest in combining them both, aiming to cover the weaknesses of the one with the strengths of the other. In combination with the overall shift in the software industry from closed systems mindset towards open systems, the uptake of some ASD principles (for example active customer engagement, incremental and iterative development, and open information flows) in product line organizations may contribute to the emergence of more flexible software ecosystems. This thesis presents a longitudinal study of a software product line organization, which has adopted an adapted ASD methodology in an SPLE context and to a large extent has successful in gaining benefits from both approaches, developing towards more open yet controlled processes. Data have been collected over a period of approximately five years following the progression from a strictly waterfall oriented approach, via the adoption of the agile method Evo, up to the current combined agile software product line engineering approach. The following research questions have been addressed in this thesis: RQ1: How can software product line engineering and agile software development be combined? RQ2: How does a software ecosystem shape? The main contributions of this work are: C 1. Through a longitudinal study of a software product line organization we provide detailed insight into an industrial case and how they have changed over time. C 2. We have illustrated some of the details of how SPLE and ASD can be combined in practical terms. We describe the current organization, their product line and their agile software product line engineering process. C 3. We have illustrated how the incorporation of some of the central agile principles has enabled a closer cooperation with external actors. C 4. We have explained the emergence and mode of operation of a software ecosystem, and provided a conceptual model of software ecosystems based on our findings. C 5. We have proposed a theory of software ecosystems, rooted in socio-technical theory and the concept of organizational ecology.
15
OLIVEIRA, GLORIA MARIA DE PAULA. "USING SOFTWARE ENGINEERING CONCEPTS TO DEFINE SOFTWARE DEVELOPMENT PROCESSES." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2007. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=12112@1.
Abstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIROA qualidade de um produto de software depende fortemente da qualidade do processo de software utilizado em seu desenvolvimento. Para auxiliar na definição de um processo de qualidade, existem diversos modelos de processo, modelos de maturidade e normas de qualidade. Entretanto, a tarefa de elaborar ou melhorar o processo de desenvolvimento de sistemas pode se tornar árdua devido à grande quantidade de informações disponíveis e decisões a serem tomadas. Outro grande problema é o risco de definição de um processo que não seja eficaz, ou seja, não melhore a qualidade dos sistemas ou somente aumente a burocracia no desenvolvimento. Esta dissertação apresenta uma abordagem para definição de processos de desenvolvimento de sistemas baseada nos conceitos da análise de sistemas, ressaltando a analogia existente entre a elaboração de um processo e de um software. Uma das principais características da abordagem é o enfoque na área de Gerência de Riscos, visando o controle dos riscos identificados na definição do processo bem como os possíveis riscos na execução do processo de desenvolvimento.
Software quality depends heavily on the quality of the process used to develop it. In order to assist the definition of an adequate process, there are several process models, maturity models and quality standards. However, creating or improving a software development process may be tough due to the large amount of available information and decisions that have to be made. Another central problem is the risk of defining an ineffective process, that is, one that increases the bureaucracy but doesn`t improve the quality of the systems developed with its support. This dissertation presents an approach for defining software development processes based on the concepts of system analysis, based on the analogy between software and process elaboration. One of the most important attributes of this approach is the focus on Risk Management, considering the identified risks in the process definition as well the possible risks during software process execution.
16
Ahmad, M. O. (Muhammad Ovais). "Exploring Kanban in software engineering." Doctoral thesis, Oulun yliopisto, 2016. http://urn.fi/urn:isbn:9789526214085.
Abstract:
Abstract To gain competitive advantage and thrive in the market, companies have introduced Kanban in software development. Kanban has been used in the manufacturing industry for over six decades. In the software engineering domain, Kanban was introduced in 2004 to increase flexibility in coping with dynamic requirements, bring visibility to workflow and related tasks, improve communication, and promote the pull system. However, the existing scientific literature lacks empirical evidence of the use of Kanban in software companies. This doctoral thesis aims to improve the understanding of the use of Kanban in software engineering. The research was performed in two phases: 1) analysis of scientific literature on Kanban in software engineering and industrial engineering and 2) investigation of Kanban implementation trends in software companies. The data was collected through systematic literature reviews, survey and semi-structured interviews. The results were synthesized to draw conclusions and outline implications for research and practice. The results indicate growing interest in the use of Kanban in software companies. The findings suggest that Kanban is applicable to software development, software maintenance, and portfolio management in software companies. Kanban brings visibility to task and offering status, limits work in progress at any given time gives people greater control over their work and limit task switching. Although Kanban offers several benefits, as reported in this dissertation, the findings show that software companies find it challenging to implement Kanban incrementallyTiivistelmä Ohjelmistoteollisuudessa Kanbanin käyttö on yleistynyt vuodesta 2004 alkaen. Sillä pyritään tuomaan joustavuutta muuttuvien vaatimusten hallintaan, tuomaan näkyvyyttä työnkulkuun ja toisiinsa liittyviin tehtäviin, parantamaan kommunikaatiota sekä edistämään imuohjauksen hyödyntämistä. Kanbania on käytetty valmistavassa teollisuudessa jo yli kuuden vuosikymmenen ajan. Olemassa olevassa tieteellisessä kirjallisuudessa on kuitenkin esitetty hyvin vähän empiirisiä tutkimustuloksia Kanbanin käytöstä ohjelmistoyrityksissä. Väitöskirjan tavoitteena on parantaa ymmärrystä Kanbanin käytöstä ohjelmistotuotannossa. Tutkimus toteutettiin kahdessa vaiheessa: 1) Kirjallisuusanalyysi Kanbanin käytöstä ohjelmistotuotannossa ja tuotantotekniikassa ja 2) Empiirinen tutkimus Kanbanin käyttöönoton trendeistä ohjelmistoyrityksissä. Tutkimusaineisto kerättiin systemaattisten kirjallisuuskatsausten, kyselytutkimuksen ja puolistrukturoitujen teemahaastattelujen kautta. Tutkimustulosten synteesin pohjalta tehtiin johtopäätöksiä Kanbanin käytöstä ohjelmistotuotannossa sekä niiden merkityksestä alan tutkimukselle ja Kanbanin käytölle yrityksissä. Tutkimuksen tulokset osoittavat kasvavaa kiinnostusta Kanbanin käyttöä kohtaan ohjelmistoyrityksissä. Tulosten perusteella Kanban soveltuu käytettäväksi ohjelmistokehityksessä, ohjelmistojen ylläpidossa sekä tuoteportfolion hallinnassa. Kanban tuo näkyvyyttä ohjelmistokehitykseen, niin meneillään olevien tehtävien kuin portfoliotarjoaman osalta. Se myös auttaa rajoittamaan työtehtävien ruuhkautumista ja antaa kehittäjille paremman tavan hallita työtään rajoittamalla työtehtävien vaihtoa. Vaikka Kanbanin käytöllä on mahdollista saavuttaa väitöskirjatutkimuksessa esitettyjä hyötyjä, tulokset osoittavat, että ohjelmistoyrityksillä on haasteita Kanbanin inkrementaalisessa käyttöönotossa
17
Chennamsetty, Harish. "Experimentation in Global Software Engineering." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5791.
Abstract:
Context: Software engineering researchers are guided by research principles to conduct any type of research. Though, there are many guidelines to detail how a particular research method can be applied, there is always a necessity to continue and to improve the existing empirical research strategies. The context of this thesis is to address guidelines for conducting controlled experiments in Global Software Engineering (GSE). With this thesis, the state-of-the-art of conducting experiments in GSE research has been explored. Objectives: The goal of this thesis is to analyze the existing experiments in GSE research. Research problems addressed with GSE experiments and the state-of-the-art of overall GSE experiment design need to be analyzed. Appropriate guidelines should be drawn in order to provide strategies to future GSE researchers in mitigating or solving GSE specific experimentation challenges. Methods: A systematic literature review (SLR) is conducted to review all the GSE experiments that are found in the literature. The search process was done on 6 databases. A specific search and quality assessment criterion is used to select these GSE experiments. Furthermore, scientific interviews are conducted with GSE research experts to evaluate a set of guidelines (thesis author’s recommendations) that address the challenges when conducting GSE experiments. Thematic analysis has been performed to analyze the evaluation results and to further improve or implement any suggestions given by the interviewees. Conclusions: The results obtained from the SLR have provided a chance to understand the state-of-the-art and to analyze the challenges or problems when conducting controlled experiments in GSE. The challenges that are identified in GSE controlled experiments are found to be with experiment study-setting, involving subjects and addressing GSE relevant threats to validity in a GSE experiments. 9 guidelines are framed, with each guideline addressing a specific challenge. The final guidelines (that resulted after interviews) provide effective recommendations to GSE researchers when conducting controlled experiments.+919441308167
18
Masoud, F. A. "Quality metrics in software engineering." Thesis, University of Liverpool, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.381358.
Abstract:
In the first part of this study software metrics are classified into three categories: primitive, abstract and structured. A comparative and analytical study of metrics from these categories was performed to provide software developers, users and management with a correct and consistent evaluation of a representative sample of the software metrics available in the literature. This analysis and comparison was performed in an attempt to: assist the software developers, users and management in selecting suitable quality metric(s) for their specific software quality requirements and to examine various definitions used to calculate these metrics. In the second part of this study an approach towards attaining software quality is developed. This approach is intended to help all the people concerned with the evaluation of software quality in the earlier stages of software systems development. The approach developed is intended to be uniform, consistent, unambiguous and comprehensive and one which makes the concept of software quality more meaningful and visible. It will help the developers both to understand the concepts of software quality and to apply and control it according to the expectations of users, management, customers etc.. The clear definitions provided for the software quality terms should help to prevent misinterpretation, and the definitions will also serve as a touchstone against which new ideas can be tested.
19
Geyer-Schulz, Andreas, and Michael Hahsler. "Software engineering with analysis patterns." Institut für Informationsverarbeitung und Informationswirtschaft, WU Vienna University of Economics and Business, 2001. http://epub.wu.ac.at/592/1/document.pdf.
Abstract:
The purpose of this article is twofold, first to promote the use of patterns in the analysis phase of the software life-cycle by proposing an outline template for analysis patterns that strongly supports the whole analysis process from the requirements analysis to the analysis model and further on to its transformation into a flexible design. Second we present, as an example, a family of analysis patterns that deal with a series of pressing problems in cooperative work, collaborative information filtering and sharing, and knowledge management. We present the step-by-step evolution of the analysis pattern virtual library with active agents starting with a simple pinboard. In this paper we propose that using patterns in the analysis phase has the potential to reducing development time by introducing reuse already at the analysis stage and by improving the interface between analysis and design phase. To quantify our proposal we present results from the Virtual University project of the Vienna University of Economics and Business Administration, where the analysis patterns developed in this paper were used to implement several information systems. (author's abstract)Series: Working Papers on Information Systems, Information Business and Operations
20
Wang, Yingxu. "Software engineering process modelling analysis." Thesis, Southampton Solent University, 1998. http://ssudl.solent.ac.uk/2429/.
Abstract:
Studies of the software engineering process are a natural extension of scope from that of conventional software development methodologies meeting the requirement for engineering large-scale software development. A new approach for dealing with the difficulties of large-scale software development in software engineeering is to establish an appropriate software engineering process system. This work researches into software engineering process system modelling and analysis. The delivered aims of this thesis are to investigate empirical software engineering process research and practices to solve current problems identified in software engineering process system modelling, to integrate current process models into a well founded and unifying framework and to lay theoretical foundations for the software engineering process as a formalised discipline.
21
Cunningham, Hamish. "Software architecture for language engineering." Thesis, University of Sheffield, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.324440.
22
Gabriel, Pedro Hugo do Nascimento. "Software languages engineering: experimental evaluation." Master's thesis, Faculdade de Ciências e Tecnologia, 2010. http://hdl.handle.net/10362/4854.
Abstract:
Dissertação apresentada na Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa para obtenção do grau de Mestre em Engenharia InformáticaDomain-Specific Languages (DSLs) are programming languages that offer, through appropriate notation and abstraction, still enough an expressive control over a particular problem domain for more restricted use. They are expected to contribute with an enhancement of productivity, reliability, maintainability and portability, when compared with General Purpose Programming Languages (GPLs). However, like in any Software Product without passing by all development stages namely Domain Analysis, Design, Implementation and Evaluation, some of the DSLs’ alleged advantages may be impossible to be achieved with a significant level of satisfaction. This may lead to the production of inadequate or inefficient languages. This dissertation is focused on the Evaluation phase. To characterize DSL community commitment concerning Evaluation, we conducted a systematic review. The review covered publications in the main fora dedicated to DSLs from 2001 to 2008, and allowed to analyse and classify papers with respect to the validation efforts conducted by DSLs’ producers, where have been observed a reduced concern to this matter. Another important outcome that has been identified is the absence of a concrete approach to the evaluation of DSLs, which would allow a sound assessment of the actual improvements brought by the usage of DSLs. Therefore, the main goal of this dissertation concerns the production of a Systematic Evaluation Methodology for DSLs. To achieve this objective, has been carried out the major techniques used in Experimental Software Engineering and Usability Engineering context. The proposed methodology was validated with its use in several case studies, whereupon DSLs evaluation has been made in accordance with this methodology.
23
Bull, Christopher Neil. "Studios in software engineering education." Thesis, Lancaster University, 2016. http://eprints.lancs.ac.uk/79064/.
Abstract:
Computing has its roots in mathematics, where lectures are the dominant mode of education. Software engineering (SE) education, born from computer science, is also traditionally taught using lectures, but has grown beyond its mathematical roots; as the name implies, it is an engineering discipline. It is arguably necessary for SE to rethink its approach to education. Studio education is one alternative being explored. Studios originated from architecture and design, and are complex spaces used by collocated students to collaboratively and individually work on projects; they emphasise a physical “home” for students, problem-based and peer-based learning, and mentoring by academic staff rather than formal lectures. There are inherent similarities between SE and the original studio disciplines: e.g. we often use the architecture of buildings as metaphors when designing and describing software. This suggests that studios in SE should be further explored, despite its apparent lack of uptake across institutions worldwide. This thesis aims to provide useful information for anyone considering utilizing a studio-based approach. Initially, with no widely accepted definition for studio education available, a series of interviews with design/architecture studio educators was conducted, culminating in an understanding in the form of the ‘studio framework’. This is followed by further interviews, with SE studio educators, to determine their perspective of studio education, and exploring the SE specific elements to studio education. Finally, experiences and observations are shared of Lancaster University’s recent SE studio, comparing it to the studio framework.
24
Watson, Cody. "Deep Learning In Software Engineering." W&M ScholarWorks, 2020. https://scholarworks.wm.edu/etd/1616444371.
Abstract:
Software evolves and therefore requires an evolving field of Software Engineering. The evolution of software can be seen on an individual project level through the software life cycle, as well as on a collective level, as we study the trends and uses of software in the real world. As the needs and requirements of users change, so must software evolve to reflect those changes. This cycle is never ending and has led to continuous and rapid development of software projects. More importantly, it has put a great responsibility on software engineers, causing them to adopt practices and tools that allow them to increase their efficiency. However, these tools suffer the same fate as software designed for the general population; they need to change in order to reflect the user’s needs. Fortunately, the demand for this evolving software has given software engineers a plethora of data and artifacts to analyze. The challenge arises when attempting to identify and apply patterns learned from the vast amount of data. In this dissertation, we explore and develop techniques to take advantage of the vast amount of software data and to aid developers in software development tasks. Specifically, we exploit the tool of deep learning to automatically learn patterns discovered within previous software data and automatically apply those patterns to present day software development. We first set out to investigate the current impact of deep learning in software engineering by performing a systematic literature review of top tier conferences and journals. This review provides guidelines and common pitfalls for researchers to consider when implementing DL (Deep Learning) approaches in SE (Software Engineering). In addition, the review provides a research road map for areas within SE where DL could be applicable. Our next piece of work developed an approach that simultaneously learned different representations of source code for the task of clone detection. We found that the use of multiple representations, such as Identifiers, ASTs, CFGs and bytecode, can lead to the identification of similar code fragments. Through the use of deep learning strategies, we automatically learned these different representations without the requirement of hand-crafted features. Lastly, we designed a novel approach for automating the generation of assert statements through seq2seq learning, with the goal of increasing the efficiency of software testing. Given the test method and the context of the associated focal method, we automatically generated semantically and syntactically correct assert statements for a given, unseen test method. We exemplify that the techniques presented in this dissertation provide a meaningful advancement to the field of software engineering and the automation of software development tasks. We provide analytical evaluations and empirical evidence that substantiate the impact of our findings and usefulness of our approaches toward the software engineering community.
25
Burge, Janet E. "Software Engineering Using design RATionale." Link to electronic thesis, 2005. http://www.wpi.edu/Pubs/ETD/Available/etd-050205-085625/.
Abstract:
Dissertation (Ph.D.) -- Worcester Polytechnic Institute.Keywords: software engineering; inference; knowledge representation; software maintenance; design rationale. Includes bibliographical references (p. 202-211).
26
Rönkkö, Kari. "Software Practice from the Inside : Ethnography Applied to Software Engineering." Licentiate thesis, Karlskrona : Blekinge Institute of Technology, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00234.
Abstract:
Empirical methodologies have recently attracted increasing attention from the broader software engineering community. In particular, organisational issues and the human role in software development have been addressed. Qualitative research approaches have been identified as necessary for understanding human nature. One qualitative methodology which has become increasingly recognised in the software engineering community is ethnography. It is also the qualitative approach that is addressed in this thesis, i.e. ethnography in relation to software engineering. Ethnography emphasises the members point of view in an effort to understand the organisation of a social, cultural and technical setting. Until now, only a handful of ethnographic studies focusing on software engineering have been carried out in accordance with the original conception of ethnography; these studies have traditionally been performed by sociologists. The understanding and application of ethnography by software engineers differ from that of sociologists as it gives up the studied people's point of view in the analysis of data. The thesis is based on two independent ethnographic studies where the ‘inside’ perspective which complies with the original understanding of the methodology is applied. Using these examples as a basis, the relation between ethnography and software engineering research is explored. The objective of this thesis is to promote ‘ethnographic knowledge’ by giving an overview of ethnographic work within software engineering, presenting an original understanding of ethnography, comparing software engineers' understanding of ethnography with the original understanding of ethnography, demonstrating how the different implicit research attitudes of ethnographers and software engineers produce different research discourses, and finally pointing to an opportunity to combine ethnography, which contributes an ‘inside perspective’, with software engineering's need for constant improvement.
27
Meridji, Kenza. "Analysis of software engineering principles from an engineering perspective." Mémoire, École de technologie supérieure, 2010. http://espace.etsmtl.ca/278/1/MERIDJI_Kenza.pdf.
Abstract:
L'ingenierie du logiciel a recemment emerge comme un nouveau domaine d'ingenierie et
continue d'evoluer. Le genie logiciel est une discipline dont I'objectif est la production de
logiciels de haute qualite, mais il manque de maturite par rapport aux autres domaines de
l'ingenierie traditionnelle. Les domaines traditionnels de l'ingenierie ont leurs propres
principes bases sur la physique, la chimie ou les mathematiques. Puisque le domaine du genie
logiciel n'est pas fonde sur les lois de la nature, il est plus difficile de comprendre I'ensemble
de ses principes.
Cette recherche sur I'ensemble des principes fondamentaux candidats contribuera a une
meilleure comprehension et, eventuellement, a I'enseignement des principes du genie
logiciel. En outre, elle aidera a ameliorer le contenu du Guide SWEBOK du point de vue du
genie.
Ce travail de recherche a permis d'etudier la question du genie logiciel comme une discipline
du genie en utilisant les categories de connaissances en genie de Vincenti, d'identifier des
principes fondamentaux a partir d'un ensemble de candidats, et enfin d'examiner I'absence de
description explicite et systematique de ces principes, et leur application, dans le Guide
SWEBOK.
Les deux principaux objectifs de cette etude sont 1'identification des principes fondamentaux
de l'ingenierie du genie logiciel a partir des 34 principes candidats et la description des
directives operationnelles pour ces principes en utilisant comme base le contenu du Guide
SWEBOK.
Pour atteindre ces objectifs, la methodologie suivante de recherches a ete utilisee. Les
principales phases de cette methodologie de recherche sont: I'analyse, d'un point de vue
d'ingenierie, de la question du genie logiciel et de I'ensemble des 34 principes fondamentaux
candidats, I'identification des principes de genie logiciel dans le contenu du Guide SWEBOK
- ISO TR 19759, la description des lignes directrices operationnelles sur la base du contenu du
Guide SWEBOK et aligne avec la norme IEEE 1362-1998 Concept of Operations (CONOPS)
Document.
Le resultat de cette these est I'identification d'un ensemble de neuf principes fondamentaux
du genie logiciel et la description de directives operationnelles pour ces principes.
28
Brophy, Dennis J. O'Leary James D. "Software evaluation for developing software reliability engineering and metrics models /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1999. http://handle.dtic.mil/100.2/ADA361889.
Abstract:
Thesis (M.S. in Information Technology Management) Naval Postgraduate School, March 1999."March 1999". Thesis advisor(s): Norman F. Schneidewind, Douglas Brinkley. Includes bibliographical references (p. 59-60). Also available online.
29
Brophy, Dennis J., and James D. O'Leary. "Software evaluation for developing software reliability engineering and metrics models." Thesis, Monterey, California ; Naval Postgraduate School, 1999. http://hdl.handle.net/10945/13581.
Abstract:
Today's software is extremely complex, often constituting millions of lines of instructions. Programs are expected to operate smoothly on a wide variety of platforms. There are continuous attempts to try to assess what the reliability of a software package is and to predict what the reliability of software under development will be. The quantitative aspects of these assessments deal with evaluating, characterizing and predicting how well software will operate. Experience has shown that it is extremely difficult to make something as large and complex as modern software and predict with any accuracy how it is going to behave in the field. This thesis proposes to create an integrated system to predict software reliability for mission critical systems. This will be accomplished by developing a flexible DBMS to track failures and to integrate the DBMS with statistical analysis programs and software reliability prediction tools that are used to make calculations and display trend analysis. It further proposes a software metrics model for fault prediction by determining and manipulating metrics extracted from the code.
30
Lin, Chia-en. "Performance Engineering of Software Web Services and Distributed Software Systems." Thesis, University of North Texas, 2014. https://digital.library.unt.edu/ark:/67531/metadc500103/.
Abstract:
The promise of service oriented computing, and the availability of Web services promote the delivery and creation of new services based on existing services, in order to meet new demands and new markets. As Web and internet based services move into Clouds, inter-dependency of services and their complexity will increase substantially. There are standards and frameworks for specifying and composing Web Services based on functional properties. However, mechanisms to individually address non-functional properties of services and their compositions have not been well established. Furthermore, the Cloud ontology depicts service layers from a high-level, such as Application and Software, to a low-level, such as Infrastructure and Platform. Each component that resides in one layer can be useful to another layer as a service. It hints at the amount of complexity resulting from not only horizontal but also vertical integrations in building and deploying a composite service. To meet the requirements and facilitate using Web services, we first propose a WSDL extension to permit specification of non-functional or Quality of Service (QoS) properties. On top of the foundation, the QoS-aware framework is established to adapt publicly available tools for Web services, augmented by ontology management tools, along with tools for performance modeling to exemplify how the non-functional properties such as response time, throughput, or utilization of services can be addressed in the service acquisition and composition process. To facilitate Web service composition standards, in this work we extended the framework with additional qualitative information to the service descriptions using Business Process Execution Language (BPEL). Engineers can use BPEL to explore design options, and have the QoS properties analyzed for the composite service. The main issue in our research is performance evaluation in software system and engineering. We researched the Web service computation as the first half of this dissertation, and performance antipattern detection and elimination in the second part. Performance analysis of software system is complex due to large number of components and the interactions among them. Without the knowledge of experienced experts, it is difficult to diagnose performance anomalies and attempt to pinpoint the root causes of the problems. Software performance antipatterns are similar to design patterns in that they provide what to avoid and how to fix performance problems when they appear. Although the idea of applying antipatterns is promising, there are gaps in matching the symptoms and generating feedback solution for redesign. In this work, we analyze performance antipatterns to extract detectable features, influential factors, and resource involvements so that we can lay the foundation to detect their presence. We propose system abstract layering model and suggestive profiling methods for performance antipattern detection and elimination. Solutions proposed can be used during the refactoring phase, and can be included in the software development life cycle. Proposed tools and utilities are implemented and their use is demonstrated with RUBiS benchmark.
31
Delorey, Daniel Pierce. "Observational Studies of Software Engineering Using Data from Software Repositories." Diss., CLICK HERE for online access, 2007. http://contentdm.lib.byu.edu/ETD/image/etd1716.pdf.
32
McMeekin, David Andrew. "A software inspection methodology for cognitive improvement in software engineering." Thesis, Curtin University, 2010. http://hdl.handle.net/20.500.11937/400.
Abstract:
This thesis examines software inspections application in a non-traditional use through examining the cognitive levels developers demonstrate while carrying out software inspection tasks. These levels are examined in order to assist in increasing developers’ ability to understand, maintain and evolve software systems.The results from several empirical studies carried out are presented. These indicate several important findings: student software developers find structured reading techniques more helpful as an aid than less structured reading techniques, while professional developers find the more structured techniques do not allow their experience to be applied to the problem at hand; there is a correlation between the effectiveness of a software inspection and an inspector’s ability to successfully add new functionality to the inspected software artefact; the cognitive levels that student developers functioned at while carrying out software inspection tasks were at higher orders of thinking when structured inspection techniques were implemented than when unstructured techniques were applied.From the empirical results a mapping has been created of several software inspection techniques to the cognitive process models they support and the cognitive levels, as measured using Bloom’s Taxonomy that they facilitate. This mapping is to understand the impact carrying out a software inspection has upon a developer’s cognitive understanding of the inspected system.The knowledge and understanding of the findings of this research has culminated in the creation of a code reading methodology to increase the cognitive level software developers operate at while reading software code. The reading methodology distinguishes where in undergraduate and software developer training courses different software inspection reading techniques are to be implemented in order to maximise a software developer’s code reading ability dependent upon their experience level.
33
Kinnula, A. (Atte). "Software process engineering in a multi-site environment:an architectural design of a software process engineering system." Doctoral thesis, University of Oulu, 1999. http://urn.fi/urn:isbn:9514253035.
Abstract:
Abstract
A fundamental problem in the software engineering community
is how to achieve a state of continuous improvement. Over the last
ten years a number of studies have been made concerning various
tools, methods and software process improvement project life-cycle models,
but the problem persists and in many cases the software process
improvement program dies off within a year.
This thesis takes the assumption that the answer cannot be
reduced to a single tool or method, as there are no silver bullets
to complex problems. Instead the entire Software Process Engineering
system should be studied to find out what elements are necessary
for sustaining improvement activity on a long-term basis. Through
understanding the fundamental elements of a Software Process Engineering
system, the organization can manage and improve the system, tune
it up to the environment and make it efficient and effective. When
the system is operational, the software process improvement program,
which is a part of the system, can be sustained.
This research studies a case in which the Software Process
Engineering system of a large, multi-site telecommunications company
was successfully revised to meet the increasing improvement challenges.
The revised system has proven to be capable of sustaining continuous
improvement and case is used here to derive architectural design
models of a Software Process Engineering system.
Two such models are established here. One is a system model
that is independent of implementation and identifies the main elements
of a Software Process Engineering system. With the help of this
model, those responsible for process improvement in their organizations
can design, evaluate, and revise complete Software Process Engineering
systems. The other model is a design of a multi-site Software Process
Engineering organization, and identifies not only the operative
part of the organization but also the key non-operative elements
that a Software Process Engineering system needs to work with. With the
help of this model a multi-site organization can set up the operative
Software Process Engineering organization and plan for strategies
for managing the cooperation with the interfacing entities up front,
rather than ending up managing such contacts on a reactive fashion.
34
Jennings, Charles A. "Re-engineering software systems in the Department of Defense using integrated computer aided software engineering tools." Thesis, Monterey, California. Naval Postgraduate School, 1992. http://hdl.handle.net/10945/23761.
35
Addy, Edward A. "Verification and validation in software product line engineering." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1068.
Abstract:
Thesis (Ph. D.)--West Virginia University, 1999.Title from document title page. Document formatted into pages; contains vi, 75 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 35-39).
36
Freund, Tessen. "Software Engineering durch Modellierung wissensintensiver Entwicklungsprozesse /." Berlin : GITO, 2007. http://deposit.d-nb.de/cgi-bin/dokserv?id=3040491&prov=M&dok_var=1&dok_ext=htm.
37
Schroeder, Andreas. "Software engineering perspectives on physiological computing." Diss., lmu, 2011. http://nbn-resolving.de/urn:nbn:de:bvb:19-139294.
38
Nojoumian, Mehrdad. "Document engineering of complex software specifications." Thesis, University of Ottawa (Canada), 2007. http://hdl.handle.net/10393/27479.
Abstract:
The research presented in this thesis aims at document engineering of complex specifications, of which the UML Superstructure Specification (version 2.1) is our initial target. Document engineering deals with principles, tools and processes that improve our ability to create, manage, and maintain documents [40].
Our motivation is that such specifications are dense and intricate to use, and tend to have complicated structures with lots of repetitive, or 'boilerplate' material. End users cannot use them efficiently because of the general complexity of the document.
Our objective and main contribution in this thesis is therefore to create an approach that allowed us to re-engineer PDF-based documents, and to illustrate how to make more usable versions of electronic documents such as specifications, conference proceedings, technical books, etc so that end-users to have a better experience with them.
The first step was to extract the logical structure of the document. Our initial assumption was that, many key concepts of a document are expressed in this structure, which includes the headings of the chapters, sections, subsections, etc. We demonstrated this by analyzing some data, and created a special-purpose parser to generate a well-formed XML document with various types of tags.
In the next phase, we created a user interface for end users by generating a multi-layer HTML version of the document to facilitate document browsing, navigating, and concept exploration.
Although our targeted document was the UML Superstructure Specification, we chose a general approach for most phases of our work including format conversions, logical structure extraction, text extraction, hypertext generation, etc. Therefore, by minor adjustments we can process other complex documents to gain our mentioned goals. We also established the major infrastructure for a new document engineering framework.
39
Freund, Tessen. "Software Engineering durch Modellierung wissensintensiver Entwicklungsprozesse." Berlin GITO, 2006. http://d-nb.info/986549339/04.
40
Rodden, Thomas. "Supporting cooperation in software engineering environments." Thesis, Lancaster University, 1990. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.304516.
41
Mannering, D. P. "Problem Oriented Engineering for Software Safety." Thesis, Open University, 2010. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.520738.
42
Cook, Carl Leslie Raymond. "Towards Computer-Supported Collaborative Software Engineering." Thesis, University of Canterbury. Computer Science and Software Engineering, 2007. http://hdl.handle.net/10092/1140.
Abstract:
Software engineering is a fundamentally collaborative activity, yet most tools that support software engineers are designed only for single users. There are many foreseen benefits in using tools that support real time collaboration between software engineers, such as avoiding conflicting concurrent changes to source files and determining the impact of program changes immediately. Unfortunately, it is difficult to develop non-trivial tools that support real time Collaborative Software Engineering (CSE). Accordingly, the few CSE tools that do exist have restricted capabilities. Given the availability of powerful desktop workstations and recent advances in distributed computing technology, it is now possible to approach the challenges of CSE from a new perspective. The research goal in this thesis is to investigate mechanisms for supporting real time CSE, and to determine the potential gains for developers from the use of CSE tools. An infrastructure, CAISE, is presented which supports the rapid development of real time CSE tools that were previously unobtainable, based on patterns of collaboration evident within software engineering. In this thesis, I discuss important design aspects of CSE tools, including the identification of candidate patterns of collaboration. I describe the CAISE approach to supporting small teams of collaborating software engineers. This is by way of a shared semantic model of software, protocol for tool communication, and Computer Supported Collaborative Work (CSCW) facilities. I then introduce new types of synchronous semantic model-based tools that support various patterns of CSE. Finally, I present empirical and heuristic evaluations of typical development scenarios. Given the CAISE infrastructure, it is envisaged that new aspects of collaborative work within software engineering can be explored, allowing the perceived benefits of CSE to be fully realised.
43
Heineman, Judie A. "A software reliability engineering case study." Thesis, Monterey, California. Naval Postgraduate School, 1996. http://hdl.handle.net/10945/8975.
Abstract:
Approved for public release; distribution is unlimitedHandling, identifying, and correcting faults are significant concerns for the software maanger because (1) the presence of faults in the operational software can put human life and mission success at risk in a safety critical application and (2) the entire software reliability process is expensive. Designing an effective Software Reliability Engineering (SRE) process is one method to increase reliability and reduce costs. This thesis describes a process that is being implemented at Marine Corps Tactical System Support Activity (MCTSSA), using the Schneidewind Reliability Model and the SRE process described in the American Institute of Aeronautics and Astronautics Recommended Practice in Software Reliability. In addition to applying the SRE process to single node systems, its applicability to multi-node LAN-based distributed systems is explored. Each of the SRE steps is discussed, with practical examples provided, as they would apply to a testing facility. Special attention is directed to data collection methodologies and the application of model results. in addition, a handbook and training plan are provided for use by MCTSSA during the transition to the SRE process
44
Unterkalmsteiner, Michael. "Coordinating requirements engineering and software testing." Doctoral thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-663.
Abstract:
The development of large, software-intensive systems is a complex undertaking that is generally tackled by a divide and conquer strategy. Organizations face thereby the challenge of coordinating the resources which enable the individual aspects of software development, commonly solved by adopting a particular process model. The alignment between requirements engineering (RE) and software testing (ST) activities is of particular interest as those two aspects are intrinsically connected: requirements are an expression of user/customer needs while testing increases the likelihood that those needs are actually satisfied. The work in this thesis is driven by empirical problem identification, analysis and solution development towards two main objectives. The first is to develop an understanding of RE and ST alignment challenges and characteristics. Building this foundation is a necessary step that facilitates the second objective, the development of solutions relevant and scalable to industry practice that improve REST alignment. The research methods employed to work towards these objectives are primarily empirical. Case study research is used to elicit data from practitioners while technical action research and field experiments are conducted to validate the developed solutions in practice. This thesis contains four main contributions: (1) An in-depth study on REST alignment challenges and practices encountered in industry. (2) A conceptual framework in the form of a taxonomy providing constructs that further our understanding of REST alignment. The taxonomy is operationalized in an assessment framework, REST-bench (3), that was designed to be lightweight and can be applied as a postmortem in closing development projects. (4) An extensive investigation into the potential of information retrieval techniques to improve test coverage, a common REST alignment challenge, resulting in a solution prototype, risk-based testing supported by topic models (RiTTM). REST-bench has been validated in five cases and has shown to be efficient and effective in identifying improvement opportunities in the coordination of RE and ST. Most of the concepts operationalized from the REST taxonomy were found to be useful, validating the conceptual framework. RiTTM, on the other hand, was validated in a single case experiment where it has shown great potential, in particular by identifying test cases that were originally overlooked by expert test engineers, improving effectively test coverage.
45
Karatasios, Labros G. "Software engineering with database management systems." Thesis, Monterey, California. Naval Postgraduate School, 1989. http://hdl.handle.net/10945/27272.
46
Greer, Desmond. "Software engineering risk : understanding and management." Thesis, University of Ulster, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.326127.
47
Martin, W. J. "App Store Analysis for software engineering." Thesis, University College London (University of London), 2017. http://discovery.ucl.ac.uk/1537482/.
Abstract:
App Store Analysis concerns the mining of data from apps, made possible through app stores. This thesis extracts publicly available data from app stores, in order to detect and analyse relationships between technical attributes, such as software features, and non-technical attributes, such as rating and popularity information. The thesis identifies the App Sampling Problem, its effects and a methodology to ameliorate the problem. The App Sampling Problem is a fundamental sampling issue concerned with mining app stores, caused by the rather limited ‘most-popular-only’ ranked app discovery present in mobile app stores. This thesis provides novel techniques for the analysis of technical and non-technical data from app stores. Topic modelling is used as a feature extraction technique, which is shown to produce the same results as n-gram feature extraction, that also enables linking technical features from app descriptions with those in user reviews. Causal impact analysis is applied to app store performance data, leading to the identification of properties of statistically significant releases, and developer-controlled properties which could increase a release’s chance for causal significance. This thesis introduces the Causal Impact Release Analysis tool, CIRA, for performing causal impact analysis on app store data, which makes the aforementioned research possible; combined with the earlier feature extraction technique, this enables the identification of the claimed software features that may have led to significant positive and negative changes after a release.
48
Yang, Bob 1976. "Managing a distributed software engineering team." Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/50394.
Abstract:
Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science; and, Thesis (B.S.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1998.Includes bibliographical references (leaves 97-98).
by Bob Yang.
B.S.
M.Eng.
49
Rantanen, E. (Eetu). "Requirements engineering in agile software projects." Bachelor's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201705091721.
Abstract:
Many software projects are failed due to the delivery decisions that were made without adequate requirements information. In addition, the project management process including agile-oriented requirement management process has been identified as one of the four success factors in the agile software projects. Having the clear rules for requirements engineering is, therefore, an important thing for agile software projects from their success point of view. In this study, the objective is to analyze agile requirements engineering and to find out practices that are used in it. The goal is to define a continuous process to identify customer needs and translate them into software requirements in the agile software development. This goal is going to be achieved by a systematic literature review on the agile requirements engineering. For the agile software development and the traditional requirements engineering, the theory has been gathered from some basic books of the theme. The primary research question for this study is: How the customer needs will be translated into requirements in the agile software project as a continuous process? There are also two secondary research questions: 1. What are the customer needs and how can they be identified? 2. What kind of practices are used in the agile requirements engineering? Generally, the requirements engineering process includes four separate steps. First, the business usefulness of the system should be evaluated (feasibility study). After that, the requirements are discovered (elicitation and analysis)and converted into some standard form (specification). Last phase includes checking that the requirements define the system as customer wants (validation). Agile requirements engineering includes four major practices. The high-level interaction between the development team and the customer, iterative approach for the requirements engineering, prioritizing the requirements based on their business value for the customer, and eliciting also the non-functional requirements. In addition, the documentation of requirements is minimalistic in agile approaches. Results of this study can generally be applied and the model created can be utilized as a guideline when doing requirements engineering in the agile software projectsMonet ohjelmistoprojektit epäonnistuvat, koska tieto vaatimuksista on riittämätöntä toimituspäätöksiä tehdessä. Lisäksi projektinhallinnan prosessi, johon sisältyy ketterä vaatimustenhallinnan prosessi, on tunnistettu yhdeksi neljästä ketterien ohjelmistoprojektien menestystekijästä. Tämän takia ketterien ohjelmistoprojektien onnistumiseksi on tärkeää, että vaatimusmäärittelylle on selkeät ohjeet. Tämän tutkimuksen tarkoituksena on analysoida ketterää vaatimusmäärittelyä ja löytää siinä yleisesti käytettyjä tapoja. Tavoitteena on määrittää jatkuva prosessi, jossa asiakkaan tarpeet tunnistetaan ja käännetään ohjelmiston vaatimuksiksi ketterässä ohjelmistokehityksessä. Tavoitteeseen pyritään tekemällä systemaattinen kirjallisuuskatsaus ketterään vaatimusmäärittelyyn. Ketterää ohjelmistokehitystä sekä perinteistä vaatimusmäärittelyä käsitellään muutaman perusteoksen pohjalta. Tutkimuksen ylätason tutkimuskysymys on: Kuinka asiakkaan tarpeet käännetään vaatimuksiksi jatkuvana prosessina ketterissä ohjelmistoprojekteissa? Lisäksi tutkimuksella on kaksi alatason tutkimuskysymystä: 1. Mitä asiakkaan tarpeet ovat ja kuinka ne tunnistetaan? 2. Minkälaisia tapoja ketterässä vaatimusmäärittelyssä käytetään? Yleinen vaatimusmäärittelyprosessi sisältää neljä vaihetta. Ensin arvioidaan järjestelmän liiketoiminnallinen tarpeellisuus (kannattavuusselvitys). Tämän jälkeen etsitään vaatimuksia (selvitys ja analyysi) ja käännetään ne johonkin standardimuotoon (spesifikaatio). Viimeisessä vaiheessa tarkistetaan, että vaatimukset määrittävät järjestelmän juuri asiakkaan haluamalla tavalla (validointi). Ketterässä vaatimusmäärittelyssä on neljä yleistä käytäntöä. Korkean tason kanssakäyminen asiakkaan ja kehitystiimin välillä, iteratiivinen eli toistava lähestymistapa vaatimusmäärittelyyn, vaatimusten priorisointi perustuen asiakkaalle syntyvään arvoon ja myös ei-funktionaalisten vaatimusten tunnistus. Lisäksi voidaan sanoa, että vaatimusten dokumentointi ketterissä menetelmissä on vähäistä. Tämän tutkimuksen tuloksia voidaan yleisesti ottaen hyödyntää ja kehitettyä mallia voidaan käyttää vaatimusmäärittelyn ohjenuorana ketterissä ohjelmistoprojekteissa
50
Zabardast, Ehsan. "Towards Understanding Assets in Software Engineering." Licentiate thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-21270.
Abstract:
The development of software products is a massive undertaking, and organisations have to manage all artefacts involved in the process. Managing such artefacts that, in many cases, become crucial assets is important for success. Recognising assets and letting them (unintentionally) degrade can result in maintainability problems. Thus, there is a need to create a structured and organised body of knowledge that can guide practitioners and researchers to deal with the assets during the product/service life-cycle. This includes, but is not limited to, what steps are needed to understand the assets’ degradation, investigating and examining the existing methods and metrics on how to estimate degradation and understanding the implication of assets’ value and degradation. This licentiate’s main objective is contributing to the software engineering field by providing a different perspective on assets focusing on assets’ value for the organisation. We have used literature reviews, focus groups, case study, and sample study to address this objective. The collected data is from peer-reviewed work, collaboration with five company partners, and 31 OSS from Apache Foundation. First, we have defined the concept and terminology in a position paper. We havecreated an asset management taxonomy based on a literature review and focus groups– fours focus groups conducted in 2019 with 29 participants. The extracted assets represent not only the stages of software development, from requirements to verificationand validation, but also operational and organisational perspectives. The taxonomy wascreated to be extendable as the field evolves and matures. Then, we have performed a more in-depth investigation of selected asset types. As a part of studying assets, in a case study, we present the impact of bug-fixing,refactorings, and new development to investigate how source code degrades. In anothersample study, we examine the longevity of specific source-code related issues in 31OSS from Apache Foundation using statistical analysis. The work done in this licentiate includes: defining the asset concept and relatedterminology, identifying assets and creating a taxonomy of assets, presenting the preliminary investigation of tools and methods to understand source-code and architecturerelated asset degradation. We conclude that a good understanding of the relevant assets for the inception,planning, development, evolution, and maintenance of software-intensive products andservices is necessary to study their value degradation. Our work builds on currentmethods and details the underlying concepts attempting to homogenise definitions andbring the areas of assets and degradation together. A natural progression of our workis to investigate the measurements to evaluate the degradation of assets. This licentiate thesis starts investigating the value degradation of source-code related assets. We planto continue investigating the degradation of architecture in our future work.