Development Issues for PDP with ePortfolios

Author(s):  
Simon Grant ◽  
Adam Marshall ◽  
Janet Strivens ◽  
Roger Clark

This chapter describes approaches firstly towards a service-oriented architecture for personal development planning (PDP), and secondly towards representing skills for interoperability. We outline a personal information aggregation and distribution service (PIADS) which serves as the key concept within a distributed approach to storing information suitable for ePortfolios and PDP, and using it through Web services. Our skills “meta-framework” is outlined as a long-term practical solution to the challenge of widely diverse descriptions of skills. It uses a published specification (IMS1 Reusable Definition of Competence or Educational Objective, RDCEO2), and elaborates this to distinguish between conceptual “competency” definitions and operational “educational objective” definitions. If these issues are not addressed, the practical value of ePortfolios for PDP would be limited. Thus the chapter is of particular importance to those planning and designing future ePortfolio systems and services.

Author(s):  
Deepika Dubey ◽  
Deepanshu Dubey ◽  
Uday Pratap Singh

A service-oriented architecture is combination of services having different platforms for implementation. These services are combined, used by, and communicate with each other. The communication is done by massage or data passing. Communication is done by interacting with each other based on different platforms. Chronic diseases are long-term illness that require observation with heavy treatments by the doctors and special attention by family members. Chronic diseases are Alzheimer's disease, Addiction, Autoimmune diseases, Blindness, Rheumatoid arthritis, Chronic renal failure, Chronic Kidney Disease, Deafness and hearing impairment, Hypertension, Mental illness, Thyroid disease, Blood Pressure abnormalities.


Author(s):  
Olga Levina ◽  
Vladimir Stantchev

E-Business research and practice can be situated on following multiple levels: applications, technological issues, support and implementation (Ngai and Wat 2002). Here we consider technological components for realizing business processes and discuss their foundation architecture for technological enabling. The article provides an introduction to the terms, techniques and realization issues for eventdriven and service-oriented architectures. We begin with a definition of terms and propose a reference architecture for an event-driven service-oriented architecture (EDSOA). Possible applications in the area of E-Business and solution guidelines are considered in the second part of the article. Service-oriented Architectures (SOA) have gained momentum since their introduction in the last years. Seen as an approach to integrate heterogeneous applications within an enterprise architecture they are also used to design flexible and adaptable business processes. An SOA is designed as a distributed system architecture providing a good integration possibility of already existing application systems. Furthermore, SOA is mostly suitable for complex and large system landscapes.


2007 ◽  
Vol 6 (4) ◽  
pp. 191-200 ◽  
Author(s):  
Jenny Moon

AbstractReflection, reflective learning, reflective writing and reflective practice are used increasingly in higher education and professional development–but we do not work to one definition and there are considerable differences in the views of educationists on issues of definition. Such discrepancies can exist between the staff working with the same student group. The situation can lead to difficulties in indicating to students how to reflect, and what reflective writing ‘should look like’. Once students do manage to represent their reflection broadly in the required manner (usually writing), there is frequently observed to be a further problem because their reflection is superficial and descriptive. A consequence is that their learning from the reflective process is restricted.This paper addresses the issue of definition of reflection initially through clarifying the different words used around the notion of reflection (e.g., reflection, reflective learning, reflective writing) and providing some suggested definitions. It then addresses the matters both of how we should help students to start with reflection, and with the problem of the superficiality of much of their work. The ‘depth’ of reflection is a concept that has not been much discussed in the literature of reflection and yet it seems to be closely related to the quality of reflective work. The paper discusses the concept of depth and then introduces a style of exercise in which a scenario is reproduced at progressively deeper levels of reflection. The exercise is related to a generic framework for reflective writing. The rationale and justification for the exercise and the framework are discussed and suggestions are made for its manner of use. The exercise and the generic framework for reflective writing are in Appendices 1 and 2.The use of reflection to enhance formal learning has become increasingly common in the past 7 years. From the principle beginnings of its use in the professional development of nurses and teachers, its use has spread through other professions. Now, in the form of personal development planning (PDP), there is an expectation that all students in higher education will be deliberately engaging in reflection in the next 2 years.1 In addition, there are examples of the use of reflective learning journals and other reflective techniques in most, if not all, disciplines.2Reflection is not, however, a clearly defined and enacted concept. People hold different views of its nature, which only become revealed at stages such as assessment. For example, what is it that differentiates reflective writing from simple description? There are difficulties not only with the definition itself but also in conveying to learners what it is that we require them to do in reflection and in encouraging reflection that is deeper than description. In this paper, we consider some issues of definition and then focus on the means of encouraging learners to produce a reflective output of good-enough quality for the task at hand. The latter is presented as an exercise for staff and learners (Appendix 1) with a framework that underpins it (Appendix 2).


2010 ◽  
pp. 72-84
Author(s):  
John Erickson ◽  
Keng Siau

Service-oriented architecture (SOA), Web services, and service-oriented computing (SOC) have become the buzz words of the day for many in the business world. It seems that virtually every company has implemented, is in the midst of implementing, or is seriously considering SOA projects, Web services projects, or service-oriented computing. A problem many organizations face when entering the SOA world is that there are nearly as many definitions of SOA as there are organizations adopting it. Further complicating the issue is an unclear picture of the value added from adopting the SOA or Web services paradigm. This article attempts to shed some light on the definition of SOA and the difficulties of assessing the value of SOA or Web services via return on investment (ROI) or nontraditional approaches, examines the scant body of evidence empirical that exists on the topic of SOA, and highlights potential research directions in the area.


