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: V-Model process in DOORS
Topic Summary:
Created On: 20-Sep-2007 20:19
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.
 20-Sep-2007 20:19
User is offline View Users Profile Print this message


Paul Lusardi

Posts: 1
Joined: 30-Aug-2007

Hello all, I am looking to create a DOORS project PROCESS template, using a V-model style where I have templated the following:
formal modules, link modules, sets, roles, views, permissions, etc in a project called "department template"-- thus creating a department standard project template for all DOORS project personnel.


what I want to do is when there is a new project, i copy the department template to a new project (and everything is already set up) and then have the person assigned to the "requirements role" enter requirements while the design team checks their view and sees that there are requirements ready to be designed, they enter their design and the developers see that they can start the coding.....and so on for the testers, etc...

It's a work flow process with DOORS in the middle -- where every person assigned to a particular role logs into DOORS, checks their "ready for you to do-something" view, makes their changes and it gets removed from that view and into someone elses view.

Has anyone atempted to do this?

What are the pro's and con's

thanks,

Paul Lusardi
lusardpj@westinghouse.com

Report this to a Moderator Report this to a Moderator
 20-Sep-2007 21:18
User is offline View Users Profile Print this message


Kevin Murphy

Posts: 206
Joined: 15-Jul-2005

Paul,

The main problem with this approach, in my opinion, is that every project is different and thus has different needs.

Maybe your company develops software/hardware that is similar to other items developed by your company. In other words, the project/schema/attributes are very similar.

The way you described this process, in my opinion, is too granular and too focused on DOORS.

Instead of having a new project copied and pasted, you should maybe make generic modules (like say an SRS) with pre-defined attributes and views.

When a new project , if there are 5 subsystems modules that derive 5 lower-level modules, the DOORS Admins have guidelines as to how to setup the schema according to your company's standards. They then start with the templates, but then document any custom attributes, types, views, and traces needed.

Thus, you have one project that contains the DOORS Template modules, and your admins and stakeholders know which templates they want put into the new project.

There is no "one size fits all" for project management. A project, by its very definition, is unique.

Give guidelines and standards, but allow for flexibility.

-------------------------
Kevin Murphy
http://www.baselinesinc.com
The Requirements Management Experts
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.