The SPAMEX system. :: Computer Science

The SPAMEX system.1. IntroductionThe SPAMEX system proposed by SCABB is outlined in the attachedletter. I hope to suggest a suitable software process personate for thedevelopment of the SPAMEX system in the following document.2. The Waterfall ModelThe falls model consists of several poses of the developmentlife-cycle, severally of which are completed in turn.The first stage in applying this model to the development of theSPAMEX system would be to document the system concept and identify thesystem requirements. After analysing these requirements, one wouldbreak the system into pieces, for modelling TIP user interface,customer database etc. Each of these components (or subsystems) nowrequire detailed design before the coding can take place. After separatelyof the components has been metre-tested and debugged individually, they canbe integrated to form part of the whole SPAMEX system. The system as awhole can now be tested and deployed although requiring ongoingmaintenance.The wa terfall model was the first of its kind and is still widelyused. It allows documented evidence of progress as each stage must beapproved and signed off before the next stage is undertaken. Thisshould appeal to SCABB since they have access to these documents andcan track the progress of the development of their software. It wouldalso benefit the project manager, who would be able to ensureconsistency in the quality of the software and manage accordingly hisinvestments in time and money.The model also allows the various stages of the development to beoverlapped in accordance with the wishes of SCABB. This isparticularly useful in this case as the current brief presented bySCABB is non to the detail required by the developer. bring forward meetingsbetween both parties would be essential and ongoing changes inrequirements will be inevitable. However, such iterations are notpossible without significant investments in time and money from boththe developer and SCABB.As we can see, one of the main characteristics of the waterfall modelis that commitments be made for each stage early on and each one mustbe completed and signed off before the next is undertaken. Manyproblems may arise from this when applied to the SPAMEX system. Forexample, instability and other coding problems may not be discovereduntil the testing of the whole system. In such cases re-design may berequired, which is very problematic because from the very beginning,this model assumes feasibility before implementation.The waterfall model works well when requirements are stable and welldefined, the present SPAMEX brief is somewhat vague and specificdetails may only be attained through extensive client-developerinteraction.