Estimation and appraisal of the costs associated with the projects is the major focus of the module. The students must proceed with the usual time pressure for the design phase. However, unlike other projects, they will also be subjected to the burden of the need to provide construction paper and other cost estimating aids. Other requirements to be met during the design phase are the selection of the Domain Model, the physical representation of the system, and the performance of the system, as explained in the earlier sections of the course.
The COCOMO II model has been refined to better reflect the latest trends in software engineering and the benefits of software reuse. A recently published book by Kimball (Arbus 2013), provides an interesting review of the evolution of the model from its inception in the early 1960s to the latest COCOMO II release (Arbus 2013; Kimball 2013). As software is translated into a formal model, the model is increasingly sophisticated, because the need for well-organized information structures and abstraction are better quantified.
A comprehensive list of all the information components and their relationship to each other will be made available to the students. They can then define the impact of each component on the overall system design. This model will also allow the students to understand the importance of each information element, along with the consequential risk associated with each cost.
It is an activity driven approach wherein all the students are required to prepare a project proposal. The proposal will not be returned, instead, the students will be asked to describe their plan at a final classes. The students are allowed to use any soft-ware development tools to approach their proposal. But, in order to ensure the standard of the proposals, it is recommended that the students use an appropriate tool set to design, document, and code the information system. d2c66b5586