Software Requirements

Specification
for

Cloud-based Digital Portfolio

Platform
Version 1.0

Prepared by

Group Name: Portech

Cheong Wan Hoy

0314101

Koh Keng Chye

Goh Ka Jiunn
Yip Fook Tian

0315048
0315321
0309284

Instructor:
Course:

wanhoy.cheong@sd.taylors.edu.m
y
kengchye.koh@sd.taylors.edu.my
kajiunngoh@gmail.com
Oscaryip4315@hotmail.com

AZWEEN BIN ABDULLAH

ITS60703 - Software Process

Lab Section:

<place your lab section here>

Teaching Assistant:

<place your TAs name here>

Software Requirements Specification for <Project>

Date:

Page ii

<place the date of submission here>

Contents
CONTENTS ................................................................................................................................................................II
REVISIONS .............................................................................................................................................................. IV
1

INTRODUCTION ...............................................................................................................................................1
1.1
1.2
1.3
1.4
1.5
1.6

OVERALL DESCRIPTION............................................................................................................................... 4
2.1
2.2
2.3
2.4
2.5
2.6
2.7

DOCUMENT PURPOSE ................................................................................................................................ 1

PRODUCT SCOPE .......................................................................................................................................1
INTENDED AUDIENCE AND DOCUMENT OVERVIEW ...................................................................................1
DEFINITIONS, ACRONYMS AND ABBREVIATIONS ....................................................................................... 1
DOCUMENT CONVENTIONS ........................................................................................................................ 3
REFERENCES AND ACKNOWLEDGMENTS ..................................................................................................3

PRODUCT PERSPECTIVE ............................................................................................................................ 4

PRODUCT FUNCTIONALITY ......................................................................................................................... 4
USERS AND CHARACTERISTICS .................................................................................................................5
OPERATING ENVIRONMENT........................................................................................................................ 5
DESIGN AND IMPLEMENTATION CONSTRAINTS .......................................................................................... 5
USER DOCUMENTATION ............................................................................................................................. 5
ASSUMPTIONS AND DEPENDENCIES ..........................................................................................................6

SPECIFIC REQUIREMENTS .......................................................................................................................... 7

3.1
EXTERNAL INTERFACE REQUIREMENTS ....................................................................................................7
3.1.1
User Interfaces.......................................................................................................................................7
3.1.2
Hardware Interfaces .............................................................................................................................. 7
3.1.3
Software Interfaces ................................................................................................................................ 7
3.1.4
Communications Interfaces ...................................................................................................................8
3.2
FUNCTIONAL REQUIREMENTS ....................................................................................................................8
3.2.1
User Authentication ............................................................................................................................... 8
3.2.2
Manager User Account .......................................................................................................................... 8
3.2.3
Create e-portfolio ..................................................................................................................................8
3.2.4
Modify e-portfolio ..................................................................................................................................9
3.2.5
Auto-save e-portfolio ............................................................................................................................. 9
3.2.6
Manage e-portfolios............................................................................................................................... 9
3.2.7
Data extraction ......................................................................................................................................9
3.2.8
Auto optimization .................................................................................................................................10
3.2.9
Search e-portfolio database .................................................................................................................10
3.3
BEHAVIOUR REQUIREMENTS ...................................................................................................................11
3.3.1
Use Case View .....................................................................................................................................11

OTHER NON-FUNCTIONAL REQUIREMENTS........................................................................................ 13

4.1
PERFORMANCE REQUIREMENTS..............................................................................................................13
4.2
SAFETY AND SECURITY REQUIREMENTS .................................................................................................13
4.2.1
24/7 Security Team .............................................................................................................................. 13
4.2.2
Safeguard users data .......................................................................................................................... 13
4.2.3
Firewalls ..............................................................................................................................................13
4.2.4
High Availability ..................................................................................................................................14
4.2.5
Authentication ......................................................................................................................................14

Software Requirements Specification for <Project>

Page iii

