[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[epf-dev] Working outside in the dark.

Jim,

I am working (ever so slowly) on plug-ins to cover:

MIL-HDBK-881 WORK BREAKDOWN STRUCTURE
MIL-HDBK-171 WORK BREAKDOWN STRUCTURE ELEMENTS FOR SOFTWARE
IEEE 12207 Software Life Cycle Processes
ISO 14764 Software Maintenance
The software support services model out of C3M

All that to role up under our requirements to work under DEF(AUST)5664A
(which steals from 881).

882 (I am not worried about DO178B as much as the process elements are
covered by 12207 via the FAA software assurance stack and simply scope
the Hazard Analysis aspects of IEEE 1012 (the depth of rigor and
practice is more handbook etc)

Also, I have started a coffee time port of http://www.opfro.org/ (hoping
to pass that to EPF community as the owner/coordinator, Dr Firebrand,
has emailed me to say he is keen for it to be ported).  I have been
working on the approach to translate OPF framework to SPEM and it has,
to date, been the most straight forward of the ports.  The others I
seems to be tearing down and reworking because it isn't apparent how to
design a truly reusable plugin from scratch despite the intent that
plugins are to be re-used (or by their nature re-useable).  I am working
them all at the same time because I am trying to make each one decouple
enough to stand on their own, but also to work together cohesively when
building process models from them.  Slow work.

Most of the examples at the EPF site are quite shallow and more or less
might see only one layer added.  Examples like TOGAF are not really
reusable as much as they are tailorable - a slightly different intent.

The real test is when you try to draw them up into your "real" process
model.  So, the absence of heuristics in the community for designing
plug-ins for re-use, rather than the so-called agile model (which means
churning, throwing away, churning, tearing hair out, epiphany, despair,
churn) means a steep learning curve.  Begs the question, when are we
getting away from point and click instuction on how to use the tool and
get to a book on the real problem? (hint)

The upshot, we have an internal process framework that drives our
process and lifecycle modelling and all the bits above need to fit into
that internal model (which I am also tooling into EPF).

Don't fret though, I still get out on the town occasionally lol

Cheers,
Ray



> ______________________________________________________________________
> From: Jim Ruehlin <jruehlin@xxxxxxxxxx>
> To: Eclipse Process Framework Project Developers List 
> <epf-dev@xxxxxxxxxxx>
> Sent: Friday, 19 June 2009 2:22:54
> Subject: [epf-dev] Query: Who is Building Stand-alone EPF Content?
> 
> 
> 
> Hello,
> 
> I'm interested in finding out how many people are creating content 
> using EPF Composer, but are not using the EPF Practice Library. Or, 
> you're just using the EPF Practice Library for a minority of the 
> content you publish. It would be useful to understand how many 
> organizations are creating a (comparatively) large amount of content 
> as opposed to creating small extensions to existing practices.
> 
> I'd appreciate it if you could respond to the newsgroup or to me 
> personally if you prefer with a quick note letting me know 
> approximately how many pages/elements you're creating, and the nature 
> of the project (large enterprise content deployment, content that 
> covers specialized areas, etc).
> 
> This is useful for the EPF community to know as people want to provide

> services or training around the way the tool and content is actually 
> being used.
> 
> Much thanks,
> Jim Ruehlin, EPF Committer
> 
> Jim Ruehlin, IBM Rational Software
> Method Architect, ADC CoP
> RMC SIG Lead
> jruehlin@xxxxxxxxxx
> voice: 949.545.8912
> 
> 
> 
> 
> 
> ______________________________________________________________________
> New Email names for you! 
> Get the Email name you've always wanted on the new @ymail and 
> @rocketmail.
> Hurry before someone else does!
> _______________________________________________
 

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4329 (20090812) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev


------------------------------

Message: 2
Date: Thu, 13 Aug 2009 15:17:41 +0930
From: "FEODOROFF, Ray" <ray.feodoroff@xxxxxxxxxxxxxx>
Subject: [epf-dev] Suggestion
To: <epf-dev@xxxxxxxxxxx>
Message-ID:
	
<ABBED6B72FCD944AA00AB64FF1645C3D0829ED6F@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Esteemed Colleagues,

I have a wbs in excel and have been labouring to block copy it into the
epf compser wbs editor under a capability pattern.

What would be helpful is if I blocked a single column of rows in the
spreadsheet and I was able to paste into the WBS editor either using a
wizard (to select row type) or if I placed a row of what ever type into
the wbs, selected it and then selected paste I get a sibling of entries
from the paste against whatever row type was selected.

Cheers,
Ray
"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email in
error, please notify us immediately. VIRUS: Every care has been taken to
ensure this email and its attachments are virus free, however, any loss
or damage incurred in using this email is not the sender's
responsibility.  It is your responsibility to ensure virus checks are
completed before installing any data sent in this email to your
computer."




------------------------------

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev


End of epf-dev Digest, Vol 44, Issue 7
**************************************
"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email
in error, please notify us immediately. VIRUS: Every care has been
taken to ensure this email and its attachments are virus free,
however, any loss or damage incurred in using this email is not the
sender's responsibility.  It is your responsibility to ensure virus
checks are completed before installing any data sent in this email to
your computer."