engineering domain

Top PDF engineering domain:

CivilOnto: An Ontology Based on Persian Articles Published in Civil Engineering Domain

CivilOnto: An Ontology Based on Persian Articles Published in Civil Engineering Domain

The present research aims to represent the terms and concepts of civil engineering and thus design its domain structure in the form of ontology. This is an applied research and the qualitative content analysis method with summative approach is used. The research population is 12309 published articles in the scientific journals (1983 to 2016), indexed in the full-text Persian articles database at Regional Information Center for Science and Technology (RICeST). Data collection was done via SQL queries from the RICeST database. The content analysis was used to create a conceptual model of the civil engineering domain and to explain the relationships and instances. To create the conceptual model, there were consulted with 10 Subject experts in civil engineering area. The process of ontology creation has been done through METHONTOLOGY methodology and protégé ontology management software (Beta 5 edition). The made-artifact of this research has 283 concepts, along with 62 object properties, 79 data type properties, 10 annotative properties, and 976 instances. In total, in the present research, 151 semantic properties were identified between the concepts. The results of this research can serve as a guide for the RICeST experts in order to identify the users’ needs and facilitate the users’ interaction with RICeST databases. This can also provide the users with access to more relevant resources. This ontology can also be served as a layer of semantic web in these databases.
Show more

21 Read more

Ontology of Domains  Ontological Description Software Engineering Domain—The Standard Life Cycle

Ontology of Domains Ontological Description Software Engineering Domain—The Standard Life Cycle

Basic concepts and notions of ontological description of domains are implemented in the concep- tual model being understandable to ordinary users of this domain. Ontological approach is used for the presentation of software engineering domain—Life Cycle (LC) ISO/IEC 12207 with the aim to automate LC processes and to generate different variants of LC for development systems. And the second aim of Conceptual Model must teach the student to standard process LC, which includes general, organizational and supported processes. These processes are presented in graphical terms of DSL, which are transformed to XML for processing systems in the modern environment (IBM, VS.Net, JAVA and so on). The testing process is given in ontology terms of Protégé systems, and semantics of tasks of this process is implemented in Ruby. Domain ontology LC is displayed by the several students of MIPT Russia and Kiev National University as laboratory practicum course “Software Engineering”.
Show more

15 Read more

AuTopEx: Automated Topic Extraction Techniques Applied in the Software Engineering Domain

AuTopEx: Automated Topic Extraction Techniques Applied in the Software Engineering Domain

To answer ”RQ 3: How well does the approach of using Latent Dirichlet Allocation (with suit- able pre-processing) perform compared to a manual method?” We assume that the human per- formance is perfect, since that is what is accepted and applied today in the Software Engineering domain. So when looking at the amount of false negatives stored (the amount of topics that should have been returned by the machine, but were not) in these two confusion matrices. The full-text gives us 36 and the title, ab- stract and keyword set 54. So that tells us that full-text data set returns the relevant topics more often than the title, abstract and keywords data set. So the full-text missed 36 topics that the humans had deemed relevant and the title, abstract and keyword missed 54. This is the indication of how much the humans and the algo- rithm disagree
Show more

37 Read more

Comparison of Example based Learning and Problem based Learning in Engineering Domain

Comparison of Example based Learning and Problem based Learning in Engineering Domain

this method is fruitful only if applied to the right persons (e.g., expert learners) and at the right time (e.g., after learners have gained sufficient content knowledge). It has been argued that PBL is not suitable for novice learners (see [5]). The reason that PBL is less efficient and less effective for novice learners is that PBL is a minimally guided learning strategy which assumes knowledge can best be learnt through experience based on the procedures of the discipline. Unguided or minimally guided instructions are usually less beneficial for novice learners because it provides inadequate guidance to the learners during the process of learning. The learners, therefore, might acquire misconception, incomplete, and disorganised domain knowledge [6].
Show more

7 Read more

