For decades, the open source model has been successfully applied to numerous software applications; however, the same success has not been found applying it to game development. Open source games tend to lack the polish of commercial titles, and there are also difficulties in applying the bazaar model (Raymond, 1999a) to game development. On the other hand, open source games are not restricted by third parties such as publishers. On top of this, Raymond’s guidelines for good open source software development contain helpful information for game development. Despite its past, the open source model still has a future, especially in the mobile gaming market.
An engineering project requires a high level of management in order to ensure a positive outcome. Throughout this course, we have learnt what a project is and why project management is important, along with a number of tools and techniques for managing a project. The real difficulty in management, however, is knowing how these techniques are relevant to
a given situation, and being able to apply these techniques accordingly. It is also important to be aware of other team members, and it is this social intelligence which can be the difference between a good project manager and a successful one.
In the past, process models were required only to ensure that projects were completed according to the constraints set out in the initial plan. While the Waterfall model achieved this aim, it was found to be too linear for most large projects, and is now considered to be suitable only when applied to smaller projects. As popularity began to shift to the more iterative Spiral model, the aim of process models began to change towards providing a more flexible structure. This has culminated in the minimal structure of modern agile models such as Extreme Programming. Agile process models are still developing, however (Beck, 1999); this is clear from the problem of a typically shorter lifespan for software developed using agile methods. Therefore, the future of software models will need to involve models that are flexible enough to allow change, whilst still being structured enough to permit the composition of strong design documentation, all while still providing development teams a means of staying within budget and deadlines.