domain engineering


Also found in: Acronyms, Wikipedia.

domain engineering

(systems analysis)
1. The development and evolution of domain specific knowledge and artifacts to support the development and evolution of systems in the domain. Domain engineering includes engineering of domain models, components, methods and tools and may also include asset management.

2. The engineering process of analysing and modelling a domain, designing and modelling a generic solution architecture for a product line within that domain, implementing and using reusable components of that architecture and maintaining and evolving the domain, architecture and implementation models.

3. A reuse-based approach to defining the scope (domain definition), specifying the structure (domain architecture) and building the Assets (requirements, designs, software code, documentation) for a class of systems, subsystems or applications. Domain engineering can include domain definition, domain analysis, developing the domain architecture domain implementation.
Mentioned in ?
References in periodicals archive ?
The traditional technique of domain engineering based on application of electric field by stripe electrodes faces such problems as domain broadening and spontaneous backswitching, which hamper achieving the submicron periods [6, 7].
Industry sector practice varies widely in their domain engineering approaches resulting in diversity in architecture, models and patterns that include their representation.
As an approach of using more advanced software engineering, we also examined the effectiveness of formal methods in requirements development in the domain engineering process in software product line engineering.
For this decade there seems to be a window of opportunity opening from one side increasing demand for formal domain engineering and from the other side from TP more and more gaining industrial relevance.
Domain engineering, like application software engineering, consists of three primary phases: analysis, design, and implementation.
Their topics include a goal and scenario-oriented approach to developing non-functional requirements for a service-oriented application platform, a security requirements engineering tool for domain engineering in software product lines, the model-driven engineering of non-functional properties for pervasive service creation, a unified deployment and management model for dynamic and distributed software architectures, control engineering for scaling service oriented architectures, and biomedical multimedia processing.
Later, Bjorner (2006) developed a complete theory of domain engineering in his three textbooks on engineering principles and techniques of software engineering.
In this paper, authors make use of Service-Oriented Learning Architecture and domain engineering to encourage the use of learning services.