SMART ROUTINE MANAGEMENT SYSTEM

SUBMITTED BY:
MD. ZILLUR RAHMAN
ID: 142 – 35 – 726
MD. READUL ISLAM
ID: 142 – 35 – 698

SUPERVISED BY:
DR. MD. MOSTAFIJUR RAHMAN

ASSISTANT PROFESSOR

DEPARTMENT OF SWE

DAFFODIL INTERNATIONAL UNIVERSITY

@ Daffodil international university

i
ii
@ Daffodil international university
iii
@ Daffodil international university
 ACKNOWLEDGEMENT

In this project, we would like to fast the thankfulness and gratefulness to all those who give

us the possibility to make our project and project documentation more actual. A special

thanks goes to our supervisor as well as honorable teacher “Dr.Md.MostafijurRahman”whose

help imitation and inspiration us to manage our project particularly writing this document.

We also would like to thanks to our friend “Md.Noyon” who help us to complete our project

in different process.

From our sincere thanks to friends who have supported our work on the project. Specially

Daffodil international university family member, friends and brothers for their valuable and

important ideas.

Finally, and overhead all we would like to thank ourparents and friends for their mental

support. I wouldn’t have been able to get here without them.

iv
@ Daffodil international university
Table ofContents
Approval………………………………………………………………………………………I
Declaration……………………………………………………………………………………ii
Acknowledgement…………………………………………………………………………...iii
Table of Contents……………………………………………………………………..............iv
List of Figures ..................................................................................................................... vii
Chapter 1: introduction.......................................................................................................... 1
1.1 Project Overview ..................................................................................................................... 1
1.2 Project Purpose ........................................................................................................................ 1
1.2.1 Background...................................................................................................................... .2
1.2.2 Benefits & beneficiaries ................................................................................................. .2
1.2.3 Project Goals ..................................................................................................................... 2
1.3 Stakeholders ............................................................................................................................ 3
1.4 Project Schedule ...................................................................................................................... 3
Chapter 2: Software Requirement Specification .................................................................... 4
2.1 Functional Requirement ........................................................................................................... 4
2.2 Performance Requirements ...................................................................................................... 6
2.2.1 Speed and Latency Requirements ...................................................................................... 6
2.2.2 Capacity Requirements...................................................................................................... 6
2.3 Dependability Requirements .................................................................................................... 6
2.3.1 Reliability and Availability ............................................................................................... 7
2.3.2 Robustness and Fault Tolerance Requirements .................................................................. 7
2.3.3 Safety Critical Requirements ............................................................................................. 7
2.4 Maintainability and Supportability ........................................................................................... 8
2.4.1 Maintenance Requirements ............................................................................................... 8
2.4.2 Supportability Requirements ............................................................................................. 8
2.5 Security Requirements ............................................................................................................. 9
2.5.1 Access Requirements ........................................................................................................ 9
2.5.2 Integrity Requirements .................................................................................................... 10
2.5.3 Privacy Requirements ..................................................................................................... 10
2.6 Usability and Human Integrity Requirements ......................................................................... 10
2.6.1 Ease of Use Requirements ............................................................................................... 11
2.6.2 Understand-ability and Politeness Requirements.............................................................. 11
2.6.3 Accessibility Requirements ............................................................................................. 11
2.6.4 User Documentation........................................................................................................ 12

v
@ Daffodil international university
 2.7 Look and Feel Requirements .................................................................................................. 12
2.7.1 Appearance Requirements ............................................................................................... 12
2.7.2 Style Requirements ......................................................................................................... 13
2.8 Operational and Environmental Requirements ........................................................................ 13
2.8.1 Release Requirements ..................................................................................................... 13
2.9 Legal Requirements ............................................................................................................... 13
Chapter 3: System Analysis ................................................................................................. 14
3.1 Use Case Diagram ................................................................................................................. 14
3.2 Use Case Description (Brief).................................................................................................. 15
3.3 Activity Diagram ................................................................................................................... 15
3.3.1 Teacher Activity.............................................................................................................. 16
3.3.2 Student Activity .............................................................................................................. 16
3.3.3 Admin Activity ............................................................................................................... 17
3.4 System Sequence Diagram ..................................................................................................... 17
3.4.1 System Sequence Diagram Teacher ................................................................................. 18
3.4.2 System Sequence Diagram Student.................................................................................. 19
3.4.3 System Sequence Diagram Admin................................................................................... 20
Chapter 4: System Design Specification .............................................................................. 21
4.1 Sequence diagram .................................................................................................................. 21
4.1.1 Sequence diagram for teacher system .............................................................................. 21
4.1.2 Sequence diagram for student system .............................................................................. 22
4.1.3 Sequence diagram for admin system ................................................................................ 23
4.2 Database Design .................................................................................................................... 23
4.2.1 E-R Diagram ................................................................................................................... 24
4.3 Development Tools & Technology ......................................................................................... 24
4.3.1 User Interface Technology .............................................................................................. 24
4.3.1.1 Programming Language ............................................................................................... 25
4.3.1.2 JavaScript and jQuery Library ...................................................................................... 25
4.3.1.3 CSS Framework ........................................................................................................... 26
4.3.1.4 Twitter Bootstrap ......................................................................................................... 26
4.3.2 Implemented Tools and Platform ..................................................................................... 27
4.3.2.1 Web Server .................................................................................................................. 27
4.3.2.2 Database Server............................................................................................................ 27
Chapter 5: System Testing................................................................................................... 28
5.1 Testing Features ..................................................................................................................... 28

