Automated Framework for Software Process Model Selection Based on Soft Computing Approach

2021 ◽  
pp. 1367-1390
Author(s):  
Swati Dhingra ◽  
Mythili Thirugnanam ◽  
Poorvi Dodwad ◽  
Meghna Madan
Keyword(s):  
Software Engineering ◽  
Model Selection ◽  
Software Development ◽  
Process Model ◽  
Development Project ◽  
Project Managers ◽  
Software Project ◽  
Rule Engine ◽  
Software Development Project ◽  
Software Companies

Software engineering is an engineering approach for software development. It is a discipline whose aim is the production of fault-free, delivered on-time and within budget software that satisfies the user's needs. Software engineering principles need to be followed to ensure a successful software development project. Within organizations that are involved in software development, the challenge is to select the appropriate process model for the software project. The objective of this chapter is to determine the factors which influence the process model selection. This chapter presents an automated framework for selection of process model using fuzzy-based rule engine and to bring more accuracy for choice of process model, J-48 decision tree was used considering factors as inputs. The user has to give characteristic value of the prioritized factor as input and on the basis of the rules, model is anticipated. The developed framework will be profitable for project managers, experts and venture pioneers in software companies.

Automated Framework for Software Process Model Selection Based on Soft Computing Approach

2017 ◽  
pp. 395-418
Author(s):  
Swati Dhingra ◽  
Mythili Thirugnanam ◽  
Poorvi Dodwad ◽  
Meghna Madan
Keyword(s):  
Software Engineering ◽  
Model Selection ◽  
Software Development ◽  
Process Model ◽  
Development Project ◽  
Project Managers ◽  
Software Project ◽  
Rule Engine ◽  
Software Development Project ◽  
Software Companies

Software engineering is an engineering approach for software development. It is a discipline whose aim is the production of fault-free, delivered on-time and within budget software that satisfies the user's needs. Software engineering principles need to be followed to ensure a successful software development project. Within organizations that are involved in software development, the challenge is to select the appropriate process model for the software project. The objective of this chapter is to determine the factors which influence the process model selection. This chapter presents an automated framework for selection of process model using fuzzy-based rule engine and to bring more accuracy for choice of process model, J-48 decision tree was used considering factors as inputs. The user has to give characteristic value of the prioritized factor as input and on the basis of the rules, model is anticipated. The developed framework will be profitable for project managers, experts and venture pioneers in software companies.

Software Project Managers under the Team Software Process

2012 ◽  
pp. 115-126
Author(s):  
Marcos Ruano-Mayoral ◽  
Ricardo Colomo-Palacios ◽  
Ángel García-Crespo ◽  
Juan Miguel Gómez-Berbís
Keyword(s):  
Software Development ◽  
Software Process ◽  
Development Project ◽  
Project Managers ◽  
Project Manager ◽  
Software Project ◽  
Software Projects ◽  
Software Development Project ◽  
Team Software Process ◽  
Definition Of

Despite the clear relevance of the Information and Communications Technologies (ICT) market in world economics and the evident lack of success of software projects, organizations devote little effort to the development and maturity of the software project manager profession. This work analyzes the figure of project manager from the perspective of the Team Software Process (TSP), and it considers the required skills, attitudes and knowledge for a software development project. The basis for the study is the analysis of relevant references from the literature for their subsequent categorization into different competency concepts. The results of the analysis are compared with the contributions which the Guide to the SWEBOK® and the PMBOK® Guide models provide of the profiles of the project manager. The results indicate that the literature relating to the Team Software Process is focused on the definitions of skills and attitudes, and to a lesser extent on knowledge components. The lack of the definition of the components which comprise competency constitutes a challenge for software development organizations that use TSP, whose project managers should confront the task with full capacities, and without the help of established and recognized competencies. The current work attempts to establish the competencies for project managers identified in the literature, in the environment of the use of TSP for software development, using a study based on content analysis.

scholarly journals ROI Estimation in a Scrum Project: A case study

10.29007/nqq6 ◽  
2019 ◽  
Author(s):  
Rita Cortés ◽  
Fulvio Lizano
Keyword(s):  
Software Development ◽  
Return On Investment ◽  
Investment Decisions ◽  
Development Project ◽  
Project Managers ◽  
Future Research ◽  
Software Project ◽  
Software Development Project ◽  
Financial Metrics

