School APPROVAL This is certified that we have

 

 

 

 

School Attendance Monitoring System

 

Session (2014-2018)

 

Program

Bachelors of Business and Information Technology (BBIT)

 

Submitted By:

Rashid Iqbal                                            2014-KIU-0142

 

Supervised By:

Lecturer Esma Wali

Assistant Professor Computer Sciences

 

___________________________________________________

KARAKORUM INTERNATIONAL UNIVERSITY

GILGIT, BALTISTAN

 

CERTIFICATE OF APPROVAL

This is certified that we have read and checked the work contained in the report as a confirming to the required standard for the partial fulfillments of the degree BBIT (Hons) 2014-2018.

It is our judgment that project is up to the standard to warrant its acceptance to the Karakorum International University for the Degree of Information Technology.

 

 

 

 

Project Supervisor                                                                   ­­­­­­­­­­­­____________________

                                                                                                 Lecturer Esma Wali

 

           

 

Chairperson/Chairman/HOD                                                  ____________________

Dr. Aftab Ahmed Khan

 

External Examiner                                                                  ____________________

 

DEDICATION

 

I am dedicating this project to my great parents who provided me favorable environment for studies, though out my life.Secondly,I am grateful for the such friendly environment that has been given to us within out tenor in University. 

 

 

ACKNOWLEDGEMENTS

 

First of all I would like to widen my sincere and unassuming thanks to Almighty ALLAH who gifted me knowledge, skills and abilities to make solid contribution to the already existing ocean of knowledge. I am very thankful to the following persons who encourage me and be cooperative with me to attain this stage academic carrier.

I am also deeply grateful to all the Faculty of Information technology and Computer Science, for providing constant guidance.

Finally, thanks to my loving parents, who provided me every suitable support both morally and financially and always prayed for me without their prayers and Allah’s blessings, it was impossible for me to complete my project.

Thank you all so much.

 

ABSTRACT

School Attendance monitoring system is mainly concerned with conversion of manual system into Computerized System (Web and Android).

In this system, I am maintaining the records of Attendance of Faulty and also provides Reporting feature.

This system also provides information about faculty; friendly screens and strategies for minimization of typing make this system efficient.

The tool used for the System designing is Java, XML, HTML, CSS and JavaScript.

This software will greatly reduce their spending and will provide them with a timely and accurate assessment of the organization.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

TABLE OF CONTENT

Part I (The Android Application)

CHAPTER 1: INTRODUCTION TO I-GUIDE

1.1  Project Aim:…………………………………………………………………………………………………… 2

1.2  Objective:………………………………………………………………………………………………………. 2

1.3  Scope of the project:…………………………………………………………………………………….. 2-3

CHAPTER 2: CORE FEATURES

2.1  Registeration:…………………………………………………………………………………………………. 4

2.2  SMS Scheduled……………………………………………………………………………………………… 4

2.3  Creating Group……………………………………………………………………………………………. 5-6

CHAPTER 3: PERFORMANCE

3.1  Issues……………………………………………………………………………………………………………. 7

3.2  Solutions……………………………………………………………………………………………………….. 7

 

CHAPTER 4: FUNCTIONS READY TO BE USED

4.1 Customization…………………………………………………………………………………………………. 8

4.2  Implemented Functions…………………………………………………………………………………… 9

CHAPTER 5: FUTURE PLANS —————————————————————–10

 

PART II (The Web Application)

CHAPTER 6: INTRODUCTION OF THE WEB APPLCATION

6.1  JSP.Net Application……………………………………………………………………………………… 13

CHAPTER 7: MAJOR SECTIONS————————————————————–14

 

PART III

CHAPTER 8: RESULTS ———————————————————————–16

CHAPTER 9: CONCLUSION—————————————————————-17

REFERENCES ———————————————————————————18

SOURCE CODE FOR FUTURE WORK————————————————–19

 

Chapter 1

Introduction to SMS android application

1.1 Project Aim

This Software Stack is developed for monitoring attendance of Schools. This software can be used to view both Schools and Teachers profiles. The basic aim of this Software Stack is to monitor faculty attendance on daily, weekly and monthly basis.

1.2     Objective

The ultimate objective of SMS is to monitor the attendance of schools and faculties and to make school systems better The SMS (attendance) provides an innovative solution for Today’s school attendance record-keeping challenges. This software will give institutes room to handle their responsibilities whether they’re just starting or are an experienced professional.

SMS opens a universe of opportunities to automate the laborious paperwork involved in proper school attendance management. With our proposed record keeping software the management can more increase faculty response, attendance character for success.

1.3     Scope of the project

This project has wide scope on educational department by using this Software Stack one can mark attendance and can get reports daily, weekly and monthly.

This project can be beneficial for Government of Gilgit Baltistan especially for the department of Education as it convert the whole manual attendance and digitalize it.which actually cause the secure system of attendance which is efficient and fast for comparative to  the manual system. Apart of this it remove the fake attendance if exist which have directly impact on learning’s of  students.

