For over 30 years, authors have documented continuous improvement techniques that can help to improve the performance of the manufacturing sector. However, recent research has found that the uptake of these available techniques for the purpose of improving business performance is comparatively low as a result of barriers preventing their adoption by manufacturing SMEs. The aim and focus of this research is to develop a user-friendly framework which would guide both industry practitioners and other researchers to achieve business process improvements in an SME manufacturing environment. The framework developed in this study consists of four stages: 1) review of the current process to be improved; 2) identification of possible improvement in terms of prompts; 3) knowledge know-how to support transfer of proven continuous improvement techniques; and 4) continual review of the process to quantify the improvements. The framework uses a combination of three continuous improvement techniques: histograms, brainstorming and Five Whys to identify actions for management implementation. Such techniques have been merged to speed up and simplify the process of root cause analysis, thus encouraging SMEs to document their successes. This will enable other SMEs to learn from their experiences as well as from the knowledge gained by being part of the communities of practice. The methodology used in this research is mixed methodology and involves a combination of literature review, pilot study, a postal questionnaire with 50 respondents and two case studies. These case studies were then used to validate the framework, based on five structured interviews. Case studies involving two manufacturing SMEs include manufacturers of high-volume, low-cost components and low-volume, high-cost components. It was concluded that the root cause of a problem can be found by using: brainstorming, histograms and Five Whys. Sometimes, it was also possible to merge these techniques as one, thus reducing the analysis time. The case studies generated substantial savings, £27,500 and £1,366,055 for SME 1 and 2 respectively. Overall the benefits of the framework to SMEs include: using the developed user-friendly framework for improved business performance, knowledge transfer of learning continuous improvement techniques, learning about other SME successes and potential cost savings that could accrue for SMEs when they apply it. The framework developed in this research, therefore, has reduced some of the barriers which have prevented uptake of innovative techniques over the last 30 years.

In this paper, we use the following scheme to construct a continuous, nowhere-differentiable function 𝑓 which is the uniform limit of a sequence of sawtooth functions 𝑓ₙ : [0, 1] → [0, 1] with increasingly sharp teeth. Let 𝑋 = [0, 1] x [0, 1] and 𝐹(𝑋) be the Hausdorff metric space determined by 𝑋. We define contraction maps 𝑤₁ , 𝑤₂ , 𝑤₃ on 𝑋. These maps define a contraction map 𝑤 on 𝐹(𝑋) via 𝑤(𝐴) = 𝑤₁(𝐴) ⋃ 𝑤₂(𝐴) ⋃ 𝑤₃(𝐴). The iteration under 𝑤 of the diagonal in 𝑋 defines a sequence of graphs of continuous functions 𝑓ₙ. Since 𝑤 is a contraction map in the compact metric space 𝐹(𝑋), 𝑤 has a unique fixed point. Hence, these iterations converge to the fixed point-which turns out to be the graph of our continuous, nowhere-differentiable function 𝑓. Chapter 2 contains the background we will need to engage our task. Chapter 3 includes two results from the Baire Category Theorem. The first is the well known fact that the set of continuous, nowhere-differentiable functions on [0,1] is a residual set in 𝐶[0,1]. The second fact is that the set of continuous functions on [0,1] which have a dense set of proper local extrema is residual in 𝐶[0,1]. In the fourth and last chapter we actually construct our function and prove it is continuous, nowhere-differentiable and has a dense set of proper local extrema. Lastly we iterate the set {(0,0), (1,1)} under 𝑤 and plot its points. Any terms not defined in Chapters 2 through 4 may be found in [2,4]. The same applies to the basic properties of metric spaces which have not been explicitly stated. Throughout, we will let 𝒩 and 𝕽 denote the natural numbers and the real numbers, respectively.

