Академический Документы
Профессиональный Документы
Культура Документы
1|P ag e
Session
Name
2|P ag e
Table of Contents
1.1
Introduction .............................................................................................................. 6
4|P ag e
Introduction
5|P ag e
1.1 Introduction
The University of Edima there is no any kind of web based system used at the moment.
Now Edima is using, totally a manual system. So it is very difficult to maintain data
methodically. To maintain a proper way, it is important to store Student Details, Lecture
Details, Lecture Rooms, Course Details and Payment details. And also specially University
of Edima has large number of students following many types of courses. Therefore it is really
difficult task to document each and every one of their information, hard to get and keep hard
copies of their projects, difficult to track students attendance and keep the staff information
and records. At the recent moment University need to implement system linked to a relational
database is required where all the students, supervisors and second markers to use a common
e supervision system handle by an authorize person that the based on the given criteria from
the assignment.
Most web based applications are far more compatible across platforms than traditional
installed software. Typically the minimum requirement would be a web browser of which
there are many. (Internet Explorer, Firefox, Dolphin, Opera, Android Web View, iPhone
Safari, to name but a few). These web browsers are available for a multitude of operating
systems and so whether users use Windows, Linux or Mac OS, Android phones & tablets,
iOS we can still run our application.
More manageable
Web based systems need only be installed on the server placing minimal requirements on the
end user workstation. This makes maintaining and updating the system much simpler as
usually it can all be done on the server. Any client updates can be deployed via the web
server with relative ease.
6|P ag e
Highly deployable
Due to the manageability and cross platform support deploying web applications to the end
user is far easier. They are also ideal where bandwidth is limited and the system and data is
remote to the user. At their most deployable you simply need to send the user a website
address to log in to and provide them with internet access.
Typically in larger more complex systems data is stored and moved around separate systems
and data sources. In web based systems these systems and processes can often be
consolidated reducing the need to move data around. Web based applications also provide an
added layer of security by removing the need for the user to have access to the data and back
end servers.
Reduced costs
Web based applications can dramatically lower costs due to reduced support and
maintenance, lower requirements on the end user system and simplified architecture.
1.4 Conclusion
In this chapter first explained about the Edima University and It Current System. Then
Explained about the Proposed System and Benefits of it. Finally think this Web based
applications have come a long way and now offer competitive advantages to traditional
software based systems allowing businesses to consolidate and streamline their systems and
processes and reduce costs.
7|P ag e
8|P ag e
9|P ag e
10 | P a g e
University of Moratuwa
Referred to the site to get an idea of the interface of the system.
11 | P a g e
University of Macquarie
12 | P a g e
Requirement Annalysis
13 | P a g e
3. Requirement Analysis
System development can generally be thought of having two major components: systems
analysis and systems design. In System Analysis more emphasis is given to understanding the
details of an existing system or a proposed one and then deciding whether the proposed
system is desirable or not and whether the existing system needs improvements. Thus, system
analysis is the process of investigating a system, identifying problems, and using the
information to recommend improvements to the system. This chapter describes how to gather
requirements for the development of the system. Also categorize the functional and non
functional requirements from identified features that have to be in the system for university of
Edima.
The contents of the statement of requirements should be stable or change relatively slowly. Once you
have created your statement of requirements, ensure the customer and all other stakeholders sign-up to
it and understand that this and only this will be delivered. Finally, ensure you have cross-referenced
the requirements in the statement of requirements with those in the project definition report to ensure
there is no mismatch.
There are different types of techniques used to gather requirements to develop the system for
university of Edima. Mainly identified the requirements by going through the scenario and
also referred to some similar portals and sites to collect information to develop the system.
Old Documentations
14 | P a g e
15 | P a g e
eSupervision
University of Edima
Mobile Device
MIS System
Student
Second Marker
Supervisor
10 students allocate to
1 supervisor and
second marker
Allocate
supervisor and
second marker
17 | P a g e
Authorized
Member
Student
Second Marker
Supervisor
Registration
Create Credentials
Pay Fees
Supervisor
Project Details
Authorized User
Project Document
Project Comments
Results
Input Marks
Student Attendance
Second Marker
Attend for Meeting
Tutorial Videos
Dump Exams
View Reports
18 | P a g e
Student
Registration
Precondition
Flow of Events
Post Condition
Use Case
Create Credentials
Precondition
Flow of Events
Post Condition
Use Case
Pay fees
Precondition
Flow of Events
Post Condition
19 | P a g e
Use Case
Project Details
Precondition
Flow of Events
Post Condition
Successfully uploaded
Use Case
Results
Precondition
Flow of Events
Post Condition
Use Case
Student Attendance
Precondition
Flow of Events
Post Condition
20 | P a g e
Use Case
Precondition
Flow of Events
Post Condition
Use Case
Tutorial Video
Precondition
Flow of Events
Post Condition
Use Case
Dump Exam
Precondition
Flow of Events
Post Condition
21 | P a g e
Use Case
View Reports
Precondition
Generate reports
Flow of Events
Post Condition
22 | P a g e
Registration
Precondition
Flow of Events
Alternative Path
In step 2, If the type if the user is not selected, It will ask to select
the type.
In step 3, All the details have to be filled up before click update
Post Condition
Use Case
Create Credentials
Precondition
Flow of Events
Alternative Path
Post Condition
23 | P a g e
Use Case
Pay fees
Precondition
Flow of Events
Alternative Path
Post Condition
Use Case
Project Details
Precondition
Flow of Events
Alternative Path
Post Condition
Successfully uploaded
Use Case
Results
Precondition
Flow of Events
Alternative Path
Post Condition
24 | P a g e
Use Case
Student Attendance
Precondition
Flow of Events
Alternative Path
Post Condition
Use Case
Precondition
Flow of Events
Alternative Path
Post Condition
Use Case
Tutorial Video
Precondition
Flow of Events
Alternative Path
Post Condition
25 | P a g e
Use Case
Dump Exam
Precondition
Flow of Events
Alternative Path
Post Condition
Use Case
View Reports
Precondition
Generate reports
Flow of Events
Alternative Path
Post Condition
26 | P a g e
28 | P a g e
29 | P a g e
30 | P a g e
31 | P a g e
32 | P a g e
System Design
33 | P a g e
5.2 ER Diagram
Sup_ID
M_ID
1
A_Date
Play
Supervisor
Meeting
Attendance
1
Record
Conduct
Role_ID
1
1
Play
1
Role
M
Has
Has
User
T_ID
St_ID
User_ID
1
Student
Watch
Tutorial
Play
Submit
1
S_Marker
Write
N
Comment
Add
1
Update Document
Upload
M
Project
S_Marker_ID
Com_ID
34 | P a g e
Doc_ID
Project_ID
Database Designs
Attendance
Comment
Meeting
Message
36 | P a g e
Project
Role
37 | P a g e
Second_Marker
Student
38 | P a g e
Supervisor
University_Blog
39 | P a g e
Upload_document
Users
40 | P a g e
42 | P a g e
43 | P a g e
Meeting Process
44 | P a g e
45 | P a g e
Attendance process
46 | P a g e
47 | P a g e
Meeting process
Attendance Process
50 | P a g e
51 | P a g e
52 | P a g e
Meeting process
53 | P a g e
Mail Process
54 | P a g e
55 | P a g e
Reports Process
56 | P a g e
57 | P a g e
Blog
58 | P a g e
Upload Process
59 | P a g e
Registration
Upload
Upload documents
Student Registration
Upload Assignments
Staff Registration
Reports
Exception Report
Allocation
Allocate by second marker
Managing Report
Meetings
Meetings with student and supervisor
E-mail of Students
Email notification for student
Logo
Link1
New Meeting
Link2
Link3
List of Meeting
Allocated Lectures
Meeting
Meeting
Meeting
Link4
Link5
Mail of Students
Logo
Link1
Link2
New Mail
Link3
Link4
Link5
Link4
Link5
Mail List
Logo
Link1
Link2
Links
View Uploaded
Files
Select Document
Upload
62 | P a g e
Link3
Choose File
Logo
Link1
Link2
Link3
New User
User Name
User Type
Password
Confirm
First Name
Last Name
Email
Tel-No
Register
63 | P a g e
Link4
Link5
Allocation Process
Logo
Link1
Link2
Link3
Allocate
Active
Student ID
Supervisor ID
Second Marker ID
Active
Student ID
Supervisor ID
Second Marker ID
Allocate
64 | P a g e
Link4
Link5
Questions
Logo
Link1
Link2
Link3
Correct Answer
Submit
Choice 1
Clear
65 | P a g e
Link4
Link5
Logo
Link 1
Link 6
Link 2
Link 3
Link 4
Link 5
Link 7
New User
User ID
User Type
Password
Confirm
66 | P a g e
Allocation Process
67 | P a g e
68 | P a g e
Student Panel
69 | P a g e
Second Marker
Supervisor
70 | P a g e
Development Methodologies
71 | P a g e
Development Team
According to Scrums founder, the team is utterly self managing. The development
team is responsible for self organizing to complete work. A Scrum development team
contains about seven fully dedicated members, ideally in one team room protected from
outside distractions.
An agile Scrum process benefits the organization by helping it to
73 | P a g e
System Testing
74 | P a g e
7. What is Testing?
Testing is a process to find whether the provided solution satisfies its requirements. Testing
used to find the gaps between solution and requirement and do the necessary arrangements to
minimize those gaps. During testing errors and missing requirements are found and have to
correct these issues. University of Edima, there are requirements and have to identify gaps
and errors and must correct those errors.
Software Testers, Software Developers, Project Managers and End Users are involved for
testing. Early involvement of testing reduces cost. Testing is a never ending process. No one
can say testing 100% completed. To finalize testing must declare testing deadlines,
completion of test case, high priority bugs are identified and bug rate falls below a certain
level etc.
STEP
EXPECTED RESULT
Status
1.1
OK
2.1
OK
2.2
OK
2.3
OK
2.4
OK
75 | P a g e
displayed
3.1
Display scheduled
Meetings & Supervisor
& Second marker
allocated
OK
3.2
OK
3.3
OK
4.1
OK
4.2
OK
5.1
Click on Uploads
OK
5.2
Uploaded document
OK
5.3
OK
6.1
OK
7.1
Display blog
OK
8.1
Click on Contact Us
OK
9.1
Click on Logout
76 | P a g e
STEP
EXPECTED RESULT
Status
1.1
OK
2.1
OK
2.2
OK
2.3
OK
2.4
OK
3.1
Display scheduled
Meetings & Supervisor
& Second marker
allocated
OK
4.1
OK
4.2
OK
5.1
Click on Uploads
OK
5.2
Uploaded document
OK
5.3
OK
61
Display blog
OK
7.1
Click on Contact Us
OK
8.1
Click on Logout
77 | P a g e
STEP
EXPECTED RESULT
Status
1.1
OK
2.1
OK
2.2
OK
2.3
OK
2.4
OK
3.1
Display scheduled
Meetings & Supervisor
& Second marker
allocated
OK
4.1
OK
4.2
OK
5.1
Click on Uploads
OK
5.2
Uploaded document
OK
5.3
OK
61
Display blog
OK
7.1
Click on Contact Us
OK
8.1
Click on Logout
78 | P a g e
STEP
EXPECTED RESULT
Status
1.1
OK
2.1
OK
2.2
OK
2.3
OK
2.4
OK
3.1
Display scheduled
Meetings & Supervisor
& Second marker
allocated
OK
4.1
OK
4.2
OK
5.1
Click on Uploads
OK
5.2
Uploaded document
OK
5.3
OK
61
Display blog
OK
7.1
Successfully Allocated
Message Appear
OK
7.1
Click on Contact Us
OK
8.1
Click on Logout
80 | P a g e
System Implementation
81 | P a g e
8. System Implementation
8.1 System Implementation Strategies
There are four strategies for implementing a new system
1. Parallel
2. Phased
3. Pilot
4. Direct
Phased is an useful strategy for systems that are made up of smaller sub-systems. The idea is
to introduce each sub-system one at a time.
Pilot is a popular approach when they want to evaluate the performance and qualities of the
system before committing to it throughout the organization.
Direct Implement approach, the system is implemented and tested to ensure it performs
properly. Then the old system is removed and the new one put in its place without any
overlap or limited roll out. And also
This is a risky strategy as any issues with the new system may have an immediate impact on
the day to day activity of the organization.
Among these four strategies we selected parallel for implementing our system. This is a very
popular method as it is relatively low risk. The idea is to run the old system alongside the
new system for a while. With this approach, the outputs or behavior of each system can be
compared to make sure that the new system is performing as expected. If a serious problem is
found, then the Edima can just carry on using the existing system until a fix has been put in
place.
82 | P a g e
83 | P a g e
Critical Appraisals
84 | P a g e
9. Critical Appraisals
9.1 Problems faced
When implementing this system I faced different problem. We run this web site firefox browser
but when sometimes We used google chrome for running the web site completely different the
design such as appearance, font size, colors And also ActiveX disable in firefox so we designed
pages in ActiveX not working. And we used pixels to web page(not using Percentage)completely
design will changed.
Therere lot of web browsers and browser versions using by employees. So the biggest
Problem we faced is producing a same user experience for each users. It was very hard
to support for old technologies.
The Web Socket technology is a great technology to synchronize data between server
and users browser with using only one static connection. This is solves unnecessary
issues and connection latency.
85 | P a g e
86 | P a g e
10. References
Impementation Strategies [online]. (2015). Available from: <http://www.teachict.com/as_a2_ict_new/ocr/A2_G063/335_implementing_systems/methods/miniweb/pg6.
htm>. [Accessed 10 April 2015].
87 | P a g e
88 | P a g e
89 | P a g e
90 | P a g e
Appendix B
Project Management
91 | P a g e
As depicted on above all team members assigned for the each allocated job must contribute
their best effort on the development and all roles are depending on each other. There may be
several roles are allocated for the same person. Because the development divided in small
modules and one person can participate in separate processes.
For the Edima university web application development were five members of a team
in order to achieve intended target within two months of a time period. This process includes
planning to execution of the development in to live environment. The following are the team
member details participate for the development.
User Trainer
End users or the operational staff in the university needs to know about how the operations
need to be handled. Therefore it need to conduct training sessions on user level and
university system need to create recording of functionality of the system and a user manual.
93 | P a g e
Meeting Minutes
Minutes of meeting
Meeting Number: 001
Date: 8/2/2015
Time: 2.00pm-3.30pm
Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:
Mr. Yasiru Identify the entities and the attributes for the database
Solution agreed:
94 | P a g e
Minutes of meeting
Meeting Number: 002
Date: 15/2/2015
Time: 4.00pm-4.30pm
Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:
Solution agreed:
Minutes of meeting
Meeting Number: 003
Date: 22/2/2015
Time: 8.30am-9.00am
Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:
Solution agreed:
96 | P a g e
Minutes of meeting
Meeting Number: 004
Date: 1/3/2015
Time: 8.00am-9.00am
Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:
Mr. Manjula Develop the database and draw use case and ER
diagram
Solution agreed:
97 | P a g e
Minutes of meeting
Meeting Number: 005
Date: 8/3/2015
Time: 4.00pm-4.30pm
Participants:
1. Mr. J.L.T Manjula De Silva
2. Mr. Yasiru Edirisingha
3. Mr. Dilan
4. Ms.Ireni Hansika
5. Mr.Indika Rathnayaka
Main things had been focused:
Mr. Manjula & Dilan Continue developing the system and draw
sequence diagram
Solution agreed:
98 | P a g e
End Date
Deliverables
8/2/2015
14/2/2015
15/2/2015
21/2/2015
22/2/2015
28/2/2015
1/3/2015
7/3/2015
8/3/2015
14/3/2015
99 | P a g e
100 | P a g e
Meeting Process
Mail Process
Dispaly Inbox
Request Date
Compose
Send mail
102 | P a g e
Blog
103 | P a g e
Password: 1111
Password: 12345678
Note-: A student account can be created by entering valid user ID with integer value along
with other relevant information. When logging into the system the student has to add s in
front of the integer user ID
Example
User ID, When creating the account: 1001
User ID, When login to the website: s1001
Password: 12345678
Note-: A supervisor account can be created by entering valid user ID with integer value along
with other relevant information. When logging into the system the supervisor has to add p
in front of the integer user ID
Example
User ID, When creating the account: 50
User ID, When login to the website: p50
Every user should have unique user ID and email address when creating an account
104 | P a g e
1.
a.
Password : 1111
105 | P a g e
106 | P a g e
a.
Enter mail address for To field, then enter title and Message and click on send.
107 | P a g e
108 | P a g e
8.
109 | P a g e
a.
110 | P a g e
a.
Enter Name, E-mail, Mobile, & subject and click Submit will register a student to
receive new updates and activities.
111 | P a g e
11.
12.
112 | P a g e
13.
113 | P a g e
114 | P a g e
Online registration
Question page
116 | P a g e
117 | P a g e
118 | P a g e
119 | P a g e
120 | P a g e
121 | P a g e
122 | P a g e
123 | P a g e
125 | P a g e
After Click the View Uploaded File Link Then Display This Section
Then You can get more details such as Doc ID, Doc Name and who are the uploaded
relevant one as follows
https://www.youtube.com/watch?v=3cpNuJJRkJA&feature=youtu.be
15 .Video Cast of the System
127 | P a g e
128 | P a g e
if( create_meeting())
{
$report = "Meeting was scheduled.";
}
}
?>
<div class="wrap"><div class="wrapper">
</select>
</div>
<div class="row">
<label>Meeting Time</label>
<select name="hour">
<?php for($i = 0 ; $i < 24; $i++ ){ ?>
<option value="<?php echo $i?>"><?php printf( "%02d", $i); ?></option>
<?php }?>
</select>
<select name="minute">
<?php for($i = 0 ; $i < 60; $i++ ){ ?>
<option value="<?php echo $i?>"><?php printf( "%02d", $i); ?></option>
<?php }?>
</select>
</div>
<div class="row">
<label>Description</label>
<textarea required="true" name="Description" rows="8"
maxlength="200"></textarea>
</div>
<div class="row">
<input type="submit" name="submit" value="Create" />
</div>
</form>
</div>
<br style="clear:both" />
</div></div>
<?php
include 'bottom.inc';
?>
131 | P a g e
global $num_qs;
for($q = 1 ; $q <= $num_qs ; $q++)
{
$question = addslashes( strip_tags($_POST['question' . $q]));
$answers = $_POST['answer' . $q];
$correct = $_POST['correct_' . $q];
//Stripping all answers
foreach($answers as $k => $v)
{
$answers[$k] = addslashes(strip_tags($v));
}
if(empty($question) || empty($correct) || empty($answers[0]) ||
empty($answers[1]) || empty($answers[2]) || empty($answers[3]) )
{
return false ; // Empty values sent
}
$sql = "INSERT INTO mcq_list(mcq_id,idx,question,ans1,ans2,ans3,ans4,correct)
VALUES('$q_id','$q','$question','{$answers[0]}' ,'{$answers[1]}'
,'{$answers[2]}' ,'{$answers[3]}'
,'$correct')";
$results = $con->query($sql);
if(!$results || $con->affected_rows ==0 )
return false;
}
return true;
}
132 | P a g e
}
?>
<style>
.form
{
width:60%;
margin-left: 10% !important;
}
.mcq textarea
{
width:80%;
}
133 | P a g e
.mcq div
{
padding:5px;
margin-top:10px;
}
.mcq h6
{
font-weight: bold;
}
.mcq span
{
font-weight: bold;
}
.mcq .answers
{
line-height: 2;
}
.mcq .answers input
{
display: inline-block;
width: 80%;
}
</style>
<div class="wrap">
<div class="wrapper questions form">
<?php
//Display error messages
if(isset($error)){ ?>
<div class="error-message"><?php echo $error ?></div>
<?php } ?>
<?php
//Sucess message
if(isset($_SESSION['report'])){ ?>
<div class="info-message"><?php echo $_SESSION['report'];
unset($_SESSION['report']); ?></div>
<?php } ?>
<h6>MCQ Title</h6>
<input type='text' id="title" required='required' value="<?php echo @$_POST['title']
?>" style="width: 80%;" name="title" />
<?php for($i = 1 ; $i <= $num_qs ; $i++) {
?>
<div class="mcq row">
<p><span>Question <?php echo $i?>.</span><br />
<textarea required="required" name="question<?php echo $i ?>"
id="question_<?php echo $i?>"><?php
echo @$_POST['question' . $i]?></textarea>
</p>
<div class="answers">
<h6>Answers</h6>
1. <input required="required"
value='<?php echo @$_POST['answer'.$i][0] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_1" /><br />
2. <input required="required"
value='<?php echo @$_POST['answer'.$i][1] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_2" /><br />
3. <input required="required"
value='<?php echo @$_POST['answer'.$i][2] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_3" /><br />
4. <input required="required"
value='<?php echo @$_POST['answer'.$i][3] ?>' type="text"
name="answer<?php echo $i?>[]" id="answer_<?php echo $i?>_4" /><br />
</div>
<div>
<span>Correct Answer</span>
<select name="correct_<?php echo $i ?>">
<?php for($j = 1 ; $j <=4 ; $j++) { ?>
<option <?php if(@$_POST['correct'] == $j) echo "selected='selected'"; ?>
value="<?php echo $j?>">Choice <?php echo $j?></option>
<?php }?>
</select>
</div>
</div>
<?php
}?>
<div class="row">
<input type="submit" name="submit" value="Submit" />
<input type="reset" value="Clear" />
</div>
</form>
</div>
135 | P a g e
</div>
<script>
function onSubmit()
{
try
{
var e = document.getElementById('title');
if(e.value.trim() == "")
{
alert('Title is empty');
return false;
}
}
</script>
<br class="clear" />
<?php require 'bottom.inc' ; ?>
137 | P a g e
Sample coding
Lecturer
<?php
require 'top.inc';
?>
<script>
jQuery(function(){
jQuery('#camera_wrap_4').camera({
height: 'auto',
loader: 'bar',
pagination: false,
thumbnails: true,
hover: false,
opacityOnGrid: false,
imagePath: '../images/'
});
});
</script>
<script type='text/javascript' src="../js/camera.min.js"></script>
<link property='stylesheet' href="../css/camera.css" rel="stylesheet" type="text/css"
media="all" />
<div class="fluid_container">
<div class="camera_wrap camera_emboss pattern_1" id="camera_wrap_4">
<div data-src="../images/slider1.jpg"> </div>
<div data-src="../images/slider2.jpg"> </div>
<div data-src="../images/slider3.jpg"> </div>
</div>
</div>
<div class="clear"></div>
<div class="wrap">
<div class="wrapper">
<h3>Meetings</h3>
<div class="section group">
<?php //Load most recent meetings , 4 Max
$user_id = $_SESSION['user_id'];
$sql = " SELECT A.* , U.Full_Name FROM (SELECT * FROM meeting
WHERE Sup_ID='$user_id' OR
138 | P a g e
139 | P a g e
Staff
<?php
include 'top.inc';
?>
<script>
jQuery(function(){
jQuery('#camera_wrap_4').camera({
height: 'auto',
loader: 'bar',
pagination: false,
thumbnails: true,
hover: false,
opacityOnGrid: false,
imagePath: '../images/'
});
});
</script>
<script type='text/javascript' src="../js/camera.min.js"></script>
<link property='stylesheet' href="../css/camera.css" rel="stylesheet" type="text/css"
media="all" />
<div class="fluid_container">
<div class="camera_wrap camera_emboss pattern_1" id="camera_wrap_4">
<div data-src="../images/slider1.jpg"> </div>
<div data-src="../images/slider2.jpg"> </div>
<div data-src="../images/slider3.jpg"> </div>
</div>
</div>
<div class="clear"></div>
<?php
include 'bottom.inc';
?>
140 | P a g e
Student
<?php
include 'top.inc'
?>
<script>
jQuery(function(){
jQuery('#camera_wrap_4').camera({
height: 'auto',
loader: 'bar',
pagination: false,
thumbnails: true,
hover: false,
opacityOnGrid: false,
imagePath: '../images/'
});
});
</script>
<script type='text/javascript' src="../js/camera.min.js"></script>
<link property='stylesheet' href="../css/camera.css" rel="stylesheet" type="text/css"
media="all" />
<div class="fluid_container">
<div class="camera_wrap camera_emboss pattern_1" id="camera_wrap_4">
<div data-src="../images/slider1.jpg"> </div>
<div data-src="../images/slider2.jpg"> </div>
<div data-src="../images/slider3.jpg"> </div>
</div>
</div>
<div class="clear"></div>
<div class="wrap">
<div class="wrapper">
<div class="main_text">
<h2>A place of light, of liberty, and learning</h2>
<h3>we provide leading intensive courses</h3>
</div>
</div>
</div>
<div class="wrap">
<div class="wrapper">
<h2>Meetings</h2>
<div class="section group">
141 | P a g e
<?php
include 'bottom.inc';
?>
142 | P a g e
Conclusion
In the first chapter weve basically talked about the project how were going to develop.
Also weve identified the requirement of a new system, organization status and achieving
objectives. Second chapter we discussed about the problems of current system and what kind
of system weve to develop to overcome those issues. In the third chapter, we discussed about
the requirement Catalogue. Requirements Definition is probably the most important
technique in Structured Analysis. It is the only technique that Permeates every step of the
method. In the fourth step, a software requirements specification (SRS) is a comprehensive
description of the intended purpose and environment for software under development. Weve
drawn use-case diagrams of the current system to clearly visualize the processes identified.
In the chapter 5, weve done Data modeling, System modeling. First we identified system
developed methodologies needed and coding architectures and structures available to develop
a maintainable and scalable web based application. According to architectures weve select,
weve drawn architecture diagrams for our application. Then weve normalized the data
analyzed in the previous chapter for create a relation database model. According with
normalized data, weve drawn the Entity Relationship Diagram, data dictionaries & relation
templates for the system. Class diagrams, activity diagrams, sequence diagrams & state
transition diagrams are drawn to plan the flow of our system. In the sixth chapter,
weve prototyped our web pages with story board, wireframes & GUI to show our customer
for feedback. The system development phase discussed in the chapter 6. There we have list
down all the sprints description, sprint plan & development issues. In the chapter 7, weve
done our user interface coding and back-end/front-end development parts along with testing.
Weve also discussed about the software testing and testing types and showed the strategy to
test our application. In the chapter 8, we discussed about the implementation part. We chose
an implementation method for our new system from among 04 system implementation
strategies. Then we talked about the system configuration and installation processes. Finally,
we given a maintain tasks to keep our system healthy and risk free. Finally in chapter 9,
weve evaluate our whole process and product weve developed. Identified weakness of our
system. Talked about problems we got and how to face them. Through that we have
discussed the lessons we learned. Future enhancements also suggested to improving the
application and making it more usable.
In conclusion this document provides the overall knowledge about the web based system. So
this gave a clear impression that web based system is more important than a manual system.
143 | P a g e
148 | P a g e
149 | P a g e