AMANAH TUGAS SYARAHAN SYSTEM (ATS)

SOFTWARE REQUIREMENT SPECIFICATION (SRS)

Version 1.0

SEMESTER MARCH – JULY 2020

GROUP: CS1104 F

NURUL SYARAFANA BINTI AZAHARI 2018656798

AHMAD MUHAIMIN BIN ZOHARI 2018637752
NUR HASYIMAH BINTI AZHAN 2018652748

PN. ZANARIAH BINTI IDRUS

SIGN
ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

Revision History
Date Version Description Author
09.05.2020 1.0 SRS Nurul, Hasyimah,Muhaimin
 ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

Table of Contents

1. Overall Description
1.1
Product Perspective 1-3
1.2
Product Functions 1
1.3
User Characteristics 2
1.4
Operating Environment 2
1.5
General Constraints 3
1.6
References 3

2. External Interface Requirements 4-5

2.1
User Interfaces 4
2.2
Hardware Interfaces 4
2.3
Software Interfaces 4
2.4
Communications Interfaces 5

3. Functional Requirements 5

4. Other Nonfunctional Requirements 5-6

4.1
Performance Requirements 5-6
4.2
Safety and Security Requirements 6

Appendix 7-8
 ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

1. Overall Description

1.1 Product Perspective

Briefly describe the proposed information system (IS) to be develop that include user,
process/module, database, hardware and software. Make sure to include a simple diagram that
shows the major components of the overall system, subsystem interconnections, and external
interface.

Arahan Tugas Syarahan (ATS) system stores the following information:

● Lecturer description:

It includes lecturer id, lecturer name, lecturer position, email, workload allotted,

number phone and department id. This information may be used for keeping the

records of the lecturer.

● Course Coordinator description:

It includes course coordinator id, username, password, name, phone number, gender

and level. This information will be used to know who is using the system.

● ATS description:

It includes ATS id, tutorial hours, lab hours, lecture hours, blended hours, lecturer id,

course id and group id. This information can be used to calculate the amount of ATS

for each lecturer.

Complete Context Diagram can be referred to Appendix at page 7 (Figure 1.1 Context Diagram).

1
 ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

1.2 Product Functions

Summarize the major functions the product must perform or must let the user perform. Provide a
bulleted list of all the major functions of the system. Provide a Data Flow Diagram (DFD) of the
system to show how these functions relate to each other.

Lecturers for the first time accessing the system must log in to enter their information to
register.The course coordinator will verify lecturers’ account to use this system. If the lecturer is
already enrolled, they fill in all ATS information. The course coordinator will monitor the information
and see if the total ATS is in line with the ATS information entered by the lecturer. Course
coordinator will be able to see the total ATS. After that, the course coordinator will update the
status of whether the lecturer passed or failed to meet the prescribed time for teaching.Lecturers
can view the status of the system.

Complete Diagram 0 can be referred to Appendix at page 7 (Figure 1.2 Diagram 0 ).

1.3 User Characteristics

Describe the different types of users/reader/stakeholders that the document is intended for. Users
may be differentiated security or privilege levels and job level.

Users of the system should be able to update information into the system. The system will support
two types of user, lecturer and course coordinator.

The course coordinator should be able to do the following functions:

● Update application status

● Open or close application and view application

● View total ATS

● Approve or disapprove the applicant

The lecturer should be able to do the following functions:

● View application status

● Open or close application and view application

● Update ATS and lecturer details

2
 ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

1.4 Operating Environment

Describe the environment/platform in which the software will operate, including the hardware
platform, operating system and versions, and any other software components or applications with
which it must peacefully coexist.

Operating environment for the Murni college system is as listed below.  

● distributed database
● client/server system
● Operating system: Windows.
● database: sql + database
● platform: xampp/Java/PHP

1.5 General Constraints

Describe any items or issues that will limit the options available to the users/stakeholders. These
might include hardware limitations, interfaces to other applications, communications protocols,
security considerations or programming standards.

General constraints in this system are :

1. Course coordinator can only update information about application status

2. Lecturer can only view information about application status

1.6 References
List any other documents (including previous student projects) or Web addresses to which this
SRS refers. These may include user interface style guides. Use the standard IEEE citation guide
for this section.

1. https://krazytech.com/projects/sample-software-requirements-specificationsrs-report-airline-
database
2. Amanah Tugas Syarahan (ATS) SDP.

