Two Way Student Information Management System Using Cellular Technology

VISVESVARAYA TECHNOLOGICAL UNIVERSITY BELGAUM-590002
A Project Report on TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY
Submitted To Visvesvaraya Technological University, Belgaum in partial fulfillment of requirements for the award of degree BACHELOR OF ENGINEERING IN COMPUTER SCIENCE & ENGINEERING By
Mr. Sayyan N. Shaikh

USN: 2VD07CS041
Under the Guidance of
Prof. Saleem .Hebbal
Karnatak Law Societys VISHWANATHRAO DESHPANDE RURAL INSTITUTE OF TECHNOLOGY HALIYAL (UTTAR KANNADA) 581 329 2010-2011
Karnatak Law Societys VISHWANATHRAO DESHPANDE RURAL INSTITUTE OF TECHNOLOGY HALIYAL (UTTAR KANNADA) 581 329
Department of Computer Science & Engineering
CERTIFICATE
Certified that the project work entitled
TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

is a bonafide work carried out by
Mr. Sayyan N. Shaikh USN: 2VD07CS041 Ms. Jyothi .Belgoankar USN: 2VD06CS014
Mr. Ganesh U.Bhat USN: 2VD06CS018 Ms.Pavitra P. Kini USN: 2VD07CS031
in partial fulfillment for the award of Degree of Bachelor of Engineering in Computer Science & Engineering of Visvesvaraya Technological University, Belgaum during the year 2010-2011. It is certified that all corrections/suggestions indicated for Internal Assessment have been incorporated in the report. The project report has been approved as it satisfies the academic requirements in respect of project report prescribed for the said Degree.
_______________ GUIDE
Prof. Saleem Hebbal
_____________ HOD
Prof. A. V. Kolaki
____________ PRINCIPAL
Dr. G. R. Udupi
External Viva
Name of the Examiners 1.___________________ 2. ___________________ Signatures with Date __________________ __________________
Dedicated to Our Beloved Parents And Teachers
ACKNOWLEDGEMENT
Culmination of project is that stage which makes the transformation a mere theoretical idea into a visible reality. Our report acknowledges some guidance, some supervision and a lot of inspiration; it is time now to acknowledge our obligations to all who have extended their cooperation all along our study tenure of project work. We express a deep sense of gratitude to Prof. Saleem Hebbal and Prof. Damodar Hotkar for the constant timely advice, valuable suggestions and help given from time to time. We wish to place a record our profound privilege & deep sense of gratitude to Prof. Saleem Hebbal for his wholehearted guidance without which this endeavor would not have been possible. Our grateful regards are also due, to Prof. A.V.Kolaki, HOD CSE Department for his continuous support and inspiration to us, which contributed to the success of our project. We are also deeply grateful to Dr. G.R.Udupi our beloved principal for having provided us the academic environment, which nurtured our practical skills, contributing to the success of our project. Our diction falls short of words to gratify the teaching and non-teaching faculty members of our Department for being primary source of inspiration and strength for the project study. We would also like to extend our grateful regards to all the people who assisted directly or indirectly for the completion of this project. Lastly with unquantifiable affection and reference we wish to express our sincere feelings to our parents and family members in the form of words, which are restrictive in expression and quantum, -Project Associates Sayyan N. Shaikh Ganesh U. Bhat Jyothi. Belgoankar Pavitra P. Kini
I
ABSTRACT
A unique marketing tool for telecom and wireless hardware, software and services vendors for leads generation, and a unique gift to their partners and customers. A comprehensive wireless communication technology guide for network and telecom professionals. An easy to use training reference for telecom and wireless technology students to get an overall picture of WLAN, WPAN, WMAN, WWAN and Mobile technologies. There are many features associated with GSM technology due to which it is bar far the most leading mobile communication technology in the world today. GSM technology facilitates with high speed integrated data, voice data, fax, mail, voice mail and mostly used SMS feature. This supports varied frequency. One of the major advantages of GSM technology which changed the way we looked mobile phones at the beginning. GSM actually brought the concept of being Mobile way beyond the limits. It enabled us to communicate across the continents. GSM phone deliver very good voice quality, support useful services and standards, it is very likely that GSM will remain the only mobile communication network technology to be adopted by each and every country of the world. This proposed project will manages students information (such as their IA averages, Attendance, Events) and sends it to their parents mobile as per the scheduled dates set by the authority. Similarly parents can also request for students information by sending their request to the service number .And this software provide them with their intended information they requested with minimal time period.
II
CONTENTS
CHAPTER DESCRIPTION
Acknowledgement Abstract List of Figures
PAGE NO
i ii v
1. 2.
INTRODUCTION LITERATURE SURVEY

2.1 2.2 2.3 2.4 Windows XP/2000 Advantages Technologies Used AT Commands Database Used
01 02 02 03 09 10 13 13 14 15 17 17 17 23 34 42 42 43 44 45 45
III
3.
REQUIREMENT ANALYSIS
3.1 3.2 3.3 Feasibility Analysis Software Requirement Specification Developers Responsibilities Overview
4.
SYSTEM ANALYSIS AND DESIGN

4.1 4.2 4.3 Introduction System Design Detailed Design
5. 6.
IMPLEMENTATION TESTING, VERIFICATION AND VALIDATION