vi
@ Daffodil international university
 5.1.1 Features to be tested ........................................................................................................ 28
5.1.2 Features not to be tested .................................................................................................. 29
5.2 Testing Strategy ..................................................................................................................... 29
5.2.1 Test Approach ................................................................................................................. 29
5.2.1.1 Black Box Testing ........................................................................................................ 29
5.2.1.2 White Box Testing ....................................................................................................... 30
5.2.2 Pass/Fail Criteria ............................................................................................................. 30
5.2.3 Testing Schedule ............................................................................................................. 30
5.2.4 Trace Ability Matrix ....................................................................................................... 31
5.3 Testing Environment .............................................................................................................. 32
5.4 Test Cases.............................................................................................................................. 32
5.4.1 Login .............................................................................................................................. 33
5.4.2 Modify Result ................................................................................................................. 33
Chapter 6: User Manual ...................................................................................................... 34
6.1 User Menu ............................................................................................................................. 34
6.2 Teacher Registration page ...................................................................................................... 35
6.3 Teacher login Page................................................................................................................. 36
6.4 Student login Page ................................................................................................................. 37
6.5 Search Page for Student ......................................................................................................... 37
6.6 Search Page for Teacher......................................................................................................... 38
Chapter 7: Conclusion ......................................................................................................... 39
7.1 project summary .................................................................................................................... 39
7.2 Limitations ............................................................................................................................ 39
7.3 Obstacles and Achievements .................................................................................................. 39
7.4 Further development ........................................................................................................... 40

vii
@ Daffodil international university
Figure 3.1 – Use Case Diagram for Class routine management System................................22

Figure 3.2 –Teacher Activity Diagram for Class routine management System.....................24

Figure 3.3 – Student Activity Diagram for Class routine management System.....................24

Figure 3.4 – Admin Activity Diagram for Class routine management System.......................25

Figure 3.5 – System sequence Diagram for Teacher…….………..........................................26

Figure 3.6 – System sequence Diagram for student ...…………..….......................................27

Figure 3.7 – System sequence Diagram for admin ………………………….........................28

Figure 4.1 – Sequence Diagram for Teacher………………………………….......................30

Figure 4.2 – Sequence Diagram for Student...………………..………...................................31

Figure 4.3 – Sequence Diagram for Admin.……………..……………..................................32

Figure 4.4 – Database Design Diagram ...………………….…………................................... 33

viii
@ Daffodil international university
Chapter 1: introduction

1.1 Project Overview

The objective of this document is to fold and examine and give an in-depth vision of the

comprehensiveclass routine management System by important the problem statement in part.

We examined and applied an automatic information system for achieve class routine for our

department. Our planned system makes informal to use the manual system. It will be able to

achieve class schedule of the department by modern computer. It will help to provide all the

information of the class schedule and status of the department in a quicker process

successfully. Our project may be used as a model for the entire department.

1.2 Project Purpose

The determination of the document is to gather and examine all mixedthoughts that have

come up to describe the system, its requirements with respect toteachers and students. Also,

we shall forecast and category out how we confidence this system will be used in order to

improvement a better understanding of the project, planideas that may be advanced later, and

document ideas that are being careful, but may be cast-off as the system grows.

In little, the determination of this SRS document is to deliver a thorough overview of our

software product, its limits and goalmouths. This document labels the system and its

companion’s members and its user interface, hardware and software requirements. It

describes how admin, teachers and studentsunderstand the system and its functionality.

However, it supports any designer and developer to contribution in software delivery

lifecycle (SDLC) processes.

@ Daffodil international university

1
1.2.1 Background

Academic class routine is the key to a well-managed, organized classroom. Routines

