Software Requirements Specification - LKIM

TDB4313: Software Requirement Engineering
Software Requirements Specification
Lembaga Kemajuan Ikan Malaysia (LKIM)
Prepared by:
Group Name: Fin.
Lab Session: Wednesday, 8.00 – 10.00 am
Alia Nabila Binti Ismail 20790
Ku Amirul Asyraf Bin Ku Amir 21059
Muhammad Faiz Farhan Bin Hashim 18213
Shamsul Nur Erzlin Binti Samsudin 20904

2
Document Control
Document Name LKIM Software Requirement Specification
Reference Number LKIM_SRS
Version 1.0
Project Code LKIM_1
Status In-Use
Date Released 6/4/2018
Name Position Signature
Prepared By:
Shamsul Nur Erzlin Binti
Samsudin
Business Analyst
Fin.
Reviewed By:
Ku Amirul Asyraf Bin Ku
Amir
Lead Developer
Fin.
Approved By:
Muhammad Faiz Farhan Bin
Hashim
Project Manager
Fin.
Version History
Version Release Date Section Amendments
1.0 6/4/2018 All Original Document

3
Table of Content
Document Control 2
Version History 2
Table of Content 3 - 4
1.0 Introduction
1.1 Purpose 5
1.2 Scope 5 - 6
1.3 Definition & Acronyms 6
1.4 References 6
1.5 Overview 7
2.0 Overall Description
2.1 Product Perspective 7
2.1.1 Operating Environment 7
2.1.2 User Interfaces 7
2.1.3 Communication Interfaces 7-8
2.2 Product Feature 8
2.2.1 Login 8
2.2.2 Logout 8
2.2.3 User Registration 8
2.2.4 Invoice Submission 8
2.2.5 Advertise Jobs 9
2.2.6 Live Chat 9
2.2.7 Support Form 9
2.3 Users Characteristics 9 -10
2.4 Constraints 10
3.0 Specific Requirements
3.1 External Interfaces 11
3.1.1 User Registration 11
3.1.2 Advertise Job using E-Pengambilan 11
3.1.3 Invoice Submission 12
3.1.4 Online Application 12
3.1.4.1 Kad Pintar 12
3.1.4.2 KUBENA 13
3.1.4.3 KUNITA 13
3.1.5 Customer Support 14
3.1.5.1 Registered User 14
3.1.5.2 Non-registered User 14
3.2 Functional Requirement 15
3.2.1 Registration, Login and Online Application 15-19
3.2.2 Customer Support
3.2.2.1 Registered User 20-23
3.2.2.2 Non-registered User 24-27
3.2.3 Invoice Submission 28-31
3.2.4 Advertise Job 32-35
3.2.5 Interface Functionality 36
3.3 Performance Requirement 37

4
3.4 Design Constraints 37
3.5 Software System Attributes
3.5.1 Availability 38
3.5.2 Security 38
3.5.3 Portability 38

5
1.0 Introduction
1.1 Purpose
The purpose of this software requirement specification document is to specify the details
at the specific requirements elicited by Fisheries Development Authority of Malaysia
(LKIM). It addresses the functionality, performance, interface, quality attributes and
compliance requirement of new system that will be develop. Furthermore, this document
will explain about the constraint, interface of the system and interaction of the system. This
SRS document will be required by the customers to get their approval and development
team will use this document as a reference to develop the system. This document is
intended for system developer, project manager, configuration manager and
client.
1.2 Scope
The current website of LKIM is build for the user to have an access with the services that
they offered. The website must provide all the relevant information needed by the user.
The LKIM website must allow user to make online registration and user will be able to
login to the website. The system will provide the online form for the user to register their
membership of KUBENA and KUNITA. The system also must allow the user to login into
the system after they register by using user ID and password. The system also will provide
different access for the LKIM staff to process the application of membership. The system
must provide feedback to the user in the form of email. The system also must provide an
online submission of the invoice for the user to claim the incentives from LKIM.
The LKIM website must provide relevant information related to the fisheries industry so
that the user can have the access to the latest information. The website needs to be updated
regularly by the administrator. For example, the online job advertisement in the LKIM
website must be updated so that the user can view the latest vacancies related to the
fisheries industry. The company can also advertise the vacancies through the LKIM
website and user can browse the job that they interests in. all the details about the job
vacancies must be shown and up-to-date.

