Pheme Project

Pheme is a communication infrastructure for all types of product software knowledge, such as product news, product updates, licenses, product feedback, and error feedback. Pheme consists of a

To give an idea of what Pheme is capable of, here are some of the user stories of Pheme. For further information on Pheme's name check out WikiPedia.

The Software Vendor
A software vendor needs to get knowledge to its end users. Such knowledge can be product news, software licenses, or product updates. The vendor wishes to approach all its customers, a group of customers, or one customer only. Pheme enables a vendor to reduce operational and support costs with software delivery through the internet. Furthermore the vendor can use Pheme to improve customer communication with targeted in-product messaging. Finally, the vendor can greatly improve development with product usage data and error feedback reports (when possible).

The System Administrator
Pheme combines system administration with software knowledge delivery, providing the system administrator with direct access to all communication that occurs between the software vendor and the end-user. The system administrator can place intermediate docks between the vendor and end-user, enabling central product and update delivery, monitoring of all communication in and out, and complete policy control. The system administrator can thus manually or automatically decide whether information enters and leaves the organization, either automatically, or manually.

The End-User
The end user wants as least as possible to do with maintenance, on the other hand, when willing, the end-user should have as much power over its own system as the system administrator does. The end-user thus must be able to plan and schedule downloads of products and uploads of feedback, and to share knowledge with peers. The End-User must also be able to redistribute any software he/she receives.

Related Work

Please also check out Sisyphus, a tool that enables continuous integration of software

Type

Year

Additional Information

Conference paper

2006

Definition and Validation of the Key Process Areas of Release, Delivery and Deployment of Product Software Vendors: turning the ugly duckling into a swan, proceedings of the IEEE International Conference on Software Maintenance (ICSM2006, Scientific track), Philadelphia, PA, USA, September, 2006. Accepted for publication.

 

Workshop paper

2006

Evaluating the Release, Delivery, and Deployment Processes of Eight Large Product Software Vendors applying the Customer Configuration Update Model - International Workshop on Interdisciplinary Software Engineering Research (WISER'06) - ICSE'06 - (bibtex) (PDF)

Conference paper

2005

A Process Framework and Typology for Software Product Updaters - CSMR 2005 - (pdf) (bibtex)

Related tool

 

Sisyphus

Sisyphus Buildfarm

Workshop paper

2005

Tijs van der Storm, Continuous Release and Upgrade of Component-Based Software, in: Proceedings of the 12th International Workshop on Software Configuration Management (SCM-12), Lisbon, 2005, [pdf] [bib], [proceedings] [abstract].

Conference - Industrial track

 

2006

Slinger Jansen and Wilfried Rijsemus: Balancing Total Cost of Ownership and Cost of Maintenance Within a Software Supply Network , proceedings of the IEEE International Conference on Software Maintenance (ICSM2006, Industrial track), Philadelphia, PA, USA, September, 2006. Accepted for publication

 

For more information please contact Slinger Jansen.

 


Click here for standalone player