4.2.6
Data Integrity.......................................................................................................................................14
4.3
SOFTWARE QUALITY ATTRIBUTES ...........................................................................................................14
4.3.1
Portability ............................................................................................................................................14
4.3.2
Maintainability ....................................................................................................................................15
4.3.3
Correctness ..........................................................................................................................................15
4.3.4
Reliability.............................................................................................................................................15
5

OTHER REQUIREMENTS ............................................................................................................................ 16

APPENDIX A DATA DICTIONARY ....................................................................................................................17

APPENDIX B - GROUP LOG .................................................................................................................................18

Software Requirements Specification for <Project>

Page iv

Revisions
Version

Primary Author(s)

Description of Version

Draft Type
and
Number

Full Name

Information about the revision. This table does

not need to be filled in whenever a document is
touched, only when the version is being upgraded.

Date Completed
00/00/00

Software Requirements Specification for <Project>

Page 1

1 Introduction
1.1 Document Purpose
The purpose of the document is to provide a detailed overview of the software, as well as
giving the outline for the requirement in order to give better understanding of the software. This
document will focus on the functionality of the software. This document will also specify the
requirements that will be needed to develop the software.

1.2 Product Scope

Profect is a cloud-based digital portfolio platform that allows users to showcase their
achievements, work experiences, and skills in the form of a professional, quality e-portfolio.
Profect also functions as a database of job candidates for employers to easily find candidates who
fit their hiring specifications.
The purpose of the software is to provide a platform for users to easily create and manage
professional e-portfolios that meet the standards of the industries. The software also serves as a
database in which employers are able to effectively search for qualified candidates. This helps to
provide exposure to job candidates by connecting them to prospective employers, and also helps
employers to find the job candidates with the specific qualities that they are looking for.

1.3 Intended Audience and Document Overview

The intended audience for the document will be the client, as they will be the users for the
software. The intended audience will be mainly focused on those that will be utilising the e-portfolio
for both job finding and hiring purposes, specifically job candidates and human resources
department in a company.
This SRS will contain the overview of the software, which includes the functionality of the software,
types and characteristics of the users, the operating environment, the design and implementations
constraints that might affect the software, the user documentation components of the software,
assumed factors that may affect the software as well as the dependencies of the software. This
SRS will also contain both the functional and non-functional requirements for the software, which
includes the hardware and software interface requirements, use case view for the software,
performance requirements, safety and security requirements as well as the software quality
requirements.

1.4 Definitions, Acronyms and Abbreviations

Acronym
CSS

Literal Translation
Cascading Style Sheets

Software Requirements Specification for <Project>

Page 2

FTP

File Transfer Protocol

GUI

Graphical User Interface

HTML5

Hypertext Markup Language Version 5

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol over SSL

(Secure Socket Layer)

IEEE

Institute of Electrical and Electronic

Engineers

OS

Operating System

SRS

Software Requirement Specification

TCP/IP

Transmission Control Protocol/Internet

Protocol

UML

Unified Modeling Language

XHTML

Extensible Hypertext Markup Language

iOS

iphone OS

RAID 0

Redundant Array of Inexpensive Disks

DMZ

Demilitarized Zone

Term

Definition

Authentication The process of identifying an individual.

Compatible

The ability of device/program to work with another device/program.

Constraints

Limitation and restriction from achieving the goal.

Feasible

Capable of being accomplished.

Functionability Range of operations that can be run on computer/devices.

Optimization

To make something as effective as possible.

Privilege

The permission level to perform an action.

Software Requirements Specification for <Project>

Page 3

Level
Troubleshoot

To identify the problem and fix it.

Verification

The process of showing the truth and accuracy.

1.5 Document Conventions

In general this document follows the IEEE formatting requirements. The document uses the
Arial font family of different font sizes throughout the document for text. Section headers use
font size 18, bolded font, white font colour, a dark gray background, and are numbered in
increments of 1. Subsection headers use font size 14, bolded font, black font colour, and are
numbered in increments of 0.1 from the parent header. Further subsections use font size 12,
bolded font, black font colour, and are numbered in increments of 0.0.1 from the parent
header. Any additional subsections use a font size of 11, bolded font, and are numbered in
increments of 0.0.0.1.
Normal text use a font size of 11.5. While comments are written in italics.

