We introduce a class of program editors that present a program using a rich set of transformations; we call these kinds of editors composable presentation editors. Proper use of these kinds of editors appears to lead to more expressive programs-programs whose structure are aligned with the problem they are trying to solve. By default, the composable presentation editor presents program elements textually as concrete syntax and enables typical editor commands on the program. Metadata on program elements control how the transformations are applied. Customized metadata can re-order, pictorialize, collapse, duplicate, or expand the displayed form of program elements and can additionally alter the available editor commands. We have developed a set of presentation techniques to be used by presentation designers (i.e., the programmers who design how a program is presented in the editor. These techniques relate to well-understood programming language design, editor design, and programming best-practices techniques including scoping, higher order functions, refactoring, prettyprinting, naming conventions, syntax highlighting, and text hovers. We introduce two implementations of composable presentation editors and a number of examples showing how programs can be made more expressive when presentation techniques are properly used. The first implementation is the ETMOP, an open editor, where a metaobject protocol is provided that allows language and editor designers to customize the way program elements are displayed. These customizations are called presenta- tion extensions and the corresponding presentation extension protocol acts in a way similar to the way that syntax macros extend the syntax of a language. The second implementation is Embedded CAL, a closed editor that uses these presentation techniques to embed one language (CAL) inside a host language (Java) through the use of presentation techniques, without changing the syntax or compiler of either language.

Mobile applications are deployed in highly dynamic environments. Devices have limited resources available and the user context changes frequently. This introduces new requirements for applications, and requires that applications are able to adapt during runtime. In addition, developers must be able to incrementally add new behaviour to applications as required by unanticipated situations. Current approaches to mobile application development and architectures do not properly address these requirements of mobile applications. This work proposes a framework, based on coordination principles, which is able to facilitate the required methods of adaptation. The framework incorporates a methodology and an architecture. The architecture provides significant advantages over previous work in terms of adaptation support. The methodology provides developers with a development process and guidelines whereby adaptive applications may be specified. As new requirements of existing applications emerge, developers can build and deploy additions to applications during runtime. The research has been evaluated through the design of application prototypes. These were built through the use of an implemented toolkit for application development, which is based on the specified methodology. The architecture, methodology and toolkit provide a unifying framework for mobile applications. The work presented in this thesis closes a gap in existing knowledge in the design and execution of distributed mobile applications.

In December 2004, at the SoDIS® (Software Development Impact Statements) symposium in Auckland, an industry certification as a method of credentialing teachers and analysis of SoDIS was mooted. SoDIS, a process of ethics-based risk assessment and analysis of downstream risk to project and software stakeholders, including the public, is currently in the process of progressing from prototype to commercial product. Certification was proposed to ensure the integrity of the process and the quality of service to stakeholders.Certification sponsored by industry, commercial organisation, or professional association (collectively referred to as industry certification, or certification) has been a form of credentialing for over half a century. Industry certification was adopted by the IT industry when Novell, Inc. began testing and certifying IT industry and IT network professionals in 1986 (Cosgrove, 2004; Novell, 1996). Global certification testing centres were established in 1990 by Drake International (now Thomson Prometric) (Foster, 2005).During the 1990s, industry certification became a veritable juggernaut: a "multi-billion dollar business" (Cosgrove, 2004, p. 486), an industry that has arisen in its own right (Adelman, 2000) and driven by several dynamics (Hitchcock, 2005). In 2000 there were over 300 discrete IT certifications with approximately 1.6 million individuals holding approximately 2.4 million IT certifications (Aldelman, 2000). The total number of available certifications is impossible to quantify (Knapp & Gallery, 2003). Many academic institutions both at tertiary and secondary level are integrating industry certification, especially IT certification, into their curricula.Is industry certification, however, a pedagogically robust form of credentialing? Does it have value to its stakeholders? Is it an appropriate form of credentialing for the SoDIS process? This research, using both Phenomenography and Interpretive Phenomenological Analysis (IPA) as a joint methodology, focuses on the experiences of actors with the phenomenon of industry certification and extracts both the essence of the understanding and perceptions of the value and validity of industry certification, and the essence of industry certification itself.Due to the vast amount of literature found describing industry actors' perceptions of and experiences within the phenomenon, the research is predominantly literature-based. Further data was collected from interviews with a small, purposive sample of industry certification holders and employers, with the research further informed by my own experiences within the domain which is the focus of the research. The methodology paradigm is interpretive: the research aims to interpret the social construction that is the phenomenon of industry certification.While this research does not attempt to single out specific industry certifications to determine their value or pedagogical robustness, the findings suggest that, in general, well designed and well administered certifications with integrity and rigour of assessment processes, are indeed pedagogically sound, with significant value. The research identifies both benefit and criticism elements of typical certifications, along with elements of the various certification programmes categorised into standard (typical), and more rigorous (less typical) certification programmes.The research develops and presents a paradigm for building an appropriate vendor specific or vendor neutral certification programme that is pedagogically sound with value for its stakeholders. The contrasts and complementary aspects of industry certification and academic qualifications are highlighted. It is therefore concluded, and supported by data from the interviews, that such a credential is indeed appropriate for teachers and analysts of SoDIS.

Zugl.: Dresden, Techn. Universiẗat, Diss., 2007.

Thesis (M.S.S.I.S.)--Regis University, Denver, Colo., 2007. / Title from PDF title page (viewed on Nov. 02, 2007). Includes bibliographical references.

Thesis (MSc (Computer science))--University of Pretoria, 2008. / Includes bibliographical references.

Thesis (M.S.)--West Virginia University, 1998. / Title from document title page. Document formatted into pages; contains vi, 53 p. : ill. Vita. Includes abstract. Includes bibliographical references (p. 50-51).

Tarek K. Abdel-Hamid, Stuart E. Madnick. / "August 1988." "This paper is a companion piece to CISR WP No. 163, Modeling the dynamics of software project management." / Includes bibliographical references (p. 18-21).

Thesis (MPhil)--Stellenbosch University, 2014. / ENGLISH ABSTRACT: Organisations are faced with ever increasing complexity. While there are many responses to complexity just as there are many definitions of complexity this thesis highlights the use of agile software development as a useful method. The case of agile software development is influenced by its people first approach and minimal process implementation to implement constraints in which phenomena of complexity can be understood. Chapter 1 introduces why complexity is relevant in the organisation today and the issues associated with complexity. A basic introduction to agile software development and why it is a response to complexity is tabled. Chapter 2 investigates the concepts of complexity. To highlight the difference between linear and non-linear systems and reductionistic thinking the ideas that not all things are complex is explored. Key concepts of complex systems are described to come to a better understanding of what entails a complex system. Information theory and dynamic systems are discussed including system attributes such as attractors and bifurcations. Finally the theory of complex adaptive systems is presented and a classification of all complexity theories is tabled. Chapter 3 is centred on agile software development, presenting practices and processes as a understanding of how agile software development is applicable to complexity. Three agile methods are identified. Chapter 4 presents the ideas of modelling and limits to understanding. Models of complex systems are useful but are limited, due to the properties of complex systems. The concept of mental models leads to models of organisations and how leaders need to help with transformation of these models towards models that are more aligned to agile type thinking. Chapter 5 looks at the core concepts, and practices of agile applied to complexity and why these are relevant in responding to complexity. Towards the end of chapter the role of narrative is explored in the terms of problem definition and solutioning in complex systems. Chapter 6 concludes the thesis with insights where agile software development is an appropriate response to complexity and the conditions in which it is not. / AFRIKAANSE OPSOMMING: Organisasies staar toenemende kompleksiteit in die gesig en alhoewel daar verskeie maniere bestaan om kompleksiteit teen te werk, asook verskeie definisies van wat kompleksiteit is, focus die tesis op aanpasbare ("agile") sagteware ontwikkeling as n bruikbare metode. Met eienskappe soos “mense/verbruiker/gebruiker – eerste” benadering asook minimale proses implementering, verskaf aanpasbare sagteware ontwikkeling die raamwerk waar binne die konsep kompleksiteit verstaan kan word. Hoofstuk 1 bespreek die kwessies rondom kompleksiteit en die relevansie daarvan in organisasies vandag. Verder word aanpasbare sagteware ontwikkeling kortliks bespreek en hoe dit gebruik kan word om kompleksiteit te verstaan, word getoon. Hoofstuk 2 ondersoek die verskillende konsepte random kompleksiteit. Daar word gekyk na linêre en nie-linêre stelsels asook die oortuiging dat nie alle dinge kompleks is nie word geondersoek. Sleutel kenmerke van komplekse stelsels word beskryf om sodoende ‘n better begrip te kry van wat ‘n komplekse stelsel behels. Informasie teorie en dinamiese stelsels word bespreek, insluitend kenmerke soos “attraktors” en “bifurkasies”. Laastens, word die teorie rondom komplekse aanpasbare stelsels bespreek en ‘n klassifikasie van alle komplekse teorieë word uiteengesit. Hoofstuk 3 fokus op “agile software development” en hoe sulke praktyke en prosesse toepaslik is op kompleksiteit. Daaropvolgend word drie aanpasbare metodes ge-identifiseer en individueel bespreek. Hoofstuk 4 verduidelik die idees rondom modellering en grense van begrip. Modelle van komplekse stelsels kan nuttig wees, maar weens die eienskappe van komplekse stelsels, is die nuttigheid beperk. Die konsep van mentale modelle lei tot modelle van organisasies en hoe leiers hierdie modelle moet transformer na modelle wat meer in-lyn is met agile denkwyses. Hoofstuk 5 kyk na die kern konsepte en praktyke waar “agile” toegepas word tot kompleksiteit en waarom dit relevant is om kompleksiteit teen te werk. In die tweede helfde van die hoofstuk word die rol van narratief ondersoek in terme van probleem-identifisering en die soek na oplossings in komplekse sisteme. Hoofstuk 6 sluit af met insigte tot aanpasbare sagteware ontwikkelingsmetodes as toepaslike oplossing tot kompleksiteit asook die toestande waaronder dit geld.

Generating code from software models is considered to be a new generation leap within software development methods. The objective of this M.Sc. project is to evaluate how different approaches to modelling and code generation affect embedded systems software development and propose recommendations on how to improve software development. Two product areas at Saab Surveillance EW Systems in Järfälla, Stockholm, are used as study objects. A research overview is made to highlight themes regarding modelling, code generation and software development in general. Based on these, interviews are held with system engineers and software developers at each product area, where they use different modelling and code generation approaches. The two development processes are described thoroughly. Challenges and advantages related to each area’s approach are investigated. Software development within product area A is affected by the product complexity and the larger scale of the development, including projects running over a longer time with more teams involved. Recommendations include enabling code generation by aligning it with other investments on process improvement and limiting the approach to generating some system components. Software developers within product area B can use full code generation, enabled by the limited product complexity. The product area is affected by software standards and external requirements on the process. Recommendations include extending the modelling approach to make it easier to trace functionality from system to software level. Conclusions are that both product areas can apply modelling and code generation to more software development activities to improve their respective development processes.