6.1 6.2 6.3 6.4 Testing Testing Strategies Test case Design Testing/Performance Analysis
6.5 Test Cases
7.
RESULTS
47
CONCLUSION
59
REFERENCES
60
IV
LIST OF FIGURES
FIGURE.NO
Figure4.1 Figure4.2 Figure4.2 Figure4.2 Figure4.2. Figure4.2 Figure4.2 Figure4.2 Figure4.2 Figure7.1 Figure7.2 Figure7.3 Figure7.4 Figure7.5 Figure7.6 Figure7.7 Figure7.7 Figure7.8 Figure7.8
DESCRIPTION
SIM300 GSM Modem DFD of proposed system DFD of sending data DFD of stored data DFD of guardians detail DFD of scheduling form DFD of receiving data DFD of scanning previous data E-R Diagram for proposed system Main form without port connectivity Main form with port connectivity Form for adding contacts Form for checking received data Form for checking sent data Form for scheduling data Form for sending data to guardians Process of selecting the clients and data Form for storing data Process of creating new drafts
PAGE NO
08 18 19 19 20 20 21 21 22 47 48 49 50 51 52 53 54 55 56
V
Figure7.8 Figure7.9
Display of data after adding new data Alert messages before exiting
57 58
VI
Chapter 1
INTRODUCTION
The project basically works by sending students information such as IA marks average, their attendance and events in college to their parents or guardians as specified in database of college using GSM modem .It also has scheduling functions that take care of sending students information automatically as per the scheduled dates. Thus it provides flexibility by allowing the members to only enter the students information within specified dates and rest of work is taken care by the software automatically without any human interaction. As GSM modem works only using AT commands whatever students information needs to be sent is passed to modem using AT commands and thus information is sent to the intended persons. If any parents want to know about any information about their childrens then they will send their request to messing service number .This message will be stored in an appropriate form, which then can be checked by authorized persons and can reply to intended person.
Department of Computer Science and Engineering, KLSs Vishwanathrao Deshpande Rural Institute Of Technology, Haliyal.
Chapter 2
LITERATURE SURVEY
2.1 Windows XP/2000 Advantages

The computing world was presented with the first release of the totally new and revolutionary operating system. Microsoft windows performance and features that previously has been accessible only $20,000 annotations become instantly available to anyone with a high end personal computer. Windows is now Microsoft Corporations premier operating system. Designed around powerful and well through software architecture, the primary features that allow windows to use the full power of todays processors are:
Scalability
The ability to run on a single pc chip with a single user up to a multi-user microprocessor and network installation.
The Windows GUI

The familiar graphical user interfaces it presents to the world.
2.2 Technologies used Introduction to .NET

2.2.1 .NET Framework
.NET is Software platform. It is a language neutral environment for development rich. .NET experiences and application that can easily and securely operated within it.When development application are developed these application will target .NET and execute where .NET is implemented instead of targeting a particular hardware /OS combination. The components that make up the .NET platform are collectively called the .NET framework. The .NET framework is managed, type safe environment for development and executing application the .NET framework manages all aspect of program execution like allocation of memory for the storage of data and instruction, granting and denying permission to the application, managing execution of the application and reallocation of memory for the resource that are not needed. The .NET framework is designed for cross language compatibility. Cross language compatibility means, an application written in Visual Basic .NET may reference a DLL file written in C#(C-Sharp).A Visual Basic .NET class might be derived from a C# class or vice versa.
2.2.2 Components Of .NET Framework

1. Common Language Runtime (CLR) 2. Class Libraries 3. Common Language Specification (CLS)
1) Common Language Runtime (CLR)

The CLR is described as the execution engine of .NET .It provides the environment within which the programs run. Its this CLR that manages the execution of programs that provides core services, such as code compilation, memory allocation, thread management and garbage collection through the common type system (CTS). It enforces strict type safety and it ensure that the code is executed in safe environment by enforcing code access security .The software version of .NET is actually the CLR version.
2) Class Libraries
Class library is the second major entity of the .NET Framework which is designed to integrate with the common language runtime. This library gives the program access to runtime environment. The class library consist of lots of prewritten code that all the element like forms, controls and rest in VB .NET and Visual Studio .NET application actually comes from the class library.
3) Common Language Specification (CLS)

If we want the code which we write in language to be used by program in other language then it should adhere to the Common Language Specification (CLS).The CLS describes a set of features that different languages have in common. The CLS define the minimum standards that .NET language compilers must conform to, and ensure that any source code compiled by .NET compiler can interoperate with the .NET Framework. Some reasons why developers are building applications using the .NET Framework: Improved Reliability Increased Performance Developers Productivity
Department of Computer Science and Engineering, KLSs Vishwanathrao Deshpande Rural Institute Of Technology, Haliyal. 4
Powerful Security Integration with existing system Ease of Development Mobility Support XML WEB service support Support for over 20 Programming languages Flexible data access
2.2.3 .NET vs. Java

Many of us wonder what .NET has done with java. Is there any relation between them? Are they similar? And so on. I even hear some people say .NET is Microsoftsanswer to java. I think every language has its own pros and cons. Java doesnt have a visual interface and requires us to write heaps of code to develop applications. On the other hand, with .NET, the framework supports around 20 different programming languages which are better and focus only on business logic leaving all other aspects of the framework. Visual Studio .NET comes with rich visual interface and supports drag and drop .Many applications were developed, tested and maintained to compare the difference between .NET and Java and the end result was particular application developed using .NET requires less line of code ,less time to develop and lower development cost along with other important issues. Personally, I dont mean to say that java is a gone or .NET based application are going to dominate the internet but I think .NET definitely has an extra edge as it is packed with features that simply application development.
2.2.4 .NET Framework advantages

The .NET Framework offers a number of advantages to developers. The following paragraph describes them in detail. Consistent programming model. Direct support for security. Simplified development efforts. Easy application development and maintenance.
2.2.5 C# .NET C# .NET provides the easiest, most productive language ant tool for rapidly building
windows and web application. C# .NET comes with enhanced visual designers, increased application performance, and powerful integrated development environment (IDE).It also supports creation of applications for wireless, internet-enabled hand held devices.[1]
Features
Powerful windows form based applications. Building a web based applications. Simplified Development. Power, flexible simplified data access. Improved coding. Direct access to the platform.
Full object oriented constructs. XML Web services. Mobile applications. COM interoperability. Reuse existing investments. Upgrade Wizard.[1]
2.2.6 About GSM Modem

GSM Modem provides full functional capability to Serial devices to send SMS and Data over GSM Network. The product is available as Board Level or enclosed in Metal Box. The Board Level product can be integrated in to Various Serial devices in providing those SMS and Data capability and the unit housed in a Metal Enclosure can be kept outside to provide serial port connection. The GSM Modem supports popular "AT Command set so that users can develop applications quickly. The product has SIM Card holder to which activated SIM card is inserted for normal use. The power to this unit can be given from UPS to provide uninterrupted operation. This product provides great feasibility for Devices in remote location to stay connected which otherwise would not have been possible where telephone lines do not exist
2.2.7 Application Areas