permitstudents to rapidlyachieveeverydayresponsibilities that are obligatory of together the

teacher and students. Routinethatrequirescommunicationamong teacher and student that a

search option for both system users. Here also have a class cancel option for teacher and

email to all the teachers. Also have option for identify overlap class, add extra class option,

search empty class room and last have an option for print the document .Our project have

different option that is automatic time update in Ramadan month. Finally our project may be

used as a model for the entire department.

1.2.2 Benefits & beneficiaries

Routines agree students to fastfinishcommonplaceerrands that are obligatory of both the

teacher and students. There are huge benefits of our project system and benefits get both

students and teachers. Benefits of this project is that a search option for students and teachers,

class cancel option for teachers, extra search option for empty room, identify overlap class

and can add extra class. The projects have extra fantastic benefit that is automatic time update

in Ramadan month. Finally have a document print option that student or teacher can print the

document. The system beneficiaries are students and teachers.

1.2.3 Project Goals

2
@ Daffodil international university
The main objective is of our class routine features for making DIU class routine management

system. It focuses on the project is to find out the limitation of the current class routine

management system in SWE, DIU from the both side of the lecturers & students.

1.3 Stakeholders

Renderingtowards the Project Management Institute (PMI),project stakeholder mentions to,

"aseparate, group, or organization, who mighttouch, be pretentious by, or observehimself to

be pretentious by a choice, action, or consequence of a project”.Stakeholdersof this project

are students, teachers and admin which staysinclude in our project system.

1.4 Project Schedule

There is a six-month timeframe to implement class routine management system in SWE, DIU

from the both side of the lecturers & students that the project commencement in time for

spring 2018.

3
@ Daffodil international university
Chapter 2: Software Requirement Specification

2.1 Functional Requirement

The Functional Requirements Specification is intended to be read by aoverallspectators.

Bookloversmustcomprehend the scheme, but no specificmechanicalinformationmust be

obligatory to recognize the document.

FR-01 Member Information

Description This module helps admin to register of class routine management
system members. Admin is able to maintain all the information of
register of class routine management system members
Stakeholders Admin

FR-02 Update System Details

Description This module helps admin to update teachers and students
information. Teachers can also update their some important
information and store these details in database.
Stakeholders Admin, Teacher

FR-03 Login system

Description Teacher must have a login option. Admin never give permission
any teacher if they go through into the login option.
Stakeholders Admin, Teacher

4
@ Daffodil international university
FR-04 Search option
Description Search option for teachers and students for find out their own class
routine and other purpose.
Stakeholders Teacher, Student

FR-05 Class cancel option

Description Why he/she cancel the class? After that when he/she take the class?
Details of class room. After cancel the class email all the teachers.
After complete all the section, then see the print option.
Stakeholders Teacher

FR-06 Extra class /makeup class

Description For extra class/makeup class teachers need to booking system. For
that need to book class room and manage time slot.
Stakeholders Teacher

FR-07 Overlap class

Description See the details of overlap class that include when take the overlap
class and which room number?
Stakeholders Student

FR-08 Makeup class & Extra class

Description This system is used to see the details of makeup class & Extra class
that when, where and which subject is taken by their teacher and
notify to all the students.
Stakeholders Student

5
@ Daffodil international university
2.2 Performance Requirements

A condition that stipulates a presentationdistinctive that a scheme or scheme

orschemeconstituent must processforinstance, speed, accuracy, frequency.

2.2.1 Speed and Latency Requirements

The structure is required a reasonablequantity of speed particularlythoughglancing the

system.

PR-01 The Landing page will response within a second

Description While the user’s browsing the system the landing page will show
within a second. It also depends on user’s internet connection.
Stakeholders Admin, Teacher and student

2.2.2 Capacity Requirements

The structureremainstalented to achievealtogether the evidence of passed out students.

PR-02 Initially this system will store minimum 20,000 student and
teacher information
Description The information of student and teachers will be stored in
database.
Stakeholders Admin, teacher and student

2.3 Dependability Requirements

Dependability requirement includes reliability, safety, security and availability but the main

topic is reliability. Therefore, these requirements are essentials.

6
@ Daffodil international university
2.3.1 Reliability and Availability

In instruction to fundingworldwide and flatprocesses of thisstructure must be accessibleround

the clock. Insteadmaximumfacilities in this system are not assignment-dangerous.

DR-01 The system must remainaccessible 24x7

Description  The system must remain accessible 24 hours in a day
 The system must be updated regularly
 The system must publish the notice, events and job
posting and update these regularly

Stakeholders Admin, teacher and student

2.3.2 Robustness and Fault Tolerance Requirements

