A process modeling based method for identification and implementation of software development tool integration-tuples

Ertürkmen, K. Alpay
Software development is highly dependent on the use of tools. These tools support and automate activities performed in different sub-domains of software development. However, they don‘t adequately provide or support integration facilities, and act as ―islands of automation‖. This restricts their benefits to only specific parts of the process. To reap the benefits of integration, this thesis provides a process modeling based method named PLETIN to identify and implement software development tool integration-tuples. The method aims to present solutions for issues observed in tool integration for software development organizations by delivering an integrated tool set. The proposed solution approach is based on the idea that if there were no integrations between tools at all, users would perform the necessary actions to cooperate different tools. PLETIN is a method for the identification of the candidate integration situations (integration-tuples) from the interactions of users with the tools. These tuples constitute the requirements used to develop integration facilities. The software development process definitions are used as inputs to create process models and provide actual implementations. The research is supported with case-study work to identify the significance of the problems and the applicability of the method as a solution to issues in tool integration.


A unification model and tool support for software functional size measurement methods
Efe, Pınar; Demirörs, Onur; Department of Information Systems (2006)
Software size estimation/measurement has been the objective of a lot of research in the software engineering community due to the need of reliable size estimates. FSM Methods have become widely used in software project management to measure the functional size of software since its first publication, late 1970s. Although all FSM methods measure the functional size by quantifying the FURs, each method defined its own measurement process and metric. Therefore, a piece of software has several functional sizes ...
Software development in practice : a qualitative study in Turkish defense sector
Dilber, Başak; Özkan Yıldırım, Sevgi; Department of Information Systems (2013)
Since management is an abstract concept, modeling or simulating software development projects is not exactly possible. Thus successful software project development and the factors affecting it have been popular fields of research for the last half century. The aim of this qualitative grounded theory study is to bring out the essence of the experience of people working as software developers in a specific organization operating in Turkey; to come up with a set of principles explaining the main success factor...
Using collaboration diagrams in component oriented modelin
Tuncel, Mehmet Burhan; Doğru, Ali Hikmet; Department of Computer Engineering (2006)
Component Oriented Software Engineering (COSE) seems to be the future of software engineering. Currently, COSEML is the only modeling language that completely supports the COSE approach. Abstract decomposition of the system and their representing components are shown in a hierarchy diagram to support the COSE process model. In COSEML, only static modeling is supported through this single diagram. However, software is about behavior and static modeling is not sufficient to describe the system. The aim of thi...
Use of project similarity for software development time estimation
Taştekin, Semra Yilmaz; Bilgen, Semih; Erten, Murat; Department of Information Systems (2013)
Accurate development time estimation is crucial for project management in general, and critical for software intensive systems projects, in particular. Before beginning the project, little information is available for development details. Therefore, development time may not be estimated correctly. If data on previous projects in the same domain is available, this can be used for development time estimations. At the beginning of the project, requirements are defined and requirements specification document is...
Development of a library for automated verification of UML models
Çelik, Makbule Filiz; Koçyiğit, Altan; Department of Information Systems (2006)
Software designs are mostly modeled as Unified Modeling Language (UML) diagrams when object oriented software development is concerned. Some popular topics in the industry such as Model Driven Development, generating test cases automatically in the early phases of software development, automated generation of code from design model etc. use the benefits of UML designs. All of these topics have something in common which is the need for accuracy against the meta-model not to face problems in the latter phases...
Citation Formats
K. A. Ertürkmen, “A process modeling based method for identification and implementation of software development tool integration-tuples,” Ph.D. - Doctoral Program, Middle East Technical University, 2010.