The goals with continuous delivery are to reduce the risk, cost, and time of releasing software to the stakeholders and the users. It is a process which can result in reliable releases and reducing errors in the software. Furthermore, there are some best practices to follow when conducting the continuous delivery process, involving version control, and build tools. There are however some obstacles and challenges for organizations when moving to continuous delivery. For example, complex environments, organizational problems, and lack of automated test cases. This master thesis investigates continuous delivery through a literature review, a multiple-case study, and fieldwork. The result can either be used by software engineers and organizations who are new to the continuous delivery concept. Or the result can be used by more experienced software engineers to gain more knowledge about existing obstacles and for further research.

Abstract Continuous software engineering (CSE) has instigated academic debate regarding the rapid, parallel cycles of releasing software and customer experimentation. This approach, originating from Web 2.0 and the software-as-a-service domain, is widely recognised among software-intensive companies today. Earlier studies have indicated some challenges in the use of CSE, especially in the context of business-to-business and product-oriented, embedded systems development. Consequently, research must address more explicit definitions and theoretical models for analysing the prerequisites and organisational capabilities related to the use of CSE. This dissertation investigates various approaches to conducting empirical evaluations related to CSE. The study aims to improve existing models of CSE and to empirically validate them in the context of software companies. The study also aims to accumulate knowledge regarding the use of CSE, as well as its impacts. The case study method is applied for the collection and analysis of empirical data. Twenty-seven interviews are conducted at five companies. In addition, a systematic literature review is used to synthesise the empirical research on agile release engineering practices. Design science research is used to portray the model design and the evaluation process of this dissertation. Three approaches for evaluating CSE are constructed: (1) LESAT for software focuses on enterprise transformation using an organisational self-assessment approach, (2) STH+ extends the “Stairway to Heaven” model and evaluates company practices with respect to evolutionary steps towards continuous experimentation-driven development, and (3) CRUSOE defines 7 key areas and 14 diagnostic questions related to the product-intensive software development ecosystem, strategy, architecture, and organisation, as well as their continuous interdependencies. This dissertation states the relevance of CSE in the context of product-intensive software development. However, more adaptations are anticipated in practices that involve business and product development stakeholders, as well as company external stakeholders. / Tiivistelmä Jatkuva ohjelmistotuotanto on herättänyt keskustelua nopeasta, samanaikaisesta ohjelmistojulkaisemisesta ja asiakaskokeiluista. Toimintatapa on peräisin Web 2.0 ja software-as-a-service yhteydestä, mutta se tunnetaan nykyään yleisesti ohjelmistoja kehittävissä yrityksissä. Aiemmat tutkimukset ovat osoittaneet haasteita jatkuvan ohjelmistotuotannon käytössä. Erityisesti haasteita on havaittu yritykseltä yritykselle liiketoiminnassa ja tuotepainotteisten sulautettujen järjestelmien yhteydessä. Näin ollen on havaittu tarve tutkimuksen avulla kehittää täsmällisempiä määritelmiä ja teoreettisia malleja, joilla voidaan analysoida jatkuvan ohjelmistotuotannon käyttöön liittyviä edellytyksiä ja organisaatioiden kyvykkyyksiä. Tässä väitöskirjassa tutkitaan malleja, joilla voidaan empiirisesti arvioida jatkuvaa ohjelmistotuotantoa. Tutkimuksella pyritään parantamaan nykyisiä malleja ja arvioimaan niiden käyttöä ohjelmistoyrityksissä. Lisäksi tutkimuksella pyritään kasvattamaan tietoa jatkuvasta ohjelmistotuotannosta ja sen vaikutuksista. Tiedon keräämiseen ja analysointiin käytettiin tapaustutkimus menetelmää. Kaksikymmentäseitsemän haastattelua tehtiin viidessä yrityksessä. Lisäksi tehtiin ketterään ohjelmistojulkaisuun keskittyvä systemaattinen kirjallisuuskatsaus. Väitöskirjassa käytetään Design Science Research menetelmää kuvaamaan tutkimuksen eri vaiheita, joissa malleja suunniteltiin ja arvioitiin. Tutkimuksessa rakennettiin kolme tapaa jatkuvan ohjelmistotuotannon arvioimista varten: (1) LESAT for Software keskittyy organisaation muutoskyvykkyyden arviointiin käyttäen itsearviointimenetelmää, (2) STH+, laajentaa ”Stairway to Heaven” mallia ja arvioi yrityksen käytäntöjä eri evoluutioaskelmilla matkalla kohti kokeilupainotteista tuotekehitystä, (3) CRUSOE määrittelee seitsemän pääaluetta ja 14 kysymystä liittyen tuotekehityksen ekosysteemiin, strategiaan, arkkitehtuuriin, organisointiin sekä näiden välisiin jatkuviin riippuvuuksiin. Väitöskirja osoittaa jatkuvan ohjelmistokehityksen olevan merkityksellinen myös tuotepainotteisessa ohjelmistokehityksessä. Nähtävissä kuitenkin on, että useita nykykäytäntöjä on tarvetta muokata. Erityisesti muokkaustarvetta on tuotekehityksen ja liiketoiminnan sidosryhmiin ja yrityksen ulkoisiin sidosryhmiin liittyvissä käytännöissä.

