Sam Supakkul
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Sam Supakkul has a total of 8 co-authors. Here are the top co-authors by number of shared publications:
- Lawrence Chung
University of Texas at Dallas
3 shared publications - Ebenezer A. Oladimeji
Verizon Communications, Irving, Texas 75038, USA
1 shared publication - José Luis Garrido
Department of Software Engineering, Computer Science School, University of Granada, Granada, Spain
1 shared publication - Kawtar Benghazi
University of Granada
1 shared publication - Manuel Noguera
Universidad de Granada Universidad de Granada Universidad de Granada Universidad de Granada
1 shared publication - María Luisa Rodríguez
Software Engineering Department, MYDASS (Modelling & Development of Advanced Software Systems) Research Group, Higher Technical School of Computer and Telecommunication Engineering, University of Granada, Granada, Spain
1 shared publication
Latest Publications
- 1 September 2006
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 539-544
Capturing and Reusing Functional and Non-functional Requirements Knowledge: A Goal-Object Pattern Approach
Pattern-based approach has proven to be an effective means for capturing and reusing past experience and best practices to facilitate communication and shorten the time required for software modeling. However, current knowledge capture is limited to mostly functional knowledge. Knowledge reuse is also often manual and limited to low-scale small model fragments. This paper presents a goal-object pattern framework that captures both functional and non-functional requirements knowledge that is modeled using UML and a goal-oriented method. Patterns in this framework are a collection of model refinement methods, each defining a single model element generation step in the target model. The patterns are model-driven in that they are defined using a UML metamodel and then used as such. The framework also supports incremental knowledge capture in that large-grain patterns can be composed from fine-grain ones, and also application-independent patterns can be specialized into application-specific ones. The framework is illustrated using a simplified on-line bookstore application to demonstrate how large-scale reuse may be possible
- 1 September 2006
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 539-544
Capturing and Reusing Functional and Non-functional Requirements Knowledge: A Goal-Object Pattern Approach
Pattern-based approach has proven to be an effective means for capturing and reusing past experience and best practices to facilitate communication and shorten the time required for software modeling. However, current knowledge capture is limited to mostly functional knowledge. Knowledge reuse is also often manual and limited to low-scale small model fragments. This paper presents a goal-object pattern framework that captures both functional and non-functional requirements knowledge that is modeled using UML and a goal-oriented method. Patterns in this framework are a collection of model refinement methods, each defining a single model element generation step in the target model. The patterns are model-driven in that they are defined using a UML metamodel and then used as such. The framework also supports incremental knowledge capture in that large-grain patterns can be composed from fine-grain ones, and also application-independent patterns can be specialized into application-specific ones. The framework is illustrated using a simplified on-line bookstore application to demonstrate how large-scale reuse may be possible
- 1 September 2006
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 351-358
Toward Component Non-functional Interoperability Analysis: A UML-based and Goal-Oriented Approach
Component-based development (CBD) has a great potential of reducing development cost and time by integrating existing software components. But it also faces many challenges one of which is ensuring interoperability of the components that may have been developed with different functional and non-functional goals. The software community has traditionally focused more on the functional aspect of the interoperability such as syntactic and semantic compatibility. However, incompatibility from the non-functional aspect could lead to poor quality such as insufficient security or even inoperable system. This paper presents a preliminary framework for analyzing non-functional requirements (NFRs) defined for the component required and provided interfaces. The components are considered non-functionally interoperable when they agree on the definition and implementation techniques used to achieve the NFRs. Any detected mismatches can be resolved using a combination of the three presented tactics, including replacing the server component, negotiating for more attainable NFRs, or using an adapter component to bridge the non-functional differences. A running example based on a simplified Web-based conference management system is used to illustrate the application of this framework
- 1 September 2006
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 351-358
Toward Component Non-functional Interoperability Analysis: A UML-based and Goal-Oriented Approach
Component-based development (CBD) has a great potential of reducing development cost and time by integrating existing software components. But it also faces many challenges one of which is ensuring interoperability of the components that may have been developed with different functional and non-functional goals. The software community has traditionally focused more on the functional aspect of the interoperability such as syntactic and semantic compatibility. However, incompatibility from the non-functional aspect could lead to poor quality such as insufficient security or even inoperable system. This paper presents a preliminary framework for analyzing non-functional requirements (NFRs) defined for the component required and provided interfaces. The components are considered non-functionally interoperable when they agree on the definition and implementation techniques used to achieve the NFRs. Any detected mismatches can be resolved using a combination of the three presented tactics, including replacing the server component, negotiating for more attainable NFRs, or using an adapter component to bridge the non-functional differences. A running example based on a simplified Web-based conference management system is used to illustrate the application of this framework