Business Application Analysis and Design PROJECT REPORT

Submitted to: Sir, AYUB LATIF

SUBMITTED BY: MUHAMMAD SHAHRUKH KHA (54161) MUHAMMAD TAHA YASEEN (54488)

SYSTEM: Institute Management System.

OVER VIEW SYSTEM:

It provides an efficient and effective tool for institute to operate. It has been designed to manage and look after all over processing of the institute. It is capable of managing student detail, faculty detail, accounts detail, program details, student schedule, faculty schedule, campus, exam type, rooms, and course detail. It provides very helpful report for managing the institute in easy and accurate way. It is a system to consolidate the vast flow of information running through the institute.

FUNCTIONAL REQUIRMENT SPECIFICATION:

The project includes the following functions:

Add , update and delete the information Store and manages student information Store and manages faculty information View the information Formation of Schedule for student and faculty both. Keep records of student course information Record student billing and payment made Defaulter of fees can easily be known Collection of detailed information of specific individual Tracks all departmental activities

FUNCTIONAL REQUIRMENT:
Administrator will add, update, delete, and view the student information. Administrator add, update, delete course wise information (student and faculty). Administrator manages student schedule maintenance. Administrator manages student fee details and generate defaulter list.

NON-FUNCTIONAL REQUIRMENT:
Form for administrator such as log in. Form for student views a history and schedule of classes. Form for faculty view a classs schedule. Form for account view a student fee history.

USECASES DIAGRAM

ADMINSTRATOR USE CASE DIAGRAM:

Administrator use case diagram

Add courses

Register student

Add/Update marks

Delete/Remove marks

Adminstrator Allocate room

View result

Update schedule

STUDENT USE CASE DIAGRAM:

Student use case diagram

Enroll in the course

Select course

Drop course

Enroll in Exam

student

View result

Pay fee's

FACULTY AND ACCOUNTANT USE CASE DIAGRAM:

Faculty use case diagram

Make course outline

Teaching

Faculty View Schedule

Accountant use case diagram

Giving fee bills to student

Fee invoice

Accoutant Generate fee bills

ACTORS INTERACTION USE CASE DIAGRAMS:

System use case diagram

Print

-<<included>>

view student information

Get student information

Get exam schedule

Student

Get result

Adminstrator

Add fee payment

-<< extend>>

Fee invoice Accoutant

Print Generate fee bill

View

FLOW OF EVENTS

ADMINISTATOR:
Use case: register student:

Use case name

Actor

Register Student Administrator The use case describes the process of administrator registering the new students for the new semester

Description

Typical course events

Actor Action

System Response

Step 1: This use case initiated when administrator wants to register the student Step2: Administrator logins the Step3: system enters student System saves the student reg. No registration number Step 4: Enters student information Step5: System save student information

Pre-condition Post condition Assumptions

Only a administrator can register the student Administrator can update student information None at this time

Use case: add marks:

Use case name Actor Description Typical course events

Add marks Administrator The use case describes the process of administrator adding marks of students

Actor action

System response

Step 1: Step2: This use case initiated when System checks the students administrator add marks of information regarding their exams the student whether he/she has given the exam or not Step 3: Add student marks Step4: System save added marks of the students

Pre-condition Post condition Assumptions

Administrator add marks if only the student has given the exam Administrator can update student marks None at this time

Use case: update schedule:

Use case name Actor Description

Update schedule Administrator The use case describes the process of administrator updating the schedule of student and faculty

Typical course events

Actor action

System response

Step 1: Step2: This use case initiated when System checks the students and administrator wants to faculty schedule update schedule of student and faculty Step 3: Step4: Update student and faculty System save updated schedule schedule

Pre-condition

Post condition Assumptions

Administrator can update schedule if only student and faculty has any type of schedule Administrator can update schedule None at this time

STUDENT: Use Case: View Result

Use case Name
View Result Student The use case described the process of student viewing the result of his exams.

Actor Description

Typical Course Events

Actor Action

System Response

Step 1: Step 2: This use case initiated System ask or user id and when a student login to password. the system. Step 3: Check user id and password (Confirmation). Step 4: Open institute form. Step 5: Student Click on result form. Step 7: This use case conclude when the student view the result. Student should give the exam. If the student cant give the exam, he cant view the result. None at this time Step 6: Show result form.

Pre-condition Post condition Assumptions

Use Case: Add Course:

Use case Name
Add Course Student The use case described the process of student add course.

Actor Description Typical Course Events

Actor Action

System Response

Pre-condition Post condition Assumptions

Step 1: Step 2: This use case initiated System ask or user id and when a student login to password. the system. Step 3: Check user id and password (Confirmation). Step 4: Open institute form. Step 5: Step 6: Student Click on Course Show Course form. form. Step 7: Student check offered courses and prerequisites. Step 8: Step 9: Student click on add System confirms course course. added successfully. Step 10: This use case conclude when the Student Add Course. Check pre requisites Add Course None at this time

ACCOUNTANT:
Use case: giving fee bills to students:

Use case name Actor Description Typical course events

Giving fee bills to students Accountant The use case describes the process of giving fee bills to students

