REQUIREMENTS ANALYSIS

4.1 Introduction

The purpose of System Requirements Analysis is to obtain a thorough and detailed

understanding of the users need and to break it down into discrete requirements, which are
then clearly defined, reviewed and agreed upon with the Customer Decision-Makers. During
System Requirements Analysis, the framework for the application is developed; including
functional requirements, non-functional requirement, hardware and software requirements as
well as the comparison of various development platforms and languages will be reviewed. In
other word, system requirement analysis will provide the foundation for all future design and
development efforts.

4.2 Fact Finding Techniques

System analysis starts with data collection. Several appropriate and effective techniques are
used to collect data in order for us to define and specify users requirements, which is also
known as requirement determinations. Below are the elaborations of techniques and method
being used:

4.2.1 Existing system review & Literature Review

The existing system review is important to know the features in the current
familiar system. The existing system is evaluated and analyzed to know its
strengthen and weaknesses. From the evaluation, good features are captured and
implemented in the Family Car Maintenance System. The literature review is
important to let us know the concepts of how the databases are built for this
maintenance system. Besides that, techniques and matching algorithm can get from
those articles of experts. The literature review will be done continuously in the future
in order to get more and more important information to build the effective and
efficient system.
 4.2.2 Brainstorming
Brainstorming with a course mate to discuss and get suggestions about the
other features are needed inside functional requirement, non-functional requirement
and use case.

4.2.3 Discussion
Discussion with supervisor, Madam Haslina Binti Hisham to gather
information and ideas. Advice and guidance from the supervisor is important to
identify a users functional and non-functional requirement and to achieve the project
objective.

4.3 SYSTEM USE CASES

NAME Sign Up
DESCRIPTION Sign Up is the procedure used to get Registered for using
the system. It contains the profile information about the
user.
ACTORS Admin, Faculty and Students.
PRECONDTIONS Internet access, Website URL, Android application needs
to be installed for student. Click Sign Up button.
BASIC FLOW OF EVENTS 1. User (Admin, faulty, student) will open the website
URL or Mobile application.
2. Click on the Sign Up button.
3. Enter users profile information, email Ad
password and press Save button.
4. After that, users will able to log In for using the
system.

ALTERNATIVE EVENT Sign In or close the system.

KEY SCENARIOS To use this system first requirement is to sign Up.

POST CONDITIONS The user will be able to Log In.

SPECIAL REQUIREMENTS The user should have a unique email address for logging
purpose.
ADDITIONAL REQUIREMENTS All the field of profile info needs to be filled.

TABLE: 4.3.1
 FIGURE: 4.3.1

NAME Sign In
Login is the procedure used to get access to system
DESCRIPTION usage. It involves user ID and Password which is unique
for everyone.
ACTORS Admin, Faculty and Students.
PRECONDTIONS Internet access, Website URL, Android application needs
to be installed for student.
BASIC FLOW OF EVENTS 1. User (Admin, Faulty, Students) will open the
website URL or Mobile application.
2. Click on the login button.
3. Enter ID.
4. Enter password.
5. Here user can use his required system.
ALTERNATIVE EVENT Sign Up or close the system.
KEY SCENARIOS By using sign In user will enter into the required system.

POST CONDITIONS The user will move to add/view or delete window.

SPECIAL REQUIREMENTS User ID must be some kind of email.
ADDITIONAL REQUIREMENTS No.

TABLE: 4.3.2
 FIGURE: 4.3.2

NAME Select Designation

Designation is selected by admin after login. This will help
DESCRIPTION to describe the position of a user.
ACTORS Admin and Faculty.
PRECONDTIONS Internet access, Website URL
BASIC FLOW OF EVENTS 1. User (Admin, Faulty) will open the website URL.
2. Click on the designated button.
3. Enter a description.
4. Submit it.
5. Record saved to database.
ALTERNATIVE EVENT Add lecture, Announcements.
KEY SCENARIOS By submitting it user will have some position against the
students and faculty.

POST CONDITIONS The user will move to add/view or delete window.

SPECIAL REQUIREMENTS The designation must be right.
ADDITIONAL REQUIREMENTS No.

TABLE: 4.3.3
 FIGURE: 4.3.3

NAME Add/view/update/delete
DESCRIPTION In this window user can view, add, update or delete the
courses of his own choice.
ACTORS Admin, Faculty and Students.
PRECONDTIONS User needs to be Sign In.
BASIC FLOW OF EVENTS 1. User (Admin, Faulty, Students) will open the
website URL or Mobile application.
2. Click on the login button.
3. Enter ID and Password.
4. Here users can view, delete or add more courses.
ALTERNATIVE EVENT Press back key to move in sign Up/ sign In window.
KEY SCENARIOS Using this system user will be able to get announcements
and lecture for his required course only.

POST CONDITIONS The user will move to his required system. Faculty and
admin can post their announcements and materials.
Faculty and students get their relevant announcements.
SPECIAL REQUIREMENTS All records must be saved correctly.
ADDITIONAL REQUIREMENTS No.

TABLE: 4.3.4
 FIGURE: 4.3.4

NAME Upload Announcements/ lecture Material

DESCRIPTION In this window admin can post news for students/faculty/
Faculty is able to upload lecture and announcements for
students.
ACTORS Admin and faculty.
PRECONDTIONS User needs to be select his relevant subject or
department.
BASIC FLOW OF EVENTS 1. User (Admin, Faulty, Students) will open the
website URL or Mobile application.
2. Click on the login button.
3. Enter ID and Password.
4. Select the subject or department for which user
uploading announcements or lectures.
5. Upload lectures and announcement.
ALTERNATIVE EVENT If a user is going to upload lecture its alternate event is
post announcements and vice versa.
KEY SCENARIOS By using this student may able to view announcements
and download lectures.

