Migration of Persistent Object Models Using XMI

2011 ◽  
pp. 92-104
Author(s):  
Rainer Fromming ◽  
Andreas Rausch
Keyword(s):  
Software Development ◽  
Software Process ◽  
Product Distribution ◽  
Object Model ◽  
Customer Requirements ◽  
Production Environment ◽  
Software Production ◽  
The Difference ◽  
Object Models

Embrace the change! Change is a constant reality of software development, a reality that must be reflected in not only our software process but also our software production environment. With ever-changing customer requirements, modifications to the object model are required during software development as well as after product distribution. The associated migration of existing persistent object data is a nontrivial problem. This chapter presents the conceptualization and implementation of a tool for the automated migration of persistent object models. The migration is controlled by an XMI-based description of the difference between the old and the new object model. Both, the schema and the data of the persistent object model are migrated efficiently and reliably.

Cuspe: propuesta ágil para la construcción de software basada en TSP [Cuspe: Agile approach for software development based on TSP]

2014 ◽  
Author(s):  
Giovanni Hernández ◽  
Álvaro Martínez
Keyword(s):  
Software Development ◽  
Analytical Approach ◽  
Work Teams ◽  
Software Process ◽  
Software Production ◽  
Palabras Clave ◽  
Agile Approach ◽  
Team Software Process ◽  
Agile Software ◽  
Progress Measurement

Resumen El objetivo principal de este artículo es aportar a la forma de trabajo de las empresas de la industria de software en Nariño mediante una propuesta metodológica ágil basada en Team Software Process (TSP). Este trabajo se desarrolló bajo el paradigma cuantitativo, con un enfoque empírico-analítico de tipo descriptivo-propositivo. La población objeto de estudio fueron las metodologías para construir software basada en equipos de trabajo, de las que se seleccionó de manera intencional TSP. Como resultado, se estableció que el nivel de agilidad que posee TSP corresponde al 79.25%. Así mismo, se diseñó Cuspe, como una propuesta para intervenir los principios del manifiesto ágil que presentan el menor nivel de cumplimiento en TSP. El trabajo permite concluir que la propuesta Cuspe basada en TSP logra incrementar el nivel de agilidad de la metodología y busca la entrega temprana y frecuente de software con valor, a través del trabajo y compromiso de personas motivadas; y consigue medir el progreso. Palabras Clave: Construcción de software, Manifiesto por el Desarrollo Ágil de Software, Team Software Process   Abstract The main goal of this article is to support Nariño’s’ Software industry’s way of work through a methodological proposal based on Team Software Process (TSP). This work was carried out under a quantitative paradigm and a descriptive-propositional-based empirical-analytical approach. The object populations were the methodologies for building software based on work teams, in which TSP was intentionally chosen. As a result, it was set that TSP’s level of agility reached 71.25%. Furthermore , It was designed Cuspe as an proposal in order to intervene the principles of the Agile Manifesto which shows the lowest level of accomplishment regarding TSP. This work allows concluding that the Cuspe proposal based on TSP increases the level of methodology’s agility and leads to an early and frequent valuable software production through the work and compromise of motivated people, and also progress measurement. Keywords: Manifest for Agile Software Development, Software Development, Team Software Process.

APPLYING EXPERT JUDGMENT TO IMPROVE AN INDIVIDUAL'S ABILITY TO PREDICT SOFTWARE DEVELOPMENT EFFORT

2012 ◽  
Vol 22 (04) ◽  
pp. 467-483 ◽  
Author(s):  
CUAUHTÉMOC LÓPEZ-MARTÍN ◽  
ALAIN ABRAN
Keyword(s):  
Software Development ◽  
Software Process ◽  
Development Effort ◽  
Academic Environment ◽  
Academic Institutions ◽  
Graduate Courses ◽  
Software Projects ◽  
Personal Software Process ◽  
Software Development Effort ◽  
Effort Prediction

Expert-based effort prediction in software projects can be taught, beginning with the practices learned in an academic environment in courses designed to encourage them. However, the length of such courses is a major concern for both industry and academia. Industry has to work without its employees while they are taking such a course, and academic institutions find it hard to fit the course into an already tight schedule. In this research, the set of Personal Software Process (PSP) practices is reordered and the practices are distributed among fewer assignments, in an attempt to address these concerns. This study involved 148 practitioners taking graduate courses who developed 1,036 software course assignments. The hypothesis on which it is based is the following: When the activities in the original PSP set are reordered into fewer assignments, the result is expert-based effort prediction that is statistically significantly better.

Review Product Distribution Through Different Channels

2021 ◽  
Vol 11 (4) ◽  
pp. 44-47
Author(s):  
Zhaoqiong Qin
Keyword(s):  
Product Distribution ◽  
Future Research ◽  
Direct Channel ◽  
Past Work ◽  
Work Related ◽  
Channel Competition ◽  
Physical Channel ◽  
The Future ◽  
The Difference

This study aims to investigate the literature in product distribution and channel competition. In this study, past work related to the product distribution through different channels is extensively reviewed. Based on the channel differentiation, channel competition is also reviewed. Finally, the study proposes that the future research may focus on helping the producer make a decision whether to sell the product through its own direct channel (online) through a physical channel or both based on the difference between these two channels.