6
The website must provide customer support services for the user who have enquiry. The
website must be able records the entire user enquiry and provide services such as online
chat with the LKIM staff.
1.3 Definition & Acronyms
Definitions
Term Definition
User A user is someone who interact with the system
LKIM Staff Someone who manage the online application and update the website
E-Perkhidmatan An online services that provide services in the website
Invoice Verification of the agreement between the buyer and seller of the goods or
services
Acronyms
LKIM Lembaga Kemajuan Ikan Malaysia
KUNITA Kumpulan Wanita Nelayan
KUBENA Kumpulan Belia Nelayan
GUI/UI Graphical User Interface/User Interface
1.4 References
This document is prepared in reference to the following documents:
1. IEEE Software Engineering Standards Committee, “IEEE Std 830-1998, IEEE
Recommended Practice for Software Requirements Specifications”, June 25, 1998.

7
1.5 Overview
This document consists of three different sections which are introduction, system overall
description and specific requirement for the system. In section 1 which is introduction part,
it explain about the purpose of this document, scope, definition, acronyms and abbreviation
as well as reference that are being use in the system that will be develop. Moreover, in
section 2, it describes the overall functionality of the new system that will be developed.
Lastly, in section 3, contains specific requirements that will be used to design and develop
the new system.
2.0 Overall Description
2.1 Product Perspective
LKIM Online System is an improvised version of the existing system and is a part of a
larger system comprising the whole LKIM Online Portal. LKIM Online System is
responsible for handling the registration of users, assist in processing of invoice submission,
improving responsiveness of display, providing a better platform for customer support and
providing an improved medium for job browsing and advertising.
2.1.1 Operating Environment
This is a web-based system and hence will require the operating environment for a client
and server GUI. This system highly depends on type and version of browser being
installed in the system i.e. browser version should be used which have HTML5 support.
2.1.2 User Interface
The user’s browser should be HTML5 compatible for a satisfactory user experience.
The UI should be easy to manipulate without additional training. The user should be
able to interact with the system in any of the languages available in the language menu.
The pages should be built with a good sense of color and contrast, and should be
printable, using keys. All pages of the system should be accessible from any page.
2.1.3 Communication Interfaces
LKIM Online System shall connect to database and application server using Local Area
Network with minimum speed of 1Mbps. Users’ devices should be enabled with Internet.

8
The web-based UI is the only means of communication between the user and the system.
The system is accessible through all popular web browsers that interact with HTML5
pages.
2.2 Product Feature
Below is the list of features to be implemented in LKIM Online System.
2.2.1 Login
This function allows the user to enter into the system. The user is required to provide
username and password. After authentication user will have access to user functions.
Availability of menu functions depends on user’s level and permission package.
2.2.2. Logout
This function can be done by all users. It terminates the user session. The system can
also do this function automatically if the session is left unused for an hour.
2.2.3. User Registration
This function is available to non-registered user. User can apply for Nelayan Smartcard
and register membership for KUBENA and KUNITA. Staff will review the application
before any approval given.
2.2.4 Invoice Submission
This function is available to registered users. User can submit invoices which will be
passed to LKIM administration center to be used for claiming of subsidy.

9
2.2.5 Advertise Jobs
This function can be done by registered users. During registration process, users can
determine if they are individual or company based to advertise the job. The user will
send a request and will be reviewed by staff before it is advertised on the system.
2.2.6 Live Chat
This function can be done by registered users. The user can request for a live chat session
with LKIM staff. The chat session is conducted in a private chatroom.
2.2.7 Support Form
This function can be done by non-registered users. The user can fill in form containing
request for support to LKIM staff. The form will be submitted and stored in database.
2.3 Users Characteristics
As from a general top view, users are grouped in one of the following groups:
 LKIM staff
 IT administrators
 Companies
 Individual
 Visitors
There are mainly two roles targeted by LKIM Online System, which are LKIM staff and
user. The expected level of knowledge for each role is explained below.
 The user needs to know the intention of using the system whether to register, to
submit their invoice, to browse or advertise jobs, or to contact the staff for customer
support services. The user should have understanding and the technical know-how
to use and navigate the interface of the system and to submit the related documents
needed.

10
 The LKIM staff must be able to comprehend data given by users to provide
appropriate response for any submission or enquiries. The staff should be trained
and qualified to handle LKIM Online System.
2.4 Constraints
This system is provisioned to be built on the Apache framework which is highly flexible.
Decision regarding which database to use should be taken considering the fact that data
being exchanged or stored is large, and the appropriate data management system will yield
efficient performance. Access to the system is restricted only to the pre-assigned logins.
Higher level users are aware of the restrictions and limitations entitled to the other levels.
Any security personnel can access/verify any user’s account in the system. Every action
taking place in the system is required to be saved in a database, for auditing purposes.

