Using domain-driven design to evaluate commercial off-the-shelf software

Wesenberg, Harald; Landre, Einar; Rønneberg, Harald

doi:10.1145/1176617.1176730

Cited by 10 publications

(6 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These three contexts exist inside different legacy systems that must be integrated with DCF. These contexts were identified when we developed a context map for the whole WSC as part of our extended Enterprise Architecture effort [11].…”

Section: Figure 2 Context Map -Digital Cargo Filementioning

confidence: 99%

“…Such software is called generic sub-domain(s). This software should, when practical, be based on commercially available packages [11] or open source offerings.…”

Section: This Moved Out Part Of the Domain Is Called Supporting Domaimentioning

confidence: 99%

“…Figure 4 illustrates how the context map from figure 3 can be reorganized into a layered representation. The placement of contexts in the different layers illustrates the responsibilities found in the WSC [11].…”

Section: Large Scale Structuresmentioning

confidence: 99%

“…The experience with use of responsibility layers from the COTS evaluation [11] indicate that use of responsibility layers simplifies communication with stake holders, because they reduce perceived complexity by introduction of more order [5]. …”

Section: Large Scale Structuresmentioning

confidence: 99%

“…The main cause driving the Enterprise Architecture effort in the Wet Supply Chain is the need to replace a set of large legacy systems with a combination of commercial packages [11] and custom made solutions. The replacement is motivated by new business requirements that can not be met within functional and technical architectures of the existing systems.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Architectural improvement by use of strategic level domain-driven design

Landre

Wesenberg

Rønneberg

2006

Companion to the 21st ACM SIGPLAN Symposium on Object-Oriented Programming Systems, Languages, and Applications

Self Cite

View full text Add to dashboard Cite

In this paper we present the experience gained and lessons learned when the IT department at Statoil ASA, a large Oil and Gas company in Norway, extended their Enterprise Architecture with strategic level Domain-Driven design techniques and used the extended Enterprise Architecture to improve the software architecture of a large enterprise system.Traditionally, Enterprise Architecture has been prescribed as the key tool to conquer complexity and align IT development with business priorities and strategies, but we found our Enterprise Architecture too coarse to be practical useful at the software level.By extending our Enterprise Architecture with context maps and the process of context mapping valuable insight was gained, insight that enabled better scoping of new projects and architectural improvement of existing software in a controlled way.In addition, use of responsibility layers combined with context maps reduces the perceived complexity of the architecture. Use of other techniques such as distillation and identification of the core domain looks promising at the tactical level of a single project, but its value is more uncertain at the strategic level.The key issue is that large enterprise systems do not have a single core. On the other hand, at the project level, there should always be a core, and the project is best of by knowing its core domain and aim its best resources to work with the core.

show abstract

Section: Figure 2 Context Map -Digital Cargo Filementioning

confidence: 99%

“…Such software is called generic sub-domain(s). This software should, when practical, be based on commercially available packages [11] or open source offerings.…”

Section: This Moved Out Part Of the Domain Is Called Supporting Domaimentioning

confidence: 99%

Section: Large Scale Structuresmentioning

confidence: 99%

Section: Large Scale Structuresmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Architectural improvement by use of strategic level domain-driven design

Landre

Wesenberg

Rønneberg

2006

Companion to the 21st ACM SIGPLAN Symposium on Object-Oriented Programming Systems, Languages, and Applications

Self Cite

View full text Add to dashboard Cite

show abstract

Role of Process Modeling in Software Service Design

Patig

Wesenberg

2009

Service-Oriented Computing – ICSOC 2007

Self Cite

View full text Add to dashboard Cite

Service-oriented architecture technically facilitates business process management as it enables software to evolve along with changing business processes by simply recomposing software services. From a theoretical point of view it is, thus, natural to take business processes as a starting point for software service design. However, deriving software services strictly top-down from business processes is awkward from a practical point of view: The resulting services are too fine-grained in scope and too vast in number, and particular process control flows become cemented in service orchestrations. In this paper, another approach of software service design is described that, though starting from process models, avoids these drawbacks. The approach is illustrated by a practical example. The presented service design approach has been successfully applied in industry for more than 14 years and enables agile service implementation.

show abstract

The Investigation of WEB Software System Based on Domain-Driven Design

Wang

Zhou

et al. 2011

Web Information Systems and Mining

View full text Add to dashboard Cite

Using domain-driven design to evaluate commercial off-the-shelf software

Cited by 10 publications

References 3 publications

Architectural improvement by use of strategic level domain-driven design

Architectural improvement by use of strategic level domain-driven design

Role of Process Modeling in Software Service Design

The Investigation of WEB Software System Based on Domain-Driven Design

Contact Info

Product

Resources

About