PowerPoint Presentation

A) PROJECT SUMMARY

PURPOSE

C) SCOPE

D) OBJECTIVEChapter - 1 INTRODUCTIONA) PROJECT SUMMARYThis is develop for maintain attendance of student and as well as faculty information. This system also include reminder to the parents for less attendance of student through the mail.B) PURPOSEThe purpose of developing attendance management system is to computerized the tradition way of taking attendance. Another purpose for developing this software is to generate the report automatically at the end of the session or in the between of the session.C) SCOPEThe scope of the project is the system on which the software is installed, i.e. the project is developed as a Desktop application, and it will work for a particular institute. But later on the project can be modified to operate it online.D) OBJECTIVESolve Problem of Searching Record: All the data easily can not search any record. User Friendly :This system does not provides user friendly interface and easy navigationLess Attendance Alert through SMS to the parents. We can easily filtering data.

Chapter - 2 PROJECT PLANNINGMilestones and Deliverables

B) Project Scheduling

C) Risk Management

Milestones and Deliverables

I have designed the new proposed system to the process of Internal Organization Management System. This will store all information about our system. It makes all record in security way so no person can make any change in a system. This record will be useful for other users instantly. The complete control of the project is under the hands of authorized person who has the password to access this project and illegal access is not supposed to deal with. All the control is under the administrator and the other members have the rights to just see the records not to change any transaction or entry. Admin Capable to Create and block New User.B) Project Scheduling

Gantte ChartProject SpecificationAnalysis of the projectDesign of project Coding2/7 to 10/8 11/8 to 17/11 18/1 to 28/3 1/3 to 20/3 21/3 to 21/5 Testing and Docu -mentationC) Risk ManagementIn contrast to software life cycle models, software process models often represent a networked sequence of activities, objects, transformations, and events that embody strategies for accomplishing software evolution. Such models can be used to develop more precise and formalized descriptions of software life cycle activities. Their power emerges from their utilization of a sufficiently rich notation, syntax, or semantics, often suitable for computational processing.

In the incremental model, there is a good chance that a requirements error will be recognized as soon as the corresponding software is incorporated into the system. It is then not a big deal to correct it. The waterfall model relies on careful review of documents to avoid errors. Once a phase has been completed, there is limited provision for stepping back. It is difficult to verify documents precisely and this is, again, a weakness of the waterfall model

The incremental model is an intuitive approach to the waterfall model. Multiple development cycles take place here, making the life cycle a multi-waterfall cycle. Cycles are divided up into smaller, more easily managed iterations. Each iteration passes through the requirements, design, implementation and testing phases.A working version of software is produced during the first iteration, so you have working software early on during the software life cycle. Subsequent iterations build on the initial software produced during the first iteration.Chapter - 3 SYSTEM REQUIREMENT STUDY

A)User Characteristics

B)Hardware and Software RequirementsA) User CharacteristicsAdmin: Can access all forms

Faculty: Can access Student, Attendance forms

Student: Can only show His/Her Attendance detailB) Hardware and Software Requirements

Requirement of the System:

Operating System: Microsoft Windows XP service pack 2 Front End: ASP.NET with C# Back End: SQL server Supporting-Tools: Microsoft word - Documentation Microsoft Power Point Presentation

H/W Specification:Processor:Intel Core2 Duo 2.20GHzRAM: 1GB DDR2 RAMHard Disk:Hitachi 320GB SATAChapter-4 SYSTEM ANALISYSA)Study of Current System

B) Problem and Weaknesses of Current System

C)Requirements of New System

D)Feasibility Study

> Technical Feasibility> Schedule Feasibility> Operational Feasibility> Economic FeasibilityA) Study of Current SystemThere is no computerized system for the attendance of student in the institute.All work and calculation are done through manually and data stored in paper.Current System does not provide facility to remind parents to automatically for their less attendance. B) Problem and Weaknesses of Current SystemNo user authenticationNo Backup and Restore Facility

C) Requirements of New SystemSolve Problem of Searching Record: All the data easily can not search any record. User Friendly :This system does not provides user friendly interface and easy navigationLess Attendance Alert through SMS to the parents. We can easily filtering data.

D) Feasibility Study

Technical Feasibility Development tool for our software is Language .net. Resources required for it are available and also the expertise. Research on Asset Management and Tracking has reached to the stage where it is technically feasible to implement it for real life application. The models for training application are developed and tested thoroughly by experts. Also those resources are available. So the proposed project is technically feasible.

Schedule Feasibility It is not important that the project gets completed, but its very important that it gets completed in allotted time. I had project duration of 4 months. As the work was divided into the 4 months, there was very good division of labor. As a result, the project within the allotted time period was possible. So my project is feasible with respect to schedule.

Operational Feasibility Once the software is developed, the work does not get over here. After the developers leave the company it should be easy to operate by the other members of the company for whom the software was developed. This demands a very good user interface to be implemented. As my project has got a very user friendly and an easy interface it can also be used by novice users after a bit of training. Moreover, the employees who are going to use my software are skilled professional so they will hardly find any difficulty in operation our software. So on and all it is totally feasible to operate my software with great ease.Economic Feasibility This feasibility is of utmost importance in development of any software for any particular company. The availability of the required hardware and software used to develop our project makes it economically very feasible. Moreover, the time duration in which the whole project is developed is appreciable. So it has indirect effect on the economy of the company, as a very good product is delivered in very less time. As our project almost removes any kind1 of manual work, the same Man power can be applied to some other work. So over all it is not only feasible economically but it also helps to increase the efficiency and profit making.

