C-SCRIP: Collaborative Security Pattern Integration Process

C-SCRIP: Collaborative Security Pattern Integration Process

Rahma Bouaziz (Department of Computer Science, Taibah University, Al-Madina Al-Munawarah, Saudi Arabia & ReDCAD, University of Sfax, Sfax, Tunisia), Fatma Krichen (ReDCAD, University of Sfax, Sfax, Tunisia) and Bernard Coulette (IRIT, University of Toulouse, Toulouse, France)
DOI: 10.4018/IJITWE.2015010102
OnDemand PDF Download:
No Current Special Offers


Collaboration is the act of working together, towards a common goal. Collaboration is essential to the success of construction project. In software engineering projects, understanding and supporting collaboration gives the broad impact on product quality. There appears that it is difficult to effectively interact and achieve a common project goals within the bounds of cost, quality and time. The purpose of the paper is to propose a collaborative engineering process, called Collaborative SeCurity patteRn Integration Process (C-SCRIP), and a tool that supports the full life-cycle of the development of a secure system from modeling to code.
Article Preview


New technologies have emerged during the last decade, such as patterns, model driven engineering and component-based approach. All these technologies have the same common objective that is to facilitate the construction and understanding of software systems. They operate at different levels of abstraction from the general architecture of the system until its implementation. We give below a brief overview of these three technologies.

Component Based Software Engineering

CBSE (Szyperski, 2002) allows building large systems by assembling reusable components. It is a good solution to optimize the time and cost of software design while still guaranteeing the quality of the software (Brown & Wallnau, 1998). Usually, a component is seen as a black box that provides and requires services through its interfaces. Modeling component-based applications consists in describing components, their required and offered services and then describes component instances and finally how these instances are connected to form the final system. At the specification level a system is described as a static interconnection of software components. At runtime a component assembly is an instantiation of an architecture composed of linked component instances.

Complete Article List

Search this Journal:
Volume 17: 4 Issues (2022): 1 Released, 3 Forthcoming
Volume 16: 4 Issues (2021)
Volume 15: 4 Issues (2020)
Volume 14: 4 Issues (2019)
Volume 13: 4 Issues (2018)
Volume 12: 4 Issues (2017)
Volume 11: 4 Issues (2016)
Volume 10: 4 Issues (2015)
Volume 9: 4 Issues (2014)
Volume 8: 4 Issues (2013)
Volume 7: 4 Issues (2012)
Volume 6: 4 Issues (2011)
Volume 5: 4 Issues (2010)
Volume 4: 4 Issues (2009)
Volume 3: 4 Issues (2008)
Volume 2: 4 Issues (2007)
Volume 1: 4 Issues (2006)
View Complete Journal Contents Listing