Semantic Bridging between Conceptual Modeling Standards and Agile Software Projects Conceptualizations

Software engineering benefitted from modeling standards (e.g. UML, BPMN), but Agile Software Project Management tends to marginalize most forms of documentation including diagrammatic modeling, focusing instead on the tracking of a project\u27s backlog and related issues. Limited means are available for annotating Jira items with diagrams, however not on a granular and semantically traceable level. Business processes tend to get lost on the way between process analysis (if any) and backlog items; UML design decisions are often disconnected from the issue tracking environment. This paper proposes domain-specific conceptual modeling to obtain a diagrammatic view on a Jira project, motivated by past conceptualizations of the agile paradigm while also offering basic interoperability with Jira to switch between environments and views. The underlying conceptualization extends conceptual modeling languages (BPMN, UML) with an agile project management perspective to enrich contextual traceability of a project\u27s elements while ensuring that data structures handled by Jira can be captured and exposed to Jira if needed. Therefore, concepts underlying the typical software development project management are integrated with established modeling concepts and tailored (with metamodeling means) for the domain-specificity of agile project management. A Design Science approach was pursued to develop a modeling method artifact, resulting in a domain-specific modeling tool for software project managers that want to augment agile practices and enrich issue annotation

Examining perceptions of agility in software development practice

This is the post-print version of the final published article that is available from the link below. Copyright @ 2010 ACM.Organizations undertaking software development are often reminded that successful practice depends on a number of non-technical issues that are managerial, cultural and organizational in nature. These issues cover aspects from appropriate corporate structure, through software process development and standardization to effective collaborative practice. Since the articulation of the 'software crisis' in the late-1960s, significant effort has been put into addressing problems related to the cost, time and quality of software development via the application of systematic processes and management practices for software engineering. Early efforts resulted in prescriptive structured methods, which have evolved and expanded over time to embrace consortia/ company-led initiatives such as the Unified Modeling Language and the Unified Process alongside formal process improvement frameworks such as the International Standards Organization's 9000 series, the Capability Maturity Model and SPICE. More recently, the philosophy behind traditional plan-based initiatives has been questioned by the agile movement, which seeks to emphasize the human and craft aspects of software development over and above the engineering aspects. Agile practice is strongly collaborative in its outlook, favoring individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan (see Sidebar 1). Early experience reports on the use of agile practice suggest some success in dealing with the problems of the software crisis, and suggest that plan-based and agile practice are not mutually exclusive. Indeed, flexibility may arise from this unlikely marriage in an aim to strike a balance between the rigor of traditional plan-based approaches and the need for adaptation of those to suit particular development situations. With this in mind, this article surveys the current practice in software engineering alongside perceptions of senior development managers in relation to agile practice in order to understand the principles of agility that may be practiced implicitly and their effects on plan-based approach

Web Services-Enhanced Agile Modeling and Integrating Business Processes

In a global business context with continuous changes, the enterprises have to enhance their operational efficiency, to react more quickly, to ensure the flexibility of their business processes, and to build new collaboration pathways with external partners. To achieve this goal, they must use e-business methods, mechanisms and techniques while capitalizing on the potential of new information and communication technologies. In this context, we propose a standards, model and Web services-based approach for modeling and integrating agile enterprise business processes. The purpose is to benefit from Web services characteristics to enhance the processes design and realize their dynamic integration. The choice of focusing on Web services is essentially justified by their broad adoption by enterprises as well as their capability to warranty interoperability between both intra and inter-enterprises systems. Thereby, we propose in this chapter a metamodel for describing business processes, and discuss their dynamic integration by addressing the Web services discovery issue. On the one hand, the proposed metamodel is in line with the W3C Web services standards, namely, WSDL, SAWSDL and WS-Policy. It considers the use of BPMN standard to describe the behavioral aspect of business processes and completes their design using UML diagrams describing their functional, non-functional and semantic aspects. On other hand, our approach for integrating processes is in line with BPEL standard recommended to orchestrate Web services. To realize executable business processes, this approach recommends the use of semantic matching and selection mechanisms in order to produce agile systems.Comment: 26 pages, 9 figures, Book chapte

KNOWLEDGE MODELING OF AGILE PROCESSES IN HEALTHCARE SYSTEMS DEVELOPMENT

