• The Transactions of the Korea Information Processing Society
• /
• v.2 no.4
• /
• pp.499-508
• /
• 1995

Domain Analysis is an activity to identify commonalities and variabilities which similar application areas in order to reuse analyzed information easily in new software construction. Most of domain analysis output is represented by various diagrams without common standard, and its manual reuses result in low reusability. Domain analysis language can be used to represent domain analysis information and make it possible to automate reuse and test the specifications. In this paper we designed and implemented a processor to reuse domain analysis information represented by domain analysis language and applied our approach to a rental domain and got new specification instances. In addition, we compared reuse of a data flow diagramming tool with reuse of a domain information processor and found combining and found combining of each approach can increase the reusability of both.

• Journal of KIISE:Software and Applications
• /
• v.33 no.12
• /
• pp.1008-1021
• /
• 2006

Product line engineering(PLE) is one of the recent and effective reuse approaches that enables developing a number of applications by instantiating a core asset. Elements of a core asset are product line architecture(PLA), component, and decision model. Among these elements, PLA is the key element since it defines the overall structure of the core asset. Although numerous PLE methodologies have been introduced, it is still unclear what should be the elements of a PLA and how to systematically instantiate it for specific applications. Formal specifications can play a key role in defining detailed and precise instantiation process. In this paper, we first present a meta model of PLA and show how to specify PLA in a formal language, Object-Z. Then, we propose instantiation rules using formal specification and those rules precisely define constraints for instantiating PLA. By applying the proposed formal specification, we believe PLA instantiation can be carried out precisely and correctly, yielding high quality software development.

• 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.27 no.2
• /
• pp.157-167
• /
• 2000

As the requirements of a software system become large and complex, it causes some problems such that requirements specification using formal methods becomes larger in its size and less understandable. In order to solve such problems, the concepts of modularity and object are adopted to specify the requirements. In addition, top-down and compositional approach to handle such requirements are also adopted. In our paper, we suggest an object-oriented Petri net, called HOONet, to hierarchically specify and verify the complex requirements by incorporating the concepts of modularity, object, abstraction and refinement into a formal method. Our HOONet method supports the incremental specification and verification of partially described or not yet fully analyzed requirements. We also show the applicability of our method by modeling and verifying the requirements of a reactor safety control system.

• Journal of KIISE:Software and Applications
• /
• v.32 no.2
• /
• pp.108-118
• /
• 2005

The software of the nuclear power plant digital control system is a safety-critical system where many techniques must be applied to it in order to preserve safety in the whole system. Formal specifications especially allow the system to be clearly and completely specified in the early requirements specification phase, therefore making it a trusted method for increasing safety. In this paper, we discuss a systematic method, which generates PLC-based FBD programs from the requirements specification using NuSCR, a formal requirements specification method. This FBD programs takes an important position in design specification. The proposed method can reduce the possible errors occur in the manual design specification, and the software development cost and time. To investigate the usefulness of our proposed method, we introduce the fixed set-point rising trip example, a trip logic of BP in DPPS RPS, which is presently being developed at KNICS.

• The KIPS Transactions:PartD
• /
• v.11D no.4
• /
• pp.855-864
• /
• 2004

Programmers can be got the test-related information for implementation without interference of source code complexity by use of the formal specification. Especially the external inputs and system responses can be represented precisely by formal specification in testing phase of web-based software systems. This paper suggests a method of extracting test cases by use of formal specification. Object-Z formal specification represents various test-related information for complex functions of web-based applications. State Transition Models could be built from the formal specification so that test scenarios were extracted from STDs from the highest level to detail levels. The target system for verification of this method is a web-based banking system which is necessary to be secured and critical on errors. This method would be an important factor in automatizing test procedure for web-based application software systems combining the user-base test technique.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.18 no.5
• /
• pp.83-91
• /
• 2008

