The Experts below are selected from a list of 329913 Experts worldwide ranked by ideXlab platform
Pornpit Wongthongtham - One of the best experts on this subject based on the ideXlab platform.
-
development of a Software Engineering ontology for multisite Software development
IEEE Transactions on Knowledge and Data Engineering, 2009Co-Authors: Pornpit Wongthongtham, Tharam S. Dillon, Elizabeth Chang, Ian SommervilleAbstract:This paper aims to present an ontology model of Software Engineering to represent its knowledge. The fundamental knowledge relating to Software Engineering is well described in the textbook entitled Software Engineering by Sommerville that is now in its eighth edition (2004) and the white paper, Software Engineering Body of Knowledge (SWEBOK), by the IEEE (203) upon which Software Engineering ontology is based. This paper gives an analysis of what Software Engineering ontology is, what it consists of, and what it is used for in the form of usage example scenarios. The usage scenarios presented in this paper highlight the characteristics of the Software Engineering ontology. The Software Engineering ontology assists in defining information for the exchange of semantic project information and is used as a communication framework. Its users are Software engineers sharing domain knowledge as well as instance knowledge of Software Engineering.
-
ontology based Software Engineering Software Engineering 2 0
Australian Software Engineering Conference, 2008Co-Authors: Tharam S. Dillon, Elizabeth Chang, Pornpit WongthongthamAbstract:This paper describes the use of ontologies in different aspects of Software Engineering. This use of ontologies varies from support for Software developers at multiple sites to the use of an ontology to provide semantics in different categories of Software, particularly on the Web. The world's first and only Software Engineering ontology and a project management ontology in conjunction with a domain ontology are used to provide support for Software development that is taking place at multiple sites. Ontologies are used to provide semantics to deal with heterogeneity in the representation of multiple information sources, enable the selection and composition of web services and grid resources, provide the shared knowledge base for multiagent systems, provide semantics and structure for trust and reputation systems and privacy based systems and codification of shared knowledge within different domains in business, science, manufacturing, Engineering and utilities. They, therefore, bring a new paradigm to Software Engineering through the use of semantics as a central mechanism which will revolutionize the way Software is developed and consumed in the future leading to the development of Software as a service bringing about the dawn of Software Engineering 2.0.
Jim Whitehead - One of the best experts on this subject based on the ideXlab platform.
-
Collaborative Software Engineering
2010Co-Authors: Ivan Mistrk, Annemieke Hoek, John Grundy, Jim WhiteheadAbstract:Collaboration among individuals from users to developers is central to modern Software Engineering. It takes many forms: joint activity to solve common problems, negotiation to resolve conflicts, creation of shared definitions, and both social and technical perspectives impacting all Software development activity. The difficulties of collaboration are also well documented. The grand challenge is not only to ensure that developers in a team deliver effectively as individuals, but that the whole team delivers more than just the sum of its parts. The editors of this book have assembled an impressive selection of authors, who have contributed to an authoritative body of work tackling a wide range of issues in the field of collaborative Software Engineering. The resulting volume is divided into four parts, preceded by a general editorial chapter providing a more detailed review of the domain of collaborative Software Engineering. Part 1 is on "Characterizing Collaborative Software Engineering", Part 2 examines various "Tools and Techniques", Part 3 addresses organizational issues, and finally Part 4 contains four examples of "Emerging Issues in Collaborative Software Engineering". As a result, this book delivers a comprehensive state-of-the-art overview and empirical results for researchers in academia and industry in areas like Software process management, empirical Software Engineering, and global Software development. Practitioners working in this area will also appreciate the detailed descriptions and reports which can often be used as guidelines to improve their daily work.
-
collaborative Software Engineering challenges and prospects
Computational Science and Engineering, 2010Co-Authors: Igor Mistrík, André Van Der Hoek, John Grundy, Jim WhiteheadAbstract:Much work is presently ongoing in collaborative Software Engineering research. This work is beginning to make serious inroads into our ability to more effectively practice collaborative Software Engineering, with best practices, processes, tools, metrics, and other techniques becoming available for day-to-day use. However, we have not yet reached the point where the practice of collaborative Software Engineering is routine, without surprises, and generally as optimal as possible. This chapter summarizes the main findings of this book, draws some conclusions on these findings and looks at the prospects for Software engineers in dealing with the challenges of collaborative Software development. The chapter ends with prospects for collaborative Software Engineering.
-
collaborative Software Engineering concepts and techniques
Collaborative Software Engineering, 2010Co-Authors: Jim Whitehead, John Grundy, Igor Mistrík, André Van Der HoekAbstract:Collaboration is a central activity in Software Engineering, as all but the most trivial projects involve multiple engineers working together. Hence, understanding Software Engineering collaboration is important for both engineers and researchers. This chapter presents a framework for understanding Software Engineering collaboration, focused on three key insights: (1) Software Engineering collaboration is model-based, centered on the creation and negotiation of shared meaning within the project artifacts that contain the models that describe the final working system; (2) Software project management is a cross-cutting concern that creates the organizational structures under which collaboration is fostered (or dampened); and (3) global Software Engineering introduces many forms of distance – spatial, temporal, socio-cultural – into existing pathways of collaboration. Analysis of future trends highlight several ways engineers will be able to improve project collaboration, specifically, Software development environments will shift to being totally Web-based, thereby opening the potential for social network site integration, greater participation by end-users in project development, and greater ease in global Software Engineering. Just as collaboration is inherent in Software Engineering, so are the fundamental tensions inherent in fostering collaboration; the chapter ends with these.
-
collaboration in Software Engineering a roadmap
International Conference on Software Engineering, 2007Co-Authors: Jim WhiteheadAbstract:Software Engineering projects are inherently cooperative, requiring many Software engineers to coordinate their efforts to produce a large Software system. Integral to this effort is developing shared understanding surrounding multiple artifacts, each artifact embodying its own model, over the entire development process. This focus on model- oriented collaboration embedded within a larger process is what distinguishes collaboration research in Software Engineering from broader collaboration research, which tends to address artifact-neutral coordination technologies and toolkits. This article first presents a list of goals for Software Engineering collaboration, then surveys existing collaboration support tools in Software Engineering. The survey covers both tools that focus on a single artifact or stage in the development process (requirements support tools, UML collaboration tools), and tools that support the representation and execution of an entire Software process. Important collaboration standards are also described. Several possible future directions for collaboration in Software Engineering are presented, including tight integration between web and desktop development environments, broader participation by customers and end users in the entire development process, capturing argumentation surrounding design rationale, and use of massively multiplayer online (MMO) game technology as a collaboration medium. The article concludes by noting a problem in performing research on collaborative systems, that of assessing how well certain artifacts, models, and embedded processes work, and whether they are better than other approaches.
Tharam S. Dillon - One of the best experts on this subject based on the ideXlab platform.
-
development of a Software Engineering ontology for multisite Software development
IEEE Transactions on Knowledge and Data Engineering, 2009Co-Authors: Pornpit Wongthongtham, Tharam S. Dillon, Elizabeth Chang, Ian SommervilleAbstract:This paper aims to present an ontology model of Software Engineering to represent its knowledge. The fundamental knowledge relating to Software Engineering is well described in the textbook entitled Software Engineering by Sommerville that is now in its eighth edition (2004) and the white paper, Software Engineering Body of Knowledge (SWEBOK), by the IEEE (203) upon which Software Engineering ontology is based. This paper gives an analysis of what Software Engineering ontology is, what it consists of, and what it is used for in the form of usage example scenarios. The usage scenarios presented in this paper highlight the characteristics of the Software Engineering ontology. The Software Engineering ontology assists in defining information for the exchange of semantic project information and is used as a communication framework. Its users are Software engineers sharing domain knowledge as well as instance knowledge of Software Engineering.
-
ontology based Software Engineering Software Engineering 2 0
Australian Software Engineering Conference, 2008Co-Authors: Tharam S. Dillon, Elizabeth Chang, Pornpit WongthongthamAbstract:This paper describes the use of ontologies in different aspects of Software Engineering. This use of ontologies varies from support for Software developers at multiple sites to the use of an ontology to provide semantics in different categories of Software, particularly on the Web. The world's first and only Software Engineering ontology and a project management ontology in conjunction with a domain ontology are used to provide support for Software development that is taking place at multiple sites. Ontologies are used to provide semantics to deal with heterogeneity in the representation of multiple information sources, enable the selection and composition of web services and grid resources, provide the shared knowledge base for multiagent systems, provide semantics and structure for trust and reputation systems and privacy based systems and codification of shared knowledge within different domains in business, science, manufacturing, Engineering and utilities. They, therefore, bring a new paradigm to Software Engineering through the use of semantics as a central mechanism which will revolutionize the way Software is developed and consumed in the future leading to the development of Software as a service bringing about the dawn of Software Engineering 2.0.
Michael Wooldridge - One of the best experts on this subject based on the ideXlab platform.
-
agent oriented Software Engineering
International Conference on Software Engineering, 2000Co-Authors: Paolo Ciancarini, Michael WooldridgeAbstract:The ATAL workshops focus on the links between the theory and practice of intelligent agents. One aspect of this, which is steadily growing in importance, is the idea of agent technology as a Software Engineering paradigm. Previous ATAL workshops have had special tracks on programming languages for agent-oriented development, and methodologies for agent system development. ATAL-99 aims to build on this experience by focussing on the wider issues of agents as a Software Engineering paradigm.
-
agent oriented Software Engineering
Lecture Notes in Computer Science, 2000Co-Authors: Stefan Bussmann, Paolo Ciancarini, Keith Decker, Michael N Huhns, Michael WooldridgeAbstract:Software Engineering has been a major concern in computer science since the late 1960s and early 1970s. Despite considerable advances in our understanding of Software since then, it remains a significant issue in computing today. Progress in Software Engineering has been made primarily through the development of incresingly powerful abstractions with which to understand and implement complex systems. Consider the progression from procedural abstraction, through abstract data types, to object-oriented programming. Each step represents a move away from a machine-oriented view of Software towards one that more closely reflects the way that we ourselves understand the world. The state of the art allows us to model and develop complex systems from essentially passive entities that interact with one another in simple ways.
Elizabeth Chang - One of the best experts on this subject based on the ideXlab platform.
-
development of a Software Engineering ontology for multisite Software development
IEEE Transactions on Knowledge and Data Engineering, 2009Co-Authors: Pornpit Wongthongtham, Tharam S. Dillon, Elizabeth Chang, Ian SommervilleAbstract:This paper aims to present an ontology model of Software Engineering to represent its knowledge. The fundamental knowledge relating to Software Engineering is well described in the textbook entitled Software Engineering by Sommerville that is now in its eighth edition (2004) and the white paper, Software Engineering Body of Knowledge (SWEBOK), by the IEEE (203) upon which Software Engineering ontology is based. This paper gives an analysis of what Software Engineering ontology is, what it consists of, and what it is used for in the form of usage example scenarios. The usage scenarios presented in this paper highlight the characteristics of the Software Engineering ontology. The Software Engineering ontology assists in defining information for the exchange of semantic project information and is used as a communication framework. Its users are Software engineers sharing domain knowledge as well as instance knowledge of Software Engineering.
-
ontology based Software Engineering Software Engineering 2 0
Australian Software Engineering Conference, 2008Co-Authors: Tharam S. Dillon, Elizabeth Chang, Pornpit WongthongthamAbstract:This paper describes the use of ontologies in different aspects of Software Engineering. This use of ontologies varies from support for Software developers at multiple sites to the use of an ontology to provide semantics in different categories of Software, particularly on the Web. The world's first and only Software Engineering ontology and a project management ontology in conjunction with a domain ontology are used to provide support for Software development that is taking place at multiple sites. Ontologies are used to provide semantics to deal with heterogeneity in the representation of multiple information sources, enable the selection and composition of web services and grid resources, provide the shared knowledge base for multiagent systems, provide semantics and structure for trust and reputation systems and privacy based systems and codification of shared knowledge within different domains in business, science, manufacturing, Engineering and utilities. They, therefore, bring a new paradigm to Software Engineering through the use of semantics as a central mechanism which will revolutionize the way Software is developed and consumed in the future leading to the development of Software as a service bringing about the dawn of Software Engineering 2.0.
