Thesis (MPhil (Informations Science))--University of Stellenbosch, 2009. / This research utilises theories of organisational knowledge creation from the field of knowledge management to analyse the manner in which the industrialisation of the software development industry is likely to occur. The aim of the research is to prove the following hypothesis: If the software development industry moves towards industrialisation, then knowledge assets in the format of universal production templates will come into being. The research commences by providing background information on the state of practise of software engineering by giving an overview of the changes in the industry over the past four decades. The software development industry is consequently presented from the viewpoint of the proponents of a craftsmanship based approach to software development, and from the viewpoint of those proposing that industrialisation will offer a solution to the problems besetting the industry. In this discussion the terms industrialisation as well as economies of scale and scope are defined. Potential paths and drivers that will allow the industrialisation of the industry are presented – software factories as a path towards industrialisation, and cloud computing as a driver for industrialisation. In order to supply a knowledge management perspective, the theories of Ikujiro Nonaka and Max Boisot are presented. These theories assume different perspectives on the creation of organisational knowledge, but an attempt is made to reconcile the differences between the two theories. Particular attention is paid to the economic meaning and implications of knowledge, information and data as factors of production. The concept of knowledge assets are examined in detail, and placed into the context of software development. In the last chapter the research and conclusions of the previous chapters are consolidated, to prove the central hypothesis of this work.

Thesis (MPhil (Information Science))--University of Stellenbosch, 2010. / ENGLISH ABSTRACT: In an effort to streamline operations and focus on what they regard as core activities, a growing number of organizations from both developed and developing countries are increasingly looking to outsource their software development and maintenance activities to lower cost countries such as India and China, this is evidenced by the phenomenal growth in India’s software industry and the number of major overseas IT companies establishing subsidiaries and relocating their Research and Development operations to India’s high-tech cities such as Hyderabad, Chennai and Pune. With the mere size of their populations standing at over a billion people each, supported by their governments, Indian and Chinese business have been able to leverage this population advantage producing a large pool of software engineers, technical specialists and back office workers to cater for the talent demands of the world. While the actual software development process might be non-core to many organizations, it however yields software applications that drive critical business processes and embed valuable organizational knowledge. The handing over of software development operations by an organization to a third party poses a risk of creating a dependency and exposing vital business knowledge to competition thereby compromising its competitive edge. Both the people that participate in software development projects and the software products these people develop possess knowledge which need to be secured and leveraged to enable the continued success of an organization. Securing these knowledge artefacts and the knowledge created by the software development lifecycle process cannot be left to chance, therefore the success of an organization’s software development activities needs to be measured largely on its ability to secure knowledge assets that derive from such process and the leveraging of such knowledge to drive organizational strategy and yield new knowledge. This thesis is premised on the fact that knowledge is the one competitive advantage that separates successful nations from failed states and one dominant force that prevails across all successful economies in the 21st century, hence the notion of a knowledge economy. The study seeks to understand the importance of the role played by knowledge in an outsourced software development engagement and how knowledge management affects the success of this engagement. By exploring the business drivers that spur organizations to outsource their IT activities, the software development lifecycle, the different outsource models available to organizations and the inherent risks surrounding knowledge loss, the thesis seeks to gain an understanding and the criticality of managing knowledge within an outsourced software development context and the strategies that organizations can utilize to deliver on outsourcing promises with minimal risk. / AFRIKAANSE OPSOMMING: Ten einde hulle werksaamhede meer vaartbelyn te maak en om ingestel te bly op dit wat hulle as kernbedrywighede beskou, kyk al hoe meer organisasies in ontwikkelde en ontwikkelende lande na die moontlikheid om die ontwikkeling en instandhouding van hulle sagteware uit te kontrakteer na lande soos Indië en China, waar dit goedkoper gedoen kan word as tuis. Dié feit blyk duidelik uit die fenomenale groei in veral Indië se sagtewarenywerheid en die getal groot oorsese IT firmas wat hulle navorsing en ontwikkeling in hoë-tegnologie stede soos Hyderabad, Chennai en Puna laat doen. Met bevolkings van meer as ’n miljard elk, kon Chinese en Indiese ondernemings hierdie voorsprong benut om ‘n magdom sagteware-ingenieurs, tegniese spesialiste en kantoorwerkers te produseer om in die wêreld se vraag na kundigheid te voorsien. Terwyl die ontwikkeling van sagteware miskien nie deur baie ondernemings as ‘n kernbedrywigheid beskou word nie, lewer dit tog aanwendings op wat kritieke sakeaktiwiteite aandryf en waardevolle organisatoriese kennis vasvang. Die oordra van sagteware-ontwikkeling van een onderneming na ‘n derde party gaan egter gepaard met die risiko dat dit afhanklikheid kan skep en ook uiters belangrike sakekennis aan konkurrente toeganklik maak, wat die mededingende voorsprong wat sulke kennis bied bedreig. Die mense betrokke by die ontwikkeling van sagteware en die produkte wat hulle sodoende skep, is ‘n bron van kennis wat beveilig en verveelvuldig moet word om ‘n onderneming in staat te stel om suksesvol te bly voortbestaan. Die versekering van hierdie verworwe kennis en die kundigheid wat deur die ontwikkelingsiklus van die sagteware geskep word, kan nie aan die toeval oorgelaat word nie – die sukses van ‘n onderneming se sagteware-ontwikkeling moet veral gemeet word aan sy vermoë om die kennisbates wat uit die proses voortvloei te verseker, en om hierdie kennis te verveelvuldig om organisatoriese strategieë aan te dryf en nuwe kennis op te lewer. Hierdie tesis se uitgangspunt is dat kennis die mededingende voorsprong is wat suksesvolle nasies onderskei van die res; dit is dié faktor wat kenmerkend is van al die suksesvolle ekonomieë van die 20ste eeu, en die kern van die begrip van ‘n “kennis-ekonomie”. Hierdie ondersoek wil die belangrikheid verken van die rol wat gespeel word deur kennis in ‘n uitgekontrakteerde verbintenis vir die ontwikkeling van sagteware and hoe kennisbestuur die sukses van so ‘n verbintenis affekteer. Deur ondersoek in te stel na die motivering wat besighede aanspoor om hulle IT bedrywighede uit te plaas, na die sagteware-ontwikkeling lewenssiklus, die verskillende modelle van uitkontraktering wat vir organisasies beskikbaar is en die inherente risiko’s rondom kennisverlies, wil hierdie tesis ‘n begrip vorm van die kritieke noodsaaklikheid vir die bestuur van kennis in ‘n uitgekontrakteerde sagteware-ontwikkeling en van die strategieë wat organisasies kan aanwend om die voordele wat uitkontraktering beloof ten volle te benut teen minimale risiko.

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.

