scholarly journals Testing Non-Functional Requirements: Lacking of Technologies or Researching Opportunities?

2016 ◽  
Author(s):  
Victor V. Ribeiro ◽  
Guilherme H. Travassos
Keyword(s):  
Software Testing ◽  
Project Success ◽  
Software Project ◽  
Functional Requirements ◽  
Software Projects ◽  
Technical Literature ◽  
Body Of Knowledge ◽  
Insufficient Amount ◽  
Literature Reviews ◽  
And Performance

Software testing aims to reveal failures due to the lack of conformity (defects) among functional and non-functional requirements and the implemented system. Thus, defects can be identified and fixed, improving software quality. However, despite several works emphasizing the importance of non-functional requirements (NFRs), there is an insufficient amount of software testing approaches dealing with them. The lack of NFR evaluation may be the cause of low-quality software that does not meet users need, influencing software project success. Goal: To organize a body of knowledge regarding NFRs and software testing approaches available in the technical literature and reveal the gaps between testable NFRs and software testing approaches. Method: To perform structured literature reviews to identify NFRs and software testing approaches dealing with testable NFRs. To combine both results, reveal research opportunities and organize a body of knowledge regarding NFRs and software testing approaches. Results: From 224 identified NFRs, 87 were described, and 47 software testing approaches observed. Only eight approaches are empirically evaluated. No testing approaches were identified for 11 testable NFRs. Furthermore, regarding the testing process, we did not observe any testing approach covering the test planning phase. Conclusion: Despite their importance, many testable NFRs seem not be tested due to the lack of appropriate software testing approaches yet. Also, the existing testing approaches do not cover all testing processes activities and, in general, lack empirical evidence about their feasibility and performance, making their use in software projects risky.

scholarly journals Software Project Management Systems Using Kanban Method in the CV. Primavisi Globalindo

2020 ◽  
Vol 4 (2) ◽  
pp. 215-231
Author(s):  
Muhammad Aliyya Ilmi ◽  
Fajar Pradana ◽  
Widhy Hayuhardhika Nugraha Putra
Keyword(s):  
Project Management ◽  
Project Planning ◽  
Software Project ◽  
Unit Testing ◽  
Functional Requirements ◽  
Software Projects ◽  
Management Planning ◽  
Scheduling System ◽  
Usability Test ◽  
Project Management And Scheduling

Reducing the risk of failure in working on software projects is one of the successes for the company. It can be done by implementing project planning management properly. One important aspect of project management planning is scheduling. Scheduling includes recording human resources and tasks in the project. The Kanban method is one of the methods used to overcome problems in controlling project schedules. This study aims to develop a project scheduling system that applies the Kanban method. In this research, project management and scheduling system will be developed using the Kanban method. This system expected to be able to assist companies in handling projects. Kanban was chosen because it can easily respond to project changes, easily implemented, and company needs. In this study, unit testing was performed on the system's three main features and tested the validity of the system's 49 functional requirements. The usability test produces a value of 76. Based on the validation and usability test results, it can be concluded that the system is included in the acceptable category.

scholarly journals Proposed T-Model to cover 4S quality metrics based on empirical study of root cause of software failures

2019 ◽  
Vol 9 (2) ◽  
pp. 1122
Author(s):  
Dheeraj Chhillar ◽  
Kalpana Sharma
Keyword(s):  
Software Development ◽  
New Technologies ◽  
Software Project ◽  
Functional Requirements ◽  
Software Failures ◽  
Root Cause ◽  
Software Development Model ◽  
Software Development Methodologies ◽  
And Performance ◽  
Over Time

<span>There are various root causes of software failures. Few years ago, software used to fail mainly due to functionality related bugs. That used to happen due to requirement misunderstanding, code issues and lack of functional testing. A lot of work has been done in past on this and software engineering has matured over time, due to which software’s hardly fail due to functionality related bugs. To understand the most recent failures, we had to understand the recent software development methodologies and technologies. In this paper we have discussed background of technologies and testing progression over time. A survey of more than 50 senior IT professionals was done to understand root cause of their software project failures. It was found that most of the softwares fail due to lack of testing of non-functional parameters these days. A lot of research was also done to find most recent and most severe software failures. Our study reveals that main reason of software failures these days is lack of testing of non-functional requirements. Security and Performance parameters mainly constitute non-functional requirements of software. It has become more challenging these days due to lots of development in the field of new technologies like Internet of things (IoT), Cloud of things (CoT), Artificial Intelligence, Machine learning, robotics and excessive use of mobile and technology in everything by masses. Finally, we proposed a software development model called as T-model to ensure breadth and depth of software is considered while designing and testing of software. </span>