REQUIREMENTS ENGINEERING DOMAIN KNOWLEDGE IN INFORMATION TECHNOLOGY

REQUIREMENTS ENGINEERING DOMAIN KNOWLEDGE IN INFORMATION TECHNOLOGY

From the above it follows that specifications can be said to satisfy requirements only when incorporating domain knowledge. The domain knowledge basically guides us to the scope of relevant domain. More specifically, a specification together with relevant domain knowledge should be sufficient to guarantee that requirements are satisfied. This is formalized in Zave and Jackson :K,Sj-R Where K is a description of the problem domain, S is the specification of the solution, and R is the problem requirement. Parnas and Madey take the approach that requirements are in essence constraints imposed on the environment. They define the relation they designated as REQ, which incorporates constraints on the environmental quantities. Specifically Pamas and Meday define in the System Requirements Document environmental quantities, which are measured or controlled by the computer system. This document includes a specification on each environmental quantity as either monitored (aquantity that the system needs to measure), controlled (a quantity that the system needs to control), or both. The environment knowledge incorporated in this document can be described by a relation defined by Pamas and Madey as the NAT relation (standing for Nature):
Show more

8 Read more

Domain Engineering: A Conceptual Model of the Software Application Architecture

Domain Engineering: A Conceptual Model of the Software Application Architecture

Domain is the business functional workout area to be designed in the mode of discrete component, domain workout area is a conceptual representation of the business logic and rules and real situation objects in the domain, here domain is also called conceptual model of the requirement engineering. In software development requirements must start with domain modeling and business workout area is formulated by the domain modeling for software application architecture. Before requirements can be defined the application domain must be defined. Here domain is the initial conceptual model of the requirement engineering. Domain classify with vertical and horizontal method to prove number of modules in hierarchical mechanism with interface in vertical method and functionalities of the each modules is defined in horizontal method. Domain engineering directly support to the acquiring business rule, logic and functionalities. As well as define the requirement elicitation and specification using tools and techniques of the domain engineering. Using this the physical objectization is extracted. In this paper we outline the basic facets of objectization from domains.
Show more

9 Read more

Requirements-Level Language and Tools for Capturing Software System Essence

Requirements-Level Language and Tools for Capturing Software System Essence

Abstract. Creation of an unambiguous requirements specification with precise domain vocabulary is crucial for capturing the essence of any software system, either when developing a new system or when recov- ering knowledge from a legacy one. Software specifications usually main- tain noun notions and include them in central vocabularies. Verb or ad- jective phrases are easily forgotten and their definitions buried inside im- precise paragraphs of text. This paper proposes a model-based language for comprehensive treatment of domain knowledge, expressed through constrained natural language phrases that are grouped by nouns and in- clude verbs, adjectives and prepositions. In this language, vocabularies can be formulated to describe behavioural characteristics of a given prob- lem domain. What is important, these characteristics can be linked from within other specifications similarly to a wiki. The application logic can be formulated through sequences of imperative subject-predicate sentences containing only links to the phrases in the vocabulary. The paper presents an advanced tooling framework to capture application logic specifications making them available for automated transformations down to code. The tools were validated through a controlled experiment.
Show more

26 Read more

The Experience of Implementing Model-Driven Engineering Tools in the Process Control Domain

The Experience of Implementing Model-Driven Engineering Tools in the Process Control Domain

house and it contains process-centric abstractions, a sophisticated behavioral model for these abstractions, and explicit modeling of the dependencies between them [8]. ProcGraph has been successfully used as a modeling (specification) language over the past 15 years in more than 20 industrial projects, ranging in size from a couple of hundred to a couple of thousand signals. In the second level (application engineering), the process control software is engineered using the results of the infrastructure level. The application- engineering level uses the infrastructure for the development of process control software. The infor- mation flow from the application-engineering level to the infrastructure-engineering level incorporates the knowledge that is being accumulated during the application-development process. This information can be potentially generalized and incorporated into new versions of the infrastructure, which would further improve the application engineering or extend the range (i.e., the variability) of the software that can be engineered.
Show more