11
3.0 Specific Requirements
3.1 External Interfaces
This section details the external interface requirement of LKIM online system, separated
by feature of the system.
3.1.1 User Registration
Requirement ID REQ_IO101 Version 1.0
Item Register feature
Description Register feature in the LKIM online system
Purpose To allow the user to register to LKIM online system
Format Register button Valid Range Not applicable
Related I/O None
Author Shamsul Nur Erzlin Binti Samsudin
3.1.2 Advertise job using E-Pengambilan
Item Advertise job
Description Advertise job using E-Pengambilan
Purpose To allow user to advertise the vacancies through LKIM online
system
Format ‘Daftar Iklan’ button Valid Range Not applicable
Related I/O None
Author Muhammad Faiz Farhan Bin Hashim

12
Item Invoice submission
Description Submission of invoice using E-Pengisytiharan
Purpose To allow user to claim subsidies provided by LKIM by submitting
the invoice through LKIM online sytem
Format ‘E-Pengisytiharan’ button Valid Range Not applicable
Related I/O None
Author Alia Nabila Binti Ismail
3.1.4 Online Application
3.1.4.1 Kad Pintar
Item Membership Registration (Kad Pintar)
Description Membership registration of Kad Pintar using LKIM online system
Purpose To allow user to register their Kad Pintar membership using
online form provided by LKIM in LKIM online system
Format ‘Daftar Keahlian’ drop
down menu and ‘Kad
Pintar’ button
Valid Range Not applicable
Related I/O None

13
3.1.4.2 KUBENA
Item Membership Registration (KUBENA)
Description Membership registration of KUBENA using LKIM online system
Purpose To allow user to register their KUBENA membership using online
form provided by LKIM in LKIM online system
down menu and
‘KUBENA’ button
Related I/O None
3.1.4.3 KUNITA
Item Membership Registration (KUNITA)
Description Membership registration of KUNITA using LKIM online system
Purpose To allow user to register their KUNITA membership using online
form provided by LKIM in LKIM online system
down menu and
‘KUNITA’ button
Related I/O None

14
3.1.5.1 Registered User
Item Customer Support
Description Customer Support for registered user
Purpose To allow user to chat with the staff if they have any enquiry or
questions
Format ‘Chat’ Button Valid Range Not applicable
Related I/O None
Author Ku Amirul Asyraf Bin Ku Amir
3.1.5.2 Non-registered User
Item Customer Support
Description Customer Support for non-registered user
Purpose To allow non registered user to submit their enquiry or questions
to LKIM staff.
Format ‘Submit Ticket’ Button Valid Range Not applicable
Related I/O None

15
3.2 Functional Requirement
Figure 1: Overall Use Case Diagram
3.2.1 Registration, Login and Online Application
Requirement ID REQ_F001 Version 1.0
Description If the user wants to apply for Nelayan smart card, the system shall
provide an online form for the user to fill in.
Description If the user wants to register for KUBENA and KUNITA
membership, the system shall provide an online form for the user
to fill in.

16
Figure 2: Use Case Diagram for Registration, Login & Online Application

17
Use Case Name Registration, Login and Register Online
Scenario Users have to register first to allow them to login and they can apply
for Nelayan Smartcard and register membership for KUBENA and
KUNITA.
Triggering Event User visits LKIM website to register for Nelayan smartcard and apply
for membership of KUBENA and KUNITA
Brief Description When the user login, the system will authenticate. The user fill up
online form and it will stored in application database. User will
received a feedback.
Actors User, System Authentication, Application Database, Email System
Related Use Cases extend: application for Nelayan Smartcard, membership registration
for KUBENA & KUNITA
include: stored in database
Stakeholders User
Preconditions User must be related to fisheries.
User must exist.
Post Condition User can access system after he/she login.
User will receive a feedback in the form of email containing details of
application.
Flow of Events Actor System
1. User have to register first if
they do not have an account
2. User login into the system
by providing the
information :
 User ID
 Password
3. User fill in online form to
apply Nelayan Smartcard
4. User fill in online form for
membership registration for
KUBENA & KUNITA
5. User receives feedback in a
form of email containing
details of application
1. All the details of registration
will be stored in a database
2. The login will be authenticated
3. Details in the online form will
be stored in application
database
4. Send feedback to the user
Exception Condition i. If user fills in incorrect User ID and/or Password, the login will
be invalid
ii. If the online form is not filled in correctly the application will
not be processed

Figure 3: Sequence Diagram for Registration, Login and Online Applicatio

