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
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 system) expects from the system. The requirements are gathered from the end user at the start of the software development phase. These requirements are analyzed for their validity, and the possibility of incorporating the requirements in the system to be developed is also studied. Finally, a requirement specification document is created which serves the purpose of guideline for the next phase of the model. In this phase, the researchers gathered data that might be used in the proposed system and also through an interview with the library staff, performed observation to the transaction and conducted survey with students of Urdaneta City National High School. System Design. Before starting the actual coding phase, it is highly important to understand the requirements of the end user and also have an idea of how should the end product looks like. The requirement specifications from the first phase are studied in this phase and a system design is prepared. System design helps in specifying hardware and system requirements and also helps in defining the overall system architecture. The system design specifications serve as an input for the next phase of the model. In this phase, the researchers will use USE CASE, DFD, ERD to evaluate and design the system in accordance to the requirements needed. Implementation. On receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality; this is referred to as unit testing. Unit testing mainly verifies if the modules/units meet their specifications. The researchers will use visual basic 2010 as programming language to create and develop the system. Likewise, MS SQL as database is used as the back end to store, maintain and manage the database integrated to the system. Upon implementation, several testing will also be done to ensure that...
Please join StudyMode to read the full document