Enforcing Modeling Guidelines in an ORDBMS-based UML-Repository

2011 ◽  
pp. 150-162
Author(s):  
N. Ritter ◽  
H.P. Steiert
Keyword(s):  
Software Development ◽  
Design Method ◽  
Unified Modeling Language ◽  
Development Project ◽  
Database Management System ◽  
Tool Support ◽  
Automated Mapping ◽  
Software Development Project ◽  
Object Relational ◽  
Uml Models

Due to its rich set of modeling concepts and its broad application spectrum the Unified Modeling Language (UML) has become widely accepted for modeling many aspects of software systems. Since UML is not related to any particular design method, each software development project has to establish its own modeling guidelines. Hence, tool support is needed for guiding the developer throughout the modeling process and for enforcing project-related integrity of UML models. In this chapter, we present our approach for enforcing guidelines in UML-based software development processes. For managing UML models, we implemented a UML repository on top of an object-relational database management system (ORDBMS). Guidelines are expressed as OCL constraints and are enforced either automatically, i. e., by the UML repository, or on user demand. For this purpose, we take advantage of ORDBMS query facilities for checking guidelines by automated mapping of OCL constraints to SQL expressions.

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.

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.

Making Agile Development and Offshoring Practice Successful on Global Software Development Project

2013 ◽  
pp. 107-119
Author(s):  
Edward Chen
Keyword(s):  
Software Development ◽  
Development Project ◽  
Lessons Learned ◽  
Global Software Development ◽  
Agile Development ◽  
Business Practices ◽  
Global Business ◽  
Software Development Project ◽  
Business Applications ◽  
Develop Software

Two significant trends have been gaining momentum in software development: the utilization of Agile development methodologies, and the continuing trend of companies to outsource development work offshore. These two trends have changed the way companies develop software and business applications. This chapter seeks to evaluate how a company can successfully manage both trends in conjunction with each other on global business. The primary question addressed is whether the benefits derived from Agile development methodologies and the savings from outsourced software development efforts cancel each other out when applied together, or whether they create a synergy greater than the sum of the parts. In order to answer this question, this chapter intends to examine several relevant business practices and industry experiences. From lessons learned, we identify factors which seem to influence a successful combination of Agile methodology and offshoring in global software development projects.

Managing Software Projects with Team Software Process (TSP)

2013 ◽  
pp. 84-117
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor
Keyword(s):  
Project Management ◽  
Software Development ◽  
Management Practices ◽  
Software Process ◽  
Development Project ◽  
Software Projects ◽  
Engineering Teams ◽  
Software Development Project ◽  
Software Failure ◽  
Team Software Process

Despite the widespread use of sound project management practices and process improvement models over the last several years, the failure of software projects remains a challenge to organisations. As part of the attempt to address software industry challenges, several models, frameworks, and methods have been developed that are intended to improve software processes to produce quality software on time, under budget, and in accordance with previously stipulated functionalities. One of the most widely practised methods is the Team Software Process (TSP). The TSP was designed to provide an operational framework for establishing an effective team environment and guiding engineering teams in their work. This chapter provides an overview of the TSP and its associated structures and processes. It also highlights how the TSP operational framework can assist project manager and software development team to deliver successful projects by controlling and minimizing the most common software failure factors. Comparative analysis between the TSP and conventional project management has also been presented. Additionally, the results of TSP implementation in industrial settings are highlighted with particular reference to scheduling, quality, and productivity. The last section indicates additional advantages of TSP and comments on the future of TSP in the global software development project.

Sign in / Sign up

Export Citation Format

Share Document