scholarly journals TESTING PROCESS OVERVIEW EXPLORATION FOR A SOFTWARE PRODUCT IN A LARGE SOFTWARE DEVELOPMENT PROJECT

2013 ◽  
pp. 100-105
Author(s):  
SRIHARSHA G ◽  
NARESH E
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Project ◽  
Test Case ◽  
Test Cases ◽  
Software Development Project ◽  
Root Cause ◽  
Software Product ◽  
Large Software ◽  
Manual Test

Software testing is a process where you have the stated requirements, pre-requisite software that is to be installed and the configuration of the machine that need to be done as per the test data for the test case and for a specific platform which when verified works perfectly. This paper describes about Manual test case process overview in the testing life cycle for a large software development project and how you track the effort for the same. A Tester need to know about the fundamentals of testing concepts. Documentation of the testing concepts and the process overview of the testing life cycle for a software product need to be done initially so that a new tester when recruited can understand the basic flow as to how it is carried out in real time in an organization practically. Initially a tester need to execute the manual test case for few platforms and some tougher manual test cases need to be learnt from the tester who is having some experience. The tougher manual test cases need to be identified initially from the experienced tester who will be giving a session for the execution of such test cases. So when the foundation for a new tester is powerful the plan assigned for the execution of test cases is met. The effort tracking for the testing can be captured for a tester and should be matched with planned effort for the execution of test cases. Measurement of the testing effort plays a very important role as to how comfortable a new tester is and further root cause analysis is done if required when the new tester does not meet the planned effort.

scholarly journals Test Case Optimization and Redundancy Reduction Using GA and Neural Networks

2018 ◽  
Vol 8 (6) ◽  
pp. 5449
Author(s):  
Itti Hooda ◽  
R.S. Chhillar
Keyword(s):  
Neural Network ◽  
Software Development ◽  
Back Propagation ◽  
Development Project ◽  
Test Case ◽  
Development Effort ◽  
Test Cases ◽  
Back Propagation Algorithm ◽  
Software Development Project ◽  
State Chart

More than 50% of software development effort is spent in testing phase in a typical software development project. Test case design as well as execution consume a lot of time. Hence, automated generation of test cases is highly required. Here a novel testing methodology is being presented to test object-oriented software based on UML state chart diagrams. In this approach, function minimization technique is being applied and generate test cases automatically from UML state chart diagrams. Software testing forms an integral part of the software development life cycle. Since the objective of testing is to ensure the conformity of an application to its specification, a test “oracle” is needed to determine whether a given test case exposes a fault or not. An automated oracle to support the activities of human testers can reduce the actual cost of the testing process and the related maintenance costs. In this paper, a new concept is being presented using an UML state chart diagram and tables for the test case generation, artificial neural network as an optimization tool for reducing the redundancy in the test case generated using the genetic algorithm. A neural network is trained by the back-propagation algorithm on a set of test cases applied to the original version of the system.

scholarly journals Suppliers’ software development project start-up practices

2017 ◽  
Vol 10 (4) ◽  
pp. 880-896
Author(s):  
Helena Merikoski ◽  
Paula Savolainen ◽  
Jarmo J. Ahonen
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Project ◽  
Cycle Phase ◽  
Development Projects ◽  
Content Type ◽  
Business Context ◽  
Software Development Project ◽  
Business Goals ◽  
Start Up

Purpose The purpose of this paper is to present a life cycle phase of a software development project which is substantial for the success of the project. This paper visualizes the project start-up phase from suppliers’ perspective. Design/methodology/approach The method is a theory building from case studies. The data were collected from three software supplier firms by conducting process modeling separately in each firm. Findings The study resulted in a model of a supplier’s software project start-up which includes start-up practices and involved roles. The results indicate that project start-up is an integral and structured phase of project life cycle, which influences the execution of a software development project, especially from the supplier’s perspective in the project business context. Research limitations/implications The study focuses on the start-up phase of software development projects delivered to external customers. Therefore, developed project start-up model is applicable as such in software supplier firms. Practical implications The project start-up model presented in this paper indicates that project start-up is a complex and multi-dimensional activity in a supplier firm. This study suggests that if the project start-up phase is clearly defined, planned and followed in a supplier firm, it reduces confusion and miscommunication among the people involved in the project and helps to achieve the business goals of a project. Originality/value This study emphasizes that it is necessary to make a distinction between the perspectives of the customer and the supplier when studying projects in the project business context. The findings contribute the new knowledge for managing outsourced software development projects.

