Mobile Phone Based Attendance Tracking System Essay Sample
In bing system. professor takes the attending and enter the inside informations of absentees or presenters through UMS. The computation of student’s attending each twenty-four hours and the per centum is done automatically. The Attendance Section of the UMS helps the pupils and staff to maintain a regular path of their attending. The pupil can look into his/her up to day of the month aggregative attending every bit good as class wise attending as and when required. The parents can besides see and look into their ward’s attending position on regular footing. But chief job is with extra characteristics that UMS provides i. e. a characteristic for Mobiles in the signifier of humanoid or window apps but that is merely for android compatible Mobiles. Though many pupils presents are utilizing humanoids based Mobiles but still many are there which do non utilize such engineering Mobiles. EXISTING SYSTEM Introduction LPU promotes a civilization of paperless University. The twenty-four hours to twenty-four hours disposal and most of the University processs are carried out online.
The University Management System ( UMS ) . an on-line portal of University. is one such advanced measure of the University to supply critical information sing faculty members and other University logistics for helping the University pupils. their parents and the staff. The bing system which is operational and is similar to our undertaking is the LPU Apps which works on assorted different platforms like Windows. Android and Iphone. These applications are available on our University Management System web site. Through these applications we can see our assignments. attending. time-table. consequence etc. In our undertaking which we are developing through the aid of JavaMe. we are developing an application which can run on any Java compatible phone irrespective of the phone’s operating system. In this application we will be taging the attending and besides sing the attending through any Java compatible phone. Existing Software University Management System ( UMS ) is a big database system which can be used to pull off. maintain and procure our university’s twenty-four hours to twenty-four hours concern. The UMS can be accessed through the UMS Login available on the University web site by logging in utilizing the Username ( pupil Registration Number in instance of pupils and parents ; and Employee ID in instance of staff ) and the Password.
For login: • The pupils should come in their Registration figure as Username and the watchword. • The Staff should come in their Employee ID as Username and the watchword. In instance of the application provided for the phone based environment named “LPUTouch” which runs on Io. Android and Windows phone. First the login page comes when we start the application. After logging in as an attested user we can entree our attending. position Markss and see our clip tabular array. What’s new in the system to be developed In the bing system the application has merely been designed for platform like Windowss. humanoid and Io. It does non work on any other phone. But the application which we have designed can run on any Java enabled device irrespective of the type of OS the phone is running. therefore widening the usage of this application. Our undertaking is based on J2ME engineering. PROBLEM ANALYSIS In this stage we analyze the bing system/product looking for their strength and failings. For bing we have already mentioned above the assorted jobs with the system. i. e. . it is excessively feverish to be handled.
For illustration everything involves paperwork like if we need to look into the old records of the vehicles entered in the premises for the parking so it normally involves direction operating expenses and registries to manually scroll through every page and entry to make a peculiar record. Whereas in the proposed system the full database would be maintained online we merely have to do a question from the user interface. Product Definition Mobile phone based attending tracking system is a J2ME Application developed by utilizing Midlets and JDBC. It is a nomadic app used for taging attending. updating attending records of pupils. and easy care of record maintaining. Feasibility Analysis A feasibleness survey of a system proposal is harmonizing to its workability. which is the impact on the organisation. ability to run into their user demands and effectual usage of resources. Therefore when a new application is proposed it usually goes through a feasibleness survey before it is approved for development. Some of import characteristics that are to be considered for the feasibleness analysis are: 1. Technical Feasibility – The system must be evaluated from the proficient point of position foremost. The appraisal of this feasibleness must be based on an outline design of the system demand in the footings of input. end product. plans and processs.
The undertaking should be developed such that the necessary maps and public presentation are achieved within the restraints. Our undertaking is developed utilizing Java/J2ME and JSP and therefore it is technically executable for development. 2. Economic Feasibility – The development system must be justified by cost and benefit. Since the system is being developed as portion of undertaking work. there is no manual cost to pass for the proposed system. Besides all the resources are already available. it give an indicant of the system is economically possible for development. Our undertaking is an app so economically executable. 3. Behavioral Feasibility – In this we focus on the client support that whether the proposed system is sufficient to back up the demands.
Our undertaking has taken attention of many client ( student-teacher ) needs. Undertaking Plan The undertaking aims in implementing package that helps professor to take the attending utilizing nomadic phone. For this nomadic must back up Java application. This undertaking is based on J2ME engineering. Professor enters the attending to the nomadic utilizing computer keyboard. It is a manual procedure. After salvaging the absentees or presenters in to the Mobile. teacher can redact the attending list in the Mobile. And this attending inside informations can direct to a computing machine through servlets. After directing the files to a computing machine. attending of pupils gets updated automatically. The undertaking is divided into different subdivisions or faculties. to pull off these all platforms and the database association with them. our squad has the undermentioned people working on different faculties: ? ASHISH NIVHAL: Connectivity Module
? GURBEER KAUR: Database Module ( BACK END )
? SUMIT SINGH: User Module ( FRONT END )
? ABHAY NATH: User Module ( FRONT END )
? SANJEEV KUMAR: Database Module ( BACK END )
As the undertaking is in J2ME. for front terminal we will be utilizing midlets as an interface for user for bringing informations and demoing consequences. The back terminal is oracle xe for storage intent. The connectivity between these terminals has been done through JDBC. Software REQUIREMENTS
? Platform: Windows or Linux
? Language/Technology: J2ME
? Development tools: JDK 1. 5 or subsequently. WTK 2. 5 or subsequently
? Database used: Prophet Xenon
? Technologies used: JSP. JDBC.
? Web Server: Glassfish Server 3. 1. 2 ( Apache Tomcat 5. 5. 9 ) Design
System design is design of constituents. architecture. faculties and interfaces of the system. It covers the design of each faculty and its working in brief through Flow charts. Data flow diagrams. The information flow diagram of our undertaking is as shown below
1. LOGIN TYPE
a. MARK ATTENDANCE: For instructors to tag attending of pupils b. GET ATTENDANCE: For pupils to look into out their attending c. ADMIN: For admin to make alterations in database
a. USERNAME: For now it is same for all instructors i. e. ”Teacher” but in future alterations can be made B. Password: As set by admin can be changed seasonably. instructors will be informed about alterations explicitly 3. Section Choice
For choosing among all the subdivisions. which section’s attending instructor want to tag. 4. ATTENDANCE
This will dwell of attending sheet with pupils name to tag the attending 5. Database
For storage intent. all the attending to be saved in this. all pupils attending records are updated etc. . Testing
Software proving is more than merely error sensing. Testing package is runing the package under controlled conditions. to ( 1 ) verify that it behaves “as specified” ; ( 2 ) to detect mistakes. and ( 3 ) to formalize that what has been specified is what the user really wanted. 1. Confirmation is the checking or testing of points. including package. for conformity and consistence by measuring the consequences against pre-specified demands. [ Confirmation: Are we constructing the system right? ]
2. Mistake Detection: Testing should deliberately try to do things travel incorrect to find if things happen when they shouldn’t or things don’t go on when they should. 3. Validation looks at the system correctness – i. e. is the procedure of look intoing that what has been specified is what the user really wanted. [ Validation: Are we constructing the right system? ]
Functional testing is a proving technique that ignores the internal mechanism of the system and focuses on the end product generated against any input and executing of the system. It is besides called black box testing because it is non concerned about codification. Black box testing is frequently used for proof. Functional Testing covers the undermentioned focal point countries:
? Mainline map: Focuss on proving the chief maps of the application. Because of this. mainline map proving frequently overlaps with other Functional Testing focal point countries. ? Error conditions: Testing for mistake conditions uses inputs that are outside of the range of valid parametric quantities and pervert from usage instances. This includes researching boundary conditions. driving error waies. and exposing all mistake messages. ? Recovery: The intent of recovery testing is to guarantee that the recovery map meets the recovery demands. Recovery demands stipulate how an application recovers from an mistake. ? Basic serviceability: Functional Testing does non include formal serviceability proving. but all Functional Testing examiners are expected to watch for and describe obvious serviceability jobs that clients might meet when seeking to utilize the merchandise. ? Vulnerability: Functional Testing examiners must analyze and verify all of the security elements designed into the system. in the same manner the mainline maps are tested. ? Arrested development: Trial instances for of import maps are rerun at appropriate points in every release. even if the functionality was unchanged since the last clip the trial was run. A trial instance might besides be rerun one time a hole is applied to verify the hole. This re-verification of old trial instances is called arrested development proving. Structural Testing
Structural testing is a proving technique that takes into history the internal mechanism of a system. It is besides called white box testing and glass box proving. It is used for the confirmation. Degree of Testing:
1. Unit of measurement Testing
Unit of measurement testing is a process used to formalize that a peculiar faculty of beginning codification is working decently. The process is to compose trial instances for all maps and methods so that whenever a alteration causes a arrested development. it can be rapidly identified and fixed. Benefits: The end of unit testing is to insulate each portion of the plan and show that the single parts are right. Unit proving provides a rigorous. written contract that the piece of codification must fulfill. As a consequence. it affords several benefits: a ) Facilitates Change
B ) Simplifies Integration
degree Celsius ) Documentation
vitamin D ) Separation of Interface from Implementation
2. Integrated Systems Testing
Integrated System Testing ( IST ) is a systematic technique for formalizing the building of the overall Software construction while at the same clip carry oning trials to uncover mistakes associated with interfacing. The aim is to take unit tested faculties and prove the overall Software construction that has been dictated by design. IST can be done either as Top down integrating or Bottom up Integration. 3. System Testing
System proving is proving conducted on a complete. incorporate system to measure the system’s conformity with its specified demands. System proving falls within the range of Black box proving. and as such. should necessitate no cognition of the interior design of the codification. System proving is really done to the full system against the Functional Requirement Specifications ( FRS ) and/or the System Requirement Specification ( SRS ) . Furthermore. the System testing is an fact-finding testing stage. where the focal point is to hold about a destructive attitude and trial non merely the design. but besides the behavior and even the believed outlooks of the client. It is besides intended to prove up to and beyond the bounds defined in the software/hardware demands specifications. Staying All Testing Models comes under System Testing 4. User Acceptance Testing
User Acceptance Testing ( UAT ) is performed by Users or on behalf of the users to guarantee that the Software maps in conformity with the Business Requirement Document. UAT focuses on the undermentioned facets ? All functional demands are satisfied.
? All public presentation demands are achieved.
? Other demands like transportability. compatibility. mistake recovery etc. are satisfied. ? Acceptance standards specified by the user is met.
The undertaking has been divided into following faculties:
1. User Faculty:
The chief intent of the user faculty is to supply security. This faculty is specially designed for staffs. which use nomadic phone to take attending. Each staff enter username and watchword before enter in to attendance list. If username and watchword can non fit. he/she can’t enter in to attendance page. It is besides for pupils who need to cognize their attending.
2. Attendance Entry Module:
The intent of Attendance Entry Module is to tag the attending utilizing cell phone. In this faculty Lecturer takes the attending utilizing the cell phone. Lectors select the subdivision. After this session he enters in to attendance page. Here staff makes a grade on the absentees. 3. Connectivity Faculty:
The chief map of this faculty is it sends attendance list to the waiter database. In this faculty connectivity is made between front terminal & A ; back end i. e. database. 4. Updating the Database Module:
The first map of this faculty is to update the attending list from the cell phone. When the attending list from the cell phone receives. server automatically updates its database. The waiter updating the database whether any alteration from cell phone occurred. 5. Display Faculty:
The Displaying attending list Module trades with the WEB application of J2ME. In this faculty Students can see their attending through this app. Student must supply their enrollment figure so they get their attending.
1. hypertext transfer protocol: //j2mesamples. blogspot. com/2009/02/database-connection-using-j2me. html 2. hypertext transfer protocol: //www. roseindia. net/j2me/check-box. shtml
3. hypertext transfer protocol: //www. youtube. com/watch? v=YbXmFp8wRDw & A ; feature=related 4. hypertext transfer protocol: //docs. prophet. com/cd/B14099_19/wireless. 1012/b13819/j2meprov. htm 5. hypertext transfer protocol: //www. zimbra. com/forums/zimbrame-j2me-client/20004-how-resolve-javax-microedition-io-connectionnotfoundexception-tcp-exception. hypertext markup language