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 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 each module is working properly. Testing. As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during Integration phase and tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer.
In this phase, the researchers will test the system to ensure that the developed system functions are according to its requirements and to avoid errors. Maintenance. Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the school library. There are many reasons for the change. Change could happen because of some unexpected input values into the system and it could directly affect the software operation. The software should be developed to accommodate changes that could happen during post implementation period.
In case there are changes necessary it has to be fixed to make the system usable or to make it comply with the library staff wishes. In this phase, the researcher will instruct the librarian on how to operate and maintain the system. Meanwhile other features that will be implementing in this phase are beyond the limitation of the researchers. Scope and Delimitations This project covers the development of Digital Library System of Urdaneta City National High School. Specifically, it will cater all the processes done in inventory, borrowing, returning, and reservation of books.
The Digital Library System of Urdaneta City National High School can access by the admin which is the Librarian, students in UCNHS, teachers of UCNHS and guest which is the alumni and students from different schools. Guest can only inquire for books availability and reserve it personally. However, the proposed system limits on the contents of book that can be viewed digitally, only the title page, table of contents and its overview are applied. Only the students and teachers are allowed to reserve and borrow book through online.
The guest is not allowed to reserve books through online. Teachers and students referral is not included in the system. Data Gathering Techniques The researchers gathered information of the system through structured interview, questionnaire and document analysis to the UCNHS library staff and students. The use of references allowed additional information about software and system Requirements as well as how some organizations use the Internet in making achieves for records that later becomes a collective library on the internet. Structured Interview.
Means of collecting data for a statistical survey. In this case, the data is collected by an interviewer rather than through a self-administered questionnaire. Interviewers read the questions exactly as they appear on the survey questionnaire. The choice of answers to the questions is often fixed (close-ended) in advance, though open-ended questions can also be included within a structured interview. In a series of interviews, researchers knew exactly what information are needed and prepared a list of pre-determined question that will be asking to the respondents.
The researchers gather some viewpoints of the people around the system that could make more efficient particularly to library and employees. Document Analysis. Technique used to gather requirements during the requirements elicitation phase of a project. It describes the act of reviewing the existing documentation of comparable business processes or systems in order to extract pieces of information that are relevant to the current project, and therefore should be consider projects requirements.
In support to the structured interview, the researchers gathered and examined thoroughly the existing documents like catalogue, logbook, and book card. Questionnaire. Research instrument consisting of a series of questions and other prompts for the purpose of gathering information from respondents. Although they are often designed for statistical analysis of the responses, this is not always the case. Questionnaires will be distributed to the students as input to the design of the proposed system. Likewise, with their feedbacks, features can be determined.
Sources of data
The Librarian, Library staff and students were interviewed as primary respondents. Also books and thesis manuscript were used to determine other requirements of the propose system. The researchers used websites, online libraries and other similar studies as references in this study. In addition to this, the researchers will distribute questionnaires to the Urdaneta National High School students to get information that will help in the progress of the development of the project study. Table 1: List of Respondents RESPONDENTS| NUMBER OF RESPONDENT| Librarian| 1| Library Staff| 2| Students| 100| Teachers| 50| Total| 153|.
Subject: Agile software development,
University/College: University of Chicago
Type of paper: Thesis/Dissertation Chapter
Date: 11 October 2016
We will write a custom essay sample on E-Library System
for only $16.38 $12.9/page