System Analysis and Design Assignment

ABSTRACT

System analyst gives the system development project meaning and directional. To
understand system development, we need to recognize that a candidate system has a
life cycle, just like a living system or a new product. In the present paper I have defined
the system and its phases to develop a system.

The first steps in the process are to identify a project that will deliver value to the
business and to create a system request that provides the basic information about the
proposed system. Next, the analysts perform a feasibility analysis to determine the
technical, economic, and organizational feasibility of the system. The systems analyst
plays a key role in information systems development projects. The systems analyst
works closely with all project team members so that the team develops the right system
in an effective way. Systems analysts must understand how to apply technology to
solve business problems. In addition, systems analysts may serve as change agents
who identify the organizational improvements needed, design systems to implement
those changes, and train and motivate others to use the systems

OBJECTIVES

 Explain the role played in information systems development by the systems

analyst.
 Describe the fundamental systems development life cycle and its four phases.
 Explain how organizations identify IS development projects.
 Explain the importance of linking the information system to business needs.
 Be able to create a system request.
 Describe technical, economic, and organizational feasibility assessment.
 Be able to perform a feasibility analysis

1|Page
 INTRODUCTION

The systems development life cycle

(SDLC) is the process of determining how an information system (IS) can support
business needs, designing the system, building it, and delivering it to users. If you have
taken a programming class or have programmed on your own, this probably sounds
pretty simple. In the real world, how-ever, it is not so easy.

To develop an understand the system development lifecycle and its role in managing
the development of digital library systems. Design/methodology/approach It provides a
conceptual analysis of the system development lifecycle within the context of digital
library system development. Findings The system development lifecycle concept has
been broadly applied to system development projects for many years. Project teams
developing digital library systems can be more effective if they understand the
expectations and outcomes of each phase of the system development lifecycle.
Originality/value – For librarians that do not have a formal system development
background, this article provides a concise and to‐the‐point overview of the various
stages of the system development lifecycle and the relationship of each phase to the
development of a digital library system.

Books and user maintenance modules are also included in this system which would
keep

track of the users using the library and also a detailed description about the books a
library contains. With this computerized system there will be no loss of book record or
member record which generally happens when a non-computerized system is used. In
addition, report module is also included in Library Management System. If user’s
position is admin, the user is able to generate different kinds of reports like lists of
users registered, list of books, issue and return reports. All these modules are able to
help librarian to manage the library with more convenience and in a more efficient way
as compared to library systems which are not computerized.

2|Page
Waterfall Model of development of LL (Limkokwing Library) System.

The Waterfall Model was first Process Model to be introduced. It is also referred to as a
linear sequential life cycle model. It is very simple to understand and use. In a waterfall
model, each phase must be completed before the next phase can begin and there is no
overlapping in the phases.
Waterfall model is the earliest SDLC approach that was used for software development.
The waterfall Model illustrates the software development process in a linear sequential
flow; hence it is also referred to as a linear-sequential life cycle model. This means that
any phase in the development process begins only if the previous phase is complete. In
waterfall model phases do not overlap.
Waterfall Model design
Waterfall approach was first SDLC Model to be used widely in Software Engineering to
ensure success of the project. In "The Waterfall" approach, the whole process of
software development is divided into separate phases. In Waterfall model, typically, the
outcome of one phase acts as the input for the next phase sequentially. Following is a
diagrammatic representation of different phases of waterfall model.

3|Page
The sequential phases in Waterfall model are:

Requirement Gathering and analysis:

All possible requirements of the system to be developed are captured in this phase and
documented in a requirement specification doc.
System Design:
The requirement specifications from first phase are studied in this phase and system
design is prepared. System Design helps in specifying hardware and system
requirements and also helps in defining overall system architecture.
Implementation:
With inputs from system design, 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 which is referred to as Unit Testing.
Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
Deployment of system: Once the functional and non-functional testing is done, the
product
is deployed in the customer environment or released into the market.
Maintenance: There are some issues which come up in the client environment. To fix
those issues patches are released. Also, to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.
All these phases are cascaded to each other in which progress is seen as flowing
steadily
downwards like waterfall through the phases. The next phase is started only after the
defined set of goals are achieved for previous phase and it is signed off, so the name
"Waterfall Model". In this model phases do not overlap.

4|Page
Waterfall Model Application
Every software developed is different and requires a suitable SDLC approach to be
followed based on the internal and external factors. Some situations where the use of
Waterfall model is most appropriate are:
 Requirements are very well documented, clear and fixed.
 Product definition is stable.
 Technology is understood and is not dynamic.
 There are no ambiguous requirements.
 Ample resources with required expertise are available to support the product.
 The project is short.