Actor action

System response

Step 1: This use case initiated when accountant wants to give fee bills to the students Step2: Accountant logins the system Step3: enters student registration System generate the fee bill number against student I.D Step 4: Accountant signs the fee bill and give it to the student

Pre-condition Post condition Assumptions

Only a accountant can generate the fee bill Accountant can give fee bills to the student None at this time

FACULTY: Use Case: View Schedule:

Use case Name
View Schedule Faculty The use case described the process of faculty view schedule.

Actor Description Typical Course Events

Actor Action

System Response

Step 1: Step 2: This use case initiated System asks for user id and when faculty login to the password. system. Step 3: Check user id and password (Confirmation). Step 4: Open institute form. Step 5: Faculty Click on faculty form Schedule. Step 7: This use case concludes when the faculty view schedule. Administrator updates the schedule. View Schedule attend the class. None at this time and Step 6: Show faculty schedule form.

Pre-condition Post condition Assumptions

CLASS DIAGRAM

* Student -StudentID : int +StudentName : string +FatherName : string -Phone : string -Address : string -Email : string -GetStudentID() -Add() -Update() 1 -Delete() * Exam +ObtainedMarks : string +TotalMarks : string +PassedMarks : string -Grading() -TotalPercentage() * * Student Schedule ExameType -ExamTypeID : int -Hourly1 : string -Hourly2 : string -Hourly3 : string -MidTerm : string -FinalPaper : string -Grade : string -Assigment : string -Quizes : string +Add() +Update() +StudentSchID : string +Time : string +Date : Date

Course History -CourseHistoryID -StudentID : int -CourseID : int +Add() +Update() Course * * -CourseID : int +CourseName : string -GetCourseID() -GetStdCourse() -Add() * 1 1 Room +RoomNo : string +RoomLocation : string +GetRoomNo() +AddRoomNo() +UpdateRoomNo() Status -StudentStatusID : int -StatusDescription : string -StudentID : int -Add() -Update() * Department -DepartmentNo : int -DepartmentName : string -Location : string -AddDept() -UpdateDept() * Faculty * Schedule -ScheduleID : int -Date : Date -Time : string -Day : string +GetStudentSch() +GetFacultySch() * * * Program -ProgramID : int +Program : string +Duration : Date +TotalNoOfStudent : string -Add() +Update() 1 Campus +CampusName : string +Location : string -GetCamppusName() * * * * * Payment Administration +Name : string +Designation : string -Get() -Add() -Update() * 1 1 Batch -SemesterID : int +SemesterName : string -AddSemester() -UpdateSemester()

* * *

Faculty Schedule -FcltySchID : int -Time : string -Date : Date

* Fee -FeeCollID : int -FeeCollDetail : string -Add() -Update() 1 * * FeeType -FeeTypeID : int -FeeType : string -FeeDescription : string -GetFeeType() -Update() 1 * Employee Type -EmployeeTypeID : int -Staff : String +Add() +Update() 1 1 * Account -AccountID : int -StudentID : int -Fees : string -PayDate : Date -TotalFee() -Balance()

+Administrator : string -CourseReg : string -SchedulingCourse : string -RoomAssigning : string -OrganizingClass : string -Add() -Update() *

-PaymentID : int -NoOfAttendance : string -FacultyName : string -TotalPay() -Balance() -Update() * *

* City +CityName : string 1 -GetCityName()

Payment Mode -Payment_ModeID : int -PaymentMode : string -Amount : double +View() +Add() +edit()

Employee -EmployeeID : int -Address : String +Add() +Update()

* *

Payslip -PayslipID : int -Paydate : Date +View()

Invoice -InvoiceID : int -Amount : double +date()

SEQUENCE DIAGRAMS

ADD COURSE:

:User
login
Return();

:Student

: Course history

:Course

Get course history

Get course

Return(); Check prerequisite Return();

Add course

Return(); successfully added

DROP COURSE:

:User
Login Return();

:Student

:Course

Get course information Return(): Drop course Return(); successfully drop

STUDENT VIEW MARKS:

:User
Login Return();

:Student

:Exam

View marks Show marks

VIEW FACULTY SCHEDULE:

:Faculty
Login Return();

:Login

:Faculty schedule

Check course timing

Get course timing

Return();

Return course timing

ACTIVITY DIAGRAMS

ADD COURSE:

Login

Enter user name and pass word

NO

Verify user
YES

Go back to login

View course history

Course offered
NO Check prerequisite YES

Cannot select the course

Add course

Course added successfully

DROP COURSE:

Login

Enter user name and pass word

NO

Verify user
YES

Go back to login

Course information and course offered

Drop course

Course drop successfully

ADMINSTARTOR ADD COURSES:

Login

Enter user name and pass word

NO

Verify user
YES

Go back to login

Ask I.D from student

View courses

No Ask student which course to add

No

Can't select the course

Yes

Yes

Add course Course added successfully

FACULTY VIEW SCHEDULE:

Login

Enter user name & password

No Verify user Yes

Go back to login

Open faculty schedule

Check course timing from from faculty scdedule

Timing viewed successfully