1.6 References and Acknowledgments

International Standard for Systems and Software Engineering Software Life Cycle
Processes, ISO/IEC 12207, 2008.

Software Requirements Specification for <Project>

Page 4

2 Overall Description
2.1 Product Perspective
Profect is an extension of online website-developing software and is therefore a follow-on member
of a product family. Profect functions very much like many web-developing software and allows for
quick and easy design of web pages. However, Profect is a unique variant that concentrates on
the production of professional electronic documents and portfolios. Profect provides a way for
users to easily generate professional and quality e-portfolios from scratch quickly and easily.
Additionally, employers are able to search through a rich e-portfolio database of job candidates
based on specific keywords and filters.

2.2 Product Functionality

There are several major functions that the product must perform or let the user perform. These
are:
User Authentication
o Allows users to authenticate themselves by inputting their username and
password
Manage user account
o Allows users to change account settings such as password, contact details,
profile description, and privacy settings.
Create e-portfolio
o Allows the user to create multiple new e-portfolios.
Modify e-portfolio
o Allows users to utilize the e-portfolio building tools to modify their e-portfolio.
Auto-save e-portfolio
o The system automatically saves modifications to the e-portfolio at 10 second
intervals.
Manage e-portfolios
o Allows users to rename, arrange, monitor, and delete existing e-portfolios, as
well as modify e-portfolio settings.
Data extraction
o The system allows users to declare text in their e-portfolios as specific
information. The defined information is then organized into the systems
database, allowing for easy searching of job candidates based on specific traits.
Auto optimization
o The software automatically optimizes the e-portfolio to be viewable in any mobile
platform.
Search e-portfolio database
o Allows users to browse through the e-portfolio database using query keywords
and filters.

Software Requirements Specification for <Project>

Page 5

2.3 Users and Characteristics

Unregistered users
Have the lowest privilege levels. Only able to browse e-portfolios available to the public
and through unlisted links.
Registered users
Have normal privilege levels. Can access e-portfolio management and building tools.
Can browse e-portfolios available to the public and through unlisted links.
Employers
Has the highest privilege levels. Can access a large database of e-portfolios, and is
able to search for specific requirements through query keywords and filters.

2.4 Operating Environment

Minimal requirements:
All operating systems (OS) that can support HTML5 compatible web browsers, such as
Windows, MacOS, Android, iOS, and unix.
Web browser that supports HTML5(Search the Web browser version that support
HTML5)
Desktop Computers, Laptop, tablets, smartphone,

2.5 Design and Implementation Constraints

The database server cant cope with the excessive of traffic.

Incompatible with the old hardware platforms.
The project team are not skilled at the language used in coding
Budget constraints limit the options of development tools

Timing Requirements (Effective data structures)

2.6 User Documentation

To maximize the user-friendliness of the software product, a brief walkthrough/tutorial will be
provided to new users who visit the website where the software is implemented for the first time,
during which short descriptions complete with icons and arrows pointing towards each button
within the GUI will be displayed. Additionally, on-line help will be provided through a moderated
forum where customer support can be provided to users who have issues with the software. The
forum also serves as a platform for users to report any bugs, or leave suggestions for
improvement of the software. For the administrators in charge of the system, user manuals
detailing the workings of the system and troubleshooting methods are provided.

Software Requirements Specification for <Project>

Page 6

2.7 Assumptions and Dependencies

There are several major assumptions that might significantly affect the requirements stated in the
SRS:
The software product is innovative and many users will use it
The software requirements can be implemented on time and within budget
The software requirements are feasible
No copyright or licensing infringement of tools used in software development
Software development team has sufficient knowledge and skills to implement software
requirements
The software product is secure and safe

Software Requirements Specification for <Project>

Page 7