Mobile Transport vehicles. LAN based SMS servers Alarm notification of critical events including Servers Network Monitoring and SMS reporting Data Transfer applications from remote locations Monitor and control of Serial services through GSM Network Integration to custom software for Warehouse, Stock, Production,
Dispatch notification through SMS. AMR- Automatic Meter Reading and many more
2.2.8 Specification for GSM Modem

In our project we use the SIM300 GSM Modem. SIM300 is a Tri-band GSM/GPRS engine that works on frequencies EGSM 900 MHz, DCS 1800 MHz and PCS 1900 MHz. SIM300 features GPRS multi-slot class 10/ class 8 (optional) and supports the GPRS coding schemes CS-1, CS-2, CS-3 and CS-4.
Figure4.1 SIM300 GSM Modem
SIM card interface

You can use AT Command to get information in SIM card.The SIM interface supports the functionality of the GSM Phase 1 specification and also supports the functionality of the new GSM Phase 2+ specification for FAST 64 kbps SIM(intended for use with a SIM application Tool-kit).Both 1.8V and 3.0V SIM Cards are supported. The SIM interface is powered from an internal regulator in the module having nominal voltage 2.8V. All pins reset as outputs driving low. Logic levels are as described in table
Network status indication LED lamp

State SIM300 function Off - SIM300 is not running 64ms On/ 0.8 sec Off - SIM300 does not find the network 64ms On/ 3 Sec Off - SIM300 find the network 64ms On/ 0.3 sec Off - GPRS communication
2.3 AT Commands
A series of machine instructions used to activate features on an intelligent modem. Developed by Hayes Microcomputer Products and officially known as the Hayes Standard AT Command Set, it is used entirely or partially by most every modem manufacturer. AT is a mnemonic code for ATtention, which is the prefix that initiates each command to the modem.
2.3.1 AT Command syntax

The "AT" or "at" prefix must be set at the beginning of each command line. To terminate a command line enter <CR>.Commands are usually followed by a response that includes.<CR><LF><response><CR><LF>Throughout this document, only the responses
are presented, <CR><LF> are omitted intentionally. The AT command set implemented by SIM300 is a combination of GSM07.05, GSM07.07 and ITU-T recommendation V.25ter and the AT commands developed by SIMCOM.
Note: Only enter AT command through serial port after SIM300 is power on and Unsolicited Result Code RDY is received from serial port. And if unsolicited result codeSCKS: 0 returned it indicates SIM card isnt present. If autobauding is enabled, the Unsolicited Result Codes RDY and so on are not indicated when you start up the ME All these AT commands can be split into three categories syntactically: basic, S parameter, and extended. These are as follows:
2.3.2 Basic syntax

These AT commands have the format of AT<x><n>, or AT&<x><n>, where <x>is the command, and <n>is/are the argument(s) for that command. An example of this is ATE<n>, which tells the DCE whether received characters should be echoed back to the DTE according to the value of <n>. <n> is optional and a default will be used if missing.
2.3.3 S parameter syntax

These AT commands have the format of ATS<n>=<m>, where <n> is the index of the S register to set, and <m>is the value to assign to it. <m> is optional; if it is missing, then a default value is assigned.
2.4 Database Used

2.4.1 Introduction to Microsoft Office Access 2010
Microsoft Access is a computer application used to create and manage computerbased databases on desktop computers and/or on connected computers (a network). Microsoft
Access can be used for personal information management (PIM), in a small business to organize and manage data, or in an enterprise to communicate with servers. Microsoft Access (MS Access) enables one to manage all important information from a single database file. Within the file, one can use: Tables to store your data. Queries to find and retrieve specific data of interest. Forms to view, add, and update data in tables. Reports to analyze or print data in a specific layout. Data access pages to view or update, the data. In MS Access, data is stored once in one table, but can be viewed from multiple locations. When the data is updated in a Table, Query or Form, it is automatically updated everywhere it appears.
2.4.2 Features Microsoft Office Access 2010

Users can create tables, queries, forms and reports, and connect them together with macros. Advanced users can use VBA to write rich solutions with advanced data manipulation and user control. The original concept of Access was for end users to be able to "access" data from any source. Other uses include: the import and export of data to many formats including Excel, Outlook, ASCII, dBase, Paradox, FoxPro, SQL Server, Oracle, ODBC, etc. It also has the ability to link to data in its existing location and use it for viewing, querying, editing, and reporting. This allows the existing data to change and the Access platform to always use the latest data. It can perform heterogeneous joins between data sets stored across different
platforms. Access is often used by people downloading data from enterprise level databases for manipulation, analysis, and reporting locally. One of the benefits of Access from a programmer's perspective is its relative compatibility with SQL (structured query language) queries can be viewed graphically or edited as SQL statements, and SQL statements can be used directly in Macros and VBA Modules to manipulate Access tables. Users can mix and use both VBA and "Macros" for programming forms and logic and offers object-oriented possibilities. VBA can also be included in queries. Microsoft Access offers parameterized queries. These queries and Access tables can be referenced from other programs like VB6 and .NET through DAO or ADO. From Microsoft Access, VBA can reference parameterized stored procedures via ADO. Microsoft Access is a file server-based database. Unlike clientserver relational database management systems (RDBMS), Microsoft Access does not implement database triggers, stored procedures, or transaction logging. Access 2010 includes table-level triggers and stored procedures built into the ACE data engine. Thus a Client-server database system is not a requirement for using stored procedures or table triggers with Access 2010. Tables, queries, Forms, reports and Macros can now be developed specifically for web base application in Access 2010. Integration with Microsoft SharePoint 2010 is also highly improved.[5]
12
Chapter 3
REQUIREMENT ANALYSIS
The analysis is intended to capture and describe the requirements of the system and to make a model that defines the key domain classes in the system. The purpose is to provide an understanding and enable a communication about the system between the developers and the people establishing the requirements. Therefore the analysis is typically conducted in cooperation with the customer.
3.1 Feasibility Analysis

