No full-text available
To read the full-text of this research,
you can request a copy directly from the author.
... a https://www.franceinter.fr/emissions/secrets-d-info/secrets-d- info-27-janvier-2018 Le développement en cascade proposé par Royce (1970) est l'une des méthodes ayant connu une forte notoriété dans la sphère des développeurs. Elle est fondée sur l'anticipation des demandes des utilisateurs, la définition complète du futur produit et une documentation exhaustive. ...
... La figure 3 permet de distinguer les différentes étapes successives à la création d'un programme selon le stepwise model. Il est par ailleurs l'un des premiers modèles à relever le défi d'intégrer une préparation rapide pour les tests et la modification du code développé (Royce, 1970). Ce modèle découle des problèmes causés par la taille croissante des logiciels, qui ne pouvaient pas être gérés par un seul programmeur. ...
... Dans son papier intitulé, Managing the development of large software systems en 1970, Winston Royce a été le premier acteur à avoir formulé une approche de conception qui fût le plus largement adoptée. Il proposa un modèle de cycle de vie pour atténuer le risque d'échec dans les projets logiciels complexes qui reposait sur l'opinion largement répandue de bons principes d'ingénierie système de l'époque (Royce 1970, Sommerville 1996. Ce modèle a par la suite été caractérisé par de nombreux praticiens comme un modèle de développement « traditionnel ». ...
Cette thèse a pour objectif d’expliquer la manière dont les grandes organisations généralisent les méthodes agiles à l’ensemble de leurs projets SI. Compte tenu des potentiels bénéfices à la clé, la tendance n’est plus d’expérimenter ce mode de fonctionnement mais plutôt de le généraliser à tous les projets. Or, la généralisation requiert des efforts importants en raison du fait que les méthodes agiles génèrent plusieurs changements au niveau des rôles, des processus et de la culture. Dans cette optique, nous nous sommes appuyées sur un design de recherche qualitatif reposant sur une analyse processuelle de quatre études de cas complexes. Nous parvenons ainsi à identifier les ingrédients favorisant des dynamiques de généralisation planifiées et émergentes
... The removal of known limitations of previous method(s) is a typical motive for the launch of a new method (e.g. Boehm 1988;Royce 1970;Vidgen and Wang 2009). Prior research has classified ISD methods in a myriad ways (Mahmood 1987). ...
... We do not know, why organizational / business context characteristics appear to have received little attention in prior ISD method selection research. The strong influence of the plan-driven waterfall (Royce 1970) and stage-gate based methods is one possible reason (Avison and Fitzgerald 2006). In these ISD methods, business requirements are specified and agreed prior to the start of technical ISD work, an ISD project is re-planned should business requirements change, and the results of previous project phase(s) are accepted at a decision gate prior to the start of the next phase. ...
... Bennington presented one of the first plan-driven ISD methods in 1956 (Benington 1983). As new plan-driven ISD methods were launched, such as the notorious waterfall model in 1970 (Royce 1970), they often borrowed, and still borrow, concepts and practices from the plan-driven project management and systems engineering realm (McCracken and Jackson 1982). Plan-driven ISD development builds on the premise that the business requirements of an IS to be developed as well as the tasks, resources, responsibilities and the timeline of an ISD project can -and need to -be planned in detail before the ISD work and project execution start. ...
Several change-driven (agile) information systems development (ISD) methods have been launched during the recent years. In addition to agile ISD methods it is still possible to succeed also with plan-driven ISD methods. To facilitate ISD method selections that maximize the probability of ISD project success we crafted and evaluated an ISD method selection framework based on the idea of matching the properties of ISD methods and the characteristics of the business contexts where ISD methods are used. We conducted a systematic literature search to evaluate whether the proposed framework is also able to capture the findings of prior ISD method selection research and to guide future empirical research. From over 1000 potential articles we identified 42 articles that address ISD method selection. We discovered that the proposed framework was able to explain the findings of prior research.
... Le modèle en cascade -Waterfallest également mentionné, et défendu comme un modèle en spirale amélioré qui intègre l'ingénierie simultanée. Dans le cadre de la cartographie, le modèle en cascade est soutenu par (Royce, 1970). Ces deux processus, en spirale (A) et en cascade (B) sont représentés ci-dessous par la Figure Royce (1970) Enfin, à noter que cette approche de conception systématique peut être rapportée à une approche qualifiée de « traditionnelle » du développement de produits, et est donc possiblement amenée à évoluer au profit d'autres approches (Hehenberger, 2015). ...
... Dans le cadre de la cartographie, le modèle en cascade est soutenu par (Royce, 1970). Ces deux processus, en spirale (A) et en cascade (B) sont représentés ci-dessous par la Figure Royce (1970) Enfin, à noter que cette approche de conception systématique peut être rapportée à une approche qualifiée de « traditionnelle » du développement de produits, et est donc possiblement amenée à évoluer au profit d'autres approches (Hehenberger, 2015). ...
Our research is framed within the “ubiquitous digital and connectivity era” that has led to numerous transformations in the industrial landscape, especially in designed products and their development. Thanks to digital and connectivity technologies, products can now evolve towards multidisciplinary products, fitted with new capacities and functions. These multidisciplinary products, as we define them, emerge from the integration of contributions from mechanical, electrical, electronic, software, and information and communication technologies. In this work, mechatronic products, cyber-physical systems, and “smart” products are especially considered for their multidisciplinary nature.
This product evolution induces two types of complexity, product intrinsic complexity and the complexity related to the organization required for its development. In this sense, it is expected that companies adapt how they develop these products. Product development adaptation relies on a variety of “concepts and techniques” (a formulation that encompasses the approaches, processes, methods and tools) which can be organized to form what has been termed in this work a “development structure”. Accordingly, our research focuses on the link between the product and the associated development structure to be deployed. However, due to the monodisciplinary anchoring of most concepts and techniques, the generation of a structure tailored to multidisciplinary products remains a challenge for many companies. Consequently, a support for product developers seems necessary. This support would involve both a cartography of the scientific literature to identify development structures and an understanding of how companies are currently developing their multidisciplinary products. These scientific literature and industrial practice facets have guided the elaboration of our proposition.
The major contributions of this work include the following. First, it proposes a four-level model for structuring development, based on definitions and a decision tree to organize the concepts and techniques in approaches, processes, methods and tools. It then establishes graphical representations, called “cartographies”, of the development of mechatronic products, cyber-physical systems and smart products, before synthesizing them into a multidisciplinary product development cartography. These cartographies represent the concepts and techniques discussed in the literature for the development of multidisciplinary products, as well as the existing links between them, in order to identify the structures, or fragments of structures, already constituted and documented. Another major contribution of our work lies in the analysis of industrial practices through semi-structured interviews. This data collection allowed us to establish the cartographies of the concepts and techniques used by 10 companies to organize their multidisciplinary product developments. The way in which companies have evolved their practices has also been analyzed, through the adaptation or selection of new development practices.
Furthermore, the divergences and similarities between the scientific literature recommendations and the way companies actually work were highlighted. On the strength of these observations, guidelines are proposed for the elaboration of a development structure. These guidelines rely on an audit to establish a cartography of the present practices as well as on the identification of the challenges related to the development of multidisciplinary products. Finally, the elaboration of the proposed structure is based on the association between the challenges encountered and the concepts and techniques depicted in the scientific literature cartographies. These guidelines were applied at an agricultural equipment manufacturer to support its evolution towards multidisciplinary products. Our work is positioned as a cornerstone aiming to better support companies that seek to take advantage of the possibilities offered by digital and connectivity technologies through the proposition of a development structure adapted to their products’ evolution.
... Traditional software engineering processes tpyically follow a recursive topdown approach, where each recursion covers parts of software's entire lifecycle. For example, the classical waterfall model [11] goes from acqisition of highlevel user requirements, to software design, and to software implementation and testing to reach workable applications. Most other process models for software engineering, as summarized by [13], derive recursive or evolutionary procedures from the basic software lifecycle to improve the waterfall model. ...
Servitization is one of the most significant trends that reshapes the information world and society in recent years. The requirement of collecting,storing, processing, and sharing of the Big Data has led to massive software resources being developed and made accessible as web-based services to facilitate such process. These services that handle the Big Data come from various domains and heterogeneous networks, and converge into a huge complicated service network (or ecosystem), called the Big Service.The key issue facing the big data and big service ecosystem is how to optimally configure and operate the related service resources to serve the specific requirements of possible applications, i.e., how to reuse the existing service resources effectively and efficiently to develop the new applications or software services, to meet the massive individualized requirements of end-users.Based on analyzing the big service ecosystem, we present in this paper a new paradigm for software service engineering, RE2SEP (Requirement-Engineering Two-Phase of Service Engineering Paradigm), which includes three components: service-oriented requirement engineering, domain-oriented service engineering, and software service development approach. RE2SEP enables the rapid design and implementation of service solutions to match the requirement propositions of massive individualized customers in the Big Service ecosystem. A case study on people's mobility service in a smart city environment is given to demonstrate the application of RE2SEP.RE2SEP can potentially revolutionize the traditional life-cycle oriented software engineering, leading to a new approach to software service engineering.
... There are two main approaches to product development. In 1970, Dr Winston W. Royce presented a paper on "Managing the Development of Large Software Systems" in which he shared his thoughts on managing successful software projects based on his experience in aerospace systems development (Royce, 1970). Winston W. Royce presented in the article "A Summary of the Waterfall Paper" a method of dividing the software development process into two phases for small projects, analysis and coding, and seven post-phases for larger projects (Fogelstrom et al., 2010). ...
The article analyzes the comparative features of management concepts for the development of a concept. Depending on management decisions, it is proposed to consider the limitations in implementing the concepts of lean manufacturing, rapid response, flexible production, and the factory of the future.
The developed concept, within the framework of implementing development projects in key areas, allows us to coordinate the work of all departments, which helps us organize effective company activities when making management decisions during digital transformation.
... A gestão de projetos no desenvolvimento de software é uma preocupação que surgiu durante os anos da década de 1960, e que já era tratado na Administração Nacional da Aeronáutica e Espaço Americana (NASA) Basili, 2003), sugeriu o conceito de ciclo de vida de projetos, divididos em fase sequenciais, e que mais tarde ficou conhecido como métodos tradicionais ou waterfall (cascata) (Rajagopalan, 2014;Royce, 1970). Este método foi inspirado na indústria da construção civil e, por isso, a abordagem é bastante estruturada onde o custo, escopo e prazo do projeto são definidos, em sua fase inicial, e toda a mudança deve ser cuidadosamente gerenciada, pois causará impactos de custo e/ou nos prazos acordados (Nerur;Mahapatra;Mangalaraj, 2005). ...
Na área de TI das empresas, em seus processos de desenvolvimento de software, destaca-se, atualmente, a utilização das práticas voltadas para a agilidade. Os conceitos presentes nos métodos ágeis exigem mudanças culturais, que buscam responder às mudanças frequentes no mercado, bem como na velocidade e na inovação no atendimento de seus clientes. Todavia, os fatores de sucesso aplicáveis em projetos não levam à eficiência em nível de portfólio, uma vez que as mudanças estruturais são mais complexas. Como resposta, o mercado tem conhecido novos modelos ágeis que atuam no nível de portfólio de projetos que não são aderentes a todo tipo de empresa, e as adaptações realizadas para a sua utilização nem sempre são as mais adequadas. Neste contexto, este estudo tem como objetivo avaliar como as empresas de grande porte brasileiras utilizam a Gestão de Portfólio Ágil de Projetos, que estão no contexto de desenvolvimento de sistemas digitais. Para tanto, realizou-se um estudo bibliométrico, seguido de uma revisão sistemática da literatura para formulação do roteiro de entrevistas e dos temas de interesse para serem respondidas em uma pesquisa de campo, com a aplicação de estudo de caso múltiplo. Os resultados encontrados podem ser utilizados como um guia de referência de boas práticas de Gestão de Portfólio Ágil, com base nos padrões encontrados nos estudos de casos, que possa apoiar as empresas do mercado brasileiro na alavancagem e na utilização das práticas ágeis, neste nível de gestão de projetos.
... Traditionally, software companies have used the waterfall methodology for software development, established by Rovce (1987). This approach is frequently used for the development, production, or building of any tangible product, with the caveat that initially, the waterfall methodology assumed that the designer could go back to any earlier stages as needed, even though doing so might often be challenging or impractical (Guerrero-Ulloa, Rodríguez-Domínguez and Hornos, 2023). ...
The study raises concerns about how employee engagement and job satisfaction in the IT sector in Pakistan, where the use of agile project management is emerging. As such, the need to find a solution to this problem arises because its employees' engagement levels are directly related to the success of projects, productivity and organisational commitment of employees, whereas dissatisfaction at the workplace causes disengagement and low commitment among employees. This study examines how agile practices like daily stand-up, continuous feedback, and pair programming affect employee job satisfaction and work-life balance in Pakistan's IT industry. The study employed a quantitative approach, whereby data were gathered through a survey and tested using hypothesis testing, Pearson correlation, and regression analysis. The results demonstrate that agile practices improve satisfaction levels and positively impact work-life balance for IT workers. Based on these findings, practical recommendations can be derived to cement agile process adoption that is beneficial for the IT companies operating in Pakistan regarding the benefit and well-being of employees and to enhance the project results. ii
... Software development involves design of programming instructions that, when executed, provide function and performance on data structures for the purpose of adequately manipulating data. The process has, in many instances, involved documentation at each stage of creation (Royce, 1970). In pursuit of high quality and responsive software, a number of approaches have been developed over the years . ...
The recent past has witnessed an upsurge of cloud technology which has, undoubtedly become an indispensable basis for contemporary application deployments. Cloud computing is vital in providing efficiency and scalability, borne in its “as a service” types of delivery models. As application developers consider the move into this cloud environment, there is an increasingly need to understand key factors necessary for dealing with challenges related to the use of cloud technologies, to realise full potential and benefits of cloud computing. This research paper attempts to establish an adoption framework particularly focussing agile developers with a view to promoting adoption and utilisation of cloud computing. A blend of methodological approaches was employed in the study. A pilot study was initially used with 36 respondents who were involved in the field of software development successfully participating. Based on some results of this pilot study and objectives underpinning the research, an in-depth study involving a case study was conducted on a select group of individuals who are professional in the domain area, enabling a better description of processes, concepts and procedures in context. Guided by Technology, organisation, and environment (TOE) framework themes, and interactions between and amongst each other, five propositions were structured around the problem to create new thinking on promoting cloud computing adoption and its utilisation by agile developers. It was found that Small, Medium and Micro Enterprises (SMMEs) using agile development methodologies can benefit from using the proposed framework when choosing to move into utilisation of cloud computing resources.
... Penelitian ini menggunakan metodologi pengembangan air terjun, disebut air terjun (waterfall) karena dilakukan berurutan fase demi fase yang dilalui harus menunggu fase sebelumnya selesai lalu lanjut ke fase selanjutnya [3]. Tahapan pengembangan perangkat lunak dengan waterfall meliputi: system requirements, software requirements, analysis, program design, coding, testing, dan operations [15]. Tahapan-tahapan waterfall yang ditunjukkan pada Gambar 2. ...
PT KSJM merupakan suatu bentuk lembaga yang bergerak di bidang jasa pengangkutan umum yang menggunakan transportasi laut, yaitu kapal yang di dalamnya terdapat kegiatan untuk memberikan jasa. Penelitian ini dilakukan untuk memberikan solusi terhadap permasalahan yang terjadi dalam proses bisnis yang dimiliki oleh PT KSJM. Tujuan penelitian adalah untuk menghasilkan aplikasi pengelolaan dokumen yang dapat mengintegrasikan proses yang ada di PT KSJM dengan data yang terkait. Pengintegrasian tersebut dilakukan untuk meningkatkan efisiensi dalam hal sumber daya yang digunakan oleh pihak perusahaan serta menyediakan media penyimpanan data yang terstruktur. Hasil dari penelitian ini adalah aplikasi pengelolaan dokumen yang dibuat memiliki modul yang dapat menyimpan unggahan DO, pengentrian data barang yang akan dimuat, pencatatan dan pencetakan faktur, serta memiliki modul yang dapat memberikan informasi untuk PT KSJM seperti daftar data klien dan data kapal.
... In software development, teams work together to create a working product by implementing a set of practices or a framework to ensure that the process is manageable and organized. The oldest methodology to develop software is the Waterfall Model, first documented by [1] and is modified by [2]. With this model, the software is developed straightforwardly in its life cycle, consisting of a few stages: planning, analysis, design, development, testing, implementation, and maintenance. ...
The iteration process in Personal Extreme Programming (PXP) consists of Initialization, Design, Implementation, Testing, and Retrospective. There are still areas for improvement in this method. In the future, this method will be a problem because it can make the application unable to run after the retrospective process. One of the problems is the version update app on Android. We propose an Advanced PXP model (APXP) for an academic information system (SIAKAD) in Balikpapan Schools that contains PXP modifications at the beginning and end of the process. At the middle stage of APXP is system testing. Each process from 1-11 iterations produces Valid results. We add Deployment methods such as Blue-Green Deployment Strategy. The deployment process can change very quickly once the switch service changes in the APXP method. Furthermore, the deployment process has almost no issues with different versions of the service
... What I have covered in this article is not all new, similar messages has been communicated in numerous articles, blog posts and books over the years. In his famous article from 1970 [14], Winston Royce already stated that the linear development method, later labeled as the waterfall method, won't work for any larger-scale information system project. But somehow and for some reason, we have been a bit deaf to all the valuable advice around us. ...
Failed software projects, delayed deliveries and unsatisfied users are topics that we read on almost daily basis on the media. We’re so used to unsuccessful software projects that we do not even seem to expect projects to provide real value to the users. Simultaneously, the societies are more dependent on the software than ever and huge amount of people make their living out of software engineering related jobs. We are investing substantially in the education and training in the software domain and emphasize modern technologies and practices in the education. A consensus exists within the academia and industry on how to effectively develop information systems: with iterative and user-centered methodologies that focus on continuous improvement, i.e. agile methods. Somehow, still, these great ideas and principles do not materialize in practice in software projects; we seem to encounter failing projects and unhappy clients more than succeeding projects with happy end-users. My claim is that we are not doing the best we can, and we know better what we should do when creating and maintaining software intensive systems. The structures that inhibit us from providing the best value possible for the user are often related to bad communication and/or non-disciplined ways of working. Many of the obstacles can be avoided through servitization: better collaboration, more user-centered development methods and iterative approaches.KeywordsSoftware development methodsAgile developmentCo-operation and collaborationServitization
... Макар Бенингтън да не споменава термина "водопаден", моделът придобива това прозвище сред разработчиците на софтуер през годините, тъй като подобно на водопад артефактите преминават от текуща към следваща фаза. Моделът по-късно е модифициран от Ройс [81] през 1970 г., който дава възможност за връщане една фаза назад. Например ако има проблем при валидацията, целият продукт се връща във фаза на разработка и ако е нужна промяна в дизайна, целият продукт се връща още една фаза назад -във фазата на дизайн и т. н. ...
Дисертацията е насочена към изследване и анализ на модели за автоматизирано тестване, с които да се определи кога въобще автоматизацията е подходящо решение, тестването на кои функционалности си струва да бъде автоматизирано, в каква последователност и с какъв инструмент, за да се улеснят специалистите по осигуряване на качеството на софтуера (ОКС) и да подобрят ефективността на процеса на тестване. Първата глава на дисертацията съдържа преглед на съвременното състояние на ИТ сектора в България, като се разглежда профилът на типичния специалист по осигуряване на качеството на софтуера, правят се първоначални изводи и базирано на тях се поставят цел и задачи. Втората глава на дисертацията разглежда дефиниции на основни понятия, широко използвани в процеса на разработката, тестването и осигуряването на качеството на софтуера, като е обърнато специално внимание на видовете тестване на софтуер. В трета глава е разгледана възвръщаемостта на инвестицията от автоматизирано тестване на софтуер и са сравнени два подхода за приоритизиране на автоматизацията на тестовите случаи. Демонстриран е и метод за използване на функционални тестове за нефункционални цели. Представена е и методология за анализ и оценка на инструменти за
автоматизирано тестване на софтуер по зададени критерии с цел най-подходящ подбор. Четвърта глава представя обобщен инструментариум за прилагане на описаните модели на практика. Дисертацията завършва с кратко заключение.
... • The waterfall model (Royce, 1970): comprises of six stages (requirement gathering, analysis, design, testing, implementation, and maintenance) that have specific goals at each stage of software development. ...
This chapter presents key considerations on developing information systems (IS) for the contemporary accounting profession. The profession has evolved over the past number of decades and has brought about growing demands due to advances in technology and availability of big data. This chapter outlines the growing capabilities of IS and the growing expectations this sets across industry. The chapter also describes the use of accounting information systems (AIS) and how systems development and methods play a key role to inform their design and development. The chapter explores the impact of systems development within the accounting profession and the growing demands for accountants with skills in data analytics. The chapter concludes with some key challenges and recommendations to consider for AIS and data analytics implementation and development on the accounting profession.
... Pada penelitian ini model waterfall digunakan sebagai model pengembangan perangkat lunak . Model waterfall mempunyai lima tahapan yang dikembangkan oleh Winston Royce dan merupakan model pengembangan klasik dengan sistem pengembangan linier [9]. Tahapan dalam model ini meliputi analysis requirements, system design, coding, system testing, implementation and maintenance [10], [11]. ...
... Model yang digunakan pada metodologi SDLC ini adalah model sekuensial linier. Model sekuensial linier SDLC merupakan suatu proses pengembangan perangkat lunak yang berurutan dimana jika mengalir semakin kebawah atau semakin kedepan maka dianggap sebagai sebuah kemajuan proses pengembangan melalui beberapa tahapan yang harus dijalankan untuk berhasil membangun sebuah perangkat lunak komputer [28]. lalu menurut Youssef Bassil [29], Model sekuensial linier mendefinisikan beberapa urutan fase yang harus diselesaikan satu demi satu dan pindah ke fase berikutnya hanya jika fase sebelumnya selesai sepenuhnya. ...
A banking company has a goal to improve the economy and people's welfare. In addition, banking companies such as PT. BPR Suadana must also improve employee performance and welfare. One way is to increase performance in the form of salary. Payroll system at PT. BPR Suadana currently looks still manual. Where in the salary input is still recorded manually. This makes time inefficient and increases the risk of errors in the payroll process. This study aims to build an information system used in the payroll system at PT. BPR Suadana. The method used in the construction of this payroll system is the Linear Sequential Model SDLC method. The results of this research are in the form of a web-based payroll system that can be accessed and used by related divisions, namely HRD, Funds Section, and also the Director. the results of the TAM test that has been carried out by the author, it can be seen that the percentage results of 88% of users or respondents stated strongly agree and 8% agreed, that the payroll system at PT. BPR Suadana that has been made by the author is easy to use and very useful in overcoming payroll problems at PT. BPR Suadana.
... The SCM process, with its initial basis in hardware development and version control management, was first applied to software development environments in the 1950s. In those days, software changes followed simple sequential software development approaches such as Waterfall etc. mostly in standalone software development environments (Royce 1970;Sommerville 2010). ...
Software configuration management is a software engineering process that facilitates the
governance of software development activities and provides traceability of changes.
Traceability and governance are important quality attributes for all types of software
development environments. At present no comprehensive traceability model exists that
can facilitate organisations by tracing both product and process knowledge during their
software development operations.
This study examines the software configuration management process in large, medium
and small organisations, where agile and traditional software development methods
coexist under the guidelines for software process improvement standards with different
types of computing environments. For this research, I examine the impact of the Tetrad
of Contextual (ToC) constraints drawn from the traceability framework for the
implementation of a software configuration management process. The ToC constraints
include the following influencing factors impacting the implementation of software
configuration management process: 1) Software development methodologies, 2)
Different types of computing environments, 3) Diverse software process improvement
standards, and 4) organisation size.
The aim of this research is to extend the existing traceability meta-model to incorporate
a management systems’ view. This extended traceability meta-model provides a
comprehensive traceability view covering both product and process knowledge
perspectives. In addition, I also propose and test a reference traceability model called
SALAM (Software configuration Agile Lean Adaptable Management; in Arabic it also
means ‘peace‘) which can facilitate the practitioner in implementing a software
configuration management process under constraints.
Due the exploratory nature of the research investigating the software configuration
management process implementations under the influence of different types of software
development methodologies, computing environments, process improvement standards
and organization sizes, an exploratory iterative sequential mixed design approach is
chosen and divided into three research phases. I identify a case study, extend the
traceability meta-model to add the management system view, develop a reference
iv
traceability model, and then perform quantitative validation of the reference traceability
model.
Both the extended holistic traceability meta-model and the associated reference
traceability model SALAM are validated. It is identified that all sizes of organisations
consider management systems very important for establishing traceability. Although
their traceability solutions varied in terms of the granularity of the software
configuration management process and the sophistication of the tools used, they all
show evidence for taking a value-based approach using lean thinking principles and
practices.
... The Waterfall Model is an early concept adapted from the construction and manufacturing industries for use in software development. The first formal use of the term 'waterfall' has subsequently been attributed to an article written in 1970 by Winston Royce [33]. Although there are multiple iterations of the number of tiers and what each tier is called, for purposes of this paper we have identified five steps including 1) planning, 2) system analysis, 3) design, 4) system development and 5) system maintenance [12]. ...
The study applied concepts of computational thinking, waterfall programming, and design-based learning management (DBLM) combined with a participatory action research (PAR) methodology to obtain an integrated learning management model (LMM) designed as a base to promote computational thinking skills (CTS) and programming proficiency. The study used three groups consisting of 21 volunteer computer science undergraduate students, three teachers, and three computer studies graduates from the Computer Studies Department of the Faculty of Education at Thonburi Rajabhat University in Thailand. To verify the model, nine educational experts conducted an assessment of the proposed model, and determined that the evaluation standards were overall at a high level (x ̅ = 4.23, SD = 0.44), with the experts feeling that the integration of the DBLM computational thinking framework, the Waterfall programming conceptual framework, and the PAR met the study's stated objectives at the highest level (x ̅ = 4.56, SD = 0.53). The proposed model is best undertaken in five week sessions of five hours each using five exercises per week. In doing each activity, the effectiveness of each activity is to be measured by taking notes, worksheets, and practice skills. The resultant outcome was that the groups jointly participated in finding a model which offered CTS and programming skill training which encouraged the participants to learn together to develop activities based on common needs.
... Al respecto, métodos tradicionales como la cascada descrito por Winston W. Royce trae una propuesta lineal y secuencial en donde cada etapa debe empezar hasta que la actual termine. Dicho método se adapta muy bien en proyectos pequeños, con tiempos de entrega cortos y requerimientos estáticos [8], sin embargo, en el mundo acelerado y complejo en que las compañías se desarrollan, surgen necesidades que deben ser solventadas con métodos novedosos, ágiles, sencillos de implementar y sobre todo cuyos resultados sean positivos. En el siguiente marco teórico se revisarán los conceptos relacionados con metodología ágil, Scrum y Jira. ...
... From the very beginning, the different approaches used to organize software development have been critically discussed. These discussions have begun with Royce [10] stating that strict sequential models do not 3 properly reflect the needs of software development. In response, shorter iterations and incremental approaches became popular, such as Boehm's Spiral model [11] representing an iterative, risk-driven process, and Mills [12] and Dyer [13] suggesting incremental development processes in the 1970s and 1980s. ...
Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.
... From the very beginning, the different approaches used to organize software development have been critically discussed. These discussions have begun with Royce [10] stating that strict sequential models do not 3 properly reflect the needs of software development. In response, shorter iterations and incremental approaches became popular, such as Boehm's Spiral model [11] representing an iterative, risk-driven process, and Mills [12] and Dyer [13] suggesting incremental development processes in the 1970s and 1980s. ...
Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.
software, which plays a key role in any kind of business. Irrespective of nature and size, every employer is showing interest in implementing suitable software to reduce the work burden and to make easy business transactions. There are so many companies that are working in developing software across the globe. Indian software companies have their own mark in producing capable employees. All companies always prefer skilled people to ensure its sustainability in this present competitive world. Now-a-days software industry is started focusing on the capabilities of an employee because of increased competition, new project scarcity and the availability of too many candidates. It is trying to filter the fake experience holders with the maximum possible ways. Employers are assigning project manager or team lead responsibilities to the person who has proven his capabilities, irrespective of his no of years of service. Clients are the customers to the software industry, if the employee is able to satisfy the client then only it is possible to get the project work from the client. Employees who are lack of capabilities are failing to configure the software as per the client's need, which is causing to loss the business opportunities for the employer.
Die digitale Transformation in Deutschland kommt nicht wie gewünscht voran. Und das trotz des Onlinezugangsgesetzes, das der Verwaltung eine Herkulesaufgabe abverlangt: alle Bürger:innenservices in digitaler Form bis Ende 2022 zur Verfügung zu stellen. Neben der grundsätzlichen Verfügbarkeit digitaler Services erwarten die Menschen vom Staat aber auch digitale Dienste, die sich nach ihren Bedürfnissen richten und die an ihre Erfahrungen mit privatwirtschaftlichen Produkten mindestens heranreichen.
Doch die gegenwärtige Praxis der öffentlichen Vergabe und Besonderheiten der Verwaltung erzeugen Anreize, die Entwicklung von digitalen Bürger:innenservices nach Methoden abzuwickeln, die häufig zu Budget- und Zeitüberschreitungen führen und die außerdem als schlecht dafür geeignet gelten, ihre Aufgabe zu erfüllen: Services zu entwickeln, die auf die Bedürfnisse ihrer Nutzer:innen eingehen, um adäquate, zeitgemäße digitale Lösungen bereitzustellen. Um dahin zu gelangen, gelten agile, nutzer:innenzentrierte Arbeitsmethoden als State-of-the-Art, doch ist ihre Anwendung in der öffentlichen Verwaltung nicht alltäglich.
Diese Arbeit widmet sich der Frage, wo Hürden auf dem Weg zu agil und nutzer:innenzentriert entwickelten Bürger:innenservices liegen, die mittels öffentlicher Projektvergabe realisiert werden. Außerdem stellt sie die Frage, welche Lösungsansätze es ermöglichen könnten, das System im Sinne dieser Methoden anzupassen.
Dazu wurde eine Reihe qualitativer Expert:inneninterviews mit Personen aus verschiedenen Wissensfeldern der öffentlichen Vergabe durchgeführt. Diese bringen Wissen und praktische Erfahrung mit, um über Herausforderungen und Möglichkeiten zu berichten, die sich bei der öffentlichen Projektvergabe von agil und nutzer:innenzentriert entwickelten digitalen Services der Verwaltung ergeben.
Als Ergebnis liefert diese Arbeit eine Diskussionsgrundlage, indem sie Hürden identifiziert, diese bewertet und praktische Lösungsansätze entwirft, die Handlungsmöglichkeiten für politische Akteure aufzeigen.
The methods and techniques of software development are important for several reasons:
1. Efficient development: Software development methods and techniques help developers work efficiently and effectively, ensuring that they deliver high-quality software within the required timeline. These methods and techniques help organize the development process and ensure that all tasks are completed on time.
2. Quality assurance: Software development methods and techniques ensure that software is developed according to established industry standards and best practices. This helps to minimize errors, bugs, and security vulnerabilities in the software, ensuring that it is of high quality and meets the needs of the end-users.
3. Collaboration: Software development methods and techniques provide a framework for collaboration between developers, testers, project managers, and other stakeholders involved in the development process. This improves communication, enhances teamwork, and helps to avoid conflicts and misunderstandings.
4. Flexibility: Software development methods and techniques allow developers to adapt to changing requirements and business needs, ensuring that the software can evolve and grow over time. This allows software to be updated and improved over time, ensuring that it remains relevant and useful to users.
5. Cost-effective: Software development methods and techniques help to minimize development costs by improving efficiency and reducing the likelihood of errors and rework. This allows businesses to develop high-quality software that meets their needs without overspending on development costs.
The methods and techniques of software development are crucial for ensuring that software is developed efficiently, effectively, and to a high standard. They help to minimize errors, enhance collaboration, and ensure that software meets the needs of users and businesses alike.
Purpose: The aim of this study is to identify the issues and problems in the current Libyan voting system, and to develop a secure e-voting prototype system associated with the Libyan electoral system and the laws and legislation governing. Theoretical framework: E-voting systems allow greater participation of eligible voters to cast their vote remotely or any location that the voter could be during election. Design/methodology/approach: This study used mixed methodology. A qualitative method via interview would be used to collect qualitative data from citizens and election staff to determine functionalities and features of the proposed system. Using Semi-structured interviews with ten eligible voters, election officials. While a quantitative study conducted to evaluate users and elections of officials to determine how the systems fulfils the requirements and their expectations, to determine if the prototype proposed system offers practical solution to the Libyan voters and if the functionalities of the system fulfil the requirement gathered at the problem definition stage. The second prototype was regarded as meeting the key functional and non-functional requirement and ease of use criteria by users. After fixing the concerns found during the first prototype's evaluation in terms of the requirement criteria. The criterion for ease of use were met. Findings: As a result, 87% of the evaluators indicated that they would adopt the system if it was introduced. Whereas 87% of the evaluators suggested that they would recommend the E-Voting system to their friends, colleagues, and Libyan Election Council. Research, Practical & Social implications: Following the trial of the second prototype, the evaluators proposed that the Libyan E-Voting System (L-EVS) would assist them enable them to exercise their election rights. Originality/value: Concerns and issues from previous political elections have spawned over numerous studies regarding voter confidentiality, voting security, and voting accuracy.
Zusammenfassung
Die Erfahrungen der letzten Jahre zeigen, dass Unternehmen häufig den Wert ihrer eigenen Daten sowie die eigenen Fähigkeiten, Umsatz aus diesen Daten generieren zu können, systematisch überschätzen. In der Praxis sind die wenigsten Unternehmen tatsächlich in der Lage ein nachhaltiges auf Daten basiertes Geschäftsmodell zu etablieren. Dies hat vielfältige Gründe: eine zu geringe Menge verfügbarer Daten, fehlende Einheitlichkeit und Vergleichbarkeit der Daten, mangelnde Möglichkeiten, diese Daten zur Erzeugung von relevanten Informationen oder Handlungshinweisen interpretieren zu können, sowie die fehlende Monetarisierung der Resultate.
Für ein besseres Verständnis, welche grundsätzlichen Aspekte es bei der Entwicklung datenbasierter Geschäftsmodelle zu beachten gilt und wie eine mögliche Umsetzung aussehen kann, beschreibt dieser Beitrag die Besonderheiten sowie die unterschiedlichen Arten datengetriebener Geschäftsmodelle und für welche Unternehmen diese besonders geeignet sind, weist auf spezifische Chancen und Herausforderungen hin und stellt die systematische Entwicklung datenbasierter Geschäftsmodelle dar.
Zusammenfassung
Daten bergen ein hohes Wertschöpfungspotenzial. Zur Umsetzung von innovative Geschäftsmodellen wird immer häufiger auch auf Daten von natürlichen Personen zurückgegriffen. Dabei stellt sich die Frage, inwieweit die betroffenen Personen Einfluss und Kontrolle auf die Verarbeitung der sie betreffenden Daten nehmen können. Der Beitrag widmet sich dem Thema Datenhoheit aus Sicht von Nutzenden, Verbraucherinnen und Verbrauchern sowie Patientinnen und Patienten. In diesem Zusammenhang werden die rechtlichen Rahmenbedingungen und bereichsspezifische Regelungen zur Gewährleistung der Datenhoheit dargestellt.
Zusammenfassung
In zunehmend vernetzten Systemen erstreckt sich die gesamte Datenwertschöpfungskette über eine Vielzahl an Systemen, wobei unterschiedliche Akteure mit unterschiedlichen und möglicherweise gegensätzlichen Interessen beteiligt sind. Es ist daher erforderlich, die Prozesse der Datenerfassung, Verarbeitung und Speicherung so abzusichern, dass Manipulationen durch externe Angriffe oder einzelne Akteure erkannt werden können. Dieser Beitrag legt den Fokus auf drei unterschiedliche technische Maßnahmen, durch welche Vertrauen in die ausgetauschten Daten selbst und letztendlich auch zwischen unterschiedlichen Akteuren hergestellt werden kann: Maßnahmen zur Kommunikationssicherheit schützen Daten während des Transports, digitale Kalibrierzertifikate erlauben eine Aussage über die Genauigkeit der erfassten Daten, Distributed-Ledger-Technologien wie zum Beispiel eine Blockchain erfassen Aktionen sowie beteiligte Akteure und legen diese Informationen manipulationsgeschützt ab. Dieser Beitrag bezieht sich auf das Forschungsprojekt GEMIMEG-II , das durch das Bundesministerium für Wirtschaft und Klimaschutz (BMWK) gefördert wird.
Zusammenfassung
Es kann künftig möglich sein, im Internet der Dinge (engl. Internet of Things, kurz IoT) Daten und Resilienz-Services ebenso souverän wie selbstsicher zu handhaben und auszutauschen. Ähnlich wie dies heutzutage mit physischen Ressourcen möglich ist. Um diese Vision zu realisieren, entwickeln Forschende im Projekt SPAICER einen GAIA-X konformen IoT-Datenraum, der Datenproduzierende, Datenkonsumierende und Datenverarbeitende an einem digitalen Ort vereint und eine medienbruchfreie Datenökonomie ermöglicht. Mit Hilfe dieser medienbruchfreien Datenökonomie lassen sich wichtige Antworten auf relevante Fragen, wie zum Beispiel nach industrieller Nachhaltigkeit und resilienter Produktion, auf Knopfdruck ermitteln. Dabei ist der Vorteil eines IoT-Datenraums, dass skalierbare und grenzkostenfreie digitale Vermögenswerte entwickelt werden können, die Datenproduzierende von produktbezogenen zu nutzungsbezogenen Technologieführern wandeln. Hierdurch werden IoT-Daten zu Wirtschaftsgütern und IoT-Services zu digitalen Geschäftsmodellen.
Zusammenfassung
Smart Contracts als algorithmen-basierte Routinen eignen sich zur automatisierten Vertragsabwicklung. Hierzu ist es notwendig, dass sich die Vertragsgestaltung der besonderen Anforderungen bewusst wird, die ein Programmcode, der lediglich einfache Wenn-dann-Beziehungen abbilden kann, an sie stellt. Ein automatisches Ablaufen eines Smart Contracts kann nur dann zur Vertragserfüllung eingesetzt werden, wenn die komplexen juristischen Vereinbarungen zwischen den Parteien derart dekonstruiert werden, dass seine automatische Ausführung möglich ist. Für den Bauvertrag wurde die Zahlungsabwicklung als ein Komplex identifiziert, der es mittels Bautenstandsfeststellungen mithilfe der Methode BIM erlaubt, eine (teil-)automatisierte Vertragsabwicklung durchzuführen. Der Beitrag möchte das Bewusstsein für das Potenzial einer solchen Teilautomatisierung, aber auch für deren Grenzen schärfen. Die Vertragsgestaltung muss ermitteln, an welchen Stellen trotz Teilautomatisierung menschlicher Input notwendig bleibt. Darüber hinaus gilt es die zwingenden Regelungen des Datenschutzes zu beachten. Im Rahmen eines Ausblicks wird untersucht, inwiefern sich die für den Bauvertrag gefundenen Ergebnisse auf die Abwicklung anderer Vertragstypen übertragen lassen.
Zusammenfassung
Die Frage nach der Kontrolle über Daten spiegelt sich in populären, aber wenig konkreten Begriffen wie „Datenhoheit“ oder „Datensouveränität“ wieder. In dieser Einleitung zum dritten Teil des Buches werden kurz die Themenfelder und Zielstellungen der folgenden drei Beiträge eingeführt, die sich u. a. mit der Datenhoheit aus Perspektive der Nutzenden, einer Einführung in Verfahren zur Anonymisierung und Pseudonymisierung sowie dem Konzept der sogenannten Datennutzungskontrolle befassen. Damit werden rechtliche, organisatorische und technische Bausteine für die Umsetzung von Datensouveränität beschrieben, die Datenschutz, Informationssicherheit und Vertraulichkeit in datenzentrierten Wertschöpfungsnetzen ermöglichen.
Zusammenfassung
Die Qualität von Daten sowie die darauf angewandten Transformationen und Berechnungen sind maßgebend für die Qualität der Entscheidungen, die auf ihrer Basis getroffen werden. Auf Seiten potenzieller Nutzender gibt es derzeit immer noch kein ausreichendes Vertrauen in datenbasierte Lösungen. Dies gilt besonders für sicherheitskritische Anwendungen oder Anwendungen im Gesundheitsbereich. In diesem Buchteil werden ausgewählte Lösungsansätze vorgestellt, um die Qualität datenbasierter Dienste und Produkte sicherzustellen beziehungsweise nachzuweisen und so das Vertrauen in diese Angebote zu stärken.
Zusammenfassung
Digitale Ökosysteme entstehen in allen Branchen und Domänen, leben von einer starken Vernetzung und ermöglichen neue, datenzentrierte Geschäftsmodelle. Die Umsetzung von Datensouveränität – also die größtmögliche Kontrolle, Einfluss- und Einsichtnahme auf die Nutzung der Daten durch den Datengebenden – ist essenziell, um eine vertrauensvolle und sichere Nutzung von Daten zwischen allen Beteiligten des digitalen Ökosystems zu ermöglichen. Datennutzungskontrolle ist hierfür ein wesentlicher Baustein, um eine organisations- und unternehmensübergreifende Selbstbestimmung und Transparenz bei der Verwendung von Daten durch Ökosystemteilnehmer zu gewährleisten. Das Kapitel befasst sich mit den Grundlagen der Umsetzung von Datensouveränität durch Datennutzungskontrolle und der Verwendung von Datendashboards für Datensouveränität in digitalen Ökosystemen. Hierzu wird ein Anwendungsbeispiel eines digitalen Ökosystems aus der Automobilbranche eingeführt und die Umsetzung von Datensouveränität anhand konkreter Szenarien verdeutlicht und diskutiert.
Zusammenfassung
Der technologische Fortschritt im Bereich digitaler Technologien und die zunehmende Verfügbarkeit unterschiedlichster (produktionsrelevanter) Daten bieten Unternehmen die Möglichkeit, sich mit neuen Geschäftsmodellen vom Wettbewerb zu differenzieren und neue Wertschöpfungspotenziale zu heben. Dabei sehen sich Unternehmen aber auch vor nicht zu unterschätzenden Herausforderungen. In dieser Einleitung werden die relevanten Themenstellungen aufgegriffen und auf die entsprechenden Beiträge in diesem Buch verwiesen. Zu den angesprochenen Themen gehört unter anderem die Überführung produktzentrierter in nutzungsbezogene Geschäftsmodelle. Hinzu kommt das Verständnis der Besonderheiten sowie die daran ausgerichtete annahmebasierte Entwicklung datenbasierter Geschäftsmodelle. Darüber hinaus wird die Preisbestimmung für Daten beziehungsweise datenbasierte Produkte und Dienstleistungen betrachtet. Abschließend richtet sich der Fokus auf die Bewertung von Datenbeständen und wie diese in die Bilanz und Bewertung eines Unternehmens einbezogen werden können.
Zusammenfassung
Dieser Beitrag stellt dar, welche Chancen und Herausforderungen mit der Bewertung von Daten sowie der Abbildung monetärer Datenwerte verbunden sind und geht auf mögliche Lösungsansätze zur Bewertung von Unternehmensdatenbeständen, insbesondere im Kontext der industriellen Produktion, ein. Zunächst werden Grundlagen zur Charakterisierung, Nutzung und Verwertung von Daten sowie bestehende Methoden zur Bewertung von immateriellen Vermögensgegenständen dargestellt. Darauf aufbauend werden Chancen und Herausforderungen spezifiziert, potenzielle Lösungsansätze zur Datenbewertung abgeleitet und anschließend Anforderungen für die Datenbewertung beschrieben sowie die nutzenorientierte Datenbewertung skizziert.
Zusammenfassung
Digitale Ökosysteme leben vom Austausch und der übergreifenden Nutzung von Daten. Dem wirtschaftlichen Nutzen von digitalen Innovationen stehen häufig Sorgen vor Kontrollverlust und missbräuchlicher Verwendung von Daten gegenüber. Abhilfe schaffen technische Lösungsansätze, die den souveränen Umgang mit Daten sicherstellen und Vertrauen zwischen den Akteuren schaffen sollen. Im engen Zusammenhang hierzu steht die Frage, wem Daten rechtlich zuzuordnen sind und wer sie nutzen darf. Die bestehende Rechtsordnung gibt hierauf nur punktuell Antworten. Die Überlassung von Daten erfolgt derzeit vor allem auf Grundlage von Verträgen. Dabei gilt weitgehend das Prinzip der Vertragsfreiheit. Dies ermöglicht eine interessengerechte Ausgestaltung der Vertragsbeziehung, stellt die Vertragsparteien aber gleichzeitig vor Herausforderungen. Die lückenlose und zugleich rechtssichere Gestaltung von Datenverträgen erweist sich mitunter als schwierig. Der folgende Beitrag befasst sich mit Herausforderungen und Grenzen bei der Gestaltung von Datenverträgen.
Zusammenfassung
Die Europäische Union strebt mit einem Bündel von Verordnungsentwürfen die Ausgestaltung des Rechtsrahmens für Datenräume an. Mit dem Vorschlag eines Data-Governance-Gesetzes soll die Grundlage für einen zukünftigen Rechtsrahmen der Datennutzung und der Datenmärkte gelegt werden. Neben dem Datentransfer aus dem öffentlichen in den privaten Sektor und der Datenspende wird das Anbieten von Diensten für die gemeinsame Datennutzung (Datenmittlung) geregelt. Das Teilen von Daten soll rechtskonform gestaltet werden können, um die Entstehung von Datenräumen auch wirtschaftlich zu ermöglichen.
Anbietern von Diensten für das Teilen von Daten, sogenannten Datenmittlern, wird eine Schlüsselrolle in der Datenwirtschaft zugeschrieben. Sie schaffen Plattformen, die das Aggregieren und den Austausch erheblicher Mengen einschlägiger Daten erleichtern, und verbinden die verschiedenen Akteure miteinander. Sie unterstützen sowohl das Teilen von Daten mehrseitiger Herkunft für mehrseitige Nutzung als auch den bilateralen Datenaustausch von Unternehmen zu Unternehmen. So kann zukünftig eine „neuartige europäische Art der Data Governance“ für datengetriebene offene Ökosysteme auf der Basis neutraler Datenmittler entstehen.
Unternehmen, die Datenbestände als Anbieter oder Nutzer innovativ einsetzen wollen, benötigen Modelle zur Datennutzung und eine Data Governance, die die künftigen gesetzlichen Vorgaben umsetzt und hierbei Technik, Ökonomie und Recht verbindet. Data Governance ist das Zukunftsmodell für alle datengetriebenen Innovationen, um die Teilhabe an Daten und datenbasierten Innovationen auch für KMU niederschwellig und rechtskonform zu ermöglichen und Markteinschränkungen aufgrund von Datenabhängigkeiten zu vermeiden. In diesem Beitrag wird für Entscheidungsträger in Unternehmen der aktuelle Rechtsrahmen erläutert und im Kontext von zukünftigen Ökosystemen bewertet.
Zusammenfassung
Derzeit wachsen im Zuge der Digitalisierung und durch das Aufkommen neuer Informations- und Kommunikationstechnologien die Datenbestände weltweit exponentiell an. Diese Daten erlangen eine immer wichtigere Rolle als Wirtschaftsgut. Als Grundlage neuer Dienstleistungen und Produkte stellen sie die zentrale Ressource der Datenwirtschaft dar. Jedoch wird das in ihnen liegende Wertschöpfungspotenzial momentan nicht vollständig gehoben. Grund hierfür sind Herausforderungen bei der Entwicklung und Vermarktung. Sie stellen ein Hemmnis für Unternehmen dar, um datenbasierte Wertschöpfungsmodelle umzusetzen und somit aktiv an der Datenwirtschaft teilzunehmen. Der vorliegende Sammelband greift solche Herausforderungen entlang der vier Felder Ökonomie, Recht, Informationssicherheit sowie Akzeptanz auf, analysiert sie und bietet praxiserprobte Lösungsansätze an. Dabei wird der Fokus auf besonders grundlegende Aspekte der Datenwirtschaft wie die Datenhaltung, das Datenteilen und die Datenverarbeitung gerichtet. Er adressiert Leserinnen und Leser aus Wirtschaft und Wissenschaft und soll dabei helfen Datenwertschöpfungsprojekte in Unternehmen und Forschung erfolgreich umzusetzen.
Zusammenfassung
Dieses Kapitel gibt einen Überblick über aktuelle Techniken für die Anonymisierung und Pseudonymisierung von Daten. Nach einer kurzen Einführung in die Thematik sowie der Klärung wesentlicher Begriffe aus rechtlicher und organisatorischer Sicht werden Methoden für die Anonymisierung strukturierter Daten erläutert. Hierbei wird der Schwerpunkt auf aggregationsbasierte Anonymisierung gelegt. Differential Privacy wird als moderne Methodik zur Bewertung rauschbasierter Anonymisierungsverfahren diskutiert und anhand eines Praxisbeispiels erläutert. Es werden Methoden für das Testen von differenziell privaten Anonymisierungsverfahren und Praxisbeispiele vorgestellt, in denen Differential Privacy von Organisationen erfolgreich eingesetzt wird. Anschließend werden Pseudonymisierungsverfahren erläutert. Hierbei werden insbesondere moderne, kryptographische Verfahren betrachtet sowie die struktur- und formaterhaltende Pseudonymisierung von Daten. Die vorgestellten Verfahren werden wiederum anhand von Praxisbeispielen erläutert.
Zusammenfassung
Daten sind Grundlage für neue Produkte und Dienstleistungen und zugleich Voraussetzung für die Entwicklung selbstlernender Systeme und künstlicher Intelligenz. Sie stehen im Mittelpunkt des digitalen Transformationsprozesses und der Datenwirtschaft. Die nutzerübergreifende Verwendung von Daten ist aber auch mit Risiken verbunden, insbesondere wenn sensible Informationen über Unternehmensgrenzen hinaus ausgetauscht werden. Neben vertrauenswürdigen Infrastrukturen bedarf es auch einer rechtlichen Absicherung von Datenaustausch und –handel, um rechtssicher zu agieren und die Werthaltigkeit von Daten zu bewahren. In diesem Buchteil werden Diskussionsergebnisse zu Konzepten und Ansätzen, wie ein rechtssicheres Umfeld in datenbasierten Wertschöpfungsnetzen geschaffen werden kann, dargestellt. Dabei werden regulatorische Herausforderungen identifiziert sowie Lösungsansätze erarbeitet und hier für die Lesenden praxisnah aufbereitet.
The aim of every business organization is to survive amid the competition and the turbulent nature of business environment. The purpose of this study was to examine the relationship between information system development approaches and organizational competitive advantage of business organizations in Port Harcourt, Rivers State, Nigeria. The study adopted the explanatory and quantitative method, hence correlational research design is employed to investigate the correlation between the study variables with target population of 45 respondents as the study population. Krejcie and Morgan determination table was used to derived the study sample size of (40) participants. The closed ended structured 4 points Likert scale Questionnaire was constructed for use in data gathering. Collected data were coded into a format and analysed with the aid of Pearson Product Moment Correlation Coefficient Statistics and presented using Statistical Package for Social Sciences (SPSS) software package for ease of interpretations. The findings showed low and moderate significant relationship between the first dimension of information system development approaches -Waterfall approach and the two measures of organizational competitive advantage – customers’ requirement and business performance. The second dimension of information system development approaches – Agile Management Approach significantly correlates with the two measures of organizational competitive advantage – customers’ requirements and business performance. Therefore, we recommended that, when developing information system for business organizations, the aims and objectives should determine the recommended approach to be used by system developers. Keywords: Information System Development Approaches, Waterfall Approach, Agile Management Approach, Organizational Competitive Advantage
During the product lifecycle, a change in the requirements may involve expensive consequences on the system development. Nevertheless, having a decent understanding of the system and documenting the correct requirements from different perspectives help to minimize the changes caused by missing functionalities, therefore, reduce the development cost.Developing comprehensive understanding of the system in the concept phase promotes the completeness and reduces the requirements’ changes. That helps also to create a good model of the system and develop simulation and test cases, which reveal the bugs and the design issues early. This work focus on thinking strategy to answer the research questions, “How to analyze the Automated Driving System (ADS) to improve the requirements’ completeness”.ADS is a complex system that works in non-deterministic environment, in addition, it is a safety related system, meaning that, any malfunction during the operation can cause a harm to people or properties.Three systematic methods were investigated. First, identify the gaps of the stakeholders. It uses product life cycle to identify a list of internal and external stakeholders and then identify their expected needs. The second systematic process utilizes holistic thinking perspectives method to build a broad understanding of ADS and its neighbor systems. This process tries to direct the system definition using external, internal, progressive, quantitative and scientific perspectives. The last method deals with safety requirements identification tools.KeywordsRequirement engineeringSystem engineeringHolistic thinkingAutomated driving system
Rigidity is a typical feature of contract law, since the cornerstone of contract law is that contracts bind the parties to it. Rigid contract law, however, is a challenge for contractual relations, where flexibility is needed. Russian contract law is rigid even compared to many other national contract laws, although the Russian Civil Code was completely re-written to correspond to the needs of a new market economy in the 1990´s. Due to the socialist inheritance, even contracting practices in business are exceptionally rigid. Such a contract culture reflecting strong attitudes of legal centralism leads on the one hand to peculiar ways in circumventing the rigid rules of contract law and neglecting written contract documents in favor of flexible practices on the other.
The article approaches contacts from two different standpoints. Firstly we study how flexibility is introduced in the rigid and formal contract law in the Russian Civil Code and court practice. Secondly we study Russian contract culture through interviews of businesspeople. We analyze our findings through several economic and sociological theories in a multidisciplinary way. The approach to understanding contracts is proactive law regarding contract as a tool in business promoting business goals rather than a legal device.
Digitalization move has motivated companies to adopt software for their business processes. This led to increase projects' complexity. Project management process plays a significant role in reaching a successful completion of IT-projects. It has been seen that management methodologies like waterfall and scrum are still not sufficient for every project. When it comes to complex projects where we need planning on the front part and agility on the developing part, a pure waterfall or agile is not sufficient. Thus, this study focuses on evaluating existing hybrid Methods as a useful alternative. A systematic literature review has been followed to select out the appropriate existing methodologies. Eleven different parameters have been selected for the evaluation on different measuring levels. It has been concluded based on a morphological analysis that a hybrid project management methodology is a good and efficient alternative.
The complexity of intermodal freight terminals poses a challenge for logistics planning. This also applies to the Next Generation Train CARGO (NGT CARGO) logistics terminal, which is embedded as a future intermodal transshipment hub in a high-speed freight train concept developed by the German Aerospace Center (DLR). Previous studies revealed that the existing terminal concept is only partially capable of facilitating the required intralogistics processes. This thesis investigates the successful application of Model-based Systems Engineering (MBSE) as guiding approach to a detailed system architecture of the NGT CARGO logistics terminal. Focus is laid on intralogistics freight handling. A tailored MBSE approach is derived and applied within a comprehensive architecture modeling process. As key outcome of the specification process, a product architecture variant is specifically designed for selected types of goods. The resulting variant is verified and validated from a logistics perspective. The underlying system model enables the creation of further NGT CARGO logistics terminal variants. The results of this work demonstrate that MBSE is capable of successfully guiding the architecture development of complex logistics facilities. Experienced advantages and disadvantages of the application of MBSE are discussed. Integration of the promising MBSE approach into current and future logistics planning is proposed.
. This study explores Global Virtual Software Teams’ development practices and try to demystify some of the misconceptions about global software development practices based on findings from the global virtual software teams’ experiment that was carried out at DePaul University from 2011 – 2018. The moments of translation from the perspective of actor-network theory (ANT) was employed in the data analysis, to examine how development approach was selected by the global virtual teams. One of the key findings from our research is that the success of a global software development project does not have a strong dependency on the development approach. While we agree that it is one of the key influencing factors, there are other equally strong factors for global virtual software team’s success.
Weeds are one of the organisms that interfere with plant growth. Information about the identity of weeds becomes very important on plantations. Although weeds data digitization has been done a lot, currently there is still not much weeds data information system can be accessed online. Weeds management is often dealt with weeds herbarium or weeds photographs.
In an effort to provide a good information system for farmers, this research aims to create a database of various types of weeds and an information system that can be accessed online. The methodology for developing a weed catalog information system uses the Software Development Life Cycle (SDLC). Weed samples in database were collected through systematic random sampling in the form of images and text. The result of this study is a Weeds Electronic Catalog or Weeds e-Catalog that can facilitate the information of weeds identity such as names, classifications, morphology, life cycles, and habitats of various types of weeds that grow on plantation land. Weeds e-Catalog can be used by plantation practitioners and farmers to make decisions in controlling weeds.
ResearchGate has not been able to resolve any references for this publication.