The Experts below are selected from a list of 12231 Experts worldwide ranked by ideXlab platform
Phillip Lord - One of the best experts on this subject based on the ideXlab platform.
-
a document centric approach for developing the tolapc ontology
Journal of Biomedical Semantics, 2017Co-Authors: Aisha Blfgeh, Jennifer D Warrender, Catharien M U Hilkens, Phillip LordAbstract:Background There are many challenges associated with ontology building, as the process often touches on many different subject areas; it needs knowledge of the problem domain, an understanding of the ontology formalism, software in use and, sometimes, an understanding of the philosophical background. In practice, it is very rare that an ontology can be completed by a single person, as they are unlikely to combine all of these skills. So people with these skills must collaborate. One solution to this is to use face-to-face meetings, but these can be expensive and time-consuming for teams that are not co-located. Remote collaboration is possible, of course, but one difficulty here is that domain specialists use a wide-variety of different “formalisms” to represent and share their data – by the far most common, however, is the “office file” either in the form of a Word-Processor document or a spreadsheet. Here we describe the development of an ontology of immunological cell types; this was initially developed by domain specialists using an Excel spreadsheet for collaboration. We have transformed this spreadsheet into an ontology using highly-programmatic and pattern-driven ontology development. Critically, the spreadsheet remains part of the source for the ontology; the domain specialists are free to update it, and changes will percolate to the end ontology.
-
a document centric approach for developing the tolapc ontology
Journal of Biomedical Semantics, 2017Co-Authors: Aisha Blfgeh, Jennifer D Warrender, Catharien M U Hilkens, Phillip LordAbstract:Background There are many challenges associated with ontology building, as the process often touches on many different subject areas; it needs knowledge of the problem domain, an understanding of the ontology formalism, software in use and, sometimes, an understanding of the philosophical background. In practice, it is very rare that an ontology can be completed by a single person, as they are unlikely to combine all of these skills. So people with these skills must collaborate. One solution to this is to use face-to-face meetings, but these can be expensive and time-consuming for teams that are not co-located. Remote collaboration is possible, of course, but one difficulty here is that domain specialists use a wide-variety of different “formalisms” to represent and share their data – by the far most common, however, is the “office file” either in the form of a Word-Processor document or a spreadsheet. Here we describe the development of an ontology of immunological cell types; this was initially developed by domain specialists using an Excel spreadsheet for collaboration. We have transformed this spreadsheet into an ontology using highly-programmatic and pattern-driven ontology development. Critically, the spreadsheet remains part of the source for the ontology; the domain specialists are free to update it, and changes will percolate to the end ontology.
Mark D Corner - One of the best experts on this subject based on the ideXlab platform.
-
chameleon application level power management
IEEE Transactions on Mobile Computing, 2008Co-Authors: Prashant Shenoy, Mark D CornerAbstract:In this paper, we present Chameleon an application-level power management approach for reducing energy consumption in mobile Processors. By using application domain knowledge, as opposed to OS-level or hardware-level inferred knowledge, Chameleon can substantially reduce CPU energy consumption. By exporting the energy management to user-space, designers can design more flexible and easily portable algorithms and systems, and use multiple energy management policies simultaneously. Specifically, we propose a minimal operating system interface that applications use to obtain global knowledge from the kernel in order to make local decisions. We consider three classes of applications soft real-time, interactive and batch and design user level power management strategies for representative applications such as a movie player, a Word Processor, a web browser, and a batch compiler. Our experiments show that, compared to the traditional system-wide CPU voltage scaling approaches, Chameleon can achieve up to 32-50% energy savings while delivering comparable or better performance to applications. Similarly, Chameleon extracts 9-41% more energy when compared to Grace OS, which uses some application knowledge but operates within the kernel. Further, Chameleon imposes minimal overhead and is effective at scheduling concurrent applications with diverse energy needs.
-
chameleon application level power management with performance isolation
ACM Multimedia, 2005Co-Authors: Xiaotao Liu, Prashant Shenoy, Mark D CornerAbstract:In this paper, we present Chameleon---an application-level power management approach for reducing energy consumption in mobile Processors. Our approach exports the entire responsibility of power management decisions to the application level. We propose an operating system interface that can be used by applications to achieve energy savings. We consider three classes of applications---soft real-time, interactive and batch---and design user-level power management strategies for representative applications such as a movie player, a Word Processor, a web browser, and a batch compiler. We also design a user level power manager based on GraceOS using Chameleon. We implement our approach in the Linux kernel running on a Sony Transmeta laptop. Our experiments show that, compared to the traditional system-wide CPU voltage scaling approaches, Chameleon can achieve up to 32-50% energy savings while delivering comparable or better performance to applications. Further, Chameleon imposes small overheads and is very effective at scheduling concurrent applications with diverse energy needs.
R F Coyne - One of the best experts on this subject based on the ideXlab platform.
-
Using an issue-based model in a team-based software engineering course
2018Co-Authors: A H Dutoit, Bernd Bruegge, R F Coyne, Carnegie Mellon University.engineering Design Research Center.Abstract:Abstract: "Communication in software engineering projects becomes a bottleneck as the number of participants increases. As today's software systems grow in complexity and size, teaching effective communication skills in software engineering courses becomes a critical issue. This paper is an experience report on the use of a [sic] issue-based model for teaching meeting procedures in a team-based software engineering project course (7 teams, 25 students). We observed that, when carefully introduced in the classroom, the use of an issue-based model provided significant benefits, even with such limited tool support as a Word Processor template. More specifically, we observed that students conducted meetings more efficiently, that they maintained a more complete record of the issues under discussion, and that intra-team communication was significantly improved.
-
using an issue based model in a team based software engineering course
International Conference on Software Engineering, 1996Co-Authors: A H Dutoit, Bernd Bruegge, R F CoyneAbstract:Communication in software engineering projects becomes a bottleneck as the number of participants increases. As today's software systems grow in complexity and size, teaching effective communication skills in software engineering courses becomes a critical issue. The paper is an experience report on the use of an issue based model for teaching meeting procedures in a team based software engineering project course (7 teams, 25 students). We observed that, when carefully introduced in the classroom, the use of an issue based model provided significant benefits, even with such limited tool support as a Word Processor template. More specifically, we observed that students conducted meetings more efficiently, that they maintained a more complete record of the issues under discussion, and that intra team communication was significantly improved.
Aisha Blfgeh - One of the best experts on this subject based on the ideXlab platform.
-
a document centric approach for developing the tolapc ontology
Journal of Biomedical Semantics, 2017Co-Authors: Aisha Blfgeh, Jennifer D Warrender, Catharien M U Hilkens, Phillip LordAbstract:Background There are many challenges associated with ontology building, as the process often touches on many different subject areas; it needs knowledge of the problem domain, an understanding of the ontology formalism, software in use and, sometimes, an understanding of the philosophical background. In practice, it is very rare that an ontology can be completed by a single person, as they are unlikely to combine all of these skills. So people with these skills must collaborate. One solution to this is to use face-to-face meetings, but these can be expensive and time-consuming for teams that are not co-located. Remote collaboration is possible, of course, but one difficulty here is that domain specialists use a wide-variety of different “formalisms” to represent and share their data – by the far most common, however, is the “office file” either in the form of a Word-Processor document or a spreadsheet. Here we describe the development of an ontology of immunological cell types; this was initially developed by domain specialists using an Excel spreadsheet for collaboration. We have transformed this spreadsheet into an ontology using highly-programmatic and pattern-driven ontology development. Critically, the spreadsheet remains part of the source for the ontology; the domain specialists are free to update it, and changes will percolate to the end ontology.
-
a document centric approach for developing the tolapc ontology
Journal of Biomedical Semantics, 2017Co-Authors: Aisha Blfgeh, Jennifer D Warrender, Catharien M U Hilkens, Phillip LordAbstract:Background There are many challenges associated with ontology building, as the process often touches on many different subject areas; it needs knowledge of the problem domain, an understanding of the ontology formalism, software in use and, sometimes, an understanding of the philosophical background. In practice, it is very rare that an ontology can be completed by a single person, as they are unlikely to combine all of these skills. So people with these skills must collaborate. One solution to this is to use face-to-face meetings, but these can be expensive and time-consuming for teams that are not co-located. Remote collaboration is possible, of course, but one difficulty here is that domain specialists use a wide-variety of different “formalisms” to represent and share their data – by the far most common, however, is the “office file” either in the form of a Word-Processor document or a spreadsheet. Here we describe the development of an ontology of immunological cell types; this was initially developed by domain specialists using an Excel spreadsheet for collaboration. We have transformed this spreadsheet into an ontology using highly-programmatic and pattern-driven ontology development. Critically, the spreadsheet remains part of the source for the ontology; the domain specialists are free to update it, and changes will percolate to the end ontology.
A H Dutoit - One of the best experts on this subject based on the ideXlab platform.
-
Using an issue-based model in a team-based software engineering course
2018Co-Authors: A H Dutoit, Bernd Bruegge, R F Coyne, Carnegie Mellon University.engineering Design Research Center.Abstract:Abstract: "Communication in software engineering projects becomes a bottleneck as the number of participants increases. As today's software systems grow in complexity and size, teaching effective communication skills in software engineering courses becomes a critical issue. This paper is an experience report on the use of a [sic] issue-based model for teaching meeting procedures in a team-based software engineering project course (7 teams, 25 students). We observed that, when carefully introduced in the classroom, the use of an issue-based model provided significant benefits, even with such limited tool support as a Word Processor template. More specifically, we observed that students conducted meetings more efficiently, that they maintained a more complete record of the issues under discussion, and that intra-team communication was significantly improved.
-
using an issue based model in a team based software engineering course
International Conference on Software Engineering, 1996Co-Authors: A H Dutoit, Bernd Bruegge, R F CoyneAbstract:Communication in software engineering projects becomes a bottleneck as the number of participants increases. As today's software systems grow in complexity and size, teaching effective communication skills in software engineering courses becomes a critical issue. The paper is an experience report on the use of an issue based model for teaching meeting procedures in a team based software engineering project course (7 teams, 25 students). We observed that, when carefully introduced in the classroom, the use of an issue based model provided significant benefits, even with such limited tool support as a Word Processor template. More specifically, we observed that students conducted meetings more efficiently, that they maintained a more complete record of the issues under discussion, and that intra team communication was significantly improved.
