Scribd
Upload
2 views1 page

Detailed Chapter 2 System Analysis Sample

This chapter discusses the analysis of the current manual system for managing customer records, highlighting issues such as data redundancy and slow report generation. It proposes a Microsoft Access database to improve efficiency through normalized tables and automated processes. The chapter also outlines functional and non-functional requirements, along with a feasibility study confirming the proposed system's viability.

Uploaded by

notchristian2008
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views1 page

Detailed Chapter 2 System Analysis Sample

This chapter discusses the analysis of the current manual system for managing customer records, highlighting issues such as data redundancy and slow report generation. It proposes a Microsoft Access database to improve efficiency through normalized tables and automated processes. The chapter also outlines functional and non-functional requirements, along with a feasibility study confirming the proposed system's viability.

Uploaded by

notchristian2008
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

CHAPTER TWO: SYSTEM ANALYSIS (Sample)

2.1 Introduction
System analysis examines the existing system, identifies weaknesses and defines the
requirements for the proposed database system.

2.2 Existing System


Customer records, payments and installation details are maintained manually. Searching
files is slow, calculations are performed by hand and report preparation consumes
significant time.

2.3 Problems Identified


Data redundancy, poor security, slow report generation, calculation mistakes, missing
records and difficulty tracking defaulters.

2.4 Proposed System


The proposed Microsoft Access database stores related information in normalized tables
connected through relationships. Forms simplify data entry while queries and reports
automate information retrieval.

2.5 Functional Requirements


The system shall register institutions, capture payments, maintain installation records,
manage bandwidth subscriptions, compute installation costs, apply upgrade discounts,
calculate overdue fines and generate reports.

2.6 Non-functional Requirements


Ease of use, security through user accounts, reliability, maintainability, performance and
data integrity.

2.7 Feasibility Study


Technical feasibility: Microsoft Access and standard PCs are sufficient. Economic feasibility:
low software cost. Operational feasibility: staff can easily learn the system.

2.8 Data Requirements


Institution details, contact persons, bandwidth plans, computers required, LAN nodes,
payment history and billing information.

2.9 Chapter Summary


This chapter analysed the existing system and justified the proposed computerized solution.

You might also like