scholarly journals The Study of Resource Allocation among Software Development Phases: An Economics-Based Approach

2011 ◽  
Vol 2011 ◽  
pp. 1-21 ◽  
Author(s):  
Peleg Yiftachel ◽  
Irit Hadar ◽  
Dan Peled ◽  
Eitan Farchi ◽  
Dan Goldwasser
Keyword(s):  
Resource Allocation ◽  
Software Development ◽  
Empirical Studies ◽  
Profit Maximization ◽  
Maximization Problem ◽  
Software Production ◽  
Software Product ◽  
Development Processes ◽  
Development Phases ◽  
Novel Concept

This paper presents an economics-based approach for studying the problem of resource allocation among software development phases. Our approach is structured along two parallel axes: theoretical and empirical. We developed a general economic model for analyzing the allocation problem as a constrained profit maximization problem. The model, based on a novel concept of software production function, considers the effects of different allocations of development resources on output measures of the resulting software product. An empirical environment for evaluating and refining the model is presented, and a first exploratory study for characterizing the model's components and developers' resource allocation decisions is described. The findings illustrate how the model can be applied and validate its underlying assumptions and usability. Future quantitative empirical studies can refine and substantiate various aspects of the proposed model and ultimately improve the productivity of software development processes.

Usability Engineering in Agile Software Development Processes

2016 ◽  
pp. 208-221
Author(s):  
Muhammad Aminu Umar ◽  
Sheidu Salami Tenuche ◽  
Sahabi Ali Yusuf ◽  
Aminu Onimisi Abdulsalami ◽  
Aliyu Muhammad Kufena
Keyword(s):  
Software Development ◽  
User Interaction ◽  
Agile Software Development ◽  
Functional Requirements ◽  
Usability Engineering ◽  
Agile Processes ◽  
Software Product ◽  
Development Processes ◽  
Software Development Methodologies ◽  
Agile Software

As the popularity and acceptance of agile software development methodologies increases, the need to integrate usability engineering in the design and development processes is imperative. While, agile the focus is on technical and functional requirements not on end-user interaction, usability is usually only dealt with on the side. Combining this two in practice will go a long way in development of better product. Since the success and acceptance of software product depends not only on the technologies used but how well it integrates user-oriented methods. Therefore, this chapter puts together works on how usability engineering has been integrated with agile processes.

Software Development Crisis

2017 ◽  
pp. 126-148 ◽  
Author(s):  
Sergey Zykov
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Nuclear Power ◽  
Oil And Gas ◽  
Software Production ◽  
Number Of Factors ◽  
Software Product ◽  
Software And Hardware ◽  
The 1960S ◽  
General Architecture

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.

Effect of knowledge management on software product experience with mediating effect of perceived software process improvement: An empirical study for Indian software industry

2019 ◽  
Vol 46 (2) ◽  
pp. 258-272
Author(s):  
Mitali Chugh ◽  
Nitin Chanderwal ◽  
Rajesh Upadhyay ◽  
Devendra Kumar Punia
Keyword(s):  
Knowledge Management ◽  
Empirical Study ◽  
Software Development ◽  
Process Improvement ◽  
Software Process ◽  
Empirical Studies ◽  
Software Process Improvement ◽  
Mediating Effect ◽  
Software Product ◽  
The Impact

The software development industry is characterised by swift innovation and competition. To survive, software engineering (SE) organisations need to develop high-quality software products in a timely fashion and at low cost. Knowledge-based approaches to software development are extremely supportive to acquiring new knowledge and leveraging existing knowledge from software projects; this enables constant improvement of software development practices. In this empirical study of Indian SE organisations, we study the impact of managing knowledge for perceived software process improvement (PSPI) and its effect on software product quality. Information technology (IT) in knowledge management (KM) is an important facilitator for any SE organisation desiring to exploit evolving technologies for management of their knowledge assets and for carrying out various KM processes of knowledge capture, storage, retrieval and sharing. Surveys collected from Indian SE organisations were analysed to propose a model using a structured equation modelling (SEM) technique. Our findings reveal that the relation between KM and quality of software product is positively mediated by PSPI. These findings reinforce an arena that is of growing importance to researchers and practitioners and which has seen only a limited number of empirical studies to date in the context of Indian SE organisations.