scholarly journals El Modelo del Análisis de Precios Unitarios Industrial adaptado a un Proyecto de Desarrollo de Software para un Producto de Informática / The Industrial analysis model of unitary prices adapted to a Software Development Project for a Software Product

2016 ◽  
Vol 4 (8) ◽  
pp. 86
Author(s):  
Cirilo Vega Magaña ◽  
Ivan Steve Vega Herrera
Keyword(s):  
Software Development ◽  
Development Project ◽  
Analysis Model ◽  
Software Development Project ◽  
Software Product

En el presente trabajo se analiza la factibilidad de realizar el cálculo y estimación de costo de un proyecto de personalización de un producto de software empleando técnicas de costeo del Análisis de Precios Unitarios utilizados en Ingeniería Industrial. Se contemplan los ajustes que se tendrían que hacer para poder utilizar el modelo de Análisis de Precios Unitarios, buscando las equivalencias de los conceptos usados en Ingeniería Industrial: maquinaria y equipo, materiales, mano de obra, jornada, etcétera, y aplicados a la ingeniería de software específicamente en proyectos de desarrollo y mantenimiento de software. Mediante un modelo simplificado obtenido a partir del análisis se verifica la viabilidad de usar el modelo de costeo comparándolo con cifras obtenidas a partir de las estimaciones generales que se hacen en informática en el mercado mexicano.

Survey on Prioritizing Test Cases in Various Levels of the Software Development Life Cycle

2021 ◽  
Vol 12 (1) ◽  
pp. 1-28
Author(s):  
Gayatri Nayak ◽  
Mitrabinda Ray
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Test Case ◽  
Test Cases ◽  
Test Case Prioritization ◽  
Research Gaps ◽  
Prioritization Process ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Conclusion Section

Test case prioritization is a technical method to reorder the execution of test cases to reduce regression testing costs. This paper has examined various existing techniques that are widely used and suggests improving test case prioritization process after finding many research gaps. These research gaps are collected after doing a thorough study on 206 papers after surfing 310 papers on test case generation and prioritization techniques. These papers are collected from different electronic databases such as IEEE Explore, Science Direct, ACM Library, Springer, Wiley, and Elsevier. The authors have targeted to make a statistical record to show research contribution on test case prioritization at three levels of software development life cycle. This survey shows that 20.87% of papers are contributing for TCP at the requirement phase, 38.83% of papers are contributing for TCP at the design phase, 40.29% of papers are contributing to TCP at the coding phase. The inference of this study cites many future recommendations for the current researchers in the conclusion section.

A Comparison of Software Product Line Traceability Approaches from End-to-End Traceability Perspectives

2014 ◽  
Vol 24 (04) ◽  
pp. 677-714 ◽  
Author(s):  
Jingyu Kim ◽  
Sungwon Kang ◽  
Jihyun Lee
Keyword(s):  
Software Development ◽  
Software Product Line ◽  
Development Project ◽  
Product Line ◽  
Future Research ◽  
Research Directions ◽  
Software Development Project ◽  
Software Traceability ◽  
Software Product ◽  
End To End

