baad project report

8/13/2019 Baad Project Report

1/27

Business Application Analysis and Design

PROJECT REPORT

Submitted to: Sir, AYUB LATIF

SUBMITTED BY:

MUHAMMAD SHAHRUKH KHA

(54161)

MUHAMMAD TAHA YASEEN

(54488)


2/27

SYSTEM:

Institute Management System.

OVER VIEW SYSTEM:

It provides an efficient and effective tool for institute to operate. It has beendesigned 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.


3/27

USECASES

DIAGRAM


4/27

ADMINSTRATOR USECASE DIAGRAM:

Adminstrator

Add courses

Delete/Remove marks

Add/Update marks

Register student

Update schedule

View result

Allocate room

Administrator use case diagram


5/27

STUDENT USE CASE DIAGRAM:

student

Enroll in the

course

Select course

Drop course

Enroll in Exam

Pay fee's

View result

Student use case diagram


6/27

FACULTY AND ACCOUNTANT USECASE DIAGRAM:

Faculty

Accoutant

Make course outline

Generate fee bills

Fee invoice

Giving fee bills

to student

View Schedule

Teaching

Faculty use case diagram

Accountant use case diagram


7/27

ACTORS INTERACTIONUSE CASE DIAGRAMS:

Student Adminstrator

Accoutant

view studentinformation

Generate fee bill

Print

View

Print

Fee invoice

Add fee payment

Get studentinformation

Get result

Get exam schedule

-

->

System use case diagram


8/27

FLOW OF

EVENTS


9/27

ADMINISTATOR:

Use case: register student:

Use case name Register Student

Actor Administrator

Description The use case describes theprocess of administrator

registering the new students

for the new semester

Typical course events Actor Action System ResponseStep 1:

This use case initiated when

administrator wants to

register the student

Step2:

Administrator logins the

system enters student

registration number

Step 4:

Enters student information

Step3:

System saves the student reg. No

Step5:

System save student information

Pre-condition Only a administrator canregister the student

Post condition Administrator can updatestudent information

Assumptions None at this time


10/27

Use case: add marks:

Use case name Add marks

Actor Administrator


adding marks of students

Typical course events Actor action System responseStep 1:


administrator add marks of

the student

Step 3:

Add student marks

Step2:

System checks the students

information regarding their exams

whether he/she has given the

exam or not

Step4:

System save added marks of the

students

Pre-condition Administrator add marks ifonly the student has given

the exam

Post condition Administrator can updatestudent marks



11/27

Use case: update schedule:

Use case name Update schedule

Actor Administrator


updating the schedule ofstudent and faculty



administrator wants to

update schedule of student

and faculty

Step 3:

Update student and faculty

schedule

Step2:

System checks the students and

faculty schedule

Step4:

System save updated schedule

Pre-condition Administrator can updateschedule if only student and

faculty has any type of

schedule

Post condition Administrator can updateschedule



12/27

STUDENT:

Use Case: View Result

Use case Name View Result

Actor StudentDescription The use case described

the process of studentviewing the result of hisexams.

Typical Course

EventsActor Action System Response

Step 1:

This use case initiatedwhen a student login tothe system.

Step 5:

Student Click on result

form.

Step 7:This use case concludewhen the student viewthe result.

Step 2:

System ask or user id andpassword.

Step 3:Check user id and password(Confirmation).

Step 4:Open institute form.

Step 6:

Show result form.

Pre-condition Student should give theexam.

Post condition If the student cant givethe exam, he cant viewthe result.



13/27

Use Case: Add Course:

Use case Name Add Course

Actor Student

Description The use case describedthe process of studentadd course.

Typical Course


Step 1:

This use case initiated

when a student login tothe system.

Step 5:

Student Click on Courseform.Step 7:

Student check offeredcourses and pre-requisites.Step 8:

Student click on addcourse.Step 10:This use case concludewhen the Student AddCourse.

Step 2:

System ask or user id and

password.

Step 3:

Check user id and password(Confirmation).Step 4:

Open institute form.Step 6:

Show Course form.

Step 9:

System confirms courseadded successfully.

Pre-condition Check pre requisites

Post condition Add Course



14/27

ACCOUNTANT:

Use case: giving fee bills to students:

Use case name Giving fee bills to students

Actor Accountant

Description The use case describes theprocess of giving fee bills to

students



accountant wants to give fee

bills to the students

Step2:

Accountant logins the system

enters student registration

number

Step 4:

Accountant signs the fee bill

and give it to the student

Step3:

System generate the fee bill

against student I.D

Pre-condition Only a accountant cangenerate the fee bill

Post condition Accountant can give fee billsto the student



15/27

FACULTY:

Use Case: View Schedule:

Use case Name View Schedule

Actor FacultyDescription The use case described

the process of facultyview schedule.

Typical Course


Step 1:This use case initiatedwhen faculty login to the

system.

Step 5:

Faculty Click on facultyform Schedule.

Step 7:

This use case concludeswhen the faculty viewschedule.

Step 2:

System asks for user id andpassword.

Step 3:Check user id and password(Confirmation).

Step 4:Open institute form.

Step 6:

Show faculty schedule form.

Pre-condition Administrator updatesthe schedule.

Post condition View Schedule andattend the class.



16/27

CLASS

DIAGRAM


17/27

-GetStudentID()-Add()

-Update()

-Delete()

-StudentID : int

+StudentName : string

+FatherName : string

-Phone : string

-Address : string

-Email : string

Student

-GetCourseID()

-GetStdCourse()

-Add()

-CourseID : int

+CourseName : string

Course

-Add()

-Update()

-StudentStatusID : int

-StatusDescription : string

-StudentID : int

Status

-AddSemester()

-UpdateSemester()

-SemesterID : int

+SemesterName : string

Batch

-Add()

+Update()

-ProgramID : int+Program : string

+Duration : Date

+TotalNoOfStudent : string

Program

-AddDept()

-UpdateDept()

-DepartmentNo : int

-DepartmentName : string

-Location : string

Department

-GetCamppusName()

+CampusName : string

+Location : string

Campus

-GetCityName()

+CityName : string

City

+StudentSchID : string

+Time : string

+Date : Date

Student Schedule

-Get()

-Add()

-Update()

+Name : string

+Designation : string

Faculty

-Add()

-Update()

-FeeCollID : int

-FeeCollDetail : string

Fee

+GetRoomNo()

+AddRoomNo()

+UpdateRoomNo()

+RoomNo : string

+RoomLocation : string

Room

-TotalFee()

-Balance()

-AccountID : int

-StudentID : int

-Fees : string

-PayDate : Date

Account

+Add()

+Update()

-ExamTypeID : int

-Hourly1 : string

-Hourly2 : string-Hourly3 : string

-MidTerm : string

-FinalPaper : string

-Grade : string

-Assigment : string

-Quizes : string

ExameType

-TotalPay()

-Balance()

-Update()

-PaymentID : int

-NoOfAttendance : string

-FacultyName : string

Payment

-Grading()

-TotalPercentage()

+ObtainedMarks : string

+TotalMarks : string

+PassedMarks : string

Exam

*

*

1

1

11

11

*

*

*

1

*

1

*

*

*

*

*

1

-GetFeeType()

-Update()

-FeeTypeID : int

-FeeType : string

-FeeDescription : string

FeeType

*

*

-Add()

-Update()

+Administrator : string

-CourseReg : string

-SchedulingCourse : string

-RoomAssigning : string

-OrganizingClass : string

Administration

*

*

+Add()

+Update()

-CourseHistoryID

-StudentID : int

-CourseID : int

Course History

*

*

*

*

*

*

-FcltySchID : int

-Time : string

-Date : Date

Faculty Schedule

+Add()

+Update()

-EmployeeID : int

-Address : String

Employee

*

*

+Add()

+Update()

-EmployeeTypeID : int

-Staff : String

Employee Type

1

1

+View()

+Add()

+edit()

-Payment_ModeID : int

-PaymentMode : string-Amount : double

Payment Mode

**

*

*

+date()

-InvoiceID : int

-Amount : double

Invoice

+GetStudentSch()

+GetFacultySch()

-ScheduleID : int

-Date : Date

-Time : string-Day : string

Schedule

*

*

*

*

*

*

1

1

+View()

-PayslipID : int

-Paydate : Date

Payslip

*

*

*

*

*

*


18/27

SEQUENCE

DIAGRAMS


19/27

ADD COURSE:

:User :Student : Course history :Course

login

Return();

Get course history Get course

Return();

Add course

Return(); successfully added

Check prerequisite

Return();


20/27

DROP COURSE:

:User :Student :Course

Login

Return();

Get course information

Return():

Drop course

Return(); successfully drop


21/27

STUDENT VIEW MARKS:

:User :Student :Exam

Login

Return();

View marks

Show marks


22/27

VIEW FACULTY SCHEDULE:

:Faculty :Login :Faculty schedule

Login

Return();

Check course timing Get course timing

Return course timingReturn();


23/27

ACTIVITYDIAGRAMS


24/27

ADD COURSE:

Login

Enter user name and pass word

Verify user Go back to loginNO

YES

View course history

Course offered

Add course

Cannot select the course

Course added successfully

NO

YES

Check

prerequisite


25/27

DROP COURSE:

Login



YES

Course information and course offered

Drop course

Course drop successfully


26/27

ADMINSTARTOR ADD COURSES:

Login



YES

Ask I.D from student

View courses

No

Can't select the course

No

Yes Yes

Add course

Course added successfully

Ask student which

course to add


27/27

FACULTY VIEW SCHEDULE:

Login

Enter user name & password

Open faculty schedule

Check course timing from from faculty scdedule

Timing viewed successfully

Go back to loginNo

Yes

Verify user

baad project report

Documents