No abstract

There is a lot of research anticipating a "Free, Libre and Open Source Software" (FLOSS) development process and recurring characteristics of FLOSS projects have been discussed by various authors. Research suggests that a unique FLOSS development approach does not exist and there is a family of different development processes instead. Pattern Languages have been used to describe distinctive and common features of processes. In this paper, we identify four FLOSS development patterns derived from related work and discussion about FLOSS in the communities. Building on that, we propose methods to verify the patterns.

On the way to a completely electronic workflow, it is necessary to include customer signatures. Legislation in many countries treats electronic signatures similar to handwritten ones. Both are accepted for various purposes such as for finalization of documents, acknowledgement of the document's contents as well as conclusion of agreements. Most important, electronic signatures are accepted as proof of those actions. But customers today often lack knowledge or means to issue them. In this study a business process is described that will produce reliable signatures without the need of previous knowledge or devices on customer side. A threat model for a generic process is described and countermeasures including cryptography, biometric features, tamper-resistant devices, timestamps, signature databases, and others are discussed.

No abstract