For my last blog I am going to discuss generic systems: systems that organisations can purchase instead of making the software themselves. An increasingly popular option as I have previously discussed in earlier posts and that has been discussed by others too. But said I’d give my own input on them.
These generic systems are designed and developed for general use as opposed to custom/tailor designed software packages.
Development of these generic systems differs from in-house software development in many ways. The biggest difference is that the systems designers have little or often no contact with the end-user of the package. Thus generic systems are designed for a market and NOT for specific customer use. Naturally all systems have to be developed with some level of the customer in mind, just with generic systems they are trying to tailor to a wide audience in order to maximise profits in the long run for their system as opposed to suiting a specific firms needs. The actual consumers of these generic systems remain unknown until the product is marketed.
A market orientated development strategy must be directed at a product that supports as many applications in as many user organisations as possible. Succeeding in the market implies having a product design that will be of interest to a big audience and to suite many firms needs!
Yes, generic systems may be a handy tool for particular firms who perhaps don’t have the technology or capital to invest in in-house development, but they mus ask themselves at what cost are they willing to allow for their tailored needs not to be directly designed for.
Also, as an aside I found this video on YouTube, it goes through Business Analysis and System Development Methodoligies! I found it kind of useful in explaining some of the SDLC development theory etc. So ye might like to have a look of it sometime 🙂
http://www.youtube.com/watch?v=yLuvGh2RlBc
Thanks for reading!
Sources: cathaldoyle.com
Eternal Sunshine of the IS Mind 
Really enjoyed this one! 🙂