IISO/IEC 9594-8 defines the public key framework and attribute certificate framework. Attribute certificate framework deals with privilege management infrastructure(PMI). In PMI, for privilege management using attribute certificates, role assignment certificates and role specification certificates are used to assign and specify privileges independently. Role specification certificates includes privilege specifications and the details far privilege management of network environments. Privilege management of unreliable network environment tries to enhance the reliability and efficiency of privilege information transmission forwarding over unreliable routes in the presence of potentially faulty nodes and edges. Each node forms a role specification tree based on role specification relationship data collected from the network. In this paper privilege management cost with the role specification certificates tree structure is evaluated trying to reduce the overhead incurred by role creation and modification of privileges. The multicasting of packets are used for scalability. We establish management cost model taking into account the packet loss and node reliability which continuously join and leave for network. We present quantitative results which demonstrate the effectiveness of the proposed privilege management scheme.

• Journal of KIISE
• /
• v.42 no.5
• /
• pp.591-600
• /
• 2015

SLA (Service Level Agreement) is an essential factor that must be guaranteed to provide a reliable and consistent service to user in cloud computing environment. Especially, a contract between user and service provider with SLA is important in an environment using a cloud service brokerage. The cloud computing is classified into IaaS, PaaS, and SaaS according to IT resources of the various cloud service. The existing SLA is difficult to reflect the quality factors of service, because it only considers factors about the physical Network environment and have no methodological approach. In this paper, we suggested a method to specify the quality characteristics of software and proposed a mechanism and structure that can exchange SLA specification between the service provider and consumer. We defined a meta-model for the SLA specification in the SaaS level, and quality requirements of the SaaS were described by the proposed specification language. Through case studies, we verified proposed specification language that can present a variety of software quality factors. By using the UDDI-based mediation process and architecture to interchange this specification, it is stored in the repository of quality specifications and exchanged during service binding time.

• The KIPS Transactions:PartC
• /
• v.8C no.2
• /
• pp.221-233
• /
• 2001

오늘날 이동 에이전트 기술은 네트워크 트래픽을 효과적으로 줄이고, 서버의 인터페이스를 바꾸지 않고 클라이언트의 다양한 요청을 융통성 있게 서비스할 수 있는 기술로 여겨지고 있다. 그러나 대부분의 이동 에이전트 시스템들은 그들 자신의 구조를 적용하고 다른 방법으로 구현되어, 특정 이동 에이전트 시스템에서 생성된 이동 에이전트는 다른 에이전트 시스템에서는 사용될 수 없다. 이러한 문제를 해결하기 위하여 OMG(Object Management Group)는 이질적인 에이전트 시스템간의 상호운용선(interoperability)을 증진시킬 목적으로 이동 에이전트와 에이전트 시스템간의 공통된 개념적인 모델에 대하여 기술한 MAF(Mobile Agent Facilities) 명세를 제안하였다. 본 논문에서는 OMG MAF 명세를 만족하는 자바 기반의 SMART 시스템에 관하여 기술한다. SMART 시스템은 MAF 명세에 따른 이동 에이전트간의 상호운용성을 지원하고, MAF 명세에서 권장하는 보안 모델을 기반으로 한 독자적인 보안 기능을 제공한다. 또한 보다 안정된 에이전트 시스템의 운영을 위하여 자체적인 에이전트 및 에이전트 시스템의 영속성(persistence)과 예외처리를 지원한다.

• Journal of KIISE
• /
• v.44 no.1
• /
• pp.27-35
• /
• 2017

Many studies have addressed 'Adaptive User Interface (AUI)', wherein the user interface changes in accordance with the situation and the environment of each user at runtime. Nevertheless, previous papers for AUI barely reflected the viewpoints from requirements engineering field, since most of them focused on proposing the architecture and design. In this study, we outline AUI with the perspective of requirements engineering and propose the requirements elicitation and specification method based on concepts which have been researched in the area of self-adaptive system. Step by step, we first redefine and reinterpret the well-known concepts of self-adaptive software, after which the AUI requirements are elicited and specified. Finally, we illustrate a case study, which demonstrates the effectiveness of our method.