Obstacles for the Integration of HCI Practices into Software Engineering Development Processes

2006 ◽  
pp. 422-428 ◽  
Author(s):  
Xavier Ferre ◽  
Natalia Juristo ◽  
Ana M. Moreno
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Computer Literacy ◽  
Software Process ◽  
Software Systems ◽  
Software Products ◽  
Software Market ◽  
Visible Part ◽  
Software Product ◽  
Development Processes

Usability has become a critical quality factor in software systems, and it has been receiving increasing attention over the last few years in the SE (software engineering) field. HCI techniques aim to increase the usability level of the final software product, but they are applied sparingly in mainstream software development, because there is very little knowledge about their existence and about how they can contribute to the activities already performed in the development process. There is a perception in the software development community that these usability-related techniques are to be applied only for the development of the visible part of the UI (user interface) after the most important part of the software system (the internals) has been designed and implemented. Nevertheless, the different paths taken by HCI and SE regarding software development have recently started to converge. First, we have noted that HCI methods are being described more formally in the direction of SE software process descriptions. Second, usability is becoming an important issue on the SE agenda, since the software products user base is ever increasing and the degree of user computer literacy is decreasing, leading to a greater demand for usability improvements in the software market. However, the convergence of HCI and SE has uncovered the need for an integration of the practices of both disciplines. This integration is a must for the development of highly usable systems. In the next two sections, we will look at how the SE field has viewed usability. Following upon this, we address the existing approaches to integration. We will then detail the pending issues that stand in the way of successful integration efforts, concluding with the presentation of an approach that might be successful in the integration endeavor.

Software Development Crisis

2021 ◽  
pp. 1145-1162
Author(s):  
Sergey Zykov
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Nuclear Power ◽  
Oil And Gas ◽  
Software Production ◽  
Number Of Factors ◽  
Software Product ◽  
Software And Hardware ◽  
The 1960S ◽  
General Architecture

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.

scholarly journals Comparison of the Two-Hemisphere Model-Driven Approach to Other Methods for Model-Driven Software Development

2015 ◽  
Vol 18 (1) ◽  
pp. 5-14
Author(s):  
Oksana Nikiforova ◽  
Ludmila Kozacenko ◽  
Dace Ahilcenoka ◽  
Konstantins Gusarovs ◽  
Dainis Ungurs ◽  
...  
Keyword(s):  
Software Development ◽  
Relevant Information ◽  
Software Components ◽  
Science Field ◽  
Model Driven ◽  
Software Product ◽  
Model Driven Software Development ◽  
Development Phases ◽  
The Moment ◽  
Model Driven Approach

Abstract Models are widely used not only in computer science field, but also in other fields. They are an effective way to show relevant information in a convenient way. Model-driven software development uses models and transformations as first-class citizens. That makes software development phases more related to each other, those links later help to make changes or modify software product more freely. At the moment there are a lot of methods and techniques to create those models and transform them into each other. Since 2004, authors have been developing the so called 2HMD approach to bridge the gap between problem domain and software components by using models and model transformation. The goal of this research is to compare different methods positioned for performing the same tasks as the 2HMD approach and to understand the state of the art in the area of model-driven software development.

Inelastic sports ticket pricing, marginal win revenue, and firm pricing strategy

2016 ◽  
Vol 42 (9) ◽  
pp. 922-927 ◽  
Author(s):  
Yang-Ming Chang ◽  
Joel M. Potter ◽  
Shane Sanders
Keyword(s):  
Demand Curve ◽  
Empirical Studies ◽  
Profit Maximization ◽  
Maximization Problem ◽  
Standard Result ◽  
Content Type ◽  
Ticket Pricing ◽  
Crowd Density ◽  
Sports Team ◽  
Profit Maximizing

