• Journal of Internet Computing and Services
• /
• v.10 no.1
• /
• pp.175-182
• /
• 2009

Less efforts has been made in developing specifications and verification techniques for quality requirements. This paper suggests specification and traceability methods supporting quality issues such as usability, performance, and understandability when developing information systems with UML notation. With traceability checking methods that augment quality extension to the use cases and sequence diagrams, developers can confirm the level of implementation for both functional and nonfunctional requirements beforehand.

• Journal of the Korean Society for information Management
• /
• v.14 no.2
• /
• pp.165-189
• /
• 1997

In analyzing, designing, implementing the system, the traditional modeling method lacks design procedure and specification in reflecting the functional or nonfunctional requirements perfectly and consequently. These problems are unreliable in the Library and Information System since it requires a diversity of reference methodes based on various types of data. In this paper, we modify the method partially which the OMT proposes and apply it on system development. We also prepare the object oriented modeling modified from OMT type' modeling for Library User System Requirements.

• The KIPS Transactions:PartD
• /
• v.16D no.6
• /
• pp.871-880
• /
• 2009

Along with the complexity and size growth of embedded software, it is critical to meet the nonfunctional requirements such as power consumption as well as functional requirements such as correctness. This paper, apart from the existing studies of source code-based power analysis, proposes an approach of model-based power analysis using UML 2.0. Specially, we focus on the development of energy library to analyze the power consumption of embedded software. Our energy library supports model-based power analysis, and also supports the easy adaption for the change of embedded application.

• 한국IT서비스학회:학술대회논문집
• /
• 2008.11a
• /
• pp.281-284
• /
• 2008

종래의 방법론은 분석대상 시스템의 기능적 요구사항을 추출하는데 초점이 맞춰져 있어서 상대적으로 시간 제한과 같은 개념은 다루어지고 있지 않다. 시간 제한과 같은 개념이 개발 시에 제대로 적용되지 않거나 간과하게 됨으로써 개발된 시스템의 성능은 예측 불가능하게 되며 시스템을 구현완료하고 테스팅 단계에서 시스템이 잘 못 개발되었다는 것을 확인하게 된다. 본 연구는 일반 업무용 소프트웨어 시스템의 개발에 있어서 비 기능적 요구사항으로 다루어지는 성능 관련 항목을 시스템 개발과정에 강제 시킴으로써 예측 가능한 소프트웨어 시스템을 구성할 수 있게 한다. 또한 하드웨어 중립적인 시간 개념을 사용함으로써 소프트웨어가 작동하는 하드웨어의 성능에 맞는 적절한 소프트웨어를 개발해 낼 수 있도록 한다.

• The Journal of Society for e-Business Studies
• /
• v.5 no.2
• /
• pp.81-99
• /
• 2000

Nowadays, many commercial ERP products, such as Oracle, SAP, and Baan, etc, are designed based on large-scaled companies. It is difficult for small and medium-size companies with weakness in budgets and resources(e.g., human, organization, technique, and so on) to use them as it was. So, new ERP system need to be provided for small and medium-size companies. In this paper, we model and provide a conceptual ERP model for small and medium-size companies by using "4＋1 View" architecture model of Unified Modeling Language(UML). The conceptual ERP model consists of five subsystems： Manufacturing, Sales, HumanResource and Payroll, Accounting, and Trading. Especially, we describe the conceptual ERP model focusing on "Manufacturing" subsystem by using several diagrams of UML. By using the conceptual ERP model, the ERP system′s developers of small and medium-size companies can obtain many benefits： improving the efficiency of software developing process and helping user requirements gathering and description of ERP system′s nonfunctional aspect as well as functional aspect.

• Journal of Information Technology Services
• /
• v.2 no.1
• /
• pp.135-143
• /
• 2003

As the functional and nonfunctional requirements of defence systems become more complex and precise, concerning about the systematic development of software embedded into the defence systems has become surged up. In order to develop more reliable and correct software, and to extend the life cycle of the developing software, adoption of some engineering technologies such as development process, methodology, CASE tools and documentation is essentially required. This paper introduce an approach to technical information management in embedded software development process, with an instance, airborne ECM system development project. Particularly, we suggest and explain how to guide the software development according to process and methodology, and how to generate technical documents using CASE tool.

