A market based approach for resolving resource constrained task allocation problems in a software development process

We consider software development as an economic activity, where goods and services can be modeled as a resource constrained task allocation problem. This paper introduces a market based mechanism to overcome task allocation issues in a software development process. It proposes a mechanism with a prescribed set of rules, where valuation is based on the behaviors of stakeholders such as biding for a task. A bid process ensures that a stakeholder, who values the resource most, will have it allocated for a limited number of times. To observe the bidders behaviors, we initiate an approach incorporated with a process simulation model. Our preliminary results support the idea that our model is useful for optimizing the value based task allocations, creating a market value for the project assets, and for achieving proper allocation of project resources specifically on large scale software projects

Beyond Surveys: Analyzing Software Development Artifacts to Assess Teaching Efforts

This Innovative Practice Full Paper presents an approach of using software development artifacts to gauge student behavior and the effectiveness of changes to curriculum design. There is an ongoing need to adapt university courses to changing requirements and shifts in industry. As an educator it is therefore vital to have access to methods, with which to ascertain the effects of curriculum design changes. In this paper, we present our approach of analyzing software repositories in order to gauge student behavior during project work. We evaluate this approach in a case study of a university undergraduate software development course teaching agile development methodologies. Surveys revealed positive attitudes towards the course and the change of employed development methodology from Scrum to Kanban. However, surveys were not usable to ascertain the degree to which students had adapted their workflows and whether they had done so in accordance with course goals. Therefore, we analyzed students' software repository data, which represents information that can be collected by educators to reveal insights into learning successes and detailed student behavior. We analyze the software repositories created during the last five courses, and evaluate differences in workflows between Kanban and Scrum usage

Agile Requirements Engineering: A systematic literature review

Nowadays, Agile Software Development (ASD) is used to cope with increasing complexity in system development. Hybrid development models, with the integration of User-Centered Design (UCD), are applied with the aim to deliver competitive products with a suitable User Experience (UX). Therefore, stakeholder and user involvement during Requirements Engineering (RE) are essential in order to establish a collaborative environment with constant feedback loops. The aim of this study is to capture the current state of the art of the literature related to Agile RE with focus on stakeholder and user involvement. In particular, we investigate what approaches exist to involve stakeholder in the process, which methodologies are commonly used to present the user perspective and how requirements management is been carried out. We conduct a Systematic Literature Review (SLR) with an extensive quality assessment of the included studies. We identified 27 relevant papers. After analyzing them in detail, we derive deep insights to the following aspects of Agile RE: stakeholder and user involvement, data gathering, user perspective, integrated methodologies, shared understanding, artifacts, documentation and Non-Functional Requirements (NFR). Agile RE is a complex research field with cross-functional influences. This study will contribute to the software development body of knowledge by assessing the involvement of stakeholder and user in Agile RE, providing methodologies that make ASD more human-centric and giving an overview of requirements management in ASD.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Visual Management in Brazilian Construction Companies: Taxonomy and Guidelines for Implementation

Visual management (VM) is the managerial strategy of consciously integrating visual tools in workspaces with the aim of increasing transparency on construction sites. Several VM tools and approaches that had been originally developed in the manufacturing context were implemented in construction. However, research on the application of VM in construction as a managerial strategy is scarce. This paper aims to investigate and classify the types of visual devices that can be used in construction sites through multiple case studies carried out in nine construction companies actively implementing VM. It also discusses strategies for the implementation of VM in construction. The main contributions of this investigation are: (1) a VM tools taxonomy that can be used to identify VM application opportunities, providing a basis for evaluating the level of VM implementation in construction; and (2) identification of critical factors for the implementation and various features of the VM strategy in construction

Customized Pull Systems for Single-Product Flow Lines

Traditionally pull production systems are managed through classic control systems such as Kanban, Conwip, or Base stock, but this paper proposes ‘customized’ pull control. Customization means that a given production line is managed through a pull control system that in principle connects each stage of that line with each preceding stage; optimization of the corresponding simulation model, however, shows which of these potential control loops are actually implemented. This novel approach may result in one of the classic systems, but it may also be another type: (1) the total line may be decomposed into several segments, each with its own classic control system (e.g., segment 1 with Kanban, segment 2 with Conwip); (2) the total line or segments may combine different classic systems; (3) the line may be controlled through a new type of system. These different pull systems are found when applying the new approach to a set of twelve production lines. These lines are configured through the application of a statistical (Plackett-Burman) design with ten factors that characterize production lines (such as line length, demand variability, and machine breakdowns).Pull production / inventory;sampling;optimization;evolutionary algorithm

Semantic business process management: a vision towards using semantic web services for business process management

Business process management (BPM) is the approach to manage the execution of IT-supported business operations from a business expert's view rather than from a technical perspective. However, the degree of mechanization in BPM is still very limited, creating inertia in the necessary evolution and dynamics of business processes, and BPM does not provide a truly unified view on the process space of an organization. We trace back the problem of mechanization of BPM to an ontological one, i.e. the lack of machine-accessible semantics, and argue that the modeling constructs of semantic Web services frameworks, especially WSMO, are a natural fit to creating such a representation. As a consequence, we propose to combine SWS and BPM and create one consolidated technology, which we call semantic business process management (SBPM

