| OSEE Setup Too Hard for Customers Who Do Requirements??? [message #563405] |
Sun, 13 April 2008 21:15 |
 Ben Garbers
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
I went through the demos on the site you sent to us. I have some concerns
on using OSEE based on the setup of the server side. This was the
comments I originally had making the plugin on the eclipse client file
based. You could think of a view like they have for web.xml files where a
user could download the plugin and then be able to right away input
requirements information. If they are dependent on OSEE in communicating
with the plugin they will have to set this up which for novice users could
take some time. Individuals who do requirements usually are not database
setup savvy. Originally, you said you did not want individuals to have to
be very technical with cvs or subversion to check there files in and
actually had experience in this where it was very ugly. However, even if
they did not use cvs or subversion they could enter their requirements and
it would be stored on their local pc within eclipse. It would be up to
them to back the requirements up within eclipse then...Whether they would
use cvs, subversion or just backup their directory of where there project
is located would be up to them.
I almost think that when designing this we should offer the flexibility of
a user to choose whether they want to use an OSEE backend or to just input
information where it would be stored in an xml based file. This would
give customers flexibility to choose whether or not they would want to set
up the osee environment so their eclipse clients could communicate to it.
|
|
|
Powered by
FUDForum. Page generated in 0.02994 seconds
] 
Search
Help
Register
Login
Home