13 Read more

Palmprint Recognition Based on Fusion of Spatial and Transform Domain Features

Palmprint Recognition Based on Fusion of Spatial and Transform Domain Features

The physiological palmprint biometric trait is used to identify a person effectively. In this paper, palmprint recognition is based on fusion spatial and transform domain features is proposed. The spatial domain features are extracted from resized palmprint images using LBP. The DWT is applied on palmprint images and LL band is considered for further processing. The SWT is used to extract transform domain features from LL band of DWT. The performance parameters are computed using spatial and transform domain techniques. The OTSR of spatial and transform domain techniques. The OTSR of spatial and transform domain techniques are fused using normalization technique to obtain better results. It is observed that the performance of the proposed method is better than the existing methods.
Show more

15 Read more

Domain engineering to ensure flexibility on interaction laws of multi-agent systems

Domain engineering to ensure flexibility on interaction laws of multi-agent systems

Law enforcement approaches have been proposed to promote dependability in open multi-agent systems. Interaction laws are defined and then enforced to promote predictability. As new software demands and requirements appear, the system and its interaction laws must evolve to support those changes. The purpose of domain engineering is to produce a set of reusable assets for a family of systems, which are then used to build concrete members of the family. Flexibility is the ease with which a system or component can be modified for use in applications other than those for which it was originally designed. In this paper, we discuss how the MLaw infrastructure was designed to support interaction law evolution providing support to produce a set of reusable laws for a family of systems. As an example, we have implemented two customizable applications in the area of electronic negotiation expressed as an open system environment.
Show more

12 Read more

Light induced ferroelectric domain engineering in lithium niobate & lithium tantalate

Light induced ferroelectric domain engineering in lithium niobate & lithium tantalate

4. Domain engineering is freed from the hexagonal constraints of the domain shapes produced by EFP. Straight domain walls along arbitrary directions and curved domain walls are all possible, as evidenced by high-magnification SEM imaging. From the results presented above, there are several intuitive trends governing the three main exposure conditions of intensity, electric field, and illumination time. In the direct- write of domain structures, a parameter of dwell time (or alternatively, scanning speed ) replaced the parameter of illumination time. In general, an increase in any or all of these parameters will result in further growth and/or spreading of a domain. With a suitably small applied E-field (determined by the dark nucleation field and dark poling properties of the material), exposed regions grew to a maximum size governed by the beam size and exposure conditions, and thereafter appeared to grow no further. According to the plot of Figure 6.16, the domains continued to expand, but followed a logarithmic profile with illumination time. Under low exposure conditions, surface domains formed with depths that were suitable for waveguiding applications. Pushing surface domains through to the +z face may be possible in a controlled manner by increasing an exposure parameter, or by later pulsed-E-field poling. Under higher exposure conditions, bulk domains extending throughout the thickness of the crystal were also possible. However, hexagonal domain shapes were reasserted particularly when using a high E-field, with a rule-of-thumb transition point near ∼1 kV for 0.5-mm thick Mg:CLN.
Show more

212 Read more

Action semantics applied to model driven engineering

Action semantics applied to model driven engineering

Action semantics [Mos96] occupies the middle of the gap between a domain and mathematical constructs. The specifications are in a readable and English like syntax, modular and composable to ease the construction and usage of the semantics. The level of abstraction is higher than mathematical approaches by introducing common computational concepts, such as storage and abstractions. The aim of action semantics is to produce formal semantic specifications that reflect ordinary computational concepts and are easy to read, understand and compose. Thus a formalization framework that is both precise and pragmatic. Action semantics originates from the field of specifying semantics for program- ming languages. It has been used to specify the semantic definitions for Pascal, ADA, Java and ML [Wat09]. Because of its origin with programming languages action semantics is designed to work with grammars and abstract syntax trees. In MDE metamodels and models serve the same purpose but are different by being object-oriented and being graphs rather than trees.
Show more

