System Analysis Design Development Planning Phase

System Analysis
Design
Development
Planning Phase
Project Manager (PM) Lumbao, John Ian Paulo I.
System Analyst (SA) Funtilon, Alken D.
Program Analyst (PA) Malaza, Arnold P.
Program Analyst (PA) Abdulrahman, Ayman M.




Table of Contents
Planning (Phase 1)
I. Introduction
System Definition
II. Project Initiation
a. Problem Definition
b. Feasibility Study
III. Project Management Plan
a. Work Plan
--Gantt Chart
b. Staffing Plan
--Organizational Chart
--Project Staffing
c. Risk Management Plan
Analysis (phase 2)
IV. Requirement Definition
a. Functional Requirements
b. Non – Functional Requirement
V. Propose System
a. Process Models (Logical)
b. Data Models (logical)
VI. System Proposal


Design (Phase 3)
VII. System Specification
a. Architecture Design
b. Hardware and Software Specification
c. Interface Design
d. Process Model (Physical)
e. Data Models (Physical)
Development
VIII. Coding
IX. Testing
A. System Test Documentation
a. Test Approach
b. Test Plan
1. Features to be tested
2. Testing Tools and Environment
c. Test Cases
1. Unit Testing
2. User Acceptance Testing
Acceptance
X. Project Sign – off
XI. Executable
XII. Code Listing
XIII. User Manual









System Definition
A Service Request System is an IT Department Help Desk that can track, manage, and organize and overview the tasks/request of the department

Problem definition
The Information and Communication Department of Saint Jude Catholic School is maintaining the school's computers, laptops, and other gadgets and devices which is currently used by the teachers and staffs of SJCS. They have difficulties in tracking those repaired devices and also the pending/unfix devices. They also experiencing problems with managing and handling files and records of the repaired devices using a paper based and manual storage system of the service request.

Issues Weight
Use of the system "spreadsheet" for managing request 10 and tracking task.
Inefficient way of handling and storing files or data. 9
Unorganized service records. 8
Objectives
Create a system that improves the management of request and tracking of tasks.
Provide a means to organize the service records.
Provide a means to improve the handling and storing of file or data and lessen the use of paper & pen.

Requirements
The system must be efficient.
The system must be user friendly.








Feasibility Study
Service Request Project Executive Summary
Arnold Malaza, Ayman Abdulrahman, John Ian Paulo Lumbao and Alken Funtilon created the following feasibility analysis for the SJCS Service Request Project. The highlight of the Feasibility Analysis are as follows:
Technical Feasibility
The Service Request System is feasible technically although there are some risk.

The project size is also considered low risk.
The project team will likely consist of 4 or fewer people.

The familiarity with technology should be good
The IT Department is the one who will use the system. They have a strong knowledge regarding the language and the database to be use in the proposed Service Request System.
The IT Department has the requirements; such as, computers, databases, server, and programming language which are necessary to create the system.

Economic Feasibility
A cost-benefit analysis was performed; see attached spreadsheet for details (provided in Page 2). Conservative estimates show that the Service Request system has a good chance of significantly enhancing the company's service.
ROI over 3 years: 39.7%
NPV over 3 years: 135,806.1664
Break-even occurs after 1.8 years

Intangible Costs and Benefits.
Improved Clientele satisfaction.

Organizational Feasibility
From an organizational perspective, this project is efficient and has low risk. The IT Department of the company have a strong interest in the project.

The IT Department of the school itself recommended the system.The users and clients are expected to appreciate the entry of the SJSR into the school. The management may have concerns about an unmanaged request, unorganized service request and unmonitored task, however this system resolve those issues and improve their service requests system efficiency.
Gant Chart










































System Analysis
Design
Development
Analysis Phase
Project Manager (PM) Lumbao, John Ian Paulo I.
System Analyst (SA) Funtilon, Alken D.
Program Analyst (PA) Malaza, Arnold P.
Program Analyst (PA) Abdulrahman, Ayman M.






