Modelling Security and Trust with Secure Tropos

2008 ◽  
pp. 981-1005
Author(s):  
P. Giorgini ◽  
H. Mouratidis ◽  
N. Zannone

Although the concepts of security and trust play an important issue in the development of information systems, they have been mainly neglected by software engineering methodologies. In this chapter, we present an approach that considers security and trust throughout the software development process. Our approach integrates two prominent software engineering approaches, one that provides a security-oriented process and one that provides a trust management process. The result is the de-velopment of a methodology that considers security and trust issues as part of its development process. Such integration represents an advance over the current state of the art by providing the ?rst effort to consider security and trust issues under a single software engineering methodology. A case study from the health domain is employed to illustrate our approach.

Author(s):  
P. Giorgini ◽  
H. Mouratidis ◽  
N. Zannone

Although the concepts of security and trust play an important issue in the development of information systems, they have been mainly neglected by software engineering methodologies. In this chapter, we present an approach that considers security and trust throughout the software development process. Our approach integrates two prominent software engineering approaches, one that provides a security-oriented process and one that provides a trust management process. The result is the de-velopment of a methodology that considers security and trust issues as part of its development process. Such integration represents an advance over the current state of the art by providing the ?rst effort to consider security and trust issues under a single software engineering methodology. A case study from the health domain is employed to illustrate our approach.


Author(s):  
Marcello Chedid ◽  
Leonor Teixeira

Software development organization (SDO) is a kind of knowledge-intensive business and their large majority is small and medium enterprise (SME) facing similar challenges of large ones. The diversity and complexity of the SDO environment makes knowledge the fundamental element in the software development process, which strengthens the importance of an effective knowledge management process. The software development process involves multidisciplinary teams, and the various working meetings that occur during a project are conducive to generate and share a lot of knowledge, in particular tacit knowledge. The use of a knowledge management process that enables to manage tacit knowledge will define the difference between a good SDO performance and the best SDO performance. This chapter aims to present an exploratory study based on literature review, with the aim of identifying the main challenge of knowledge management in the SDO context. The authors also aim to address some new research directions.


Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  

The quality in software projects is related the deliveries that are adjusted to the use, and that they take care of to the objectives. In this way, Brazilian organizations of software development, especially the small and medium ones, need to demonstrate to future customers whom an initial understand of the business problem has enough. This chapter has as objective to demonstrate methodology, strategy, main phases and procedures adopted beyond the gotten ones of a small organization of development of software in the implantation of a Customized Software Engineering Process and of a Tool of Support to the Process in the period of 2004 to 2006 on the basis of rational unified process (RUP) and in the Microsoft solutions framework (MSF).


Author(s):  
Petraq Papajorgji ◽  
Panos M. Pardalos

This chapter aims to present a new modeling paradigm that promises to significantly increase the efficiency of developing enterprise information systems. Currently, the software industry faces considerable challenges as it tries to build larger, more complex, software systems with fewer resources. Although modern programming languages such as C++ and Java have in general improved the software development process, they have failed to significantly increase developer’s productivity. Thus, developers are considering other paths to address this issue. One of the potential paths is designing, developing and deploying enterprise information systems using the Model Driven Architecture (MDA). MDA is a model-centric approach that allows for modeling the overall business of an enterprise and capturing requirements to developing, deploying, integrating, and managing different kinds of software components without considering any particular implementation technology. At the center of this approach are models; the software development process is driven by constructing models representing the software under development. Code that expresses the implementation of the model in a certain underlying technology is obtained as a result of model transformation. Thus, the intellectual investment spent in developing the business model of an enterprise is not jeopardized by the continuous changes of the implementation technologies. Currently there are two main approaches trying to implement MDA-based tools. One of the approaches is based on the Object Constraint Language and the other on Action Language. An example of designing, developing and deploying an application using this new modeling paradigm is presented. The MDA approach to software development is considered as the biggest shift since the move from Assembler to the first high level languages.


Author(s):  
Mirna Muñoz

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.


Author(s):  
Andreza Vieira ◽  
Franklin Ramalho

The Model-Driven Development (MDD) approach shifts the focus on code to models in the software development process. In MDD, model transformations are elements that play an important role. MDD-based projects evolve along their lifecycle in a way that changes in their transformations are frequent. Before applying changes it is important to measure their impacts within the transformation. However, currently no technique helps practitioners in this direction. We propose an approach to measure the change impact in ATL model transformations. Based on static analysis, it detects the elements impacted by a change and calculates the change impact value through three metrics we defined. By using our approach, practitioners can (i) save effort and development time since the elements impacted with the change are automatically detected and (ii) better schedule and prioritize changes according to the impact value. To empirically evaluate our approach we conducted a case study.


2019 ◽  
Author(s):  
Alexandra Terrill ◽  
Justin J. MacKenzie ◽  
Maija Reblin ◽  
Jackie Tyne Einers ◽  
Jesse Ferraro ◽  
...  

BACKGROUND Individuals with disability and their partners, who often provide care, are both at risk for depression and lower quality of life. Mobile health (mHealth) interventions are promising to address barriers for mental health care. Rehabilitation researchers and software development researchers must collaborate effectively with each other, and with clinical and patient stakeholders to ensure successful mHealth development. OBJECTIVE To aid researchers interested in mHealth software development by describing the collaborative process between a team of rehabilitation researchers, software development researchers, and stakeholders. Thus, we provide a framework (conceptual model) for other teams to replicate in order to build a web-based mHealth app for individuals with physical disability. METHODS Rehabilitation researchers, software development researchers, and stakeholders (people with physical disabilities and clinicians) are involved in an iterative software development process. The overall process to develop an mHealth intervention includes initial development meetings and a co-design method called “designbox”, in which the needs and key elements of the app are discussed. Based on the objectives outlined, a prototype is developed and goes through scoping iterations with feedback from stakeholders and end-users. The prototype is then tested by users to identify technical errors and gather feedback on usability and accessibility. RESULTS Illustrating the overall development process, we present a case study based on our experience developing an app (SupportGroove) for couples coping with spinal cord injury. Examples of how we addressed specific challenges are also included. For example, feedback from stakeholders resulted in development of app features for individuals with limited functional ability. Initial designs lacked accessibility design principles made visible by end-users. Solutions included large text, single-click, and minimal scrolling to facilitate menu navigation for individuals using eye-gaze technology. Prototype testing allowed further refinement and demonstrated high usability and engagement with activities in the app. Qualitative feedback indicated high levels of satisfaction, accessibility, and confidence in potential utility. We also present key lessons learned about working in a collaborative interdisciplinary team. CONCLUSIONS mHealth promises to help overcome barriers to mental health intervention access. However, the development of these interventions can be challenging because of the disparate and often siloed expertise required. By describing the mHealth software development process and illustrating it with a successful case study of rehabilitation researchers, software development researchers, and stakeholders collaborating effectively, our goal is to help other teams avoid challenges we faced and benefit from our lessons learned. Ultimately, good interdisciplinary collaboration will benefit individuals with disabilities and their families. CLINICALTRIAL n/a


Sign in / Sign up

Export Citation Format

Share Document