Financial metrics are necessary to inform decisions about the beginning or continuity of a software development project to justify investments. This research discuses initial ROI (Return on Investment) estimates in a software project using Scrum and how to analyze variations in the initial calculations to make return on investment decisions during partial deliveries of the product. The case study included a survey, a review of documentation, two focus group sessions, and an exercise involving application of the proposed technique. Twenty-four professionals participated, of which 4 were Scrum trainers (17%), 4 were officials of the company where the estimation technique was applied (17%), and 16 were project managers of domestic and foreign software development companies (66%), all of whom had experience in project management. This study provides elements to be considered in future research on ROI calculation in projects using Scrum, and can be used as a guide to estimate and review financial metrics during the execution of an actual project.

Software Project Managers under the Team Software Process

2010 ◽  
Vol 1 (1) ◽  
pp. 42-53 ◽  
Author(s):  
Marcos Ruano-Mayoral ◽  
Ricardo Colomo-Palacios ◽  
Ángel García-Crespo ◽  
Juan Miguel Gómez-Berbís
Keyword(s):  
Software Development ◽  
Software Process ◽  
Development Project ◽  
Project Managers ◽  
Project Manager ◽  
Software Project ◽  
Information And Communications Technologies ◽  
Software Projects ◽  
Software Development Project ◽  
Team Software Process

Despite the clear relevance of the Information and Communications Technologies (ICT) market in world economics and the evident lack of success of software projects, organizations devote little effort to the development and maturity of the software project manager profession. This work analyzes the figure of project manager from the perspective of the Team Software Process (TSP), and it considers the required skills, attitudes and knowledge for a software development project. The basis for the study is the analysis of relevant references from the literature for their subsequent categorization into different competency concepts. The results of the analysis are compared with the contributions which the Guide to the SWEBOK® and the PMBOK® Guide models provide of the profiles of the project manager. The results indicate that the literature relating to the Team Software Process is focused on the definitions of skills and attitudes, and to a lesser extent on knowledge components. The lack of the definition of the components which comprise competency constitutes a challenge for software development organizations that use TSP, whose project managers should confront the task with full capacities, and without the help of established and recognized competencies. The current work attempts to establish the competencies for project managers identified in the literature, in the environment of the use of TSP for software development, using a study based on content analysis.

scholarly journals Towards a methodology to estimate cost of object-oriented software development projects

2004 ◽  
Vol 1 (2) ◽  
pp. 173-194 ◽  
Author(s):  
Radoslav Rakovic
Keyword(s):  
Software Development ◽  
Development Process ◽  
A Priori ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Subsequent Development ◽  
Development Project ◽  
Software Project ◽  
Software Development Project ◽  
Early Estimate

Successful management of a software project, besides a well-defined project development process, requires an early estimate of project complexity. In a prevailing practice, software development costs usually have been determined a posteriori i.e. after software project implementation. It is essential however, to know this estimate a priori, i.e., before commencement of works. This paper presents an attempt to construct a methodology that would enable an early estimate of software development cost and its refinements during subsequent development phases. The methodology assumes an object-oriented approach based on the Unified Modeling Language (UML) and Unified Software Development Process (USDP). It outlines an Use Case Driven Architecture-Centric, Iterative and Incremental estimate process that could significantly improve and simplify early cost estimates. The presented methodology is illustrated on example of the POST software development project.

Measuring Software Development Project Performance

2019 ◽  
pp. 315-345
Author(s):  
Nihan Yildirim ◽  
Semih Ersöz ◽  
Bilal Altun
Keyword(s):  
Data Collection ◽  
Software Development ◽  
Measurement Model ◽  
Development Project ◽  
Agile Development ◽  
High Tech ◽  
Software Development Project ◽  
Software Companies ◽  
Expert Opinions ◽  
Development Processes

Adopting agile methodologies to software development processes helps software companies to sustain their growth through efficiency for long term. In the digital transformation era, Industry 4.0 as part of High-Tech Strategy 2020 for Germany involves agile principles and brings the latest technological trends in production process. The purpose of this chapter is to design a proper agile project management performance measurement model for start-up software companies. First, all key performance indicators related to agile development in the literature have been listed. Then KPIs that are provided from literature review with content analysis have been reviewed and categorized by expert opinions that were collected through in-depth interviews. Seven strategic KPIs and their data collection systems are defined and designed. Lastly, process and data collection improvements are recommended in order to sustain agile development measurement model.

QPLAN

2017 ◽  
pp. 259-283
Author(s):  
Marco Antônio Amaral Féris
Keyword(s):  
Software Development ◽  
Design Science ◽  
Science Research ◽  
Design Science Research ◽  
Research Process ◽  
Project Performance ◽  
Development Project ◽  
Software Project ◽  
Software Development Project ◽  
Key Factor

