• Journal of KIISE:Software and Applications
• /
• v.35 no.7
• /
• pp.424-430
• /
• 2008

Identifying crosscutting concerns during requirements engineering phase is one of the most essential parts in Aspect-Oriented Software Development. Considering crosscutting concerns in the earlier phase of the development improves consistency among requirements so that it can help maintain software systems efficiently and effectively. It also provides a systematic way to manage requirements changes by supporting traceability throughout the software lifecycle. Thus, identifying tangled and scattered concerns, and encapsulating them into separate entities must be addressed from the early phase of the development. To do so, first, functional and non-functional concerns must be clearly separated. Second, a pointcut where a main concern meets crosscutting concerns should be defined and specified precisely. Third, it is required to detect conflicts being occurred during composition of crosscutting concerns from the earlier phase. Therefore, this paper proposes a systematic approach to identifying and specifying crosscutting concerns using goal-scenario based requirements analysis. And we demonstrate the applicability of the approach by applying it into the intelligent service robot system.

• Journal of KIISE:Software and Applications
• /
• v.34 no.9
• /
• pp.773-784
• /
• 2007

Aspect-Oriented Programming (AOP) has focused on improving the modularity of the crosscutting concerns. The existing AOP methodology has been mainly focused on the implementation method of programs and thus developer-oriented concern extraction and development were performed. Recently, many studies for applying AOP to the entire software development processes ranging from requirement analysis to design and implementation are being conducted. But specification methods having consistency from the initial phase of concern extraction to implementation phase are not sufficient. In this paper, we have presented the specification of crosscutting concerns so as to solve these problems. The specification of crosscutting concerns provides guidelines and specification from the requirement analysis phase to the process of converting extracted crosscutting concerns to codes. This method reduces the gap to the process of mapping extracted crosscutting concerns into a single class and thus enhances program development and understandability. In addition, it raises program reusability, maintenance and extensibility by enhancing traceability.

• Journal of KIISE:Software and Applications
• /
• v.35 no.12
• /
• pp.741-752
• /
• 2008

Aspect-Oriented Software Development(AOSD) is the software development methodology that classifies concerns of the system and identifies crosscutting concerns and organizes aspect class, and AOSD has emerged as an important user-oriented software development methodology with high maintainability. However, most of related studies worked on identification and specification and coding of crosscutting concerns. And there have been few studies on slicing technique for tracing method of specified crosscutting concerns. Therefore, this paper proposes slicing technique based on AOSD that identifies and specifies crosscutting concerns through interactive analysis between use cases; also, suggests slicing technique which improves traceability centering on identified crosscutting concerns; applies the aspect-oriented slicing technique to Learning Management System(LMS) for case-study. LMS is a cyber educational system that demands a lot of functional changes and expansion, so it is effective to apply AOSD with high maintainability in developing LMS; and shows the results that compared with related studies by comparing six elements.

• Proceedings of the Korean Information Science Society Conference
• /
• 2007.06a
• /
• pp.49-50
• /
• 2007

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.10c
• /
• pp.453-457
• /
• 2006

프로그램 구현 방법에 편중되어온 기존의 AOSD 방법론이 최근에는 전체 개발 라이프사이클에서 초기 요구사항의 중요성이 강조되면서 요구사항 모델링, 분석, 설계분야에서 많은 연구가 진행되고 있다. 하지만, 요구사항 분석에서 추출된 관심사를 설계하여 구현 단계로 변환하는 과정에서 아직까지 상세화된 프로세스가 부족하다. 본 논문에서는 횡단 관심사 구현 명세 기법을 제시한다. 이 기법은 추출된 관심사를 구현 코드로 변환하기 위한 4단계의 프로세스로 구성되어 있다. 상세화된 명세 기법과 가이드라인은 AOSD에서 해결하기 어려운 설계에서 구현간의 갭을 줄여줌으로써 이해 및 유지보수성을 높여준다.

• Journal of KIISE:Software and Applications
• /
• v.36 no.5
• /
• pp.386-395
• /
• 2009

Business entities with which most service components interact are kind of cross-cutting concerns in a multi-layered distributed application architecture. When business entities are modified, service components related to them should also be modified, even though they implement common functions of the application framework. This paper proposes what we call DTT (Data Type-Tolerant) component model to process the variability of business entities, or externalized data, which feature modern application architectures. The DTT component model expresses the data variability of product lines at the implementation level by means of SCDTs (Self-Contained Data Types) and variation point interfaces. The model improves the efficiency of application engineering through data type converters which support type conversion between SCDTs and business entities of particular applications. The value of this model lies in that data and functions are coupled locally in each component again by allowing service components to deal with SCDTs only instead of externalized business eutities.

• Journal of KIISE:Software and Applications
• /
• v.37 no.4
• /
• pp.239-251
• /
• 2010

In modern distributed enterprise applications that have multilayered architecture, business entities are a kind of crosscutting concerns running through service components that implements business logic in each layer. When business entities are modified, service components related to them should also be modified so that they can deal with those business entities with new types, even though their functionality remains the same. Our previous paper proposed what we call the DTT (Data Type-Tolerant) component model to efficiently process the variability of business entities, which are data externalized from service components. While the DTT component model, by removing direct coupling between service components and business entities, exempts the need to rewrite service components when business entities are modified, it incurs the burden of implementing data type converters that mediate between them. To solve this problem, this paper proposes a method to use ontology as the metadata of both SCDTs (Self-Contained Data Types) in service components and business entities, and a method to generate data type converter code using the ontology. This ontology-based DTT component model greatly enhances the reusability of service components and the efficiency in processing data variability by allowing the computer to automatically generate data type converters without error.