Transcript CSolutions

CSolutions
(Creative Solutions)
STUDENT REGISTRATION
SYSTEM
Cihan ARSLAN
Volkan ERDOGAN
Bahadir GULDIKEN
Guvenc GUNGOR
Contents
• What is a Student Registration System (SRS)
• Main responsibilities of a S.R.S.
– Properties of our system
• Technical properties of current system
– Technology choice
– Disadvantages
• Technical properties of our system
– Which Technology is chosen and why ?
– Software architecture of our system
• Database Design
• Conclusion
What is a Student Registration System
(SRS)
• Student Registration System (SRS) is a computer-based
!
application program which manages the registration of
students with keeping necessary information
Main responsibilities of a S.R.S.
• Storage of student information
–Personal information
–GPA,CGPA
–Academic History etc.
• Course Management
–The information about prerequisite courses
–The information about courses
–The information about the instructors etc.
• Course assignment
• Registration
• Approval
Additional Properties of Our System
• As a result of interview with department secretaries and
some instructors, we will try to add some properties
which are not present in METU S.R.S.These are;
–
–
–
–
Course Scheduling
Help / TroubleShooting System
Pre-registration of courses
Elective Course distribution
Technical properties of current system
• Started working in 1997
• Uses Common Gateway Interface (CGI)
– CGI : A standard which lets Web server can hand a browser's
request for a Web page off to any program. Produces dynamic
content
• Developed using Sapphire from Bluestone
– A tool that can produce CGI programs from C code
• Can work with DB2,Informix,Oracle or Sybase DBMS
– Currently working with an Informix DBMS
Disadvantages of the Current System
• Inefficent
– Uses CGI:
• new process creation for each request
• Database connections cannot be reused
• Example: current METU system uses 3 MB of memory for each
connected user
• Not portable
– C code is used for development. Needs modifications for every
platform
Technical Properties of Our System
• Chosen Technology: Java
– Java Servlets for presenting Dynamic Content
– JDBC for database operations
• Why ?
– Java for portability and security in general
– Servlets for performance
• Based on threads not processes
• They persist across different requests
– JDBC for database independence
• JDBC offers a standart way to access virtually any DBMS
Software Architecture of Our System (1)
• We have 3 layered software architecture, which are:
– Presentation Layer
– Business Layer
– Database Integration Layer
• Why ?
– To seperate different functions of the system
– To increase cohesion of the parts of the system
Software Architecture of Our System (2)
Presentation Layer: Responsible for interacting
with the users of SRS and presenting the data it
acquires from business layer.
http or https
Client
/
USER
http or https
Business Layer: Responsible for managing
the communication between Presentation and
DBIntegration Layers
Socket Connection
Database Integration Layer: Responsible for
interaction with the database and passing data
from DB to the business layer
DBMS
Important Elements of Our Architecture
• DBIntegration Layer
– This layer is added to manage database access
• Database connections are precious: they take time to create
• Pools database connections
• Does load balancing
– Also handles course management and rule management
– Located in the database server
• To reduce the network overhead
– Uses Request and RequestResult objects to communicate with
the Business Layer
Important Elements (cont’d)
• Request and RequestResult objects
– These two objects are used for communication
• Passed between Business and DBIntegration layers using object
serialization and socket connections.
– They represent user request and the result of the request
– Request object can be used for any type of request
• Take course
• Drop course
• Approve student etc.
– Used to achieve flexibility
UML Deployment Diagram for S.R.S.
DATABASE DESIGN
• In our Database design,we first determined the
entities,their attributes and the relationships between the
entities.
• Our entities are;
– Students
– Instructors
– Courses
– Departments
– Locations
DATABASE DESIGN (cont’d)
• Some attributes of these entities must be multivalued.
• There are also some weak entities apart from the main
entities.
– The rules which are specific for each courses.Such as;
• Can not take a course who did not take its prerequisites
– The rules which contain the basic criteria for the registration
such as;
• Can not register in the suspension cases
• After the normalizing all the tables we will use this design
in the implementation.
CONCLUSION
We talked about:
• General information about SRS
• What we plan to do in project
• How we can do? (Our Technical Approach)
• General figures that describe our method approach
• Database DESIGN
THANKS FOR YOUR
PATIENCE

CSolution