• Journal of KIISE:Computing Practices and Letters
• /
• v.15 no.3
• /
• pp.167-177
• /
• 2009

This paper is about our experience of developing a context-aware exhibit guide system called MyGuide by applying Simtext development methodology. In particular, we introduce some issues to be considered in development process, the way that we solved them, and other things related to context. In requirements elicitation phase, we reduced the complexity of requirements by separating business logic requirements and context-awareness related requirements. After that, we modeled context, and designed software architecture, classes, and database in sequence during design phase. We considered system requirements and context modeling issues for context modeling because it influences class and database design.

• International Journal of Computer Science & Network Security
• /
• v.21 no.2
• /
• pp.130-141
• /
• 2021

This paper is in the intersection of software engineering and system engineering, two intimately intertwined disciplines. A dominating theme in this paper is the integral conceptualization of systems at large, as well as an underlying concern with software systems. In the software development life cycle, challenges still exist in translating requirements into a design artifact and then into an implementation (e.g., coding), then validating the results. From our perspective, software engineering requires an integrating paradigm toward a unified modeling orientation. Many methodologies, languages, and tools exist for facilitating system development processes. This paper is a venture into project development. To focus the materials, we concentrate on Harel's novel (and classic) development environment, which integrates a scenario-based engineering object orientation and statecharts through developing a railcar system. The railcar system is used as a detailed sample of translating requirements into a design artifact and then into an implementation, then validating the result. The project is re-cased as a single integrated modeling endeavor to be contrasted with the scenario and statecharts' development. The result of this scheme is an enriched understanding through experimenting with and contrasting various development methods of software projects.

• Journal of KIISE
• /
• v.43 no.8
• /
• pp.857-868
• /
• 2016

With changing software industry structure, the emerging concept called Software Ecosystems (SECO) has various challenges that software engineers have to overcome. In market-driven software product development, they should have the capability to offer high value products to their own business and their customers in order to being competitive. Each stakeholder's perspectives and interests should be reconciled in terms of requirements so that engineers can offer high value products through requirements selection. Existing works have just mentioned the need of requirements negotiation between stakeholders without proposing detailed guidelines or practice. In this work, a systematic Requirements Negotiation process is proposed to resolve conflicts of interests of stakeholders in SECO. The interests of stakeholders are analyzed based on goal-based requirements engineering. The rationale of requirements conflict is structured for management. A stepwise requirements negotiation process aims at resolving requirements conflict by applying game theory concepts based on self-interested behaviors of stakeholders.

• Convergence Security Journal
• /
• v.4 no.2
• /
• pp.71-75
• /
• 2004

The Common Criteria (CC) philosophy is to provide assurance based upon an evaluation of the IT product or system that is to be trusted. Evaluation has been the traditional means of providing assurance. It is essential that not only the customer' srequirements for software functionality should be satisfied but also the security requirements imposed on the software development should be effectively analyzed and implemented in contributing to the security objectives of customer's requirements. Unless suitable requirements are established at the start of the software development process, the re suiting end product, however well engineered, may not meet the objectives of its anticipated consumers. By the security evaluation, customer can sure about the quality of the products or sys tems they will buy and operate. In this paper, we propose a selection guide for If products by show ing relationship between security engineering and security evaluation and make help user and customer select appropriate products or system.

• Proceedings of the Korea Information Assurance Society Conference
• /
• 2004.05a
• /
• pp.141-144
• /
• 2004

The Common Criteria (CC) philosophy is to provide assurance based upon an evaluation of the IT product or system that is to be trusted. Evaluation has been the traditional means of providing assurance. It is essential that not only the customer' srequirements for software functionality should be satisfied but also the security requirements imposed on the software development should be effectively analyzed and implemented in contributing to the security objectives of customer's requirements. Unless suitable requirements are established at the start of the software development process, the resulting end product, however well engineered, may not meet the objectives of its anticipated consumers. By the security evaluation, customer can sure about the quality of the products or systems they will buy and operate. In this paper, we propose a selection guide for If products by showing relationship between security engineering and security evaluation and make help user and customer select appropriate products or system.

• Journal of KIISE:Software and Applications
• /
• v.33 no.8
• /
• pp.655-667
• /
• 2006