In any project feasibility, analysis is a very important stage; here the project is checked for its feasibility. Any project may face resources scarcity, time or workforce scarcity, so all these are to be studied in detail and a conclusion should be drawn that whether the project under conclusion is feasible or not. The organizational and the technical feasibility regarding whether the project meets the requirement standards like meeting the strategic objectives etc.
3.1.1 Organizational Feasibility

The system meets the organizational need. It provides facilities to do the organizational work automatically and efficiently and also exchange information within the organization efficiently. It also provides a comprehensive route for enhancing all communication services and upgrade operations for everyone concerned with the institution. .
3.1.2 Technical Feasibility

The proposed system is developed using current technology that is C#.NET and the general purpose data base used is Microsoft Access 2007 which is easily available in the office package.
3.1.3 Operational Feasibility

The users easily understand the procedures followed by the system. The user-friendly forms are designed to support this. The end user need not be an expert in VC#.NET.
3.2 Software Requirement Specification

3.2.1 Abstract
The requirements document for TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY is described here.. It provides facility to exchange information between administrator and guardians regarding the institute. It avoids manual operations to be done by the institute faculty such as Internal Assessment details, student or staff details and book inventory details.
3.2.2 Introduction Purpose

The purpose of this document is to describe the functional, nonfunctional and user characteristics for the Student/Organization Management system.
Scope
This document aims to describes the requirements of the system. It is used for validating the final delivered system.
3.2.3 Definitions, Acronymes, Abbreviations C#.NET

ER Diagram DFD C Sharp .NET Framework Entity Relationship Diagram Data Flow Diagram
3.3 Developers Responsibilities Overview

The developer is responsible for developing for a) Developing the system as per the SRS. b) Installing the software for demonstration.
3.3.1 Specific Requirements Functional Requirements

These are the statements of service the system should provide, how the system should react to particular inputs and how the system should behave in particular situations. In some cases, the functional requirements may also explicitly state what the systems should not do. Provides facility to add new user. Provide overall information of all the students in the institution. We should supply frequently power to GSM MODEM. It should provide special permissions for administrator. Provide password option to the database. Provide administrator to view and edit his information. It should provide details of received data.
Non Functional Requirements

The basic nonfunctional requirements are Security issue that is to provide access only to authorized users. The system has to provide good speed in response to the requests.
External Interface Requirements

Applicable.
Performance Constraints
Good speed in response to the requests.
Design Constraints
Good speed in response to the requests.
Software Constraints
The system has to be developed using C# .NET and Microsoft Access 2010
Hardware Constraints
Standard PC configuration with standard mouse interface.
Acceptance Criteria
The system must be demonstrated to work according to the specifications of all the functions. The test case has to be designed to meet all the conditions to be tested. [3]
16
Chapter 4
SYSTEM ANALYSIS AND DESIGN

4.1 Introduction
The design phase expands the details of an analysis model by taking into account all technical implications and restrictions. The purpose of the design is to specify a working solution that can be easily translated into programming code. Design consists of two phases System Design Detailed Design
4.2 System Design

The system design provides the modules that are to be implemented in the system in order to meet the functional requirements used in the system. It provides the specifications of each modules used in the system. (Refer fig. 4.1) COM Port setting Adding information to database Sending a message Receiving a message Scheduling a message
17
4.2.1 Data Flow Diagram for System Design
Figure 4.2.1.1 DFD of Two Way Student Information Management System
18
DFD for Sending Data
Figure 4.2.1.2 DFD of sending data
DFD for Storing Data
Figure 4.2.1.3 DFD of storing data
19
DFD for Contacts
Figure 4.2.1.4 DFD of guardians detail
DFD for Scheduling
Figure 4.2.1.5 DFD of scheduling form
20
DFD for Receiving Data
Figure 4.2.1.6 DFD of receiving data
DFD for Scanning Previous Data
Figure 4.2.1.7 DFD of scanning previous data
21
4.2.2 E-R Diagram for the Two Way Student Information Management system
DId DNam e DMessage
DMessagereated
Message
SendOn
Id W MS VS T
Drafts
SendTo
1 Scheduler
Id W MS ItemIdVS T
Message
Can schedule
N N
Can select
1
On success
1
DelOn
Id W MS VS T Sent items
1
Saves it in
ToSend ToMobile DeliStatus
Contacts N
Name MNumber
Can select
Send 1
Id
Id
Message Status SendTo o
Figure4.2.2.1 E-R Diagram for the proposed system

4.3 Detailed design

This part of documentation deals with the part of procedural steps of processing the data. This part deals with the steps that how the data is to be sent to the guardians, how it is scheduled, and also how the retrieved data is processed.
Algorithm for Main form

Step 1: initialize all components Step 2: instantiate all children forms Step 3: set following properties system into text mode send sms using specific characters new sms message indication preferred sms storage reporting mobile equipment error Step 4: define all event handlers used Step 5: call serial port data received event handler Step 6: stop
Algorithm for Drafts form

Step 1: start Step 2: initialize components
23
Step 3: set connection and properties Step 4: goto step 7 Step 5: goto step 12 Step 6: stop Algorithm for LoadDraftsData method Step 7: clear all nodes from collection Step 8: setup the connection if connection state open close connection endif open connection Step 9: read contents of drafts table if datareader has rows do add nodes while datareader has rows endif close datareader Step 10: repeat step 9 for different id values
Step 11: Stop Algorithm for LoadYMD method Step 12: clear all nodes from collection Step 13: setup the connection if connection state open Close connection endif open connection Step 14: fetching data from database read contents of drafts table while datareader has rows add date endwhile Step 15: stop
Algorithm for send form.