• International conference on construction engineering and project management
• /
• 2009.05a
• /
• pp.464-471
• /
• 2009

Robot and application of IT skill of construction industry are slow comparatively than another thing industry by the feature. This research proposes progress management and real time information gathering through construction automation and RFID focused on steel structure construction. Building for RTPM system, must consider various variables and surrounding situation in construction field and it is the most important and difficult matter that draw right requirement and grasp relation between this requirements to accomplish one suitable task considering these environment. Therefore, in this study analyzes requirement and target for RTPM system based on scenario that is easy to draw requirement and apply this to use case model. Presented method suggests that represent relation between goals and way that refines goal systematically from requirement of RTPM system. And it could express for visualization through the Way that attaches nonfunctional elements of system with system internal goal.

• Journal of KIISE
• /
• v.45 no.1
• /
• pp.36-44
• /
• 2018

Due to the advent of the 4th Industrial Revolution, it is imperative that we aggressively continue to develop state-of-the-art, cutting edge ICT technology relative to autonomous vehicles, intelligent robots, and so forth. Especially, systems based on convergence IT are being developed in the form of CPSs (Cyber Physical Systems) that interwork with sensors and actuators. Since conventional CPS specification only expresses behavior of one system, specification for collaboration and diversity of CPS systems with characteristics of hyper-connectivity and hyper-convergence in the 4th Industrial Revolution has been insufficiently presented. Additionally, behavioral modeling of CPSs that considers more collaborative characteristics has been unachieved in real-time application domains. This study defines the non-functional requirements that should be identified in developing embedded software for real-time constrained collaborating CPSs. These requirements are derived from ISO 25010 standard and formally specified based on state-based timed process. Defined non-functional requirements may be reused to develop the requirements for new embedded software for CPS, that may lead to quality improvement of CPS.

• Journal of KIISE:Software and Applications
• /
• v.33 no.2
• /
• pp.186-200
• /
• 2006

Analysis model focuses only on functional requirements and postpones nonfunctional requirements and implementation specific issues until subsequent design activities are undertaken. Based on the analysis models, the design activities are performed by refining and clarifying the analysis models. Thus, the quality of analysis models has a vast impact on the design models. Therefore, much effort should be taken to build correct analysis model. In this paper, we propose a set of structural constraints that analysis models of typical object-oriented development methods should satisfy. Three kinds of constraints are proposed: class related constraints, relation related constraints, and usage related constraints. For each constraint, formal definition and description with OCL are provided. In addition, through a case study with two medium-sired industrial systems, we demonstrated that the proposed approach can help to identify and correct serious deficiencies in object-oriented analysis models.

• Journal of the Korea Safety Management & Science
• /
• v.6 no.3
• /
• pp.211-235
• /
• 2004

Component based design is perceived as a key technology for developing advanced real-time systems in a both cost- and time effective manner. Already today, component based design is seen to increase software productivity, by reducing the amount of effort needed to update and maintain systems, by packaging solutions for re-use, and easing distribution. Nowdays, a thousand and one companies in If(Information Technology) industry such as Sl(System Integration) and software development companies, regardless of scale of their projects, has spent their time and endeavor on developing reusable business logic. The component software is the outcome of software developers effort on overcoming this problem; the component software is the way propositioned for quick and easy implementation of software. In addition, there has been lots of investment on researching and developing the software development methodology and leading If companies has released new standard technologies to help with component development. For instance, COM(Component Object Model) and DCOM(Distribute COM) technology of Microsoft and EJB(Enterprise Java Beans) technology of Sun Microsystems has turned up. Component-Based Development (CBD) has not redeemed its promises of reuse and flexibility. Reuse is inhibited due to problems such as component retrieval, architectural mismatch, and application specificness. Component-based systems are flexible in the sense that components can be replaced and fine-tuned, but only under the assumption that the software architecture remains stable during the system's lifetime. In this paper, It suggest that systems composed of components should be generated from functional and nonfunctional requirements rather than being composed out of existing or newly developed components. about implements and accomplishes the modeling for the Product Control component development by applying CCD(Contract-Collaboration Diagram), one of component development methodology, to MRP(Material Requirement Planning) System