Software traceability is the ability to provide trace information on requirements, design, and implementation of a system. It helps stakeholders understand the many associations of software artifacts created during a software development project. End-to-end traceability refers to linkage of all artifacts in the entire lifecycle of a software development project. Its goal is to provide stakeholders of the software development with trace information in order to analyze impacts due to changes in a software system. Compared to that of a single product, the end-to-end traceability of software product line is more complicated because Software Product Line Development (SPLD) requires two separate but intimately related phases of domain engineering and application engineering. Various SPLD traceability approaches have been proposed in the past. However, thus far no research work on SPLD traceability has focused on SPLD end-to-end traceability. This paper defines SPLD end-to-end traceability and evaluates the existing SPLD traceability approaches from SPLD end-to-end traceability perspectives. We surveyed studies on SPLD traceability methods, traceability mechanisms used in major SPLD approaches, and software traceability survey papers. We compared the existing SPLD traceability approaches based on Systematic Literature Review (SLR). Through the survey, we found that none of the SPLD traceability studies fully supports SPLD end-to-end traceability, and there are unexplored research areas of SPLD end-to-end traceability in the existing SPLD traceability studies. The contribution of this paper is that it presents future research directions that give research guidelines for each unexplored research area in SPLD end-to-end traceability. Finally, based on the research directions, this paper suggests future research opportunities for SPLD end-to-end traceability.

Considerations in Planning and Managing a Large Software Development Project

2014 ◽  
Author(s):  
Dave C. Milton
Keyword(s):  
Software Development ◽  
Development Project ◽  
Legacy Systems ◽  
Vendor Selection ◽  
Software Development Project ◽  
Original Plan ◽  
New Business ◽  
Large Software ◽  
And Training

While the pipeline industry is no stranger to complex and expensive projects, the unique characteristics of a truly large software development project require a special set of considerations. Many companies are finding themselves undertaking such a project in order to manage growth, achieve efficiencies, adjust to a new business driver, or simply to replace aging legacy systems. Without the proper attention to topics such as vendor selection, off-shore resourcing, the role of the internal IT shop, testing and training, these projects are almost sure to cost more, take longer and under deliver benefits compared to the original plan and justification.

scholarly journals A STEP TOWARDS LIGHT—LIFE CYCLE GLOBAL HYPERTEXT

1994 ◽  
Vol 05 (05) ◽  
pp. 765-766
Author(s):  
JULIAN BUNN ◽  
PAOLO PALAZZI ◽  
BERTRAND ROUSSEAU ◽  
MATTHIEW SMITH
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Source Code ◽  
Information Access ◽  
Development Project ◽  
Requirements Specification ◽  
Software Life Cycle ◽  
Analysis And Design ◽  
Software Development Project ◽  
Specification Analysis

Life Cycle Global HyperText offers easier information access to all members of a software development project, with all documents resulting from the software life cycle being available through WWW hypertext. These documents are connected, via hypertext links, to the documents produced in other stages of the life cycle. To experiment with this concept we have developed converters that transform several kind of documents into the WWW format. Up to now we have focused on source code, but we are now concentrating on documents produced in earlier stages of the software life cycle, such as requirements specification, analysis and design.

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.

Knowledge Management and Quality Control in Software Outsourcing Projects

2017 ◽  
Vol 13 (4) ◽  
pp. 31-55 ◽  
Author(s):  
Rajorshi Sen Gupta
Keyword(s):  
Quality Control ◽  
Knowledge Management ◽  
Intellectual Property ◽  
Software Development ◽  
Service Providers ◽  
Economic Incentives ◽  
Development Project ◽  
Apparent Paradox ◽  
Software Development Project ◽  
Lump Sum

This article describes how entrepreneurs face critical risks in terms of quality control and knowledge management while outsourcing software development to independent service providers. First, it is recommended that lump-sum payment contracts should be avoided since software development project involves uncertainty. Instead, a variable payment contingent on observed quality can induce the service provider to exert optimal effort on the project. Second, entrepreneurs must not overlook the importance of providing economic incentives. They can protect their intellectual property by withholding critical knowledge and paying information rents in terms of higher than market wages to the service providers. Third, a startling result is that a low wage nation is not necessarily the optimal location to outsource software development projects. Thus, high wage-strong IPR nations might be chosen instead of low wage-weak IPR nations. Finally, the article explains the apparent paradox that software projects are often outsourced to locations that are characterized by weak intellectual property rights regime and high propensity of imitation.

Sign in / Sign up

Export Citation Format

Share Document