Chapter-5 SYSTEM DESIGN A)E-R Diagram B)Class Diagram C)Activity Diagram D)Use case Diagram E)Sequence Diagram

F)Context Diagram G)Data Flow Diagram (0 and 1 level)A) E-R Diagram

B) Class Diagram

C) Activity Diagram

D) Use case Diagram

E) Sequence Diagram

F) Context Diagram Student Attendance Management SystemFacultyGive Attendance DetailsTake Attendance /DetailsAdminGet Faculty/StudentDetailsManaged Faculty / StudentDetailsStudentSearch Attendance by AdmNoShow AttendanceG) Data Flow Diagram (0 and 1 level)

Chapter 6 DATA BASEAttendance

Batches

Faculty

Schedule

Student

SubjectAttendanceTable Name: AttendanceDescription: This Table is for fell AttendanceConstraint FieldName Primary Keyadate Candidate KeyPeriodCandidate KeyAdmnoFieldName Datatype Size Constraint AdateDatetime-Primary KeyWeeknoInt- Not Null PeriodInt-Candidate KeyFcodevarchar 10Not Nulladmno Int-Candidate KeyStatusChar1 Not Null RemarksVarchar50Not NullBatches

Table Name: Batches Description: This Table is for Country

Constraint FieldName Primary Key BcodeFieldName Datatype Size Constraint bcode Int - Primary Key BnoInt-Not Null Faculty

Table Name: Faculty Description: This Table is for Faculty Detail

Constraint FieldName Primary Key FcodeFieldName Datatype Size Constraint FcodeVarchar10Primary Key Pwdvarchar 10 -FnameVarchar50 -DeptVarchar50 -Schedule

Table Name: Schedule Description: This Table is for Schedul of time tableConstraint FieldName Primary Key WeeknoCandidate keyBcodeCandidate keyPeriodFieldName Datatype Size Constraint WeeknoInt - Primary Key bcode Int- Candidate KeyPeriodInt - Candidate KeyFcodeVarchar10Not NullScodeVarchar10Not NullStudent

Table Name: Student Description: This Table is for Student details

Constraint Field Name Primary Key AdmnoField Name Datatype SizeConstraint AdmnoInt - Primary Key bcode Int- Not Null SnameVarchar50Not NullSubject

Table Name: Subject Description: This Table is for Subject Detail

Constraint Field Name Primary Key ScodeField Name Datatype SizeConstraint ScodeVarchar10 Primary Key Snamevarchar 50 - Chapter 7 USER MANUAL

Home Page

Data Entry in Login Form

Invalid Username or Password

Successful Login

Change Password FormData Entry in Change Password Form

ValidationPassword Changed Successfully

Standard Master

Subject MasterAdd New Subject

Subject Stored Successfully

Record Navigation

Update DataRecord Updated

Record DeletedFaculty Master

Add New FacultyRecord Saved

Record Navigation

Student Master

Add New Student

Data Entry

Record Stored Successfully

Newly Stored Record in Gridview

Record Navigation

Update Record

Record Updated Successfully

ReportsFaculty Report

Student Report

Export Report to Word

Ask for Save

Stored Location

Word File

Faculty Login

Fill Attendance

Fill Attendance

Fill Attendance

Attendance Stored Successfully

Search Student

Student Found

Show Attendance of Selected Student

Old Attendance

Enter Search Criteria

Show Selected Attendance

Edit Attendance

Update Record

Attendance Updated

Faculties List

Student Side Search Attendance

Enter Student Admission No

Another Students Attendance

Chapter - 8 ADVANTAGES

Admin Can Add , Update and Delete details of Faculty and Student.

Faculty Can Add and Update Student Attendance And Search Student.Student can search their Attendance.

Chapter - 9 TESTING

Validation Mechanism We have used required field validators with those fields which are compulsory. Eg. Username, password, date of registration, book id, book name etc.We have used Compare field validators with those field which should be compared with another field. Eg. Password field We have used Regular expression validators with those fields in which input should be done in some specific manner like e-mail id, phone no, etc.

Security MechanismThere are mainly two types of user in our site. They areAdminFacultyTo identify which user can access which pages we have provided security for every page.We have used Forms mode in Authentication in web.config file.We have used special code which checks the user type at login time. And as per the type the pages will be available to the user of the website.We have also used session and cookies to store the detail of users login.We have used login related controls like login view, login status, login name, etc to maintain login detail.Proposed Enhancement

FUTURE ENHANCEMENTDue to time limitations we cant provide following facilities in our project:Online book purchaseOnline paymentOnline BillPay pal

Chapter - 10 CONCLUSIONS

Any work may not be always perfect. There may be some error or some defect in the work. We have taken enough care to make the project user friendly and more interactive. We have tried our level best to make the service useful and to provide maximum facility.

We hope that "Attendance Management System" will prove to be a boon for our users.

Any suggestion to make this project more useful is always most welcome.

Table

Table

System

FACULTY

Use Case

ADMIN

Login

Add/update student details

View student

Add/updateattendance

Marks/attendancereport

View marks report

Attendance Management System

Use Case

Fill Attendence

Attendence

Mail Attendence