3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
Web Page Outline:
Homepage (Sign in Button, Page menu button bar)
My Portfolio
o Sign in Screen: Email & password input box, Radio button for New user Or
Existing user, A Remember me checked box, A GO button
o Sign in successfully message: Go to dashboard page which consists of all the
portfolio created
o Unsuccessful login message: Invalid email or password.
o Dashboard Screen (If log in is successful): Create new portfolio button, Edit
button , delete button,
Explore Portfolio
o Gallery of portfolio examples
o A search bar included (Filter the types and category)

3.1.2 Hardware Interfaces

Profect does not have any specifically designated hardware just for it to be run on the clients
side. The system stills require the hardware devices such as desktop computers, laptops,
smartphones and tablets to run the web browsers which are capable to deal with the
necessary functionality in the system on the clients side. The database servers interfaces are
solely depends on its underlying operating systems which is designated by the server
subscription services.

3.1.3 Software Interfaces

There is one key software component which is required for the Profect to works which is the
Web browsers. The major web browser that are able to run Profect are Mozilla Firefox 35 or
above, Google Chrome 39 or above and Internet Explorer 11 or above. The operating system
that are able to run the web browser application such as Windows, Linux, Mac OS, Ubuntu,
Android, IOS and more. The web browser must have the ability to support the web libraries
such as HTML, CSS, JavaScript and XHTML.
The key data item that might go through the software component are the account login & signup information. Account login and sign-up information are the web clients input for the system
to authenticate the access of the Profect. At the moment, account verification service is
happening to verify the validity of username and password. Message output of the system are
expected at this moment to notify the users whether the login operation is successful or not.

Software Requirements Specification for <Project>

Page 8

The login information will be shared across the different web browser in a local machine if the
user used the Remember Me option which will store the username and password as a local
internet cache. The web browsers will be automatically use this local cache to fill in the login
information for the consecutive logins. However, there is one constraint for the implementation
which is the local cache that created on the local machine are only available to that machine
alone. You need to re-input the login information for others machine or computers.

3.1.4 Communications Interfaces

The communication interface for the Profect uses HTTPS, HTTP and FTP protocol to establish
the connection between the Web browser and server. The HTTP will be used for the web
clients to request the content of the web pages from the web server through the web browsers.
HTTPS (Secure HTTP) is required to establish a secure communication between the web
browser and servers. Secure communication is necessary to handle the sensitive information
such as the password and username during the login process. The FTP (File Transfer
Protocol) is for the purpose of users transferring the files to our web server or vice versa. Basic
web browser standard support such as the CSS, XHTML, JavaScript are required for the web
browsers in compliance with the Web TCP/IP to fully utilize the Profect functionality for the
users.

3.2 Functional Requirements

3.2.1 User Authentication

Username and password input

o The fields for both username and password only accepts alphanumeric input,
spaces and special characters are not allowed.
Authentication
o Once the login button has been clicked, the data entries are crosschecked with
the user data from the database server. Appropriate access is granted
depending on type of user if authentication is successful.

3.2.2 Manager User Account

Change profile settings

o Users can edit profile details such as name, date of birth, contact details, and
addresses. The user has the choice to save or discard all changes.
Change account settings
o Allows users to edit account password, privacy settings (eg. who can see their eportfolios, who can contact them, who can look them up), payment settings, and
notification settings.

3.2.3 Create e-portfolio

Software Requirements Specification for <Project>

Page 9

Create new e-portfolio

o Users can create a new empty e-portfolio that can be modified later if the user
has not exceeded the maximum number of e-portfolios he can have.

3.2.4 Modify e-portfolio

Manage content windows

o Users are able to drag-and-drop windows into their desired positions within the
webpage with ease. Users are also able to delete the windows by hitting the
delete key with the window selected. Additionally, the windows can also be
realigned and reorganized using the drag-and-drop method.
Manage pages
o Users are able to add, remove, and reorganize all pages within the e-portfolio.
Navigate between pages
o Users are able to navigate easily from page to page using a top-bar menu.

3.2.5 Auto-save e-portfolio

Active auto-saving
o

