For example, Dr.

Sunday, 10. April 2011

Huizinga, COTS can offer higher quality because they are developed by vendors who specialize in systems that provide the required functionality and are well-tested by many users. Dr. Huizinga notes that this might include the use of specialized COTS (commercial off-the-shelf) hardware and software components. “Many times, this is the point at which an ROI study will be carried out in order to determine project costs and benefits,” says Dr. According to Dr. Huizinga believes that taking such measures reduces the error-prone human influence when the software is implemented. Following are a set of practical guidelines to approach a software development project, established by two university professors and business consultants with specialized expertise in the computing, engineering, and general business environments. For any software development or other project initiative your company may be considering, it is critical to have in place and practice a set of effective and proven guidelines to ensure project success and delivery of the expected results:  taking into consideration the role and responsibilities of a well-qualified project manager, knowledge of important business and financial aspects, and a step-by-step process that all contribute to the solid foundation and implementation of an effective project plan. Because of the complex nature of software projects and the technology involved, new software development warrants this systematic approach. Designing a strategic plan means taking into consideration all aspects that can contribute to success or potential failure. Embarking on the Initiative: Key Steps to Consider With a comprehensive approach and a competent project manager in place to guide the new software development initiative, there is another important element your organization may find helpful as you embark on the project: establishing specific steps that can be followed to project completion that are based on proven industry experience in such a project environment. When observed over an extended period, notes Dr. Huizinga. Gehrs points out that testing also may vary quite widely depending on the individual testing procedures adopted by the organization. Gehrs points out that development cycles may produce several versions of the software: • Alpha: preliminary feature/functionality only • Beta: used for internal testing or usability testing • Release Candidates: usually a very stable build that may need minor tweaks • Production Build or Gold Master: ready for release.