1. Presentation Prepared by:-
Mr. Soumya Subhadarshi Behera
B.Tech (CSE) – 5th Semester
Roll No. 1826
UIET, MDU, Rohtak

2. This presentation Includes:
 Introduction
 Motivation
 System Development


3. Introduction
 A School Management System is a large
database system which can be used for
managing school's daily work.
 It is configurable and can be configured to meet
most individual school's needs.
 It is a multi-user system and can be used by
hundreds of users at same time.
 Generally speaking, it is platform available for
running on a Local Area Network (LAN).
3

4. This presentation
Includes:
 Introduction
 Motivation
 System Development
Mihal Brumbulli 

5. Motivation 5
 As everywhere everyone wants things to be done in an
easier and faster way so I worked on a developed
strategy which aims the development of administrative
and management structures in all the high schools of
the country.
 Most of the high schools are already equipped with
necessary hardware and network structures under the
supervision of the Ministry of Education.
 Open issue:
 Managing the information electronically.
 Solution:
 School Management System
Mihal Brumbulli

6. Goals:
 Managing information on students,
 Employees,
 Teaching Processes
 Result Processing
 etc...
Mihal Brumbulli 6

7. This presentation Includes:

 Introduction
 Motivation
 System Development
Mihal Brumbulli

8. Components of making a
software are:-
 System and software requirements analysis
 Design and implementation of software
 Ensuring, verifying and maintaining software
integrity

9. System analysis is an activity that
encompasses most of the tasks that
are collectively called Computer
System Engineering.

10. System analysis is conducted
with following objectives:
 Identify the customer’s need
 Evaluate the system concept for feasibility
 Perform economic and technical analysis
 Allocate functions to hardware, software,
people, database and other
system elements
 Establish cost and schedule constraints
 Create a system definition that forms the
foundation for all the subsequent engineering
work.

11.  FRONT END / GUI TOOLs: Visual Basic 6.0
 BACK END / RDBMS: ORACLE / SQL 9i and 11g:

12. Special Features:
 VISUAL BASIC is a high level programming language
evolved from the earlier DOS version called BASIC.
BASIC means Beginners' All-purpose Symbolic
Instruction Code.
 A fairly easy programming language to learn.
 Different software companies produced different version
of BASIC, such as Microsoft QBASIC, QUICKBASIC,
GWBASIC ,IBM BASICA and so on.
 VISUAL and events driven Programming Language.
 Graphical environment.
 Integrated Development Environment.

13. VISUAL BASIC - THE BASIC
CANVAS
Every time you load a VB or VBA project, you will be greeted
by roughly the layout with five GUI tools:
• First, the toolbox(1) contains all the GUI
elements/controls needed to create any VB form and the
front end to all VB programs.
• Second is form(2). you can size it, color it, give it a
caption ("Database Test" in this case) and fill the form with
GUI controls which help your program do useful works.

14.  The third part of the Basic canvas are the menus and
toolbars(3) which manage and control all of VB.
 Fourth is the Project Explorer (4)which you use to
access all the forms and coding files in your VB program.
 Fifth, and even more frequently used than the
Project Explorer is the Properties sheet(5). If you want to
change the property of any control like its color, shape,
caption, or whatever - the Property sheet is the place to
go.

15. VB INTERFACE

16. Structure of VB Program
Private Sub <name>()
Comment statement(s)
Declaration statement(s)
BASIC statement(s)
End Sub

17. Steps in Building a Visual Basic
Application:-
Step 1 : Design the interface
Step 2 : Set Properties of the controls (Objects)
Step 3 : Write the events' procedures

18. •Personal DBMS Vs Client/Server DBMS
•Oracle 9 Environment
•SQL – syntax and examples
•PL/SQL-introduction

19. Server
Personal Gets file requests from clients
Sends files to client
DBMS Receives files back from clients
NETWORK
Client A Client B
Sends file requests to server Sends file requests to server
Receives files from server Receives files from server
Updates data Updates data
Sends files back to server Sends files back to server

20. Server
Client/server Gets data requests from clients
Adds, Deletes and updates data
DBMS Sends results to clients
NETWORK
Client B
Client A Sends data requests to server
Sends data requests to server Receives results from server
Receives results from server Sends new data or changes to server
Sends new data or changes to server