Purpose A standard result of firm theory is that a monopoly maximizes profit somewhere along the elastic portion of its demand curve. However, empirical studies of sports ticket pricing routinely find that (home) teams price along the inelastic portion of demand. Despite compelling theoretical explanations of this finding, at least one important factor remains unconsidered. A profit-maximizing team considers not only direct marginal revenue and direct marginal cost when setting a ticket price but also deferred, strategic benefit (revenue) from present game success. The paper aims to discuss these issues. Design/methodology/approach Prior literature finds that a given win is valued in that it generates additional future revenue and likelihood of home victory rises, ceteris paribus, in crowd density. The authors construct a firm profit maximization problem in which a sports team considers both present and future revenue when pricing home games in the present period. Findings If the deferred benefit is sufficiently large, a forward-looking, profit-maximizing team prices along the inelastic portion of its static demand curve. Importantly, this same price falls along the elastic portion of the firm’s (empirically unobserved) dynamic demand curve. Originality/value This is the first model of sports ticket pricing to recognize the intertemporal nature of demand for a sports match.

scholarly journals Interior point algorithm for solving farm resource allocation problem

2017 ◽  
Vol 11 (1-2) ◽  
pp. 45-49
Author(s):  
Henry De-Graft Acquah ◽  
Sarah Acquah
Keyword(s):  
Resource Allocation ◽  
Interior Point ◽  
Profit Maximization ◽  
Simplex Algorithm ◽  
Allocation Problem ◽  
Maximization Problem ◽  
Similar Amount ◽  
Interior Point Algorithm ◽  
Resource Allocation Problem ◽  
Jel Code

This paper introduces interior point algorithm as an alternative approach to simplex algorithm for solving farm resource allocation problem. The empirical result of interior point algorithm is compared with that of the simplex algorithm. It goes further to address a profit maximization problem. The result revealed several relevant patterns. Results of the interior point algorithm is similar to that of the simplex algorithm. Findings indicated that in both algorithms, the farm is to produce peppers, wheat which is irrigated and weeded manually, hire additional month of labour, and also purchase urea and muriate fertilizer to realize a similar amount of profit. Additionally, both algorithms suggested that practicing crop rotation where beans, if grown, should be altered with wheat cannot be possible since no beans will be grown. The Simplex algorithm saves 39 iterations over Interior Point algorithm in solving the farm resource allocation problem. The findings demonstrate that the interior point algorithm offers a useful alternative to the simplex algorithm when addressing farm resource allocation problem. JEL code: D24, D57, C61, C63, C67

Computable metrics of personal performance in software development teams

2019 ◽  
Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Product Quality ◽  
Performance Indicators ◽  
Key Performance Indicators ◽  
Project Manager ◽  
Development Life Cycle ◽  
Software Product ◽  
Software Development Life Cycle

The present article describes setup, configuration and usage of the key performance indicators (KPIs) of members of project teams involved into the software development life cycle. Key performance indicators are described for the full software development life cycle and imply the deep integration with both task tracking systems and project code management systems, as well as a software product quality testing system. To illustrate, we used the extremely popular products - Atlassian Jira (tracking development tasks and bugs tracking system) and git (code management system). The calculation of key performance indicators is given for a team of three developers, two testing engineers responsible for product quality, one designer, one system administrator, one product manager (responsible for setting business requirements) and one project manager. For the key members of the team, it is suggested to use one integral key performance indicator per the role / team member, which reflects the quality of the fulfillment of the corresponding role of the tasks. The model of performance indicators is inverse positive - the initial value of each of the indicators is zero and increases in the case of certain deviations from the standard performance of official duties inherent in a particular role. The calculation of the proposed key performance indicators can be fully automated (in particular, using Atlassian Jira and Atlassian Bitbucket (git) or any other systems, like Redmine, GitLab or TestLink), which eliminates the human factor and, after the automation, does not require any additional effort to calculate. Using such a tool as the key performance indicators allows project managers to completely eliminate bias, reduce the emotional component and provide objective data for the project manager. The described key performance indicators can be used to reduce the time required to resolve conflicts in the team, increase productivity and improve the quality of the software product.

Sign in / Sign up

Export Citation Format

Share Document