Log in

Relevant bibliographies by topics / Software engineering / Dissertations / Theses

To see the other types of publications on this topic, follow the link: Software engineering.

Dissertations / Theses on the topic 'Software engineering'

Author: Grafiati

Published: 4 June 2021

Last updated: 25 July 2025

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

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/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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, relac

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

Abstract:

Dissertation (Ph.D. in Software Engineering)--Naval Postgraduate School, September 2008.<br>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.

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

6

Sezer, Bulent. "Software Engineering Process Improvement." Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12608338/index.pdf.

Full text

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&uuml<br>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&#039<br>s improvement suggestions have been discussed wi

APA, Harvard, Vancouver, ISO, and other styles

7

Boriani, Dario V. "Software engineering for control." Thesis, University of Oxford, 1989. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.253293.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 shoul

APA, Harvard, Vancouver, ISO, and other styles

9

Loomes, Martin James. "Software engineering curriculum design." Thesis, University of Surrey, 1991. http://epubs.surrey.ac.uk/844417/.

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

10

Alrabghi, Leenah O. "QFD IN SOFTWARE ENGINEERING." Kent State University / OhioLINK, 2014. http://rave.ohiolink.edu/etdc/view?acc_num=kent1385046526.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 researc

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 org

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 propos

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 indust

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

Abstract:

PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO<br>A 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, o

APA, Harvard, Vancouver, ISO, and other styles

16

Ahmad, M. O. (Muhammad Ovais). "Exploring Kanban in software engineering." Doctoral thesis, Oulun yliopisto, 2016. http://urn.fi/urn:isbn:9789526214085.

Full text

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 us

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 experime

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 var

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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 analy

APA, Harvard, Vancouver, ISO, and other styles

20

Wang, Yingxu. "Software engineering process modelling analysis." Thesis, Southampton Solent University, 1998. http://ssudl.solent.ac.uk/2429/.

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

21

Cunningham, Hamish. "Software architecture for language engineering." Thesis, University of Sheffield, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.324440.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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.

Full text

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ática<br>Domain-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

APA, Harvard, Vancouver, ISO, and other styles

23

Bull, Christopher Neil. "Studios in software engineering education." Thesis, Lancaster University, 2016. http://eprints.lancs.ac.uk/79064/.

Full text

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 physica

APA, Harvard, Vancouver, ISO, and other styles

24

Watson, Cody. "Deep Learning In Software Engineering." W&M ScholarWorks, 2020. https://scholarworks.wm.edu/etd/1616444371.

Full text

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 al

APA, Harvard, Vancouver, ISO, and other styles

25

Burge, Janet E. "Software Engineering Using design RATionale." Link to electronic thesis, 2005. http://www.wpi.edu/Pubs/ETD/Available/etd-050205-085625/.

Full text

Abstract:

Dissertation (Ph.D.) -- Worcester Polytechnic Institute.<br>Keywords: software engineering; inference; knowledge representation; software maintenance; design rationale. Includes bibliographical references (p. 202-211).

APA, Harvard, Vancouver, ISO, and other styles

26

Srinivasaraghavan, Narayanan. "Software engineering : knowledge and performance." Doctoral thesis, importedStudentThesis, 2010. https://researchprofiles.canberra.edu.au/en/studentTheses/0b70f51e-8660-4537-8dfe-f090cfbd5a4a.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

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.

Full text

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 p

APA, Harvard, Vancouver, ISO, and other styles

28

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.

Full text

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'en

APA, Harvard, Vancouver, ISO, and other styles

29

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.

Full text

Abstract:

Thesis (M.S. in Information Technology Management) Naval Postgraduate School, March 1999.<br>"March 1999". Thesis advisor(s): Norman F. Schneidewind, Douglas Brinkley. Includes bibliographical references (p. 59-60). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

30

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.

Full text

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 accu

APA, Harvard, Vancouver, ISO, and other styles

31

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/.

Full text

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 C

APA, Harvard, Vancouver, ISO, and other styles

32

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

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.

Full text

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 mor

APA, Harvard, Vancouver, ISO, and other styles

34

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.

Full text

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 stud

APA, Harvard, Vancouver, ISO, and other styles

35

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

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.

Full text

Abstract:

Thesis (Ph. D.)--West Virginia University, 1999.<br>Title from document title page. Document formatted into pages; contains vi, 75 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 35-39).

APA, Harvard, Vancouver, ISO, and other styles

37

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Schroeder, Andreas. "Software engineering perspectives on physiological computing." Diss., lmu, 2011. http://nbn-resolving.de/urn:nbn:de:bvb:19-139294.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Nojoumian, Mehrdad. "Document engineering of complex software specifications." Thesis, University of Ottawa (Canada), 2007. http://hdl.handle.net/10393/27479.

Full text

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 contrib

APA, Harvard, Vancouver, ISO, and other styles

40

Freund, Tessen. "Software Engineering durch Modellierung wissensintensiver Entwicklungsprozesse." Berlin GITO, 2006. http://d-nb.info/986549339/04.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Rodden, Thomas. "Supporting cooperation in software engineering environments." Thesis, Lancaster University, 1990. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.304516.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Mannering, D. P. "Problem Oriented Engineering for Software Safety." Thesis, Open University, 2010. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.520738.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

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.

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

44

Heineman, Judie A. "A software reliability engineering case study." Thesis, Monterey, California. Naval Postgraduate School, 1996. http://hdl.handle.net/10945/8975.

Full text

Abstract:

Approved for public release; distribution is unlimited<br>Handling, 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),

APA, Harvard, Vancouver, ISO, and other styles

45

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.

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

46

Karatasios, Labros G. "Software engineering with database management systems." Thesis, Monterey, California. Naval Postgraduate School, 1989. http://hdl.handle.net/10945/27272.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Greer, Desmond. "Software engineering risk : understanding and management." Thesis, University of Ulster, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.326127.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Martin, W. J. "App Store Analysis for software engineering." Thesis, University College London (University of London), 2017. http://discovery.ucl.ac.uk/1537482/.

Full text

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 prese

APA, Harvard, Vancouver, ISO, and other styles

49

Yang, Bob 1976. "Managing a distributed software engineering team." Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/50394.

Full text

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.<br>Includes bibliographical references (leaves 97-98).<br>by Bob Yang.<br>B.S.<br>M.Eng.

APA, Harvard, Vancouver, ISO, and other styles

50

Rantanen, E. (Eetu). "Requirements engineering in agile software projects." Bachelor's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201705091721.

Full text

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

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!