Nuno Santos

Derivation of process-oriented logical architectures: an elicitation approach for cloud design

The benefits of cloud computing approaches are well known but designing logical architectures for that context can be complicated. Prior to designing a logical architecture, a proper requirements elicitation must be executed. When requirements are not properly elicited, and there are insufficient inputs for a product approach to requirements elicitation, a process-level perspective is an alternative way for achieving the intended base requirements for the logical design. Our proposed solution regards the adaptation and extension of the 4SRS (Four-Step-Rule-Set) method to derive logical architectural models, in a process-level perspective. This perspective creates context for the product-level requirements elicitation conducing to cloud design. We present a real industrial case where the method was applied and assessed. The method application results in the creation of a validated architectural model and in the uncovering of hidden requirements for the intended cloud design.

A SoaML Approach for Derivation of a Process-Oriented Logical Architecture from Use Cases

Designing logical architectures for cloud computing environments can be a complex endeavor, moreover when facing ill-defined contexts or insufficient inputs to requirements elicitation. Existing solutions are no longer enough to embrace challenges brought by complex scenarios and multi-stakeholder realities, as in Ambient Assisted Living ecosystems. As new concepts and cross-domain solutions emerge, these problems are tackled by connecting evermore the world of requirements and architectures, of business and technology, through service-oriented approaches. This due, we propose to extend the Four-Step-Rule-Set (4SRS) method, which has proven successful in generating a proper candidate logical architecture for an information system in ill-defined contexts, to a Service-Oriented Architecture approach for greater business integration, flexibility, and agility, by using the SoaML language. We present the result of a demonstration project, based in an industrial live setting where the 4SRS-SoaML reshaped method was applied, by generating the architectural participants, and respective channels of services and requests.

A V-Model Approach for Business Process Requirements Elicitation in Cloud Design

The benefits of cloud computing approaches are well known but designing logical architectures for that context can be difficult. When there are insufficient inputs for a typical (product) approach to requirements elicitation, a process-level perspective is an alternative way for achieving the intended logical design. We present a V-Model based approach to derive logical architectural models to execute in the different cloud layers from a process-level perspective, instead of the traditional product-level perspective. This V-Model approach encompasses the initial definition of the project goals and the process-level perspective of the systems intended logical architecture. The approach application results in the creation of a validated process-level structure and behavior architectural models that create a context for eliciting requirements for a cloud product. Throughout this process, we assess our decisions based on the ARID method to identify process vulnerabilities and evaluate the quality of the derived logical architecture. We introduce a case study where our approach was applied and the resulting logical architectural model is presented.

Transition from Process- to Product-Level Perspective for Business Software

When there are insufficient inputs for a product-level approach to requirements elicitation, a process-level perspective is an alternative way for achieving the intended base requirements. We define a V+V process approach that supports the creation of the intended requirements, beginning in a process level perspective and evolving to a product-level perspective trough successive models derivation with the purpose of creating context for the implementation teams. The requirements are expressed through models, namely logical architectural models and stereotyped sequence diagrams. Those models alongside with the entire approach are validated using the architecture validation method ARID.

Delivering User Stories for Implementing Logical Software Architectures by Multiple Scrum Teams

In software projects, agile methodologies are based in small development cycles and in continuous communication with customers with low needs on modeling formalism for requirements elicitation and documentation. However, there are projects whose context requires formal modeling and documentation of requirements in order to raise and manage critical issues from the very beginning of the project, like architectural diagrams. This work presents an approach for deriving a list of User Stories using a logical architectural diagram as input. Derived User Stories are then delivered to multiple Scrum teams.

Aligning Domain-Related Models for Creating Context for Software Product Design

A typical software product is developed so that it can fulfill the specific needs (problem that needs to be solved) within a given business domain, based on a proper product design context. Although, assuring an alignment between the technological developments with the business domain is a demanding task. With the purpose of clarifying the relations between the models that support the business and the software representations, we present in this paper a V-Model based approach to align the business domain requirements with the context for product design. This V Model encompasses the models that support the initial definition of the project goals, expressed through organizational configurations, and the analysis and design of models that result in a process-level perspective of the system’s logical architecture. Our approach adopts a process-level perspective with the intent to create context for product-level requirement elicitation. We present a case study as a demonstration and assessment of the applicability of our approach. Since the case study is extremely complex, we illustrate how to use the ARID method to evaluate the obtained process-level architecture.

A Transformation of Business Process Models into Software-Executable Models Using MDA

Traditional software development projects for process-oriented organizations are time consuming and do not always guarantee the fulfillment of the functional requirements of the client organization, and thus the quality of the resulting software product. To reduce the time spent for developing software and improve its quality, we adopt the inclusion of automation in some parts of the software development process. Thus, in this paper, we propose a model transformation approach to derive an executable model for the business processes of a given organization. We execute a mapping between processes (described with a business process execution language) and software components. We also propose a supporting software architecture based on an Enterprise Service Bus and on Java Business Integration, and we use an already defined methodology to execute the model transformation project.

Using Scrum Together with UML Models: A Collaborative University-Industry R&D Software Project

Conducting research and development (R&D) software projects, in an environment where both industry and university collaborate, is challenging due to many factors. In fact, industrial companies and universities have generally different interests and objectives whenever they collaborate. For this reason, it is not easy to manage and negotiate the industrial companies’ interests, namely schedules and their expectations. Conducting such projects in an agile framework is expected to decrease these risks, since partners have the opportunity to frequently interact with the development team in short iterations and are constantly aware of the characteristics of the system under development. However, in this type of collaborative R&D projects, it is often advantageous to include some waterfall practices, like upfront requirements modeling using UML models, which are not commonly used in agile processes like Scrum, in order to better prepare the implementation phase of the project. This paper presents some lessons learned that result from experience of the authors in adopting some Scrum practices in a R&D project, like short iterations, backlogs, and product increments, and simultaneously using UML models, namely use cases and components.

iFloW: An Integrated Logistics Software System for Inbound Supply Chain Traceability

Visibility plays an important role in supply chain management. Such visibility is not only important for better planning, but especially for real-time execution related with the traceability of goods. In inbound supply chain management, logistics planners need to trace raw materials from their requests in order to properly plan a plant’s production. The iFloW (Inbound Logistics Tracking System) integrates logistics providers IT applications and Global Positioning System (GPS) technology to track and trace incoming freights. The Estimated Time of Arrival (ETA) is updated in real-time allowing an improved materials planning process. This paper presents the iFloW project and describes how these issues are addressed and validated in a real pilot project.

Using the NIST reference model for refining logical architectures

The emergence of the Internet as a ubiquitous means of communication fostered the growth of new business and service models based on Cloud Computing. Information and Communication Technology companies use reference models to define their Cloud Computing strategies. NIST Cloud Computing Reference Architecture is one of these reference models that assist in the design of business, services, and architecture models. This paper aims to present the use of NIST reference architecture in the design of Cloud Computing architectures by employing a method that enables the application of the reference architecture to the refinement of logical architectures.