This paper proposes a method for counting function point using goal and scenario based requirements. Function Point is a software sizing method and widely used as a basis to estimate software development cost. Requirements elicitation and analysis should be performed before function point analysis but function point analysis method doesn't deal with requirements elicitation and analysis. For that reason, Function point extraction method from existing requirements method is needed and if the requirements method has advantage for traceability and elicitation, it is suitable for managing cost. Goal and scenario method is widely used as requirements elicitation and analysis. It has also good traceability. Therefore, this paper discusses a method for extracting function point from requirements text gathered using the goal and scenario based requirements elicitation technique. The proposed method aims to establish and maintain traceability between function point and requirements text. Text based function point extraction guidance rules have been developed. The proposed methodology has been applied to Order Processing System development.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.12
• /
• pp.543-548
• /
• 2017

In recent years, the importance of the safety of medical device software has been emphasized because of the function and role of the software among components of the medical device, and because the operation of the medical device software is directly related to the life and safety of the user. To this end, various standards have been set up that provide activities that can effectively ensure the safety of medical devices and provide their respective requirements. The activities that standards provide to ensure the safety of medical device software are largely divided into the development life cycle of medical device software and the risk management process. These two activities should be concurrent with the development process, but there is a limitation that the risk management requirements to be performed at each stage of the medical device software development life cycle are not classified. As a result, developers must analyze the association of standards directly to develop risk management activities during the development of medical devices. Therefore, in this paper, we analyze the relationship between medical device software development life cycle and risk management process, and extract risk management requirement items. It enables efficient and systematic risk management during the development of medical device software by mapping the extracted risk management requirement items to the development life cycle based on the analyzed associations.

• Journal of the Korea Society for Simulation
• /
• v.32 no.3
• /
• pp.23-31
• /
• 2023

Software development involves a series of stages, including requirements analysis, design, implementation, unit testing, and integration testing, similar to those used in the system engineering process. This study utilized MathWorks' model-based design platform to develop multi-function radar software and evaluated its feasibility and efficiency. Because the development of conventional radar software is performed by a unit algorithm rather than in an integrated form, it requires additional efforts to manage the integrated software, such as requirement analysis and integrated testing. The mode-based platform applied in this paper provides an integrated development environment for requirements analysis and allocation, algorithm development through simulation, automatic code generation for deployment, and integrated requirements testing, and result management. With the platform, we developed multi-level models of the multi-function radar software, verified them using test harnesses, managed requirements, and transformed them into hardware deployable language using the auto code generation tool. We expect this Model-based integrated development to reduce errors from miscommunication or other human factors and save on the development schedule and cost.

• International journal of advanced smart convergence
• /
• v.9 no.3
• /
• pp.227-231
• /
• 2020

Recently, the importance of user experience (UX) has been rapidly increasing. Its utilization is emphasized for development of systems, products, and services. User experience is widely used across industries including services, products, processes, society, and culture. Therefore, if it is unsatisfactory, it is likely to have a direct negative impact on the corresponding system, product, or service. The failure to analyze user experience causes significant damage to the project, which may lead to its failure or redevelopment; it is hence necessary to prioritize the verification of UX in the earliest stages of development. The requirements development stage, which is a preceding stage, is an appropriate stage for the verification of user experience because the identification of user needs is completed and prototypes can be implemented. In this paper, we proposed a systematic requirements development stage; it adds user experience verification activities to the requirements development stage, using the Honeycomb model, which is a widely used tool for verifying the overall UX. User experience verification was added to the existing requirements development activities, which consisted of three steps: model definition and requirements placement, discussions between external and internal stakeholders, and review by internal stakeholders. By easily validating the user experience through this systematic requirements development stage, we expect to minimize the damage to the project due to the failure of the user experience analysis and increase the possibility of success.

• Proceedings of the Korean Society for Quality Management Conference
• /
• 2004.04a
• /
• pp.114-119
• /
• 2004

Software verification and validation(V&V) is a means to develop high-quality software and assure safety and reliability for software. Also, we can achieve the desired software quality through systematic V&V activities. The software to be applied safety critical system like nuclear power plants is required to setup the V&V methodology that comply with licensing requirements for nuclear power plants and should be performed V&V activities according to it. In this paper, we classified safety-critical, safety-related and non-safety for software according to safety function to be peformed and define V&V activities to be applied software grade. Also, we defined V&V activities, procedures and documentation for each phase of software development life cycle and showed techniques and management to perform V&V. Finally, we propose the V&V framework to be applied software development of SMART(System-integrated Modular Advanced ReacTor) MMIS (Man-Machine Interface System) and to comply with domestic licensing requirements.