Journal of Pervasive Systems Engineering

Guide for Authors

The Journal will accept and review submissions in US and UK English. A body of international peers will review all submissions, with potential author revisions as recommended by reviewers, with the intent to achieve published papers that:

Editorial selection of works for publication will be made based on content, without regard to the stature of the authors. Selections will include a wide variety of international works, recognizing and supporting the essential breadth and universality of the field. Final selection of papers for publication, and the form of publication, shall rest with the Editor. Submission of quality papers for review is strongly encouraged. The review process is estimated to take three months. All papers should be submitted to editor in chief Stefan Wagner, at

Submission guidelines

Papers should be in US or UK English. Previously published work may not be submitted, nor may the work be concurrently submitted to any other conference or journal. Such papers will be rejected without review. The paper submissions should follow the ACM formatting. Submissions prepared according to IEEE guidelines will have no disadvantage in the review process, however camera-ready must be in ACM formatting.

Instructions and Templates

Prepare your paper using the 2-column format, ACM Strict SIG style. In order to ensure the proper formatting of submitted papers, you must follow the instructions found in these ACM Guidelines - detailed instructions on paper formatting. Also, you may download a LaTeX Template or a Word Template. Submission Papers should be submitted as a PDF and sent as an email to the editor in chief: All submissions must be anonymized. No identifying information on Authors or their affiliation should appear on the paper (except for neutral references to their own work).



Each paper should contain an abstract of 100 to 250 words that appears at the beginning of the document. Use the same text that is submitted electronically along with the author contact information. References. Please list and number all references at the end of the document. The references can be numbered in alphabetical order or in order of appearance in the paper. When referring to them in the text, type the corresponding reference number in square brackets as shown at the end of this sentence [1]. The end of the document should include a list of references containing information similar to the following example: [1] D. E. Ingalls, "Image Processing for Experts," IEEE Trans. ASSP, vol. ASSP-36, pp. 1932-1948, 1988.

Illustrations and Colors

Illustrations must appear within the designated margins. They may span the two columns. If possible, position illustrations at the top of columns, rather than in the middle or at the bottom. Caption and number every illustration. All halftone illustrations must be clear in black and white. Page Numbers. Do not put page numbers on your document. We will add appropriate page numbers to accepted papers when the conference proceedings are assembled.

Please contact the editor-in-chief in case of any questions .


Online Articles

Volume 4 (2015/1):

Volume 3 (2014/1):

Volume 2 (2013/2)

Volume 1 (2013/1):


Open Access

What is Open Access?

Open access publishing allows free access to and distribution of published manuscrupts where the author retains copyright of their work by employing a Creative Commons attribution licence, therefore removing any barriers to access.

This implies:

Definition of Open Access

The idea and practise of providing free online access to journal papers began at least a decade before the term "open access" was formally coined. Computer scientists had been self-archiving in anonymous ftp archives since the 1970s and physicists had been self-archiving in arxiv since the 1990s. The Subversive Proposal to generalize the practice was posted in 1994. The term "open access" itself was first formulated in three public statements in the 2000s: the Budapest Open Access Initiative in February 2002, the Bethesda Statement on Open Access Publishing in June 2003, and the Berlin Declaration on Open Access to Knowledge in the Sciences and Humanities in October 2003.

The Budapest statement defined open access as follows: There are many degrees and kinds of wider and easier access to this literature. By 'open access' to this literature, we mean its free availability on the public internet, permitting any users to read, download, copy, distribute, print, search, or link to the full texts of these articles, crawl them for indexing, pass them as data to software, or use them for any other lawful purpose, without financial, legal, or technical barriers other than those inseparable from gaining access to the internet itself. The only constraint on reproduction and distribution, and the only role for copyright in this domain, should be to give authors control over the integrity of their work and the right to be properly acknowledged and cited.

The Bethesda and Berlin statements add that for a work to be open access, users must be able to "copy, use, distribute, transmit and display the work publicly and to make and distribute derivative works, in any digital medium for any responsible purpose, subject to proper attribution of authorship."


Aims and Scope

The Journal of Pervasive Systems Engineering s a peer reviewed, open access, online journal covering all subjects within pervasive systems engineering, including the management of products and services, and processes within the fields of pervasive computing and related areas. Pervasive systems engineering activities involve the technologies, processes, and systems management approaches needed for the definition of pervasive systems, including identification of user requirements and technological specifications; development of pervasive systems, including conceptual architectures, tradeoff of design concepts, configuration management during system development, integration of new systems with legacy systems, and integrated product and process development; and deployment of systems, including operational test and evaluation, maintenance over an extended lifecycle, and reengineering. Modern pervasive systems, including both ubiquitous products and services, are often highly knowledge intensive, and are found in both the public and private sectors.

The journal emphasizes strategic and program management of these topics, and the information and knowledge base for knowledge principles, knowledge practices, and knowledge perspectives for the engineering of pervasive systems. The main methodology of pervasive systems engineering include the pervasive systems engineering method that operates within the unified process methodology framework, including the pervasive proof-of-concept prototyping method. Definitive case studies involving current practice and novel methods and technologies for the design and evaluation of pervasive healthcare systems engineering are especially welcome.

