[14] in Project_DB
Re: Few clarifications needed
daemon@ATHENA.MIT.EDU (Robert V. Ferrara)
Fri Feb 14 16:42:03 1997
Date: Fri, 14 Feb 1997 16:45:11 -0500
To: miki@MIT.EDU, project-db@MIT.EDU
From: rferrara@MIT.EDU (Robert V. Ferrara)
Miki, I think the database is looking great! I offer my thoughts below:
Thanks, Bob
At 3:27 PM 2/14/97, miki@MIT.EDU wrote:
> Looking at the schema, erd and the Data that I have as initial data to
>the Project DB we have the following issues :
>
>
> a. The Practice is not allways filled in. I decided to relax the requirement
>for a Not NULL Practice in the DB's schema.
Right!
>
> b. We have many values for practice, which are not among the 3 (or 4)
>practices of MIT. I will list the practices as they appear in the data
>and ask for a resolution of what are the final values to be put in the DB.
>I would prefer to know what are the values for practice now, as the Web
>interface does not allow for the update of the practice table. (The values
>for practice could be changed only by somebody who is logged into the
>server machine and knows sqlplus).
>
> The values in the data I received are :
>
>ACADEMIC
>OFFICE
>MIT External
>I/T INTERNAL
>SAP / OFFICE
>INFRASTRUCTURE
>I/T INTEGRATION
>I/S INTERNAL
I think this set - plus Null - are OK. A procedure to add a practice (i. e.
send e-mail to MIKI) would finish the job. This will be very infrequent.
>
> d. The status of a project should be a value people may like to search on.
>I will put in few status values at the initial load of the DB and latter
>new values may be added. Looking at the data I have, the status has too many
>values. They are :
I'm not sure people will really search on these and I'm not sure that it's
at all critical to constrain these values. I think that people should be
able to create their own status if possible. The best siuation would be to
pick from a list or make their own.
>
>requirements
>completed discovery
>implementation
>alpha test
>service handoff
>on hold
>in-progress
>completed
>potential
>DESIGN
>RESEARCH PHASE
>ANALYSIS: PROTOTYPE BEING BUILT
>UNDER REVIEW
>Close to implementation
>NEARING PRODUCTION
>DETAILED DESIGN
>CODING
>FINAL TEST
>SOME PORTS COMPLETE
>DESIGN: PROTOTYPE BUILT
>AWAITING IMPLEMENTATION
>COMPLETE
>PRODUCTION
>TEST
>COMPLETE as of January, 1997
>NEARING IMPLEMENTATION
>IN PROCESS
>COMPLETED DISCOVERY
>
>
Anyway, that's my nickel. Keep up the good work.
Thanks, Bob
