No abstract

Purpose This paper aims to develop and empirically test a model of relationships between antecedents and outcomes of flow experience of users of massive open online courses (MOOC). Design/methodology/approach The researchers surveyed individuals primarily from India, who had enrolled in at least one MOOC offered by MOOC providers such as Coursera, edX and FutureLearn. The data were collected from 310 individuals using an online questionnaire. The partial least squares technique of structural equation modeling (PLS-SEM) was used to test the reliability and validity of the data, and the study’s hypothesized relationships. Findings The study found support for identification of telepresence, challenge and skill as antecedents of flow experience. MOOC satisfaction and MOOC usage intention were found to be the outcomes of flow experience, as hypnotized. The study also found the mediating role of MOOC satisfaction in the relationship of flow experience and MOOC usage intention. Practical implications The findings indicate that if the MOOC providers can orchestrate flow experience for MOOC users then that will increase the satisfaction of MOOC users, which will lead to increase in MOOC adoption. Originality/value The study makes the contribution towards better understanding of flow experience in the context of MOOC usage by identifying both antecedents and outcomes of flow experience. Further, it highlights the influencing role of flow experience on MOOC adoption.

No abstract

No abstract

No abstract

Not every company has the same needs in adopting a service-oriented architecture (SOA). The authors compare four options for increasing system flexibility.T hese days, almost every CIO or IT manager is looking into service-oriented architecture (SOA). A year ago, The McKinsey Quarterly surveyed 72 senior IT executives about their investment priorities and found that 64 percent were planning to implement SOA in 2007. 1 Forrester reported in February 2007 that 62 percent of its surveyed companies from the North American and European regions are either using SOA or planning to do so within the next 12 months. 2 Interestingly, adopting SOA isn't the same as deploying a software application, which can be a one-time activity. Rather, it's a journey for an organization over a long period of time-an important detail for everyone involved to understand.Although a few vendors claim that SOA can be quickly and easily implemented with their products, the overall understanding in the industry is that SOA adoption is an evolutionary, rather than revolutionary, process. Beginning the JourneyTechnically speaking, SOA is an architectural pattern that says that computational units (such as system modules) should be loosely coupled through their service interfaces for delivering the desired functionality. This pattern can be applied to the architecture of a single system (such as a quality management information or insurance claims management system) or the overall architecture of all applications in an en- 36IT Pro May/June 2008 P u b l i s h e d b y t h e I E E E C o m p u t e r S o c i e t y 1520-9209/08/$25.00

No abstract

No abstract