The system will almost ensure 0% crush in any single minor error and don’t give any wrong

calculation.

DR-02 The system handles over access and system errors

Description Sometimes multiple users can over access to this system. The
system can handle multiple user access
Description N/A

2.3.3 Safety Critical Requirements

Thereis no exact safety critical requirements .Because there is no conceivableharm,

destruction, or damage that mightconsequence from the procedure of the invention. If some

problem occurs then protections or movements that must be taken, in addition tomovements

that must be preventing.

7
@ Daffodil international university
2.4 Maintainability and Supportability

Supportability is the grade to which system design features and deliberate logistics

incomesencounter system necessities. Supportability is the ability of a total system design to

support processes and willingnesswantsthrough the life-cycle of a system at an

inexpensivecharge.

2.4.1 Maintenance Requirements

MS-01 The system helps to update any information in any time

Description The admin and teacher can post any events and can enable to
change or update any information in any situation if they need.
Stakeholders Admin and teacher

2.4.2 Supportability Requirements

So that understands the structure's behavior on a methodologicalprovision required by the

structureworker. The aim for interpretation they might be

 Structurefault has happened and the structureworker has to catch the strictfact

of time when this occurred.

 Structurecropsincorrectconsequences and the designers must be talented to

copy the data movementfinished the structure.

 Hacker strained to opening the scheme's security devices and the

schemeworker must comprehend what he did

8
@ Daffodil international university
2.5 Security Requirements

There is no access requirements beside those that have been drew in the below:

 The software essential validate all user input to safeguard it does not surpass

the scopestated for that kind of effort

 The waiter must validateeachappealretrieving the limited Web pages

 Afterwardvalidating the browser, the waiter must control whether that browser

is official to access the demandedlimited Web pages

 The scheme must have security panels to defendin contradiction

ofrenunciation-of-service bouts

 The scheme must encrypt subtle data conveyed over the Internet among the

server and the browser

To get access to this system or a specific module the system must provide a central

authentication mechanism. So as tostopanybody to feattaken all users password must be

encrypted in hash process.

2.5.1 Access Requirements

To get access to the system, the system provides authorization/authentication way. This

system uses various modules.

SR-01 The system provides security strategies.

Description The system is intended in method that permits all units to
access a device that delivers security services.
Stakeholders Admin , teacher and student

9
@ Daffodil international university
2.5.2 Integrity Requirements

To protect credentials of user from being stolen, all passwords are stored in encrypted form.

The Requirements significantly decreases the price of taken user identifications, it’s not

informal to decrypt the password.

2.5.3 Privacy Requirements

The system provides a defense of the database in the server. Though, the system will have to

increase this level of defensesince of the individual data mode obtainable on the system & the

superiorpart of persons that will be having admission to it finished the system’s login. The

user’s confidentiality will be decided by the incompleteadmission that the log in procedure is

successful to stretch to the database.

SR-02 All data will be protected

Description The keycondition in the setting is the teachers and students
data for examination.
Stakeholders Admin , teacher and student

2.6 Usability and Human Integrity Requirements

These Requirements describein what way to see the corporeal and reasoningwants of the

envisioned users of your website or application.

10
@ Daffodil international university
2.6.1 Ease of Use Requirements

The system is easy to use and can easily be understandable.

UH-01 The system must be usable for students and teachers.

Description The system indicates the numerouspotentials that the
teachers and students have to drive on in using the system.
The alumni members are allowable to unfasten any of the
process. Admin and teacher are allowed to undo any of the
operation.
Stakeholders Admin , teacher and student

2.6.2 Understand-ability and Politeness Requirements

This section describes more requirements of DIU class routine management system to add

more features in future –

UH-02 The features of DIU class routine management System

Description The system is more efficiently ease of use more added
features .The system is understand-ability for both user. The
system will not use any term that is not specified in this
system
Stakeholders Admin

2.6.3 Accessibility Requirements

There are no entrée requirements beside those that have been drew in the below:

AR-1: Log in as a Admin

AR-2: Log in as a teacher

AR-4: Log out as a Admin

AR-5: Log out as a teacher

AR-1: Log in as a Student

AR-1: Log out as a Student

11
@ Daffodil international university
To get access to this system or a specific module the system must offer a

vitalverificationdevice. So as toavoidanybody to feattaken all users password must be

encrypted in hash process.

2.6.4 User Documentation

UH-03 The system developer documentation

Description To develop this project we have specified requirement of user
documentation. The teams are involved to this project
documentation.
Stakeholders System Developer

2.7 Look and Feel Requirements