As business competition increases, there is pressure on software development projects to become more productive and efficient. Previous research has shown that quality planning is a key factor in enhancing project performance. Thus, this article reports on the successful development and implementation of a tool (QPLAN) that enhances software development project performance by evaluating the planning quality of any type of software project and introducing best planning practices (such as references from historical data) that suggest how to manage projects in an appropriate manner, including encompassing lessons learned and involving the customer in the development process. This is applied research aimed at solving a real problem; thus, Design Science Research was adopted as the research methodology and the design science research process (DSRP) model was selected to conduct it. This artifact was designed for the project management literature, and implemented and validated in 11 organizations in five countries.

scholarly journals Knowledge management in small software development organisations: A South African perspective

2017 ◽  
Vol 19 (1) ◽  
Author(s):  
Mzwandile M. Shongwe
Keyword(s):  
Knowledge Management ◽  
Software Development ◽  
Software Process Improvement ◽  
Development Project ◽  
Project Managers ◽  
Intervention Strategies ◽  
Software Development Project ◽  
Organisational Routines ◽  
Software Development Methodologies ◽  
Knowledge Intensive

Background: Software organisations have been experiencing software development failures since the beginning of software development. Globally, latest Standish Group CHAOS reports indicate that only 29% of projects are successful. In South Africa (SA), the ITWeb report (2013) indicates that only 11% of all projects are successful. Intervention strategies such as software process improvement (SPI) frameworks and new software development methodologies such as agile methods have been introduced to address this issue. These intervention strategies do not seem to be effective because software development projects continue to fail. To address this issue, software organisations are turning to knowledge management (KM). This is because software development is a knowledge-intensive task.Objectives: The study aimed to investigate KM practices in small, medium and micro (SMMEs) software development organisations in SA and to determine if KM has benefited the organisations.Method: Fifteen software development project managers from 15 software development SMMEs were interviewed. Content analysis was used to analyse the data.Results: The study found six KM practices in the organisations: knowledge acquisition, creation, storage, sharing, organisation and application. The study found that KM has benefited organisations by making them effective, efficient and productive.Conclusions: The study concluded that software development organisation have adopted KM, although informally, and that KM practices have improved organisational routines and processes.

3LRM-3 Layer Risk Mitigation Modelling of ICT Software Development Projects

2016 ◽  
Vol 6 (1) ◽  
pp. 349 ◽  
Author(s):  
Salma Firdose ◽  
L. Manjunath Rao
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Risk Mitigation ◽  
New Technology ◽  
Development Project ◽  
Risk Modelling ◽  
Software Development Project ◽  
Critical Issues ◽  
Random Probability ◽  
Adoption Of New Technology

With the adoption of new technology and quality standards, the software development firms are still encountering the critical issues of risk modelling. With the changing dynamics of customer needs, potential competition has being mushrooming in the global IT markets to relay a new standard of software engineering which has higher capability of sustaining risk.  However, till date, it is still theoretical to large extent from research viewpoint. Hence, this paper presents a mathematical model called as 3LRM that is designed with the simple approach keeping in mind the real-time issues of risk factors in software engineering for ICT software development project. The study has also identified requirement volatility as one of the prominent source of risk and hence, the framework intends to identify a risk as well as mitigating the risk to a large extent. The paper is illustrated with some of the simple statistical approaches of random probability.

A study of software development project cost, schedule and quality by outsourcing to low cost destination

2016 ◽  
Vol 29 (3) ◽  
pp. 454-478 ◽  
Author(s):  
Debasisha Mishra ◽  
Biswajit Mahanty
Keyword(s):  
Software Development ◽  
Development Project ◽  
Dynamics Simulation ◽  
Software Project ◽  
Design Work ◽  
Project Cost ◽  
Content Type ◽  
Software Development Project ◽  
Study Results ◽  
Testing Work

Purpose – The purpose of this paper is to find good values of onsite-offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team so as to reduce project cost and improve schedule in a global software development (GSD) environment for software development project. Design/methodology/approach – This study employs system dynamics simulation approach to study software project characteristics in both co-located and distributed development environments. The authors consulted 14 experts from Indian software outsourcing industry during our model construction and validation. Findings – The study results show that there is a drop in overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule. Research limitations/implications – The implication of the study is that the project management team should be careful not to keep high percentage of manpower at offshore location in distributed software environment. A large offshore team can increase project cost and schedule due to higher training overhead, lower productivity and higher error proneness. In GSD, the management effort should be to keep requirement analysis and design work at onsite location and involves the offshore team in coding and testing work. Practical implications – The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment. Originality/value – The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in GSD environment.

Sign in / Sign up

Export Citation Format

Share Document