An Evaluation of Software Development Practices among Small Firms in Developing Countries

2016 ◽  
Vol 24 (3) ◽  
pp. 45-70 ◽  
Author(s):  
Delroy Chevers ◽  
Annette M. Mills ◽  
Evan Duggan ◽  
Stanford Moore
Keyword(s):  
Developing Countries ◽  
Software Development ◽  
Process Improvement ◽  
Small Firms ◽  
Software Process ◽  
Software Process Improvement ◽  
Future Research ◽  
Capability Maturity ◽  
Software Product ◽  
Software Development Practices

For software development firms to be competitive they must assure the quality of the software product. This has led many firms to adopt software process improvement (SPI) programs such as the capability maturity model integration (CMMI). However, for small software firms, especially those in developing countries with limited resources, these programs are often too cumbersome and costly to implement. To address this issue, this paper proposes a simplified SPI model for small firms (SPM-S) comprised of 10 key software development practices; with fewer practices, the proposed model should be more accessible and less costly to implement. Using data collected in four developing countries in the English-speaking Caribbean from 112 developer/user dyads, the model is evaluated with respect to its impact on software quality. The findings show that the software development process coupled with supporting technology (e.g. project management tools) significantly impact software product quality. Implications for software process improvement in small firms and future research are discussed.

scholarly journals CMMI and Ideal in Software Process Improvement

2020 ◽  
Vol 17 ◽  
Keyword(s):  
Customer Satisfaction ◽  
Best Practices ◽  
Software Development ◽  
Process Improvement ◽  
Software Process ◽  
Software Process Improvement ◽  
Critical Factors ◽  
Development Processes ◽  
The Ideal

Different models and standards have been developed with the purpose of improving software development processes and obtaining quality products and achieving customer satisfaction. Despite the efforts that organizations make, they do not always achieve these results. In this article we present the results of the implementation of best practices established by the CMMI model using the IDEAL and SCAMPI B methodology. The results show that applying best practices helps organizations to improve their processes, minimize the number of defects and increase customer satisfaction. Likewise, the critical factors that were considered and aspects to be considered in the deployment of processes are presented.

Systematische Methodenauswahl bei der Digitalisierung/Systematic selection of methods for digitization projects – Leveraging established software development methods in the manufacturing industry

2020 ◽  
Vol 110 (04) ◽  
pp. 226-230
Author(s):  
Andreas Selmaier ◽  
Benedikt Martens ◽  
Martin Sjarov ◽  
Marlene Kuhn ◽  
Meike Herbert ◽  
...  
Keyword(s):  
Software Development ◽  
Manufacturing Industry ◽  
Project Planning ◽  
Production Environment ◽  
Software Projects ◽  
It Systems ◽  
Planning Methods ◽  
Systematic Selection ◽  
Iterative Procedures ◽  
Selection Of

Digitalisierungsprojekte sind Softwareprojekte. Sequenzielle Planungsmethoden, wie sie im konventionellen Projektmanagement überwiegend Anwendung finden, eignen sich nur bedingt für diesen Projekttyp, da die anwendungsspezifischen Anforderungen sowie die Abhängigkeiten der Anlagen und IT-Systeme untereinander zu einem erheblichen Anstieg der Gesamtkomplexität führen. In diesem Beitrag wird daher ein Ansatz zur systematischen Auswahl geeigneter Projektmanagementmethoden für Digitalisierungsprojekte vorgestellt, welcher die traditionelle Projektplanung im Produktionsumfeld um iterative Vorgehensweisen aus der Software- entwicklung ergänzt.   Digitalization projects are software projects. Less suitable for such projects are sequential planning methods often used in conventional project management, as application-specific requirements and interdependencies of facilities and IT systems considerably increase overall complexity. Therefore, this paper presents an approach for the systematic selection of suitable management methods for digitalization projects, which adds iterative procedures from software development to traditional project planning in the production environment.

Software Development Using Service Syndication based on API Handshake Approach between Cloud-Based and SOA-Based Reusable Services

2014 ◽  
pp. 1878-1899
Author(s):  
Vishav Vir Singh
Keyword(s):  
Software Development ◽  
Inflection Point ◽  
Application Programming Interface ◽  
Turnaround Time ◽  
Business Services ◽  
Software Production ◽  
Quantum Leap ◽  
Application Programming ◽  
Software Execution ◽  
Programming Interface

Reusability in the software development realm is a momentous cornerstone in deciding the success of an organization. The quantum leap in reusability was provided by object-orientation, which fundamentally altered the manner of thinking of software architects. The notion of the object and the installation of reusability as one of the central tenets is a critical requisite. Components that represented bigger and better software aggregates easily utilized by businesses to gain instant execution for their business services have made great strides. This gave way to the ultimate notion of a service which took software aggregates in components to fine and sharpened streams of software execution called services. This has been another inflection point in the overall curve of reusability, and most importantly, in agility and turnaround time for software production. The notion of services mandated the birth of a secure and trusted public interface to a service, which is called the Application Programming Interface (API). APIs represent a directory of services that a given enterprise offers.

Sign in / Sign up

Export Citation Format

Share Document