Secondly,it can be launched by the private group of school to manage or ensure the presence of faculty in school.So, it make true impact on nations carrier.Hence, this will result positive impact upon the educational system and if government rely on this it will remove the huge burden of insecure paper work into secure system.

 

The app admin can mark teacher attendance and can add Faculty members using the android app. This application will be helpful to the all type of education institutes (schools and colleges).The web admin can monitor and search for different institutes on the basis of names, category and district.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter 2

 Core Features

2.1   Creating and Modifying Faculty profiles. 

Using the application one can add, edit and remove faculty members. This app contains User Interface for CRUD operation that can be applied to the faculty. The web app only provides facility to edit school profile not faculty profiles. Web app can create and modify the Institute information.

2.2    Profile Overview

The Web and Android app both have the interface to view the faculty profiles, but the Web app can be used to view profiles of both institutes and faculty. We had provided User Experience based User Interface for easy navigation to Institute and Faculty profiles.

Admin can jump from many sections of the web app to the School Profiles like, searching section, section to add the and modify  the institute profiles.

2.2    Marking Attendance

The android app can be used to mark attendance and sync the attendance to sever. Attendance is of four types i.e. present, absent, late and leave. We had provided user friendly Interface to interact with the app to mark faculty attendance.

 

2.3     Getting Reports

Using Android and Web app the user (admin) can get daily, weekly and monthly reports, but the web app can be used to view collective or individual reports. Reports can be easily generated in the proposed system so user can generate the report as per the requirement

.

 

 

Chapter 3

REQUIREMENT SPECIFICATION

3.1.       Functional requirements

This app has following functional requirements.

·         Android version 4.4 kit Kat to Android 7.0 nougat.

·         Android API 16 to 26.

·         512 MB of RAM.

·         128 MB of storage.

·         Mobile Network.

·         Data Connection.

3.2.       None functional requirements

This is first order heading 1, the body text should be 12 regular and indent should be 0.5 of first line of paragraph left margin should be 1.5 and space between two lines should be double , space after and before line should be 6pt

3.3.       Required tools and technologies

Android Studio:  Android Studio is a powerful IDE provided by Jet Brains that ensures quality code throughout the entire application life-cycle, from design to deployment and is a very powerful IDE with intellisense.

MYSQL: MySQL is a relational database management system. As a database management System, it is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet).

SQLite:  SQLite is a relational database management system that is currently used by android OS. As a database management System, it is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet).

JSP: JSP is a Web application development scripting and server side language and is open source to allow programmers to build dynamic Web sites, Web applications and Web services.

Java: Java is a programming language developed by Sun Microsystems and later Oracle becomes the owner.

SQL: – SQL is a structured query language used for querying database.

HTML: – HTML is a scripting language to give layout to the web pages.

CSS: CSS is cascading style sheet which is used to give designer look to HTML using the external file.

Java script: – Java script is used for client side scripting which can help in using validation on the website and many more other functions.

 

 

 

 

 

 

 

Chapter 4

DESIGN

4.1.       System architecture

4.1.1.      MVC5 Architecture

When it comes to development and designing we refer to use MVC or MVC5 architecture.

This architecture distinguishes main role of the project: the Model, View, Controllers and Helpers. Models are used to store results generated by program logic, Views are the User Interface, Controllers are used control the events generated by the View components or System, Helpers contributes with the controllers to do their jobs.

In android we used Fragments and Activities as Controllers, Views are created with in the res/layout folder, and all the models, controllers and helpers are created in the java folder of the Android Studio project.

4.2.       Design constraints

Software design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm and area of application. Design is the first step in the development phase for any engineered product or system. The designer’s goal is to produce a model or representation of an entity that will later be built. Beginning, once system requirement have been specified and analyzed, system design is the first of the three technical activities -design, code and test that is required to build and verify software. The importance can be stated with a single word “Quality”. Design is the place where quality is fostered in software development. Design provides us with representations of software that can assess for quality. Design is the only way that we can accurately translate a customer’s view into a finished software product or system. Software design serves as a foundation for all the software engineering steps that follow. Without a strong design we risk building an unstable system – one that will be difficult to test, one whose quality cannot be assessed until the last stage.

 

4.2.1.      UML DIAGRAMS

The Unified Modeling Language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules. A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

4.2.2.      User Model View:

This view represents the system from the user’s perspective. The analysis representation

describes a usage scenario from the end-users perspective.

4.2.3.      Structural model view:

In this model the data and functionality are arrived from inside the system. This model

View models the static structures.

4.2.4.      Behavior Model View:

It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.

4.2.5.      Implementation Model View:

In this the structural and behavioral as parts of the system are represented as they are to be built.

4.2.6.      Environmental Model View:

 In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented. Use case Diagrams represent the functionality of the system from a user’s point of view.

