Dissertations / Theses: 'Software/systems development'

1

Cao, Lan. "Modeling Dynamics in Agile Software Development." Digital Archive @ GSU, 2005. http://digitalarchive.gsu.edu/cis_diss/4.

Full text

Abstract:

Agile software development challenges the traditional way of software development and project management. In rapidly changing environments, changing requirements and tight schedule constraints require software developers to take a different approach toward the process of software development. However, beyond a few case studies, surveys and studies focused on specific practices such as pair programming, the effectiveness and applicability of agile methods have not been established adequately. The objective of my research is to improve the understanding of and gain insights into these issues. For this purpose, I develop a system dynamic simulation model that considers the complex interdependencies among the variety of practices used in agile development. The model is developed on the basis of an extensive review of the literature as well as quantitative and qualitative data collected from real projects in seven organizations. The development of the model was guided by dynamic hypotheses on customer involvement, refactoring and quality of design. The model was refined and validated using data from independent projects. The model helps in answering important questions on the impact of customer behavior, cost of making changes and economics of pair programming. Experimentation with the model suggests that the cost of change is not constant; instead, its value changes cyclically and increases towards the later phase of development. Also, the results of simulation show that with no pair programming, fewer tasks are delivered and it costs more to deliver a task when compared to development with pair programming. Further, customer behavior has a major impact on project performance. The quality of customer feedback is found to be very critical to the successful of an agile software development project. The primary contribution of this research is the simulation model of agile software development that can be used a tool to examine the impact of agile practices and management policies on critical project variables including project scope, schedule, and cost. This research provides a mechanism to study agile development as a dynamic system of practices rather than using a static view and in isolation. The results from this study are expected to be of significant interest to practitioners of agile methods by providing them a simulation environment to examine the impact of their practices, procedures and management policies.

APA, Harvard, Vancouver, ISO, and other styles

2

Minich, Matthias Ernst. "Industrialising software development in systems integration." Thesis, University of Plymouth, 2013. http://hdl.handle.net/10026.1/2772.

Full text

Abstract:

Compared to other disciplines, software engineering as of today is still dependent on craftsmanship of highly-skilled workers. However, with constantly increasing complexity and efforts, existing software engineering approaches appear more and more inefficient. A paradigm shift towards industrial production methods seems inevitable. Recent advances in academia and practice have lead to the availability of industrial key principles in software development as well. Specialization is represented in software product lines, standardization and systematic reuse are available with component-based development, and automation has become accessible through model-driven engineering. While each of the above is well researched in theory, only few cases of successful implementation in the industry are known. This becomes even more evident in specialized areas of software engineering such as systems integration. Today’s IT systems need to quickly adapt to new business requirements due to mergers and acquisitions and cooperations between enterprises. This certainly leads to integration efforts, i.e. joining different subsystems into a cohesive whole in order to provide new functionality. In such an environment. the application of industrial methods for software development seems even more important. Unfortunately, software development in this field is a highly complex and heterogeneous undertaking, as IT environments differ from customer to customer. In such settings, existing industrialization concepts would never break even due to one-time projects and thus insufficient economies of scale and scope. This present thesis, therefore, describes a novel approach for a more efficient implementation of prior key principles while considering the characteristics of software development for systems integration. After identifying the characteristics of the field and their affects on currently-known industrialization concepts, an organizational model for industrialized systems integration has thus been developed. It takes software product lines and adapts them in a way feasible for a systems integrator active in several business domains. The result is a three-tiered model consolidating recurring activities and reducing the efforts for individual product lines. For the implementation of component-based development, the present thesis assesses current component approaches and applies an integration metamodel to the most suitable one. This ensures a common understanding of systems integration across different product lines and thus alleviates component reuse, even across product line boundaries. The approach is furthermore aligned with the organizational model to depict in which way component-based development may be applied in industrialized systems integration. Automating software development in systems integration with model-driven engineering was found to be insufficient in its current state. The reason herefore lies in insufficient tool chains and a lack of modelling standards. As an alternative, an XML-based configuration of products within a software product line has been developed. It models a product line and its products with the help of a domain-specific language and utilizes stylesheet transformations to generate compliable artefacts. The approach has been tested for its feasibility within an exemplarily implementation following a real-world scenario. As not all aspects of industrialized systems integration could be simulated in a laboratory environment, the concept was furthermore validated during several expert interviews with industry representatives. Here, it was also possible to assess cultural and economic aspects. The thesis concludes with a detailed summary of the contributions to the field and suggests further areas of research in the context of industrialized systems integration.

APA, Harvard, Vancouver, ISO, and other styles

3

Ramos, Marcelo Augusto. "Bridging software engineering gaps towards system of systems development." Universidade de São Paulo, 2014. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-13082014-103931/.

Full text

Abstract:

While there is a growing recognition of the importance of System of Systems (SoS), there is still little agreement on just what they are or on by what principles they should be constructed. Actually, there are numerous SoS definitions in the literature. The difficulty in specifying what are the constituent systems, what they are supposed to do, and how they are going to do it frequently lead SoS initiatives to complete failures. Guided by a sample SoS that comprises all the distinguishing SoS characteristics and a generic SoS Engineering (SoSE) process, this thesis explores the SoS development from different Software Engineering (SE) perspectives that include requirements, analysis, design, and reengineering. For the Requirements Engineering (RE), we propose a scene-based RE approach to describe the SoS progressively as an arrangement of elementary but meaningful related behaviors named scenes. The objective is making easier the description and the understanding of the SoS dynamism. For the analysis, we propose extensions to statecharts to visually improve the modeling of systems interactions. They are symbolic notations that result from an analogy with multi-layer Printed Circuit Boards (PCB). The resulting diagrams are named PCBstatecharts. For the design, we propose an extension to the conventional SPLE process in such a way that SPL can become a natural source of SoS members. Domain engineering is extended to deliver components able to share abilities in SoS environments. Then, application engineers can design families of products that comply with different SoS requirements and still improve their products using the abilities of other SoS members. For the reengineering, we propose an approach extension to evolve legacy systems to SPL and then to SoS members. We demonstrate that when legacy systems are reengineered properly, they can share useful abilities, work cooperatively, and compose SoS
Apesar do crescente reconheciimento da importância de Sistemas de Sistemas (SoS) ainda não há um consenso sobre o que eles são um para que princípios devem ser construídos. De fato, existem várias definições de SoS na literatura. A dificuldade de especificar quais são os sistemas constituintes, as suas tarefas e como eles irão realizá-las frequentemente conduzem iniciativas de SoS ao completo fracasso. Guiados por um exemplo que inclui todas as características distintas de um SoS e um processo genérico de engenharia de SoS (SoSE), esta tese explora o desenvolvimento de SoS a partir de diferentes perspectivas da engenharia de software (SE), que incluem requisitos, análise, projeto e reengenharia. Para a engenharia de requisitos (RE) é proposta uma abordagem para descrever progressivamente um SoS como um arranjo de comportamentos mais simples, porém significativos, denominados \'cenas\'. O objetivo é facilitar a descrição e o entendimento do SoS e seu dinamismo. Para a análise, propõe-se as extensões de statecharts para melhorar a modelagem das interações entre sistemas. Elas são notações simbólicas que resultam de uma analogia com placas de circuito impresso multi camadas (PCB). Os diagramas resultantes são denominados PCB-statecharts. Para o projeto, é proposta uma extensão para o processo convencional de engenharia de linha de produtos (SPLE), de tal forma que linhas de produto (SPL) possam se tornar uma fonte natural de membros para SoS. A engenharia de domínio é estendida para prover componentes capazes de compartilhar habilidades em ambientes de SoS. Desta forma, engenheiros de aplicação podem projetar famílias de produtos complacentes com diferentes requisitos de SoS e ainda melhorar seus produtos usando habilidades de outros membros de um SoS. Para a reengenharia propõe-se extensão de uma abordagem existente para evoluir legados para SPL e depois para membros de um SoS. O objetivo é demonstrar que quando sistemas legados são tratados apropriadamente, eles podem compartilhar habilidades úteis, trabalhar de maneira cooperativa e compor SoS

APA, Harvard, Vancouver, ISO, and other styles

4

Kortetjärvi, Fredrik, and Rohullah Khorami. "Software development of visualizationsystem." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-44789.

Full text

Abstract:

Today wireless technologies are increasing in the automation systems used in homes and buildings. More electrical devices are used in a house to save time, money, and energy because they are relatively inexpensive and easy to install; these devices even allow smart components such as mobile tablets and computer connectivity. To connect all these devices for data transmission purposes and easy access, the KNX is the best choice. The KNX standard is an open standard for home and building automation. KNX standard supports different communication media such as Twisted pairs, Power line, Radio Frequency, and tunnelling IP. KNX system is a bus system for building control, making all electrical and smart devices in a KNX system use the same transmission method and exchange telegrams via a shared bus network. To check and control all the electrical devices in a home or an apartment takes time; that is why there is a massive need for applications to make every room’s controlling process much easier and take a much shorter time. This project is about designing and implementing a visualization application for windows and .NET for managing and comparing input data with the actual data. This application is equipped with a KNX bus driver to communicate with hardware in a building. The practical part of the application is to take some raw data and then sort them in a specific way to minimize the time of controlling the process of the KNX devices in a building.

APA, Harvard, Vancouver, ISO, and other styles

5

Quezada, Gomez Juan Manuel. "Model-based guidelines for automotive electronic systems software development." Thesis, Massachusetts Institute of Technology, 2015. http://hdl.handle.net/1721.1/100383.

Full text

Abstract:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2015.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 96-98).
The automobile innovation transformed the human life style ever since its introduction to the public, and for over the last one hundred years incumbent technologies have been adopted to improve its performance characteristics. Yet, we need a holistic approach to understand that automobiles shifted from being a mere assembly of mechanical parts to a multidisciplinary system that form the modern automobile. Thanks to the increased use of electronics and software in automobiles, consumers benefit from better gas mileage, more amenities and features, such as comfort, driving assistance, and entertainment. At the same time, stability and performance of automobiles as systems have been facing deterioration, and eventually vehicle owners are finding that features and functions become inoperative over time, causing frustration, loss of time and money. Reports of problems experienced by vehicle owners have stem from casual factors of system defects that model-based systems engineering can reduce or eliminate. This research presents a model-based systems engineering approach to an automobile electronic system design. The work is founded on a comprehensive OPM model and engineering guidelines for electronic control module software design. The purpose of the framework developed in this study is to support development of complex vehicle software that allows flexibility for changing features and creating new ones, and enables software developers to pinpoint systemic faults quicker and at earlier lifecycle phases, reducing rework, increasing safety, and providing for more effective resolution of such problems.
by Juan Manuel Quezada Gomez.
S.M. in Engineering and Management

APA, Harvard, Vancouver, ISO, and other styles

6

Webster, David D. "Hardware, software, firmware allocation of functions in systems development." Diss., Virginia Polytechnic Institute and State University, 1987. http://hdl.handle.net/10919/49907.

Full text

Abstract:

The top-down development methodology is, for the most part, a well defined subject. There is, however, one area of top-down development that lacks structure and definition. The undefined topic is the hardware, software, and firmware allocation of functions. This research addresses this deficiency in top-down system development. The key objective is the restructuring of the hardware, software, and firmware process from a subjective, qualitative decision process to a structured, quantitative one. Factors that affect the hardware, software, and firmware allocation process are identified. Qualitative data on the influence of the factors on the allocation process are systematized into quantitative information. This information is used to develop a model to provide a recommendation for implementing a function in hardware, software, or firmware. The model applies three analytical methods: 1) the analytic hierarchy process, 2) the general linear model, and 3) the second order regression technique. These three methods are applied to the quantified information of the hardware, software, firmware allocation process. A computer-based software tool is developed by this research to aid in the evaluation of the hardware, software, and firmware allocation process. The software support tool assists in data collection. Future application of the support tool will enable the capture and documentation of expert knowledge on the hardware, software, and firmware allocation process. The improved knowledge base can be used to improve the model which in tum will improve the system development process, and resulting system.
Ph. D.
incomplete_metadata

APA, Harvard, Vancouver, ISO, and other styles

7

Ramanath, Ana Maria. "The role of information systems development methods in interorganisational systems development." Thesis, Brunel University, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.289900.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Hui, S. C. "Software development of real-time distributed systems." Thesis, University of Sussex, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.375841.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Kelanti, M. (Markus). "Stakeholder analysis in software-intensive systems development." Doctoral thesis, Oulun yliopisto, 2016. http://urn.fi/urn:isbn:9789526213682.

Full text

Abstract:

Abstract A stakeholder analysis is commonly a part of the requirements engineering process in the development of software systems. It contributes to identifying, analysing, negotiating and validating requirements from multiple stakeholder viewpoints that do not necessary share the same views on a system under development and do not necessary express themselves using a similar language. Stakeholder analysis is often integrated into a used development method or practice and doesn’t necessarily appear as a separate process. The increase in software size, availability and use in different appliances, however, requires more from the stakeholder analysis than has been recognized in Software Engineering literature. The increasing scale of software systems and connections to other systems increase the number of involved stakeholders complicating the stakeholder analysis. In addition, how the actual stakeholder analysis should be implemented in large scale software development and how it supports the development effort is problematic in practice. The purpose of this thesis is to study the role and purpose of a stakeholder analysis in a large-scale software-intensive systems development. In this thesis, an empirical approach is taken to study the large-scale software-intensive systems development as phenomena in order to observe it as a whole. This approach allows this thesis to analyse the phenomena from different perspectives in order to identify and describe the nature and purpose of a stakeholder analysis in large-scale software-intensive systems development. The contribution of this thesis is the following. First, the thesis contributes to both the practical and scientific community by describing the role of stakeholder analysis in the software-intensive systems development process. Secondly, it demonstrates how a stakeholder analysis can be implemented in a large-scale software-intensive systems development process
Tiivistelmä Sidosryhmäanalyysi on yleensä osa vaatimusmäärittelyprosessia ohjelmistojärjestelmien kehityksessä. Se edesauttaa vaatimusten tunnistamista, analysointia, sopimista ja vahvistamista useiden eri sidosryhmien näkökulmasta tilanteissa, missä eri sidosryhmät eivät välttämättä jaa samaa näkökulmaa kehitettävään järjestelmään ja eivät välttämättä käytä samaa kieltä ilmaistakseen itseään. Sidosryhmäanalyysi on usein integroitu suoraan käytettyyn kehitysmenetelmään tai käytäntöön ja ei välttämättä ilmene erillisenä prosessina. Ohjelmiston koon kasvaessa ja yhteyksien lisääntyminen yhä useampiin laitteisiin on johtanut tilanteeseen, missä sidosryhmäanalyysilta vaaditaan yhä enemmän kuin kirjallisuudessa on aiemmin tunnistettu. Ohjelmistojärjestelmien alati kasvava koko ja yhteyksien lisääntyminen muihin järjestelmiin kasvattaa sidosryhmien määrää vaikeuttaen sidosryhmäanalyysin tekemistä. Lisäksi on ongelmallista, että miten sidosryhmäanalyysin tulisi tukea suuren mittakaavan ohjelmistotuotantoa ja miten se käytännössä toteutetaan tällaisessa ympäristössä. Tämän väitöskirjan tavoitteena on tutkia sidosryhmän roolia ja tarkoitusta suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Tutkimus on toteutettu empiirisellä lähestymistavalla tarkkailemalla suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotantoa kokonaisuutena. Tämä lähestymistapa mahdollistaa kokonaisuuden analysoinnin eri näkökulmista, jotta sidosryhmäanalyysin luonne ja tarkoitus voidaan tunnistaa ja kuvata suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Väitöskirjan tulosten kontribuutio jakautuu kahteen osaan. Ensimmäiseksi väitöskirjan tulokset auttavat sekä tiedeyhteisöä ja käytännön työtä tekeviä kuvaamalla sidosryhmäanalyysin suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Toiseksi tulokset havainnollistavat miten sidosryhmäanalyysi voidaan toteuttaa suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotekehitysprosessissa

APA, Harvard, Vancouver, ISO, and other styles

10

Rathor, Shekhar. "Facilitators for Software Development Agility." FIU Digital Commons, 2016. http://digitalcommons.fiu.edu/etd/3059.

Full text

Abstract:

Software development methodologies provide guidelines and practices for developing information systems. They have evolved over time from traditional plan-driven methodologies to incremental and iterative software development methodologies. The Agile Manifesto was released in 2001, which provides values and principles for agile software development. Over the last few years, agile software development has become popular because its values and principles focus on addressing the needs of contemporary software development. IT and Business teams need agility to deal with changes that can emerge during software development due to changing business needs. Agile software development practices claim to provide the ability to deal with such changes. Various research studies have identified many factors/variables that are important for agile software development such as team autonomy, communication, and organizational culture. Most of these empirical studies on agile software development focus on just a few variables. The relationships among the variables is still not understood. The dimensions of agility and the relationship between agility and other variables have not been studied quantitatively in the literature. Also, there is no comprehensive framework to explain agile software development. This research study addresses these research gaps. This study analyzed a comprehensive research model that included antecedent variables (team autonomy, team competence), process variables (collaborative decision making, iterative development, communication), delivery capability, agility, and project outcomes (change satisfaction, customer satisfaction). It presents key dimensions of agility and quantitatively analyzes the relationship between agility and other variables. The PLS analysis of one hundred and sixty survey responses show that process variables mediate the relationship between antecedent variables and delivery capability and agility. The findings show that the delivery capability of the teams contributes to agility, antecedents and process variables contribute to agility, and delivery capability for better customer satisfaction. These results will help IS practitioners to understand the variables that are necessary to achieve agility for better project outcomes. Also, these quantitative findings provide better conceptual clarity about the relationship between various key variables related to agile software development.

APA, Harvard, Vancouver, ISO, and other styles

11

Mäkäräinen, Minna. "Software change management processes in the development of embedded software /." Espoo [Finland] : Technical Research Centre of Finland, 2000. http://www.vtt.fi/inf/pdf/publications/2000/P416.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Carroll, Don, Craig Miller, and Don Nickens. "An Object-Oriented Systems Analysis and Design Technique for Telemetry Systems." International Foundation for Telemetering, 1995. http://hdl.handle.net/10150/611496.

Full text

Abstract:

International Telemetering Conference Proceedings / October 30-November 02, 1995 / Riviera Hotel, Las Vegas, Nevada
Object Oriented techniques have been successfully applied to all phases of software development including Requirements Analysis, Design, and Implementation. There has been some reluctance to extend the Object paradigm into the System Analysis, Architecture Development, and System Design phases. This is due to reasons generally related to technology immaturity and concerns with applicability. Telemetry systems in particular appear to be somewhat slow in embracing object technology. The Range Standardization and Automation program has integrated proven techniques to successfully produce an Object-oriented Systems Model. This paper presents the techniques and benefits.

APA, Harvard, Vancouver, ISO, and other styles

13

Paes, Carlos Eduardo de Barros. "RUP extension for development of distributed systems." Instituto Tecnológico de Aeronáutica, 2008. http://www.bd.bibl.ita.br/tde_busca/arquivo.php?codArquivo=528.

Full text

Abstract:

The increasing number of distributed systems results from the progress of computing and communication technology. This progress contributed to the expansion of Internet, increasing both availability and decentralization of the storage and processing. Nowadays the development of mature software for those systems is accomplished through the use of good practices of software engineering. The software engineering discipline provides processes, methods, techniques and tools that allow a suitable organization of the development process, as well as a quality result. Security, performance and fault tolerance are considered essential requirements for distributed systems. In this way, it is important that during the system development that these quality requirements be considered from the initial to end phases of software development lifecycle. Most of the software development processes were proposed before this understanding and they do not provide appropriate support for the development of distributed systems yet. RUP (Rational Unified Process) is a well-known software engineering process that provides a disciplined approach to assigning tasks and responsibilities; however, it has little support for development of distributed systems. The proposal of this work is to propose an extension to RUP for the development of distributed systems. In this proposal we considered security, fault tolerance and performance as important aspects of distributed systems design. All these aspects are embodied in RUP as a knowledge area (discipline), named distributed systems, with activities and roles defined according to the architecture of process engineering UMA (Unified Method Architecture). Examples were elaborated to clarify and show the feasibility of the proposal for both each knowledge areas and all the knowledge areas.

APA, Harvard, Vancouver, ISO, and other styles

14

Kayongo, Patrick. "Why do software developers practice test-driven development?" Master's thesis, University of Cape Town, 2016. http://hdl.handle.net/11427/20417.

Full text

Abstract:

This dissertation describes research that has been undertaken to understand factors influencing software developers' intention to perform test driven development (TDD). Unit tests are a form of testing, where tests are written for small units of software being developed. TDD is a practice where these tests are written before the functionality is written, so as to guide the design of the code for the functionality, as well as to ensure test coverage for all functionality. There has been some research conducted to understand TDD by looking at its effects on both the outcomes and the practice of software development. It has been found to increase quality by decreasing defects, while also increasing the maintainability and the changeability of the code. On the other hand, some research has also found it to increase time spent on completing tasks. Despite this, to the best of the researcher's knowledge, there hasn't been research done to understand the behavioural components of TDD, and in particular, why developers choose to practice TDD. A conceptual model based on the Theory of Planned Behaviour (TPB) is described and used as a lens to understand intention. TPB proposes that intention to perform a behaviour (TDD in this case) is influenced by three factors: attitude towards the behaviour, subjective norm, and perceived behavioural control. This dissertation seeks to build onto this model for the purpose of understanding TDD, and proposes the following determinants of the influences of intention: attitude is influenced by attitude towards time taken, differences in quality, maintainability and developer efficiency; subjective norm is influenced by the perceived perception of the environment regarding changes in quality, time taken, and maintainability of the code. Lastly, perceived behavioural control is posited to be made up of perceived difficulty of TDD, and how much experience a developer has. This model is then tested based on data collected from a n online survey distributed around the world. 779 responses were collected from developers in various countries around the world. The majority of the respondents to practice TDD, allowing us to gain greater insight into why those that practice TDD actually do so. Because the study is a psychographic study, perceptions were understood from the developers using an ordinal Likert scale. To analyse this data in order to prove the hypotheses, Chi -¬‐ square tests with contingency tables, Kruskal -¬‐ Wallis tests and ordinal logistic regression were used as statistical methods. It is found the data collected does not conform to the model, and recommendations are made for a future study to form a more comprehensive model.

APA, Harvard, Vancouver, ISO, and other styles

15

Zhang, Meishenglan. "Power-Aware Software Development For EMCA DSP." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-215711.

Full text

Abstract:

The advent of FinFET technology necessitates a shift towards early dynamic power awareness, not only for ASIC block designers but also for software engineers that develop code for those blocks. CMOS dynamic power is typically reduced by optimizing the RTL models in terms of switching activity and clock gating efficiency. There is not much to be done after a model is committed. Programmable blocks though, like the Phoenix 4 Digital Signal Processor(EMCA Ericsson Multi Core Architecture), can have a “second chance” for low power even after silicon is produced by efficient use of the software source code in order to impact the dynamic power metrics. This requires a "full-stack" of power awareness all the way from the DSP hardware model up to the software development IDE. This Thesis work aims at two goals. The first goal is to realize a prototype, encapsulated flow for the DSP software developers which connects software IDE entry point to the low level, complex hardware power analysis tools. The second goal is to demonstrate how software can be used as an auxiliary knob to exploit potential tradeoffs in order to improve the DSP's dynamic power metrics. This hypothesis is tested by rescheduling operations on the DSP's resources either manually or implicitly through the compiler. Moreover, a method to align and compare algorithms, when it is possible to tradeoff performance for power, is devised and the estimation results are compared against real silicon measurements. The results show that the developed analysis flow is reliable and very efficient for the given purpose, even for people who have limited knowledge about low level hardware to facilitate quick power exploration and profiling. This is mainly realized by a unique feature that associates specific lines in the source code with the toggling behavior of the hardware model while execution. Based on that, the tradeoffs between power and performance for several testcases are demonstrated at both the assembly and C levels with good correlation versus silicon. Overall, this work's outcome hints that the compiler and software teams have many options to consider in order to optimize dynamic power for products already in the field.

APA, Harvard, Vancouver, ISO, and other styles

16

Demir, Kadir Alpaslan. "Analysis of TLcharts for weapon systems software development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2005. http://library.nps.navy.mil/uhtbin/hyperion/05Dec%5FDemir.pdf.

Full text

Abstract:

Thesis (M.S. in Computer Science and M.S. in Software Engineering)--Naval Postgraduate School, December 2005.
Thesis Advisor(s): Doron Drusinsky, Man-Tak Shing. Includes bibliographical references (p. 87-89). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

17

Alegre-Ibarra, Unai. "A software development framework for context-aware systems." Thesis, Middlesex University, 2018. http://eprints.mdx.ac.uk/25480/.

Full text

Abstract:

The beginning of the new century has been characterised by the miniaturisation and accessibility of electronics, which has enabled its widespread usage around the world. This technological background is progressively materialising the future of the remainder of the century, where industry-based societies have been moving towards information-based societies. Information from users and their environment is now pervasively available, and many new research areas have born in order to shape the potential of such advancements. Particularly, context-aware computing is at the core of many areas such as Intelligent Environments, Ambient Intelligence, Ambient Assisted Living or Pervasive Computing. Embedding contextual awareness into computers promises a fundamental enhancement in the interaction between computers and humans. While traditional computers require explicit commands in order to operate, contextually aware computers could also use information from the background and the users to provide services according to the situation. But embedding this contextual awareness has many unresolved challenges. The area of context-aware computing has attracted the interest of many researchers that have presented different approaches to solve particular aspects on the implementation of this technology. The great corpus of research in this direction indicates that context-aware systems have different requirements than those of traditional computing. Approaches for developing context-aware systems are typically scattered or do not present compatibility with other approaches. Existing techniques for creating context-aware systems also do not focus on covering all the different stages of a typical software development life-cycle. The contribution of this thesis is towards the foundation layers of a more holistic approach, that tries to facilitate further research on the best techniques for developing these kinds of systems. The approach presents a framework to support the development not only with methodologies, but with open-source tools that facilitate the implementation of context-aware systems in mobile and stationary platforms.

APA, Harvard, Vancouver, ISO, and other styles

18

Jabangwe, Ronald. "Software Quality Evaluation for Evolving Systems in Distributed Development Environments." Doctoral thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00613.

Full text

Abstract:

Context: There is an overwhelming prevalence of companies developing software in global software development (GSD) contexts. The existing body of knowledge, however, falls short of providing comprehensive empirical evidence on the implication of GSD contexts on software quality for evolving software systems. Therefore there is limited evidence to support practitioners that need to make informed decisions about ongoing or future GSD projects. Objective: This thesis work seeks to explore changes in quality, as well as to gather confounding factors that influence quality, for software systems that evolve in GSD contexts. Method: The research work in this thesis includes empirical work that was performed through exploratory case studies. This involved analysis of quantitative data consisting of defects as an indicator for quality, and measures that capture software evolution, and qualitative data from company documentations, interviews, focus group meetings, and questionnaires. An extensive literature review was also performed to gather information that was used to support the empirical investigations. Results: Offshoring software development work, to a location that has employees with limited or no prior experience with the software product, as observed in software transfers, can have a negative impact on quality. Engaging in long periods of distributed development with an offshore site and eventually handing over all responsibilities to the offshore site can be an alternative to software transfers. This approach can alleviate a negative effect on quality. Finally, the studies highlight the importance of taking into account the GSD context when investigating quality for software that is developed in globally distributed environments. This helps with making valid inferences about the development settings in GSD projects in relation to quality. Conclusion: The empirical work presented in this thesis can be useful input for practitioners that are planning to develop software in globally distributed environments. For example, the insights on confounding factors or mitigation practices that are linked to quality in the empirical studies can be used as input to support decision-making processes when planning similar GSD projects. Consequently, lessons learned from the empirical investigations were used to formulate a method, GSD-QuID, for investigating quality using defects for evolving systems. The method is expected to help researchers avoid making incorrect inferences about the implications of GSD contexts on quality for evolving software systems, when using defects as a quality indicator. This in turn will benefit practitioners that need the information to make informed decisions for software that is developed in similar circumstances.

APA, Harvard, Vancouver, ISO, and other styles

19

Thipphayathetthana, Somwang. "Model-based guidelines for user-centric satellite control software development." Thesis, Massachusetts Institute of Technology, 2015. http://hdl.handle.net/1721.1/105320.

Full text

Abstract:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, 2015.
Cataloged from PDF version of thesis.
Includes bibliographical references (page 45).
Three persistent common problems in satellite ground control software used by satellite controllers are obsolescence, lack of desired features and flexibilities, and endless software bug fixing. The obsolescence problem occurs when computer and ground equipment hardware become obsolete usually after only one third into the satellite mission lifetime. The satellite ground control software needs to be updated to accommodate changes on the hardware side, requiring significant work of satellite operators to test, verify, and validate these software updates. Software updates can also result from a new software version that offers new features or just fixes some bugs. Trying to help solve these problems, an OPM model and guidelines for developing satellite ground control software have been proposed. The system makes use of a database-driven application and concepts of object-process orientation and modularity. In the new proposed framework, instead of coding each software function separately, the common base functions will be coded, and combining them in various ways will provide the different required functions. The formation and combination of these base functions will be governed by the main code, definitions, and database parameters. These design principles will make sure that the new software framework would provide satellite operators with the flexibility to create new features, and enable software developer to find bugs quicker and fix them more effectively.
by Somwang Thipphayathetthana.
S.M. in Engineering and Management

APA, Harvard, Vancouver, ISO, and other styles

20

Anton, Ana I. "Goal identification and refinement in the specification of software-based information systems." Diss., Georgia Institute of Technology, 1997. http://hdl.handle.net/1853/8130.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Nivoit, Jean-Baptiste (Jean-Baptiste Henri). "Issues in strategic management of large-scale software product line development." Thesis, Massachusetts Institute of Technology, 2013. http://hdl.handle.net/1721.1/90607.

Full text

Abstract:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2013.
This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
Cataloged from student-submitted PDF version of thesis.
Includes bibliographical references (pages 159-163).
This thesis reflects on the issues and challenges large software product engineering managers face. Software is hard to engineer on a small scale, but at a larger scale, engineering and management tasks are even more difficult. In the context of software product line evolution, the goal of this work is to look at current managing practice, through the lens of Systems Thinking as well as my own experience. We develop a System Dynamics model to operationalize the notions examined here and run a variety of experiments representative of real situations, from which we learn some lessons and recommend policies that engineering leaders may use to manage large-scale software development organizations. During the course of this research, we found that the model developed intuitively matched experiences in the software industry. Product line engineering and tighter deadlines force software producers to require more accurate control of the production capability of their development organization. In the context of many release cycles and multiple simultaneously active releases, we present some findings about scheduling of the workload, which the engineering manager may leverage to make decisions about the allocation of work. The research presented here from the point of view of the producers of software can help other stakeholders in the software ecosystem understand the challenges these organizations face and the reasoning behind choices made by these providers.
by Jean-Baptiste Nivoit.
S.M. in Engineering and Management

APA, Harvard, Vancouver, ISO, and other styles

22

Graham, Cumming. "The formal development of secure systems." Thesis, University of Oxford, 1992. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.315747.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Gardner, Lesley Ann. "Hypermedia for prototyping and system integration in information systems development." Thesis, London School of Economics and Political Science (University of London), 1991. http://etheses.lse.ac.uk/1126/.

Full text

Abstract:

This thesis investigates information systems development with special regard to the area of Geographical Information Systems. It addresses the area through the investigation of the software life-cycle development model and its augmentation by the use of prototyping. Observations are made on empirical experiments conducted to assess the usefulness of the new techniques of hypertext and hypermedia and their suitability within this field of study. This investigation is complemented by a case study, the Norfolk and Suffolk Broads Authority. The Norfolk and Suffolk Broads are designated by statute with similar status to the National Parks of Great Britain, and are managed by the Norfolk and Suffolk Broads Authority. Through cooperation with the Norfolk and Suffolk Broads Authority, a prototype information system was created. This system makes use of geographical data from the Broads Authority. The development stages of this system were used to conduct experiments for this thesis. The tools and techniques used for the development of this system are described. These include a hypertext tool called FIELD (Fully Integrated Environment for Layered Development) which has been especially designed for the complete storage of all information for each stage throughout this development. The use of this tool and hypertext for the development of the geographically based information system for the Norfolk and Suffolk Broads Authority are discussed.

APA, Harvard, Vancouver, ISO, and other styles

24

Ng, Andrew Eng Jwee. "Switched-current filtering systems : design, synthesis and software development." Thesis, University of Glasgow, 1999. http://theses.gla.ac.uk/5040/.

Full text

Abstract:

Allpass filters are commonly employed in many applications to perform group delay equalisation in the passband. They are non-minimum phase by definition and are characterised by poles and zeros in mirror-image symmetry. SI allpass filters of both cascade biquad and bilinear-LDI ladder types have been in existence. These were implemented using Euler based integrators. Cascade biquads are known to have highly sensitive amplitude responses and Euler integrators suffer from excess phase. The equalisers that are proposed here are based on bilinear integrators instead of Euler ones. Derivation of these equalisers can proceed from either the s-domain, or directly from the z-domain, where a prototype is synthesised using the respective continued-fractions expansions, and simulated using standard matrix methods. The amplitude response of the bilinear allpass filter is shown to be completely insensitive to deviations in the reactive ladder section. Simulations of sensitivities and non-ideal responses reveal the advantages and disadvantages of the various structures. Existing DI multirate filters have to date been implemented as direct-form FIR and IIR polyphase structures, or as simple cascade biquad or ladder structures with non-optimum settling times. FIR structures require a large number of impulse coefficients to realise highly selective responses. Even in the case of linear phase response with symmetric impulse coefficients, when the number of coefficients can be halved, significant overheads can be incurred by additional multiplexing circuitry. Direct-form IIR structures are simple but are known to be sensitive to coefficient deviations and structures with non-optimum settling times operate entirely at the higher clock frequency. The novel SI decimators and interpolators proposed are based on low sensitivity ladder structures coupled with FIR polyphase networks. They operate entirely at the lower clock frequency which maximises the time available for the memory cells to settle. Two different coupling architectures with different advantages and disadvantages are studied.

APA, Harvard, Vancouver, ISO, and other styles

25

Sato, Yoshikazu. "Software package and vendor selection for corporate systems development." Thesis, Massachusetts Institute of Technology, 1997. http://hdl.handle.net/1721.1/10150.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Seth, Deepak. "A platform based approach for embedded systems software development." Thesis, Massachusetts Institute of Technology, 2006. http://hdl.handle.net/1721.1/35092.

Full text

Abstract:

Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2006.
Includes bibliographical references (leaves 94-96).
A platform based approach for product development allows companies to eliminate redundancies, efficiently utilize its resources and provide products for a wider market. The basic idea is to develop and share key components and to introduce new technologies in as many products as possible. The automobile industry has for long used the concept of product platforms and has successfully achieved savings in development costs and seen a growth in sales and market share. By creating a common software platform, this concept can be applied to software development for embedded systems where software modules and applications can be shared across products within a product family. This provides better code reuse and increases standardizations across products. This thesis will examine how the concept of platforms can be applied to software development from the viewpoint of the telecommunications industry. By using the power of a common software platform, telecommunication equipment makers can accelerate product delivery and introduce new technologies to a wider range of customers. With the right strategy, they can also make their products into platforms that serve as a foundation on which other companies can develop products and offer their services.
by Deepak Seth.
S.M.

APA, Harvard, Vancouver, ISO, and other styles

27

Gibson, J. Paul. "Formal object oriented development of software systems using LOTOS." Thesis, University of Stirling, 1993. http://hdl.handle.net/1893/24014.

Full text

Abstract:

Formal methods are necessary in achieving correct software: that is, software that can be proven to fulfil its requirements. Formal specifications are unambiguous and analysable. Building a formal model improves understanding. The modelling of nondeterminism, and its subsequent removal in formal steps, allows design and implementation decisions to be made when most suitable. Formal models are amenable to mathematical manipulation and reasoning, and facilitate rigorous testing procedures. However, formal methods are not widely used in software development. In most cases, this is because they are not suitably supported with development tools. Further, many software developers do not recognise the need for rigour. Object oriented techniques are successful in the production of large, complex software systems. The methods are based on simple mathematical models of abstraction and classifi cation. Further, the object oriented approach offers a conceptual consistency across all stages of software development. However, the inherent flexibility of object oriented approaches can lead to an incremental and interactive style of development, a consequence of which may be insuffi cient rigour. This lack of rigour is exacerbated by the inconsistent and informal semantics for object oriented concepts at all stages of development. Formal and object oriented methods are complementary in software development: object oriented methods can be used to manage the construction of formal models and formality can add rigour to object oriented software development. This thesis shows how formal object oriented development can proceed from analysis and requirements capture to design and implementation. A formal object oriented analysis language is defined in terms of a state transition system semantics. This language is said to be customer-oriented: a number of graphical views of object oriented relations in the formal analysis models are presented, and the specifi cations produced say what is required rather than how the requirements are to be met. A translation to ACT ONE provides an executable model for customer validation. This translation is founded on a precise statement of the relationship between classes and types (and subclassing and subtypes). The structure of the resulting ACT ONE requirements model corresponds to the structure of the problem domain, as communicated by the customer. The step from analysis to design requires an extension to the requirements model to incorporate semantics for object communication. A process algebra provides a suitable formal model for the specifi cation of communication properties. LOTOS, which combines ACT ONE and a process algebra in one coherent semantic model, provides a means of constructing object oriented design semantics. Design is de fined as the process of transforming a customer-oriented requirements model to an implementation-oriented design, whilst maintaining correctness. Correctness preserving transformations (CPTs) are defined for: transferring requirements structure to design structure, manipulating design structure and changing internal communication models. Design must be targetted towards a particular implementation environment. The thesis examines a number of different environments for the implementation of object oriented LOTOS designs. It illustrates the importance of understanding programming language semantics. We show how Eiffel can be used to implement formal object oriented designs. A case study which evaluates the formal object oriented models and methods, developed in this thesis, is reported. This identifi es re-use at all stages of software development and emphasises the role of structure: it improves understanding and communication, and makes validation and veri fication easier and better. The thesis shows that formal object oriented technology is ready for transfer to industry. These methods should be exploited sooner rather than later: object oriented development can incorporate formal methods without signi ficant cost, and formal methods can utilise the object oriented paradigm to manage complexity. The thesis provides a rationale for formal object oriented development and a set of conceptual tools which makes the development of software systems a true engineering discipline.

APA, Harvard, Vancouver, ISO, and other styles

28

Nikolaidis, Fotios. "Tromos : a software development kit for virtual storage systems." Thesis, Université Paris-Saclay (ComUE), 2019. http://www.theses.fr/2019SACLV033/document.

Full text

Abstract:

Les applications modernes ont des tendances de diverger à la fois le profile I/O et les requiers du stockage. La liaison d'une application scientifique ou commerciale avec un system "general-purpose" produit probablement un résultât sous-optimale. Même sous la présence des systèmes "purpose specific" des application aux classes multiples de workloads ont encore besoin de distribuer du travail de calcul au correct system. Cependant, cette stratégie n'est pas triviale comme des plateformes différentes butent diversifier leur propos et par conséquence elles requièrent que l'application intégrée des chemins multiples de code. Le but de l'implémentation de ces chemins n'est pas trivial, il requiert beaucoup d'effort et des capacités de codage. Le problème devient vaste quand les applications ont besoin de bénéficier de plusieurs data-stores en parallèle. Dans cette dissertation, on va introduire les "storage containers" comme le prochain étape logique, mais révolutionnaire. Un "storage container" est une infrastructure virtuelle qui découple une application de ses data-stores correspondants avec la même manière que Docker découple l'application runtime des servers physiques. En particulier, un "storage container" est un middleware qui sépare des changements fait pour bouts de code des application par des utilisateurs scientifiques, de celui fait pour des actions de I/O par des développeurs ou des administrateurs.Pour faciliter le développement et déploiement d'un "storage container" on va introduire un cadre appelé Tromos. Parmi son filtre, tout qui est nécessaire pour qu'un architecte d'une application construite une solution de stockage est de modéliser l'environnement voulu dans un fichier de définition and laisser le reste au logiciel. Tromos est livré avec un dépôt de plugins parmi les quelles l'architecte peut choisir d'optimiser le conteneur pour l'application activée. Parmi des options disponibles, sont inclus des transformations des données, des politiques de placement des données, des méthodes de reconstruction des données, du management d'espace de noms, et de la gestion de la cohérence à la demande. Comme preuve de concept, on utilisera Tromos pour créer des environnements de stockage personnalisés facilement comparés à Gluster, un système de stockage bien établi et polyvalent. Les résultats vous montrent que les "storage containers" adaptés aux applications, même s'ils sont auto-produits, peuvent surpasser les systèmes "general purpose" les plus sophistiqués en supprimant simplement la surcharge inutile de fonctionnalités factices
Modern applications tend to diverge both in the I/O profile and storage requirements. Matching a scientific or commercial application with a general-purpose system will most likely yield suboptimal performance. Even in the presence of purpose-specific' systems, applications with multiple classes of workloads are still in need to disseminate the workload to the right system. This strategy, however, is not trivial as different platforms aim at diversified goals and therefore require the application to incorporate multiple codepaths. Implementing such codepaths is non-trivial, requires a lot of effort and programming skills, and is error-prone. The hurdles are getting worse when applications need to leverage multiple data-stores in parallel. In this dissertation, we introduce "storage containers" as the next logical in the storage evolution. A "storage container" is virtual infrastructure that decouples the application from the underlying data-stores in the same way Docker decouples the application runtime from the physical servers. In other words, it is middleware that separate changes made to application codes by science users from changes made to I/O actions by developers or administrators.To facilitate the development and deployment of a "storage container" we introduce a framework called Tromos. Through its lens, all that it takes for an application architect to spin-up a custom storage solution is to model the target environment into a definition file and let the framework handles the rest. Tromos comes with a repository of plugins which the architect can choose as to optimize the container for the application at hand. Available options include data transformations, data placement policies, data reconstruction methods, namespace management, and on-demand consistency handling.As a proof-of-concept we use Tromos to prototype customized storage environments which we compare against Gluster; a well-estalished and versatile storage system. The results have shown that application-tailored "storage containers", even if they are auto-produced, can outperform more mature "general-purpose" systems by merely removing the unnecessary overhead of unused features

