• Journal of Internet Computing and Services
• /
• v.9 no.5
• /
• pp.59-72
• /
• 2008

Computing systems in the modern era are expanding rapidly to include mobile-based businesses that make us of the various convergence distributed business process. This has lead to growing interest in the field of mobile embedded software development methodology, which has in turn lead to the proliferation of the embedded mobility. The use of CBD (Component Based Development) provides reusability, maintainability and portability, all of which are very important and focus issues to the business process. It also comes with the inherent productivity, quality and reliability of CBD. To make efficient use of CBD, though, clarified interface definitions for component integration are necessary. These definitions should be made up of collaborative hierarchical and horizontal architecture layers. Successful definitions should apply an effective framework made up of the architecture and process. In this paper, we describe an interface specification for small grained mobile embedded components(MEC) for the mobile embedded domain to meet maximum user requirements. We build and deploy the reconfigurable design patterns and components (in business domain categories) to make a component hierarchy and business logics for mobile embedded software. Proposed components specification plays a major role in development of the software for handling inconsistency in existing specification. It also includes plenty of specification information, using semantics and modeling based mechanisms to support business processes. We propose a development model of mobile embedded software using CBD for very complex and dynamic mobile business. We can apply it in a plug and play manner to develop the software. We verify that our framework supports very good productivity, quality and maintainability to meet the user's requirements in mobile business.

• Nuclear Engineering and Technology
• /
• v.26 no.4
• /
• pp.502-506
• /
• 1994

The design of safety computer system is described along with the case of software design and testing in the Core Protection Calculator System (CPCS). The application of computer system in safety system requires not only hardware qualification but thorough testing on software to verify its correctness and completeness. The testing on software for CPCS is performed by comparing the outputs of two versions of code. One is implemented in assembly language and the other is in Fortran. The testing is performed in sequencial and overlapping manner. Phase I test verifies that each software module is implemented correctly by executing every branch. Phase II test verifies that the integrated software is complete, meeting its requirements specification and also the integrated system meet its requirement and timing constraints. Through these testing, the Yonggwang Nuclear Power Plant Units (YGN) 3 and 4 CPCS software is verified to be correct and complete, and the integrated system is designed as in its requirements specification.

• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.198-202
• /
• 2020

User review sites are spaces where users can freely post and share their opinions, which are trusted by many people and directly influence sales. In addition, they overcome the limitations arising from existing requirements collection and are able to gather the needs of large numbers of different people at a low cost. Therefore, such sites are attracting attention as new spaces for understanding user needs. In a previous study, a user review analysis was attempted using 5W and 1H, and we inferred that a sentence containing "when" has special information based on the user experience. In addition, the requirements of the derivative activities in a user review can identify more user needs than the general requirements of derivative activities. In this paper, we propose a systematic method of deriving "when" sentences contain meaningful information from user reviews and converting them into use cases, which is one of the requirements of a specification method. This method converts unstructured data into structured data such that it can be included as the user requirements during software development from user comments expressed in natural language. This method will reduce project failures and increase the likelihood of success by enabling an efficient collection and analysis of user needs from valuable user reviews.

• 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 the Korea Society for Simulation
• /
• v.13 no.1
• /
• pp.51-63
• /
• 2004

Current distributed systems are attacked from the outside as well as in which new intrusions are occurred. In particular there is a growing but largely unnoticed intrusion threat due to the emerging middleware technologies such as CORBA, WAP, XML support, and enterprise application integrators. In order to cope with these attacks, intrusion tolerance technology is introduced. Intrusion tolerance technology means that it can provide services normally although attacks are occurred into system. There are intrusion tolerance architectures such as ITUA, HACQIT, SITAR, and so on as a part of DARPA project. In this paper, we analyze and discuss existing intrusion tolerance architectures with respect to intrusion tolerance technology. Also, we extract intrusion tolerant requirements, which are required to develop ,intrusion tolerant system. We propose UML-IT(Intrusion Tolerance) profiles and specify intrusion tolerant software by applying UML-IT profiles.

• Journal of Information Processing Systems
• /
• v.13 no.1
• /
• pp.26-39
• /
• 2017