Requirements on healthcare software products are becoming more and more complicated and software systems of today are characterized by increasing complexity and size. Therefore, software systems can no longer be developed feasibly without the processes supported by appropriate methods. We propose a method for configuration and modification of agile processes behind healthcare products development based on gathered knowledge and formal modeling. Our approach allows to support and optimize the processes with formal methods of modeling and machinelearning based simulations

Iterative criteria-based approach to engineering the requirements of software development methodologies

Software engineering endeavours are typically based on and governed by the requirements of the target software; requirements identification is therefore an integral part of software development methodologies. Similarly, engineering a software development methodology (SDM) involves the identification of the requirements of the target methodology. Methodology engineering approaches pay special attention to this issue; however, they make little use of existing methodologies as sources of insight into methodology requirements. The authors propose an iterative method for eliciting and specifying the requirements of a SDM using existing methodologies as supplementary resources. The method is performed as the analysis phase of a methodology engineering process aimed at the ultimate design and implementation of a target methodology. An initial set of requirements is first identified through analysing the characteristics of the development situation at hand and/or via delineating the general features desirable in the target methodology. These initial requirements are used as evaluation criteria; refined through iterative application to a select set of relevant methodologies. The finalised criteria highlight the qualities that the target methodology is expected to possess, and are therefore used as a basis for de. ning the final set of requirements. In an example, the authors demonstrate how the proposed elicitation process can be used for identifying the requirements of a general object-oriented SDM. Owing to its basis in knowledge gained from existing methodologies and practices, the proposed method can help methodology engineers produce a set of requirements that is not only more complete in span, but also more concrete and rigorous

Clients’ participation in software projects: comparative case study between an agile and a ‘traditional’ software company

One of the main characteristics of agile software development is the active and continuous participation and involvement of the clients throughout the project. According to agile proponents, this leads to building ‘the right’ product and to satisfied clients. In this paper we present a comparative study of two Dutch software development companies in respect to client participation and its impact on the project. One of the companies is purely agile while the other is following a traditional software development approach. Our study suggests that active clients’ participation is not an exclusive attribute of agile projects and that it can be successfully integrated (and implemented) in a traditional project as well. Further, the study shows that by involving clients, software companies have the chance to get higher customer satisfaction, regardless whether or not they implement agile software development processes. Although our study is not quantitative, we think that it is indicative about the impact of the factor “client’s participation” on the client’s satisfaction

A Strategic Framework for Agile Supply Chain Management on Global Supply Chain

A Strategic Framework for Agile Supply Chain Management on Global Supply Chain - Focusing on Agile Manufacturing Inventory Management KIM DONGWON Major in Department of Port Logostics Graduate School of Maritime Industrial Studies Korea Maritime University Abstract Changing customer and technological requirements force companies to develop agile supply chain capabilities in order to be competitive. A wealth of valuable approaches to supply chain strategic, tactical, and operational planning has been extensively developed. In this situation, agile inventory management on global supply chain has become one of the most major strategies to face stronger competition, the market pull and shorter product lifecycles. This study develops a framework to control the supply chain complexity and increase the efficiency, capability, implacability, and sustainability of decisions on how to design, plan, and run supply chains. In this paper, we especially focus on agility of inventory management on global supply chain. Futhermore, we propose to consider a strategic framework, using the crucial factors of agile supply chain managementalignment, adaptability, and visibility. In order to achieve agile supply chain management, integrated and optimal business processes are required. This research provide the opportunities for integration of business processes to a limited extend because most of them are rule based systems that control non-integrated transactions but there is no impetus for collaboration. We present one such business process framework modeling complex and its realization on global environment. Key words: Suppy chain management, Agile supply chains, Agile inventory management, Agility.1. Introduction 1 2. SCM & Business Performance 4 2.1 Factors for High Performers in SCM 4 2.2 SCM Pressures and Capabilities 8 2.3 Application Techniques for SCM Framework 16 3. Agility and Precedent Studies of Agile SCM 20 3.1 The Concept of Agility in SCM 20 3.2 The Importance of Agility 22 3.3 Limits of Precedent Studies of Agile SCM 24 4. Agile SCM framework 29 4.1 Visibility - Supply Chain Governance 32 4.2 Alignment to control complexity 38 4.3 Adaptability 43 4.4 Agile Manufacturing Inventory Management 46 5. Conclusion 6