E-Library System
Chapter 2 METHODOLOGY This chapter presents the software development methodology used by the researchers in the design and development of the proposed Online Library system of UCNHS, the scope and delimitation, the date gathering techniques, and the sources of data.
Software Development Methodology
The Modified Waterfall Model in software engineering came into existence because of the defects of the traditional Waterfall Model. The phases of the Modified Waterfall Model are similar to the traditional Model. The main change is that phases in the Modified Waterfall Model life Cycle are permitted to overlap. A lot of flexibility has been introduced in the Modified Waterfall Model in software engineering due to overlapping phases. At the same time, a number of tasks can function, concurrently, which ensures that the defects in the software are removed in the development stage itself and the over head cost of making changes to the software before implementation is saved. The Modified Waterfall Model is more relaxed approach to formal procedures, documents and reviews. It also reduces the huge bundle of documents. Due to the development team, the devote to work on the code has more time and does not have to bother about the procedures. The researchers used Modified Waterfall Model because documentation is produced at every stage of the software development. This makes understanding the product designing procedure, simpler and will closely work with the school and users to understand their needs. The figure below describes the structure and activities in the Modified Waterfall Model (Bhakti Satalkar, 2010). Requirement gathering and analysis System Design Implementation Testing
Maintenance
Figure 2. Modified waterfall Model
Requirement gathering and analysis. All possible requirements of the system to be developed are captured in this phase. Requirements are a set of functions and constraints that the end user (who will be using the
Software Development Methodology
The Modified Waterfall Model in software engineering came into existence because of the defects of the traditional Waterfall Model. The phases of the Modified Waterfall Model are similar to the traditional Model. The main change is that phases in the Modified Waterfall Model life Cycle are permitted to overlap. A lot of flexibility has been introduced in the Modified Waterfall Model in software engineering due to overlapping phases. At the same time, a number of tasks can function, concurrently, which ensures that the defects in the software are removed in the development stage itself and the over head cost of making changes to the software before implementation is saved. The Modified Waterfall Model is more relaxed approach to formal procedures, documents and reviews. It also reduces the huge bundle of documents. Due to the development team, the devote to work on the code has more time and does not have to bother about the procedures. The researchers used Modified Waterfall Model because documentation is produced at every stage of the software development. This makes understanding the product designing procedure, simpler and will closely work with the school and users to understand their needs. The figure below describes the structure and activities in the Modified Waterfall Model (Bhakti Satalkar, 2010). Requirement gathering and analysis System Design Implementation Testing
Maintenance
Figure 2. Modified waterfall Model
Requirement gathering and analysis. All possible requirements of the system to be developed are captured in this phase. Requirements are a set of functions and constraints that the end user (who will be using the