Академический Документы
Профессиональный Документы
Культура Документы
A Project Proposal
Presented to
The Faculty of STI College Koronadal
In Partial Fulfilment
of the Requirements for the Degree
Bachelor of Science in Information Systems
Booc,charl,
Celebrar, Jhey Vy,D.
Liwa Angel
Tayona Raychel Joy V.
August 2019
Page
Title Page i
Approval Sheet ii
Table of Contents iii
I. Introduction
a. Background of the problem
b. Overview of the current state of technology
c. Project Rationale
II. Project Description
a. Problem Statement
b. Proposed Research Project
i. General Objectives
ii. Specific Objectives
iii. Scope and Limitations
iv. Methodology of the Study
III. Project Management
a. Calendar of Activities
b. Resources
IV. Appendices
a. References
b. Resource Person/s
c. Personal Technical Vitae
for the past 13 year, the saravia national high school continue to serve and pursue the
vision to nurtures students by competent with mid and passion for excellence.
The saravia national high school(SNHS) is a competitive school. The school was build in
the year 2006 which is the first principal is Gil Subang. The school library was founded
june 2018.
Saravia National Highschool (SNHS) library, as one of any other libraries is an organized
institution that accommodates students who access and borrow reading materials for one’s use.
For 2 year of its operation, although it is useful and efficient, it still encounters some problems
particularly in its insufficient in the outgoing and incoming of books. There are some instances
that the borrowed books are not monitored whether they have been returned by the student or
not. With this premise, this study focus on the automation of borrowing and returning of books
specifically addressing how technology provides ease of transaction inside the library.
Library System enhancing the manual library processes and minimizes paper-based transactions.
The automation of the manual library processes covers the acquisition of books, registration of
clients, and circulation processes in the library. In the acquisition of books, new arrivals will be
processed which also includes the cataloguing process where card catalogs are produced. In
cataloguing, the entire book’s information is listed for monitoring purposes. In this processes,
clients are registered and given a library card. The books are circulated in the circulation section
where borrowing and returning of books are done and generates necessary reports periodically.
resources, skills and abilities. Over the past few years, library automation has undergone a
dramatic shift in direction. Library automation began with in-house processing of traditional task
and grew to include the use of computing and telecommunication tools. Now there is a "library
without walls" which uses technology to expand services, resources and relationship between
libraries and resources around the world. This "virtual library" is a reality. A world of digital
information is just a keystroke away claims IBM digital library. The future of library automation
system will include information kiosks, where people with no computer experience can access
information easily. Information scientists will create human computer interfaces and library
Dilroshan (1998) says that automating a library is only the first step. Keeping up with
the libraries fail to meet these challenges successfully the tremendous investment that
universities have made in their library collections and facilities will be seriously undermined.
Nok (2006) observes that the success of automation in the university library depends
largely on the ability of staff to facilitate and implement the process. Proper, frequent, and
regular in-house IT training is a necessity if the maximum benefit is to be gained from the
automation of library services. It was further added that if the library ensures sound and quality
automation of services and information resources, they need to create new approaches to user
education, pays attention to the provision of continuing education for library staff, helping them
to master the new techniques required for the management of electronic and the networked
a. Problem Statement
The manual system used by Saravia national highschool library should aim to Record all the
borrowed and returned books. This manual system is takes a minute of time
Example: "The boarding protocols used by ABC Airlines should aim to get each flight's
passengers aboard the plane quickly and efficiently so that the plane can take off as soon
as possible. The process of boarding should be optimized for time-efficiency but also
should be straightforward enough that it can be easily understood by all passengers."
However the proponents identified that the problem of the school is on the manual
system that records all the information about the student who borrowed and returned
books. If the book is lost it is hard for them to trace the student who borrowed books in
case the manual copy of the school gets lost. The manual causes them delay to record the
books that the student borrowed.
Soon after you state your problem, you'll want to explain why it's a big deal — after all,
no one has the time or resources to try to solve every single minor problem. In the
business world, money is almost always the bottom line, so you'll want to try to highlight
the financial impact of your problem on the company or organization you're writing for.
For instance, is the problem you're discussing keeping your business from making more
money? Is it actively costing your business money? Is it damaging your brand image and
thus indirectly costing your business money? Be as exact and specific about the financial
burden of your problem — try to specify an exact dollar amount (or a well-supported
estimate) for your problem's cost.
For our airline example, we might proceed to explain the problem's financial cost like
this:
"The inefficiency of the current boarding system represents a significant financial burden
for the company. On average, the current boarding system wastes roughly four minutes
per boarding session, resulting in a total of 20 wasted man-hours per day across all ABC
flights. This represents a waste of roughly $400 per day, or $146,000 per year."
No matter how much money you claim your problem is costing your company, if you can't
back up your claims with reasonable evidence, you may not be taken seriously. As soon as
you start making specific claims about how serious your problem is, you'll need to start
supporting your statements with evidence. In some cases, this may be from your own
research, from data from a related study or project, or even from reputable third-party
sources.
Let's reexamine the sentences we used in the previous step. They describe the cost of the
Example: "...Based on internal performance tracking data, [1] on average, the current
boarding system wastes roughly four minutes per boarding session, resulting in a total of
20 wasted man-hours per day across all ABC flights. Terminal personnel are paid an
average of $20 per hour, so this represents a waste of roughly $400 per day, or $146,000
per year." Note the footnote — in an actual problem statement, this would correspond to
a reference or appendix containing the data mentioned.
When you've explained what the problem is and why it's so important, proceed to
explain how you propose to deal with it. As with the initial statement of your problem,
your explanation of your solution should be written to be as clear and concise as possible.
Stick to big, important, concrete concepts and leave any minor details for later — you'll
have plenty of opportunities to get into every minor aspect of your proposed solution in
the body of your proposal.
In our airline example, our solution to the problem of inefficient boarding practices is this
new system we've discovered, so we should briefly explain the broad strokes of this new
system without getting into the minor details. We might say something like,
Example: "Using a modified boarding system proposed by Dr. Edward Right of the
Kowlard Business Efficiency Institute which has passengers aboard the plane from the
sides in rather than from the back to the front, ABC Airlines can eliminate these four
minutes of waste."
We might then go on to explain the basic gist of the new system, but we wouldn't use
more than a sentence or two to do this, as the "meat" of our analysis will be in the body
of the proposal.
Again, now that you've told your readers what should be done about the problem, it's a
very good idea to explain why this solution is a good idea. Since businesses are always
trying to increase their efficiency and earn more money, you'll want to focus primarily on
the financial impact of your solution — which expenses it will reduce, which new forms of
revenue it will generate, and so on. You can also explain non-tangible benefits, like
improved customer satisfaction, but your total explanation shouldn't be too much longer
than a few sentences to a paragraph.
In our example, we might briefly describe how our company could conceivably benefit
from the money saved with our solution. A few sentences along these lines might work:
Example: "ABC Airlines stands to benefit substantially from the adoption of this new
boarding program. For instance, the $146,000 in estimated yearly savings can be re-
directed to new sources of revenue, such as expanding its selection of flights to high-
demand markets. In addition, by being the first American airline to adopt this solution,
ABC stands to gain considerable recognition as an industry trend-setter in the areas of
value and convenience."
After you've presented the ideal vision for your company, identified the problem keeping
your from achieving this ideal, and suggested a solution, you're almost done. All that's
left to do is to conclude with a summary of your main arguments that allows you
transition easily into the main body of your proposal. There's no need to make this
conclusion any longer than it needs to be — try to state, in just a few sentences, the basic
gist of what you've described in your problem statement and the approach you intend to
take in the body of the article. In our airline example, we might conclude like this:
This sums up the main point of the problem statement — that the current boarding
procedure isn't very good and that this new one is better — and tells the audience what
to expect if they continue reading.
i. General Objective
The Library System is designed to help the school’s librarian to effectively do their daily
transactions and use a system that is user friendly and less human effort
Scope
The proponents identified the scope of the system that will accept library
transactions of book issue, return, monitor books and add if they have newly arrived
books. The system made the transaction automated and made their work faster. The
system can make use of it for providing information about author and content of the
available books. The system would provide basic set of features to add student
information and book information, update books and student, and to record all the
borrowing and returning of books. The system can record payment of lot and damaged
book.
Limitation
The library system is limited only to the borrowing and returning o books. The
information of the student is also limited. It allows transaction within the library and
other transactions are not accepted. The library system cannot hold the penalties that
will be paid by the students; however it can record all the payment of student for the
lost and damaged books.
This should contain the specific approaches that may be employed by proponents in
arriving at the realization of a solution to the problem.
In developing the system, the proponents used a Rapid Application Development model
(RAD) as a method of developing the new Online Bond and Credit Purchase Processing
System. RAD is a form agile development methodology. It is a systems development life
cycle model designed to give much faster development by prototyping, iterative and
incremental development, reuse of components, and continuous integration
(Balakrishnan, 2018). James Martin developed the RAD in the late 1980s when working at
IBM based on Barry Bohem spiral model. He then published a book called Rapid
Application Development in 1991 to formalize it (Lemaignent, 2017). The methodology is
based on four main phases: (1) the proponent has to define the scope and the
a. Calendar of Activities
Description of Activities
This should contain the detailed sequence of activities that the proponents will undergo
in completing the project.
This should contain a chart giving when each of the activities listed above are expected to
start and end. The time unit should be in terms on the week number (not actual dates)
from the start of the semester
b. Resources
Hardware
This should list the specific hardware resources that the proponents expect to need in
completing the project.
HARDWARE REQUIREMENT
Monitor 24 inches LCD
Processor/CPU Intel Core i5 (2.66 GHz, Quad Core) or
AMD FX (3.0 GHz, Octa Core) or higher
recommended
Memory (RAM) 8 GB RAM or more recommended.
Graphics AMD Radeon 6750 or Nvidia 550 Ti or
higher
Hard disk space 1 TB, or 256 GB solid state drive (SSD)
Networking Hardware 10/100/1000 Ethernet adapter
This should list the specific software resources that the proponents expect to need in
completing the project.
SOFTWARE REQUIREMENT
SQL Server 2000 Client Tools SQL Server 2000 client tools, required by
SQLXML.
IV. APPENDICES
a. References
b. Resource Person/s