The look and feel requirements definebythe envisionedsoul, the disposition, or the style of the

produce'sarrival. These requirements stipulate the meaning of the arrival, and are not a full

design of an interface.

It should be clear to the admin and users of this system which fields need to be filled and

which can be left blank in this system.

2.7.1 Appearance Requirements

LF-01 Labels of obligatory fields must be bold

Description Labels of obligatory fields must be bold to classify them by way
ofexistence of obligatory.
Stakeholders Admin and operators of this system

12
@ Daffodil international university
2.7.2 Style Requirements

We will provide a web based user interface. This requirement does not individualdescribe the

need to usage a css but though the requirements concerning the css’sgratified as well as css

framework like bootstrap.

LF-02 The look and feel must be manageable using style sheet.
Description The styling of the elements of the web based operator interface
will be clearbycss, JS and bootstrap.
Stakeholders Admin, System Developer

2.8 Operational and Environmental Requirements

This requirements emphasis on how the operators will operate the system, counting interfaces

and interoperability with other systems. The requirements found how healthy and below what

circumstances the system must perform.

2.8.1 Release Requirements

Here are not any exactannouncement requirements but in the project schedule section it was

described briefly.

2.9 Legal Requirements

These requirements consider any violence of rules and regulation and which rules should be

followed to maintain this system.

13
@ Daffodil international university
Chapter 3: System Analysis

3.1 Use Case Diagram

By the use case diagram we try to represent our system easily that the user easily can

understand our system. For that reason we draw use case diagram that is given below in

figure no- 3.1.

Figure 3.1: Use Case Diagram of class routine management System

14
@ Daffodil international university
3.2 Use Case Description (Brief)

There are three types of users in this system. The first two are teachers and students who is

the main user of this system and the third type of user, the administrator, who is able to

initially setup the system, modify this system and set their authorization level.

Teachers: This is a one of the main users of this system .This type of user able to see

Specific routine for every teacher, class cancel and also take extra class or makeup class. All

this system teacher must have to login into their own account.

Students: This is also one of the main users of this system .This type of user also able to see

their individual routine, makeup class, extra class, overlap class. Also see the details of the

class room.

Admin: Finally, the system administrators are users who are able to setup the system from

the initial installation and maintain the systems member accounts. They automatically have

the functionality of authorized users within the normal operation of the system.

3.3 Activity Diagram

Activity diagram is another important diagram in UML to describe the dynamic aspects of the

system. Activity diagram is basically a flowchart to represent the flow from one activity to

another activity. The activity can be described as an operation of the system.

For our better understand we also draw activity diagram for different users that include

Teacher activity, Student activity and Admin activity that show below in figure no- 3.2, 3.3,

3.4.

15
@ Daffodil international university
3.3.1 Teacher Activity

Figure 3.2 Activity diagram for teacher

3.3.2 Student Activity

Figure 3.3 Activity diagram for student

16
@ Daffodil international university
3.3.3 Admin Activity

Figure 3.4 Activity diagram for admin

3.4 System Sequence Diagram

In software engineering, a system sequence diagram (SSD) is a sequence diagram that

displays, for a specificsituation of a use case, the proceedings that outsideperformersgenerate

their instruction, and likely inter-system proceedings. Here we also draw system sequence

diagram that helps us how they interact with this system that show in figure no-3.5, 3.6, 3.7.

17
@ Daffodil international university
3.4.1 System Sequence Diagram Teacher

Figure 3.5 System Sequence diagram for teacher

18
@ Daffodil international university
3.4.2 System Sequence Diagram Student

Figure 3.6 System Sequence diagram for student

19
@ Daffodil international university
3.4.3 System Sequence Diagram Admin

Figure 3.7 System Sequence diagram for admin

20
@ Daffodil international university
Chapter 4: System Design Specification

4.1 Sequence diagram

Sequence diagrams are sometimes called event diagramsor event scenarios.Heresequence

diagram represent how the system process work through the sequence in this system. In this

sequence diagram we try to show all different users process through by the sequence diagram

in below infigure no-4.1, 4.2, 4.3.

4.1.1 Sequence diagram for teacher system

Figure 4.1: Sequence diagram for teacher

21
@ Daffodil international university
4.1.2 Sequence diagram for student system

Figure 4.2: Sequence diagram for student

22
@ Daffodil international university
4.1.3 Sequence diagram for admin system

Figure 4.3: Sequence diagram for admin

4.2 Database Design

Database design is the organization of dataaccording to a database model.

The designerdetermines what data must be stored and how thedata elements interrelate. With

this information, they can begin to fit the data to the database model.Database

design involves classifying data and identifying interrelationships.

