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

Software architecture is the high level model of a software system. It should be specified with ADLs (Architecture Description Languages) for its clarity and preciseness. Most ADLs such as C2SADL have not come into extensive use in industries since ADL users should learn a distinct notation specific to architecture, and ADLs do not address all stakes of the development process that is becoming diversified everyday. On the other hand, UML is a do facto standard general modeling language for software developments. UML provides a consistent notation and various supporting tools during the whole software development cycle. But, UML is a general modeling language and does not provide all concepts that are important to architecture description. UML should be extended in order to precisely model architecture. In this paper, we defined a C2 architecture modeling language as a UML2.0 profile. We applied the defined C2 architecture modeling language to the modeling of a restaurant reservation system.

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

Software architecture, which is the high level model of a software system, should be specified with ADLs (Architecture Description Languages) for its clarity and preciseness. Most of ADLs such as ACME, however, have not come into extensive use in industries since ADL users should learn a distinct notation specific to architecture. On the other hand, UML is a do facto standard general modeling language for software developments. UML provides a consistent notation and various supporting tools during the whole software development cycle. UML, being a general modeling language, does not provide all concepts that are important to architecture description. UML should be extended in order to precisely model architecture. A number of researches on architecture modeling based on WML have been progressed. Ail of them, however, are based on the UML1.x. UML2.0 embraces much more concepts that are important to architecture modeling than UML1.x. In this paper. we defined an architecture modeling language based on UML2.0. We defined Generic ADL by extending UML2.0 and applied the defined Generic ADL to a restaurant reservation system.

• The Journal of Society for e-Business Studies
• /
• v.13 no.4
• /
• pp.93-110
• /
• 2008

Reference modeling for Collaborative Networked Organizations(CNOs) has just started, and Enterprise Architecture Modeling Languages(EAMLs) for CNOs are very few. Lack of reference models makes it difficult for people to communicate with each other and lack of EAMLs also makes it difficult to implement information systems for CNOs. We propose an EAML for CNO called CAML. It supports (1) multi-level modeling based on Model- Driven Architecture of OMG's for expressive power and efficiency of implementations, and (2) multi-focus modeling based on Zachman Framework for completeness of modeling The effectiveness of the CAML is investigated through modeling of a supply chain and execution of change impact analysis.

• Journal of information and communication convergence engineering
• /
• v.17 no.2
• /
• pp.117-127
• /
• 2019

In software engineering, to ensure reliability between systems, describing both system architecture and assurance arguments between system elements is considered necessary. There are proposals for system architecture assurance, but use of these traditional methods often requires development of different diagrams using different editors. Because the visual sense of the traditional methods is inadequate, errors readily occur when manipulating different diagrams. Therefore, it is essential that the assurance of dependability between components and systems is visualized and easy to understand. In this paper, an integrated approach to describe the relationship between system actors and system architecture is proposed, and this approach is clarified using an enterprise architecture modeling language. A case study is carried out and comparison to the traditional approach $d^*$ framework is explained. The comparison results show that the proposed approach is more suitable for ensuring dependability in system architecture.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.8
• /
• pp.1970-1976
• /
• 2009

It is more emphasized on the software architecture recently, as the scale of a software becomes huge and the need of the software management becomes more dynamic. Software architecture is a representation of structures of software framework just like the blueprint of building architecture. In order to describe software components and their relationships accurately and entirely, software architecture is documented in some different views, by using of modeling tools. UML(Unified Modeling Language) is a software modeling tool recently used for documentation of software and as well as software architecture. Nevertheless, what we have to agree with is that UML is not easy to use and its standard changed continuously. And also the documentation with UML is found some burden because of its difficulties in learning and using. This inconvenience enforces us to purchase and use commercial tool for UML. The study introduces the architecture views refined from 4+1 Views for architecture design and shows how to represent architecture views for software architecture. Especially, we simplifies UML diagrams for the purpose of focusing on architecture views and facile manipulation. At the end, we add the evaluation on the refined architecture views as well as refined UML diagram.

