ISBN : 978-81-963532-2-3 (E-Book) CompleteCOCOMO model AmajorshortcomingofboththebasicandintermediateCOCOMOmodelsisthattheyconsidera software product as a single homogeneous entity. However, most large systems are made upseveral smaller sub-systems. These sub-systems may have widely different characteristics. Forexample, some sub-systems may be considered as organic type, some semidetached, and someembedded.Notonlythattheinherentdevelopmentcomplexityofthesubsystemsmaybedifferent,b utalsoforsomesubsystemsthereliabilityrequirementsmaybehigh,forsomethe development team might have no previous experience of similar development, and so on. Thecomplete COCOMO model considers these differences in characteristics of the subsystems andestimatestheeffortanddevelopmenttimeasthesumoftheestimatesfortheindividualsubsystems. The cost of each subsystem is estimated separately. This approach reduces themarginof errorin thefinal estimate. The following development project can be considered as an example application of the completeCOCOMOmodel.AdistributedManagementInformationSystem(MIS)productforanorgani zation having offices at several places across the country can have the following subcomponents: • Databasepart • GraphicalUserInterface(GUI)part • Communicationpart Of these, the communication part can be considered as embedded software. The database partcould be semi-detached software, and the GUI part organic software. The costs for these threecomponentscanbeestimatedseparately,and summedupto givetheoverall costof thesystem. 170 Software Engineering Keerthana P, Manasa KN, Ganga D Bengal
176 Publizr Home