View allAll Photos Tagged documentation
This is what the documentation at my current job looks like. I work in Desktop Support and the other guy has all his notes on print outs in a giant folder. So I get to dig through this every time I need to find something.
My Russian fiancée is applying for a Danish visa, but even though it's a short 60-day tourist visa, the department of emigration needs "Documentation of the relationship" to make sure I'm not.. I don't exactly know what. Print-outs of Flickr photos, personal e-mail, phone bills, photocopies of stamps and visas from my passport etc. etc. It's like falling in love with someone outside Europe is a crime.
How I hate bureaucracy.
After two school buses collided on the San Diego (405) Freeway in west Los Angeles on January 10, 2009, Los Angeles Firefighters moved the two lightly damaged vehicles - carrying a total of 126 passengers, to a large off-highway parking lot where an efficient triage led them to transport twenty-five with minor complaints to area hospitals. © Photo by John Conkle
this is the reason why mike keeps good care of geoserver docs, he has a great skeptical response to each developer explanation
Picnickers prepare to visit and document the creator of Space City. Sue Johnson, Stella Marrs, Steve Peters, Rich Jensen. Olympia, Washington. Late Summer 1985. Photo by Julie Fay.
Documentation of public intervention and graffiti at confederate monument sites in wake of Charlottesville riots.
A small but fine private botanical garden in the Odenwald, Hesse, Germany with the focus on Yucca & Co.
Yucca necopina Shinners, Spring Fl. Dallas-Fort Worth. 91, 408. 1958
Vernacular names: Brazos River Yucca, or Glen Rose Yucca
A rare endemic native to a small region in north-central Texas, in Somervell, Hood, Parker, and Tarrant Counties, west of Dallas and Fort Worth, River terraces, deep sand; 200--300 m
This is the first flowering specimen of this Yucca in Germany, and it is grown from Seeds collscted by Fritz Hochstetter in Texas as Y. arkansana (var. / subsp) necopina, field collection number fh 1185.29. In his new treatments Hochstetter conceals this taxon. Also, the forthcoming treatment for the FNA will treat this taxon as a synonym for Yucca arkansana, But field and molecular studies support species rank!
Photo made by the owner of the "Exotic garden in the Odenwald" to complete the documentation:
Original - Photo by Walter Schönherr in the forum "Yucca & more"
Documentation from the Tessellation Exposition, July 29th -August 6th at the Jardim Botanico in Brasilia, Brazil.
my friend evan gealy at kyklops tattoo in pittsburgh updated my shoulder tattoo and added some work (some partially visible here) on my back. sorry for the lame photo.
This photograph shows my work 'Werkhuizen' at my art academy for the 'Open doors days' in june 2006.
This photograph was taken by someone else some days after the art opening. Some people had already taken some cards. It seemed clear which card was the most wanted... Again after some days, all cards had been taken. So, overall the concept seemed to be working.
The "data" represented here are for discussion only: it's the framework that's relevant.
The vertical axis varies depending on the document, methodology, or project, but in general it represents the maturity of the deliverable.
The point is that you create an artifact as part of a project, and it goes through these four stages:
• framing (where you initialize the artifact)
• elaboration (where you add detail)
• finalizing (where you cross the Ts and dot the Is)
• shelving (where you archive and reference the document)
The scale of maturation at each phase will vary.
In the background, the curve represents how important the artifact is over the course of its lifecycle. Again, this will vary depending on circumstance. I've imagined that relevance crests mid-way through elaboration, and then tapers off as the final due date comes near, with a drop after the due date.
My question to you:
• Does the framework resonate with your experience?
• Is the framework applicable for all kinds of documents of varying formality?
• Are there additional phases in the lifecycle?
• How dramatically can the curves (maturity and relevance) vary between different types of documents/projects?
What's next:
• Stuff happens in a project that "disrupts" this lifecycle. I'd like to integrate those into the picture.
--------------
Responding to @zsazsa and @soldierant (via Twitter):
A document's lifecycle is interdependent with the project methodology. These phases don't correspond to the project's process because I'll create different documents throughout a project. Each one of those documents has its own lifecycle, even if it doesn't last the length of a project.
At the same time, a document's capacity to mature is dependent on the circumstances of a project. This is the next layer of information I'd like to include: how can this lifecycle be disrupted?
This diagram isn't prescriptive (like a project methodology would be). Instead, I'm trying to describe the "natural" evolution of individual documents. (Why I use gerunds to label the phases rather than imperatives.)
As a metaphor, you might look at a whole story and describe the entire plot (the project process) or you might look at an individual character in the story (a deliverable) and describe his or her specific arc. Character's come and go: not every character at the beginning of the story is still there at the end of the movie.