Pervasive computing, often synonymously called ubiquitous computing, is an emerging field that since the early nineties has introduced several novel paradigms for computing models. Tremendous developments in such technologies as wireless communications and networking, mobile computing and handheld devices, embedded systems, wearable computers, sensors, RFID tags, smart spaces, middleware, software agents, and the like, have led to the evolution of pervasive computing platforms. The goal of pervasive computing is to create ambient intelligence and calm technologies where networked devices embedded in the environment provide unobtrusive and continuous connectivity and services, thus improving human experience and quality of life without explicit awareness of the underlying communications and computing technologies. In this environment, all devices and in the world around us (e.g., key chains, coffee mugs, computers, appliances, cars, homes, offices, cities, and the human body) is interconnected as pervasive network of intelligent devices that cooperatively and autonomously collect, process and transport information, in order to adapt to the associated context and activity.

Pervasive systems engineering is a specialization of the general field systems engineering, which is defined as "an interdisciplinary approach and means to enable the realization of successful systems". More specifically, systems engineering "is a discipline that concentrates on the design and application of the whole system as distinct from the parts. It involves looking at a problem in its entirety, taking into account all the facets and all the variables and relating the social to the technical aspect". Furthermore, systems engineering has also been described as "an iterative process of top-down synthesis, development, and operation of a real-world system that satisfies, in a near optimal manner, the full range of requirements for the system". The systems engineering perspective is based on systems thinking. This occurs "through discovery, learning, diagnosis, and dialog that lead to sensing, modeling, and talking about the real-world to better understand, define, and work with systems. A systems thinker knows how systems fit into the larger context of day-to-day life, how they behave, and how to manage them". And furthermore, "systems thinking recognizes circular causation, where a variable is both the cause and the effect of another and recognizes the primacy of interrelationships and non-linear and organic thinking-a way of thinking where the primacy of the whole is acknowledged". In other words, systems engineering is well suited for developing complex systems such as self-care systems, where a telemonitoring system consists of many subsystems, with multiple points of failure in the many parts in each subsystem, and where the system in itself is part of other healthcare systems, not limited to technical systems, but also organizational and political systems. The thesis work is highly influenced by systems thinking, seeing the healthcare sensors, devices, infrastructure, systems, and the stakeholders as a whole, that needs to be systems engineered effectively, while also maintaining the notion of feasibility and cost-benefit constrained approach that is a main element of systems engineering discourse.

Applying the well-established systems engineering methods of modeling, simulation, and prototyping during the design phases significantly reduces the risk of failure in the finished system. Modeling and simulation are often used on large and complex projects to analyze the feasibility of novel concepts and are typically constrained to conducting idealized experiments, using e.g. Matlab, LabView, or other simulation environments. It is seldom possible to capture all aspects and features of a problem domain when introducing novel interventions, and modeling it sufficiently precise to be useful, especially in systems relying on a very broad user population, with a large variety of cognitive capabilities and skills. Alternatively, prototyping is a systems engineering technique, and a specialized type of modeling, that allows for evaluating different approaches outside the constraints of the idealized model, in order to capture real world experiences to novel interventions designs. Rapid prototyping is a specialized systems engineering technique for creating prototypes that are designed to be only sufficiently robust to evaluate the scientific or engineering objectives they are addressing. Haskins et al. state that "a rapid prototype is a particular type of simulation quickly assembled from a range of existing physical, graphical, or mathematical elements.", and further, "They are frequently used to investigate form and fit, human-system interface, operations, or producibility considerations.". Other concepts include partial prototypes "used to verify critical elements of the system-of-interest" and full prototypes for creating a "complete representation of the system.". This thesis relies on rapid prototyping, constructing both partial and full prototypes as needed to address the thesis objectives. Modeling has been performed using Matlab for evaluating different data algorithms for interpreting both healthcare and context data. Most systems engineering processes are targeted at large scale industrial projects with a focus on hardware components rather than software engineering. Software engineering is tightly related to systems engineering, but with a main focus on the software development process. As the research prototypes developed in this thesis rely heavily on service and object oriented software components the unified process was chosen as the main software development approach.


Submit a Manuscript

Before submitting your manuscript, please take a moment to verify that you have formatted the manuscript according to the guidelines of the journal (see "Guide for Authors").

Submit your manuscript by sending it to the editor-in-chief at

We strive for feedback within one work week. Feedback categories include "desk reject", "enligsh language editing required", "academic language editing required", "major revisions required", "minor revisions required", and "manuscript accepted".


Contact Information

Please contact us at for any questions.


Image Maps

Information for developers: We created these image maps using Please go here and and try them


We are moving!

The Journal of Pervasive Systems Engineering is moving to become part of a well-known brand of open access high-quality journals. We expect to be online again in May 2016.

All published and indexed papers will remain available at this site until the relaunch in May.

Thank you for your patience.