The need for embedded devices to be able to exchange information with each other and with data centers is essential for the advent of the Internet of Things (IoT). Several existing communication protocols are designed for small devices including the message-queue telemetry transport (MQTT) protocol or the constrained application protocol (CoAP). However, most of the existing implementations are convenient for computers or smart phones but do not consider the strict constraints and limitations with regard resource usage, portability and configuration. In this paper, we report on an industrial research and development project which focuses on the design, implementation, testing and deployment of a MQTT module. The goal of this project is to develop this module for platforms having minimal RAM, flash code memory and processing power. This software module should be fully compliant with the MQTT protocol specification, portable, and inter-operable with other software stacks. In this paper, we present our approach based on abstraction layers to the design of the MQTT module and we discuss the compliance of the implementation with the requirements set including the MISRA static analysis requirements.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.26 no.4
• /
• pp.82-90
• /
• 2003

The Systems Engineering, as a methodology for engineering and management of today's ever-growing complex system, is a comprehensive and iterative problem-solving process. The process centers on the analysis and management of the stakeholders' needs throughout the entire life-cycle of a system and searches for an optimized system architecture. There are many essential needs and requirements to be met when a system development task is carried out. Systems Engineering Management Plan(SEMP), as a specification for system development process, must be established to satisfy constraints and requirements of stakeholders successfully and to prevent cost overrun and schedule delay. SEMP defines technical management functions and comprehensive plans for managing and controlling the entire system development process, specialty engineering processes, etc. Especially. in the case of a large-scale complex system development program where various disciplinary engineering such as mechanical; electrical; electronics; control; telecommunication; material; civil engineering etc. must be synthesized, it Is essential to develop SEMP to ensure systematic and continuous process improvements for quality and to prevent cost/schedule overruns. This study will enable the process knowledge management on the subject of SEMP as a core systems engineering management effort, that is, definitely defining and continuously managing specification of development process about requirements, functions, and process realization of it using a computer-aided systems engineering software. The paper suggests a systematic SEMP development process and demonstrates a data model and schema for computer-aided systems engineering software, RDD-100, for use in the development and management of SEMP. These are being applied to the systems engineering technology development task for the next-generation high-speed railway systems in progress.

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.5
• /
• pp.169-178
• /
• 2014

In this paper, we present a research utilizing decentralized LTL specifications for ensuring a quality for interaction-centralized system. In this system, for ensuring the quality, we need to validate interactions between modules of the system and then we should check whether the system achieves the expected requirements. This task remains difficult and labor-intensive and requires an expert. In this paper, we present a method to assist such a task. First of all, the requirements of the system is written as multiple LTL specifications. Interactions between modules mean that behaviors of one module are related with other one's behavior. We generate the automaton model fully achieving specification through GR(1) synthesis. And we simulate them using the simulator based on the software agent for checking behaviors of the system. Finally, we validate the whole system whether it achieves given requirements.

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.1-16
• /
• 2006

As the size of software is getting huge, it has been impossible for testers to test all of source coed. Therefore, the method which uses information of requirements for testing has been researched and accepted. Although there are a lot of test methods based on requirement specification, each method has a different approach and coverage. So we should consider their various approach and coverage in the stage of test planning. This paper presents the empirical comparison and the result by applying various black-box testing methods to software system. For this experiment we studied five black-box testing methods including UML based specification technique. We applied the five testing methods to application system and evaluated the coverage of extracted test case.

• Journal of Software Engineering Society
• /
• v.26 no.2
• /
• pp.45-52
• /
• 2013

A cloud computing service provider must assure Service Level Agreement (SLA) to provide reliable and consistent quality of service to a user. The SLA is a contract between the user and the service provider that connects to assure constant level such as availability to target provided service. 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 quality factors of service because it only considers factors about the physical Network environment. In this paper, we suggest the UDDI-based interchange process with the architecture and the specification language having a XML schema for the SLA specification. The quality requirements of SaaS are defined by a proposed specification language in the cloud environment. It is stored in the repository of a quality specification and exchanged on during the service binding time based on the exchange architecture.