Design and Implementation of Software Engineering Developed Process Models

An Analysis is done of the traditional software life cycle models that are used in the field and current software development practices. It then gives a more in-depth look at the traditional models of software evolution that are used a lot and are thought of as the best way to organize software engineering projects and technologies. There are so many things that go into making software that it's hard to think of a single process model that would work for all projects. This study, however, came up with a generalized model that could help companies make good software. A general goal for evaluation, which means to think about or think about how important it is, is shown. Examining current practices, confirming theories, exploring when the subject isn't well understood, and describing the current state of things are all part of the general evaluation goals. Evaluation helps predict the future and explain why things or sequences are taking place, so it is important to do it. It is important to know about both the software process and what the software does. With this evaluation, we can figure out how to evaluate it

Process-based Software Tweaking with Mobile Agents

We describe an approach based upon software process technology to on-the-fly monitoring, redeployment, reconfiguration, and in general adaptation of distributed software applications, in short 'software tweaking'. We choose the term tweaking to refer to modifications in structure and behavior that can be made to individual components, as well as sets thereof, or the overall target system configuration, such as adding, removing or substituting components, while the system is running and without bringing it down. The goal of software tweaking is manifold: supporting run-time software composition, enforcing adherence to requirements, ensuring uptime and quality of service of mission-critical systems, recovering from and preventing faults, seamless system upgrading, etc. Our approach involves dispatching and coordinating software agents - named Worklets - via a process engine, since successful tweaking of a complex distributed software system often requires the concerted action of multiple agents on multiple components. The software tweaking process must incorporate and decide upon knowledge about the specifications and architecture of the target software, as well as Worklets capabilities. Software tweaking is correlated to a variety of other software processes - such as configuration management, deployment, validation and evolution - and allows to address at run time a number of related concerns that are normally dealt with only at development time

Processo de evolução colaborativo de guias de referência de software

Dissertação (mestrado) - Universidade Federal de Santa Catarina, Centro Tecnológico. Programa de Pós-Graduação em Ciência de Computação.Na melhoria de processos de software, guias de referência podem fornecer um apoio sobre como definir um modelo específico de processo em uma organização, alinhado aos modelos genéricos de referência, como: ISO / IEC 15504, CMMI e MPS.BR. Tais guias de referência indicam diversas alternativas quanto à forma de estabelecerem as melhores práticas em diferentes ambientes organizacionais, descrevendo vários métodos, técnicas e ferramentas e indicando em que contexto cada uma destas é aplicável. No entanto, o desenvolvimento e a atualização de tais guias de referência não são tarefas triviais e representam um esforço contínuo e colaborativo. Portanto, este trabalho apresenta um processo para a evolução contínua e colaborativa de guias de referência. Este processo é aplicado e avaliado, onde o resultado da avaliação consiste em um primeiro indício de que a utilização do processo de evolução colaborativo pode facilitar a atualização contínua de guias de referência. Software process improvement reference guides can provide a support on how to define organization specific process models in alignment with generic software process reference models, such as, ISO/IEC 15504, CMMI or MPS.BR. Such reference guides describe various methods, techniques and tools and indicate in which context each of them is applicable. Yet, the development and update of reference guides is not trivial and represents a collaborative and continuous effort. Therefore, a process for the continuous and collaborative evolution of such reference guides is described in this thesis. This process was implemented and evaluated, and the assessment results provide a first indication that the use of the collaborative development of reference guides can facilitate the continuous updating of the reference guides

Orchestrating the Dynamic Adaptation of Distributed Software with Process Technology

Software systems are becoming increasingly complex to develop, understand, analyze, validate, deploy, configure, manage and maintain. Much of that complexity is related to ensuring adequate quality levels to services provided by software systems after they are deployed in the field, in particular when those systems are built from and operated as a mix of proprietary and non-proprietary components. That translates to increasing costs and difficulties when trying to operate large-scale distributed software ensembles in a way that continuously guarantees satisfactory levels of service. A solution can be to exert some form of dynamic adaptation upon running software systems: dynamic adaptation can be defined as a set of automated and coordinated actions that aim at modifying the structure, behavior and performance of a target software system, at run time and without service interruption, typically in response to the occurrence of some condition(s). To achieve dynamic adaptation upon a given target software system, a set of capabilities, including monitoring, diagnostics, decision, actuation and coordination, must be put in place. This research addresses the automation of decision and coordination in the context of an end-to-end and externalized approach to dynamic adaptation, which allows to address as its targets legacy and component-based systems, as well as new systems developed from scratch. In this approach, adaptation provisions are superimposed by a separate software platform, which operates from the outside of and orthogonally to the target application as a whole; furthermore, a single adaptation possibly spans concerted interventions on a multiplicity of target components. To properly orchestrate those interventions, decentralized process technology is employed for describing, activating and coordinating the work of a cohort of software actuators, towards the intended end-to-end dynamic adaptation. The approach outlined above, has been implemented in a prototype, code-named Workflakes, within the Kinesthetics eXtreme project investigating externalized dynamic adaptation, carried out by the Programming Systems Laboratory of Columbia University, and has been employed in a set of diverse case studies. This dissertation discusses and evaluates the concept of process-based orchestration of dynamic adaptation and the Workflakes prototype on the basis of the results of those case studies

A decentralized architecture for software process modeling and enactment

The Serendipity-II process management environment supports distributed process modeling and enactment for distributed software development projects. Serendipity-II is based on a decentralized architecture and uses Internet communication facilities