(3)

23
@ Daffodil international university
4.2.1 E-R Diagram

Figure 4.4: E-R diagram system

4.3 Development Tools & Technology

Design and implementation constraints are those that we have used to implement this project

make successful. It also describes tool that enables developers and testers to view and interact

with the user interface (UI) elements of this application.

4.3.1 User Interface Technology

User interface (UI) is everything designed into a system view that which person’s associates

with this system may like the interface of this system.

24
@ Daffodil international university
4.3.1.1 Programming Language

For developing this system we will use PHP as a programming language. PHP (recursive

acronym for PHP: Hypertext Pre-processor) is a widely-used open source general-purpose

scripting language that is especially suited for web development and can be embedded into

HTML. PHP is a server scripting language, and a powerful tool for making dynamic and

interactive Web pages

(4)

4.3.1.2 JavaScript and jQuery Library

The most common use of JavaScript is to add client-side behavior to HTML pages, also

known as Dynamic HTML (DHTML). Scripts are embedded in or included from HTML

pages and interact with the Document Object Model (DOM) of the page.

J Query is a JavaScript library. J Query greatly simplifies JavaScript programming. J Query

UI is a curated set of user interface interactions, effects, widgets, and themes built on top of

the j Query JavaScript Library. Whether you're building highly interactive web applications

or you just need to add a date picker to a form control, j Query UI is the perfect choice. J

Query UI is built for designers and developers alike. We've designed all of our plug-ins to get

you up and running quickly while being flexible enough to evolve with your needs.

(5)

25
@ Daffodil international university
4.3.1.3 CSS Framework

CSS is a language that describes the style of an HTML document. CSS describes how HTML

elements should be displayed. Build responsive, mobile-first projects on the web with the

world's most popular front-end component library.

Bootstrap is an open source toolkit for developing with HTML, CSS, and JS. Quickly

prototype your ideas or build your entire app with our Sass variables and mix INS, responsive

grid system, extensive prebuilt components, and powerful plug-ins built on j Query.

The bootstrap code is included minified, which means that white spaces are removed to make

the file size smaller and therefore make the load time faster for the file which improves the

load time for the whole page. The main design that bootstraps ads without specifically adding

design to elements is that when hovering over a link. This is fixed with some simple CSS

code added to the CSS-file, unless the bootstrap CSS-file is included after the original, then

bootstrap will override the custom ones and the changes will not be seen. Having some basic

knowledge about how Bootstrap works before starting to use it would increase the efficiency

and speed one might achieve the goal one has in mind for including bootstrap into the project.

(6)

4.3.1.4 Twitter Bootstrap

Bootstrap is a free and open-source front-end framework for designing websites and web

applications. It contains HTML- and CSS-based design templates for typography, forms,

buttons, navigation and other interface components, as well as optional JavaScript text

extensions. Unlike many earlier web frameworks, it concerns itself with front-end

development only.

(7)

26
@ Daffodil international university
4.3.2 Implemented Tools and Platform

Eachcommercialstrategy, movement, or schemeoriginatesdepressed to Strategies, Tools, and

Plans. Towardconsider, grow, and tool a complete social media advertising strategic plan

that will be fruitfulwants to have those three dangerousmechanisms.

4.3.2.1 Web Server

A Web server is a program that uses HTTP (Hypertext Transfer Protocol) to serve the files

that form Web pages to users, in response to their requests, which are forwarded by their

computers' HTTP clients. Dedicated computers and appliances may be referred to as Web

servers as well. We will use the Apache HTTP server to implement this project.

(8)

4.3.2.2 Database Server

We will use MySQL database server to store all of the information of this system. The reason

behind to choose the database server are given below:

 Security
 Reporting and Data Mining
 Replication
 Fault tolerance
 Performance diagnostics

27
@ Daffodil international university
Chapter 5: System Testing

5.1 Testing Features

A Software feature can be strong as the changes made in the system to add new functionality

or adapt the current functionality. Allfeaturesaresupposed to have characteristics that are

designed to be useful, intuitive and effective.

In realism, a new test set is shaped for testing that feature consistent to that cycle of that

announcement. The tremendouslysignificant and usually used new features must to be tested

methodically in each build of that release and also reversion testing should be done pertinent

to those areas.

5.1.1 Features to be tested

Features Priority Description

Registration 1 Get all service from this system, it is required to be
registered.
Modify 3 Edit the information when need
Delete 2 Delete information from the list
Show details 1 All posted information will show in the page.
Login 1 Login as authenticated user
Logout 1 Logout from the system.
Change password 2 Change password by the system users
Application error 1 It is important for all to get the proper error message
message
processing
Technological Features
Database 1 Entrée to database is oftenwantedprocess. So this
technical feature should be firmly in control for
management system