Step 1: start Step 2: initialize all components and set appropriate properties to the components. Step 3: add all components to the view. Step 4: if connection state==open
close connection endif open connection Step 5: query the table and fetch data in datareader Step 6: while datareader has rows add read data row by row to form end while close connection Step 7: repeat step 5 and step 6 to read all the data Step 8: goto step 11 Step 9: goto step 16 Step 10: stop Algorithm for loadContactData function Step 11: initialize tree node. Step 12: if connection state==open close connection. endif open connection. Step 13: fetch the data from tables using appropriate query and store all data in datareader
Step 14: if datareader has rows add contacts data to form endif Step 15:stop Algorithm for loadDrafts method Step 16: initilize tree node. Step 17: if connection state==open Close connection. endif open connection. Step 18: fetch the stored messages from tables using appropriate query and store all data in datareader. Step 19: if datareader has rows add stored drafts to form endif Step 20: stop
Algorithm for receive form

Step 1: initilize all form components and set appropriate properties for component.
27
Step 2: goto step 5 Step 3: goto step 10 Step 4: stop Algorithm for loadContactData method Step 5: initilize tree node. Step 6: if connection state==open close connection. endif open connection. Step 7: load all stored contacts from table into datareader. Step 8: if datareader has rows add data hierarchically to node . endif close connection. Step 9: stop Algorithm for loadYMDData method Step 10: if connection state==open close connection. endif
open connection. Step 11: read all received data in datareader. Step 12: while datareader has rows add data. end while add time. Step 13: stop
Algorithm for scheduler form

Step 1: initilize all components and set their properties. Step 2: if connection state==open close connection. endif open connection. Step 3: load all saved drafts from tables into datareader Step 4: while datareader has rows add data to form. endwhile close datareader Step 5: goto step 8
Step 6: goto step 14 Step 7: stop Algorithm for loadYMDData method Step 8: if connection state==open close connection. endif open connection. Step 9: read all received data in datareader. Step 10: while datareader has rows add data. end while add time. Step 13: stop Algorithm for loadContactData function Step 14: initilize tree node. Step 15: if connection state==open close connection. endif open connection.
Step 16: fetch the data from tables using appropriate query and store all data in datareader Step 17: if datareader has rows add contacts data to form endif Step 18: stop
Algorithm for sentitem form

Step 1: initilize all form components and set appropriate properties for component. Step 2: goto step 5 Step 3: goto step 10 Step 4: stop Algorithm for loadContactData method Step 5: initilize tree node. Step 6: if connection state==open close connection. endif open connection. Step 7: load all stored sent message list from table into datareader. Step 8: if datareader has rows add data hierarchically to node .
endif close connection. Step 9: stop Algorithm for loadYMDData method Step 10: if connection state==open Close connection. endif open connection. Step 11: read all received data in datareader. Step 12: while datareader has rows add data. end while add time. Step 13: stop
Algorithm for Contact form

Step 1: initilize all components Step 2: if connection state==open close connection. endif
open connection. Step 3: load all stored contacts list from table into datareader. Step 4: if datareader has rows add data hierarchically to node . endif Step 5: goto step 7 Step 6: stop Algorithm for load Data method Step 7: initilize tree node. Step 8: if connection state==open close connection. endif open connection. Step 9: load all stored contacts from table into datareader. Step 10: if datareader has rows add data hierarchically to node. endif close connection. Step 11: stop
Chapter 5 IMPLEMENTATION
Main form code //initialization of used components
public static SerialPort smsPortMain = new SerialPort(); public static SerialPort smsPortSub = new SerialPort(); //initialization of components used to access database public static OleDbConnection cn = new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Jet OLEDB:Database Password=WMSVST;Data Source=" + Environment.CurrentDirectory + "\\BulkSMS.mdb"); public static OleDbCommand cmd = new OleDbCommand(); public static OleDbDataReader dr ; public static DataSet ds= new DataSet(); public static OleDbDataAdapter da = new OleDbDataAdapter(); //instantiations of children form frmSendReceive SR = new frmSendReceive(); frmDrafts frmdrafts = new frmDrafts(); frmInbox frminbox = new frmInbox(); frmSentItems frmsentitems = new frmSentItems(); frmSchedular frmschedular = new frmSchedular(); frmName frmname = new frmName(); frmOptions frmoptions = new frmOptions(); frmSend frmsend = new frmSend(); //cmgf=1 set system into text mode. smsPortSub.Write("AT+CMGF=1" + Convert.ToChar(13));
34
//send sms using specific characters. smsPortSub.Write("AT+CSMP=49,167,0,0" + Convert.ToChar(13)); // cnmi- new sms message indication. smsPortSub.Write("AT+CNMI=2,2,0, 1,0" + Convert.ToChar(13)); // cpms- prefred sms message storage. smsPortSub.Write("AT+CPMS=\"SM\"" + Convert.ToChar(13)); //cmee - reporting mobile equipment error. smsPortSub.Write("AT+CMEE=1" + Convert.ToChar(13)); //function for monitoring the data received from data fort smsPortSub.DataReceived += new SerialDataReceivedEventHandler(this.serialPort1_DataReceived1); timer2.Tick += new EventHandler(timer2_Tick); timer2.Interval = 30; tw.Enabled = true; pictureBox1.Image = frmoptions.imageList1.Images[0];
Send form code