On the Interface Between Operations and Human Resources Management

Operations management (OM) and human resources management (HRM) have historically been very separate fields. In practice, operations managers and human resource managers interact primarily on administrative issues regarding payroll and other matters. In academia, the two subjects are studied by separate communities of scholars publishing in disjoint sets of journals, drawing on mostly separate disciplinary foundations. Yet, operations and human resources are intimately related at a fundamental level. Operations are the context that often explains or moderates the effects of human resource activities such as pay, training, communications and staffing. Human responses to operations management systems often explain variations or anomalies that would otherwise be treated as randomness or error variance in traditional operations research models. In this paper, we probe the interface between operations and human resources by examining how human considerations affect classical OM results and how operational considerations affect classical HRM results. We then propose a unifying framework for identifying new research opportunities at the intersection of the two fields

New species of hybrid pull systems

production models;control systems;simulation

Optimal Kanban Number: An Integrated Lean and Simulation Modelling Approach

Kanban is credited as a major means to controlling the inventory within a manufacturing system. Determining the optimum number of Kanban is of great interest for manufacturing industries. To fulfill this aim, an integrated modelling approach using discrete-event simulation technique and Kanban Lean tool is developed for a pull system ensuring an optimum Kanban number. This research has developed a base-case simulation model which was statistically validated using ANOVA. Initial Kanban number obtained from the mathematical model of Toyota motor company is used to obtain initial results. A Kanban integrated simulation model is developed that employed the idea of pull system that required the arrival of a customer for a product and Kanban pair to proceed through the production steps. The Kanban-Simulation integrated model is further used to test the effect of different Kanban numbers to obtain the best value of Kanban which is selected as 275. This approach has been applied on a case company involved in the manufacturing of agricultural and construction metal hand tools. The optimum Kanban number is selected by simulating the model about three performance indicators: customer waiting time, weekly throughput, and Work-in-progress. The analysis of the results obtained from the proposed integrated Kanban-simulation model showed a 76.7% reduction in the inventory level. The integrated Kanban-simulation model has also given a minimum customer waiting time of 0.84 Hrs. and a maximum throughput value of 737 Pcs of shovels. The integrated Kanban-simulation model is useful for manufacturing industries working to avoid overproduction waste and greatly reduce inventory costs

Agile and Lean Systems Engineering: Kanban in Systems Engineering

This is the 2nd of two reports that were created for research on this topic funded through SERC. The first report, SERC-TR-032-1 dated March 13, 2012, constituted the 2011-2012 Annual Technical Report and the Final Technical Report of the SERC Research Task RT-6: Software Intensive Systems Data Quality and Estimation Research In Support of Future Defense Cost Analysis. The overall objectives of RT-6 were to use data submitted to DoD in the Software Resources Data Report (SRDR) forms to provide guidance for DoD projects in estimating software costs for future DoD projects. In analyzing the data, the project found variances in productivity data that made such SRDR-based estimates highly variable. The project then performed additional analyses that provided better bases of estimate, but also identified ambiguities in the SRDR data definitions that enabled the project to help the DoD DCARC organization to develop better SRDR data definitions. In SERC-TR-2012-032-1, the resulting Manual provided the guidance elements for software cost estimation performers and users. Several appendices provide further related information on acronyms, sizing, nomograms, work breakdown structures, and references. SERC-TR-2013-032-2 (current report), included the “Software Cost Estimation Metrics Manual.” This constitutes the 2012-2013 Annual Technical Report and the Final Technical Report of the SERC Research Task Order 0024, RT-6: Software Intensive Systems Cost and Schedule Estimation Estimating the cost to develop a software application is different from almost any other manufacturing process. In other manufacturing disciplines, the product is developed once and replicated many times using physical processes. Replication improves physical process productivity (duplicate machines produce more items faster), reduces learning curve effects on people and spreads unit cost over many items. Whereas a software application is a single production item, i.e. every application is unique. The only physical processes are the documentation of ideas, their translation into computer instructions and their validation and verification. Production productivity reduces, not increases, when more people are employed to develop the software application. Savings through replication are only realized in the development processes and on the learning curve effects on the management and technical staff. Unit cost is not reduced by creating the software application over and over again. This manual helps analysts and decision makers develop accurate, easy and quick software cost estimates for different operating environments such as ground, shipboard, air and space. It was developed by the Air Force Cost Analysis Agency (AFCAA) in conjunction with DoD Service Cost Agencies, and assisted by the SERC through involving the University of Southern California and the Naval Postgraduate School. The intent is to improve quality and consistency of estimating methods across cost agencies and program offices through guidance, standardization, and knowledge sharing. The manual consists of chapters on metric definitions, e.g., what is meant by equivalent lines of code, examples of metric definitions from commercially available cost models, the data collection and repository form, guidelines for preparing the data for analysis, analysis results, cost estimating relationships found in the data, productivity benchmarks, future cost estimation challenges and a very large appendix.SERCU.S. Department of DefenseSystems Engineering Research Center (SERC)Systems Engineering Research Center (SERC) Contract H98230-08-D-0171