111 Read more

Comparison of intra-domain traffic engineering methods

Comparison of intra-domain traffic engineering methods

There is a common belief that multiple weight changes disturb network more than single weight change because multiple weight change events take a longer time to flood. It may be true in the sense of the queuing delay (although more LSps only cause an insignificant increase in the queuing delay). However, it is not true in the sense of the transmission time. The completion time of flooding all LSPs caused by the multiple weight changes is the same as the completion time of flooding an LSP which travels the most number of links. It implies that multiple weight changes do not necessarily increase the transmission time. Therefore, the impact in terms of transmission time due to multiple weight changes might be the same (or even less) than a single weight change in an extreme scenario (imagine when multiple weight changes happen in the centre of network, and a single weight change does in the edge of network). Interaction with Inter-Domain Problem: It is possible that the exit point of the AS outgoing (inter-AS) traffic changes when a link weight is altered. This happens when the “hot-potato” routing, which selects the nearest exit point based on IGP metric, is used to route the inter-AS traffic. This must be taken into consideration because according to measurement study in Sprint backbone network [2], 70% of traffic can be potentially affected by hot-potato routing. Recent study, such as [7], considers the joint optimisation of intra-domain and inter-domain routing. However, this may only be applicable to Tier-1 ISPs which have many connectivity to the Internet backbone. Hot potato routing may not be relevant at all for lower level ISPs.
Show more

8 Read more

Protein stability engineering insights revealed by domain-wide comprehensive mutagenesis

Protein stability engineering insights revealed by domain-wide comprehensive mutagenesis

The accurate prediction of protein stability upon sequence mutation is an important but unsolved challenge in protein engineering. Large mutational datasets are required to train computational predictors, but traditional methods for collecting stability data are either low-throughput or measure protein stability indirectly. Here, we develop an automated method to generate thermodynamic stability data for nearly every single mutant in a small 56-residue protein. Analysis reveals that most single mutants have a neutral effect on stability, mutational sensitivity is largely governed by residue burial, and unexpectedly, hydrophobics are the best tolerated amino acid type. Correlating the output of various stability prediction algorithms against our data shows that nearly all perform better on boundary and surface positions than for those in the core, and are better at predicting large to small mutations than small to large ones. We show that the most stable variants in the single mutant landscape are better identified using combinations of two prediction algorithms, and that including more algorithms can provide diminishing returns. In most cases, poor in silico predictions were tied to compositional differences between the data being analyzed and the datasets used to train the algorithm. Finally, we find that strategies to extract stabilities from high- throughput fitness data such as deep mutational scanning are promising and that data produced by these methods may be applicable toward training future stability prediction tools.
Show more

46 Read more

Human IgG Fc domain engineering enhances antitoxin neutralizing antibody activity

Human IgG Fc domain engineering enhances antitoxin neutralizing antibody activity

human tissues. So, our findings, obtained with the use of FcγR-hu- manized mice, are physiologically relevant to the context of human B. anthracis infection. Additionally, we showed that the in vivo neu- tralization activity of mouse-human chimeric 19D9 mAb offers significant advantages over conventional strategies using wild-type mice, thus allowing the precise characterization of the activity of Fc domain variants with altered capacity to engage specific classes of human FcγRs. Most importantly, our findings establish that it is possible to enhance the toxin-neutralizing activity of an anti- body by manipulating Fc-mediated interactions. Indeed, increased endocytic uptake of mAb-opsonized PA by augmented engagement of activating FcγRs on effector cells could prevent furin-mediated cleavage of PA and the subsequent assembly of the anthrax LeTx (1, 10). That finding in turn suggests strategies for designing more effective therapeutic antibodies for toxin neutralization and vac- cines that elicit superior toxin-neutralizing responses through the production of antibodies that engage activating FcγRs.
Show more