frmMain.cn.Close(); frmMain.cn.Open(); frmMain.cmd.CommandText = "Select Distinct ItemId,ItemName From Contacts Where ItemName is not null and ItemName <> '' and ItemGorI = 'I' Order By ItemName,ItemId"; frmMain.dr = frmMain.cmd.ExecuteReader(); while (frmMain.dr.Read()) { Name.Items.Add(frmMain.dr["ItemName"].ToString()); } frmMain.dr.Close();
dgvSendMessage.Rows.Add(); //Loads saved contacts in TreeView this.loadContactData(); //Loads saved Drafts in TreeView this.loadDrafts();
Inbox code
frmMain.cmd.Connection = frmMain.cn; //adds all specified contents in list view lvInbox.Columns.Add("Sender", "Sender"); lvInbox.Columns.Add("SentDate", "Sent Date"); lvInbox.Columns.Add("SentTime", "Sent Time"); lvInbox.Columns.Add("Message", "Message"); //sets the properties of specific column lvInbox.Columns["Message"].Width = (lvInbox.Width - 20) / 2; lvInbox.Columns["Sender"].Width = ((lvInbox.Width - 20) lvInbox.Columns["Message"].Width) / 3; lvInbox.Columns["SentDate"].Width = ((lvInbox.Width - 20) lvInbox.Columns["Message"].Width) / 3; lvInbox.Columns["SentTime"].Width = ((lvInbox.Width - 20) lvInbox.Columns["Message"].Width) / 3; this.loadContactData(); this.loadYMDData(); this.updateSenderName();
36
SentItems code
public frmSentItems() { InitializeComponent(); frmMain.cmd.Connection = frmMain.cn; //adds the properties in list view lvSentItems.Columns.Add("ToName", "To"); lvSentItems.Columns.Add("SentDate", "Sent Date"); lvSentItems.Columns.Add("SentTime", "Sent Time"); lvSentItems.Columns.Add("Message", "Message"); lvSentItems.Columns.Add("SendStauts", "Send Status"); lvSentItems.Columns.Add("DeliveryStatus", "Delivery Status"); SendTo.Name = "SendTo"; SendTo.HeaderText = "To"; SendTo.ReadOnly = true; Message.Name = "Message"; Message.HeaderText = "Message"; Message.ReadOnly = true; SendStatus.Name = "SendStatus"; SendStatus.HeaderText = "Send Status"; SendStatus.ReadOnly = true; DeliveryStatus.Name = "DeliveryStatus"; DeliveryStatus.HeaderText = "Delivery Status"; DeliveryStatus.ReadOnly = true; dgvSentItems.Columns.Add(SendTo); dgvSentItems.Columns.Add(Message); dgvSentItems.Columns.Add(SendStatus); dgvSentItems.Columns.Add(DeliveryStatus); this.lvSentItems_Resize(lvSentItems, new EventArgs()); this.dgvSentItems_Resize(dgvSentItems, new EventArgs()); this.loadContactData(); this.loadYMDData();
37
Contact form
InitializeComponent(); frmMain.cmd.Connection = frmMain.cn; if (frmMain.cn.State == ConnectionState.Open) frmMain.cn.Close(); frmMain.cn.Open(); frmMain.cmd.CommandText = "Select * From ContactsSub Order By ColOrder"; frmMain.dr = frmMain.cmd.ExecuteReader(); while (frmMain.dr.Read()) { string s = frmMain.dr["ColNameI"].ToString(); if (!frmMain.dr["ColNameI"].ToString().Contains("Greetings") && !frmMain.dr["ColNameI"].ToString().Contains("Day")) { dgvRContacts.Columns.Add(frmMain.dr["ColNameI"].ToString(), frmMain.dr["ColName"].ToString()); dgvContacts.Columns.Add(frmMain.dr["ColNameI"].ToString(), frmMain.dr["ColName"].ToString()); } else if (frmMain.dr["ColNameI"].ToString().Contains("Day") && !frmMain.dr["ColNameI"].ToString().Contains("Greetings")) dgvRContacts.Columns.Add(new DataGridViewDatePickerColumn()); dgvRContacts.Columns[dgvRContacts.Columns.Count - 1].Name = frmMain.dr["ColNameI"].ToString(); dgvRContacts.Columns[dgvRContacts.Columns.Count - 1].HeaderText = frmMain.dr["ColName"].ToString(); dgvContacts.Columns.Add(new DataGridViewDatePickerColumn());
38
dgvContacts.Columns[dgvContacts.Columns.Count - 1].Name = frmMain.dr["ColNameI"].ToString(); dgvContacts.Columns[dgvContacts.Columns.Count - 1].HeaderText = frmMain.dr["ColName"].ToString(); } else { dgvRContacts.Columns.Add(new DataGridViewCheckBoxColumn()); dgvRContacts.Columns[dgvRContacts.Columns.Count - 1].Name = frmMain.dr["ColNameI"].ToString(); dgvContacts.Columns.Add(new DataGridViewCheckBoxColumn()); dgvContacts.Columns[dgvContacts.Columns.Count - 1].Name = frmMain.dr["ColNameI"].ToString(); dgvContacts.Columns[dgvContacts.Columns.Count - 1].HeaderText = frmMain.dr["ColName"].ToString(); } if (frmMain.dr["ColNameI"].ToString() != "Name") { if (Convert.ToBoolean(frmMain.dr["ColRDisplay"].ToString())) { dgvRContacts.Columns[frmMain.dr["ColNameI"].ToString()].Visible = true; dgvRContacts.Columns[frmMain.dr["ColNameI"].ToString()].Width = 200; } else { dgvRContacts.Columns[frmMain.dr["ColNameI"].ToString()].Visible = false; dgvRContacts.Columns[frmMain.dr["ColNameI"].ToString()].Width = 200;
} if (Convert.ToBoolean(frmMain.dr["ColDisplay"].ToString())) { dgvContacts.Columns[frmMain.dr["ColNameI"].ToString()].Visible = true; dgvContacts.Columns[frmMain.dr["ColNameI"].ToString()].Width = 200; } else { dgvContacts.Columns[frmMain.dr["ColNameI"].ToString()].Visible = false; dgvContacts.Columns[frmMain.dr["ColNameI"].ToString()].Width = 200; }}} this.dgvRContacts.ContextMenuStrip = this.cMS; this.dgvContacts.ContextMenuStrip = this.cMS; this.loadData();
Scheduler form
InitializeComponent(); frmMain.cmd.Connection = frmMain(); lvSchedular.Columns.Add("SendOn", "Send On"); lvSchedular.Columns.Add("Message", "Message"); Message.HeaderText = "Message"; Message.Name = "Message"; Message.FlatStyle=FlatStyle.Flat; SendTo.HeaderText = "Send To"; SendTo.Name = "SendTo"; SendTo.Visible = false; SendTo.Width = 0; dgvSchedular.Columns.Add(SendOn); dgvSchedular.Columns.Add(Message); dgvSchedular.Columns.Add(SendTo);
dgvSchedular.Columns["SendTo"].Visible = false; lvSchedular.Columns["SendOn"].Width = (lvSchedular.Width - 20) / 6; //100; lvSchedular.Columns["Message"].Width = (lvSchedular.Width lvSchedular.Columns["SendOn"].Width - 20) ;//400; lvSchedular.Columns["SendTo"].Width = 0; SendOn.Width = (dgvSchedular.Width - 60) / 6; //100; Message.Width = (dgvSchedular.Width - dgvSchedular.Columns["SendOn"].Width 60) ;//400 if (frmMain.cn.State == ConnectionState.Open) frmMain.cn.Close(); frmMain.cn.Open(); frmMain.cmd.CommandText = "Select * from Drafts Where DraftId <> 0 and DraftGorI = 'R'"; frmMain.dr = frmMain.cmd.ExecuteReader(); while (frmMain.dr.Read()) { Message.Items.Add(frmMain.dr["DraftName"].ToString()); } frmMain.dr.Close(); frmMain.cmd.CommandText = "Select * from Drafts Where DraftGorI = 'I'"; frmMain.dr = frmMain.cmd.ExecuteReader(); while (frmMain.dr.Read()) { Message.Items.Add(frmMain.dr["DraftName"].ToString()); } tvContacts.Enabled = false; dgvSchedular.Enabled = false;
this.loadYMDData(); this.loadContactsData(); tvSchedular.Focus();
41
Chapter 6 TESTING, VERIFICATION AND VALIDATION 6.1 Testing

Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. Software testing fundamentals define the overriding objectives for software testing. Testing is one of the steps in the software engineering process that could be viewed (psychologically, at last) as destructive rather than constructive.
6.1.1 Test Plan

