Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Regulations
Topic Summary: How to include regulations within requirements
Created On: 12-Jul-2006 16:04
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 12-Jul-2006 16:04
User is offline View Users Profile Print this message


Laura Aldred

Posts: 9
Joined: 25-May-2006

Just a quick query to anyone who can help.

Our company is very new to DOORS and while we are attempting to structure our project requirements the issue of how to include regulations is starting to raise some questions.   

We think that there is one of two ways to go: 
The first would be going through the regulatory documents and taking the regulations that are applicable to the system we are designing and making them top(ish) level requirements in a module which the design requirements would then satisfy. 
The second way is to have a seperate folder within DOORS which would house all the regulations and we would just link out to the relevant object in a module, but how do you ensure that the design requirements will satisfy these?

How do other companies store regulations in order to prove compliance?

Any feedback or suggestions would be very warmly welcome.

Best Wishes,

Laura

-------------------------
Laura Aldred

Requirements Controller
Marshall of Cambridge Aerospace Ltd, UK
Report this to a Moderator Report this to a Moderator
 12-Jul-2006 22:09
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

A standard hierarchy would to have numerous top-level specs containing various potential requirements. Behavioral, safety, personel, regulations are candidates for these sorts of specs. The Customer and the Contractor haggle over these potential requirements creating a single System Specs that encapsulates all the contractural requirements applicable to the program. In this method, the System Spec has a copy of the text of all applicable regulations.

Another method would be that the System Spec grounds the regulations by refering to it: The ABC System shall conform to the regulations in XYZ document version NN dated 2001-June. This requirement gets pushed down to the design folks who are expected to design in accordance to the regulations.

A mix of the above two is probably correct. Regulated Behavior ('shall give the user the opportunity to cancel') needs to be spelled out in the Sys spec and decomposed down to the design, but Design Regulations ('shall resist corrosion') need only be referenced.

- Louie
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.