• The KIPS Transactions:PartD
• /
• v.19D no.1
• /
• pp.81-94
• /
• 2012

FORM(Feature-Oriented Reuse Method) is one of representative product line engineering methods. The essence of FORM is the FORM architecture models, which can be reused in the development of multiple products of a software product line. The FORM architecture models, however, have the following problems when applied in practice. First, they are not standardized models like UML(Unified Modeling Language) and therefore they can be constructed only through a specific modeling tool. Second, they do not represent architectural variability explicitly. Instead their variability is only managed through a mapping from a feature model. To address these two problems, we developed at first a method for representing the FORM architecture models using UML, which enables the FORM architecture models to be constructed through various available UML modeling tools. Also, we developed an effective method for representing as well as managing the variability of the FORM architecture models through a mapping from a feature model.

• Korean Management Science Review
• /
• v.17 no.3
• /
• pp.147-160
• /
• 2000

These days, a modeling tool or environment has to know about the others on the market and build bridges to them with which their customers insist on sharing models and data. When it is based on a closed architecture, a tangle of import/export point translators is required. Using an exchange standard, we can design an open architecture for the interchange of models and data. XML(Extensible Markup Language) provides a framework for describing the syntax for creating and exchanging data structures. The explosive growth of XML-based business proposals and standards reflects the urgent requirements and its strength. This paper proposes an XML-based language for sharing decision models within the MSOR/DSS community. The language is able to allow applications and on-line analytic processing tools to models obtained from multiple sources without having to deal with individual differences between those sources. It is expected to be a medium for B2B integration by supporting flexible interchange of decision models.

• Journal of Korea Society of Industrial Information Systems
• /
• v.6 no.4
• /
• pp.39-47
• /
• 2001

Software architecture serves as a framework for understanding system component and their interrelationships. Software architectures can be reusable assets to achieve low costs, high productivity, and consistent quality. We have developed a software architecture design environment, called Happy Work. In this paper, we would like to present the structure and functions of Happy Work. Happy Work has two main functions. First, it provides a graphic editor for modeling of software architecture diagram. Second, it provides an ADL, called HWL(HappyWork language). HWL is a language that describes software architecture.

• Journal of the Korea Society for Simulation
• /
• v.17 no.4
• /
• pp.209-218
• /
• 2008

The Unified Modeling Language becomes popular to specify, visualize, construct, and document software-intensive systems, especially in supporting the design phase of software engineering. Most of designs in UML have focused on firm designing of software system structure. Recently, some researches have raised additional demands in many emerging complex software systems, such as aspect-oriented design. In this paper, we work on the dynamic aspect of policy-driven architecture. We present a UML-based high-level modeling of policy-driven management which is applicable in various application domains. In order to manage a number of activities of applications, dynamics and flexibility should be supported with policies consistently on different resources in the same context. Thus, a methodology of meta-modeling to represent dynamic aspects of policy-driven architecture is studied. Based on our methodology, we could achieve meta-modeling to develop a number of policy-driven management applications.

• Journal of Information Technology Applications and Management
• /
• v.14 no.2
• /
• pp.117-127
• /
• 2007

Using an exchange standard, we can design an open architecture for the interchange of decision models and data. XML (eXtensible Markup Language) provides a general framework for creating such a standard. Although XML -based model representation languages such as OOSML were proposed, they are partly limited in expression capability, flexibility, generality, etc. This paper proposes a new method for expressing and sharing decision models and data based on XBRL (eXtensible Business Reporting Language), which is a XML language specialized in business reporting. We have developed a XBRL taxonomy for decision models with the concepts and relationships of a representative modeling framework, SM (Structured Modeling). The method allows for expressing data as well as decision models in a consistent and flexible manner. Diverse dependencies between components of SM models can also be affluently expressed.