Use cases are used during requirements elicitation and analysis to represent the functionality of the system. Use cases focus on the behavior of the system from external point of view.  Actors are external entities that interact with the system. Examples of actors include users like administrator, bank customer …etc., or another system like central database.

 

4.3.       Design methodology

4.3.1.      Water fall model

 The design methodology I have used is waterfall model, because water fall model is the simplest model of software development life cycle.

 

 

 

 

 

 

 

Following are the phases of Waterfall model.

 

4.3.1.1.            Requirement gathering

This step onward the software development team works to carry on the project. The team holds discussions with various stakeholders from problem domain and tries to bring out as much information as possible on their requirements. The requirements are contemplated and segregated into user requirements, system requirements and functional requirements.

 

4.3.1.2.            System Analysis

At this step the developers decide a road-map of their plan and try to bring up the best software model suitable for the project. System analysis includes understanding of software product limitations, learning system related problems or changes to be done in existing system beforehand, identifying and addressing the impact of project on organization and personnel etc. The project team analyzes the scope of the project and plans the schedule and resources accordingly.

4.3.1.3.            System Design

Next step is to bring down whole knowledge of requirements and analysis on the desk and design the software product.

4.3.1.4.            Coding

This step is also known as programming phase. The implementation of software design starts in terms of writing program code in the suitable programming language.

4.3.1.5.            Testing

Errors may ruin the software from critical level to its own removal. Software testing is done while coding by the developers and thorough testing is conducted by testing experts at various levels of code such as module-testing, program testing, product testing and testing the product at user’s end.

4.3.1.6.            Integration

Software may need to be integrated with the libraries, databases and other programs.

4.3.1.7.            Implementation

 This means installing the software on the user machines. Software is tested for portability and adaptability and integration related issues are solved during implementation.

4.3.1.8.            Operation and Maintenance.

 This phase confirms the software operation in terms of more efficiency and less errors. If required. The users are trained on or aided with the documentation on how to operate the software and how to keep the software operational.

 

4.4.       High level design

4.5.       Low level design

4.6.             Database design

4.7.        GUI design

4.8.        External interfaces

 

 

 

 

 

 

 

 

 

 

 

CHAPTER 5

SYSTEM IMPLEMENTATION

5.1.       System architecture

It is best to also reiterate information in your literature review to help substantiate the findings of your research. In general, there should be no new information presented here.  It should be a synthesis of information that you’ve already discussed.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter 6

 

SYSTEM TESTING AND EVALUATION 

Policy and research implications of your research results, and future research aspects. This template is best used for directly typing in your content. 

 

Chapter 7

CONCLUSION

The end results of the application are of great importance and were very good, the application can have a positive impact on the people who are new to this area as well as to the people of this area who are still unaware of the progress and development in the region of any specific area, this application is more beneficial in terms of economy to the region especially the tourism department and government of the area especially.

The application is much more productive and beneficial in the near future, it may introduce a new trend as e-guide business by advertising trusted sources.

The mobile phone applications can replace the human guide which is easy to use, trusted to guide and easy to manage.

 FUTURE PLANS

 

The current feature in SMS Scheduler Application may need to further change and improvement to support the present technology. Therefore, there are some recommendation that might be done in future such as add more features to continues the system enhancement. There are several improvement that can be made as sending a multimedia message. to provide ease for the user by developing an inbuilt keypad that reduces the effort to type whole word and the chance of spelling mistakes.

 

 

 

 

 

 

 

 

RESULTS

The end results out of the project can be divided into two main categories.

The user skills results

The application results

 

As far as user skills are concerned the project is purely developed by myself , each and every implementation here in this project is based on my own logic how to create application , how to get locations , what to include in the application as android and web application are purely my ideas there were things I learn from “stack overflow” a well known web platform to get the programming related solutions their advantages and disadvantages but there is no any related implementation in any kind of web application I found to copy or to guide the implementation of the application until now, so this helped me increasing my creativity skills and to test my programming skills in a real world application like this hence the skills are really more developed and results upon skills remarkable.

The application results are also more better than that of what I was think of as due to online and offline map guide processes the application is truly working in a great manner than that of any other application which is running over the internet especially in unavailability of the internet hence the results of the application are even more encouraging and of primary importance and much more than we can think of.

 

 

 

 

 

 

 

 

 

 

REFERENCES

Includes all references: articles, media facts, books, reports, regulations, internet articles, papers that you referenced from the text. Use the APA style of referencing (www.apastyle.org).

Or any other standard format as per requirement of the subject.

 

APPENDICES

Type or paste your appendices here. Appendices are a place to organize and include all of the “extra” material that is important to your research work but that is too detailed for the main text.  Examples can include: specific analytical methods, computer code, spreadsheets of data, details of statistical analyses, etc.  But, these materials do not speak for themselves.  There should be a reference to these materials from the main chapters and there should be some text at the beginning of each appendix to briefly explain what the information is and means that is included in that appendix.

 

Appendix A

USER MANUALS

.

 

Appendix B  

SOURCE CODE