RE: [plcs-dex] State and view definitions

["Barker, Sean (UK)" <sean.barker@baesystems.com>]

1) state is useful for following a process, including the design processes. As per my PDT Europe 2001 paper, concurrent engineering processes run at at least three levels: product = universe, product_view=team, and property=individual/subteam. Since we don't have view or property versioning, state might be useful here.

 

2) Engineering analysis uses states to define start, end and intermediate conditions which the analysis applies to. In practice, such analyses are disciple (and therefore view) based. These may also define validity conditions for the design.

 

Therefore, in the long term, it should be done. The only question is "when?"

 

Sean Barker
ATC Filton
0117 302 8184

-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 10 May 2004 14:34
To: plcs-dex@lists.oasis-open.org
Subject: [plcs-dex] State and view definitions

*** WARNING *** This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message.

Hi

Right now we can apply state to versions of products.

 

I was wondering whether it made sense to apply state to view definitions instead or as well as product versions.

 

Regards
Rob

-------------------------------------------   
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401

 

******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ********************************************************************