Olin Lathrop wrote:
>
> While there may be some slight advantage to having your stock listed in a
> computer, you seem to be forgetting the cost. =A0For that database to be
> useful, it has to be accurate. =A0That means someone has to make a entry =
every
> time they add or remove parts to/from the bins. =A0That would take a lot =
of
> time and severly increase the hassle level of building small prototypes,
> making quick changes to something, or quick experiments. =A0These are exa=
ctly
> the kind of procedures that make big companies slow to get anything done.
>

That can be normal company's database of parts. Plus all the records
an engineer gets parts from the stock would build his personal list of
parts. From time to time, say once a week, the engineer would look
through the list and mark which parts are in his "personal" stock and
roughly in what quantities.

Another engineer would search the "personal" stocks for a specific
part. He would borrow the part and the operation may or may not be
recorded into the database, that would depend on the part and the
relations within the team. Some "expert" functionality over that would
be nice, say to search by part's parameters, not only by name, etc.

The programming technology should not be "fancy". MVC, in my opinion,
is a bit overkill here as the web server is local and the Presentation
Layer is not traffic consuming. The problem, as I see it, is that an
EE can't write clear specs on this project, as he has no clue about
the programming technologies ("I don't know PHP, and I've never even
heard of nanoMVC."). And SE knows the programming technologies but he
got no clue what EE is expected about the project.

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.