 |
privacy |
||
|
Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.
Blog Feed Recent Items 
The nfoCentrale Blog Conclave nfoCentrale Associated Sites |
2005-03-11TROST: Templates for Raising Open-System TrustworthinessOn February 1, my proposal for an M.Sc in IT project dissertation was accepted by my Dissertation Advisor and approved by the Academic Coordinator of the program. I more or less went autistic and comatose at that point, although I had prepared a project plan and the clock began running in relentless one-day-per-day fashion. My deadline is July 28 and my plan envisions the dissertation being submitted on July 4 (and already slipping slightly in a replan I am conducting this weekend). There have been many little stumbles getting started, and that is something for 43 Things at another time. Today, I want more of the world to know what this is about. That's mostly because I have other items to post about related work and materials that I find in my explorations. It seems useful to establish the perspective that gives rise to my interest. Why TROST? Well, FROST was already taken and I was grasping at straws. Once I had an acronym that worked in a (puny?) punny way, I held onto it. I even adjusted the name of the project at one point. I was careful to preserve the acronym. Templates? "Frameworks," "patterns," and "templates" all work. It is not about laws or theories although principles, practices, guidelines, and approaches figure in. I can go either way with "model" but I think I'll save that one from further over-use just now. Raising? Sure, as in improving, enhancing, enriching, increasing, expanding, and so on. I am looking at the achievement of trustworthiness as a process and a journey, not an absolute result. I do mean continuous improvement along with resilience in the face of setbacks. Open-System? I had originally said Open-Source here. It didn't take long to realize that there is nothing in my vision for TROST that is peculiarly about open-source development (not to be confused with open-source licensing). I chose open-system trustworthiness in homage to OSI, the Open Systems Interconnection effort that had much to teach us about interoperability and integration as well as network interconnection. I mean open-system in this general way. My attention is on ways in which we can address the trustworthiness of components and their integrations in any open-systems setting. Trustworthiness? Well, that should be easy. We all know trustworthiness when we see it, right? Maybe not. Starting out, I am looking at trustworthiness in terms of human arrangements for mitigation of the risks of everyday and not-so-everyday life. There is, most of all, the risk of dealing with each other, especially at a distance. I foresee a mapping into trustworthiness projected onto artifacts. I am not willing, at this point, to take my eye off of the ultimately human and social nature of trust and trustworthiness. Enough blather, where's the code? Uh, yes, this is an Information Technology project and that usually means that something will be built. So, along with some templates and a fair amount of metatemplating too, there is a feasibility demonstration involving honest-to-gosh delivered software. The sofware will be produced using open-box development of an open-source component. This component will integrate into open-system middleware, ODMA, on the Microsoft Windows desktop. Here's more based on the definition of TROST as a SourceForge project:
|
||
|
You are navigating Orcmid's Lair. |
template
created 2004-06-17-20:01 -0700 (pdt)
by orcmid |