All changes made to the content of the e-portfolio are automatically saved every
time changes are made. This function is utilized throughout the e-portfolio
modification process.

3.2.6 Manage e-portfolios

View all created e-portfolios

o Users are able to view all their e-portfolios as large grids with thumbnails in a
uniform grid panel.
Organize e-portfolios
o Users can rearrange the e-portfolio grids by dragging and dropping them in their
desired orders.
Change e-portfolio settings
o Users are change the settings of each individual e-portfolio created, such as
visibility settings (ie. Who can view this e-portfolio) and lock settings (ie. Can this
e-portfolio be deleted?).
Access e-portfolios
o Users are able to click on buttons to access individual e-portfolios for
modification.

3.2.7 Data extraction

Automatic data extraction

o Information is stored into the database when the user enters information into
pre-defined fields. (eg. name, e-mail address, date of birth).

Software Requirements Specification for <Project>

Page 10

Manual data declaration

o Users are able to declare specific text in their e-portfolio as pre-defined types of
information to be stored into the database (eg. The user defines a field of text as
Programming Languages Known by highlighting the text and defining it from an
action menu. The defined text is then automatically organized by the system into
a form for the user to verify and modify. Once verified and completed, the
information is stored into the database, allowing employers to find them based
on that information.)

3.2.8 Auto optimization

Mobile platform optimization

o The software automatically reorganizes e-portfolio contents to optimize it for
mobile platforms such as tablets and smart phones.

3.2.9 Search e-portfolio database

Access level authentication

o The system checks if the user has the required access level to use the search
database function. Only allows access if true.
Search by keyword and filters
o

Employers can enter specific keywords and choose filters to screen out the job
candidates that meet their criteria. Examples of keywords are independent,
and multilingual. Filters are more specific and can be chosen from drop-down
lists and checkboxes. Examples of filters are years of work experience, field of
study/work, spoken languages, and country of residence.

Software Requirements Specification for <Project>

Page 11

3.3 Behaviour Requirements

3.3.1 Use Case View

The Use case diagram was drawn based on the assumptions as follows:
Users are successfully access our system through the web browsers.
The web page is functioning.
Only basic functional requirements are showing in the UML diagram.
3.3.1.1 Actors
The possible actors that are interacting with the system are as following:
Users
Its the main actor for the system which access the system to use most of the
functionality of the system. The user can be categorized as registered or unregistered
user.
Web browsers

Software Requirements Specification for <Project>

Page 12

Web browsers is the external actor which associate with the user to interact with the
system in order to fully utilize the functionality of the system.
3.3.1.2 Use Case
The key use case that are being captured in the system are as following:
Sign Up Account
One of the initial Use Case that showing the unregistered user need to sign up account
before they can fully utilize the functionality of the system.
Login Account
One of the initial Use Case that the registered user can log in to access our core
system for the purpose of create portfolio, delete portfolio and etc..
Explore Portfolio
One of the initial Use Case shows that both registered or unregistered users are able to
explore the example of created portfolio by using keyword filtered-based search.
Verify Account Validity
This Use Case only occurs if the registered user want to login their account. This is
consider a verification action for unauthorized access. Hence, the extension point for
this use case is invalid login attempt.
Check Account Availability
This Use Case is for the purpose for checking account availability in the systems web
server to verify whether the sign-up information provided by the users is conflicting with
the existing accounts.
Send Error Message
Web browsers will send the error message to the users if the invalid login or sign up
attempts.
Manage Account Settings
Allow registered users to change certain settings for the account created.
Log Out Account
Registered users might log out of the account for security purpose.
Create Portfolio, Edit Portfolio, Delete Portfolio
Registered users can manage their portfolio through creating a new portfolio, delete
existing portfolio, and make changes to the content of the portfolio.

Software Requirements Specification for <Project>

Page 13

4 Other Non-functional Requirements

