I read and kept an article by Leslie Goh on Straitstimes newspaper some time back:-
Keeping our trees green - The tree database in NParks logs information on more than one million trees. Leslie Goh finds out what else it can do.
I can still remember in our team of about 7 persons, we really slogged it out to get this system to live! This was one of the longest project I ever consulted and get involved real deep for about 2 years, in my stint with NCS Pte Ltd. I can fully understand why the credit goes to NParks themselves, because we are just Human Resource outsourced. The company we worked for has the slightest ideas what we are working on, because most of the resources are provided by NParks and the 7 of us. We are literary working for the employer who provided our office headcount.
The ironic part is that the initial system that was proposed was by another set of people who have never implemented such a system before, and NParks buy the idea and awarded the project to NCS Pte Ltd. Although we should be thankful to be given such an opportunity to have experienced a full SDLC, especially getting the application to go live. It was definitely a challenging project and have contributed to making what I am today. It was kind of mind blowing experience to some of us, and we can assimilate with NParks, whenever we see the logo on TV or Signboards.
This is a system that integrates GIS, ERP, CRM, and DMS. In simple terms, it is just a Oracle Database Server, that contains Data of several sorts from Maps, to Works Order, Policy Paper, and Public Feedback. There are several means of doing the inputs and outputs, mostly achieved using a 4GL like visual basic, called Powerbuilder by Sybase. It was not a "pretty" system at first, getting it to work as what it should is already a challenge. As the years passes, upgrades and retrofitting done, made it more robust and asthetically appealing. This is what we called the software rigor.
I can still remember very clearly, how I implemented a "daily build release cycle" for NParks to be able to propagate changes into the production environment with proper testing and checks in place. It is a duty based soft process which may change where necessary. And prior to the implementaton of this process similar to that of Microsoft's Daily build, I was single handedly managing all requests for 2 months. At that time, there was one Build every day, which have to be done after all staffs log off. I am very satisfied that the Software and the Process developed for NParks is still in use up till today! It was part of my intention in the design so that it can live more than 5 years, especially with this self-renewal process.
In conclusion, SI (System Integration) companies have the slightest idea what they are dealing with because they just wanted the deal. Its the luck of the customer, who they employed that save the day. What the customer needed is a Database and a Program that handles all the inputs and outputs to and from it. This employee, me, throw in the "Daily Build" self-renewal process free! An individual heroic effort that was not recognised. The only gratification I got is, the software has lived for 5 years and beyond!
