Arcade Collecting > Pinball
Need for Pinball Management software?
ChadTower:
--- Quote from: Cenobyte on July 12, 2011, 10:36:20 am ---From that standpoint it's often easier to develop a small piece of software with all the things in it that the user wishes than to adapt an existing system, which always results in compromises. A dedicated program can also be optimized for fast input of data, skipping optional stuff that most people will never use.
--- End quote ---
Look at existing issue management systems. They are designed to be customized in a short timeframe for your needs. Don't just dismiss them because you think you know what they might be.
Any software developer who has worked in an organization that has any sort of software lifecycle process should have at least used a basic issue management system. Any developer in a good lifecycle process has used a decent one.
TopJimmyCooks:
M$ Access.
There was a time when I could develop this very user friendly dbase with frontend for you in about an hour. Unfortunately, that time was 1993.
ChadTower:
Yep, and in a lot of those systems, you could have the db tables implemented in less time than it took to figure out what tables you really need. The front end form will be generated for you in the process. You don't have to spend a week designing a full on workflow here unless you really do want one.
TopJimmyCooks:
CT, you know what I'm talking about. Roll your own rather than waiting for JD Edwards or Oracle to drop some megabloat "custom" app on you.
tables:
list of machines
list of possible areas of repair
list of responsible fixers, name, phone, email etc.
list of repairs needed done
list of repair requests/trouble tickets???
list of possible parts
list of parts vendors
list of list of parts orders/status
list of parts inventory
Hmm, wonder if I still have a copy of Access 97 installed anywhere. . . . . ......
ChadTower:
--- Quote from: TopJimmyCooks on July 12, 2011, 04:29:35 pm ---CT, you know what I'm talking about. Roll your own rather than waiting for JD Edwards or Oracle to drop some megabloat "custom" app on you.
tables:
list of machines
list of possible areas of repair
list of responsible fixers, name, phone, email etc.
list of repairs needed done
list of repair requests/trouble tickets???
list of possible parts
list of parts vendors
list of list of parts orders/status
list of parts inventory
Hmm, wonder if I still have a copy of Access 97 installed anywhere. . . . . ......
--- End quote ---
That list can probably be normalized way down into 4-5 tables or maybe split off into two separate ticket types: repair tickets and parts inventory.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version