APA, Harvard, Vancouver, ISO, and other styles

29

Shams, Siamak. "Information systems : operationalization of agile software development 2003 – 2007." Thesis, Brunel University, 2007. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.556992.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Teo, Ching Leong. "Bistatic radar system analysis and software development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03Dec%5FTeo%5FChing.pdf.

Full text

Abstract:

Thesis (M.S. in Engineering Science)--Naval Postgraduate School, December 2003.
Thesis advisor(s): David C. Jenn, D. Curtis Schleher. Includes bibliographical references (p. 95-96). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

31

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

Full text

Abstract:

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

APA, Harvard, Vancouver, ISO, and other styles

32

Taborga, Jorge. "Toward Adaptive Stage Development in Software Scrum Teams." Thesis, Saybrook University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10930703.

Full text

Abstract:

Over the last 70 years, teams have become the ubiquitous unit of work in our organizations. The software industry heavily utilizes the Scrum methodology to develop software. Scrum is a team-based methodology that requires the constant formation and development of team capabilities. Researchers and practitioners dealing with work team dynamics have relied on the popular team developmental stages of forming, storming, norming, and performing, defined by Dr. Bruce Tuckman in 1965. However, this framework was conceived primarily from articles dealing with therapy groups and not modern teams. This study expands the body of research in work team stage development applied to Scrum, a methodology that itself has no social science foundation and minimal theoretical coverage.

A combined case study and grounded theory method is used to leverage the strengths of both to investigate the developmental stage of 5 Scrum teams at a high-tech company. A questionnaire along with team interviews were utilized to gather data on how teams relate to developmental factors found in the literature. Descriptive analytics were leveraged to uncover the questionnaire findings, and grounded theory analysis was applied to code interview answers into usable concepts, categories, and themes. Themes were further explored concerning their causal relationships.

The study proposed and validated 12 theoretical factors that contribute to the stage development of Scrum teams across 4 distinct stages. These factors interconnect and form 4 quadrants with unique dynamics associated with a team’s mission, structure, execution, and teaming. Furthermore, higher stage teams proved to be self-managed and adaptable and able to handle higher task complexity. Leaders were observed shifting roles as teams evolved through stages. This latter finding is consistent with the theoretical model of Kozlowski, Watola, Jensen, Kim, and Botero. The research also identified common challenges that teams encounter in their development.

The findings from this study can help organizations who practice Scrum become more intentional about the development of their teams toward adaptability. A concerted effort by software organizations to optimize the evolution of teams across the factors found in the study could yield significant benefits, particularly for missions dealing with high complexity and innovation needs.

APA, Harvard, Vancouver, ISO, and other styles

33

Rangevik, Alexander. "Software Development across Time Zones : A Study of Globally Distributed Software Development in Small Enterprises." Thesis, Uppsala universitet, Informationssystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-203325.

Full text

Abstract:

Globally distributed software development has become an important topic for small and medium enterprises. However, the distinct requirements of small and medium enterprises (SMEs) are still not fullyunderstood. To contribute to this growing discussion, I will present an ethnographical field study of a Swedish software company engaged in a distributed development practice with its American branch. By applying a theoretical view based on communication, coordination and control over time, space and socio/cultural difference, I show to what extent a distributed software development model affects SMEs. Whereproblems related to formal and informal communication, knowledge sharing, articulation work and programming methodologies are discussed. My findings suggest that organizational adjustments are needed for SMEs in order to take advantage of distributed software development (DSD), that specialized tools supporting coordination and articulation work is not so common in practice and that certain adjustment to agile methodologies could be made in order to better support DSD.

APA, Harvard, Vancouver, ISO, and other styles

34

Martin, Timothy Patrick. "Flexible manufacturing system software development using simulation." Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/101236.

Full text

Abstract:

This paper presents a hierarchical modeling method that can be used to simulate a Flexible Manufacturing System (FMS) at all levels of detail. The method was developed specifically to aid the software development needed for the hierarchy of computers that are present in an FMS. The method was developed by modeling an existing FMS. The models developed of the existing FMS are described in detail to provide an example of how to model other FMSs. The basic building blocks needed for designing other FMSs with this modeling method are provided. The models were written in the SIMAN simulation language. SIMAN was found to be an easy language to use for the hierarchical modeling of FMSs.
M.S.

APA, Harvard, Vancouver, ISO, and other styles

35

Saleh, Mehdi. "Built-in software quality in Agile development." Thesis, Uppsala universitet, Institutionen för informatik och media, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-413344.

Full text

Abstract:

Abstract Waterfall and Agile are the two most popular software development methodologies. Waterfall as the traditional one, is a progressive method. The progress flows in one direction, and upon the completion of previous process. Agile is another software development methodology with more iterative approach and possible change of requirements; with incremental delivery. Agile introduces freedom to requirement change and iterative delivery. However, such a liberty should not disrate software quality. Especially in automotive industry that deals with human safety and security. In such an iterative environment, there is a higher risk to compromise on quality checks before each delivery, due to short intense lead times. There will not be enough time for intensive quality assurance activities after each iteration. The solution to downsize the intensive quality check after each iteration, is to improve development quality during the development and building quality into development processes. This is what we refer as “Built-in quality”; the quality that is built during software artefacts development on a continuous basis. This study conducted at Volvo Cars during Agile transformation time and the main objective was to connect and emphasize the importance of built-in quality in agile software development. In this study we look at existing challenges that decrease quality of software artifacts during the development. Thus, by prevailing those challenges we can improve the software quality during iteration delivery. Such an improvement decreases the amount of intensive quality check after each iteration. Additionally, we look at guidelines and tools that used by different development teams to improve software artifacts’ quality. We also investigate how quality assurance engineer can support builtin quality during agile transformation.

APA, Harvard, Vancouver, ISO, and other styles

36

Begic, Amela, and Malin Almstedt. "Hur används Lean Software Development i praktiken?" Thesis, Örebro universitet, Handelshögskolan vid Örebro Universitet, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-85800.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Aslam, Gulshan, and Faisal Farooq. "A comparative study on Traditional Software Development Methods and Agile Software Development Methods." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsområde Informationsteknik, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-15383.

Full text

Abstract:

Everyone is talking about the software development methods but these methods are categorised into the different parts and the most important are two categories, one is agile software development methods and second is using the traditional software development methods. Agile software methods are relatively considered to be quick and for the small teams. Our main mission is to check which method is better from each other, so for that purpose we go out in the software development market to meet the professional to ask about their satisfaction on these software development methods. Our research is based on to see the suitable method for the professionals; see the challenges on the adoptability of methods and which method is quicker. To perform this study we have gone through a survey questionnaire, and results are analysed by using mixed method approach. Results shows that professionals from both types of methods are satisfied but professionals with traditional methods are more satisfy with their methods with respect to development of quality software, whereas agile professionals are more satisfied with their methods with respect of better communication with their customers. With agility point of view, our study says that both methods have characteristics which support agility but not fully support, so in such case we need to customize features from both types of methodologies.

APA, Harvard, Vancouver, ISO, and other styles

38

Court, Cliff. "A new estimation methodology for reusable component-based software development projects." Master's thesis, University of Cape Town, 1999. http://hdl.handle.net/11427/9708.

Full text

Abstract:

Bibliograhy: leaves 118-121.
Estimating the duration of software development projects is a difficult task. There are many factors that can derail software projects. However, estimation forms the fundamental part of planning and costing any project and is therefore very necessary. While several formal estimation methodologies exist, they all exhibit weaknesses in one form or another. The most established methodologies are based on early software development methods and it is questionable as to whether they can still address more modern development methods such as reusable component-based programming. Some researchers believe not and have proposed new methodologies that attempt to achieve this. Thus what is needed is a methodology that takes into account modern component-based development practices and, as a result, provides acceptable accuracy for the software organisation. This dissertation attempts to uniquely satisfy both of these requirements.

