Getting Right User Requirements

Getting the right user requirements in initial phase of software implementation is always a challenge. Poor requirements specifications can result in systems that do not meet user needs. In the most extreme case, incomplete or error-riddled requirements specifications result in both time and money wasted building the wrong system. Customer perception of past solution package, past software problems and past operation procedure often build a wrong way of providing the right business requirements. Other aspect in getting the right business requirement is also due to schedule pressure which cause oversight.

Some ways to having a better process are :

• Including Business Process Owners who runs day to day operation in the discussion
• Having a software business analyst to interview business process owners
• Understanding that business requirements might not be able capture 100% since day one, so several can be categorised as current business, new business req and potentially new requirements that are not foreseen
• Mapping requirements into software standard package features, package extentions, and non system solution such as adjustment in the system procedures
• Choosing from several System Development Life Cycle approaches which is fit for a complex implementation such as : Spiral Model, Incremental Development are found will reduce risk.

To support the above process, especially getting complete business requirements - a tool from ravenflow which help to give a visual requirement definition can be also useful to validate if you have missing requirements.

Software Quality Certification

Improving your software quality will require a lot of dicipline from your programmer in executing the SDLC method that you want to apply. I found many fresh programmers often look software source code management, change management, proper documentation as the burden. These topics also do not have to be a popular subject in the college or university. I discussed with couple of programmers with average about 1.5 years experience, many of them do not know the importance of it. While now a day, solution in software development and testing is already so advance which then will 'force' programmer must follow certain rules however providing the explanation of how importance of running those routines is the key.

In regards to equip programmers, system analysts and business analysts with a structured knowledge, it is worth to have your team member certified in these several subjects. The certification is approved by a body call QAI Global Institute. It has several certifications, several of them are :

1. Certified Associate in Software Quality (CASQ)
2. Certified Associate in Software Testing (CAST)
3. Certified Associate Business Analyst (CABA)
4. Certified Software Business Analyst (CSBA)
5. Certified Software Process Engineer (CSPE)
6. Certified Quantitative Software Process Engineer (CQSPE)

Most of the training is done through web and tested through prometric testing center wordwide. So it is quite flexible and also the cost of training also justify for you who want to have the right source of knowledge in improving software quality.