![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: V-Model process in DOORS Topic Summary: Created On: 20-Sep-2007 20:19 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
Telelogic DOORS
» General Discussion
»
V-Model process in DOORS
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.