Development of admission management system

Presentation on
Development of Admission Management
System
Presented by
Alok Datta
ID: 12103026
Program: BCSE

Contents of The Presentation
• Project Overview
• Requirements Engineering
• System Planning
• Analysis & Design
Sunday, November 29,
2015
2

Project Overview
2015
3

Introduction
• Admission Management System is a desktop-base application built with
the aim of computerizing the admission procedure in colleges. The system
proposed here incorporates handling and management of multi-
departmental and multi-divisional system that includes various daily
activities in the system.
2015
4

Specific Objectives
• Making a student organization.
• To store all the information to initiate all the processes.
• To design desktop based Admission system.
• Identifying the problems to develop the system.
• Designing a effective user interface.
• To build up a system with advance technology.
2015
5

Software Development Process Model
2015
6
waterfall model

Requirements Engineering
2015
7

Functional Requirements
• Log in management
• Admission Form management
• Manage Student Information
• Manage Teacher Information
• Manage Update and Delete assessment process
• Manage Account
• Viewing Report
2015
8

Non-functional Requirements
• Admin can update a user, and delete a user.
• Strong and effective searching system for efficient access to any
accounts information.
• A dashboard with all the functionality where admin can found any
option easily.
• Strong security system for better support.
2015
9

Use case Diagram
2015
10

System Planning
2015
11

Functions of Proposed System
Functions Synonym
Log in F1
Student Admission form F2
Teacher Admission form F3
Student info F4
Teacher info F5
Update F6
Delete F7
Account info F8
Report F9
Setting F10
2015
12

Function Oriented Metrics
• Number of external inputs – Each user input that provides distinct
application-oriented data to the software
• Number of external outputs – Each user output that provides
application-oriented information to the user
• Number of external inquires – An inquiry defined as an on-line input
that results in the generation of some immediate software response in
the form of an on-line output. Each distinct inquiry counted
• Number of internal logical files – Each logical internal file is a logical
grouping of data that resides within the application’s boundary
• Numbers of external interfaces – All machine-readable interfaces that
used to transmit information to another system.
2015
13

FP Count
Information Domain Value Optimistic Most Likely Pessimistic Estimated Count Weight FP Count
Number of External Inputs
3 2 4 2.5 3 7.5
Number of External Outputs
2 2 3 2.167 4 8.6
Number of External Inquiries 3 3 3 3 3 9
Number of Internal Logical Files 4 3 4 3.33 7 23.31
Number of Interfaces 3 3 3 3 5 15
Count Total = 63.49
2015
14

Complexity Adjustment Value
Complexity Adjustment Factor (Fi)(=1-5) Value
1 Dose the System require reliable backup &recovery? 3
2 Are communications required? 5
3 Are there distributed processing system? 2
4 Is performance critical? 3
5 Are the system existing operational environment? 2
6 Does the system require on-line data entry? 0
7 multiple screens 3
8 Are master file uploaded on-line? 0
9 Are the information values complex? 3
10 Is the internal processing complex? 3
11 Is the code design for the reusable? 4
12 Are the conversation/installation included in design? 2
13 Is multiple design for change? 3
14 Is the application design to facilitate change and case? 2
Total value of Fi () = 35
2015
15

FP Based Estimation
• FP = Count Total * [0.65 + 0.01 * Σ (Fi)]
=63.49* [0.65 + 0.01 *35 ]
=63.49
• Final Estimation
Effort = FP / total no. of functions
= 625.08 / 10
= 62.508
TIME = 63 man month (Approximate)/15 (organizational
productivity)
=4 months
2015
16

Process Based Estimation
2015
17

TIME ESTIMAION
• FP Based estimation = 4 months
• Process Based estimation = 3 months
• In Average Estimated time = 3.5 months
• Software development team = 15 members
Sunday, November 29, 2015 18

Effort Distribution
2015
19

Detailed Effort Distribution
• Requirement gathering
and refinement 40%
• Quick design 20%
• Building prototype 30%
• Customer evaluation of
prototype 10%
2015
20

Project Scheduling Chart
2015
21

Cost Estimation
2015
22
Salary
System Analyst
CC
Planer
Risk Analyzer
system Designer
Coder
Tester
Technical Communicators
20000
8000
10000
7000
15000
13000
10000
6000
Total= 89000

Analysis & Design
2015
23

Activity Diagram for Add Student
2015 24
Student Not Added
Add Student Form
Student Added
Required info
provided ?
yes
No

Activity Diagram for Add Teacher
2015
25
Teacher Not Added
Add Teacher Form
Teacher Added
Required info
provided ?
yes
No

Activity Diagram for Manage Account
2015
26
Account Form
Account info
Get Account Form
Select any one
yes
No
Get Account Clearance Give Data
yes No
Account not Completed

Context-level DFD
2015
27

First Level DFD
2015
28

Level 2 DFD Process 1(Login Management)
2015
29

Level 2 DFD Process3 (Manage Admission)
2015
30

Level 2 DFD Process 4(Student Information)
2015
31

Level 2 DFD Process 5(Manage Teacher)
2015
32

Level 2 DFD Process 6 (Manage Account)

ER Diagram
2015
34

Software Demo
2015
35

Conclusion
• Computer World BD provides me the chance of working in a
professional working environment. During the internship
period I have tried my level best to make my system efficient.
I followed the lessons, methods, tools and techniques that I
have learned during my study period at IUBAT. Successful
software development is a blend of standard development
practices, proper theoretical knowledge and the developer’s
creativity.

Development of admission management system

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Development of admission management system

Similar to Development of admission management system (20)

Recently uploaded

Recently uploaded (20)

Development of admission management system