EPF Wiki

Do we really want to continue top develop software which requires detailed documentation? How much documentation did you read before using the latest version of your favorite operating system? Or did you dive in after (or without) watching the 30-second online tutorial?

How many apps do you have on your phone, which you regularly use but for which you've never read the docs?

I offer that any need for product documentation is testament to the failure to design a usable solution.

People need training in the terminology and business process of the work that they do with software, and if our software mirrors their expectations and terminology, they should require no training on how to use our software.

There is another reason user documentation should become extinct: users have changed. Once upon a time most people who worked on computers never saw one except at work, the green screens required memorization of codes (think about flying from YVR to LGW via JFK) and a wrong code offered a cryptic error message because the system was interconnected to ... only itself. Today users have computers in their pocket or purse which litsne to satellites in orbit and interconnect with mainframes around the globe. They create their own codes on the fly, IMHO. We don't need to teach them what PF4 does or the difference between click and drag. What we need to do is to build solutions which leverage what they already know ratrher than teach threm new ways to do what they already know how to do. And if our solution is adding value, their work should include significantly fewer steps than what they did before this latest release (which implies the user doc may only need to tell them what not to do)..

This makes tremendous economic sense: we know from studies that about half of the features delivered are never used, so it makes sense to build about half as much software to deliver the same business value. That means the features delivered are expected to be used, which means the case for their usage should be apparent and they can be made to conform to the usage, eliminating the time and cost of documentation development, testing, and maintenance.

There remains a strong case for documentation to support the needs of installers, administrators, and operations staff because those folks use the software infrequently and as one of many systems they install, administer, or operate. The style and extent of such documentation may differ significantly from what we wite for users, and the maintenance is generally less expensive since installation, admin, and operations procedures for a given system tend to change less frequently than its functional or quality features.

Skip Pletcher Usern

08:00 10 Sep 2012 - Scrum Overview in Scrum PT

Verificando como ele publica

Eliel Wosniak Usern

13:55 23 Jul 2012 - Introduction to OpenUP/Basic in OpenUP SP

Hola una pregunta , el open up lo han realizado con el epf composer , lo cual me parece una herramienta muy buena sin embargo eh leido bastante material acerca del epf y por lo entendido el epf es solo una herramienta para modelar , pero me interesaria aplicarla en el desarrollo de proyectos si utilizara el epf¡ tendria que utilizar otra herramienta para administrar mis proyectos es decir los entregables y avances que salen cuando se aplica el RUP? solo deseo confirmar lo que eh leido con la opinion de alguien que la haya usado de antemano gracias

Juan Renato Usern

10:12 17 Jan 2012 - Development in OpenUP

Ok, FYI we have used EPF to represent a large scale process based on ISO-15288 where this question has been addressed.

Daniel

04:48 07 Dec 2011 - Iteration Plan in OpenUP

Test

Glen Schrijvers Usern

14:50 22 Nov 2011 - Inception Iteration [1..n] in OpenUP

please ignore the comment above....didn't mean to send that one...sorry.

brett sharon Usern

14:49 22 Nov 2011 - Inception Iteration [1..n] in OpenUP

I don]t agee...

brett sharon Usern

08:37 14 Sep 2011 - Introduction to OpenUP in OpenUP

The definition says OpenUP is a unified process, but does not say what it is used for. Is it a unified process for developing applications software?

David Thompson Usern

12:37 02 Aug 2011 - Develop Solution Increment in OpenUP

It is part of that activity, not a mistake.

rbalduino

13:07 10 Mar 2011 - Guidance in OpenUP

Hey all, I am trying to determine how to create glossary for an existing project I am working on. I know there is a feature called "Term Definition" however it is limited only in the glossary link on the top. Is "Term Definition" guidance best uses for the terms that aren't included in the normal project?

Michael Lee Usern

06:24 08 Mar 2013 - 14.pdf - Piyush Mahajan "
test
"
19:53 20 Jul 2012 - Introdução ao OpenUP.pdf - Daniel Ferreira "Tradução do artigo do Ricardo Balduino."
23:32 18 Jul 2012 - library.xmi - José Luis Nájera Alejo
09:01 11 Feb 2010 - EPF_Installation_Tutorial_Manual_2010024_v14.pdf - Bjorn Tuft "I have written a manual for the EPF Composer, containing installation and configuration instructions, tutorials and a user manual. It is a draft version, created from the help files and from the experience gathered while experimenting with the application. "
08:10 15 Dec 2009 - Address+Correction+Interface.jpg - darshita "eqew"
03:12 27 Nov 2009 - Water lilies.jpg - Neha Vyas
01:34 27 Nov 2009 - Blue hills.jpg - Neha Vyas
06:44 09 Dec 2008 - architecture_notebook_tpl.dot - Mark Kamoski "OpenUp - architecture_notebook_tpl.dot - Adding new version to fix minor typos, fix layout issues, and fixed formatting for hidden-text."
16:07 08 Dec 2008 - vision_tpl.dot - Mark Kamoski "
OpenUP Template - vision_tpl.dot - Made minor spelling/layout changes where necessary. Corrected "hidden text" formatting so that it works properly now.
"
16:07 08 Dec 2008 - uc_specification_tpl.dot - Mark Kamoski "
OpenUP Template - uc_specification_tpl.dot - Made minor spelling/layout changes where necessary. Corrected "hidden text" formatting so that it works properly now.
"
16:06 08 Dec 2008 - test_script_tpl.dot - Mark Kamoski "
OpenUP Template - test_script_tpl.dot - Made minor spelling/layout changes where necessary. Corrected "hidden text" formatting so that it works properly now.
"
16:06 08 Dec 2008 - test_cases.dot - Mark Kamoski "
OpenUP Template - test_cases.dot - Made minor spelling/layout changes where necessary. Corrected "hidden text" formatting so that it works properly now.
"
16:06 08 Dec 2008 - systemwide_req_spec.dot - Mark Kamoski "
OpenUP Template - systemwide_req_spec.dot - Made minor spelling/layout changes where necessary. Corrected "hidden text" formatting so that it works properly now.
"
16:05 08 Dec 2008 - project_plan_tpl.dot - Mark Kamoski "
OpenUP Template - project_plan_tpl.dot - Made minor spelling/layout changes where necessary. Corrected "hidden text" formatting so that it works properly now.
"
16:05 08 Dec 2008 - iteration_plan_tpl.dot - Mark Kamoski "
OpenUP Template - iteration_plan_tpl.dot - Made minor spelling/layout changes where necessary. Corrected "hidden text" formatting so that it works properly now.
"