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.

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.

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 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.

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.

scholarly journals Modeling Relational Events: A Case Study on an Open Source Software Development Project

2012 ◽  
Vol 2012 (1) ◽  
pp. 11233
Author(s):  
Eric Quintane ◽  
Marco Tonellato ◽  
Guido Conaldi ◽  
Alessandro Lomi
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Development Project ◽  
Open Source Software Development ◽  
Software Development Project

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.

Sign in / Sign up

Export Citation Format

Share Document