baad project report

Post on 04-Jun-2018

212 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • 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)

  • 8/13/2019 Baad Project Report

    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.

  • 8/13/2019 Baad Project Report

    3/27

    USECASES

    DIAGRAM

  • 8/13/2019 Baad Project Report

    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

  • 8/13/2019 Baad Project Report

    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

  • 8/13/2019 Baad Project Report

    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

  • 8/13/2019 Baad Project Report

    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/13/2019 Baad Project Report

    8/27

    FLOW OF

    EVENTS

  • 8/13/2019 Baad Project Report

    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

  • 8/13/2019 Baad Project Report

    10/27

    Use case: add marks:

    Use case name Add marks

    Actor Administrator

    Description The use case describes theprocess of administrator

    adding marks of students

    Typical course events Actor action System responseStep 1:

    This use case initiated when

    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

    Assumptions None at this time

  • 8/13/2019 Baad Project Report

    11/27

    Use case: update schedule:

    Use case name Update schedule

    Actor Administrator

    Description The use case describes theprocess of administrator

    updating the schedule ofstudent and faculty

    Typical course events Actor action System responseStep 1:

    This use case initiated when

    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

    Assumptions None at this time

  • 8/13/2019 Baad Project Report

    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.

    Assumptions None at this time

  • 8/13/2019 Baad Project Report

    13/27

    Use Case: Add Course:

    Use case Name Add Course

    Actor Student

    Description The use case describedthe process of studentadd course.

    Typical Course

    EventsActor Action System Response

    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

    Assumptions None at this time

  • 8/13/2019 Baad Project Report

    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

    Typical course events Actor action System responseStep 1:

    This use case initiated when

    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

    Assumptions None at this time

  • 8/13/2019 Baad Project Report

    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

    EventsActor Action System Response

    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.

    Assumptions None at this time

  • 8/13/2019 Baad Project Report

    16/27

    CLASS

    DIAGRAM

  • 8/13/2019 Baad Project Report

    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