USING GRAMMAR-ORIENTED OBJECT DESIGN TO SEAMLESSLY MAP BUSINESS MODELS TO COMPONENT-BASED SOFTWARE ARCHITECTURES

Although current object-oriented analysis and design methods and modeling languages have each a rich set of semantics and syntax to support the modeling of software systems, their support for business modeling has been more limited. In addition, there is no full lifecycle support for the challenges posed by componentbased development and integration (CBDI). The transition and traceability from business models to software component architectures is by no means smooth. This paper explores extensions to current methods to fully support CBDI across the life cycle starting from business modeling and throughout the software development lifecycle. We propose Grammar-oriented Object Design (GOOD) as a method of identifying and mapping reusable subsystems in a business model to a well-mannered component-first software architecture. The latter architecture assumes the modeling and design process is based on an assembly-based paradigm of wiring prebuilt or customized components that have been designed for change and with the intent of repeated long-term reuse and customization.

[1]  Martin Fowler,et al.  Analysis patterns - reusable object models , 1996, Addison-Wesley series in object-oriented software engineering.

[2]  G. Arango Domain analysis: from art form to engineering discipline , 1989, IWSSD '89.

[3]  M. Fox,et al.  Enterprise Modeling , 1998, AI Mag..

[4]  Charles Consel,et al.  Domain-Specific Languages: From Design to Implementation Application to Video Device Drivers Generation , 1999, IEEE Trans. Software Eng..

[5]  Hans-Erik Eriksson,et al.  Business Modeling with UML , 2001 .

[6]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[7]  Paul Allen Realizing e-business with components , 2000 .

[8]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[9]  Bradley P. Allen,et al.  Simplifying the construction of domain-specific automatic programming systems: The NASA automated software development workstation project , 1988 .

[10]  Ali Arsanjani Analysis, Design and Implementation of Distributed Java Business Frameworks Using Domain Patterns , 1999, TOOLS.

[11]  Don Batory,et al.  A Domain Model for Avionics Software * * ADAGE-UT-93-03 May 1993 , 1993 .

[12]  Mark A. Ardis,et al.  Domain engineered configuration control , 2000, SPLC.

[13]  簡聰富,et al.  物件導向軟體之架構(Object-Oriented Software Construction)探討 , 1989 .

[14]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[15]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[16]  Manfred Broy,et al.  What characterizes a (software) component? , 1998, Softw. Concepts Tools.

[17]  D. W. McDavid,et al.  A Standard for Business Architecture Description , 1999, IBM Syst. J..