APA, Harvard, Vancouver, ISO, and other styles

39

Yu, Angus Gonghua. "Managing application software suppliers in information system development projects." Thesis, University of Stirling, 2000. http://hdl.handle.net/1893/3450.

Full text

Abstract:

Information system development (ISD) projects have been associated with the "software crisis" for over three decades. A set of common "root causes" has often been cited in literature with corresponding "solutions". Yet the overall project success rate has remained low, resulting in a paradox of many solutions and little progress over the years. This study examines the management of application software acquisition from external suppliers in ISD projects. Three case studies are documented based on participant observation with complete membership roles. After within-case analyses highlighting issues in individual cases, crosscase analyses are conducted, first to identify a pattern of ISD project challenges and then to search for their explanations. Concepts from agency theory, contract theory and product development literature are used in the process of diagnosing root causes behind the observations. The proposed explanation is that the Traditional Systems Development Framework (TSDF), characterized by competitive-bidding-monopolized-development, underlies the identified root causes. Accordingly, competitive development is suggested as an alternative approach. Following the "Inference to the Best Explanation" (IBE) analytical strategy, the suggested approach is subject to two contrastive analyses, first with the prepackaged software development and then with the construction industry, to demonstrate that the suggestion is a "warranted inference". Further analogical analyses illustrate the feasibility of development competition for software product development. A Performance-Based Systems Development Framework (PBSDF) is outlined as a tentative implementation of the suggested competitive development approach for ISD projects supported by risk-sharing supplier contract and a relative product evaluation approach. A number of future research implications are described as a result of this study after summarizing the research contributions.

APA, Harvard, Vancouver, ISO, and other styles

40

Wani, John Rubena. "Project Managers’ Communication Strategies for Team Collaboration in Software Development." ScholarWorks, 2019. https://scholarworks.waldenu.edu/dissertations/7769.

Full text

Abstract:

Effective communication among team members in software development projects is increasingly significant for the success of the project. Successful software projects are the catalyst for achieving profitability objectives and creating shareholder value in organizations. The purpose of this single case study was to investigate communication strategies information technology (IT) project managers used for successful team collaboration in software development. The population for this study comprised senior IT project managers. The project managers had supervision responsibilities from a midsized IT company in Alberta, Canada. The sociotechnical theory guided this study as the conceptual framework. Data were collected from semistructured interviews with 13 senior IT project managers on their experiences using effective communication strategies for team collaboration. A review of 11 company documents was conducted. Using methodological triangulation and member checking of original interview transcripts served to establish the trustworthiness of final interpretations. Through thematic analysis, 4 significant themes emerged from the study: effective communication, attributes of communication, the importance of social and emotional intelligence, and the impact of postwork activities for team collaboration. The findings of this study might bring about positive change by supporting senior project managers use of communication strategies for team collaborations in midsize IT companies to increase job satisfaction and project completion.

APA, Harvard, Vancouver, ISO, and other styles

41

Singh, Krishna Devi. "The development of biomagnetic systems : planar gradiometers and software tools." n.p, 1991. http://oro.open.ac.uk/19786/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Sentilles, Séverine. "Towards Efficient Component-Based Software Development of Distributed Embedded Systems." Licentiate thesis, Mälardalen University, School of Innovation, Design and Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-7368.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Singh, K. D. "The development of biomagnetic systems : planar gradiometers and software tools." Thesis, Open University, 1991. http://oro.open.ac.uk/19786/.

Full text

Abstract:

This thesis is concerned with two aspects of the design and construction of biomagnetic systems. Firstly, it considers the optimum design of planar gradiometers. The modelling of gradiometers is discussed and an algorithm for optimising the sensitivity of a specific type of gradiometer is presented. A test thin-film procedure for the manufacture of a planar gradiometer is outlined. The performance of three different types of gradiometer in recovering test current distributions, using a distributed current analysis technique, is assessed. Secondly, four major software tools that are essential in the analysis of data from large multi-channel biomagnetic systems are presented. These tools are then used to analyze data from a visual evoked response experiment. The system used to collect data was the Helsinki multi-channel system which consists of 24 planar gradiometers. The results confirm the retinotopic mapping of visual field information, and suggest that the time evolution of activity in different parts of the visual cortex is similar for early latencies.

APA, Harvard, Vancouver, ISO, and other styles

44

Santos, Rodrigo Augusto Silva dos. "Towards an SDLC for software development projects involving distributed systems." Pontif?cia Universidade Cat?lica do Rio Grande do Sul, 2016. http://tede2.pucrs.br/tede2/handle/tede/6830.

Full text

Abstract:

Submitted by Setor de Tratamento da Informa??o - BC/PUCRS (tede2@pucrs.br) on 2016-07-14T16:42:02Z No. of bitstreams: 1 DIS_RODRIGO_AUGUSTO_SILVA_DOS_SANTOS_COMPLETO.pdf: 4285051 bytes, checksum: b4430aa54c46e6ecf90c0564e8668d1f (MD5)
Made available in DSpace on 2016-07-14T16:42:02Z (GMT). No. of bitstreams: 1 DIS_RODRIGO_AUGUSTO_SILVA_DOS_SANTOS_COMPLETO.pdf: 4285051 bytes, checksum: b4430aa54c46e6ecf90c0564e8668d1f (MD5) Previous issue date: 2016-03-10
[Context] Since the 1970?s, Distributed Systems have been turning into a more viable and reliable option for the implementation of information systems. Since then, their evolution continued in an accelerated pace. They now are applicable to a variety of purposes, such as online games, financial systems, cloud computational solutions, etc. It is possible then to assume that today, Distributed Systems are found everywhere, and that there is a great probability for any given in-progress software development project to be using this paradigm as part of its delivery proposal. Thus, it is relevant to study the impacts that Distributed Systems bring to the Project Management discipline. [Objectives] In this dissertation we discuss those impacts and challenges, as well as propose a Software Development Lifecycle (SDLC) and associated practices, both adapted for use within software development projects involving Distributed Systems. These practices are optimized for implementation under a Waterfall regime, but are also adaptable for use under the Scrum agile framework. [Method] At first a Systematic Mapping Study (SMS) was conducted for understanding the State-of-the-art regarding academic studies located in intersection of Project Management and Distributed Systems. Next, empirical qualitative interviews were held with members from the Information Technology Industry, aiming to confirm the SMS results as well as obtaining feedback regarding present day?s challenges of Distributed Systems Projects. Desirable countermeasures for these challenges were also being searched for. [Results] As a third and final step, a generic SDLC as well as its associated practices, both tailored for projects involving DS, were proposed in direct response to the results obtained from the qualitative interviews. The tailored practices constitute the backbone of our contributions. The presented proposals went through the process of memberchecking for validation and refinement, which led to the final version shown in this dissertation.
[Contexto] Desde os anos 1970, Sistemas Distribu?dos v?m se tornando em uma op??o cada vez mais vi?vel e confi?vel para a implementa??o de sistemas de informa??o. Desde ent?o, a evolu??o destes sistemas continuou em um ritmo acelerado. Eles atualmente s?o aplic?veis a uma variedade de prop?sitos, tais como jogos online, sistemas financeiros, solu??es computacionais em nuvem, etc. ? poss?vel ent?o assumir que nos dias de hoje, Sistemas Distribu?dos est?o em todos os lugares, e que h? uma grande probabilidade de que qualquer projeto de desenvolvimento de software em andamento esteja usando este paradigma como parte da sua proposta de entrega. Dessa forma, ? relevante o estudo dos impactos que Sistemas Distribu?dos trazem ? disciplina de Gest?o de Projetos. [Objetivos] Neste trabalho, n?s discutimos estes impactos e desafios, assim como propomos um Ciclo de Vida de Desenvolvimento de Software (SDLC) e suas pr?ticas associadas, ambos sendo adaptados para o uso em projetos de desenvolvimento de software que envolvam Sistemas Distribu?dos. As pr?ticas propostas foram otimizadas para implementa??o em um regime Cascata, sendo contudo tamb?m adapt?veis ao uso sob o framework Scrum. [M?todo] Em um primeiro momento, um Estudo de Mapeamento Sistem?tico foi conduzido para entendimento do Estado-da-arte com rela??o aos estudos acad?micos localizados na intersec??o entre Gest?o de Projetos e Sistemas Distribu?dos. A seguir, entrevistas qualitativas foram executadas com membros da ind?stria da Tecnologia da Informa??o, objetivando confirmar os resultados encontrados no Estudo de Mapeamento Sistem?tico, al?m de obter feedback relacionado aos desafios que Projetos atuais de Sistemas Distribu?dos trazem, buscando-se ainda identificar contramedidas desej?veis para mitigar ou mesmo anular tais desafios. [Resultados] Como terceiro e final passo, um SDLC gen?rico, assim como pr?ticas associadas ? ele, ambos tailorizados para projetos envolvendo sistemas distribu?dos, foram propostos como resposta direta aos resultados obtidos das entrevistas qualitativas. As pr?ticas tailorizadas mencionadas se constituem na espinha dorsal de nossas contribui??es. As propostas apresentadas passaram pelo processo de member-checking para valida??o e refinamento, o que resultou na vers?o final apresentada nesta disserta??o.

