![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: impact on support resources and project teams Topic Summary: how to plan for support and project lifecycles? Created On: 28-Jul-2006 21:59 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I work with a large company in LA that is implementing Doors. We are trying to explain to management why we should be planning for a Doors support team.
I would appreciate anything you can share with me about successful and unsuccessful implementations and how the success or lack thereof may relate to how well the support areas are staffed. Edited: 28-Jul-2006 at 23:38 by Jim Jones |
|
![]() |
|
![]() |
|
We went through a 7 day project architecture workshop with a Telelogic professional services person to discuss the lifecycle of requirments gathering (we only use DOORS for requirements at this time.) This also included what type of link_modules sets to establish and setting them up for all projects. We are trying to prescribe a consistent use of DOORS for our project requirements instead of letting people link things at free will.
Once we established our artifacts and our linking schemas, we started creating MS Word or Excel documents to start collecting data outside of DOORS (just so we weren't confusing people by learning a new tool as well as practices). Creating the templates and writing up the guidelines has been an ongoing thing for about 1 yr of approx 4 FTE's, but would highly recommend you get someone with good tech writing skills (as we learned the hard way!!) Once we filled in our templates we started creating DOORS template projects, created new projects and copied the templates, and then imported our documents and started linking. That's when we found out that our templates didn't quite work the first time and had to do a little modification (not nearly as time consuming as setting up the templates in the first place). Now when new projects come on board to use DOORS, they can capture their requirements in the MSoffice templates and we can easily import them into DOORS. Ultimately we want/need to train users on capturing their requirements directly in DOORS, but we are still trying to get our BSA's through a more generic Requirements Gathering 101 class to make sure they are gathering good requirements. (Basically putting junk into DOORS really doesn't help a project.) So lot's of architecture thought should be done prior to jumping in and using DOORS in order to have an more consistent way of managing your projects down the road. We haven't gotten this far yet, but our Telelogic sales repr indicates there is one company that has only 3 or 4 people that administor and trouble shoots problems for all the projects now that they are using it. It seems it's really the startup time that will take the most effort. Hope this helps. ------------------------- Brenda Heiss Cornell |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.