Beruflich Dokumente
Kultur Dokumente
PROJECT REPROT
ON
“AUTOMATION MANAGEMENT SYSTEM”
Submitter for the partial fulfillment of the degree
Of
Bachelor of Technology
In
COMPUTER SCIENCE
Submitted by
Manish Kumar Kushwaha
And
Manish Sharma
(RAJDHANI COLLEGE, UNIVERSITY OF DELHI)
(NEW DELHI)
Acknowledgement
I would sincerely like to thank for the constructive criticism, support, encouragement, valuable
comments, suggestions, timely helps and many innovative ideas given to me by my project
supervisor Mrs. Diksha Grover in carrying out the project and the report.
I must convey my gratitude to Mrs. Diksha Grover for giving me the constant source of
inspiration and help in preparing the project, personally correcting my work and providing
encouragement throughout the project.
I also thank all my faculty members for steering me through the tough as well as easy phases of
the project in result oriented manner with concern attention.
Index
Table of contents:
I. Problem statement
V. Effort Estimation
IX. Testing
Basis Path Testing
X. Bibliography
Problem Statement
Today all works at the time of the admission of the students is done manually by ink and paper,
which is very slow and consuming much efforts and time. It is required to design of the
computerized Automation Management system, to speed up and make it easy to use system.
The present system is the manual one. Hence all the information about the student and faculty
details maintained in the files. The whole session attendance is stored in the registers and at
the end of the session the report are generated. It becomes very difficult to generate the report
in the middle of the session or as per requirement because it takes more time in calculation. At
the end of the session the student who don’t have 75% attendance are get a notice. It is unfair
to those students if they would have short attendance so that they could take regular classes.
The ‘Automation Management System’ software overcomes this problem since the data is
stored in computer using DBMS, we can retrieve the record of any student whenever we
requires it. It also reduces the manpower needed to perform the entire admission and
administration task by reducing the paper works needed.
Process Model
The Process Model used in our projects “College Management System” is waterfall model.
The waterfall development model originates in the manufacturing and construction industries:
highly structured physical environments in which after-the-fact changes are prohibitively costly,
if not impossible. Since no formal software development methodologies existed at the time,
this hardware-oriented model was simply adapted for software development.
Diagram:
Ans. Yes.
Q2. Are estimates (e.g. size, cost, and schedule) documented for use in planning and
tracking the software project?
Ans. Yes, because the without estimates our software will not developed before the given
deadline.
Ans. It is the organizational software so answer is obviously yes to build a good quality
software.
Q4. Has your organization developed and does it maintain a standard software process?
Ans. Yes.
Q5. Does your organizational policy allows you to update or modify the software by taking
uses feedback?
Ans. No.
Q6. Are the activities for managing software quality planned for the project?
Ans. Yes.
Q7. Do the new technology have some effect on quality and productivity?
Ans. Obviously Yes, but we are making component based software so any changes can be
managed easily.
Q8. How much pressure it puts on you to develop a cost effective, reliable software in a
limited amount of the time and how you handle this?
Ans. Not very much, because we will not include any unnecessary features so that it will be
cost effective and developed in given time.
Interview
Q1. Do you want restore and backup property in the software?
Ans. Yes.
Q2. What kinds of the interface you expects from this software?
Ans. It should be simple and user friendly. So that a common person or student can operate
it easily.
Q3. Can you provide any kinds of suggestion to reduce its cost?
Ans. If the system works efficiently then, cost doesn’t matter. But yeah you can reduce cost,
by not imposing extra taxes and not adding unnecessary features.
Q4. Do you want online support in your system or should ewe design it for offline works
only?
Ans. No, we do want this software to work online. So that student and faculties access it
from anywhere.
Ans. No, software should work on most of the common operating systems. It should have
latest technology
Software Requirements Specification (SRS)
I. Introduction
Purpose
Scope
Need for the proposed system
User Interface
Hardware Interface
Software Interface
Communication Interface
Memory Constraints
Operations
Site Adaption Requirements
Product Functions
Constraints
Assumptions
User Interface
Hardware Interface
Software Interface
Software System Attributes
Introduction:
Today all the work at the time of admission of the students is done manually by ink and paper,
which is very, slow and consuming much efforts and time. It is required to Design of
Computerized Automated Management System, to speed up and make it easy to use system. It
reduces the manpower needed to perform the entire admission and administration task by
reducing the paper works needed. The main goal of the system is to automate the process
carried out in the organization with improved performance and realize the vision of paperless
work.
1. Purpose:
Its purpose is to automate and centralize the whole system of the department. We are
attempting to improve our existing system that runs on pen and papers. The main goal of the
system is to automate the process carried out in the organization with improved performance
and realize the vision of paperless works.
2. Scope:
It is more efficient and convenient for the colleges. It reduces the manpower needed to
perform the entire administration task by reducing the paper works needed. If all the work is
done by the computer there will be no chance of errors.
Moreover storing and retrieving of the information is easy, so work can be done speedily and in
time.
Admin Details
User
Get info
Manage Data
AMS
Report
Level 1DFD
Admin
Verified
User ID
And Authent ic ation Checking ID Login Info
Passwor d
Remove Modifying
Removing Entry
Removing Enr ty Updating Entry
Updating Entry
Repor t Generated
Repor t Details
Level 2 DFD
View Info
Faculty info
Student info
Checking info
Details
Details
Details Details
Viewing Attendanc e
In system engineering use cases are used at a higher level that within software engineering,
often representing missions or stakeholders goals.
Usecase
Use case1: 1:Update
Updateananentry
entryofofthe
thestudent.
student.
PrimaryActor:
Primary Actor:Admin
Admin
Precondition:Admin
Precondition: Adminhas
haslogged
loggedin.in.
MainSuccess
Main SuccessScenario:
Scenario:
1.1. Admin
Adminchecks
checksallallthe
thepreviously
previouslyfilled
filleddata.
data.
2.2. Admin
Adminretrieve
retrievethe
thestudent
studentdata
datawhich
whichisismeant
meanttotoupdate.
update.
3.3. Admin
Adminupdated
updatedthe theselected
selectedstudent
studentdata
datafrom
fromthe
thedatabase.
database.
4. System confirm the modification.
4. System confirm the modification.
ExceptionScenario:
Exception Scenario:
-2a)There
-2a) Thereisisnonosuch
suchstudent
studentdata,
data,which
whichthe
thesearched
searchedfor.
for.
System
Systemshows
showserror
errormessage.
message.
Calculating FP:
Consider the value of the above question be simple.
Weighting Factor
Information Count Simple Average Complex
Domain Values
External Inputs (EIs) 2 x 3 4 6 6
External Outputs (Eos) 1 x 4 5 7 4
External Inquiries (EQs) 6 x 3 4 6 18
Internal Logical Files (ILFs) 2 x 7 10 15 14
External interface Files (EIFs) 2 x 5 7 10 10
Count Total: 52
∑ (Fi ) = 45,
And project FP is 57.2.
Effort Estimation
Work effort is the labor required to complete an activity. Work effort is typically the
amount of focused an uninterrupted labor time required to compute an activity.
FP-based Estimation:
Decomposition for FP-based estimation focuses on information domain values rather than
software functions.
FP estimated =57.2
The organizational average productivity rate for system of this type is 6.5 FP/pm.
An estimate of the project effort is computed using:
= 57.2/6.5
= 8.8
Time Line Chart
Risk Table
Risks Category Probability Impact
Size estimate may be significantly low PS 60% 2
View info
Remove Modify
View details
User
Print Report
View info
Generate report
Basis Path Testing
Basis path testing, or structured testing, is a white box method for designing test cases. The
method analyzes the control flow graph of a program to find a set of linearly independent paths
of execution. The method normally uses cyclomatic complexity to determine the number of
linearly independent paths and then generates test cases for each path thus obtained. Basis
path testing guarantees complete branch coverage (all CFG edges), but achieves that without
covering all possible CFG paths—the latter is usually too costly. Basis path testing has been
widely used and studied.
To measure the logical complexity of our software we consider the following procedure:
void view_info(){
cout<<"Select option: \n";
cout<<"1.Student info.\n";
char ch;
cin>>ch;
if(ch==1){
cout<<"1.Student Profile.\n";
cout<<"2.Student Performance.\n";
cout<<"3.Attendance.\n";
cout<<"4.Fee details.\n";
char ch;
cin>>ch;
if(ch==1){
obj.profile();
}else if(ch==2){
obj.perfrm();
}else if(ch==3){
cout<<"Attendance: ";
obj.attendance();
}else{
obj.pay();
}
}else{
cout<<"1.Profile\n";
cout<<"2.Working Days\n";
char ch;
cin>>ch;
if(ch==1){
cout<<"Profile";
obj.profile();
}else{
cout<<"Working Days";
obj.wday();
}
Flow Graph of the above procedure:
11 3
4
12
6 5
14 13
8 7
10 9
15
Cyclomatic complexity: Cyclomatic complexity V (G) for a flow graph G is defined as
V (G) =E-N+2
=19-15+2 = 6
Path 2: 1-2-3-4-6-7-15
Path 3: 1-2-3-4-6-8-9-15
Path 4: 1-2-3-4-6-8-10-15
Path 5: 1-2-11-12-13-15
Path 6: 1-2-11-14-15
Test Cases:
Test Requirements Test cases Test Data Result
Scenario
All correct Check response Username:mohit0749 Login
Check Login combinations on entering valid Password:temp@123 successful
Functionality entered in username and
login/password password.
field will let user in. Check response Username: MOHIT username
All other on entering Password: temp is invalid
combinations will invalid username
be rejected. and password.
Login includes Check response Username: Username
minimum 8 letters when username Password: and
and 4 digits/special and password password
characters or both field is empty invalid
(except space and login button
character). is pressed.
Login is not case
sensitive.
Password cannot
be less than any 8
characters (except
space character).
Password is not
case sensitive.
“Login in “button is
disable unless both
fields typed in.
Screen Shots
Admin Section:
Username:
Password:
Login
Search
Student
Faculty Select Course: None
XYZ
Enter Student name:
1234
Enter Student Roll No.:
Find Cancel
Automation Management System
Profile Attendance Performance Fee details
Details
Name: XYZ
Father Name: ABC
Mother Name: DEF
Course: B.tech computer Science
Year: Second
Change Photo Roll No.: 1234
Mob. No.: +91-1234567890
Address: New Delhi
Edit Remove
User Section:
Automation Management System
http:/ / www.mysite.edu/ ams/ ams.php/
Student
Faculty Select Course: All
XYZ
Enter your name:
1234
Enter Your Roll No.:
Submi
t
Details
Name: XYZ
Father Name: ABC
Profile
Attendance
Performance
Fee details
Bibliography
Books
[1] R.S. Pressman, Software Engineering: A Practitioner’s Approach, McGraw-Hill, Ed 7, 2010.
[2] P. Jalote, an Integrated Approach to Software Engineering, Narosa Publishing House, Edition
3, 2011.
Other References
[1] https://en.wikipedia.org/
[2] https://www.google.co.in/
[3] https://creately.com/