Introduction The development of programs such as games requires that an organization commit a large amount organizational resources and time. In large projects it is not uncommon for the budgets to run into millions of dollars and take years of effort before completion (Everett and McLeod 2007). In time it has been observed that to develop a sequence of activities that can be used as a guide can ensure that quality software is always produced within the required time frame. There are two common terms often used in the context of software development life cycles namely, methodology and tools. Methodology can be used to define a recommended way of tackling a specific task. On the other hand a tool can be taken to refer a device devices used to accomplish the same task (Everett and McLeod 2007). Using the example of a construction project, the architect’s blueprint can be taken to construe the methodology while the tools used by the construction workers are the tools needed for the task (Everett and McLeod 2007). With reference to software development lifecycles for information systems, methodology can be taken to be the series of stages that are followed in the process of development or revision of a software project (Everett and McLeod 2007). There are several stages in a software development lifecycle and each stage is a segment that consists of specific defining activities. The stages in the lifecycle are normally competed in a specific sequence using a variety of tools. These tools are crucial in that they make the completion of tasks associated with a segment simpler. For example, when designing the data or processes to be followed in the software development process, the developers will use data or process modeling tools (Everett and McLeod 2007). Some examples of data modeling tools include entity relationship diagrams. These tools will help the developers identify essential aspects within the system and model the data accordingly. In the case of process modeling some examples of the tools used include data flow diagrams and use case diagrams. Object modeling tools may include sequence and class diagrams while business processing tools may include workflow process diagrams. All these sequences and tools are essential to the final product in that they assist in production of the required system. The evolution of software development lifecycles can be traced to the early 1960’s (Everett and McLeod 2007). During this formative period a series of do’s and don’ts for software design began to emerge as a standard. Initially it included four main steps namely, planning, analysis, design and implementation. Planning basically consisted of developing specifications for the problem to be solved or developing objectives for the proposed system (Everett and McLeod 2007). The analysis stage involved conducting a thorough analysis with a view to fully understanding the existing system. In the design process the main task was to create processes and data to be used in the new system. Lastly implementation involved the actual preparation of software, construction of data objects, assembly of the new system and finally the cross over from the old to the new system