21. Client/Server DBMS
Minimal load on the client and the network
Performs table locking automatically
Fault tolerant in the case of client failure
File based transaction logging

22. Oracle 9 Environment
SQL * Plus
PL/SQL
Query Builder
Developer
Enterprise Manager
Web application server

23. SQL * Plus commands
Sqlplus username/password
ALTER USER user-name IDENTIFIED BY newpassword
CLEAR SCREEN
HELP <command>
SAVE filename[.ext] REPLACE|APPEND
EXIT

24. SQL
Both an ANSI and ISO standard
Types of commands:
1. Data Definition Language (DDL) : Create, Alter, Drop,
Rename, Truncate
2. Data Manipulation Language (DML): Insert, Delete,
Update
3. Data Retrieval: Select
4. Transaction Control: Commit, Rollback, Savepoint
5. Data Control Language (DCL): Grant, Revoke

25. A PL/SQL Example:
CREATE OR REPLACE PROCEDURE raise_salary (empno INTEGER,
increase REAL) IS
current_salary REAL;
salary_missing EXCEPTION;
BEGIN
SELECT salary INTO current_salary FROM emp WHERE emp.empid = empno;
IF current_salary IS NULL THEN
RAISE salary_missing;
ELSE
UPDATE emp SET salary = salary + increase WHERE emp.empid = empno;
END IF;
EXCEPTION
WHEN salary_missing THEN
UPDATE emp SET salary=0 where emp.empid=empno;
END raise_salary;

26. Design and implementation of
software
This includes:
1. Preliminary Investigation
2. Feasibility Study-
a) Technical
b) Economical
c) Operational

27. SYSTEM DESIGN
 It describes desired features and operations
in detail, including screen layouts, business
rules, process diagrams, pseudo code and
other documentation.
 The most creative and challenging phase of
the software development life cycle is
software design. The term design describes
final software and the process by which it is
developed.

28. Ensuring, verifying and
maintaining software
integrity
 The degree to which the software makes optimal use of
system resources as indicated by the following sub
attributes: time behavior, resource behavior. The efficiency
is the amount of computing resources and code required by
a program to perform its functions.
 A design should clearly be very verifiable, complete
(implements all the specification), and traceable (all design
elements can be traced to some requirements). However,
the two most important properties that concerned
designers are efficiency and simplicity.

29.  The Term “ Code Optimization” refers to techniques a
compiler can employ in an attempt to produce a better
object language program than the most obvious for a given
source program.
 Verification and validation (V & V) is the generic name given
to the checking processes which ensure that software
conforms to its specification and meets the need of the
software customer.
 Verification and validation i.e. starts with requirements
reviews and continues through design and code reviews to
product testing.

30. Maintenance:
 The term Maintenance is a little strange when
applied to software. In common speech, it
means fixing things that break or wear out. In
software nothing wears out; it is either wring
from beginning, or we decode later that we want
to do something different. It is a very broad
activity that includes error corrections,
enhancements of capabilities, deletion of
obsolete capabilities, and optimization.

31. There are three major
categories of software
maintenance:
 Corrective Maintenance: It means repairing processing
or performances failures or making changes because of
the previously uncorrected problems.
 Adaptive Maintenance: It includes modifying the
software to match changes in the ever-changing
environment.
 Perfective Maintenance: It means improving processing
efficiency or performance, or restructuring the software
to improve changeability.

32. SYSTEM SECURITY MEASURES
 Security involves both policies and mechanism to protect
data and ensure that it is not accessed, altered or deleted
without proper authorization.
 Integrity implies that any properly authorized access,
alteration or deletion of the data in the database does
not change the validity of the data.
 Database security policies are guidelines for present and
future designers regarding the maintenance of the data
base security.

33. PROGRAM EVALUATION REVIEW
TECHNIQUE (PERT) CHART
 The chart shows clearly that the project
consists of the activities of Analysis, design,
front-end coding, back-end coding and report
generation.

34. GANTT CHART
A Bar / Gantt chart is Sales
perhaps the simplest Analysis
form of formal project Design
management. The bar Front End Coding
Back End coding
chart is used almost Testing
exclusively for Report Generation
scheduling purposes 14% 11%
and therefore controls 11%
only the time 16%
24%
dimension of projects. 24%

35. Thank You
for Watching!!!