O objetivo deste trabalho é comparar dois paradigmas distintos de desenvolvimento de software, o emergente Paradigma Orientado a Notificações (PON) e o Paradigma Orientado a Eventos (POE). Objetivos, métodos e ferramentas são apresentados, e são descritos dois casos de estudo (o primeiro em três cenários), respectivas reflexões, experimentos e dados. A comparação é teórico-prática, correlacionando características estruturantes em PON e POE conforme uma taxonomia comum, os mensurando em complexidade de código-fonte (números de linhas de código, escopos e tokens) e os comparando em medições durante execução (tempo de reposta e tempo total de execução), por meio da construção e experimentação dos casos de estudo em ambos os paradigmas. Como resultados, identifica-se que PON, apesar de ter inspiração em eventos, utilizando notificações em seu ciclo de execução, apresenta diferenças conceituais em relação a POE. Além disso, no atual estado da técnica, utilizando o Framework PON, apresenta tempo de resposta durante execução comparável ao POE, enfatizando desempenho que se adapta ao contexto do software (tempos de resposta menores quando os eventos devem ser desprezados e tempos de resposta maiores quando da execução de mais uma ação por evento). Já quando se utiliza uma linguagem e compilador específico para PON (LingPON e respectivo código compilado) os tempos de resposta foram lineares e comparáveis ao POE. / The objective of this work was comparing two distinct software development paradigms, namely, the emerging Notification Oriented Paradigm (NOP) and Event-driven Paradigm (EDP). Objectives, methods and tools are presented and two case studies are described (the first with three scenarios) and their respective reflexions, experiments and data. The comparison is theoretical and practical, correlating structural characteristics in NOP and EDP in a common taxonomy, therefore comparing them in code complexity (number of lines of code, closures and tokens) and comparing them with respect to performance (response time and total execution time), by building and instrumenting the case studies in both paradigms. As results, was identified that NOP, despite being inspired by events, using notifications on its execution model, shows conceptual differences from EDP. Moreover, in the present state of technology, NOP has response time during execution comparable to EDP implementation, and NOP has performance that adapts to software context (faster response times when events should be ignored and higher response times when executing more actions per event. With specific NOP language and compiler (LangNOP) data shows linear response times comparable to the EDP.

Esta tese aborda o problema de prover a independência de plataforma em transformações de modelos no contexto da MDA (Model Driven Architecture). A MDA é uma abordagem de desenvolvimento de software baseada na criação e na transformação de modelos. Assim, em MDA os modelos são os principais artefatos ao longo do ciclo de vida de desenvolvimento de software e as transformações desempenham um papel fundamental. No entanto, a maioria das iniciativas MDA são dedicadas, isto é, as características da plataforma são implicitamente especificadas nas regras de transformação. À medida que os aspectos ligados à plataforma não são separados das regras de transformação, para cada plataforma selecionada deve haver uma transformação de modelos correspondente. Por um lado, isto facilita o desenvolvimento de transformações de modelo. Por outro lado, a transformação torna-se limitada a uma plataforma específica, uma vez que os recursos da plataforma estão fortemente associados com as regras de transformação. Um dos desafios consiste em criar regras de transformação independentes das características da plataforma de implementação de sistemas de software. Esta tese propõe um método para a criação de transformações de modelo chamado PI-MT (Platform Independent - Model Transformations). O PI-MT é voltado ao desenvolvimento de software embarcado baseado em Sistemas Operacionais em Tempo-Real (RTOS - Real-Time Operating System). Além disso, o método permite a adaptação de transformações de modelos para diferentes plataformas baseadas em RTOS, por meio de modelos de plataforma explicitamente definidos. Como resultado, o método de PI-MT oferece independência entre as regras de transformação e as características da plataforma. / This thesis deals with the platform-independence matter in the Model Driven Architecture (MDA) context. MDA is an approach to software development based on the design and transformation of models. In the MDA approach models are the core artifacts throughout the entire software development lifecycle, and thus a key role is played by model transformations. Nevertheless, most MDA initiatives are dedicated, i.e., the platform features are implicitly employed in the transformation rules. As the aspects associated with the platform are not separated from the transformation rules, for each selected platform there must be a corresponding model transformation. On the one hand, this makes the model transformation development easier. On the other hand, model transformation becomes limited to a specific platform, once the platform features are strongly associated with the transformation rules. An open challenge consists of how to create transformation rules independently of the deployment platform features of software systems. This thesis proposes a method for creating model transformations, called PI-MT (Platform Independent - Model Transformations). The PI-MT is particularly applied to embedded software development based on Real-Time Operating Systems (RTOS). In addition, it allows the adaptation of the model transformation process to different RTOS-based platforms by means of Platform Models explicitly defined. As a result, the PI-MT method provides independence between the model transformation rules and the platform features.

This dissertation focuses on how requirements for a new software development system are elicited and what pitfalls could cause a software development project to fail if the said requirements are not captured correctly. A number of existing requirements elicitation methods, namely: JAD (Joint Application Design), RAD (Rapid Application Development), a Formal Specifications Language (Z), Natural Language, UML (Unified Modelling Language) and Prototyping are covered. The aforementioned techniques are then integrated into existing software development life cycle models, such as the Waterfall model, Rapid Prototyping model, Build and Fix model, Spiral model, Incremental model and the V-Process model. Differences in the domains (knowledge and experience of an environment) of a client and that of the software development team are highlighted and this is done diagrammatically using the language of Venn diagrams. The dissertation also refers to a case study highlighting a number of problems during the requirements elicitation process, amongst other the problem of tacit knowledge not surfacing during elicitation. Two new requirements elicitation methodologies are proposed namely: the SRE (Solitary Requirements Elicitation) and the DDI (Developer Domain Interaction) methodology. These two methods could potentially be more time consuming than other existing requirements elicitation methods, but the benefits could outweigh the cost of their implementation, since the new proposed methods have the potential to further facilitate the successful completion of a software development project. Following the introduction of the new requirements elicitation methods, they are then applied to the aforementioned case study and highlight just how the hidden domain of the client may become more visible, because the software development team has gained a deeper understanding of the client’s working environment. They have therefore increased their understanding of how the final product needs to function in order to fulfil the set out requirements correctly. Towards the end of the dissertation a summary and a conclusion as well as future work that could be undertaken in this area are provided. / Computer Science / M. Sc. (Computer Science)

No Brasil existe um número limitado de empresas com certificações de qualidade, a baixa qualificação na mão de obra pode confirmar este cenário. Uma equipe altamente qualificada pode ser uma das formas de se melhorar a qualidade das empresas e consequentemente a sua competitividade. Este trabalho apresenta um delineamento de um processo de sistematização de ambientes de residência em software, cujo objetivo é propiciar qualificação para os profissionais de empresas de software. As teorias de gestão de conhecimento e residência em software foram utilizadas em um método experimental para validar a sistematização apresentada neste trabalho. Foram executados quatro experimentos: três executados com alunos de programa de mestrado e um em uma empresa real. A execução dos experimentos evidência que é possível sistematizar um ambiente de residência em software. A contribuição deste trabalho é a validação do processo e consequentemente o ganho e a transferência de conhecimentos entre os funcionários de uma empresa de software. / Brazil has a limited number of organizations with quality certification, and low unskilled workers can confirm this scenario. A well qualified team can be one of the ways to improve the quality of organizations and consequently increase their competitiveness. This work presents the process of systematizing a software residency environment, whose aim is to provide qualification for employees in software organizations. The knowledge management and software residency theories were adapted in an experimental method to validate the systematization proposed. Four experiments were conducted: three were executed with computer science master students and one within a real company. The performed experiments show evidences that it is possible to systematize a residency software environment. The contribution of this work is the validation of the process and, a as consequence, the knowledge gain and transfer among employees of a software organization.

O crescimento da competitividade entre as empresas de desenvolvimento de software, trouxe uma maior pressão no aumento da produtividade, adaptação rápida à mudanças e entregas cada vez mais rápidas de produtos cada vez melhores e mais baratos. Baseado nesse contexto, surgiram as metodologias ágeis, cujo enfoque principal está relacionado à adaptabilidade com o propósito de entregar produtos com maior valor agregado no menor espaço de tempo possível. A fim de preencher algumas lacunas de gestão ainda apresentadas pelas metodologias ágeis, houve um desdobramento da Filosofia Lean, dentro da perspectiva do desenvolvimento de software, o Lean Software Development (LSD). As implementações de LSD são recentes, e a partir de pesquisas em diversos periódicos, foi possível observar que pouco se falou até então sobre essas aplicações em empresas de desenvolvimento de software inseridas em diferentes contextos. Este estudo também se preocupou com os excessos produzidos no desenvolvimento de software, acima e além das necessidades ou recursos disponíveis. A literatura possui poucas referências nesta questão, sendo o assunto importante para novas discussões. Tratando-se do Arranjo Produtivo Local (APL) de Tecnologia da Informação do Sudoeste do Paraná, há oportunidades de pesquisa a serem desenvolvidas. Apesar das metodologias ágeis já estarem inseridas, ainda existem diversas lacunas da sua aplicação e processos ainda sem gestão. A partir dessa concepção de ideias, este trabalho se propôs a levantar as possibilidades de inserção dessas metodologias nos processos já trabalhados nas empresas do APL, analisando as áreas de processos que sofrem excessos no desenvolvimento, bem como convergindo para a ideia de melhorar o desempenho e produtividade das empresas analisadas. Para essa finalidade, foi realizado estudo de caso múltiplo, abrangendo três empresas de desenvolvimento de software. Com o levantamento de dados durante a pesquisa, observou-se crescimento emergente das metodologias ágeis no setor. As três empresas analisadas já buscam inserir ferramentas e métodos ágeis e/ou Lean no processo. No entanto, esse crescimento ainda é embrionário em sua maioria. Apenas uma das empresas teve contato com a filosofia Lean para software, enquanto as outras duas inseriram métodos ágeis há apenas um ano, uma com uma evolução e integração da equipe bem formalizada, a outra com um pouco menos de consistência. É interessante salientar que os excessos ainda ocorrem mesmo quando o uso da metodologia Lean ou Ágil já está inserida. Sendo possível observar melhorias, mas ainda lacunas em que o processo pode ser mais refinado e os desperdícios menos impactantes ou até inexistentes. / The growth of competitiveness between software development companies has brought greater pressure on increasing productivity, quickly adaptation to changes and ever faster deliveries of ever better and cheaper products. Based on this context agile methodologies have emerged, with the mainly focus related to adaptability with the purpose of delivering products with higher added value in the shortest time possible. In order to fill some management gaps still presented by the agile methodologies, there was an unfolding from Lean Philosophy, inside of the perspective of software development, the Lean Software Development (LSD). The LSD implementations are recent, and through surveys at various periodic intervals, it was possible to observe that little has been said about applications in software development companies inserted in different contexts. This study also concerned itself with the excesses produced in software development, above and beyond the needs or resources available. The literature has few references in this issue, being the subject important for new discussions. In the case of the Local Productive Arrangement (LPA) of Information Technology of the SouthWest of Paraná, there are research opportunities to be developed. Although agile methodologies are already inserted, there're still several gaps in its application and processes that aren't managed yet. Based on this conception of ideas, this work aims to raise the possibilities of insertion of these methodologies in the processes already worked in the LPA companies, analyzing as areas of processes that suffer excesses in the development as well as converging on the idea of improving the performance and production of the companies analyzed. For this purpose, a multiple case study was carried out, covering three software development companies. With the data collection during the research, there was an emerging growth of the agile methodologies in the sector. The three companies analyzed already seek to insert agile and / or Lean tools and methods in the process. However, this growth is still embryonic in its majority. Only one of the companies had contact with the Lean philosophy for software, while the other two introduced agile methods only a year ago, one with a well-formed team evolution and integration, the other with a little less consistency. It's interesting to note that excesses still occur even when the use of the Lean or Agile methodology is already inserted. It's possible to observe improvements but still gaps, in which the process can be more refined and the wastes less impacting or even none existent.

Thesis (MTech (Information Technology))--Peninsula Technikon, 2004 / This dissertation was written in fulfillment of the requirements for the degree Master of Technology in the Faculty of Information Technology at the Peninsula Technikon in South Africa. The dissertation covers the introduction of the study; the reviews of the case, Free and Open Source Software; the discussion of methodology of software project management in terms of software engineering; the analysis of assessment methods; the techniques of using PHP, MySQL, Apache and CVS; and the implementation of a test module. The research represents the consideration of the problem, namely that there are few free assessment manager programmes that can be used for the quick and efficient deployment of academic assessments. An experimental research method was used to with the aim of solving the above problem. In other words, a test management system module had to be designed and implemented to function within the architectural constraints of a developing Open Source Software (OSS) Learning Management System (LMS), which is called Knowledge Environment for Web-based Learning Next Generation (KEWL.NextGen). The test management system is a module developed on Object-Oriented Programming (OOP) in PHP and MySQL application. The scripts of this test module are written under the KEWL.NextGen' application framework, which is based on a close approximation of model, view and controller (MVC) design III pattem. Now the entire source coding of the test module has been uploaded to Web site http://kngforge.uwc.ac.za. This test module can be used for the creation and management of an online test. It provides facilities to create a new test, and to preview, edit, delete and mark an existing test. Three question types have been achieved, namely multiple-choice, true/false and short answer.

Thesis (MTech (Information Technology))--Peninsula Technikon,Cape Town, 2004 / Higher education and online discussions are an integral part of collaboratively based e-Learning systems. However, there problems can be associated with current online discussion models. For example, it can be easy to set open-ended discussions which attract little participation and to assess contributions can be difficult or time-consuming. Students may not achieve the expected learning outcomes without proper structure and management in online discussions. This paper proposes to design and implement a discussion forum object to function within the architectural constraints of an existing Oss learning management system (to meet target user requirements) that is a web-based environment for online discussions where the facilitator can structure each discussion according to its nature and where learning requirements are using already designed templates.