Advantages :

• main task to be tackled in each phase is clearly outlined

• easier to divide tasks

• alerts the developers to which task to place their attention on

• developers can tell immediately if they are behind schedule

Inherent Problems :

• system is too rigid

• once a team lags behind others, it may lead to confusion in re-allocation of tasks and emphasis

• different nature of projects may require different allocation of work emphasis for each aspect

• lack of software assessment for inception phase (the first phase) may lead to wrong project goals to be written and followed, leading to huge losses in time, effort and costs.

• software assessment should have at least secondary importance for each phase, since it would be easier to rectify a mistake as it unfolds rather than to try to change it at the very end

Modifications :

Inception

Component	Percentage allocated (%)	Reason (s)
Software Management	15	important to let individual groups know respective roles to prevent duplication of effort
Software Architecture	25	main components of software should be drawn easier to visualize once available "arsenal of equipment" is made known
Software Development	10	nothing important is needed to be developed at the moment
Software Assessment	50	main task should be the analysis of the job draw out requirements of software solution

Elaboration

Component	Percentage allocated (%)	Reason (s)
Software Management	05	not much integration is needed since the main development of the software itself is yet top take place
Software Architecture	45	more importance drawn due to higher need to fully understand what components are needed in the software
Software Development	25	higher percentage allocated since software development is made possible with more details on the software required
Software Assessment	25	re-allocation of tasks might be required

Construction

Component	Percentage allocated (%)	Reason (s)
Software Management	20	more emphasis should be placed on software management since integration of various modules would be required
Software Architecture	05	main components required would have already been discussed, selected and readied for the main portion of the physical development of the software
Software Development	45	main task required in software construction phase
Software Assessment	30	continuous assessment of software development is important

Transition

Component	Percentage allocated (%)	Reason (s)
Software Management	40	last stages of software integration should be taking place here
Software Architecture	05	not much importance
Software Development	20	suitable changes and fine-tuning are to be made
Software Assessment	35	reviews on the state of the software is important

 

Best viewed with a resolution of 800x600 or better.

©2003 Tang Teck Leng