From Use Cases to Objects: An Industrial Information Systems Case Study Analysis

Fernandes, João M.; Machado, Ricardo J.

doi:10.1007/978-1-4471-0719-4_33

Cited by 20 publications

(32 citation statements)

References 6 publications

(4 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…One of such architectural transformation techniques is the 4-Step Rule Set (4SRS) [5,6] that employs successive transformations of use cases to obtain a logical software architecture that satisfies the elicited user requirements. It provides a comprehensive set of guidelines divided into four steps that helps developers to obtain an initial architecture for the software system in a consistent, coherent and systematic way.…”

Section: Introductionmentioning

confidence: 99%

Deriving Software Architectures for CRUD Applications: The FPL Tower Interface Case Study

Mashkoor

Fernandes

2007

International Conference on Software Engineering Advances (ICSEA 2007)

View full text Add to dashboard Cite

The main aim of this paper is to present how to derive logical software architectures for CRUD (Create, Read, Update and Delete) applications using a specific technique called 4SRS. In this technique, a component diagram, which is obtained through transformations of use cases, is used to represent the logical software architecture. To show that the 4SRS technique, which was initially devised for behavior-intensive reactive systems, is also effective and gives seamless results for other software domains, it is being experimented on data processing systems, which typically follow a CRUD pattern. For demonstration purposes, the FPL tower interface system, which is responsible for communication between air traffic control operators and flight data processing system on airports of Portugal, has been used as a case study.

show abstract

Section: Introductionmentioning

confidence: 99%

Deriving Software Architectures for CRUD Applications: The FPL Tower Interface Case Study

Mashkoor

Fernandes

2007

International Conference on Software Engineering Advances (ICSEA 2007)

View full text Add to dashboard Cite

show abstract

“…In particular, the use case model specifies the functionality of the system, whilst the object diagram specifies the structure of the system. The latter is used as the foundation for the design and implementation phases 8,9].…”

Section: Introductionmentioning

confidence: 99%

“…Nowadays, there are many methods dealing with the problem of objects and classes identification 3,8,9,11,12]. Unfortunately, these methods suffer from at least two drawbacks: first is a focus on classes rather than objects and, second, a direct identification of classes and/or objects from the use case textual description.…”

Section: Introductionmentioning

confidence: 99%

An Approach to Building Object Models with UML in Embedded Systems

Tahar¹

2004

CIT

View full text Add to dashboard Cite

The UML-based development methods of embedded systems are use case-driven. In these methods, identifying objects that constitute the software system is a critical and hard task, since there is no firm guidelines. In this article, we propose a systematic approach to building object models in embedded systems. After hierarchically decomposing the system into its parts, the approach consists of firstly converting the use case into a statechart that models states of the concerned system parts and, secondly, identifying the objects from the statechart. The proposed approach bridges the gap between the outside behavioral system description, as offered by use cases and the system structure represented by the object model.

show abstract

“…This difference, that might apparently look superficial, entails a distinct approach and focus. A strategy, called 4-Step Rule Set (4SRS), was already devised to assist the designers in the transformation of use cases into objects [41].…”

Section: Transforming Use Cases Into Objectsmentioning

confidence: 99%