Hi JoAnn,
I have a couple of questions for you.
First, have we left out any of the basic requirements of your case(s)? Here is what I added to the proposal:
- product group responsible for the change -- which product is this
- regulatory relevance -- ISO, FDA, a specific IEEE requirement
- functional area requesting the change -- engineering, support
- localization required -- yes/no
- function responsible for validation
- identify who made the change (secure ID)
- time and date of the change to the second
- nature of the change -- draft comment, including if change is valid for each reuse of the content (metadata -change)
- resolution of the change: accepted, rejected, and so on
- some way of marking the exact location of the change in the content of the topic
Next, are there any of these requirements that can’t be accommodated with the current bookchangehistory domain elements?
Thanks very much.
with best regards
Tom Cihak
NMG Information Development
Freescale
512.996.5072
From: JoAnn Hackos [mailto:joann.hackos@comtech-serv.com]
Sent: Monday, April 29, 2013 6:20 AM
To: Cihak Thomas-R65612
Cc: dita-techcomm@lists.oasis-open.org
Subject: Re: [dita-techcomm] Groups - Release Management Stage 2 proposal DRAFT uploaded
Could you and or Seth handle the call today? It would be good to review this with all the others. I'm out of town and mostly out of cell phone range this week and next.
JoAnn
Sent from my iPad
710 Kipling Street Suite 400
Hi JoAnn,
I have updated the proposal with the very basics of the medical device industry requirements, mostly taken from the wiki summary section. I obviously don’t
understand their requirements as well as you do, so please edit it as you see the need. I made almost no other changes, pending a discussion during the call.
Thank you.
with best regards
Tom Cihak
NMG Information Development
Freescale
512.996.5072
Thank you for getting this Stage 2 proposal started. However, I assume that you have not looked at the material in the TechComm SC's wiki about release management,
which includes use cases that I authored from the medical device industry. The notes include the requirements for this industry for information in the change-history of the prolog that need to be incorporated into this proposal.
These comments were misplaced under change control. I just duplicated them in Seth's release management info.
They need to be taken into account in your Stage 2 proposal because they are an integral part of our discussion in the committee of the release management requirements.
We have a lot more requirements than the ones you've developed at Freescale.
Let me know if you need to discuss. I hope to make tomorrow's call at 8 am Pacific time. I'm on vacation this week but will try to attend in the morning. I trust
Seth is going to chair.
710 Kipling Street, Suite 400
Submitter's message
Better late than never (I hope) is the release management stage 2 proposal DRAFT. (I said it was the stage 3 proposal, but I was confused about the state.)
A few notes:
--Some parts are blank (I marked these with [[ and ]].)
--Use cases: if you know of others, we should add them.
--Some items in part 1 are blank for now.
--I recast the questions in 'Technical requirements' and 'Costs' to tables for ese of use and commenting.
Thank you.
-- Tom Cihak