The Impact of Project Initiators on Open Source Software Project Success

2021 ◽  
pp. 221-238
Author(s):  
Ling Wang ◽  
Jinxiao Wang
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Collective Behaviors ◽  
Collective Wisdom ◽  
Open Source Software Project ◽  
Development Costs ◽  
Collaborative Innovation

This paper focuses on studying the role of open source software project initiator in affecting the OSS project success from the perspective of individual and collective behaviors. The authors collected the data from an emerging OSS hosting platform Gitee in China. This research indicates that the success mode for open source software projects in China relies a lot on the project initiators. Project initiators not only contribute codes to aid the project directly, but also use their social capital to facilitate the project success. But no full play has been given to social network's effect on mass production and collaborative innovation. The authors suggest collaborative innovation which could lead to coherence of global collective wisdom, reduced development costs, and expanded source of innovation should be the further direction for the OSS project in emerging platforms.

Engineering Model-Based Software Testing of WIMP Interactive Applications

2021 ◽  
Vol 5 (EICS) ◽  
pp. 1-30
Author(s):  
Alexandre Canny ◽  
Célia Martinie ◽  
David Navarre ◽  
Philippe Palanque ◽  
Eric Barboni ◽  
...  
Keyword(s):  
Software Testing ◽  
Formal Model ◽  
Interactive Software ◽  
User Centered Design ◽  
Functional Requirements ◽  
Interactive Applications ◽  
Model Based ◽  
Threats To Validity ◽  
Interactive Application ◽  
And Performance

The goal of software testing is to detect defects with the objective of removing them at a later stage in the development process. Interactive software development follows the User Centered Design approach that promotes continuous involvement of users both at design and evaluation phases. This process is meant to produce usable interactive software by gathering functional and non-functional requirements related to both user needs and context of use. However, taking into account these potentially very-complex-to-implement requirements increases the complexity of the software that is likely, without appropriate methods and tools, to encompass a large number of defects. One of the limitations of UCD approaches is that it provides no guidance on the engineering of the interactive application, which thus usually embeds numerous defects resulting in failures at the origin of user frustrations and performance drops. Even though a classification of interactive application defects has been proposed, interactive application testers remain only superficially supported in detecting them. This paper defines a model-based approach to engineer the testing activity for interactive applications. It proposes a process that bridges the gap between UCD artefacts and interactive software implementation by the production of a dedicated formal model exploited for testing purposes only. The application of the process is demonstrated on an interactive cockpit WIMP application. Finally, threats to validity (capability of the approach to detect defects and to ensure an acceptable coverage testing of the interactive application) are addressed by a longitudinal study on 61 variants of a simple application developed by 61 different developers. ?

Software Project Costing

2012 ◽  
Vol 3 (4) ◽  
pp. 72-86 ◽  
Author(s):  
Liran Edelist ◽  
Roy Gelbard ◽  
Jeffrey Kantor
Keyword(s):  
Organizational Context ◽  
Project Managers ◽  
Software Project ◽  
Maturity Model ◽  
Software Projects ◽  
Capability Maturity ◽  
Body Of Knowledge ◽  
Organizational Perspective ◽  
Proposed Model ◽  
Software Engineers

This study puts forward a generic and comprehensive costing framework for software projects that aims for simplicity. This is achieved by integrating commonly used CMMI (Capability Maturity Model Integration) and PMBOK (Project Management Body of Knowledge) costing concepts in a broader organizational context. The costing framework comprises three layers: costing targets, costing activities, and policy evaluation. While the first two layers are derived from commonly used software engineering elements, the third integrates an organizational perspective through software engineers, project managers, accountants and top management. Employment of CMMI and PMBOK standards allows for easy adoption of the proposed model by organizations that are already relying on these standards.

Adaptive and Dynamic Hybrid Model for Software Project Management: A Review on its Clarity and Usage to Improve Project Success

2019 ◽  
Vol 892 ◽  
pp. 38-45
Author(s):  
Marzanah A. Jabar ◽  
Norhayati Mohd. Ali ◽  
Yusmadi Yah Jusoh ◽  
Salfarina Abdullah ◽  
S. Mohanarajah
Keyword(s):  
Project Management ◽  
Software Development ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Software Developers ◽  
Effective Role ◽  
Software Development Methodologies ◽  
Dynamic Hybrid ◽  
Current Research Interest

