Academic management system PPT

1. ACADEMIC
MANAGEMENT SYSTEM
(AMS)
Presented By:
PAVAN DESHPANDE
NAGRAJ KANDUR
PRAKASH SINDHE
SATISH PATTEDAR
Guided By:
Prof. THYAGARAJU GOWDA

2. Abstract
2
Computers have become part of human’s life.
It makes the work easier compared to manually done.
Student Academic management system (SAMS) is a first phase centralized
management project.
Academic Management System software helps our college to maintain
information about students, Staffs, fees details, internal exam marks etc.

3. Objectives
3
1. The main goal of this software is to simplify the process of
information management in a particular college.
2. It helps the college to maintain the information about students,
staffs, fees details ,IA marks, Department details. Thus it helps the
college to maintain the records in a systematic order and also to
access details very quickly.
3. It can be implemented in all colleges to proceed the office works
smoothly.
4. Thus we can retrieve any details regarding student, staff, exams
etc. within a short interval of time. Thus we can make administers
task very easy as well as fast.

4. Project Outcomes
4
 Skills In Using Tools Such as Rational Rose(Design Tool) etc.
 Report Writing Skills.
 Formal way Developing The Software Product.
 Writing Industry Standard Code.

5. Project schedule
5
Project schedule
Task-No Duration(Week) Dependencies
T1 1-week
T2 4-week T1
T3 3-week T1,T2
T4 4-week T1,T2,T3
T5 2-week T1,T2,T3,T4
The project is divided into 5-tasks as below.
T1-Synopsis, T2-SRS,T3-Design,T4-Coding,T5-tesing.

6. Tools / Platform
6
Tools:
Software:
Hardware:
 Pentium IV & above
512 MB RAM & above
HDD 80 GB & above
Rational rose (Design Tool).
Dreemweaver8 and Net Beans.
IBM-DB2.
Platform:
JAVA(JSP).

7. Category
7
Academic Management System comes under RDBMS category.

8. 8
Architecture

9. Project Modules
9
1. Administrator
2. Student
3. Faculty
4. Department

10. Software Requirement Specification
10
This shows the abstract system specification.
Project Title: Academic Management System.

11. REQUIREMENT System Specification Abstract
R1 Access Security through “login and Password” and “role based privilege” of
accessing information in administrative, student, faculty, department.
R2 Allow department to register department name, department no, subject, subject
code, sem.
R3 Allow the department to organize the events.
R4 Allow the student to register course, sem, subject.
R5 Allow the faculty to register his/her details.
R6 Allow update status to administrator, faculty, and department.
R7 Allow student to view attendance detail and marks,
R8 Allow student to organize events, work shop.
R9 Allow department to organize events, work shop.
R10 Faculty should have option to maintain attendance, CAT- marks of student.
R11 Department should have option to prepare time –table and publish to notice board.
R12 Allow Department, faculty, administrator to generate report
R13 Web enabled application 11

12. Software Requirement Specification
12
This shows the detailed system specification.
Project Title: Academic Management System.

13. Functional Requirements
13
1. Login.
2. Department Registration.
3. Event And Workshop Organization.
4. Student Registration.
5. Staff Registration.

14. Functional Requirements
14
6. Updating.
7. Viewing Of Marks and Attendance By Students.
8. Maintenance of Attendance & Marks By Faculty.
9. Time Table Generation and Scheduling.
10. Report Generation.

15. 15
Intermediate
State
Start
State
End
State
Start
End
Basic Flow
Basic Flow
Alternate
State
Alternate
State
Flow Of Events
Alternative Flow Alternative Flow
Alternative Flow Alternative Flow

16. 16
N
N
M
N
N
1
1
1
N
N
1
1
1
N
Student
Faculty
Course
Department
Tech-Event
Exam
L-Name
USN
F-Name
DOB
M-Name
Address
E-name E-Id
E-Date
Score
Date
C-Name C-Code
Reg-noDate
C-Marks
T-attendance
F-Name
D-no D-Name
DOJ
Exprience
DOB
F-Id
Des
Enroll
Handel
Offers
Have
Result
Belongs
Attendance
Organize
E-date type
ER-Diagrams

17. 17
`
1 1 N 1
N 1
N
N M
N
N
N 1
N N N
1
1 1
N
N
1
1
1 1 1
N
Student
Faculty
Organize
Course
Department
Tech-Event
Exam
Result
Attendance
L-Name
USN
F-Name
DOB
M-Name
Address
E-name E-Id
E-Date
Score
Date
C-Name
C-Code
Reg-no
Date
C-Marks
T-attendance
F-Name
D-no D-Name
DOJ
Exprience
DOB
F-Id
Des
Enroll
Handel
Offers
Maintain
For
Is
Have
forGet
Belongs
Do
By
has
Has
Sem
E-Date
Type

18. 18
Update
Organize Events
Register Course
View Result
Register Department
Admin
Student
Register
Update
Delete
Organize events
Conduct Exam
LogIn
Faculty
Maintain Student Details
Use Case Diagram

19. 19
Class Diagram

20. 20
: Admin
System Database
1: Enter Correct UserName & Password
2: Get Details
3: QuerryFor Details
4: Data Obtained
5: Validation
6: LogInSuccessful
Sequence Diagrams
LogIn: Successful LogIn

21. 21
LogIn: UnSuccessfulLogIn
: Admin
System Database
1: Enters Invalid UserName & Password
2: Get Details
3: QuerryFor Details
4: Data Obtained
5: ValidationFailed
6: LogInFailed

22. 22
Registration:Succesful Registration
: Admin
System Database
1: Enter UserName & Password
5: Verification With Entered Data
6: LogIn Successfull
2: Get Details
3: Querry For Details
4: Data Obtained
7: Enters valid Details For Registration
8: Information Validation
9: Registering & Saving Data
10: Data Saved
11: Acknowledgement
12: Successfully registered

23. 23
Registration:UnSuccesful Registration
: Admin
System Database
1: Enters UserName & Password
2: Get Details
3: Querry For Details
5: Verification With Entered Data
6: LogIn Successfull
4: Data Obtained
7: Enters Invalid Details For Registration
8: Information Validation Failed
9: Registering & Saving Failed
10: Message To Enter Proper Details
11: Registration Failed

24. 24
For Further sequence Diagrams
Click Here

25. 25
Activity Diagram
LogIn
Enter User Name &
password
User Interact With System
Accepted
System Displays
Error Message
Rejected
LogIn
Successfull

26. 26
Enter Rgistration
Details
Save Datails
Valid Information
Saving
Failed
Invalid Information
Registered
Successfully

27. 27
For Further Activity Diagrams
Click Here

28. 28
Front End Design

29. 29

30. 30

31. 31

32. 32

33. 33

34. 34

35. 35

36. 36

37. 37

38. 38

39. 39

40. 40

41. 41

42. 42

43. 43

44. 44

45. 45

46. Conclusion
46
 This application can be utilized for making institution
work easier .
Information management can be done efficiently.
This helps the college to maintain records in a systematic
order and also to find the details very quickly.

47. Future Application
47
In future we can Host this application into Google
App engine.

48. References
48
WEB Site:
www.slideshare.net
EBook’s:
Servlet and JSP Programming with IBM WebSphere
Studio and VisualAge for Java(ibm.com/redbooks).
The complete reference java (Herbert Schildt).

49. 49