Author(s):  
Andrej Kocbek ◽  
Matjaz B. Juric

Service Oriented Architecture (SOA) is an evolution of distributed computing and it is based on the concepts of interoperable services. To enable reliable and robust service oriented information systems, it is important to establish an effective fault handling. WS-BPEL 2.0 specification does not provide sophisticated and reusable support for handling faults and challenges process designers with many obstacles in the process implementation. We introduce a novel policy driven fault handling framework for BPEL by extending the WS-BPEL 2.0 specification. We propose to separate business process and fault handling logic with the aim to decrease code duplication, process complexity and overall process size. The proposed framework consists of a fault policy which includes the definition of BPEL fault handling logic. The fault policy defines fault handlers and fault handling recovery actions that can be used to design handling BPEL process faults. As a proof-of-concept, we have developed a prototype implementation of the proposed policy driven fault handling framework for BPEL and tested it on 117 real world BPEL scenarios. We have confirmed that the proposed solution decreases the code duplication, the process complexity and overall the process size. Even more, we successfully improved the reliability and readability of BPEL processes.


2015 ◽  
Vol 11 (3) ◽  
pp. 327-346
Author(s):  
Tomasz Miksa ◽  
Rudolf Mayer ◽  
Andreas Rauber

Purpose – This paper aims to address the issue of long-term stability of services and systems depending on service-oriented architecture that has become a popular architecture in systems development and is often implemented using Web services. However, the dependency, especially on externally provided services, can impact the reliability of a system. This is often caused by the loose coupling also implying a less stringent policy for change management and notifications. Therefore, the authors characterise the types of changes that can happen in remote services and propose the concept of resilient web services (RWSs) as an example on how to upgrade existing services to better support the long-term stability of services and systems. Design/methodology/approach – Having analysed several use cases where systems broke because of external dependencies not correctly maintained, the authors derived requirements for RWSs. Findings – By means of a prototype implementation and evaluation of this solution in a case study, the feasibility of the approach was verified. Several scenarios of changes in WSs were simulated, correctly identified and responded to. Originality/value – The authors propose a set of extensions to existing standards such as Web Services Description Language to improve the long-term availability of services in SOAs. A prototype implementation was developed for service monitoring and RWSs.


Author(s):  
Stamatia-Ann Katriou ◽  
Ioannis Ignatiadis ◽  
Garyfallos Fragidis ◽  
Evangelos Tolias ◽  
Adamantios Koumpis

Businesses are aware of the popular demand for careful waste management as a high priority environmental issue. Small and Medium-sized Enterprises (SMEs) face greater pressure when coping with waste products, because they often lack necessary resources or expertise. E-business could offer unique opportunities both for SMEs wanting to dispose of their waste or find waste management services and for SMEs who deal with specific aspects of waste disposal itself. This chapter proposes an approach for locating actors involved in the transportation, disposal, recycling and reuse of waste created by SMEs. Our approach incorporates the notion of Request Based Virtual Organizations (RBVOs) using a Service Oriented Architecture (SOA) and an ontology for the definition of waste management requirements. The populated ontology is utilized by a Multi-Agent System which performs negotiations and forms RBVOs. This approach enables SMEs to find appropriate partners, handle waste management and gain competitive advantage in the marketplace.


Author(s):  
Deepika Dubey ◽  
Deepanshu Dubey ◽  
Uday Pratap Singh

A service-oriented architecture is combination of services having different platforms for implementation. These services are combined, used by, and communicate with each other. The communication is done by massage or data passing. Communication is done by interacting with each other based on different platforms. Chronic diseases are long-term illness that require observation with heavy treatments by the doctors and special attention by family members. Chronic diseases are Alzheimer's disease, Addiction, Autoimmune diseases, Blindness, Rheumatoid arthritis, Chronic renal failure, Chronic Kidney Disease, Deafness and hearing impairment, Hypertension, Mental illness, Thyroid disease, Blood Pressure abnormalities.


Author(s):  
John Erickson ◽  
Keng Siau

Service-oriented architecture (SOA), Web services, and service-oriented computing (SOC) have become the buzz words of the day for many in the business world. It seems that virtually every company has implemented, is in the midst of implementing, or is seriously considering SOA projects, Web services projects, or service-oriented computing. A problem many organizations face when entering the SOA world is that there are nearly as many definitions of SOA as there are organizations adopting it. Further complicating the issue is an unclear picture of the value added from adopting the SOA or Web services paradigm. This article attempts to shed some light on the definition of SOA and the difficulties of assessing the value of SOA or Web services via return on investment (ROI) or nontraditional approaches, examines the scant body of evidence empirical that exists on the topic of SOA, and highlights potential research directions in the area.


Author(s):  
S. Ghosh

This chapter describes the DoD (Department of Defense) policy goal toward Net centric transformation as an example of enterprise architecture in practice. An integrated architecture across the enterprise provided by the DoD Global Information Grid (GIG) is a key ingredient toward meeting Net centricity. The chapter provides background information on key concepts and details the steps necessary to meeting the Net-ready key performance parameter (NR-KPP). The DoD architecture framework provides the Supporting System View, Operational View, and Technical Standards View architecture products that each DoD program must create to meet the Net-centric model. The Net-centric transformation is detailed based on the Net-centric data strategy, Net-centric IA strategy, use of service-oriented architecture, and use of a communications transport strategy. The path toward Net centricity is a significant and long-term effort and the chapter focuses on specific areas that affect DoD programs on their path toward Net-centric compliance. The implementation of enterprise services and the use of key technical standards are also discussed as emerging efforts.


Sign in / Sign up

Export Citation Format

Share Document