B.

Sc (Business Information Technology) Special Degree

Course: System Analysis & Design
(ITM 2233)

Under the supervision of

Mr.P.G.Munasinghe

Department of Business Information Technology.

Faculty of Management Studies.
Rajarata University of Sri Lanka.
Mihinthale.
 DETAILS OF STUDENTS

Name Registration No. Date

D.P.P.Perera MGT/14/15/196

R.G.L.S.Rambukwella MGT/14/15/215

E.A.N.Sandamali MGT/14/15/240

L.H.M.G.I.Wikramaraththana MGT/14/15/293

K.W.W.M.S.D.Wijekoon MGT/14/15/301
 Organization Profile

Rajarata University of Sri Lanka , located in the historic city of Mihintale, which is situated 14
kilometres away from the east of Anuradhapura, was established on 31 of January, 1996. It
envisages to highlight the city, Mihintale, which marks the inception of the Sri Lankan social
development, as one of the most prominent centre of the present academic arena in the Sri
Lankan history. Through this, it is expected to produce virtuous, intellectual and competent
citizens for the needs of the 21 st century.

At the beginning there were four faculties namely Faculty of Social Sciences and Humanities,
Faculty of Management Studies, Faculty of Agriculture and Faculty of Applied Sciences were
established and in the year 2006, the Faculty of Medicine and Applied Sciences was established
as the fifth faculty of Rajarata University of Sri Lanka. The faculties of Social Sciences and
Humanities, Faculty of Management Studies and Faculty of Applied Sciences are conveniently
located in the Mihintale premises while the Faculties of Agriculture and Medicine and Allied
Sciences are situated in Puliyankulama and Saliyapura respectively.

During the past twenty years, the contribution made to tertiary education by Rajarata University
of Sri Lanka is immense.
Current Situation of the organization

 Existing system is highly depend on the manual based excel related system and it will
causes lots of errors occurred in the system and it’s very hard to handle.

 Current process has less security and it causes troubles when unauthorized persons
can access to the information, it’s difficult to work with that process.

 Historical data easily can be destroyed, stolen and use for unauthorized purposes.

 Manual process can be cause in difficulties of delete update and view data. In addition
the manual process is unstructured and due to this problem immediate updating of data
is not offered & this makes it difficult to make quick managerial decisions.

 There is no sufficient features to manipulate data in a proper way. Information can be

scattered, redundant and collecting relevant information may be very time consuming.

 Finally the organization needs to design a software solution to maintain in relation to

the information about examine result as a solution for a current situation
 Object of the Project

 The object of this project is to create a Student Result System to store the Name, Index
Number, Department, NIC, Marks, year & Semester of different student by a linear
structure using Java programming.
 In this software one can very easily add student's record, sort student's record, search

student's record, compute (using algorithms), and view all student's records.

 This application stand out among all others software in a way that it is user friendly and

can be modified easily as per the requirements. It allows user to add new/

view/sort/search records.

 There is opportunity to view results online.

 In this can make reports important to decision makers.

 Both of workers can appear as admins & both of them can entry results.

 When the results are release admin send a message to the students.
 User Requirements

There are two type of users.

 Admin : Requirements ,
o Student Registration.
o Manage Student.
o Manage Subject.
o Manage Marks.
o System login.
o Test.
o Report.

 Student : Requirements,

o Student Registration.
o System login.
o Test.
o View Result.
 View result

Student Registration

Manage Student

Manage Subject

Manage Marks

Student Admin
System Login

Test

Reports
 Methodology

Analysis Tools

1. Interviews

The details necessary to understand processes or product needs are usually in

the heads of the staff of the examination unit. The only way to mine this
information from the is to talk with them and we identified the system
requirements. Interviews should be focused, with a prepared list of questions or
concepts to be discussed. Document each interview by recording it using a small
digital recorder or summarize the conversation immediately after it is
completed.

2. Use Cases

Short narratives describing how a product will be used, limited to a few

paragraphs, often helps analysts and customers refine product features. Refine
these narratives throughout the analysis phase. These use cases can be used
throughout the project life cycle, especially during testing.