28
@ Daffodil international university
5.1.2 Features not to be tested

The features which have not been tested are

Features Description
Check users status it is not required because it will be done by system administrator

5.2 Testing Strategy

A test strategy is aplan that defines the testingmethod of the software development cycle. It is

created to notify project managers, testers, and developers about some importantsubjects of

the testing process. They are created based on development design documents.

5.2.1 Test Approach

Test approach is the test planapplication of a project, describes how testing would be

approvedavailable.

5.2.1.1 Black Box Testing

Black box testing also called functional testing that ignores the internal mechanism of a

system or component and focuses on the outputs generated in response to selected inputs and

execution conditions. We have decided to perform equivalence partitioning and Boundary

value analysis for this system

29
@ Daffodil international university
5.2.1.2 White Box Testing

White box testingis a software testing method in which the internal structure /implementation

of the item being tested is known to the tester. The tester chooses inputs to exercise paths

through the code and determines the appropriate outputs. Programming know-how and the

implementation knowledge is essential.

(9)

5.2.2 Pass/Fail Criteria

The arrival criteria’s for allstage of testing must be encounteredbeforehand the

followingstage can begin. Currently the criteria’s for pass and fail are given below.

 Rendering to the assumedsituation the predictable result need to take place then the

situation will be careful as pass then that standards should be failed.

 If an item tested 10 times, 9 times flawlessly worked and single time do not work

correctly then it will reflect as fail case.

 System crash will be careful as fail case.

 Afterwardsuccumbingainquiry in the system, if predictable page won’t seem then it

will be careful as fail case.

5.2.3 Testing Schedule

This section will describe testing schedule.

 Stipulate test signs.

 Stipulateentirelyarticle transmitted proceedings.

 Approximation time obligatory to do each testing mission.

30
@ Daffodil international university
  Schedule entirely testing tasks and test signs

 For each testing supply, stipulate its retro of use.

Test Phase Time

Test Plan Creation 1 week
Test specification creation 2 week
Unit Testing During Development time
Component testing 1 week
Test Phase Time
Integration Testing 1 week
Use case validation 1 week
User interface testing 1 week
Load testing 1 week
Performance Testing 2 week
Release to Production 1 week

5.2.4 Trace Ability Matrix

BR# Category/Fu Requirement Use Case Test Case Comments

nctional Description Reference Reference
Activity
BR_1 Functional Teacher page Use case 3.2 Test case 5.4.1 &
5.4.2
BR_2 Functional Student page Use case 3.2 Test case 5.4.1
BR_3 Functional Admin panel Use case 3.2 Test case 5.4.1 &
5.4.2
BR_4 Performance Speed & N/A N/A
requirements latency
requirements

31
@ Daffodil international university
5.3 Testing Environment

Testing environment is aarrangement of software and hardware for the testing teams to

perform test cases. In additional words, it ropes test implementation with hardware, software

and network configured.

For test environment, key part to set up comprises

 System and applications

 Test data

 Database server

 Front end running environment

 Client operating system

 Browser

 Hardware includes Server Operating system

 Network

 Documentation required like reference documents/configuration guides/installation

guides/ user manuals

(9)

5.4 Test Cases

A test case is a set of conditions or variables under which a tester will determine whether a

system under test satisfies requirements or works correctly. The process of developing test

cases can also help find problems in the requirements or design of an application.

(10)

32
@ Daffodil international university
5.4.1 Login

Test Case #01 Test Case Name: Login

System: Class Routine Management System Subsystem: Student & Teacher
Designed By: MdZillurRahman& Md. Readul Islam Designed Date: 10/26/2018
Executed By: Executed Date:
Short Description: They both are registered and trying to log into the system
Pre-condition:
1. Students and Teachers both are registered
2. Assume username is ‘zillur@gmail.com’ and password is ‘zillur’
Ste UserId Email Password Expected result Pass/ Comment
p Fail

1 142-35-7717 zillur@g Zillur Wrong userid

mail.com
2 --- zillur@g Zillur Invalid userid
mail.com
3 zillur@g Zillur Userid can’t be
mail.com blank
4 142-35-726 --- Zillur email can’t be
blank
5 142-35-726 zillur@g Password can’t be
mail.com blank
6 A142-35-726 zillur@g 123qwe Wrong userid
mail.com
7 142-35-726 zillur@g @@ Invalid password
mail.com Zillur@@
8 142-35-726 zillur@g Zillur Successfully
mail.com logged in
9 Userid,Gmail&pass
word can’t be blank
10 142-35-726 zillur@g Zillur Userid can’t be
mail.com greater than 9
number