6 Read more

Exploring Knowledge Engineering Strategies in Designing and Modelling a Road Traffic Accident Management Domain

Exploring Knowledge Engineering Strategies in Designing and Modelling a Road Traffic Accident Management Domain

In this paper we have developed requirements for a new plan- ning domain, the RTA domain, addressing the problem of managing emergency situations in road traffic accidents. We have elicited a set of requirements, and used domain analy- sis to make precise and unambiguous relevant features for the planning problem. We then described two methods used for formulating requirements into domain models, and set up an evaluation experiment where they were used to design and create RTA domain models. Special attention was given to knowledge engineering aspects such as how long it takes to create a model or which tools can be used to verify the model. We observed that creating different models does not take very different amounts of time (taking into account the developers’ expertise). We also noticed that most of the existing domain- independent planners do not support many features required for modelling real world situations: i.e., negative precondi- tions and durative actions. This is, clearly, a big limitation for their application. The main outcome from our work to feed back to tools developers is to provide facilities to couple plan- ning engines and formulation tools (see [Shah et al., 2013] for more details of such lessons learned).
Show more

8 Read more

ProcDSL + ProcEd - a Web-based Editing Solution for Domain Specific Process-Engineering

ProcDSL + ProcEd - a Web-based Editing Solution for Domain Specific Process-Engineering

As input and output, an instance of the above defined gram- mar is used. After upload, the ASG is constructed from the file through the MontiCore-generated tools, although these objects are kept separate from the ones behind the displayed items. This separation enables us to replace both sides, grammar-generated objects and data-objects, with- out changing much at the corresponding one in case an engineering- or design-related update is necessary. No in- stance of an ASG-object is kept in a visualizable one and vice versa to achieve a very clean separation between the two worlds. Since the editor does not get any display-related information from the grammar, it has to decide itself on the positioning and use of visual elements such as icons, colors, etc.
Show more

5 Read more

Domain Engineering for Enhanced Ferroelectric Properties of Epitaxial (001) BiFeO Thin Films

Domain Engineering for Enhanced Ferroelectric Properties of Epitaxial (001) BiFeO Thin Films

distortion along one of the four (111) crystallographic directions of the pseudocubic perovskite unit cell. [6] Thus, eight possible polarization (ferroelectric) variants, which correspond to four structural (ferroelastic) domains, may form in the films, leading to complex domain patterns with both {100} and {101} twin boundaries. [6,7] Such a complex domain structure can deteriorate the ferroelectric response of the system by external electric field, and complicates the examination of the coupling between magnetic and ferroelectric order parameters in BiFeO 3 . [3]

7 Read more

Observability of Software Engineering Processes in Open Source Software Projects Domain

Observability of Software Engineering Processes in Open Source Software Projects Domain

engineering processes. Step 3: Appropriate data analysis approach. In this step, we commit appropriate analysis approaches based on the collected and validated data from step 1. For example, by using health indicators approach we make analysis on two indicators, namely the service delay and the proportion of the developer contribution. In OSS project, we define the service delay as a function of time to respond and time to resolve an issue/bug. The proportion of the developer contribution is very important to obtain an outlook of software creation performance and the current developers’ motivation state. Both indicators are derived from the aggregation of metrics, which at the lowest level the metrics are obtained by mining the project repositories.
Show more

9 Read more

An Improved Blood Splatters Analysis Technique

An Improved Blood Splatters Analysis Technique

The domain of computation and their applications are expanding day by day. Among various application domains of computations now in these days in forensic science it also becomes popular. Basically the forensic science is a domain or subject of investigation of criminal activities. That is responsible for preservation, investigation and collection of criminal facts that helps to explore the crime. In this proposed work the domain of forensic science is key area of study and fact collection. In addition of that the effort is made in order to provide enhance and efficient approach for finding the blood splatter trajectory.
Show more

8 Read more

Show all 10000 documents...