Software developers have shown a lot of interest in using agile approaches and methods to manage projects. The Agile Manifesto in 2001 provided a good basis to use this as it formulated its 4 values and 12 principles. Adaptability was a common feature in the Agile Manifesto to make agility happen and there appears a need to combine dynamism to ensure agility takes a more concrete and effective role. Whilst the term adaptability is discussed more often than dynamism by most researchers, the clarity in its meaning needs improvement as the terms are used interchangeably. This paper proposes a useful clarity on its differences and how it should be used. In addition, this approach would also facilitate the current research interest in mixing and combining software development methodologies to create hybrid versions as pure methods (traditional and agile) have not worked well in most software projects.

scholarly journals La gestión ágil de proyectos de software en la formación Académica Universitaria: Una revisión sistemática de la literatura

2020 ◽  
pp. 8-21
Author(s):  
Luz María Hernández-Cruz ◽  
Margarita Castillo-Téllez ◽  
Diana Concepción Mex-Álvarez ◽  
José Ramón Cab-Chan
Keyword(s):  
Project Management ◽  
Project Success ◽  
Software Project ◽  
Effective Management ◽  
Software Projects ◽  
Scientific Publications ◽  
Agile Project Management ◽  
Revisión Sistemática ◽  
Basic Concepts ◽  
Agile Software

Agile project management is an iterative approach that allows you to plan and guide project processes that require special speed and flexibility to achieve project success. It is for this reason that today professionals must master the basic concepts of this work as disciplinary or professionalizing competence. The objective of the study lies mainly in compiling recent research, including the last three years, in relation to Agile Software Project Management, its current situation and its application in practice. The study shows the implementation of the methodology proposed by Kitchenham for the systematic literature review (RSL) analyzing 40 scientific publications, concluding that the agile management of software projects allows efficient and effective management with the application of a standard o priority methodology and with the unavoidable use of software tools of specific use for it.

The Impact of Project Initiators on Open Source Software Project Success

2020 ◽  
Vol 12 (1) ◽  
pp. 28-43
Author(s):  
Ling Wang ◽  
Jinxiao Wang
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Collective Behaviors ◽  
Collective Wisdom ◽  
Open Source Software Project ◽  
Collaborative Innovation ◽  
The Impact

This paper focuses on studying the role of open source software project initiator in affecting the OSS project success from the perspective of individual and collective behaviors. The authors collected the data from an emerging OSS hosting platform Gitee in China. This research indicates that the success mode for open source software projects in China relies a lot on the project initiators. Project initiators not only contribute codes to aid the project directly, but also use their social capital to facilitate the project success. But no full play has been given to social network's effect on mass production and collaborative innovation. The authors suggest collaborative innovation which could lead to coherence of global collective wisdom, reduced development costs, and expanded source of innovation should be the further direction for the OSS project in emerging platforms.

Identification and Quantitative Analysis of Project Success Factors for Large Scale Projects

2014 ◽  
Vol 5 (1) ◽  
pp. 83-95 ◽  
Author(s):  
Basit Shahzad ◽  
Abass Md Said
Keyword(s):  
Resource Allocation ◽  
Quantitative Analysis ◽  
Large Scale ◽  
Success Factors ◽  
Project Success ◽  
Research Area ◽  
Software Project ◽  
Software Projects ◽  
Open Research ◽  
Timely Completion

Software projects require a right mix of the software resources and the expertise to increase the chances of timely completion. The interface for the resource allocation to the software projects is provided by the project factors. The identification of the comprehensive project factors for the diversified nature of projects in itself is an open research area. This paper is based on a quantitative study that helps in identifying the prominent software project factors for large scale projects. The paper then, as a result provides a list of project success factors and provides the statistical evidence to support the result of the survey.

scholarly journals Rethinking success in software projects

Tehnika ◽  
2020 ◽  
Vol 75 (6) ◽  
pp. 639-645
Author(s):  
Zorica Mitrović ◽  
Dejan Petrović ◽  
Marko Mihić
Keyword(s):  
Literature Review ◽  
Software Development ◽  
Project Success ◽  
Three Dimensions ◽  
Development Projects ◽  
Software Project ◽  
Software Projects ◽  
Multidimensional Construct ◽  
Strategic Project ◽  
Clear Line

In recent years, one of the most important topics in the field of software development projects is rethinking success in context of increasing complexity and failure of software projects. Literature review shows that there is no clear line between success and failure, especially considering that a project can be both successful in one area and unsuccessful in another. In addition, the increasing complexity, context and broader conceptualization of projects, required both change in project and success definition. The aim of this paper is to perform literature review in field of software project success definition, as well as to propose a multidimensional construct that includes project management success, project success and strategic project success as three dimensions for measuring software's project success.

Sign in / Sign up

Export Citation Format

Share Document