2010
Feasibility Study Report
Name Index Number
S.C Rangoda 09020871
C.U Serasinghe 09020551
T.K.N Weragoda 09020748
G.K.D.B Kiriella 09020888
G.R Sapukotana 09020519 Group 10
10/15/2010
Table of Contents
1. Purpose of the document .......................................................................................... 3
2. Scope .......................................................................................................................... 3
3. Overview of the System ............................................................................................. 4
3.1. Software architecture overview ........................................................................................ 4
3.2. Hardware overview .......................................................................................................... 5
4. Current Functional Procedure .................................................................................. 5
4.1. Examination procedure .................................................................................................... 5
4.2. Recording attendance details ............................................................................................ 5
4.3. Recording personal details ............................................................................................... 5
4.4. Inventory controlling ........................................................................................................ 5
4.5. Gallery booking ................................................................................................................ 6
5. Requirements Identified ............................................................................................ 6
5.1. Functional requirements ................................................................................................... 6
5.2. Non-functional requirements............................................................................................ 6
6. Feasibility Parameters of the proposed system ...................................................... 7
6.1. Technical feasibility ......................................................................................................... 7
6.1.1. Client side technologies ............................................................................................ 7
6.1.2. Conclusion ................................................................................................................ 8
6.1.3. Server side technologies ........................................................................................... 8
6.1.4. Conclusion ................................................................................................................ 8
6.1.5. Web servers ............................................................................................................... 9
6.1.6. Conclusion Selected technology: Apache ................................................................ 9
6.1.7. Database management system .................................................................................. 9
6.1.8. Conclusion .............................................................................................................. 10
6.2. Operational feasibility .................................................................................................... 10
6.3. Legal feasibility .............................................................................................................. 11
6.4. Cultural feasibility .......................................................................................................... 11
6.5. Economic feasibility....................................................................................................... 12
6.5.1. Cost-Benefit Analysis ............................................................................................. 12
6.5.2. Project development cost for the proposed system ................................................. 13
6.5.3. Projected annual operating cost for the proposed system ....................................... 13
6.6. Schedule feasibility ........................................................................................................ 14
7. Alternative solutions ................................................................................................ 15
7.1. Standalone system .......................................................................................................... 15
7.2. Flat client server system ................................................................................................. 15
7.3. Hierarchical client server system ................................................................................... 17
8. Recommended Solution (Flat client server Web based System) ......................... 17
9. Candidate solution matrix ....................................................................................... 18
10. References ................................................................................................................ 19
1. PURPOSE OF THE DOCUMENT
In order to satisfy all user requirements, analyzing feasibility of proposed system is very
important to reduce circumstances arising while and after implement the system. This is
believed to be vital for a successful project.
So intention of this document is to provide clear idea about the alternative system solutions
and brief explanation of results of feasibility study for the ‘Nenasayura’ information system
and through that to introduce most suitable solution for the problem.
2. SYSTEM SCOPE
The system scope of ‘Nenasayura’ information system can be described as follows:
Handling user levels by creating user accounts logins.
There will be user accounts and login system for school teachers who are
uploading term test papers and questions.
Uploading, downloading, storing and retrieving of questions and question papers.
There will be a rating system for questions and papers.
Question papers and module wise can be found easily by user define search system.
This document provides the description on the problem that the project intends to address. Objectives
of the projects and the current functional procedure of the semi computerized system are mentioned in
An economic discussion on the selected alternative and how it meets the established objectives and
the functional requirements are further discussed in detail. And discussion on technological capabilities
of developing the selected alternative and the operational impact of the system on the current
environment is addressed.
This document further includes a discussion and an economic analysis of the life cycle costs and
benefits of the project and the costs and benefits of the current method of operation during the life
cycle of the project.
Under the schedule feasibility the project schedule and the key milestones are defined.
3
3. OVERVIEW OF THE SYSTEM
Functioning of the System
The system will be developed to automate the following major processes including their sub process.
1. Recording and managing the attendance details of students, lecturers and non-academic staff
2. Computerizing of the student attendance marking process
3. Managing exam results
4. Time table management
5. Inventory control
6. Record personal details
7. Exhibition details of gallery
With respect to those processes, the system will be generating following reports:
1. Attendance details
a. Student
b. Lecturer
c. Non-Academic
2. Exam results details
a. Personal transcript
b. Report
3. Annual leave details
4. Inventory report
Since the proposed solution is web based, client end software is usual web browsers.
3.1. Software architecture overview
Following applications/systems are required in the deployment environment.
1. Operating system(Windows XP)
2. MySQL as database management system
3. Apache as web server
Following applications are to be used in the development environment.
1. PHP as server side technology
2. HTML/JavaScript/CSS as client side technologies
3. Apache as web server
4. MySQL as database management system
5. Sinhala Unicode
4
3.2. Hardware overview
The system will be running on the server computer and the usage is distributed over the office,
department and labs.
The main hardware to be used in the system:
i. Web server machine
ii. UPS for the web server
iii. Computers for the department heads
iv. Printer
4. Current Functional Procedure
Faculty of Visual Arts of the University of Visual arts & Performing arts consists of nine departments
and a gallery. Currently faculty has a semi computerized system. We have identified following
processes which are done using this existing semi computerized system.
4.1. Examination procedure
The clerk who is responsible for entering the exam marks, record them in MS Excel sheets and finalize
and send them to their head office in the University of Visual Arts and Performing Arts. The finalized
results sheets will be issued by the examination branch of the University of Visual Arts and Performing
Arts. Results are displayed in the notice board including the index number. Students can personally
request for result sheets from the head office.
4.2. Recording attendance details
This is a semi computerized process. By using printed signed attendance sheets clerks enter the
attendance details of students into MS Excel sheets and store them in the computer. They use these
records for calculations like checking 80% of attendance of students for examinations and 51%
attendance for Mahapola and Bursary scholarships.
4.3. Recording personal details
Personal details of students, lecturers, and non-academic staff are recorded manually into the files by
clerks.
4.4. Inventory controlling
It is completely a manual process. The store keeper manually keeps the inventory details. For an
example when someone wants to request some materials he/she has to fill a printed form and hand it
over to the stock keeper. Then if it is a valid request the stock keeper issues materials and record the
issuing details.
5
4.5. Gallery booking
The gallery is under the control of the Faculty of Visual Arts, but it is used by all three faculties in the
University of Visual & Performing Arts (Faculty of Aesthetic, Faculty of Dancing and Faculty of Visual
Arts). Gallery booking details entered into the files and exhibition details like name of the exhibition
are displayed on the notice board.
5. Requirements Identified
5.1. Functional requirements
1. System should facilitate for recording personal details of students, lecturers and non-
academic staff in the database.
2. Student attendance should be recorded and calculated for the Mahapola and Bursary
scholarship payments and for the examination purposes.
3. Exam results should be stored in the database and facilitate for viewing exam results online.
4. Timetables should be displayed by the system.
5. System should facilitate for entering inventory details, managing issuing of materials and tools
and for calculations like depreciation of tools and usage of materials
6. Exhibition details of the gallery should be displayed. Such as the name of the exhibition, date
and the time of the exhibition and the names of the organizers.
7. Appointment letter for the visiting lecturers should be displayed online by the system. And
also visiting lecturers’ attendance should be recorded in order to calculate lecture hours.
5.2. Non-functional requirements
1. Total security to the data in the data base should be provided, since the database contains
the data about student results, students’ and lecturers’ attendance details, students and
lecturers personal details and inventory details.
2. Performances and speed should be maximized.
3. Interface requirements should focus more on non technical users
6
6. Feasibility Parameters of the proposed system
6.1. Technical feasibility
The proposed system is completely developed as web based system and it is requires
to use web technologies appropriately.
Currently available web technologies-PHP, JSP and Servlets, ASP.net, Perl / cgi
Servers: Apache, Microsoft IIS, Google web server
DBMS: Oracle, Mysql, Microsoft SQL server, Access
The system is developed using PHP as the main development language due to clients
hard ware specification, and Apache has been chosen to be the web server due to high
reliability and flexibility in between platforms. MySql is chosen to be the DBMS of the
system, due to flexibility
Availability of the chosen technologies: All the chosen technologies are widely used in
the world and are available for free use. These technologies are all open source
software (MySql, Apache, PHP, Java Script) and does not require any registering or
purchasing of any kind.
Maturity of the technology Apache over 50% of the servers in the world are Apache
therefore the technology is considered to be mature enough to be used.
PHP: relatively new but gaining popularity fast
Source Availability: These open source software sources are available widely and
knowledge is freely available through the internet.
Technical expertise: The software team currently does not possess the required
expertise to complete the system, but it is possible to expertise the technologies in the
given period of time.
6.1.1. Client side technologies
Description HTML/CSS/JavaScript Flash/Action Script Java Applets
[2] [2]
User friendliness High High Very low
Life cycle stage Matured Growing Declining
Bandwidth usage Very low High Low
Browser support Enabling JavaScript Flash player JVM
Security Medium Medium Low
Table 6.1.1 – Client side technologies
7
6.1.2. Conclusion
Selected combination: HTML/CSS/JavaScript
We have selected this technology for the client side mainly because it is the matured technology when
comparing with the other client side technologies. It also has higher user friendliness and majority of
web browsers are JavaScript enabled by default.
6.1.3. Server side technologies
Description PHP [3] .Net [4] JavaEE
Availability of free
and open source Yes No Yes
components
Life cycle stage Mature Mature Mature
Scalability Low High High
Operational cost Low High Medium
Availability of High High High
resources
Popularity High Medium High
Reliability Very low High High
Security Low High High
Table 6.1.3 – Server side technologies
6.1.4. Conclusion
Selected technology: PHP
We have selected this technology because it has free and open source components. We do not have
to handle high secured data in our system. Therefore low security of PHP is not that affected for our
system. We have highly considered this factor because it is extremely economical for the client as well
as for the developers.
8
6.1.5. Web servers
Description Apache IIS
Free and open source
Yes No
Reliability High Medium
Description Access MySQL Oracle
Fast response High High
Free and open
No Yes No
source
Platform
independency Dependant Independent Independent
Concurrent User
Accessibility Single user Multiple users Multiple users
Table 6.1.5 – Web servers
6.1.6. Conclusion
Selected technology: Apache
In the world over 50% of web servers use the Apache as the web server. Therefore this technology is
considered to be mature enough to be used.
6.1.7. Database management system
9
Database Size Small Large Large
Security
Less High High
Table 6.1.7 – Database management system
6.1.8. Conclusion
Selected technology: MySQL
We have selected MySQL for the DBMS because in this proposed system we have to handle
considerable amount of data. For an example students, lecturers, academic staff, non-academic staff
personal details, exam result details, inventory details. And here also we considered the economical
factor when selecting the suitable DBMS for the proposed system therefore MySQL is the best solution
because it is free open source.
6.2. Operational feasibility
1. Proposed System is a web based system and therefore it facilitates for the multiple user
accessibility. This overcomes the time consuming problem of existing semi computerized system.
2. Indexing and searching will be easy because system the finds the necessary records from the
database and will retrieve and output data in seconds without having someone to look inside the
files manually.
3. To perform some current manual processes it needs to meet several personals. The system can
overcome this issue by allowing the relevant person to do it using single interface in front of the
system.
4. Data backups: The current semi computerized system maintains files and they do not keep any
systematic backups at all. The proposed system facilitates for keeping such backups and in any
case of data loss system data will be safe because of having data backups.
5. Data retrieval and the data presenting will be done by the system so the report generation will be
automated by the system.
6. Security issues: User access levels will be set and the system will only allow necessary access
according to those levels.
10
6.3. LEGAL FEASIBILITY
In this section we evaluate how well the solution can be implemented within existing legal and
contractual obligations.
1. Copyright Issues: We will be using open source software & technologies for
developing the proposed system. They are free to use, distribute and modify. Because of
that there will be minimal licensing and other related issues and it will not violate any law
related to copyright issues.
2. Government Constraints: The proposed system is will be dealt with government
schools and therefore it may be subject to rules and regulations imposed by government.
3. Code ownership: The proposed system will only developed by group members and will
not take any outside assistance. Because of that there will not arose any issue related to
code ownership.
6.4. CULTURAL FEASIBILITY
The main objective of this is to evaluate how well the solution will be accepted in the given
social (students & teachers) and cultural climate.
The final output of this system will look like an application which runs on the Internet. The
government has established ‘e – nenasala’ centers in island wide which provide IT
knowledge and Internet facilities. Therefore it will not be too difficult to access the system to
students who are in rural areas. And also they can learn from those centers about Internet
access and how to use the system.
Users of our proposed system will not be arose problems related to the language. Because we
expect to include instructions to our proposed system in Sinhala language as well as English
language.
Most of teachers in Sri Lanka have fair IT knowledge and government also conducting many
IT training programs to school teachers. Therefore it will not difficult to access and operate
(upload papers) proposed system to school teachers. And also system will have user friendly
11
interfaces and it will be much easier to users of the system.
6.5. ECONOMIC FEASIBILITY
The objective of this is to evaluate the cost effectiveness of the proposed system. To measure
the economic feasibility, we use cost/benefit analysis.
Through this analysis we determine the benefits and savings that are expected from a required
system and compare them with costs will incurred when implementing the system. However,
it should also be noted that some benefits could be intangible (non monetary).
Cost-Benefit Analysis
Benefits
1. Efficiency and effective services can be provided.
2. Reduction in labor cost as fewer employees would be needed in entering the data into the system
and
process the information.
3. Data redundancy and security issues would be lessened due to improved backups and security
features in the system.
4. Eliminates inconsistencies due to centralized data management.
5. Saves paper and hence money and environment due to less use of paper.
6. Increases collaboration and communication because of multiuser system.
Costs
1. Development & Purchasing Costs
a. Hardware- I. sever machine (4GB ram 320HDD)
II. twenty personal computers(2GB ram,120HDD)
b. Software (fully free and open source software)
2. Installation & Conversion Costs
a. Installing the system
b. Training the staff
3. Operational Costs
a. Maintenance of the system
4. Personnel Costs
a. Operational staff cost
12
6.5.1. Project development cost for the proposed system
Expenses (Rs) Total (Rs.)
100000
System analyst Rs.500/hr
x 200hrs
120000
Programmers Rs.600/hr x
400hrs
15000
Database Administrator
Rs.250/hr x 60hrs
5000
Training for the staff
240000
New hardware and software
Table 6.5.2 – New server machine (4GB Project
100000
ram 320 HDD)
development cost for the
New twenty PCs(2GB ram
1000000
160 HDD)
proposed system
1100000
Total projected
1340000
development cost
6.5.2. Projected annual operating cost for the proposed system
Expenses (Rs.) Total(Rs.)
Maintenance cost of the
20000
server and the PCs
Data entry and employee
30000
cost
Total projected annual
50000
operating cost
13
Table 6.5.3 – Projected annual operating cost for the proposed system
6.6. Schedule feasibility
With regard to the timeline of the proposed system, the below Gantt chart will show the mandatory
deadlines that we are expected to achieve. (Refer the printed report for further clarification of the chart)
14
Figure 6.6 – Schedule feasibility
7. Alternative solutions
7.1. Standalone system
Standalone desktop based application: everything is kept and processed in the same PC.
Implementing a standalone system has following benefits.
1. Data security is very high. Because there is only one computer in the system. So there is no
need to transfer data over a network.
2. Because of the entire system is in one machine, data can be accessed very quickly.
Therefore reliability is very high.
3. Cost is very low. Because the whole system is located in one machine, there is no need to
buy additional computers or there is no need to implement a network.
4. Easy to implement and the maintenance cost is very low.
But it has following drawbacks too.
1. Only one user can access the system at a time. Multiple users are not allowed
simultaneously.
2. If this single machine fails, whole system will fail. So need a proper and regular backing up
strategy.
Using a standalone system isn’t a feasible solution for our client, because client needs one or more
users to access the system at the same time. Therefore multiple users must be allowed by the
system.
7.2. Flat client server system
Figure 7.1 - Flat client server system: Single server multiple clients. [1]
15
The system will be separated in to two sub systems as client and the server. The client can be
developed in several ways.
Web based application
Advantages
1. Runs on browser. Therefore no need of installing at each client. If the server is connected to
Internet clients can even have the access anywhere in the world.
2. Ease of updating the system.
3. Less dependency on platform.
Disadvantages
1. Will not work in the same manner in all browsers.
2. Limited features: Limited by browser limitations. Cannot play as we do in desktop
applications.
Desktop applications
Advantages
1. Runs on the operating system have much power than a browser.
2. Less communication traffic.
Disadvantages
1. Not easy to update. Have to update in each machine.
2. Maintenance and development is hard.
3. Cannot access if the desired client is not installed.
Therefore the most suitable system is a web base system.
Implementing flat client server web base system has following benefits to our client.
1. Multiple users can access the system at the same time.
2. Increase the collaboration.
3. Efficient and effective services can be provided.
But at the same time it has following drawbacks.
1. Low scalability.
2. If this single server fails, whole system will fail.
3. If the server goes down the system will become unavailable for that period.
16
This is the most suitable solution for our client when considering the main requirement of the client,
multiple user accessibility and low cost. This single server has high vulnerability so we hope to provide
a proper and regular backing up strategy.
7.3. Hierarchical client server system
Figure 7.3 - Hierarchical client server system: Multiple servers multiple clients connect in a hierarchical
way. [1]
Here also clients can be developed in the above two ways. As mentioned above the suitable system is
web based. Therefore Implementing hierarchical client server web based system has following benefits
to our client.
1. Multiple users can access the system at the same time.
2. More customizable.
3. High scalability.
4. Efficient and effective services can be provided.
5. High availability.
6. System can be developed to make automatic backup copies.
But at the same time it has following drawbacks.
1. High computation cost.
2. Maintain and deploy cost will be very high.
3. Maintaining data integrity and consistency is hard and will need extra effort.
Our client preferred to a low cost and easily maintainable system. Therefore this will not be a suitable
solution for our client. Because in this solution maintain and deploy cost will be very high.
8. Recommended Solution (Flat client server Web based System)
17
When considering the above mentioned alternatives, the most suitable system is a flat client server
Web based System. According to the client’s current requirements following benefits could be obtained
over the other alternatives.
1. Multiple concurrent accesses through different locations inside the institute.
2. Low implementation cost with the technologies proposed.
3. Low maintenance cost compared to a distributed system.
4. Ability to use the existing hardware and software devices.
5. Increase the collaboration.
6. Efficiency and effective services can be provided.
.
9. Candidate solution matrix
18
10. References
1. ftp://ftp.tik.ee.ethz.ch/pub/students/2002-2003-Wi/SA-2003-16.pdf
Description Weight Stand alone Flat client server Hierarchical
system system client server
system
High security, High Concurrent access More
reliability, Low cost, allowed, Increase the customizable, High
Easy to maintain, collaboration, high scalability, High
High failure efficiency and effective availability, Hard
Operational 30% percentage, services, Fully support and costly to
Feasibility Concurrent access user required deploy and
not allowed. functionalities, Low maintain.
cost, Low scalability.
Score – 60% Score – 90% Score – 80%
Special user training Typical user training is Typical user
is required. required. training is
Difficulties in Easy to design user required.
Technical designing user interfaces using free Development will
30% interfaces using java. and open source be very hard.
Feasibility Can be used .Net but software.
it cost much.
Score – 80% Score – 100% Score – 70%
Low cost. Because no Low cost, because of Deploy and
additional hardware is the use of free and maintain will be
Economical required. open source software costly.
20% and can be used some
Feasibility existing hardware.
Score – 95% Score – 90% Score – 70%
Changes are easy to Changes are easy to Changes are easy
Cultural 10% apply. apply. to apply.
Feasibility
Score – 100% Score – 100% Score – 100%
Easy to implement on Needs to maintain a Needs to maintain
schedule. tight schedule. a tight schedule.
Schedule Relatively easy to Relatively easy to
5% implement on implement on
Feasibility schedule. schedule.
Score – 90% Score – 85% Score – 85%
Used free software. Used free software. Used free
Therefore the legal Therefore the legal software.
Legal 5% feasibility is high. feasibility is high. Therefore the legal
Feasibility feasibility is high.
Score – 90% Score – 90% Score – 90%
Weight Score 100% 80% 93.75% 77.75%
2. http://www.ajaxwith.com/ActionScript-vs-JavaScript.html
3. http://www.serverwatch.com/article.php/3074841
4. http://www.bizfive.com/articles/web-design/comparing-php-and-asp.net/
19
5. Htto://www.laptop.lk
20