The importance of software testing and its implications cannot be overemphasized. Software testing is a critical element of Software Quality Assurance and represents the ultimate review of the specifications, design and coding.
6.1.2 Testing Objectives

Testing is the exposure of the system to trial to see whether it produces correct output. Testing is a process of executing program with intent of finding an error. A good test case is one that has a high probability of finding a yet undiscovered error. In a word, tests are designed systematically so that they uncover different classes of errors and do so with a minimum time and effort. If testing is conducted successfully, it will uncover errors in the software. As a secondary benefit, testing demonstrate that software functions appear to be working according to specifications made by customer. It is important to keep in mind that, software testing cannot show the absence of defects, and rather it shows the error present in the software.
6.2 Testing Strategies

A strategy for software testing integrates software. Test case design techniques into well planned series that results in successful construction of software.
6.2.1 Unit Test

Unit testing focuses verification effort on the smaller unit of software designs the module. Important control paths are tested to uncover errors within the boundary of the module. The relative complexity of tests and errors deleted as a result is limited by the constrained. The local data structure is examined to ensure that data stored temporarily maintains its integrity during all steps in an algorithms execution. Boundary conditions are tested to ensure that module operates properly at boundaries. All independent paths though the control structure are exercised to ensure that all statements in a module have been executed at least once. All error-handling paths are tested. Testing is done for the incorrect variable names, data types, under flow, overflow etc.
6.2.2 Integration Test

Integration testing is a systematic technique for constructing the program structure while the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested module and build a program structure that has been dedicated by design. All the modules are combined in advance. The entire program is tested as a whole.
6.2.3 Validation Test

At the culmination of integration testing, software is completely assembled as a package, interfacing errors have been uncovered and corrected and a final series of software tests validation may begin.
Software validation was achieved through a series of black box test that demonstrates conformity with the requirements. Validation test was succeeded because the software functions in the manner that can be reasonably expected by the customer.
6.4.2 System Test

System testing is actually a series of difficult test whose primary purpose is to fully exercise the computer based system. Include Recovery Testing during crashes.
6.3 Test case design

6.3.1 While-Box Testing (Glass-box testing)
White-box tests focus on the program control structures. Test cases are derived to ensure that all statements in the program have been executed at least once during testing and that all logical conditions have been exercised. Knowing the internal working of the product, tests can be conducted to ensure that all gears mesh that is internally operations performs according to specification and all internal components have been adequately exercised. White Box testing is a case design method that uses the control structure of the procedural design to derive test cases. Using white box testing methods, the test cases should be guaranteed that all independent paths within a module have been considered at last once. Exercise all logical decisions on their true and false sides. Execute all loops at their boundaries and within their operational bounds. Exercise internal data structures to ensure their validity.
44
6.3.2 Black-Box Testing

Black-box testing focuses on the functional requirements of the software. It is not an alternative to White-box technique. Rather it is compulsory approach that is likely to uncover a different class of errors than white-box methods. Black-box testing attempts to find following types of errors Incorrect or missing functions. Interface errors. Errors in data structures or external database access. Performance errors and Initialization and termination errors.
6.4 Testing/Performance Analysis

The application will be tested on Personal computers. The following tables will be created to analyze and the performance of these tables will be analyzed.
6.5 Test Cases

Following are some of the important test cases and expected outcomes as per the testing plan. One to One Message sending. One to Many Message sending. Many to One Message sending. Many to Many Message sending.
6.5.1 One to One Message sending

In this we can send only one message to one person. And the massage size is up to 255 characters which may include symbols and numbers.
6.5.2 One to Many Message sending

In this we can send only one message to many persons. And the massage size is up to 255 characters which may include symbols and numbers.
6.5.3 Many to One Message sending

In this we can send many messages to only one person. And the massage size is up to 255 characters which may include symbols and numbers.
6.5.4 Many to Many Message sending

