168 research outputs found
The role of ontologies in creating and maintaining corporate knowledge: a case study from the aero industry
No full textThe Designers’ Workbench is a system, developed to support designers in large organizations, such as Rolls-Royce, by making sure that the design is consistent with the specification for the particular design as well as with the company’s design rule book(s). The evolving design is described against a jet engine ontology. Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench’s knowledge base (KB). This is an error prone and time consuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a tool, ConEditor+ that enables domain experts themselves to capture and maintain these constraints. The tool allows the user to combine selected entities from the domain ontology with keywords and operators of a constraint language to form a constraint expression. Further, we hypothesize that to apply constraints appropriately, it is necessary to understand the context in which each constraint is applicable. We refer to this as “application conditions”. We show that an explicit representation of application conditions, in a machine interpretable format, along with the constraints and the domain ontology can be used to support the verification and maintenance of constraints
ConEditor+: Capture and Maintenance of Constraints in Engineering Design
No full textThe Designers' Workbench is a system, developed to support designers in large organizations, such as Rolls-Royce, by making sure that the design is consistent with the specification for the particular design as well as with the company’s design rule book(s). Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench's knowledge base (KB). This is an error prone and time consuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a tool, ConEditor+ that enables domain experts themselves to capture and maintain these constraints. The tool allows the user to combine selected entities from the domain ontology with keywords and operators of a constraint language to form a constraint expression. Further, we hypothesize that to apply constraints appropriately, it is necessary to understand the context in which each constraint is applicable. We refer to this as "application conditions". We show that an explicit representation of application conditions, in a machine interpretable format, along with the constraints and the domain ontology can be used to support the verification and maintenance of constraints
The role of ontologies in creating and maintaining corporate knowledge : A case study from the aero industry
Full text linkPeer reviewe
Constraint capture and maintenance in engineering design
Full text linkThe Designers' Workbench is a system, developed by the Advanced Knowledge Technologies (AKT) consortium to support designers in large organizations, such as Rolls-Royce, to ensure that the design is consistent with the specification for the particular design as well as with the company's design rule book(s). In the principal application discussed here, the evolving design is described against a jet engine ontology. Design rules are expressed as constraints over the domain ontology. Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench's knowledge base (KB). This is an error prone and time consuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a system, ConEditor+ that enables domain experts themselves to capture and maintain these constraints. Further we hypothesize that in order to appropriately apply, maintain and reuse constraints, it is necessary to understand the underlying assumptions and context in which each constraint is applicable. We refer to them as “application conditions” and these form a part of the rationale associated with the constraint. We propose a methodology to capture the application conditions associated with a constraint and demonstrate that an explicit representation (machine interpretable format) of application conditions (rationales) together with the corresponding constraints and the domain ontology can be used by a machine to support maintenance of constraints. Support for the maintenance of constraints includes detecting inconsistencies, subsumption, redundancy, fusion between constraints and suggesting appropriate refinements. The proposed methodology provides immediate benefits to the designers and hence should encourage them to input the application conditions (rationales)
ConEditor: Tool to Input and Maintain Constraints
No full textWe present a tool which helps domain experts capture and maintain constraints. The tool displays parts of an ontology (as classes, sub-classes and properties) in the form of a tree. A number of keywords and operators from a constraint language are also listed. The tool helps a user to create a constraint expression. Additionally, the tool has a facility which allows the user to input tabular data. The expressed constraints can be converted into a standard format, making them portable. It is planned to integrate this tool, ConEditor, with Designers’ Workbench, a system that supports human designers
Designing a business Plan for a European-Nepalese Fusion Restaurant in Nepal
Full text linkThe author draws up a business plan in this thesis on the basis of research, personal experi-ences and understanding with the intention of implementing it in real life. The main objec-tive of this thesis is to generate a business plan for authors own restaurant. The author intends to establish a European-Nepalese fusion restaurant in Nepal which will serve break-fast, lunch and dinner alongside non-alcoholic beverages.
The theoretical framework of the thesis theories, such as food culture in Nepal and Europe, where European, Nepalese food culture and fusion food trends are briefly discussed. It helps the author to deeply understand both food cultures and the potential of establishing a fusion food restaurant in Nepal. Entrepreneurship provides an idea on how to start and op-erate the business, factors affecting entrepreneurship as well as entrepreneurship opportu-nities in Nepal. The theory section also includes a business plan where the types of a busi-ness plan and its advantages, financial planning in business plan are included. It provides some knowledge about the process of building a business plan for a restaurant and factors to focus on. The business plan teaches the importance of creating a business plan for any company and how it is prepared in relation with the business canvas model. The business model canvas illustrates the key factors of the company which are the most essential factors to start and operate any business.
The research methods used for the development of this thesis are online interview and net-scouting. The online interview was conducted with the owner and manager of Sri Sai palace restaurant and bar located in Jhapa, Nepal, with the concept of obtaining genereal information about planning and opening a new restaurant in Nepal. Similarly, net-scouting was done obout three Nepalese restaurants located in the capital region of Nepal inorder to have an idea about the ideal location, products and services and customers.
The outcome of this thesis helped the author to have a better understanding of creating an effective business plan, how to write it and eventually apply it in the real market. The information collected during the thesis process helped the author to have a better understanding of the factors needed to operate a restaurant. The interview provided specific information to establish and operate a restaurant in Nepal. The results of net-scouting helped the author to focus on the specif areas to ensure the success of the business
Capture and Maintenance of Engineering Design Constraints
No full textThe Designers’ Workbench is a system, developed by the Advanced Knowledge Technologies (AKT) consortium to support designers in large organizations, such as Rolls Royce, by making sure that the design is consistent with the specification for the particular design as well as with the company’s design rule book(s). Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the workbench’s knowledge base (KB). This is an error prone and timeconsuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a tool, ConEditor that enables domain experts themselves to capture and maintain these constraints. The tool allows the user to combine selected entities from the domain ontology with keywords and operators of a constraint language to form a constraint expression. However we hypothesize that to apply constraints appropriately, it is necessary to understand the context in which each constraint is applicable. We refer to this as “application conditions”. We plan to make these application conditions machine interpretable and investigate how they, together with a domain ontology, can be used to support the verification and maintenance of constraints. <br/
Acquisition and Maintenance of Constraints in Engineering Design. In
Full text linkThe Designers' Workbench is a system, developed by the Advanced Knowledge Technologies (AKT) consortium to support designers in large organizations, such as Rolls- Royce, by making sure that a design is consistent with the specification for the particular design as well as with the company’s design rule book(s). Currently, to capture the constraint information, a domain expert (design engineer) has to work with a knowledge engineer to identify the constraints, and it is then the task of the knowledge engineer to encode these into the Workbench's knowledge base (KB). This is an error prone and time consuming task. It is highly desirable to relieve the knowledge engineer of this task, and so we have developed a tool, ConEditor, that enables domain experts themselves to capture and maintain these constraints. The tool allows the user to combine selected entities from the domain ontology with keywords and operators of a constraint language to form a constraint expression. We hypothesize that to apply constraints appropriately, it is necessary to understand the context in which each constraint is applicable. We refer to this as "application conditions". We plan to make these application conditions machine interpretable and investigate how they, together with a domain ontology, can be used to support the verification and maintenance of constraints
Exam as an assessment instrument in computer programming courses
Full text linkAssessment can take many forms, and it can be argued that the greater the diversity in the methods of assessment, the fairer, assessment is to students (Race 2007). The most effective form of assessment is one that appropriately examines the learning outcomes of the module. Assessment methods are also known to play an important role in how students learn (Brown 2004). The traditional assessment approach, in which one single written examination counts towards a student's total score, no longer meets new demands of programming language education (Wang, Li et al. 2012). Students tend to gain higher marks from coursework assignments than they do from examinations (Gibbs and Simpson, 2004). Students consider coursework to be fairer than exams, to measure a greater range of abilities than exams and to allow students to organize their own work patterns to a greater extent (Kniveton, 1996, cited in Gibbs and Simpson, 2004). Do students really hate exams? Are exams ineffective as an assessment approach in computer programming courses? A university wide research survey regarding assessment approaches in computer programming was conducted among students of undergraduate computing courses (including all three levels). 167 students participated in the survey. The author discusses some interesting results obtained from the survey. More than 50% of the students surveyed indicated that they would like examination to be a part of the assessment approach. The author explores possible reasons for this choice by students and compares these results with that of research conducted in other subject areas
Exam as an assessment instrument in computer programming courses: student perceptions
Full text linkAssessment can take many forms, and it can be argued that the greater the diversity in the methods of assessment, the fairer, assessment is to students (Race 2007). The most effective form of assessment is one that appropriately examines the learning outcomes of the module. Assessment methods are also known to play an important role in how students learn (Brown 2004). The traditional assessment approach, in which one single written examination counts towards a student's total score, no longer meets new demands of programming language education (Wang, Li et al. 2012). Students tend to gain higher marks from coursework assignments than they do from examinations (Gibbs and Simpson, 2004). Students consider coursework to be fairer than exams, to measure a greater range of abilities than exams and to allow students to organize their own work patterns to a greater extent (Kniveton, 1996, cited in Gibbs and Simpson, 2004). Do students really hate exams? Are exams ineffective as an assessment approach in computer programming courses? A university wide research survey regarding assessment approaches in computer programming was conducted among students of undergraduate computing courses (including all three levels). 167 students participated in the survey. The author discusses some interesting results obtained from the survey. More than 50% of the students surveyed indicated that they would like examination to be a part of the assessment approach. The author explores possible reasons for this choice by students and compares these results with that of research conducted in other subject areas
- …
