Nuno Santos

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… Exibir mais

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. Exibir menos

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… Exibir mais

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. Exibir menos

In the end of a requirements elicitation phase, it is expectable that all information can be properly perceived by the implementation teams. In our work, we faced the problem of dealing with a large set of requirements that need to be implemented by different teams, to ensure on-time delivery. The teams are physically separated and with different working cultures and skills. The system requirements were (semi )automatically derived from user requirements, are framed within a logical… Exibir mais

In the end of a requirements elicitation phase, it is expectable that all information can be properly perceived by the implementation teams. In our work, we faced the problem of dealing with a large set of requirements that need to be implemented by different teams, to ensure on-time delivery. The teams are physically separated and with different working cultures and skills. The system requirements were (semi )automatically derived from user requirements, are framed within a logical architecture (of the intended system) and the desired high-level execution scenarios are defined and included in the requirements description. Due to the large size of the architecture and to the nature of the working environment, the architecture must be divided before being delivered. In this paper, we present our approach for dividing the logical architecture of the intended system into modules to be delivered for implementation. The division in constructed upon requirement views that provide information about the modules, their interfaces, the intended execution scenarios, and the interfaces with other modules or systems. The approach is evaluated using the ISOFIN project. Exibir menos

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… Exibir mais

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. Exibir menos

At the analysis phase of an enterprise information system development, the alignment between the process level requirements (information systems) with the product level requirements (software system) may not be properly achieved. Modeling the processes for the enterprise’s business is often insufficient for implementation teams, and implementation requirements are often misaligned with business and stakeholder needs. In this paper, we demonstrate, though a real industrial case, how transition… Exibir mais

At the analysis phase of an enterprise information system development, the alignment between the process level requirements (information systems) with the product level requirements (software system) may not be properly achieved. Modeling the processes for the enterprise’s business is often insufficient for implementation teams, and implementation requirements are often misaligned with business and stakeholder needs. In this paper, we demonstrate, though a real industrial case, how transition steps and rules are used to assure that process- and product-level requirements are aligned, within an approach that supports the creation of the intended requirements. The input for the transition steps is an information system logical architecture, and the output is a product-level (software) use case model. Exibir menos

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… Exibir mais

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. Exibir menos

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… Exibir mais

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. Exibir menos

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… Exibir mais

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. Exibir menos

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… Exibir mais

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. Exibir menos