APA, Harvard, Vancouver, ISO, and other styles

45

Strassl, Johann Gerhard. "Requirements engineering for business workflow systems : a scenario-based approach." Thesis, Durham University, 2001. http://etheses.dur.ac.uk/4136/.

Full text

Abstract:

Workflow implementations require a deep understanding of business and human cooperation. Several approaches have been proposed to address this need for understanding, but largely in a descriptive way. Attempts to use them in software development have had mixed results. The work reported here proposes that these approaches can be used in a generative way, as part of the requirement engineering process, by (a) extending requirements engineering modelling techniques with underlying cooperation properties, (b) integrating these techniques through the use of a derivation modelling approach, and (c) providing pragmatic heuristics and guidelines that support the real-world requirements engineering practitioner to ensure a high probability of success for the business workflow system to be developed. This thesis develops and evaluates a derivation modelling approach that is based on scenario modelling. It supports clear and structured views of cooperation properties, and allows the derivation of articulation protocols from business workflow models in a scenario-driven manner. This enables requirements engineering to define how the expectations of the cooperative situation are to be fulfilled by the system to be built - a statement of requirements for business workflow systems that reflects the richness of these systems, but also acts as a feasible starting point for development. The work is evaluated through a real-world case study of business workflow management. The main contribution of this work is a demonstration that the above problems in modelling requirements for business workflow systems can be addressed by scenario-based derivation modelling approach. The method transforms models through a series of properties involving cooperation, which can be addressed by using what are effectively extensions of current requirements engineering methods.

APA, Harvard, Vancouver, ISO, and other styles

46

Abed, Jaser Zaid, and Osamah Haitham Sabhan Al-Braichi. "Measuring Test Coverage in Embedded Software Development Branches." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-45425.

Full text

Abstract:

Most of the hardware products today, especially those that people interact with, are controlled by software. There are many devices with inbuilt software which many people do not bother to notice. Software may be critical in terms of strict quality requirements due to failures which enable risks of endangering the production and more importantly the lives of people. The testing team of Westermo Network Technologies AB faced a challenge with not being able to identify the coverage of tested cases in software. Identifying the coverage of total executed test cases enables the possibility of knowing the potential future quality of a software. By reaching such a stage a software will likely not suffer from failures due to higher quality, therefore the lives of people and the production at stake will not get harmed. The essential problem is that test cases are both tested and skipped, which makes it more difficult for the company to identify what has been actually tested and skipped. The purpose of this thesis is to identify and calculate the coverage of test cases, the process was mainly to understand the essence in the identification of executed test cases. The ethical aspect of putting people's lives at stake is what inspired us to investigate software failures. Software is typically tested before a release, therefore our investigation was to research testing process of software. When investigating test result over many days and test systems we developed a coverage calculator system which helps Westermo to decide and determine the release of tested software, either the software test result is acceptable for a release or not.

APA, Harvard, Vancouver, ISO, and other styles

47

Bentley, Richard Michael. "Supporting multi-user interface development for cooperative systems." Thesis, Lancaster University, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.385241.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Lycett, Mark Geoffrey. "The development of component-based evolutionary information systems." Thesis, Brunel University, 1999. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.266634.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Ehlers, Kobus. "Agile software development as managed sensemaking." Thesis, Stellenbosch : University of Stellenbosch, 2011. http://hdl.handle.net/10019.1/6455.

Full text

Abstract:

Thesis (MPhil (Information Science))--University of Stellenbosch, 2011.
ENGLISH ABSTRACT: The environment in which all organisations currently operate is undoubtably dynamic. Regardless of the nature, size or geographical location of business, companies are being forced to cope with a rapidly changing world and increasing levels of unpredictability. This thesis tracks the history of software development methodologies leading up to agile development (chapter 2). Agile development has appeared in response to the limitations of traditional development approaches and evolved to address the particular demands of a changing world (chapter 3). The theory of sensemaking is used to gain insight into the functioning of agile development. Sensemaking is introduced and a working definition of this concept is formulated (chapter 4). This research does not argue that agile development is the same as sensemaking, but rather that it can be better understood through sensemaking. Agile development can be seen as a type of sensemaking, but sensemaking is also a generic, universal cognitive ability. The structure and design of agile development is well aligned with sensemaking, and one can understand its nature and the type of management needed to support agile development better from this perspective. In fact, agile development directly supports and facilitates several important elements of the sensemaking process. For successful sensemaking to occur, certain organisational conditions need to be present. The term "managed sensemaking" is introduced to expand this notion. After performing an analysis of agile development (chapter 5), certain pertinent implications and challenges facing organisations are considered (chapter 6). By framing these implications in terms of sensemaking, practical management suggestions can be provided based on a good fit between the problem that agile development is meant to solve and the cognitive requirements of the process leading to a solution. The research conducted in this process opens the door to further research opportunities (chapter 7) and allows for the application of sensemaking in the context of software development methodologies. This study provides insight into the prevalence and functioning of agile methodologies, in software engineering contexts, by leveraging the theory of sensemaking to provide an explanation for the underlying worldview and processes constituting this approach.
AFRIKAANSE OPSOMMING: Die omgewing waarin alle organisasies tans funksioneer in ongetwyfeld dinamies. Maatskappye word genoop om die uitdagings van 'n vinnig-veranderende wêreld die hoof te bied, ongeag die aard, grootte of geografiese ligging van die besigheid. Hierdie tesis volg die geskiedenis van sagteware-ontwikkelingsmetodologiee tot by agile development (hoofstuk 2). Agile development het verskyn as 'n reaksie op die beperkings van tradisionele ontwikkelingsbenaderings en evolueer om aan te pas by huidige uitdagings (hoofstuk 3). Die teorie van sensemaking word gebruik om insig te verkry in die funksionering van agile development. Sensemaking word ingelei en 'n werksdefinisie word geformuleer (hoofstuk 4). Hierdie navorsing argumenteer nie dat agile development dieselfde is as sensemaking nie, maar eerder dat dit beter verstaan kan word deur sensemaking. Agile development kan wel gesien word as 'n tipe sensemaking, maar sensemaking is ook 'n generiese, universele kognitiewe vermoe. Die struktuur en ontwerp van agile development is goed belyn met sensemaking, en 'n mens kan die aard daarvan en tipe bestuur benodig om agile develop- ment te ondersteun beter verstaan vanuit hierdie perspektief. Tewens, agile development ondersteun en fasiliteer verskeie belangrike elemente van die sensemaking proses direk. Vir suksesvolle sensemaking om plaas te vind, word sekere organisatoriese toestande benodig. Die term "managed sensemaking" word ingelei om hierdie idee uit te brei. Na 'n analise van agile development (hoofstuk 5) word sekere dwingende implikasies en uitdagings, wat organisasies in die gesig staar, oorweeg (hoofstuk 6). Deur hierdie implikasies te plaas in sensemaking-terme kan praktiese bestuursvoorstelle aangebied word, gegrond op 'n goeie passing tussen die probleem wat agile development probeer aanspreek en die kognitiewe vereistes van die proses wat lei na 'n oplossing. Die navorsing wat onderneem is in hierdie proses ontsluit moontlikhede vir verdere studies (hoofstuk 7) en skep die moontlikheid vir die toepassing van sensemaking in die konteks van sagtewareontwikkelingsmetodologiee. Hierdie studie bied insig in die voorkoms en funksionering van agile methodologies in sagteware-ingenieurwese omgewings deur die teorie van sensemaking te hefboom om 'n verduideliking vir die onderliggende wereldbeeld en prosesse aan te bied.

APA, Harvard, Vancouver, ISO, and other styles

50

Lockhart, Jonathan A. "Software Development Process and Reliability Quantification for Safety Critical Embedded Systems Design." University of Cincinnati / OhioLINK, 2019. http://rave.ohiolink.edu/etdc/view?acc_num=ucin1562673285477425.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Software/systems development'

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