POST CONDITIONS A window appears where the user can see his uploaded
announcements and lectures. By pressing back button
window appears where the user can choose his required
subjects.
SPECIAL REQUIREMENTS Only faculty and Admin can use this function
ADDITIONAL REQUIREMENTS No.

TABLE: 4.3.5
 FIGURE: 4.3.5

NAME View Announcements/ Download lectures Material

DESCRIPTION In this window Student and faculty can view their relevant
announcements and download their materials.
ACTORS Student and faculty.
PRECONDTIONS User needs to sign In and select his relevant subject to
view and download lecture materials.
BASIC FLOW OF EVENTS 1. User (Faulty, Students) will open the website URL
or Mobile application.
2. Click on the login button.
3. Enter ID and Password.
4. Select the subject or department for which user
wants to see announcements.
5. Downloads lectures and announcement.
ALTERNATIVE EVENT If a user is going to download lectures its alternate event
is view announcements and vice versa.
KEY SCENARIOS By this user may be able to read lectures and can add
comments against announcements.

POST CONDITIONS Downloading starts.

SPECIAL REQUIREMENTS Only students and faculty can use this function
ADDITIONAL REQUIREMENTS No.

TABLE: 4.3.6
 FIGURE: 4.3.6

NAME Add Comments

DESCRIPTION In this window Student and faculty can add comments to
post.
ACTORS Student and faculty.
PRECONDTIONS User needs to sign In and select his relevant subject to
view post so that comments can be added to that post.
BASIC FLOW OF EVENTS 1. User (Faulty, Students) will open the website URL
or Mobile application.
2. Click on the login button.
3. Enter ID and Password.
4. Select the subject or department for which user
wants to see announcements.
5. Add comments below the announcement.
ALTERNATIVE EVENT Only view the announcements or by pressing back key to
move on the previous screen.
KEY SCENARIOS By using this user may be able to write something about
announcements.

POST CONDITIONS Comments are added against the post.

SPECIAL REQUIREMENTS Only students and faculty can use this function
ADDITIONAL REQUIREMENTS No.

TABLE: 4.3.7
 FIGURE: 3.3.7

4.2 USE CASE DIAGRAMS

FIGURE: 3.3.7
4.4 System requirements

The requirement specification outlines the general users requirements to identify the
systems functional requirements as well as non-functional requirements.

4.4.1 Functional Requirements.

In software engineering, a functional requirement defines a function of a software system or

its component. A function is described as a set of inputs, the behavior, and outputs.

4.4.1.1 Registration
User needs to be signed up and sign in for using the system. The student
notification system will have the record of three categories Admin,teacher and
student. Select one option at home page. Teacher and an admin will use the web
base application and create their account with their required information. On web
application unique code will be selected against every subject and admin when
user uses android application he/she will need specific code to register in
relevant field. Unique code will be entered by admin or faculty members.

4.4.1.2 Admin

Admin after registration control two fields (1) Faculty (2) Students. Admin will
post all types of notification of students and faculty. There will be a separate
option for faculty and students notifications. Students and faculty cant be able to
access notification of each other posted by admin. All notes board activity will
perform by admin panel.

4.4.1.3 Faculty

The faculty member will use both application android and web.On the web,
he/she will create an account (sign up). Add new subjects and every subject will
have its unique code. View subjects list. Upload all types of data (assignment,
lecture and announcement). Faculty member by using admin code receive all
types of notification from the admin. Faculty can reply to students comments.
4.4.1.4 Students

The student will get notification from the admin and faculty. Students will need to
select the subject using unique code and download all types of data through
android app. The student also can view marks of related subjects during
semester, view timetable of classes posted by faculty, view date sheet, view
notifications and can add comments.

4.4.2 Nonfunctional Requirements.

Non functional requirement are the requirements that specify criteria that can be used
to judge the operation of a system, rather than specific behaviors.

4.4.2.1 User Friendly

The application interface is user friendly and should facilitate the user using
the application. The interface components should be self-evident.

4.4.2.2 Reliability
Specify the factors required to establish the required reliability of the software
system at the time of delivery.

4.4.2.3 Availability
The system shall be available all the time with internet availability as a web
application and mobile application.

4.4.2.4 Security
Main admin will be able to register all the users (admin, faculty, students). All
the data will be saved on secure .net server which can only be accessed by
developers of this application. Password and personal information of users
shall be secure.

4.4.2.5 Maintainability
The Student Notification system is being developed on Android and web
languages. So its easy to maintain the system new version and functionality
can also be added to this system.
 4.4.2.6 Portability
The Student Notification System can be used on every android mobile and
browser. User can see his/her announcements, simply by installing this
application and sign in with his user name and password using code and get
specific information.

4.4 Development Environment

The hardware requirements for developing the system are listed as below:
IBM PC or Compatible, with Pentium 144 MHz Processor or higher
Minimum 64 MB RAM (512 MB RAM recommended)
4GB hard disk space or higher
VGA or high-resolution monitor
Printer as output devices
Keyboard, Mouse as input devices

The software requirements for developing the system are listed as below:
Microsoft Visual studio 2012
Microsoft SQL Server Management Studio 2012
Windows operating system