19
Figure 4: Activity Diagram for Registration, Login & Online Application

20
3.2.2.1 Registered User
Description If registered users have an enquiry, the system should provide an
online chat platform for the user to directly communicate with the
staff.
Figure 5: Use Case Diagram for Customer Support for Registered User

21
Use Case Name Customer Support for Registered User
Scenario Registered user can login to use online chat function to communicate directly with
LKIM staff for any inquiries.
Triggering Event User login to LKIM website and opens online chat function at customer support
section
Brief Description When registered user login, the system will authenticate, and will allow the
functionality of online chat to be used by user. System will notify LKIM staff to
respond to chat.
Actors User, LKIM Staff, User Database, Chat Log Database
Related Use Cases extend: authenticate credentials when user login, chat in room
include: join private chat
Stakeholders Web User: Registered user and LKIM Staff
Preconditions User is registered and has correct user authentication
Post conditions User closes the chat window, exiting the system
1. User login into system
2. User start customer support
chat
3. Staff accept chat
4. User ends chat session and left
1. System authenticate user
credential
2. System prompt staff to attend to
chat request
3. System connects user to staff in
a private chat session
4. System record messages into
database
Exception Condition i. If user does not have login credential, user cannot use the chat functions
ii. If system has no record of user credential, user needs to register
iii. If no staff is online at the moment, system will inform the user and chat
will be rejected

22
Figure 6: Sequence Diagram for Customer Support for Registered User

23
Figure 7: Activity Diagram for Customer Support for Registered User

24
3.2.2.2 Non-registered User
Description If non-registered users have an enquiry, the system should provide
contact form for the user to get feedback from the staff.
Figure 8: Use Case Diagram for Customer Support for Non-registered User

25
Use Case Name Customer Support for Non-Registered User
Scenario Non-registered user can contact LKIM staff using support form
Triggering Event User visits LKIM website, open customer support section, submit support
form
Brief Description When non-registered user opens the customer support section, the system
will display a support form for users to fill in. System will store the form in
database and notify staff to respond to support request. User will receive
feedback from system.
Actors User, LKIM Staff, Support Info Database
Related Use Cases Extend: respond to support request
Stakeholders User; Non-registered user, LKIM Staff
Preconditions User is not registered and not logged in
Post conditions User submitted the form, receive feedback from system and exit the system
1. User opens support page
2. User fill in and submit
support form
1. System receive support form
and give feedback to user
2. System store support form
into database
3. System notify LKIM staff of
support form and prompt for
response
4. System display support form
to staff
Exception Condition i. If user fill in support form and exit the window without
submitting, form will be invalid and not be stored in database

26
Figure 9: Sequence Diagram for Customer Support for Non-registered User

27
Figure 10: Activity Diagram for Customer Support for Non-registered User

28
Description If the user wants to claim for subsidies, the system shall provide
an upload feature for the user to submit the invoices.
Figure 11: Use Case Diagram for Invoice Submission

29
Use case name Invoice Submission
Scenario The user submits the invoices to LKIM administration center to
claim for subsidies.
Triggering event User visit LKIM website to upload the invoices and claim for
subsidies.
Brief description The fishermen that are registered under LKIM want to claim the
subsidies from LKIM organization.
Actors User and LKIM staff
Related use case include: claim subsidy
Stakeholder User and LKIM staff, LKIM organization
Pre conditions The user must login into the system before uploading the invoices.
Post conditions The user receives notifications stating that they can claim subsidy
from LKIM after submitting the invoices.
Flow of event Actor System
1. User must login into the
system by providing the
information:
 User ID
 Password
2. User need to upload their
invoices into the system
3. LKIM staff will verify the
invoices whether or not user
can receive subsidy.
1. Verify user’s details and
information
2. Store the user’s invoices
3. Send automatic email
notifications as a proof to
users.
Exception condition i. If user fills in the incorrect user ID and/or password, the login
procedure will fail.
ii. If the invoices are invalid, the claim process will not be
considered and invoices will be deleted from the system.

30
Figure 12: Sequence Diagram for Invoice Submission

31
Figure 13: Activity Diagram for Invoice Submission

32
3.2.4 Advertise Job
Figure 14: Use Case Diagram for Advertise Job
Description If the user wants to view the job vacancies, the system shall
display job advertisements from internal and external parties.