4.1 Performance Requirements
1. Optimize, consider about the memory usage, the use of the efficient algorithm, and also
the amount of calculation and processes when running the system.
2. 0.2 second roughly the limit of processing speed to process the information after users
input the data, so that the output can be immediately viewed, which can be also said good
response time is needed.
3. System must be able to handle around 100,000 customers or users at the same time.
4. Reduce the systems workload to prevent going beyond the limit of the number of the
processes system that can handle, like the scalability of the system.
5. The storage space also needed to be taken into consideration.
6. For the mobile devices application, it should occupies less memory with high performance
because nowadays, those smart devices are having limited memory capacity and didnt
have high processing power, so that it will causes some problem here, that why the
application for the mobile devices should have the above features.

4.2 Safety and Security Requirements

4.2.1 24/7 Security Team
The purpose of having this security is to alter or obtain the confidential data. Hackers or intruders
may actually come in to damage or steal the information by physically entering the data centres to
obtain the physical access to the servers, which is quite dangerous. Any physical damage done to
these servers would result in a severe loss to the company, that why a full-time security personnel
will be needed to guard the data by involving in role to implement and develop the company
security policies and standard.

4.2.2 Safeguard users data

We need to have this security as users data will be distributed into different computer with
different location rather combining every data into one single computer or big machine, which it is
totally not safety enough because if someone get to access it in just one single computer or big
machine, everything is gone or will be controlled by others people who get in. Other that, people
can get in and see all the users data if they managed to hack in or access. Moreover, having this
requirement is to giving the data to have multiple database servers at different locations that are
not revealed to guarantee the data availability. This has the same concept as RAID 0 (Redundant
Array of Inexpensive Disks) which is also known as striping the location of a stored data file in
s e v e r a l p h y s i c a l h a r d d r i v e s t o i m p r o v e t h e r e a d a n d wr i t e t h e p e r f o r m a n c e .

4.2.3 Firewalls
Usually hacking is done by different kind of hacker such as black hat hacker, white hat hacker, or
many others, that why the server has to be strengthen to prevent this happen. So by having this
solution is to provide the databases and the server with the feature of double firewall, which known

Software Requirements Specification for <Project>

Page 14

as demilitarized zone (DMZ) configuration because with the double solid layer of protection, it
actually can help detect most of the penetration made on the internal network. Besides that, with
this safeguard, it actually filter everything more than just one time, making it more safe when
accessing databases and server, and it also helped to guard more sensitive internal network from
nefarious external users. Actually this security that provided is much better than the single
configuration.

4.2.4 High Availability

The system should actually be available 24/7 to the intended audience with a 99% availability and
should be correctly handle with the high load circumstances. It will be concerned with the reliability
of the software and network components. For the Intentional Denial of Service Attack, it is not
foreseen as a significant concern. It is like giving the users to have 24/7 accessibility to our
system.

4.2.5 Authentication
For this security, authentication actually addresses security and safety requirements to ensure
those who are using the system are actually their own self who access it. This is definitely one of
the biggest concern when data is being involved. A users authentication is primarily done through
usernames and passwords, which actually each users will have their own account and it can be
only accessed by their own self, so that their data will be kept safe and only them can see their
own data and others people cannot simply access peoples data without the users username and
password.

4.2.6 Data Integrity

The integrity of Cloud-Based Digital Portfolio data will be critical to its success as a product. Before
data are uploaded and as part of the upload process, it will go through an extensive data
validation. Organizations policies and procedures are needed and should be followed in order to
protect the data from intentional or unintentional modifications and to ensure accurate data are
made available.

4.3 Software Quality Attributes

4.3.1 Portability
For the portability, it ensure the portability of the system for the user as they dont need to
purposely get a specific computer or laptop to just install the system and enjoy it. Portability
actually refers to the usability of the same software in different mobile operating system or
computer which utilize high-level computer programming. The application or system would be
develop in different programming languages allows to be supported by the mobile operating
system currently popular in the market, which is the iOS and Android, and also in all kind of the
computer or laptop.

Software Requirements Specification for <Project>

Page 15