33
@ Daffodil international university
11 142-35-726 zillur@g Abc Password cann’t be
mail.com less than 6
characters
12 142-35-726 zillur@g Assdfghjjkll password can’t be
mail.com kjhgf greater than12
characters
Post condition: Student and teacher both successfully logged into this system and can
access the system.

5.4.2 Modify Result

Test Case #02 Test Case Name:Modify Result

System: Class Routine Management System Subsystem:
Designed By: MdZillurRahman& Md. Designed Date: 10/26/2018
Readul Islam
Executed By: Executed Date:
Short Description: When modify any result then show the result in the page
Pre-condition:
1. Modify information and show in page
Step Action Expected result Pass/Fail Comment

1 Modify result Modify result and show in page

publish
Post condition: if any information is modify then show in page

34
@ Daffodil international university
Chapter 6: User Manual

6.1 User Menu

Here we see that is our user menu for routine management system. This routine management

system includes home page, student registration, student login and also teacher registration

and teacher login option.

35
@ Daffodil international university
6.2 Teacher Registration page

This is teacher registration page for login to his/her individual page in routine management

system. Every section must be needed to fulfill to complete the registration.

36
@ Daffodil international university
6.3 Teacher login Page

This is login page for every teacher. After complete their registration they able to login to

their own page.

37
@ Daffodil international university
6.4 Student login Page

Here we see the student login page for every student who already completes their registration

only they can login to this system.

6.5 Search Page for Student

This is the search page for students. They are able to search to find out their class routine and

other information through their id.

38
@ Daffodil international university
6.6 Search Page for Teacher

Here we see that this is the search page for every teacher. They can find their own routine

through the search option.

39
@ Daffodil international university
Chapter 7: Conclusion

7.1 project summary

This project is about class routine management system. The main focus of the project is to

find out the limitation of the current class routine management system in SWE, DIU from the

both side of the lecturers & students such as Specific routine for every teacher, class cancel,

extra class option for teacher and Individual routine, overlap class, makeup class or extra

class option for students.

7.2 Limitations

There are some limitations in my project such as us only show only Teacher can modify

his/her page. Another we cannot set the logic of the system that when any mistake in routine

system in student individual routine they don’t do anything.

7.3 Obstacles and Achievements

From the beginning of the system I learn so many things which are needed for developer.

Firstly I don’t know how to make a design properly such as database design how to write

algorithm and diagrams associates of a project work. Before this I don’t know the importance

of algorithm and how much it is needed for a programmer to build up a project.In the time of

building this system many importance part of the using language which I use for building this

system. I also learn before starting logical portion if the database design and project UI is

ready then it will be very easy to implement the code. In a word it was a great achievement

for me to build this system.

40
@ Daffodil international university
7.4 Further development

The developing software is good quality software. I am trying my best to satisfy the actual

need of the department system. But there is always scope for further development. I have

implemented the software and try my level best to deliver an excellent system though it has

some bug it will try to recover them Insha- Allah.

41
@ Daffodil international university
 APPENDIX

A O
Accessibility requirement, 19 Objective, 7
Activity diagram, 25

C P
Css, 36 Project overview, 8
Project purpose, 8

D project goals, 9

Database Design, 34 Project Shedule,10

Dependability requirement, 22Project summary, 52

FR
Functional requirement,12 Requirement engineering process, 29
Further development, 53 Requirement validation, 30

T S
Testing Features, 39 Security requirement, 24
Testing schedule, 41 Sequence Diagram, 26

Trace ability matrix, 43 System Sequence Diagram, 26

Test case, 44
U
L User manual,49
Limitation, 52 Use case diagram, 23

M
Maintainability and supportability, 23

42
@ Daffodil international university
 References

[1] https://en.wikipedia.org/wiki/Special:BookSources/9781447122388

[2] file:///D:/final%20project/SRS%20for%20DIU%20Alumni%20Association.pdf

[3]https://www.c-sharpcorner.com/article/javascript-vs-jquery-difference-between-javascript-

and-jquery/

[4]http://www.assignmentpoint.com/business/management/routine-management-system-for-

department-of-computer-science-and-engineering.html

[5] http://deshuniversal.com/class-routine-management-system

[6] https://guru99.com

[7] https://wiki openoffice.org

[8]https://en.wikipedia.org/wiki/CSS_framework

[9] (Logistics & Supply Management)

[10] (tutorialspoint.com)

[11] https://www.draw.io

43
@ Daffodil international university