33
Use case name Advertise Job
Scenario The company fills in vacancy details to be advertised in LKIM
website.
Triggering event Company visits LKIM website and fill in the details on their job
vacancy to be advertised.
Brief description The company wants to advertise their job vacancies in LKIM
website.
Actors Company and LKIM staff
Related use case include: fill in vacancy details.
Stakeholder Company and LKIM staff, LKIM organization
Pre conditions None.
Post conditions Job vacancies which are verified by LKIM staff will be advertised
on their website.
Flow of event Actor System
4. Company will fill in the job
vacancy details that they
want to advertise in LKIM
website.
5. LKIM staff will review and
verify the details for the job
vacancy before allowing it
to be displayed in the
website.
4. Store job vacancy details.
5. Display verified job
vacancy details.
Exception condition iii. If the job vacancy is not verified and approved by LKIM staff,
it will not be displayed in LKIM website.

34
Figure 15: Sequence Diagram for Advertise Job

35
Figure 16: Activity Diagram for Advertise Job

36
3.2.5 Interface and Functionality
Description If the user visits the website using mobile phone, the system shall
provide responsive and compatible display of the website.
Description If the user visits the website using PC, the system shall provide
responsive and compatible display of the website.
Description If the user wants to access all the features, the system shall require
single login from the user.

37
3.3Performance Requirement
Reliable Data Transfer
The system shall have a high success rate on packet transfers to ensure a reliable data
transfer. System should implement error detection, receiver feedback, and retransmission
to the receiver.
Mobile Cross-Compatibility
The application shall be cross compatible between multiple platforms. The most notable
devices shall be the Android, iOS, Windows, MacOS and Linux.
Multi-threading
The system should be multithreaded to insure high speed data acquisition
3.4 Design Constraints
The services that are offered by LKIM currently redirects to multiple websites that requires
different log in. The services should be integrated together to be part of a singular system
that requires only one log in to access every single service smoothly. Logging out from any
screen shall then log the user out and terminate the user session from the whole system.
The various services being offered shall work interchangeably by which user information
can be fetched from the database by all the system.
The website should be able to be displayed across multiple platforms correct proportions,
fitting various screen sizes. The website interface elements need to be responsive by
adapting and resizing according to the screen size be it either mobile phone or desktop to
enhance the user experience. Therefore, the system should also be able to support various
browsers such as Google Chrome, Firefox and Internet Explorer and support multiple
operating system like iOS, Android and Windows OS.
The constraints for language is that the website will be available in English and Malay only
as the company does not have Tamil and Chinese translators. In the future when available,
perhaps the client will provide funds to hire translators for other languages.

38
3.5 Software System Attributes
3.5.1 Availability
Requirement
ID
Description Priority Author
REQ_Q001 The system shall able to be used if there
is Internet connection
High Shamsul Nur
Erzlin
3.5.2 Security
Requirement
ID
REQ_Q002 If a user log in, the User Id and Password
need to be validate first by the System
Authentication
High Shamsul Nur
Erzlin
3.5.3 Portability
Requirement
ID
REQ_Q003 The website can be view using PC and
mobile phone
High Shamsul Nur
Erzlin

39
MINUTES OF MEETING
Meeting/Project Name: Client – Vendor Meeting
Date of Meeting: 28th
March 2018 Time: 8.45 am – 9.00 am
Minutes Prepared By: Shamsul Nur Erzlin Binti
Samsudin
Location: 01-00-03
1. Meeting Objective
 To discuss and validate Use Case Diagram
 To discuss and validate Activity Diagram
 To discuss and validate Paper Prototype
2. Attendance at Meeting
Name Client/Vendor
Ku Amirul Asyraf Bin Ku Amir Vendor
Shamsul Nur Erzlin Binti Samsudin Vendor
Muhamad Syafiq Bin Hazhar Client from Lembaga Kemajuan Ikan Malaysia
Nur Amira Izzaty Binti Azhar Client from Lembaga Kemajuan Ikan Malaysia
3. Agenda and Notes, Decisions, Issues
Topic Owner
Validate Use Case Diagram
- Client check and validate the use case diagrams that have been
developed
All group members
Validate Activity Diagram
- Client validate whether the flow of activity for each functionality is
correct or not
All group members
Refining Prototype
- Client see the first draft of prototype and a few parts need to be
improved
All group members
4. Action Items
Action Owner
Improvise prototype as per client request to ensure that the interface is user
friendly
All group members
5. Next Meeting (if applicable)
Date: 4th
March 2018 Time: 8.00 am Location: 01-00-03
Objective: To validate final prototype

Software Requirements Specification - LKIM

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Software Requirements Specification - LKIM

Similar to Software Requirements Specification - LKIM (20)

Recently uploaded

Recently uploaded (20)

Software Requirements Specification - LKIM