No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
Structured Rapid Prototyping: An Evolutionary Approach to Software Development
Abstract
An abstract is not available.
... Este tipo de prototipificação visa testar alternativas de implementação de partes do (21) Na realidade, têm sido consideradas diversas utilizações da prototipificação, a que correspondem os respectivos tipos de protótipo. Uma boa taxonomia pode ser observada em [Conne89,20]. Após ter sido elaborada a especificação de projecto e codificadas as partes necessárias, o programa é ainda sujeito a testes em que se procura encontrar pontos de inadequação aos requisitos, ou em que os padrões de desempenho não são os desejados, ao que se segue a afinação do programa. A partir daí, o programa encontra-se pronto para utilização e, se necessário, para manutenção. ...
... Metodologia de desenvolvimento por prototipificação evolutiva[Conne89, 24].No segundo ciclo é elaborada uma análise rápida do programa, que inclui especificações deliberadamente incompletas. As especificações resultam de entrevistas com o cliente/utilizador e conduzem ao protótipo inicial. ...
... Esta dimensão também pode ser referida como de controlo.(30) Segundo Connell e Shafer[Conne89, 9], o conceito das três dimensões é apresentado, pela primeira vez, em[DeMar82, 62]. Assim, neste estudo, este conceito é referido como as três dimensões de DeMarco.De seguida apresentam-se alguns aspectos gerais destes dois tipos de métodos, bem como considerações acerca da sua aplicação nas metodologias de desenvolvimento tratadas na essencialmente, através de uma "rede de funções" [DeMar82, 65]. ...
Consideram-se duas fases na produção de um programa educativo: a fase de concepção e
a fase de desenvolvimento. Analisam-se abordagens de concepção e desenvolvimento de
programas educativos em que se identificam dificuldades, quer na fase de
desenvolvimento de programas complexos, quer na transição entre as duas fases. Por esse
motivo, é elaborado um estudo da importância da aplicação da Engenharia de Software na
fase de desenvolvimento de programas educativos. Dadas as dificuldades na transição
entre as duas fases, é proposto um modelo, o modelo das três entidades, orientado para a
aplicação prática através de uma tabela que também se propõe, a tabela de
responsabilidades estendida. A aplicação deste modelo conduz a um desenvolvimento
com utilização de métodos orientados a objectos. Para a realização desse
desenvolvimento é apresentada uma proposta de abordagem, que se designou por
prototipificação continuadamente evolutiva. Esta abordagem é aplicada, na prática,
através de métodos orientados a objectos.
... Three relevant software engineering techniques are rapid prototyping, domain analysis, and object-oriented design. Rapid prototyping is a mechanism for delivering functional, but incomplete, systems to users to obtain feedback before completing development [1]. In some domains, rapid prototyping may not speed up total development time, but genetics is changing so rapidly that prototypes must be delivered because traditional programming techniques may produce systems which are obsolete before they are completed. ...
... The eight operators are select, project, join, product, union, difference, intersection and division. There are two database-independent integrity constraints: (1) No component of the primary key of a base relation is allowed to accept nulls; (2) The database must not contain any unmatched foreign key values. ...
... 2. Edges are composed of the labels and vertices of the graph in which the edge occurs, i.e., G=(V,E,L) where . These constraints correspond roughly to the integrity constraints for the relational data model: (1) No component of the primary key of a base relation is allowed to accept nulls; (2) The database must not contain any unmatched foreign key values. ...
Genome databases have specific requirements which limit the usefulness of some da- tabase management systems. By using more appropriate database technology, a data- base system can be developed for genome data. We have developed a data representation based on graph theory which captures the highly interconnected structure of genome data. Graphs are a language which can be tailored for describing genomic in- formation, and we develop a data model based on graphs which serves as the founda- tion of a graph database management system.
... An example is Multiview, which permits researcher to select their role as either doctor, facilitator, emancipator and social warrior depending on the setting (Avison & Wood-Harper 1990). Another example is prototyping, which exists in both facilitative (Connell & Shafer 1989) or collaborative forms (Gronbaek 1989). ...
... Unlike the fairly singular form of canonical action research, prototyping regards a fairly broad class of information system development techniques. Connell and Shafer (1989) identify several categories of prototypes within this class. There are "throw-away" design prototypes, e.g. ...
... TheConnell and Shafer (1989) evolutionary prototyping process. ...
Discussions of action research in information systems (IS) often proceed as if there were one definitive action research method. This paper describes and analyses the different frameworks, assumptions and goals that characterise the diverse forms of action research. A more inclusive action research paradigm is delineated that offers a basis for validating a wider range of IS research. Acceptance of the full range of the diverse forms of action research may enable the IS field to be more explicit about its research methodology, thereby enabling criteria to be improved and applied to a broader range of IS research.
... In this prototyping process, intended users are directly involved in test and analysis activities. The pragmatic paradigm has become especially prominent within the domain of application software design (Connell & Shafer, 1989). More recently, it has influenced the field of educational software, particularly interface design (Hix & Hartson, 1993) and to a limited extent the field of electronic learning materials design (Keursten, 1994;Moonen, 1996). ...
... Since these highly iterative approaches involve creating a prototype early in the process, some authors refer to these processes as rapid prototyping (Rieber, 1994;Tripp & Bichelmeyer, 1990). Others use the term rapid to indicate that there will be numerous and tightly scheduled interactive tryouts of multiple and, perhaps, competing designs as part of the process (Connell & Shafer, 1989). ...
This chapter will provide four different perspectives on educational design and development: instrumental, communicative, pragmatic, and artistic. The perspectives will be compared, and upon technical as well as social aspects of design will be their different views described. We will argue that designers should be aware of the usefulness of these perspectives and use the one that is most adequate for a certain design situation.KeywordsCurriculum developmentInstructional developmentDesign paradigmsDesign rationalityInstrumental approachDeliberative approachPrototyping approachArtistic approach
... In this prototyping process, intended users are directly involved in test and analysis activities. The pragmatic paradigm has become especially prominent within the domain of application software design (Connell & Shafer, 1989). More recently, it has influenced the field of educational software, particularly interface design (Hix & Hartson, 1993) and to a limited extent the field of electronic learning materials design (Keursten, 1994;Moonen, 1996). ...
... Since these highly iterative approaches involve creating a prototype early in the process, some authors refer to these processes as rapid prototyping (Rieber, 1994;Tripp & Bichelmeyer, 1990). Others use the term rapid to indicate that there will be numerous and tightly scheduled interactive tryouts of multiple and, perhaps, competing designs as part of the process (Connell & Shafer, 1989). ...
This chapter will report some preliminary findings of a study on educational design and development practices in the Netherlands. The purpose of the study is to describe the strategies that professional education and training developers use in practice. Twenty-four developers were interviewed intensively and documents of their projects were analyzed. The data show that there are many differences between developers, but that there are also several common themes. This paper discusses the most important results in both the technical-professional and socio-professional domain, as well as the overall structuring of the process.
... Au niveau du développement des SADIPE, la méthode la plus utilisée est le prototypage (Connell et Shafer, 1989). Cette méthode permet la flexibilité au niveau du développement, l'amélioration des extrants projetés et une plus grande satisfaction de l'utilisateur. ...
... La méthode de conception du SE utilisée est le prototypage, soit l'une des formes de la recherche-action (Baskerville et Wood-Harper, 1998). Cette méthode permet l'élaboration d'une solution par incréments, de façon itérative, c'est-à-dire qu'elle permet de valider progressivement et de modifier le prototype (Connell et Shafer, 1989). ...
Résumé Depuis quelques années, deux éléments ont été considérés des plus importants dans les organisations : la capacité des technologies de l'information à transformer le pouvoir compétitif de ces dernières ainsi que l'ouverture des marchés favorisée par l'abolition des barrières commerciales. En raison des différentes limites des PME au niveau de l'acquisition, du traitement et de l'exploitation des informations, un système d'aide à la décision intelligent propose aux propriétaires-dirigeants un diagnostic comparatif afin d'évaluer la performance de son entreprise en la comparant avec d'autres entreprises semblables. Le prototype de démonstration a été développé en considérant les pratiques de gestion des ressources humaines ainsi que l'expertise de spécialistes reconnus dans le domaine. Une première validation du système démontre que cette technologie peut assister les dirigeants dans les PME. Les résultats de cette recherche démontrent également que ce prototype devra être enrichi avec les autres domaines de la gestion.
... In this prototyping process, intended users are directly involved in test and analysis activities. The pragmatic paradigm has become especially prominent within the domain of application software design (Connell & Shafer, 1989). More recently, it has influenced the field of educational software, particularly interface design (Hix & Hartson, 1993) and to a limited extent the field of electronic learning materials design (Keursten, 1994;Moonen, 1996). ...
... Since these highly iterative approaches involve creating a prototype early in the process, some authors refer to these processes as rapid prototyping (Rieber, 1994;Tripp & Bichelmeyer, 1990). Others use the term rapid to indicate that there will be numerous and tightly scheduled interactive tryouts of multiple and, perhaps, competing designs as part of the process (Connell & Shafer, 1989). ...
Over the years, many authors have tried to describe, conceptualize, and visualize the instructional design or development
processes via a variety of process models. Most descriptions imply a rather homogeneous view of design, depicting it as an
overall problem-solving process following general phases such as analysis, design and development, implementation, and evaluation
(ADDIE). However, researchers who have investigated how instructional designers actually work suggest that the process is
much more heterogeneous and diverse than these ADDIE models suggest. This study collected case study data from 24 instructional
designers in six different settings; they were identified as experts by their peers. The design processes they used for a
specific project were compared to four different paradigms created from the literature. The four paradigms and their underlying
theoretical foundations are described and illustrated. Detailed results are reported, and reasons that designers did or did
not use a particular paradigm are considered.
... The application has been developed following a rapid prototyping paradigm (Connell and Shafer 1989). There have been four different prototypes that were used in the feedback sessions. ...
It can be difficult to assess the design of, and learning, within Massive Open Online Courses (MOOCs). It is especially hard when trying to analyse this at the level of the individual learner. This study has developed a tool, inspired by Sankey diagrams, to visualise learners’ behaviour and paths through MOOC content. This tool can be used to investigate if learners are interacting with the content as planned when the course was designed. It has been designed iteratively through four stages of rapid prototyping. This paper presents the narrative of the development of the tool with an emphasis on validation via feedback from three user groups at each prototype stage.
... If a solution worked, then what was before a prototype may have been a part of the products delivered to the customer. Therefore, their overall strategy can also be described as evolutionary prototyping, consisting of a number of cycles that each improve the product over time [29]. ...
This study explores the value of visualizing the prototyping activities in a new product development process from idea to production. Through a case study of a hardware startup, we present a visualization of their prototyping processes, from early idea to the introduction of several product generations to market. We call this visualization technique ProtoMapping. Analyzing qualitative and quantitative parameters of the ProtoMap allows us to understand how prototyping strategies can change over the course of a product development process. Specifically, we focus on the prototyping of parallel concepts, iterations of concepts, manufacturing processes used for prototypes, prototype media, prototype tests, as well as prototyping of isolated or integrated systems. Based on this longitudinal analysis, we present a number of insights that are otherwise difficult to extract. We observe how parallel prototypes of isolated systems can be used to explore the solution space and later be synthesized into prototypes for integrated systems. Furthermore, we understand how the need to scale up production can lead to increased prototyping activities, as several parts of a product must be redesigned. This study illustrates the utility of a retrospective visualization approach and serves as the first step in formulation of generalized guidelines for prototyping strategies for holistic product development, through further case studies.
... Two methods were used in this research: rapid prototyping [18] and the case study method [19]. ...
... While effective, this process often takes a considerable amount of time and resources to create and demonstrate the different prototypes. As such, this model is often suited for larger organizations with a greater than average amount of research and development resources [20]. ...
Developing large scale software projects involves huge efforts at every stage of the software development life cycle (SDLC). This led researchers and practitioners to develop software processes and methodologies that will assist software developers and improve their operations. Software processes evolved and took multiple approaches to address the different issues of the SDLC. Recently big data analytics applications (BDAA) are in demand as more and more data is collected and stakeholders need effective and efficient software to process them. The goal is not just to be able to process big data, but also arrive at useful conclusions that are accurate and timely. Considering the distinctive characteristics of big data and the available infrastructures, tools and development models, we need to create a systematic approach to the SDLC activities for BDAA development. In this paper, we rely on our earlier work identifying the characteristic and requirements of BDAA and use that to propose appropriate models for their development process. It is necessary to carefully examine this domain and adopt the software processes that best serve the developers and is flexible enough to address the different characteristics of such applications.
... Various forms of prototypes have been identified in literature, based on differing stages of development (Connel & Shafer, 1989;Nieveen, 1999). In earlier iterations, the A curriculum perspective 126 product of the design stage may be an initial prototype that globally demonstrates the nature of the design. ...
... This model therefore emphasises the importance of collaborative work between developers and users, which is necessary for the product under development. Early input from end-users not only has the potential to highlight problems earlier in the design phase, this method can shorten the development time of a project [9]. Besides helping to ensure that the actual needs of users are met, it minimizes the risk of conflict between users and the development team. ...
This paper introduces a new proposed framework for the development process of interface design for Malaysian interactive courseware by exploring four established model in the recent research literature, existing Malaysian goverment guidelines and Malaysian developers practices. In particular, the study looks at the stages and practices throughout the development process. Significant effects of each of the stages are explored and documented, and significant interrelationships among them suggested. The results of analysis are proposed as potential model that helps in establishing and designing a new version of Malaysian interactive courseware.
... Through numerous newsgroups, websites, blogs, software conferences, the word about agile methodology spread day by day among thousands of software engineers world-wide to an extent that today, it is acknowledged as an alternative to the waterfall and V-model in uncertain environments. Moreover, even the academic world has increasingly been teaching agile methodology and thereby acknowledged the conceptual difference to seemingly similar methods like rapid prototyping (Connell & Shafer, 1989) -the difference lies in the specification of their practical implementation, the software development practices. Such practices as specified by agile methods are called agile practices in this study. ...
... It might be done for the entire program, or for several components. Different forms of prototypes have been identified in the literature, including throwaway; quick and dirty; detailed design; non-functional mock-ups, and evolutionary (Connel and Shafer 1989). For example, a paper prototype of a software program would constitute a non-functional mock-up. ...
There are no one-size-fits-all steps for tackling different design challenges within the context of education. There are, however, processes and activities that are often useful. Developing a repertoire so that designers can select and use the most fruitful and fitting approaches for specific situations is the focus of this chapter. After discussing this phase in relation to those of analysis and evaluation, attention is given to how both analytical and creative perspectives can serve the work of design and construction. The body of the chapter is devoted to presenting specific activities that can be undertaken during design (exploring and mapping solutions) and construction (actually building the solutions). This chapter presents ideas in linear fashion, which loosely approximates the order in which these activities might logically be carried out. However, each design project is different. Not all activities described here are useful in all projects, others are likely to be added, and several activities described in this chapter often take place simultaneously.
... Different forms of prototypes have been identified in literature, including: throw-away; quick and dirty; detailed design; non-functional mock-ups; and evolutionary (cf. Connell & Shafer, 1989). For example, a paper prototype of a software program would constitute a nonfunctional mock-up. ...
... Rapid prototyping model (Connell & Shafer, 1989) No; iteration occurs prior to coding Yes; early prototype up-front in process N/A Rational Unified Process (Kruchten, 2002) Yes; variable length, driven by iteration sizes ...
... This definition is based on the work of Boar [Boar83] and Connell [Connell89]. The important distinguishing features for a prototype (according to our definition) therefore is that it must be able to produce it at low costs -on the other hand a prototype must be executable und must show essential system functionality. ...
Currently, use cases (scenarios) and contracts play an increasing important role in software development. For scenarios this is mainly due to the fact that the application of UML and UML related process (e.g., the Rational Unified Process) leads to an augmented application of use cases and UML interaction diagrams throughout the software development cycle. Furthermore, contracts also have an increasing importance due to the integration of the Object Constraint Language (OCL) in the UML and due to the MDA-activities of the OMG. Currently, only tools exist that support the specification of scenarios but most of them do not support the entire software development cycle. For contracts the support available is restricted to editors, parsers and execution environments – a prototyping oriented approach is not supported by most toolsets available. We therefore developed a set of tools that support prototyping-oriented software development with scenarios and contracts. The developed toolset itself is implemented as prototype and laboratory experiments show the feasibility of the chosen approach.
... There are a large number of widely varied methods available for information systems developers. These include structured approaches (e.g., Yourdon 1989), prototyping approaches (e.g., Connell and Shafer 1989), information engineering (e.g. Finkelstein 1989), soft systems (e.g., Checkland and Scholes 1990), sociotechnical (e.g., Mumford 1983), object-oriented (e.g. ...
The organizational structure has to do with human relationships, and is distinguished from the various artifacts (like information technology, systems development methods, and other mechanical products) that reflect those relationships. Information technology represents a first-level artifact and systems development methods represent a second-level artifact. This paper explains and illustrates a theory in which method engineering introduces third-level structural artifacts in organizations. A demonstration is included that uses security as one of the system imperatives that must be captured by third-level structural artifacts such as method engineering. This demonstration shows how method engineering may produce methods that are more complete and more harmonized with the organizational situation.
... The software engineering and information systems development literatures suggest a wide variety of approaches to prototyping (cf. Andriole, 1990; Arthur, 1992; Connell and Shafter, 1989; Sage and Palmer, 1990). The selection of prototype form should be based on the goals of the current development phase and the information that must be derived from the prototype. ...
This chapter presents a human systems integration framework for user-centered systems engineering. The framework emphasizes methods for creating, structuring, and applying models and processes needed to identify and address human systems integration issues across all phases of the acquisition lifecycle. The chapter discussion centers on the opportunities and challenges of the system acquisition lifecycle, showing how HSI issues can be incorporated into systems engineering processes. More specifically, the framework provides a guide for the systems engineering manager to better appreciate and employ cognitive systems engineering methods to define problems, identify and represent cognitive task requirements, develop design goals, and implement and evaluate system designs for human machine decision making.
... Research on how designers design suggest why teaching design within the context of teaching a programming language is so difficult. This research [9], [13], [14], [15], [16], [17], [18], [19] and insights from software engineers [20], [21], [22], [23], [24], [25] give us two general characteristics of the process of designing software: ...
Abstract This project is demonstratingthe feasibility of using the object-oriented paradigm,to teach students software design in a nonprogramming context. The program, developed using principles of user-based, prototyping design, teaches students to create responsibility-driven designs of computer games. Investigations with high school students with little or no knowledge,of computers and senior computer science majors have demonstrated that students can indeed learn to use Class-ResponsibilityCollaborator (CRC) cards to produce creditable high-level designs in a relatively short time whether or not they have programming,experience and can generalize what they have learned to a new design. Computer science majors created more complete designs and demonstrated a deeper understanding of the design process than the high school students, but they still found the experience valuable and they still showed,room for improvement. Both samples generally find the process interesting and relatively painless. 3 1.0 Introduction Studies of the learning outcomes,of introductory programming,courses have shown relatively poor understanding of the programming language under study, little development of problem solving skills, and little progress toward the central issues of analysis and design, e. g., [1], [2], [3], [4], [5], [6], [7], [8], [9], [10]. In addition, both research and the practical experiences of expert software designers have suggested that the analysis of the problem domain,and the design of an overall plan of the software are more central to the development,of software than is learning to code. Students in
... At the heart of these more flexible models was the notion that a prototype or an actual working version of the software should be released to customers at an extremely early stage of development. 1,2 To facilitate this process, development was often broken into several subcycles, each geared to producing a subset of the final product's functionality. 3,4 So, a large number of software development practices have been proposed over the past 40 years, many as part of more comprehensive development models. ...
... " Around the same time Boehm was developing the rapid prototyping model, other engineers were coming to similar conclusions (Dichter and Pease, 1995, 27). 6 Connell and Shafer (1989) developed the technique called structured rapid prototyping. That is, in their book Structured Rapid Prototyping, they developed an approach that evolved into a development process. ...
Purpose
The purpose of this paper is to review the content, contributions and subsequent developments of the seminal paper by Barry Boehm, “A spiral model of software development and enhancement” written in 1988. The relationships of this paper to software development, agile projects, real options and present practice are put into perspective.
Design/methodology/approach
Basically an essayist approach is taken. First, the contents of Boehm's paper are reviewed and then associated with subsequent developments.
Findings
Review of the paper as published represents a documentation of cutting‐edge software development as it existed at the time. Fundamentally it suggests the viability of a non‐linear, customer‐influenced, development approach.
Practical implications
This basic approach illustrated in the spiral model of course has found its way into complex project approaches and management.
Originality/value
This paper follows the lines of increasing attention to classics, which is the purpose of this special issue of the journal. In particular, attention is called to the transition of thought on projects and project management from supplier‐oriented, linear processes to customer/client‐influenced, non‐linear ones.
... Database systems provide support for large amounts of data, and software engineering addresses the need to build systems which frequently change [Connell and Shafer 1989;Prieto-Diaz and Arango 1991;Coleman et al. 1994]. Two subareas of artificial intelligence have contributed representation languages which can be used to describe genome data: knowledge representation and computational linguistics. ...
Genome databases have specific requirements which limit the usefulness of some da-tabase management systems. We have developed a data representation based on graphs which capture the highly interconnected structure of genome data. Graphs form a lan-guage which can be tailored for describing genome information, and we develop a data model based on graphs. Our graph data model defines a graph as a collection of vertices, edges, and edge la-bels. We extend the basic definition of a graph by adding constructs to capture external identifiers, ordered collections of data, packaged graphs, and graph templates for query-ing and creating updatable views. We also describe a graph schema language which can be used for conceptual modeling.
... But literature from early1990's suggested that researchers were reached to some consensus on the definition of prototype and prototyping. In [65, 70], [70] phase oriented development model and prototyping oriented model complement each other. The major difference between prototyping oriented software development and phase oriented software development are deliverables, iterative cycle, requirements. ...
... Alternative design paradigms such as rapid prototyping and concurrent engineering also require new tools as they become mainline development approaches. As has been pointed out elsewhere (e.g., Connell & Shafer, 1989; Nieveen & Gustafson, 1999), powerful prototype creation and testing tools are essential for rapid prototyping to be both efficient and effective . Similarly, concurrent engineering requires tools to support a high degree of collaboration among a variety of specialists, each with a different perspective. ...
This article critiques the instructional design tools described in the special issue of Educational Technology Research and
Development, Volume 50 Number 4, “Computer-Based Tools for Instructional Design.” Although focusing on four tools, (a) digital
management systems, (b) CASCADE, (c) knowledge management systems, and (d) ADAPTIT, the author also comments on the introductory article (van Merriënboer and Martens), and compares the four described tools
with earlier models.
Cancer Treatment Disease Application Software Technology in Medicine
In this paper, we discuss co-innovation between Lead Users and Producers. To practically apply the user innovation theory to product development, two methods have been used: the lead user method and user-community based theory. Recently, community-based methods have become main stream in this field of research. On the other hand, the lead user method has been less noticed. In this paper, we show the significance and problems of the co-innovation between lead users and producers through interpreting a case of the development process of an innovative skating blade by a top figure skater from the two perspectives: lead user theory and the sticky information hypothesis.
With the increasing interest in applying object oriented technology, more and more software developers are shifting from the procedural to the object oriented paradigm. This paper presents an incremental build framework to software development during the paradigm transition. The incremental build model has been found to be a practical and effective approach in managing software projects. This paper also summarizes the experience and lessons learned in an industrial application of the incremental build framework. The incremental build framework also proves to be effective in facilitating phased programming paradigm transition.
Heute gibt es mehr als vierzig Analysemethoden, die den Anspruch erheben, objektorientiert zu sein.1 Nicht alle sind wirklich objektorientert, und viele spielen praktisch keine Rolle. Eine Umfrage in der Internet-Newsgroup „comp.object“ im Herbst 1992 und eine Umfrage unter den Lesern der Zeitschrift „OBJEKTspektrum“ im Frühjahr 1994 zum Einsatz objektorientierter Analysemethoden brachte folgende Ergebnisse:2
Wenn auch beide Umfragen sicher nicht repräsentativ sind, bestätigen sie doch den Eindruck, den man auf Messen und Ausstellungen gewinnt: Die Methoden von Coad/Yourdon, Rumbaugh et al., Shlaer/Mellor und Booch sind „marktbe-herrschend“.
Die moderne Informations- und Produktionstechnik bietet die Möglichkeit, vollständige und abwechslungsreiche Tätigkeiten zu unterstützen. Um technische, humane und organisatorische Rationalisierungspotentiale gleichermaßen auszuschöpfen, ist es erforderlich, die rechnergestützte Arbeit als Gesamtheit zu betrachten. Dies erfordert bei der Entwicklung von Software, die organisatorischen und personellen Einsatzbedingungen der Software in der Anforderungsanalyse und im Entwurf mit zu berücksichtigen. Den übergeordneten Zielen der Optimierung von Arbeitsabläufen und der persönlichkeitsförderlichen Arbeitsgestaltung sind dabei die Ziele der Software-Entwicklung unterzuordnen. Persönlichkeitsförderliche Merkmale der Arbeit werden besonders in dezentralen und gruppenorientierten Arbeitskonzepten berücksichtigt. Aufgrund der weitgehenden Selbststeuerung in Arbeitsgruppen gewinnt Software den Charakter eines Arbeitsmittels zur Unterstützung der Arbeitsaufgaben und zum Erwerb individueller Kompetenzen der Gruppenmitglieder.
Gerne denke ich an mein fünftes Studiensemester zurück, als ich durch den Besuch der Vorlesung „Werkzeugmaschinen“ an der TU München erstmals Kontakt zu Herrn Professor Milberg bekam. Durch seinen begeisternden Vorlesungsstil wurde mein besonderes Interesse fir das Gebiet der spanenden Werkzeugmaschinen und Fertigungsverfahren geweckt. Es entstand sehr bald mein Wunsch, über eine Diplomarbeit an seinem Lehrstuhl eine spätere wissenschaftliche Tätigkeit mit dem Ziel der Promotion anzustreben. Als akademischer Lehrer und Forscher war er mir während der gemeinsamen Zeit am iwb von 1990 bis 1993 stets Vorbild und Ansporn. Mit großem Bedauern wurde am Institut sein Wechsel in den Vorstand der BMW AG aufgenommen, sah man dies doch einhellig als erheblichen Verlust für das iwb. Sein heutiges erneutes Wirken im Dienst von Lehre und Forschung auf ingenieurwissenschaftlichem Gebiet ist eine große Bereicherung fir uns alle. Zu seinem runden Geburtstag gelten Herrn Milberg unsere besten Wünsche. Wir freuen uns über die überwältigende Resonanz, die der Aufruf zu dieser Festschrift gefunden hat.
Software ist zu einem wichtigen Wirtschaftsfaktor geworden, und die Softwareindustrie ist eine aus unserem Wirtschaftsleben nicht mehr wegzudenkende Wachstumsbranche. Softwareprodukte werden immer häufiger zentrale Bestandteile komplexer Systeme, die technische oder betriebswirtschaftliche Prozesse steuern oder unterstützen. Aber auch im täglichen Leben werden wir immer stärker — meist unbemerkt — von funktionierender Software abhängig. In einzelnen Bereichen, wie z.B. in der Flugsicherung oder in der Energietechnik, hängen Sicherheit und Leben vom richtigen Funktionieren der dort eingesetzten Software ab. Die Funktionsfahig-keit und Zuverlässigkeit von Software ist Voraussetzung für die Funktionsfähigkeit des Gesamtsystems, dessen Bestandteil sie ist.
The sections in this article are
We propose a new innovation model designed to accelerate the rate of learning from provider payment reform initiatives. Drawing on themes from operations research, we describe a new approach that balances speed and rigor to more quickly build evidence on what works in delivery system redesign. While randomized controlled trials provide "gold standard" evidence on efficacy, traditional RCTs tend to be static and provide information too slowly given the CMMI tagline of "We can't wait." Our approach speaks to broader needs within health financing and delivery reform for testing that while rigorous recognizes the urgency of the challenges we face.
Published by Elsevier Inc.
Software prototyping is an attractive altemative approach to systems de-velopment, within which end-users exercise with a series of prototypes in a working environment. Such interactions offer an excellent scope for meaningful participation of end-users in the system development process. This is crucial for the success of a project. However, despite its significance, relatively little attention has been paid towards the management of end-user involvement. Advoce.tes of prototyping approach merely ex-press a need for active user participation in the prototype development process. They fail to offer any practical guidelines. Moreover, few documented case studies concerning management of user involvement within a prototype project have been published. It is argued that managing user participation is not ~ trivial task and it requires consi-derable attention. In this paper, the authors propose a framework that relates degree of user involvement with the type of prototyping approach adopted and the stages of prototype development process.
Extracting pertinent and useful information from customers has long plagued the process of requirements elicitation. This paper presents a new approach to support the elicitation process. This approach combines various techniques for requirements elicitation which include model-based concept acquisition, goal-driven structured interview and concept reuse. Compared with the available approaches for requirements elicitation, the most significant feature of our approach is that it supports both the automation of interaction with customers by using domain terminology, not software terminology and the automated construction of application requirements models using model-based concept elicitation and concept reuse. The capacity of this approach comes from its rich knowledge which is clustered into several abstract levels.
This article describes a Prototyping Environment for Information Systems based on Semantic Data Models. This environment intends to reduce development and maintenance costs, handling all the development process at a design level. The approach is based on an exhaustive analysis of the data model. The rules that a prototype (generated from the model) must consider to guarantee the consistency and integrity of the data base can be inferred from the analysis. The run-time representation of the model is an ER-T (Heuser and Peres, 1991). A prototype of a development environment for this method has been implemented and is described.
In global markets, firms should be connected to a plurality of external actors to
acquire knowledge for sustainable competitive advantage. Over the last decade,
knowledge management scholars have highlighted the opportunity to acquire a
wide spectrum of knowledge from clients, not limited to their characteristics and
preferences. This opportunity is particularly evident, considering small software
firms operating on commission, due to their interaction with clients; at the same
time, it represents a challenge for small companies, because the knowledge
acquired from clients is usually context-specific and can become an opportunity
This paper combines theoretical models on organisational and Information Systems (ISs) change with the experiential theorising of practitioners from a case study site. Contemporary strands of IS and organisational change literature were reviewed, grouping common themes into planning, leadership, learning and culture approaches. This theoretical basis was extended through a case analysis of an IS organisation in the banking industry which had undergone wide ranging and successful strategic change. Twenty in-depth interviews were conducted with senior experienced change practitioners from across the organisation. Three propositions on IS and organisational change theory were developed from the finding for this research. Firstly, IS change is a subset of organisational change which is frequently noted and argued through existing academic or ‘espoused’ change theories. Secondly, whether successful or unsuccessful, strategic change is in itself a rich learning experience which may be leveraged through experience, intuition and self-reflexion. Thirdly, managers develop their own ‘theories in use’ of change based on experiential learning and apply them in a highly context specific ‘informed’ way. The main contribution of the research is a ‘meta-learning’ framework for informing IS strategic change which suggests valuable theoretical insights, a practitioner implementation process and proposals for further research directions and limitations.
The risks associated with making the transition from requirements to design are high. Undiscovered errors in requirements are expensive to fix in the later stages of the software development, but they can be difficult to find prior to design and implementation. One approach to this problem is to use rapid prototyping. This paper will explore some of the issues involved in rapid prototyping, and will discuss the application of a particular rapid prototyping tool to the prototyping of a portion of a system being developed for the Canadian military
This study uses an organizational psychology lens to gain a fundamental understanding of how Agile Practices positively influence socio-psychological mechanisms that lead to a successful project. The theoretical framework of this study is based on a causal model of teamwork derived from innovation research with the major constructs of coordination capability and knowledge growth. We will investigate the impact of Agile Practices on these constructs through well-researched teamwork variables such as goal commitment and social support, and by the new constructs adaptivity and open communication. We will then determine the impact of these constructs on project performance. In addition, we will analyze the moderating effect of team autonomy on the relationship between coordination capability and project performance. The quantitative field study will be conducted in Nov 2008 and targets a sample size of 60 agile projects.
Abstract Empirical studies have shown that, in many fields, product end users rather than product manufacturers,are the first to prototype ,and apply innovations that later become ,the basis of important commercial ,products. This fundamental ,finding has the potential to significantly affect the way ,that product developers and market researchers go about ,the idea generation stages of new product and service development. Inthis study, we explore aspects of user innovation that are central to the systematic tapping of user innovation as an input to new,product and service idea-generation. By,studying data drawn from a sample of 122 Australian libraries using a type of library IT system called an “OPAC,” we confirm that users do frequently innovate. What is new is that we find that innovating users have two characteristics – leading edge status and in-house technical capability - that can reliably distinguish them from non-innovating users. We also find that user-developed innovations are frequently of potential commercial interest to product manufacturing firms, and that users are often willing to share or trade information about their innovations with fellow users and inquiring manufacturers. We ,develop ,and test an economic ,model ,which ,explains this behavior. We ,conclude ,by discussing ,how ,our findings might ,affect approaches ,to idea generation in product and service development,processes.
This report details the development of the DesignPro interactive computer-based advisory system for user-computer interface (UCI) design, prototyping and evaluation. DesignPro permits designers of user computer interfaces to represent requirements, to build prototypes, and to evaluate their impact -- all via a "workbench" of user accessible functions. DesignPro supports the UCI designer; it does not call for the replacement of human UCI expertise in the design process. The methodology assumes that commercial-off-the-shelf (COTS) software can be used to create an integrated environment for designing, prototyping and evaluating interactive user computer interaction routines. The overall process includes interaction among knowledge templates to develop a requirements model that, in turn, helps yield displays and UCI routines which, in turn, suggest a prototyping strategy which, in turn, identifies evaluation tactics. Anchored in the systems engineering approach to interactive systems design and development, an initial prototype of DesignPro was released in January 1993; refinements were made to the prototype with a final prototype released in August 1995. The prototypes were used to validate workstation requirements and to communicate what the system does, as well as permitted the integration of concepts, tools, and COTS software programs into the design.
This article documents a process for software development designed and successfully used by the Academic Computing Department of the Summer Institute of Linguistics (SIL) in Dallas, Texas. Standing at the start of a complex five-year development project, the department realized that seat-of-the-pants management techniques would not be successful. The goal of the paper is to describe the authors' process in enough detail that readers can borrow from it to define or improve their own development process. The process embodies a few new ideas, a few twists on old ideas, and many time-honored and often-repeated ideas.
New approaches to teaching introductory computer science are sorely needed. Current instruction in programming has been shown to result in relatively poor understanding of the programming language under study, little development of problem solving skills, and little progress toward the central issues of analysis and design (e. g. An alternative approach would be to teach students software design before teaching them a programming language. In this approach students would not actually produce a finished software application, because they would not learn to program. Rather, their task would be to learn to think through what needs to be included in a particular program (in our case, a computer game) and how to organize the parts into a structured whole that has the characteristics desirable in a good software design--comprehensibility, nonredundancy, modifiability, reusability, and encapsulation. Although students would not implement their designs, they could experience the connection between design and implementation, if staff programmers implemented one of the student designs. Teaching software design in this way promises to provide a learning experience with three features that do not often coexist. The design process requires analytic, logical, and integrative reasoning. Designers start with an ill-structured problem. They have to make explicit the implicit requirements of that problem and then generate a pathway from goal to solution. In addition, they must do so with a number of goals at the same time, which means they must integrate these disparate threads into a common structure. Such thinking is difficult and time consuming and students typically prefer to escape into simpler, less demanding modes of functioning (c. f., Dalbey, Tourniaire, & Linn, 1986, with structured diagramming in programming students, Kurland et al., 1986, with learning LOGO programming, Sims-Knight, 1990, with algebraic story problems). In analysis and design of software students can not avoid using their most powerful reasoning skills.
Uncertain and dynamic environments present fundamental challenges to managers of the new product development process. Between successive product generations, significant evolutions can occur in both the customer needs a product must address and the technologies it employs to satisfy these needs. Even within a single development project, firms must respond to new information, or risk developing a product that is obsolete the day it is launched. This paper examines the characteristics of an effective development process in one such environment---the Internet software industry. Using data on 29 completed development projects we show that in this industry, constructs that support a more flexible development process are associated with better-performing projects. This flexible process is characterized by the ability to generate and respond to new information for a longer proportion of a development cycle. The constructs that support such a process are greater investments in architectural design, earlier feedback on product performance from the market, and the use of a development team with greater amounts of "generational" experience. Our results suggest that investments in architectural design play a dual role in a flexible process: First, through the need to select an architecture that maximizes product performance and, second, through the need to select an architecture that facilitates development process flexibility. We provide examples from our fieldwork to support this view.
ResearchGate has not been able to resolve any references for this publication.