4.3.2 Maintainability
For the maintainability, it actually refer to the ability of the system should be able and easy to
extend. By allowing for testing of different functions, and the test environment will be build for
the system. Besides that, the codes will be written in a way that it favors implementation of
new functions in the future. The system will also be fit and fulfill all the requirements to perform
system testability. By achieving it, we can actually making the maintainability work to be easy
by making the line of codes to be easy to understand with comment on it, so that when another
person who come in and in charge of this, he or she will understand each line of the code and
how did it work. Other than that, we can also make the codes short and organize for easy to
maintain.

4.3.3 Correctness
Correctness should be there to provide facilities for legal persons only. A boundary has been
set to ensure privacy and precision as appropriate. Any classified information can only be
viewed by restricted audience.

4.3.4 Reliability
Since this is a security product the reliability is a major requirement to achieve security goals.
The system must be efficiently available 24/7 and be able to handle a high maximum number
of load.

Software Requirements Specification for <Project>

Page 16

5 Other Requirements
<This section is Optional. Define any other requirements not covered elsewhere in the SRS. This
might include database requirements, internationalization requirements, legal requirements, reuse
objectives for the project, and so on. Add any new sections that are pertinent to the project.>

Software Requirements Specification for <Project>

Page 17

Appendix A Data Dictionary

Name
accountUsername

Length
8~36

Data Type
String

Purpose
Authentication

Data Owner
Security Dept.

accountPassword

8~36

String

Authentication

Security Dept.

accountAccessLevel

24

String

Access Privileges

accountFirstName

24

String

User Details

Database
Admin
Database Dept.

accountLastName

24

String

User Details

Database Dept.

accountCreatedDate

N/A

Date

Account Record

Database Dept.

accountContactNo

24

Numeric

User Details

Database Dept.

accountEmail

36

String

User Details

Database Dept.

Software Requirements Specification for <Project>

Page 18

Appendix B - Group Log

Meeting Minute 1
Date:

7 April 2015

Time:

12:00 p.m. ~ 2.00 p.m.

Attendance
Koh Keng Chye, Cheong Wan Hoy, Goh Ka Jiunn, Oscar Yip

Agenda Items

Evaluate the ideas for the project

Present the overview of the idea to the group members.

Outcomes

Idea of the project was decided

All of the team members need to do research regarding the projects methodologies.

Meeting Minute 2
Date:

9 April 2015

Time:

12:00 p.m. ~ 2.00 p.m.

Attendance
Koh Keng Chye, Cheong Wan Hoy, Goh Ka Jiunn, Oscar Yip

Agenda Items

Discussion on any add on for the project

Clear the doubts of team members on the projects scope

Software Requirements Specification for <Project>

Page 19

Outcomes

Outline on the scope of the project is defined

Next meeting need to discuss and identify the functional requirement for the system.

Meeting Minute 3
Date:

10 April 2015

Time:

2:00 p.m. ~ 4.00 p.m.

Attendance
Koh Keng Chye, Cheong Wan Hoy, Goh Ka Jiunn, Oscar Yip

Agenda Items

Identify the functional requirement of the system

Discussion on the separation of task to fill in the SRS

Outcomes

Outline of the functional requirements of the system are briefly described

Goh Ka Jiunn is responsible in filling the (1. Introduction ) in SRS.

Cheong Wan Hoy is responsible in filling the (2. Overall Description) in SRS.

Koh Keng Chye is responsible in fill the (3. Specific Requirements) in SRS.

Oscar Yip is responsible in frilling the (4. Other Non-functional Requirements)

Meeting Minute 4
Date:

14 April 2015

Time:

12:00 p.m. ~ 2.00 p.m.

Attendance
Koh Keng Chye, Cheong Wan Hoy, Goh Ka Jiunn, Oscar Yip

Software Requirements Specification for <Project>

Page 20

Agenda Items

Review and report the progress of SRS

Identify follow-up actions in finalizing the SRS draft

Discussion on the design of the system prototype

Outcomes

All team members are required to further refine and fix the mistakes in SRS.

Cheong Wan Hoy is going to design the prototype based on the design outline which
has been established.