POLYTECHNIC SULTAN MIZAN ZAINAL ABIDIN
DEPARTMENT OF INFORMATION AND COMMUNICATION TECHNOLOGY
DFC40243
SYSTEM ANALYSIS AND DESIGN
TOPIC CHAPTER 2
TITLE OF PROJECT POLI SEJAHTERA
GROUP NAME PRIME COMPUTING
ASSESMENT CASE STUDY
NAME & REG NO 1)NIK NASYAD BIN NIK SHAUKI 13DDT20F1022
2)MUHAMMAD IZZUL MUAZZAM BIN PAUZI
13DDT20F1148
3)MUHAMMAD SHAHRUL IZWAN BIN AHAMAD
SAHARUDIN 13DDT20F1133
PROGRAMME DDT4S4
LECTURER PUAN NUR AISYAH BINTI MOHAMAD RAFIUDDIN
SUBMIT BY 7/4/2022
MARKS
TABLE OF CONTENT
CONTENT PAGES
1.0 Introduction 1
2.0 Problem statement 1
3.0 Objective 1
4.0 Scope and Constraints 2
5.0 Project Significance (Case of Action) 2&3
6.0 Gantt chart 4
7.0 Cost 4&5
8.0 Conclusion 5
Rubric 6
1.0 INTRODUCTION
The preliminary investigation is carried out to determine the scope and objectives of the new
system and to investigate whether there is a feasible solution. New applications normally originate
from end-user requests and are weighed against the other requests for IS resources before approval to
develop the system is granted.
Based on these hard times of going through a global pandemic, it has become very hard to isolate
and keep track on whether or not people around us are infected or not. This is much more emphasised
in the situation where students are now required to go back to their universities and live in the dorms
which will be much more harder to isolate and find out if the people round us is positive or not.
Because of this, this system has been developed for our university which will be able to keep track of
who is affected by the virus and would be able to take swift action towards the infected.
This system would require the residents to fill out their information and answer questions inside
the form to decide whether or not they are positive or not and that information then would be recorded
into the database which is accessible to the dormitory management and health care management of
PSMZA.
2.0 PROBLEM STATEMENT
The dormitory management and health care management of PMSZA isn’t able to observe and
control the movement and isn’t able to record each and every one of the dormitory residents that
register into the dormitory at once
3.0 OBJECTIVES
The objective of the system is to help the dormitory management and health care management of
PMSZA to reduce the number of staff or volunteers that is involved in the traditional process of
registering and moving process of the dormitory residents that are confirmed to have positive or close
contact statuses.
Next, the aim of the system is to help positive and close contact residents to register their
information efficiently and fast to the dormitory management and health care management of PSMZA
through a questionnaire which will ask for the information of the resident and inside the questionnaire
would also include accurate question to decide whether or not the student is positive or close contact
or not infected at all.
Lastly, the system aims to replace the traditional way of recording data which is by writing all of
the information in to a book/report/list with a more modern way of doing it which is inputting all of
the information into a database would increase efficiency and would be able to make it easier to find
specific resident’s information.
4.0 SCOPE AND CONSTRAINTS
4.1 SCOPE 1
4.1.1 USER SCOPE
For the user scope we will focus on two groups which are the normal residents as normal users and
the dormitory management and health care management of PSMZA as admins. Normal users are only
allowed to see their own information and statuses while admins can refer to a database with all of the
user’s information that has been inputted
4.1.2 SYSTEM SCOPE
For the system scope, we will use oracle database software to store and record user information
that is received from the form and use mobile development software to build our system. We are
using oracle as it is the best for managing data, eliminating redundancy, and easy to use.
4.2 CONSTRAINTS
The constraints of the system is that the system only focuses on dormitory residents and not the
whole university which means if any cases came from outside of the dormitory would make the whole
database useless or incorrect. The next constraint is that the system only focuses on positive and close
contact status residents which would make the other residents who are not infected not relevant to the
database. And lastly, the system’s database is only available for the administration to view, edit, copy
or export which would make the residents of the dormitory not have any access to any information on
which resident and dorm room that is affected and make it hard for them to be prepared on which
room and whom to keep their distance with
5.0 PROJECT SIGNIFICANCE
5.1 FACT FINDING
5.1.1 Interview
An interview will be held with the dormitory management and health care management of PSMZA
and the main focus of the interview would be the way that the registration of the positive students and
close contact student and how to improve on it. And another topic would be in the management of the
covid cases in the dormitory.
5.1.2 Questionnaire
A form will be made in which would ask the past resident that went through the process of moving
and quarantining to another dorm on whether or not the process of collecting information, the moving
of dorms and the satisfaction of the whole process is efficient or not, or is it good or bad and we will
revolve around the feedback.
5.1.3 Observation
2
An observation will be done towards the way that the traditional process and the standard of
procedure would undergo for positive and close contact student in the official Whatsapp group that is
made by the dormitory management and health care management of PSMZA and would observe on
the efficiency of the whole process.
5.2 FEASIBILITY
5.2.1 Feasibility – technical
The system will provide a physical terminal in which we will be able to maintain the system and
server with our basic database knowledge skills. With the terminal we will be able to pin point the
exact problem in which it would be able to fix.
5.2.2 Feasibility – operational
The system would operate efficiently and accurately in collecting resident’s information that has
registered for our system.
5.2.3 Feasibility schedule
The system is will be done approximately in 16 weeks in which everything would be done and we
will request for additional time if any more problem would arise in the future.
6.0 GANTT CHART 3
7.0 COST
TANGIBLE COST
ITEM SPECIFICATIONS COST DESCRIPTION
RENTAL SERVER - INTEL XEON ES- RM700/MONTH
1650 V3 3.5 GHZ (RM1400 OVER 2
SIX CORE MONTHS OF
PROCESSOR BUILDING AND
- RAM 64GB TESTING PHASE)
- SSD 500GB
DATABASE - GUARDS RM300/MONTH
SOFTWARE: AGAINST DATA (RM600 OVER 2
ORACLE BREACHES MONTHS OF
- EASY TO USE BUILDING AND
AND EASY TO TESTING PHASE)
DEPLOY
- ALWAYS
AVAIALABLE
- USES A SINGLE
DATABASE FOR
ALL DATA TYPES
NETWORK: UNIFI - 300 MBPS RM200/MONTH
NETWORK (RM600 OVER 3
4
BANDWIDTH OVER THE
- FIBER OPTIC WHOLE PROCESS
CABLES OF PLANNING
UNTIL
DEPLOYMENT)
INTANGIBLE COST
ITEM SPECIFICATIONS COST DESCRIPTION
MOBILE APP -CAPABLE OF -RM600/MONTH
DEVELOPMENT MAKING A
CLASSES WORKING
ANDROID AND IOS
APP
-ABLE TO MAKE
AN USER
INTERFACE
ORACLE SERVER -CAPABLE OF -RM600/MONTH
BASICS CLASSES BASIC
MAINTANANCE
ON A DATABASE
-CAPABLE OF
USING THE
BASICS OF
ORACLE
8.0 CONCLUSION
In conclusion, the purpose of this system is to help the dormitory management and health care
management of PSMZA to replace the old traditional way of recording positive and close contact
residents by writing in a book or a report and have the chance of the data to be lost physically ie: the
book or report is missing due to misplacing or the book itself is damaged by environmental impact
and changing it into the new and modern way of recording data which is through a database which is
highly secure, easy to use, easy to refer to and will always have a back up if the data is corrupted or
missing. The system also aims to increase efficiency and to speed up the process of moving residents
from their room to the quarantine room.
5
CRITERIA 5 4 3 2 1 TOTAL SCORE
Introduction Always clearly Clearly explains the Sometimes clearly Occasionally explains Unclear and
& Conclusion explains the project project to be explains the project the project to be incomplete
5 /5*5
to be undertaken undertaken most of to be undertaken undertaken understanding of the
the time project to be taken
Problem Always clearly Clearly explain the Sometimes clearly Occasionally explains Vague explanations
Statement explains the problems most of the explain the problems. the problems faced. of the problems 5 /5*5
(must have 3) problems. time.
Objectives The all objectives are The two of three The objectives need The objectives are The objectives are
(must have 3) very clear. objectives are clear. to be improved. clear after review. clear with guidance. 5 /5*5
Scope & Always clearly clarify Clearly clarify system Most of the required Few of the required No clear clarification
Constraints system scope and scope and user scope system scope and system scope and between system
user scope and the and the constraints user scope and the user scope and the scope and user scope 5 /5*5
constraints. most of the time. constraints are constraints are and the constraints.
included. included
Project Very clear Clear explanation of Somewhat clear Less clear about State very little
Significance explanation of the the project explanations of project significant about the project
5 /5*5
(cannot be project significance significance project significant significance
measured)
The chart is accurate The chart is accurate The chart is accurate The chart is less The chart is not
based on project based on project based on project accurate based on accurate based on
schedule and the schedule but less schedule but not project schedule and project schedule and
Gantt Chart &
cost meets all normal specific and the cost specific and the cost the cost meet very the cost none meet 5 /5*5
Cost
requirements and meets most normal meet few normal little normal the normal
reasonable requirements and requirements. requirements. requirements.
reasonable
TOTAL MARK 30
