You are on page 1of 16

B.

A Jesica Malani Azhar Zakaria Mahgoub Ebadi Ahmad Slddig Mohsen Joozdani

Student Management System (S.M.S) is to create an integrated information technology environment for students, faculty, staff and administration SMS manages the student information by accepting adding, modifying or removing (i.e. processing) information and generating reports

Providing a proper registration channel/system to the new students Maintaining all students accounts since enrollment till graduation Updating the transmitted users information Information availability at any time and any where Secure and easy data accessibility Centralized and monitored control over the records

Student Management System captures: Student attendance Students grades Classes time table Education previous profile

Real-time information and data decision accessed by: Lecturers and tutors Students Faculties and academic centers Administrators Parents

Application form Add, edit or delete student application form Report

Manage Fees Manage Billing Manage Payment Manage Collection Report

Admission Module

Financial Module

Graduation Status Transcripts Report

Graduation Module

Academic Module

Academic Structure Student Registration Class time table Student time table Student attendance Examination Student Progress Report

Client-server and object-oriented architecture styles are used to build this system. Three tier architecture pattern is used in this project to build client-server application.

First Tier Second Tier


Business Object/ Component

Third Tier

Business Object/ Component

Business Object/ Component

Student

Registration

Faculty

Billing Entry

Graduate School

Payment

Administration

Student

Registration

Faculty

S.M.S Database

Administration

Staff

Payment

Application Software - SAP OS Windows Server 2008 Database Oracle10g Programming Language Java Script, PHP Hardware HP Enterprise Server

Extensibility/Reuse The software should be extensible in order to add new features without affecting the base modules. The new releases of the system should maximize the reuse of the solutions developed in earlier releases Ease of use The system must be easy to use without requiring users to memorize the commands, special terms, or notations. A new user should not require more than one hour of training to get comfortable using the system Portability The system must be easily portable to a wide variety of platforms using various operating systems. Porting the software from one operating system to another should not require more than 5% of the code to be changed. Similarly changing the backend database should not require more than 5% of the code to change.

Quality Attribute Performance

Attribute Refinement

Scenarios

Transaction Response Time


Throughput

Response time for each transaction less than 0.5 sec


At peak hour, system able to complete 150 normalized transaction Redrawn the graph in 1 sec Provide user training and system training User friendly During blackout or system down, S.M.S able to backup all the data

Generating Report Usability Training Normal Operation Efficiency Data Recovery

Quality Attribute

Attribute Refinement Output accuracy

Scenarios The propability for non-accurate output, 1% of mistake The system support 24/7 webbased account Assurance that data is consistent and correct, column chosen to be the primary key should be unique and not null Data can only be accessed by authorized user A maintainer encounter search and response time defencies,fix the bug and distributes the bug fix The probability the S.M.S will found in state of failure during peak hours is required to below 0.5%

Correctness

Security

Availability

Integrity

Confidentiality Maintainability Debugging

Reliability

System failure

Design issues and its effects Data traffic Security issues with third parties

System design specifications Team management Lack of certain skills (designing and programming) Time pressure

Thank You

You might also like