Waterfall Model Pros & Cons

Advantage
The advantage of waterfall development is that it allows for departmentalization and
control. A schedule can be set with deadlines for each stage of development and a
product can proceed through the development process model phases one by one.

Development moves from concept, through design, implementation, testing,

installation, troubleshooting, and ends up at operation and maintenance. Each phase of
development proceeds in strict order.

Disadvantage

The disadvantage of waterfall development is that it does not allow for much reflection
or revision. Once an application is in the testing stage, it is very difficult to go back and
change something that was not well-documented or thought upon in the concept stage.
The following table lists out the pros and cons of Waterfall model:

5|Page
Pros
Simple and easy to understand and use
Easy to manage due to the rigidity of the
model. each phase has specific
deliverables and a review process
Phases are processed and completed
one at a time.
Works well for smaller projects where Poor model for long and ongoing
requirements are very well understood.
Clearly defined stages.
Well understood milestones.
Easy to arrange tasks.
Process and results are well documented
6|Page
Cons
No working software is produced until
late during the life cycle
High amounts of risk and uncertainty.
Not a good model for complex and
object-oriented projects.
projects.
Not suitable for the projects where
requirements are at a moderate to high
risk of changing. So risk and uncertainty
is high with this process model.
It is difficult to measure progress within
stages.
Limkokwing Library system is a project which aims in developing a computerized

system to maintain all the daily work of library. This project has many features

which are generally not available in normal library management systems like

facility of user login and a facility of teacher’s login. It also has a facility of admin

login through which the admin can monitor the whole system. It also has facility

of an online notice board where teachers can student can put up information about

workshops or seminars being held in our colleges or nearby colleges and librarian

after proper verification from the concerned institution organizing the seminar can

add it to the notice board. It has also a facility where student after logging in their

accounts can see list of books issued and its issue date and return date and also the

students can request the librarian to add new books by filling the book request

form. The librarian after logging into his account ie admin account can generate

various reports such as student report, issue report, teacher report and book report

Overall, this project of ours is being developed to help the students as well as staff

of library to maintain the library in the best way possible and also reduce the

human efforts.

7|Page
Limkokwing Library system will be developed and designed to help librarian record
every book transaction so as to reduce and eradicate problem of loss of books and files
in the library.

Statement of the Problem

Presently, transaction of books in the institutional libraries have been done manually in
most cases, thereby taking more time for transaction like borrowing of books or return
of books and also searching of member and books. Series of problems occur as a result
of this thereby resulting to inefficient library management. In most cases as a result of
human error there maybe loss and damages of records due to not using a computerized
system in the library. Nevertheless, the difficulty in the searching of books which could
be termed to be inadequacy in book Management is a problem in the manual library
thereby causing inefficiency and time consuming in the library. Also, the problem of
space consuming erupts after the number of records become large the space for
physical storage of file and records also increases if no computerized system is
implemented as well as the issue of cost. Due to problem of lack of prompt information
retrieval and time wastage in using the library. In addition, due to the cumbersome, in
this project computer approach will be used to solve these problems. Each of the
manual procedure will be analyzed.

Aim and Objectives

The aim of this project is to develop a system that can handle and manage the activities

involved in a library in an efficient and reliable way.

The objectives are:

 Designing a computerized library management system which would help

evacuate the problem faced in manual library.
 Implementing the system.
 Evaluating and testing the performance of the system.

8|Page
The system requirement in library management focuses on the possibility of
search for books by title, author or subject by the member. They should be able to
locate a book physically by the unique identification code and the rack number for each
book. The system should provide details on the books held by the members. The
system should limit the number of books that can be taken and the number of days that
a book can be kept for. The system should generate fines when due from the member.

The next step focuses on the functions of the librarian, the member and the system.
Managing books by the librarian, searching for books by the members and notifications
sent by the system are detailed in a case diagram.

The third step in the design of the library management system software is based on the
different aspects of a library. The name of the library, the book details, member details,
membership cards, book reservations, book lending, cataloging, fines, book racks and
notifications are consolidated as a class diagram.

The next step further breaks down the functions into specific activities that are
performed in a library. An activity diagram based on the primary activities – checking
out a book, returning a book and renewing a book – is drawn.

The final stage is coding for each activity in the case, class and activity diagrams. This
is the most important function in the design of the library management system
software.

9|Page