3. Requirements Lists

When designing this project, it is helpful to keep a running list of requirements.

These should be presented as a list or in outline form, organized by categories.
As the list grows, this list helps the analyst understand the organization’s needs
and helps limit what features are necessary and which are not.

Design Tools

1. Flowcharts

Flowcharts come in many varieties and under many names, but the basic
concept is to take a process and describe it as a diagram. Whether presented as
a process flow chart or an Entity/Relation diagram, the drawing helps the
analyst describe a series of steps or decisions in visual form in a manner that
facilitates communication.

2. Prototypes

A model or prototype can turn a group of ideas into solid

form. Software engineers often hear the statement “I’ll know what I want when
I see it” and a model or prototype can facilitate these issues. By presenting a
prototype, the analysts gather features that work and open discussion on other
features and improvements.
 3. DFD

DFD is a designing tool used in the top-down approach to Systems Design. This
context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how
the system is divided into sub-systems (processes).

Implementation tool

1. NetBeans

NetBeans is a software development platform written in Java.

The NetBeans Platform allows applications to be developed from a set of
modular software components called modules. Applications based on
the NetBeans Platform, including the NetBeans integrated development
environment (IDE), can be extended by third party developers.

2. MySQL Worckbench

MySQL Workbench enables a DBA, developer, or data architect to visually

design, model, generate, and manage databases. It includes everything a data
modeler needs for creating complex ER models, forward and reverse
engineering, and also delivers key features for performing difficult change
management and documentation tasks that normally require much time and
effort.

3. PHP
PHP is a server-side scripting language designed for web development but
also used as a general-purpose programming language. Originally created
by Rasmus Lerdorf in 1994, the PHP reference implementation is now
produced by The PHP Group. PHP originally stood for Personal Home
Page,[3] but it now stands for the recursive backronym PHP.PHP code may be
embedded into HTML code, or it can be used in combination with various web
template systems, web content management systems, and web frameworks.
 Time Schedule
 Project Activities and Time Durations

Task Name Start Finish Duration

Initiating Tue 12/12/17 Tue 1/13/18 31
Study of the Organization Tue 12/12/17 Fri 12/15/17 3
Identify the Problem Sat 12/16/17 Wed 12/20/17 4
Create the Solution & Identify Project 6
Thu 12/21/17 Wed 12/27/17
Objectives
Finalize the project Proposal & 10
Thu 12/28/17 Mon 1/8/18
Proposal Submission
Initiating Completed Tue 1/9/18 Sat 1/13/18 4
Planning Sun 1/14/18 Sat 1/29/18 25
Planning Requirements Sun 1/14/18 Tue 1/20/18 16
Create priority order of the 4
Wed 1/21/18 Fri 1/25/18
Requirements
Create & present Project Mid 4
Sati 1/26/18 Sat 1/29/18
Presentation
Executing Sat 1/30/18 Sun 2/26/18 26
Database and Interface Designing Sat 1/30/18 Fri 2/10/18 10
Start and Continuing Coding Process Wed 2/10/18 Wed 2/21/18 11
Testing and Debugging Thu 2/22/18 Sat 2/24/18 3
Submission of the Draft Version of the 2
Sat 2/25/18 Sun 2/26/18
Project Report & Final Presentation
Controlling Mon 2/27/18 Fri 3/6/18 9
Monitoring and Controlling Mon 2/27/18 Fri 3/6/18 9
Closing Sun 3/7/18 Tue 4/27/18 50
Complete the Final version of the 45
Sat 3/7/18 Thu 4/22/18
System
Submission of the Final Version of the
Fri 4/23/18 Tue 4/27/18
Project Report 4
 Grantt Chart
12/12 1/1 1/21 2/10 3/2 3/22 4/11 5/1 5/21

Initiating

Planning

Executing

Controlling

Closing

Closing Controlling Executing Planning Initiating

START DATE 3/7/18 2/27/18 1/30/18 1/14/18 12/12/17
DURATION (days) 50 9 26 15 31