When the traditional approach to system development transitioned over to agile methods the demand for ways to continuously deliver valuable software increased. With the increasing interest in these methods the umbrella term DevOps were introduced in 2008. DevOps is the practice to shorten the time, as well as streamlining the process, between changes in the source code and when it reaches the customer. This study aimed at investigating the process of adopting DevOps practices and identify success factors and challenges in this transition. We conducted a quality approached case study on a DevOps team in a multinational IT-consulting firm. Four explorative interviews were conducted based on categories identified in relevant literature as well as basis provided by the case company. We discovered that an implementation of continuous practices is far more complex than we initially thought. It is related to more fields outside the technical aspect that must be considered during a transition.  Our findings include four critical success factors for a successful DevOps implementation; conscious staff, conscious organization, functional infrastructure and adapted business model. Embedded in these critical success factors we were able to identify challenging fields that should be considered when adopting DevOps. These critical success factors and challenges was the basis for our model presented in the study.

No description available.

Although most organisations want to improve quality and reduce costs, the deployment and implementation of continuous improvement methodologies is commonly viewed as a daunting journey. Many organisations fail to properly structure and/or support continuous improvement initiatives, which ultimately doom them to failure. South African Banks are not adopting Lean and/or Six-sigma to the point where it is going to make any sort of significant difference to the bottom line over a significantly meaningful period of time. So where are they going wrong? Often it comes down to key issues that are not addressed effectively as part of the deployment. The research objectives are: • The primary objective is to establish what the mission critical success factors for Lean and/or Six-sigma implementation in South African Banking are. • The secondary objective is to define a list of the sources of benefits for Lean and/or Six-sigma implementations in South African Banking. The research questions/problems to be addressed are: • What are the mission critical success factors for Lean and/or Six-sigma implementations in South African Banking? • How do South African Banks prioritise these critical success factors? • How do South African Banks that are already on the Lean and/or Six-sigma journey perform against these critical success factors? • What are the gaps between the importance’s of the critical success factors versus the banks actual performance against these, and how is this gap impacting on the benefits that the banks are experiencing? • What sources of benefits are South African Banks experiencing? • Can generic guidelines be provided to the South African Banks for successful Lean and/or Six-sigma implementation?

International Telemetering Conference Proceedings / October 23-26, 2000 / Town & Country Hotel and Conference Center, San Diego, California / The Advanced Range Telemetry (ARTM) program is a tri-service telemetry modernization project whose goal is to assure that all Department of Defense (DoD) test and training ranges are able to use telemetry as necessary to carry out their respective missions. Multi-h Continuous Phase Modulation (CPM) has been selected by the ARTM JPO as the Tier II ARTM waveform, because it offers significant improvements over both legacy telemetry waveforms (PCM/FM) and the newly-introduced Tier I waveform (Feher-patented FQPSK) in terms of spectral containment and detection efficiency, while retaining a constant envelope characteristic. The paper describes the theoretical and measured performance of the ARTM Tier II multi-h CPM waveform, and the implementation of the trellis demodulator being developed for it.

No description available.

No description available.