Software Project’s Complexity Measurement: A Case Study

Fitsilis, Panos; Damasiotis, Vyron

doi:10.4236/jsea.2015.810052

Cited by 8 publications

(3 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The most common methods can be used for story size estimation is a planning poker method [15]. The complexity refers to a measure of the resources expended by a system while interacting with a piece of software to perform a given task [16]. Also, the teamwork uses the Fibonacci series method to scale the complexity.…”

Section: Story Point's Methodsmentioning

confidence: 99%

An Enhanced Framework for Effort Estimation of Agile Projects

Raslan¹,

Darwish²

2018

IJIES

View full text Add to dashboard Cite

Software effort estimation methods are used to measure the total time and forecast the amount of required effort to develop the software. In addition, agile software projects, the requirements are characterized by changeability during the software projects. Therefore using the traditional estimation models in agile software projects may cause inaccurate effort estimation. This paper proposes a framework which utilizes The Constructive Cost Model (COCOMO II), story points, and fuzzy logic models without affecting the sacredness of agile principles. Furthermore, the results show the proposed framework increasing the value of Prediction Level (Pred) to 80%.

show abstract

Section: Story Point's Methodsmentioning

confidence: 99%

An Enhanced Framework for Effort Estimation of Agile Projects

Raslan¹,

Darwish²

2018

IJIES

View full text Add to dashboard Cite

show abstract

“…In [7] Vyron et al, proposed that the project management is a management method which used widely today in order to manage the complex problems. In this paper they analyzed he factors involved in the complexity of software that are related to project time, cost and quality.…”

Section: Literature Reviewmentioning

confidence: 99%

A Comparitive Analysis Between Open Source And Closed Source Software in Terms of Complexity and Quality Factors

Sirshar¹,

Akramizadeh²,

Ibrahim³

2019

Preprint

View full text Add to dashboard Cite

The complexity of software is increasing day by day due to the increase in the size of the projects being developed. For better planning and management of large software projects, estimation of software quality is important. During the development processes, complexity metrics are used for the indication of the attributes/characteristics of the quality software. There are many studies about the effect of the complexity of the software on the cost and quality. In this study, we discussed the effects of software complexity on the quality attributes of the software for open source and closed source software. Though, the quality metrics for open and closed source software are not distinct from each other. In this paper, we comparatively analyzed the impact of complexity metrics on open source and private software. We also presented various models for the management of the project complexity such as William’s Model, Stacey’s Agreement and Certainty matrix, Kahane’s Approach and UCP Model. Quality metrics here refer to the standards for the measurement of the quality of software which contains certain attributes or characteristics of the software that are related to the quality of the software. Certain quality attributes addressed in this study are Usability, Reliability, Security, Portability, Maintainability, Efficiency, Cost, Standards and Availability, etc. Both Open source and Closed source software are evaluated on the basis of these quality attributes. This study also recommended future approaches to manage the quality of project Open source and Closed source software and specify which one of them is mostly used in the industry.

show abstract

“…The factors which will be used for the initial version of the scale have been taken from prior research into project failure which focussed on factor analysis. In particular the leadership competence construct is been drawn from the work of Englebrecht, Johnston and Hooper (2017), while the software project complexity measures are being informed, principally, by the work of Fitsilis and Damasiotis (2015).…”

Section: Testing Situational Incompetencementioning

confidence: 99%

Situational Incompetence: The Failure of Governance in the Management of Large Scale IT Projects

Carlton

Peszynski

2018

Smart Working, Living and Organising

View full text Add to dashboard Cite

Information technology (IT) projects in the government (public) sector experience significant challenges. Despite decades of research, the adoption of formal methods, the use of external suppliers and packaged software, these remediation attempts have not appeared to have reduced nor mitigated the problems faced when the public sector undertakes large IT projects. Previous studies have examined the causes of IT project failure, in particular these have focused on factor analysis. A relatively limited number of studies have investigated the contribution of IT competence, and even fewer have considered the role and contribution of non-IT executives in IT project outcomes. This study sought a deeper understanding of what drives the behaviour of large scale IT projects. Of particular note was the finding by Kruger and Dunning (2008) that 'the skills required to do the job are the same skills needed to identify competence in others'. It was this finding which was found to most influence the observed behaviours of executive leadership leading to IT project failure.This research reports on a qualitative study that investigated 181 interviews and 5,000 pages of project data drawn from a large-scale public sector IT project which resulted in a cost overrun that exceeded AUD$1 Billion. The interview transcripts and project data were analysed using an inductive case study methodology and the research process was influenced by aspects of Grounded Theory.A new Theory of Situational Incompetence has been developed as a result of the analysis. The research culminates in a proposed measurement instrument intended to gauge leadership competence in the context of increasing project size and complexity.

show abstract

Software Project’s Complexity Measurement: A Case Study

Cited by 8 publications

References 10 publications

An Enhanced Framework for Effort Estimation of Agile Projects

An Enhanced Framework for Effort Estimation of Agile Projects

A Comparitive Analysis Between Open Source And Closed Source Software in Terms of Complexity and Quality Factors

Situational Incompetence: The Failure of Governance in the Management of Large Scale IT Projects

Contact Info

Product

Resources

About