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

The complexity of embedded systems and the effort to develop them has been rising in proportion with their importance. Also, the heterogeneity of the hardware and software parts in embedded systems makes it more challenging to develop. Errors caused by hardware/software interfaces, especially, account for up to 13 percent of failures with an increasing trend. Therefore, verifying the interface between hardware and software in embedded system is one of the most important research areas. However, current approaches such as co-simulation method and model checking have explicit limitations. In this paper, we propose the synthesizable interface co-verification framework for hardware/software co-design. Firstly, we introduce the separate interface specifications for the heterogeneous components to describe hardware design and software design. Our specifications are expressive enough to describe both. We also provide the transformation rules from the software specification to the hardware specification so that the whole system can be described from the software view. Secondly, we address the solution of verifying the interface of the software and hardware design by adopting and extending existing verification-techniques and extending them. In hardware interface verification, we exploit the model checking technique and provide more efficient verification by closing the hardware design from the assumption of the software behavior which is ensured by software verification step. Lastly, we generate the interface codes such as device APIs, device driver, and device controller from the specification so that verified hardware and software codes can be synthesized without extra efforts.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.6 no.6
• /
• pp.361-367
• /
• 2011

In this paper, we propose an interactive embedded system framework for efficient training management in u-health environment. First, we analyzed various requirements of smart training systems for quality of life. We also analyzed the oversea trends and positive effects of the embedded system in terms of both technical and economical factors. Second, we proposed detailed design specification for embedded hardware implementation. Third, we developed effective OS(Operating System) specification for the embedded hardware. Finally, we developed a training scenario and embedded applications such as training control software and analysis software for the smart training systems.

• Journal of the Semiconductor & Display Technology
• /
• v.22 no.1
• /
• pp.88-93
• /
• 2023

In software engineering, requirement analysis is an important task throughout the process and takes up a high proportion. However, factors that fail to analyze requirements include communication failure, different understanding of the meaning of requirements, and failure to perform requirements normally. To solve this problem, we derived actors and behaviors using morpheme analysis and BERT algorithms in the Korean requirement document and constructed them as ontologies. A chatbot system with ontology data is constructed to derive a final system event list through Q&A with users. The chatbot system generates the derived system event list as a requirement diagram and a requirement specification and provides it to the user. Through the above system, diagrams and specifications with a level of coverage complied with Korean requirement documents were created.

• 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.

• 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 The Korean Association of Information Education
• /
• v.8 no.4
• /
• pp.555-562
• /
• 2004

There are informal, semi-formal and formal methods in software specification. Among them, formal method which is based on mathematical theory had been used to remove ambiguity, incompleteness and contradiction efficiently. In this paper, we propose implementation steps from Z specification to EJB source code, Also, as a case study we show steps consisted of specifying stack data structure and implementing it in EJB. In conclusion, Z specification proved to be capable of implementing EJB interface, exception class, method, through refinement and definition of schema, interface, post-condition, pre-condition.

• IEMEK Journal of Embedded Systems and Applications
• /
• v.14 no.6
• /
• pp.329-338
• /
• 2019

Today's embedded software (SW) developments are mostly preceded by composing Software Requirement Specification (SRS). In particular, in the domain of weapon systems, it is essential to have a systematic method for the verification of the SW functionality. To be more specific, it is crucial to check if the SW functionality is implemented as described in SRS, so-called SW suitability verification. Unfortunately, existing static or dynamic SW testing methods are not sufficient to evaluate suitability with SRS since those testings only verify the robustness of the SW codes. In this paper, we propose an automatic embedded SW suitability verification framework which is based on a structured SRS. The major challenge in the automation of this verification framework is how to get rid of ambiguities in SRS. In order to overcome this challenge, we propose a structured SRS description framework and the supporting toolchain for that. We show how the proposed framework is applied to an actual SRS of a weapon system.

• Proceedings of the Korean Nuclear Society Conference
• /
• 2004.05a
• /
• pp.226-226
• /
• 2004

• 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 KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.120-133
• /
• 2000

Major obstruction of using formal methods for hybrid real-time systems in industry is the difficulty that engineers have in understanding and applying the quantitative methods in an abstract requirements phase. While formal methods technology in safety-critical systems can help increase confidence of software, difficulty and complexity in using them can cause another hazard. In order to overcome this obstruction, we propose a framework for qualitative requirements engineering of the hybrid real-time systems. It consists of a qualitative method for requirements specification, called QFM (Qualitative Formal Method), and a safety analysis method for the requirements based on a causality information, called CRSA (Causal Requirements Safety Analysis). QFM emphasizes the idea of a causal and qualitative reasoning in formal methods to reduce the cognitive burden of designers when specifying and validating the software requirements of hybrid safety systems. CRSA can evaluate the logical contribution of the software elements to the physical hazard of systems by utilizing the causality information that is kept during specification by QFM. Using the Shutdown System 2 of Wolsong nuclear power plants as a realistic example, we demonstrate the effectiveness of our approach.