3
 ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

2. External Interface Requirements

2.1 User Interfaces

Describe the logical characteristics of each interface between the software product and the users.
This may include sample screen images, any GUI standards or product family style guides that are
to be followed, screen layout constraints, standard buttons and functions (e.g., Cancel) that will
appear on every screen, error message display standards, and so on. Those who will be able to
provide optional Graphical User Interface (GUI) screenshots will be rewarded by extra marks.

ATS system user interfaces is designed to meet user requirements which will make them
easy to access and very convenient for user to use the button that can make user to go through
the system smoothly. Our main page will display the login and register button for lecturer to enter
the system. After they login. the interfaces will display lecturer details and class that they are
assigned to. They are required to enter KS and PS in the existing box for calculation of ATS. We
also provide logout button for lecturer to logout from the interfaces. All requirement that we
provided for our customer is really user-interactive so our customer can understand easily.

Main page interface can be referred at appendix page 8. (Figure 2.1 Main Page) .
Main page interface can be referred at appendix page 8. (Figure 2.2 Login Page) .

2.2 Hardware Interfaces

Describe the logical and physical characteristics of each interface between the software product
and the hardware components of the system.

● Windows
● A browser which support HTML, Javascript

2.3 Software Interfaces

Describe the connections between this product and other specific software components (name and
version), including databases or operating system.

Software Used Description

Operating system We have chosen Windows operating system

for its best support and user-friendliness.

Database To save the flight records, passengers records

we have chosen SQL+ database.

xampp To implement the project we have chosen

xampp language for its more interactive
support.

4
 ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

2.4 Communications Interfaces

Describe the requirements associated with any communications functions required by this product,
including e-mail, web browser, network server communications protocols, electronic forms, and so
on.

Course coordinator and lecturer need to open ATS system website to log in. They must
enter their lecture ID and password in order to enter the system. Lecturer will update their ATS
information to the system for calculation. The system will update the calculation to lecturer and
course coordinator. The lecturer who does not meet the total requirements will be monitored by the
course coordinator

This project supports all types of web browsers. We are using simple electronic form for the
lecturer to calculate their total ATS for next semester.

3. Functional Requirements

Functional requirements capture the intended behavior of the system. List the detail of different
user/stakeholder functions with specific explanations regarding every function.

Users/Stakeholders Function Description

Course coordinator able to view
Course coordinator View and update data user
and update data
After completing the registration
Lecturer Login process process, user able to log into the
information system
Lecturer can update ATS
Lecturer Update KS and PS infromation to the system for
calculation.

4. Other Nonfunctional Requirements

4.1 Performance Requirements

If there are performance requirements for the product/information system (IS) under various
circumstances, state them here and explain their rationale, to help the users/stakeholders
understand the intent and make suitable design choices.

For example: 1. Any transaction will not take more than 10 seconds.

1. Response time
● It takes less than 5 seconds for system to calculate total ATS and it will show the
total ATS instantaneously to the lecturer.

2. Scalability

5
 ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

● Our system will capable to supporting unlimited of customers detail that will be save
in our database.

4.2 Safety and Security Requirements

Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well as
actions that must be prevented.

Safety Requirement

If there is extensive damage to a wide portion of the database due to catastrophic failure,
such as a disk crash, the recovery method restores a past copy of the database that was backed
up to archival storage (typically tape) and reconstructs a more current state by reapplying or
redoing the operations of committed transactions from the backed up log, up to the time of failure.

Security Requirement

1. Identification Requirement

The system shall identify all of its user applications before allowing them to use its
capabilities

2. Data Transfer

The system shall use secure sockets in all transactions that include any confidential
customer information.The system shall automatically log out all customers after a period of
inactivity. The system shall not leave any cookies on the customer’s computer containing the
user’s password.

3. Data Storage

The customer’s web browser shall never display a customer’s password. It shall always be
repeated with special characters representing typed characters.The customer’s password may be
reset but never shown.The system’s back-end databases shall be encrypted.

6
ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

Appendix

(Figure 1.1 Context Diagram)

(Figure 1.2 Diagram 0)

7
ATS SYSTEM Version: 1.0
Software Requirement Specification (SRS) Date: 09.05.2020
Nurul,Hasyimah,Muhaimin

(Figure 2.1 Main Page)

(Figure 2.2 Login Page)