Functional And Non – Functional Requirements
FUNCTIONAL
MANAGER AND STAFF
The system must allow the user to view all the task and request.
The system must allow the user to search or find a specific task.
The category of request should have Create new Request, Add Request, Edit Request, Delete Request
The Notification Must Include view Status
The System must allow the user to view the request
MANAGER
The system must be able to generate a report of all the tasks.
SYSTEM RATING
SYSTEM REPORTING
SYSTEM
The system must be able to validate user (log in form).
- The Log-in System must include the following Incorrect Username, Incorrect Password, No E-mail, and No Password
NON-FUNCTIONAL
SECURITY
The system must have user access restriction (to the manager or staff).
OPERATIONAL
The system must be web based.
The system must categorize all the task if it is new pending on hold solved closed.
The system must have user friendly interface.


Use Case Diagram


Context Diagram




Data Flow Diagram




Entity Relationship Diagram


Process Illustration


System Analysis
Design
Development
Design Phase
Project Manager (PM) Lumbao, John Ian Paulo I.
System Analyst (SA) Funtilon, Alken D.
Program Analyst (PA) Malaza, Arnold P.
Program Analyst (PA) Abdulrahman, Ayman M.






ARCHITECTURE DESIGN
Data Server
Data Server
Client
Client






TerminalApplication Logic, Data Storages, Data Access Logic, Presentation Logic
Terminal
Application Logic, Data Storages, Data Access Logic, Presentation Logic


Standard Terminal
Standard Database Server

Operating System
- Windows 7,8,10
- Windows 7,8,10
Special Software
Google Chrome
XAMP

MY-SQL
XAMP
Hardware
Intel® Celeron® CPU
B800 @ 1.50GHz 1.50GHZ

Intel® Atom CPU
Z3745 @1.33GHz 1.33GHz
At least 2GB RAM
Intel® Celeron® CPU
B800 @ 1.50GHz 1.50GHZ

Intel® Atom CPU
Z3745 @1.33GHz 1.33GHz
2GB RAM
250GB Hard Disk / 500GB Hard Disk
Lan Ethernet
Network
Lan Ethernet
Broadband at least 250kbps
Dual 100 Mbps Ethernet
Lan Ethernet
Dual 100 Mbps Ethernet

My SQL Remarks of RequestorD1My SQL Records Rate Service RequestClientD1Service Request FormService Request Form (Rating) RatingHTML/PHP/JAVASCRIPT4RequestingHTML/PHP/JAVASCRIPTService Request InfoService Request InfoStaffService Request InfoApproved Service Request FormService Request FormService Request Form Approved Service Request Form3D1My SQL AccountClientMy SQL RecordsAccount InfoUser – ManagementHTML/PHP/JAVASCRIPT2D1Update Account InfoMy SQL AccountAdminManage AccountAccount InterfaceUser AccessMy SQL AccountMy SQL RecordsVerify Log – In DetailsAccount InfoAccessAdminStaffLog - InHTML/PHP/JAVASCCRIPT1AccessAccount Info
My SQL Remarks of Requestor
D1
My SQL Records
Rate Service Request
Client
D1
Service Request Form
Service Request Form (Rating)
Rating
HTML/PHP/JAVASCRIPT
4
Requesting
HTML/PHP/JAVASCRIPT
Service Request Info
Service Request Info
Staff
Service Request Info
Approved Service Request Form
Service Request Form
Service Request Form
Approved Service Request Form
3
D1
My SQL Account
Client
My SQL Records
Account Info
User – Management
HTML/PHP/JAVASCRIPT
2
D1
Update Account Info
My SQL Account
Admin
Manage Account
Account Interface
User Access
My SQL Account
My SQL Records
Verify Log – In Details
Account Info
Access
Admin
Staff
Log - In
HTML/PHP/JAVASCCRIPT


1
Access
Account Info





















Staff
Staff

ReportingHTML/PHP/JAVASCRIPTPrinted ReportGet / Query ReprotAdmin5Report Info My SQL Records Retrieve ReportMy SQL RecordsD1
Reporting
HTML/PHP/JAVASCRIPT
Printed Report
Get / Query Reprot
Admin
5
Report Info
My SQL Records
Retrieve Report
My SQL Records
D1