In this we can send many messages to many persons. And the massage size is up to 255 characters which may include symbols and numbers.
46
Chapter 7
RESULTS
Main form without connectivity
Figure 7.1 Main Form without port connectivity
The Figure 7.1 shows the Main welcome form, the progress bar at topmost right indicates that there is no connectivity with GSM Modem.
Main form with connectivity
Figure 7.2 Main Form with port connectivity
The Figure 7.2 shows the Main welcome form with connectivity to GSM Modem .Here in order to connect to modem user need to go to Tool select Options menu item and select proper port, baud rate, data bits, parity, and stop bits from drop down menu based on GSM Modem configuration.
48
Contact Form
Figure 7.3 Form for adding contacts.
Figure 7.3 shows the layout of contact form through which end user can individually add new contacts as well as create new groups to the database and save the contacts in the newly created groups.
49
Inbox form
Figure 7.4 Form for checking received messages.
Figure 7.4 shows the layout of inbox form which contains all the received messages based on specific dates / months/ years which can be checked later.
50
Sent items form
Figure 7.5 Form for checking sent messages.
Figure 7.5 shows the layout of sent item form which is an sub item under Message option, it also helps the end users to check whether the intended message is been sent to the clients or not and if sent whether it is valid information or not.
51
Scheduler form
Figure 7.6 Form for scheduling the messages that is to be sent later.
Figure 7.6 shows the basic layout of the scheduler form, this form is basically used when some information is to be sent to the clients but at some specified dates (for example any event invitation / starting date for semester in this case).
52
Send Form
Figure 7.7 Form for sending messages to clients.
Figure 7.7 show the basic layout of the send form which is used to send the pre-stored messages in drafts form to the clients. This form also allows the end user to select the client and also to select the message that has to be sent, and it also provides the message status to the end user.
53
Figure 7.7.1 Form showing the process of selecting the client and the message.
Figure 7.7.1 shows the process of sending the messages to clients. Initially process proceeds by first traversing through the root node to the group node to which client belongs and then selecting the intended client by clicking on checkbox similarly for selecting message to be sent initially proceed through message centre which is root to group to which message to be sent belongs then select the message by clicking on checkbox for specific intended message and finally click on the send button i.e. Green highlighted arrow in the figure 7.7.1
54
Draft form
Figure 7.8 Form for storing messages in drafts.
Figure 7.8 shows the layout of draft form which contains the messages that are to be sent to the clients. All the messages need to be manually generated providing specific names to the messages and need to be stored in some specific group of messages to which newly generated message belongs. Once the message is typed completely it needs to be saved by clicking on save button on the tool strip. [NOTE: Messages with only 255 characters are accepted.]
55
Figure 7.8.1 Draft form displaying process of creating new draft within a group.
Figure 7.8.1 show the view of draft form after selecting the group to which new message needs to be added. Then proceed in by providing new title to the message and then add the actual message content in the Message block as shown in figure 7.8.1.
56
Figure 7.8.2 Draft form displaying content of message group after adding new message.
Figure 7.8.2 displays the recently added message to group with blue highlighting in above figure.
57
Exit form
Figure 7.9 Alert message before exiting the application.
Figure 7.9 shows the message box requesting user confirmation before exiting from the application, if the user clicks on Yes button then application is closed and if user continues to work with application then he can click on No button .This facility helps user by preventing accidentally terminating the application while working on it.
58
CONCLUSION
Two way student information management system using cellular technology aims at reducing the manual operations of the institute as well as reduces the burden of faculty members. This application moves towards to retrieve the whole student information management system using cellular technology. A single administrator can handle the entire information of the overall students in the institute efficiently.
Future Enhancement
Two way student information management system using cellular technology currently works efficiently for texted data to be sent or received from the guardians. Further extended to this application following operations can be implemented
Automated response
This operation provides the facility of responding to the queries that is obtained from the guardians side which will still more reduce the burden of the administrator.
Efficiency
Efficiency can be increased by increasing the speed of the management system, also by increasing the size of the characters from 255 to desired size.
59
REFERENCES
[1] Pro C# with .NET 3.0 - Andrew Troelsen, Special Edition, Dream tech Press, India, 2007. [2] Programming C# 4. -Ian Griffiths, Matthew Adams, Jesse Liberty,6th edition,Oreilly Publication,2010. [3] Software Engineering -Ian Somerville, 8th edition, Pearson Education 2007. [4] Database Management System -Elmasri and Navathe, 5th Edition,AddisonWesley, 2007. [5] Microsoft Visual Studio 2008 MSDN Library
60

Two Way Student Information Management System Using Cellular Technology

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Two Way Student Information Management System Using Cellular Technology

Transféré par

Droits d'auteur :

Formats disponibles

VISVESVARAYA TECHNOLOGICAL UNIVERSITY BELGAUM-590002

Mr. Sayyan N. Shaikh

Under the Guidance of

Prof. Saleem .Hebbal

Department of Computer Science & Engineering

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

Mr. Ganesh U.Bhat USN: 2VD06CS018 Ms.Pavitra P. Kini USN: 2VD07CS031

Dedicated to Our Beloved Parents And Teachers

INTRODUCTION LITERATURE SURVEY

SYSTEM ANALYSIS AND DESIGN

IMPLEMENTATION TESTING, VERIFICATION AND VALIDATION

6.5 Test Cases

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.1 Windows XP/2000 Advantages

The Windows GUI

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.2 Technologies used Introduction to .NET

2.2.2 Components Of .NET Framework

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

1) Common Language Runtime (CLR)

3) Common Language Specification (CLS)

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.2.3 .NET vs. Java

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.2.4 .NET Framework advantages

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.2.6 About GSM Modem

2.2.7 Application Areas

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.2.8 Specification for GSM Modem

Figure4.1 SIM300 GSM Modem

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

SIM card interface

Network status indication LED lamp

2.3.1 AT Command syntax

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.3.2 Basic syntax

2.3.3 S parameter syntax

2.4 Database Used

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

2.4.2 Features Microsoft Office Access 2010

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

3.1 Feasibility Analysis

3.1.1 Organizational Feasibility

3.1.2 Technical Feasibility

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

3.1.3 Operational Feasibility

3.2 Software Requirement Specification

3.2.2 Introduction Purpose

3.2.3 Definitions, Acronymes, Abbreviations C#.NET

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

3.3 Developers Responsibilities Overview

3.3.1 Specific Requirements Functional Requirements

Non Functional Requirements

External Interface Requirements

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

SYSTEM ANALYSIS AND DESIGN

4.2 System Design

TWO WAY STUDENT INFORMATION MANAGEMENT SYSTEM USING CELLULAR TECHNOLOGY

4.2.1 Data Flow Diagram for System Design

Figure 4.2.1.1 DFD of Two Way Student Information Management System