• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.155-168
• /
• 2006

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

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

This research introduces the architecture of managing products based software. There are many of the architectures for managing products using software instead of manpower. In case of MVC and existing architectures, The architectures transfer redundant data so the architectures cause a problem that unnecessary data moved. This research presents VMDC(View, Model, Dispatcher, Controller) architecture to solve the problem. Dispatcher of VMDC grasps necessary data and reconstructs objects to efficient transferring data. This research shows usecase that designed VMDC(View, Model, Dispatcher, Controller) and demonstrate efficiency of VMDC(View, Model, Dispatcher, Controller) together. after demonstration this research present with next research.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.11
• /
• pp.101-110
• /
• 2021

The Weapon Control Software performs the function of supporting weapon operation within the Naval Combat System in connection with the Weapon System. As Weapon Control Software depends on an Weapon System, it has the characteristic that software modification is unavoidable with the change in Interface information. Modification of software causes an increase in development costs since it must take verification step such as software reliability test. In this paper, We design the standard architecture of weapon control software to minimize the modification elements of existing weapon control software. For Interface information management, Feature Model were applied to make a division between common factor and variable factor. In addition, Strategy Pattern were applied to improve the software design. Software evaluation test results show that new architecture provides better modifiability and reuse than existing software as well as the cost of development decrease.

• 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.5 no.1
• /
• pp.123-134
• /
• 2000

Over the past several decades, several architectural approaches have been applied to develop Information Systems, The software architectural model has been recognized as one of the most important methods for improving productivity. Most conceptual models are difficult to understand and interpret at various system models. As a consequence, conceptual models of many Information Systems fail to represent, exploit, and apply to various aspects, which is needed for reducing development step of the architecture. In this paper, we will explain the architectural model as the 4＋1 View of UML. This model integrates the Knowledge Management System into five views： the Logical View, the Process View, the Deployment View, Implementation View, and the Use-Case View. Moreover, this paper will not only provide information on the application of the software architectural model by stakeholders, but also ultimately improve productivity.

• Journal of KIISE:Software and Applications
• /
• v.29 no.5
• /
• pp.295-310
• /
• 2002

Software architecture representing a common high-level abstraction of a system can be used as a basis for creating mutual understanding among all stakeholders of the system. In determining a software architecture's fitness with respect to its desired qualities as well as in improving a software architecture, software architecture evaluation is importantly performed. However moat of architecture evaluation methods are not still sufficient in that they do not explicitly consider artifacts discussed during architecture evaluation and their processes are net systematic. As a result, we are hard to follow them. To address these problems, this paper presents the method to evaluate systematically a software architecture with respect to its desired qualities. In this approach, the functional and non-functional requirements are separately handled, and software architecture is represented in the 4+1 view model using UML. Through this initial consideration, the important artifacts such as goals, scope, and target of evaluation are clearly determined. Also, the method provides the well defined process to produce the important evaluation artifacts such as sub-designs, design decisions, rationale, qualities from inputs. In addition, it enables us to determine satisfaction of a architecture with respect its desired qualities or improve a architecture through the structured evaluation results.

• Journal of KIISE
• /
• v.42 no.3
• /
• pp.341-360
• /
• 2015

While architectural patterns provide software development solutions by providing schemas for structural organizations of software systems based on empirical knowledge, Jackson's problem frames provide a method of analyzing software problems. Problem frames are useful to understanding the software development problem, by putting emphasis on the problem domain, rather than on the solution space. Research exists that relates problem frames and software architecture, but most of this research uses problem frames only to understand given problems. Moreover, none of the existing research derives architectural patterns by considering both problem frames and quality attributes. In this paper, we propose a software architecture design method for pattern-based architecture design, by matching problem frames and architectural patterns. To that end, our approach first develops the problem model based on the problem frames approach, and then uses it to match with candidate architectural patterns, from the perspectives of both functionality, and quality attributes. Functional matching uses the problem frame diagram to match the problem model of an architectural pattern. We conduct a case study to show that our approach can systematically decide the right architectural patterns, and provide a basis for fine-grained software architecture design.

• Journal of the Korea Society of Computer and Information
• /
• v.14 no.3
• /
• pp.149-159
• /
• 2009

Nowadays, as the importance of service-oriented architecture software is recognized, the market of service-oriented software is getting bigger. In response to this, the requirements of high reliability and quality about service-oriented architecture software is getting increased. In this research, we clearly suggested the evaluation method by giving a specific evaluation example to evaluate the reliability qualify of service-oriented architecture software. It is expected to raise the objectivity and the utilization by inducing the reliability qualify improvement from this research.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.1
• /
• pp.117-124
• /
• 2002

In software development process, appropriate design can exist more than one. And software architectures can be restructured by modification and update during design processes. Therefore, the method that specify efficiently the modification elements of architectures, and manage different versions of architecture designed through various aspects is required. In this study, we propose software architecture restructuring mechanism that can restructure legacy architecture and a new software architecture designed with reuse of it in integrated form, and define specification elements and structure of the proposed restructured architecture specification. It provides the method that can reference and reuse architectures designed with various aspects of developers in architecture design processes. In addition, it supports flexible specification method for specification of modification elements such as revision, substitution, update of legacy software architecture.