final doc

1. INTRODUCTION:Mobile based COLLEGE PORTAL is application which reduces the manual effort by introducing online service. It is a mobile application that provides the information about our college to students/anonymous users. In some situations students might be out of stations or they may be non-local students if they dont know anything about what is new in college or what is happening in the college in that case if he/she can generally browse the net and search for our college website or may directly go to that college and consult the administration ,so it is such a big process. It is such a waste of time, so we are introducing new online application. This application allows the Students to browse the college website through mobile. Students need to register in application along with their details like student-id, student name, d.o.b, gender, personal contact, and current address email-address. After registration she/he can check for desired details about attendance, results, and events.1.1MOTIVATION:

In present scenario, we can know the information regarding students, attendance, exam results, and events going on in the college either through notice board or by consulting the administration. so to reduce the student effort. we are introducing this application mobile based college portal management system.1.2PROBLEM DEFINITION:In order to overcome the present problem this application "college portal" is useful in knowing information like attendance, exam results, and events from anywhere without wasting user time and without much effort.1.3OBJECTIVE OF PROJECT:The main objective of the project is that introducing mobile services to the college portal management system and reducing the time of the students. This application which reduces the manual effort by introducing online service. It is a mobile application that provides the information about the students attendance, results and events. The purpose of this Software Requirement Specification (SRS) is to help the project. It is provided with some requirements which are used in mobile based COLLEGE PORTAL . All parts; design, coding andtesting will be prepared with helping of SRS. The purpose of this document is todevelopers as to what is to be expected and how the componentsof the system are to work with each other with external systems.This document will be checked by group members supervisor and it willcorrected by members if supervisor orders.1.4LIMITATIONS OF PROJECT: It is time consuming. The information that is given to the user is done manually.1.5ORGANISATION OF DOCUMENTATION

The organization of document provides the basic report of the stages encountered in the project development, in the form of chapters.

Chapter1:

The Chapter1 provides the Introduction of the project.Chapter2:

The Chapter2 deals with the literature survey,which provides the information regarding the need of developing the project .

Chapter3:

The Chapter3 specifies about the software requirements, which help in building the project for developing the code, and a database to store the information.Chapter4:

The Chapter4 specifies feasibility report and design phase of project.Chapter5:

The Chapter5 shows the detail Implementation of module description.Chapter6:

The Chapter6 specifies the Testing, in which Testing refers to the testing methodologies.

Chapter7: The Chapter7 Result, which specifies the output of the code generated. Chapter8:

The Chapter8 is the Conclusion and Future Scope part.

Chapter9: This chapter9 specifies Bibliography which consists of additional reference sites and books.

Chapter10:

This chapter10 Appendix is to specify the additional information regard the code and some expansions and etc.2. LITERATURE SURVEY2.1. INTRODUCTION:

After analyzing the requirements of the task to be performed, the next step is

to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution.

2.2 EXISTING SYSTEM:

In the existing system if we want to know about any details of our college we have go through the web-site of our college (or) we have to directly go to the college and enquiry.2.3 LIMITATIONS IN THE EXISTING SYSTEM:

In this existing system we have to know about the web-site of our college.

We have to enquiry all the particular detail so it is time taking process.

The information that is to be given is done manually2.4 PROPOSED SYSTEM:

In this proposal system we are providing the mobile application to the collegesystem. In this mobile application we can search about our desired module like attendance,events,results from everywhere and at anytime.

2.5 CONCLUSION:

By this mobile based application college portal,a user can get desired information about his/her attendance ,results and events that are to be held in our college.3. ANALYSIS3.1 INTRODUCTION:The model that is basically being followed is the SPIRAL MODEL, which states that the phases are organized in a linear order. First of all the feasibility study is done. Once that part is over the requirement analysis and project planning begins. If system exists any modification and addition of new module is needed, analysis of present system can be used as basic model.

The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model the sequence of activities performed in a software development project are: -

Requirement Analysis

Project Planning

System design

Detail design

Coding

Unit testing System integration & testing

Here the linear ordering of these activities is critical. End of the phase and the output of one phase is the input of other phase. The output of each phase is to be consistent with the overall requirement of the system.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.The following diagram shows how a spiral model acts like:

Fig 3.1 : Spiral Model3.2 SOFTWARE REQUIREMENT SPECIFICATIONSThis document is the complete product requirement specification for the Mobile based college portal . This is the only document that contains all information regarding the requirements placed on the mobile based college portal by the administrator, catalogued in an unambiguous fashion.

Unless otherwise stated, this document, and any future revisions of this document,supersedes all other requirements documents that exist for the mobile based college portal.

3.2.1 USER REQUIREMENTS: New users give his complete personnal, address and phone details for registration. student can search for attendance student can search for results. student can search for events.3.2.2 SOFTWARE REQUIREMENTS

JDK 1.6

Apache tomcat server

Oracle 10g

Android SDK

Eclipse IDE

3.2.3 Hardware Requirements:

Android mobile device.

2GB RAM.

HDD 40 GB Hard Disk Space.

Intel Pentium 43.3 CONTENT DIAGRAM OF PROJECT:

3.4 CONCLUSION

The Analysis and Software Requirement Specification (SRS) is to help the project. It is provided with some requirements which are used in mobile based college portal management system. All parts; design, coding and testing will be prepared with helping of SRS. The purpose of this document is to detail the requirements placed on the mobile based college portal management system and serves as a contract between the students and the college as to what is to be expected of the mobile based college portal management system, and how the components of the system are to work with each other with external systems. This document will be checked by group members

supervisor and it will corrected by members if supervisor orders.

4. DESIGN4.1 INTRODUCTION:

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 designers 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 customers 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 ER/UML DIAGRAMS ER-DIAGRAMS: The relation upon the system is structure through a conceptual ER-Diagram, which not only specifics the existential entities but also the standard relations

through which the system exists and the cardinalities that are necessary for the

system state to continue.

The Entity Relationship Diagram (ERD) depicts the relationship between the dataobjects. The ERD is the notation that is used to conduct the date modeling activitythe attributes of each data object noted is the ERD can be described resign a dataobject descriptions.

The set of primary components that are identified by the ERD are Data object

Relationships Attributes

Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

E-R (Entity-Relationship) Diagram is used to represents the relationship between

entities in the table.

The symbols used in E-R diagrams are:

SYMBOL PURPOSE

RepresentsEntitysets

RepresentsEntitysets

.

Represent attributes.

Represent Relationship Sets.

Line representsflow

FIG.4.2.1 ER-DIAGRAM FOR COLLEGE PORTAL MANAGEMENT SYSTEM4.2.2 UML DIAGRAMS:A.USE CASE DIAGRAMS:

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 the external point of view. The actor is outside the boundary of the system, where as the use cases are inside the boundary of the system.

Fig 4.2.2(A) usecase diagram for user

B.CLASS DIAGRAMS:

Class diagrams to describe the structure of the system. Classes are abstraction that specifies the common structure and behavior of a set of objects. Class diagrams describe the system in terms of objects, classes, attributes, operations and their association

Fig 4.2.2(B) class diagram for college portal management systemC.SEQUENCE DIAGRAMS:

SEQUENCE DIAGRAM:

Sequence diagram depicts the interactions between class instances, in the form of method calls and call returns shows a specific scenario of execution in the system in terms of object instances. This diagram focuses on the time ordered messages between objects that collaborate to accomplish some task.

Fig 4.2.2(C)sequence diagram for college portal management systemD.COLLABARATION DIAGRAMS:

A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML). The concept is more than a decade old although it has been refined as modeling paradigms have evolved.

Fig 4.2.2(D)collaboration diagram for the system

4.2.5. ACTVITY DIAGRAMS:

A State diagram/Activity diagram is a specification of the sequences of states that an object or an interaction goes through in response to events during its life, together with its responsive action. Every state diagram is having one entry and exit state. And the state can have any number of sub-states. The above state diagram represents, how admin will interact with other objects, and how he will perform actions and change his state.

4.3 MODULE DESIGN AND ORGANISATION:

Tab 4.3(a) Student details table

Tab 4.3(b) year table

Tab 4.3(c) Year and Sem id table

Tab 4.3(d) Sem table

Tab 4.3(e) Branch table

4.3.1Attendance module:This is the first module in this college portal management system .In this module user can check the attendance status by entering the student details and there by picking a date he/she is viewed whether they are present/absent on the particular date.Tab 4.3.1(a) attendance table

4.3.2. Result moduleThis is the second module of the college portal management system.In this results module user can know about results according to their hall ticket number,year,branch and semester.user can also choose examination type and examination category.After entering student details and choosing examination type & category student can get marks according to his/her selected subject.

Tab 4.3.2 Results table

Tab 4.3.2(a) Exam category table

Tab 4.3.2 (b)Exam type table

Tab 4.3.2(c) Subject table

Tab 4.3.2(d) Result-id table

Tab 4.3.2(e)Marks table

4.3.3 Events module:This is the third and final module in college portal management system.Event management module gives information about the events that are going to be held in the college.it also gives the information about the event venue,timings,event date and what type of events are going to be held?whether they are technical or cultural,by whom the events are going to be conducted ?.All these information can be known in this module.

Tab.4.3.3.Results table

Tab 4.3.3(a) Event details table

5. IMPLEMENTATION & RESULTS5.1 EXPLANATION OF KEY FUNCTIONS:

5.1.1 OUTPUT SCREENS:

This chapter describes about the output screens. Following are the output screens of our project.

1. Home page

2. Student details

3. Attendance information

4. Results information

5. Events information

1. HOME PAGE:

Scr: 5.1.1(A) screen shot for home pageNAVIGATION: Go to - >eclipse->select project file->run->click on college portal app.2. STUDENT DETAILS:

Scr: 5.1.1(B) screen shot for student details

NAVIGATION: Go to - >eclipse->select project file->run->click on go to college portal button-> enter student details.3. ATTENDANCE INFORMATION:

Scr: 5.1.1(C) screen shot for attendance information

NAVIGATION: Go to - >eclipse->select project file->run->click on college portal->select attendance module->pick a date->check attendance.4.RESULTS INFORMATION:

Scr 5.1.1(D) screen shot for results information

NAVIGATION: Go to - >eclipse->select project file->run->click on college portal button->enter student details->select results->choose exam & category type->check/get results.5. EVENTS INFORMATION:

Scr: 5.1.1(E) screen shot for events information

NAVIGATION: Go to - >eclipse->select project file->run->click on college portal button->enter student details->select events->choose event type->check events information.5.2 RESULT ANALYSIS:

FEASIBILITY REPORT

Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:

Technical Feasibility

Operation Feasibility

Economical FeasibilityTECHNICAL FEASIBILITY:

The technical issue usually raised during the feasibility stage of the investigation includes the following:

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required to use the new system?

Will the proposed system provide adequate response to inquiries, regardless of the number or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and data

security?

OPERATIONAL FEASIBILITY:Proposed projects are beneficial only if they can be turned out into information system. That will meet the organizations operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following:

Is there sufficient support for the management from the users?

Will the system be used and work properly if it is being developed and implemented?

Will there be any resistance from the user that will undermine the possible application benefits?

This system is targeted to be in accordance with the above-mentioned issues.

Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.

ECONOMIC FEASIBILITY:

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs.

The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at ABC Tech, There is nominal expenditure and economical feasibility for certain.5.3 METHOD OF IMPLEMENTATION:

HOME ACTIVITY:

import android.app.Activity;

import android.content.Intent;

import android.os.Bundle;

import android.provider.Contacts.Intents;

import android.view.View;

import android.view.View.OnClickListener;

import android.widget.Button;

public class Homeactivity extends Activity{

Button atd,res,evt;

@Override

protected void onCreate(Bundle savedInstanceState) {

// TODO Auto-generated method stub

super.onCreate(savedInstanceState);

setContentView(R.layout.home);

atd=(Button)findViewById(R.id.atdet);

res=(Button)findViewById(R.id.reset);

evt=(Button)findViewById(R.id.eveet);

atd.setOnClickListener(new OnClickListener() {

@Override

public void onClick(View v) {


Intent i=new Intent(Homeactivity.this,AtdsActivity.class);

startActivity(i);

}

});

res.setOnClickListener(new OnClickListener() {

@Override



Intent i1=new Intent(Homeactivity.this,ResultActivity.class);

startActivity(i1);

}

});

evt.setOnClickListener(new OnClickListener() {

@Override



Intent i2=new Intent(Homeactivity.this,eventlist.class);

startActivity(i2);

}

});

}

}

EVENTS ACTIVITY:

package com.view;

import java.util.ArrayList;

import org.json.JSONArray;

import org.json.JSONException;




import android.widget.AdapterView;

import android.widget.ArrayAdapter;

import android.widget.EditText;

import android.widget.Spinner;

import android.widget.AdapterView.OnItemSelectedListener;

public class EventsActivity extends Activity{

private EditText eventname;

private EditText venet;

private EditText time;

private EditText dateet;

private EditText desp;

String request,response;

@Override




setContentView(R.layout.events);

eventname=(EditText)findViewById(R.id.eventnameet);

venet=(EditText)findViewById(R.id.venet);

time=(EditText)findViewById(R.id.timet);

dateet=(EditText)findViewById(R.id.dateet);

desp=(EditText)findViewById(R.id.despet);

eventdesc();

}

void eventdesc(){

ArrayList name=new ArrayList();

ArrayList desc=new ArrayList();

ArrayList venu=new ArrayList();

ArrayList date=new ArrayList();

ArrayList timings=new ArrayList();request=ConnectionUtility.url+"RegistrationServlet?action=event&id="+eventlist.selectedtypeid;

System.out.println(request);

response=ConnectionUtility.send(request);

System.out.println(response);

JSONArray array;

try {

array = new JSONArray(response);

for (int i = 0; i < array.length(); i++) {

name.add(array.getJSONObject(i).getString("name"));

desc.add(array.getJSONObject(i).getString("desc"));

venu.add(array.getJSONObject(i).getString("venue"));

date.add(array.getJSONObject(i).getString("date")); timings.add(array.getJSONObject(i).getString("timings"));

}

eventname.setText(name.get(0));

venet.setText(venu.get(0));

time.setText(timings.get(0));

desp.setText(desc.get(0));

dateet.setText(date.get(0));

} catch (JSONException e) {

// TODO Auto-generated catch block

e.printStackTrace();

}

}

}

ATTENDANCE ACTIVITY:

package com.view;

import java.util.ArrayList;

import java.util.Calendar;

import org.json.JSONArray;

import org.json.JSONException;


import android.app.DatePickerDialog;

import android.app.Dialog;



import android.view.View.OnClickListener;

import android.widget.Button;

import android.widget.DatePicker;

import android.widget.EditText;

import android.widget.TextView;

public class AtdsActivity extends Activity{

Button pickdate,ATNDATE;

EditText attendancestatus;

TextView selcteddate;

static final int DATE_DIALOG_ID=0;

private int mYear,mMonth,mDay;

String request,response=null;

@Override




setContentView(R.layout.attendance);

ATNDATE=(Button) findViewById(R.id.ATDbutton1);

pickdate=(Button)findViewById(R.id.attendancedate);

attendancestatus=(EditText)findViewById(R.id.attendancestatuset);

selcteddate=(TextView) findViewById(R.id.attndancetextView1);

getdate();

System.out.println("selected date is"+selcteddate.getText());

ATNDATE.setOnClickListener(new OnClickListener() {

@Override



getatndance();

}

});

}

void getdate(){

final Calendar cal=Calendar.getInstance();

mYear=cal.get(Calendar.YEAR);

mMonth=cal.get(Calendar.MONTH);

mDay=cal.get(Calendar.DATE);

updateDisplay();

pickdate.setOnClickListener(new OnClickListener() {



showDialog(DATE_DIALOG_ID);

}

});

}

public void updateDisplay()

{

selcteddate.setText(new StringBuilder().append(mMonth+1).append("-").append(mDay).append("-").append(mYear));

}

@Override

protected Dialog onCreateDialog(int id) {


Dialog D = null;

switch (id) {

case DATE_DIALOG_ID:

D= new DatePickerDialog(AtdsActivity.this, mDataSetListener, mYear, mMonth, mDay);

}

return D;

}

private DatePickerDialog.OnDateSetListener mDataSetListener=new DatePickerDialog.OnDateSetListener() {

@Override

public void onDateSet(DatePicker view, int year, int monthOfYear,

int dayOfMonth) {


final Calendar c=Calendar.getInstance();

mYear=year;

mMonth=monthOfYear;

mDay=dayOfMonth;

updateDisplay();

}

};

void getatndance(){

String stuid=DetailsActivity.getstudentid;

String selcteddateforatndance=(String) selcteddate.getText();

request=ConnectionUtility.url+"AttendanceServlet?action=attendance&student_id="+stuid+"&date="+selcteddateforatndance;

System.out.println(request);

response=ConnectionUtility.send(request);

System.out.println(response);

try {

JSONArray array=new JSONArray(response);

ArrayList status=new ArrayList();

for (int i = 0; i < array.length(); i++) {

status.add(array.getJSONObject(i).getString("status"));

}

if(status.size()==0){

attendancestatus.setText("not avialble");

}else {

attendancestatus.setText(status.get(0));

}

} catch (JSONException e) {

// TODO Auto-generated catch block

e.printStackTrace();

}

}

}6. TESTING & VALIDATION6.1. INTRODUCTION:

Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. In fact, testing is the one step in the software engineering process that could be viewed as destructive rather than constructive.

A strategy for software testing integrates software test case design methods into a well-planned series of steps that result in the successful construction of software. Testing is the set of activities that can be planned in advance and conducted systematically. The underlying motivation of program testing is to affirm software quality with methods that can economically and effectively apply to both strategic to both large and small-scale systems.STRATEGIC APPROACH TO SOFTWARE TESTING:The software engineering process can be viewed as a spiral. Initially system engineering defines the role of software and leads to software requirement analysis where the information domain, functions, behavior, performance, constraints and validation criteria for software are established. Moving inward along the spiral, we come to design and finally to coding. To develop computer software we spiral in along streamlines that decrease the level of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit testing begins at the vertex of the spiral and concentrates on each unit of the software as implemented in source code. Testing progress is done by moving outward along the spiral to integration testing, where the focus is on the design and the construction of the software architecture. Talking another turn on outward on the spiral we encounter validation testing where requirements established as part of software requirements analysis are validated against the software that has been constructed. Finally we arrive at system testing, where the software and other system elements are tested as a whole.

TESTING OBJECTIVES:Testing is a process of executing a program with the intent of finding an error.

A good case is one that has a high probability of finding an error. A successful test is one that uncovers a yet undiscovered error. If testing is conducted successfully it will uncover errors in the software. Testing cannot show the absence of defects, it can only show the software defects are present.

TESTING TYPES

A product can be tested in one of two ways.

1. Black Box Testing

The concept of the black box is used to represent a system whose inside workings or no available for inspection. In a black box, the test item is treated as a black since its logic is unknown: all that is known is what goes in and what comes out, or the input and output. Here, in this Electronic Management Information System the internal functionalities have been tested.

2. White Box Testing

The main use of the white box testing is in error based testing. It is predict on close examination of procedural detail logical providing test cases that exercise specific sets of conditions and/or loops test path enough the software. Basis path testing is a white box testing technique. The basis path method enables the test case designer to derive a logical complexity of a procedural design and use this measure as a guide for defining as basis set of execution path.

TESTING STRATEGIES

A strategy for software testing integrates software test case design methods into a well-planned series of steps that result in the successful construction of software. Testing is the set of activities that can be planned in advance and conducted systematically. The underlying motivation of program testing is to affirm software quality with methods that can economically and effectively apply to both strategic to both large and small-scale systems.

1. Unit Testing

Unit testing focuses on verifying the effort on the smallest unit of software module. The local data structure is examined to ensure that the date stored temporarily maintains its integrity during all steps in the algorithms execution. Boundary conditions are tested to ensure that the module operates properly at boundaries established to limit or restrict processing.

2. Integration Testing

Data can be tested across an interface. One module can have an inadvertent, adverse effect on the other. Integration testing is a systematic technique for constructing a program structure while conducting tests to uncover errors associated with interring.

3. Performance Testing

Performance Testing is used to test runtime performance of software within the context of an integrated system. Performance test are often coupled with stress testing and require both software instrumentation.6.2. DESIGN OF TEST CASES AND SCENARIOSTest case 1: entry of student details

Test Objective: as the student enters the details and clicks on the submit button it redirects to another page

Test Description: The student click on the submit button the total details are stored in database

Requirements Verified: Yes

Test Environment: : Apache Tomcat Server

Oracle 10g

Ecllipse IDE

Android SDK

JDK 1.6

Test Setup/Pre-Conditions:

1) The web server should be in ON state

2) The system should have a connection with the database.

ActionsExpected Results

The student clicks on submit button if they are valid then it redirects to another pageit gives entry of user details successful.

Pass: Yes Conditions pass: No Fail: No

Problems / Issues: NIL

Notes: entry of student details is successesful

6.2.1 Test Case Report1:6.2.2 Test Case report 2:Test case 2: selection of the module

Test Objective: after the entry of student details the student selects the module.

Test Description: : after the entry of student details if they are valid it redirects to next page.After the redirection student should select any one of the module from three modules



Oracle 10g Eclipse IDE

Android SDK

JDK 1.6





The student selects any module from attendance,results,eventsRedirection to modules page is succesfull



Notes: redirection to next page is succesfull

6.2.3Test Case report3:Test case 3: attendance

Test Objective: student clicks on attendance and checks the status

Test Description: The student selects the attendance ,picks a date then student is viewed the attendance status of his/her as present/absent on the chosed date


Test Environment: Apache Tomcat Server


Android SDK

JDK 1.6





Student clicks on attendance and enters the valid details.We can confirm the result of this test case as success if the attendance status is displayed on the date picked by the student.



Notes: attendance status is successfully displayed.

6.2.4 TestCase report 4:Test case 4: results

Test Objective: To check whether the results are displayed or not.

Test Description: The student enters the details like year,branch,semester,subject and searches for the result with those details.




Android SDK

JDK 1.6





students enters the valid details to enter the result page We can confirm the result of this test case as success if the marks are displayed according to the search.



Notes: results are successfully displayed

6.2.5TestCase report5:

Test case 5: events

Test Objective: To allow a valid student to check for the events that are to be held in the college.

Test Description: The user selects the events module and it is redirected to the events page. student can check the events according to the branch-wise and also year-wise .student can also check whether it is a cultural event or the technical event. student can also see the venue, timings and by whom the events are conducted by.


Test Environment: Apache Tomcat Server


Android SDK

JDK 1.6





Student enters the valid details to enter the events pageWe can confirm the result of this test case as success if the events ,event-venue, event-type, event-timings are displayed.



Notes: events page is successfully displayed.

7. CONCLUSIONProject Conclusion:If we are new to college or unable to know information about attendance, results, events conducted in college this application is very useful . This application is divided into three modules viz.., attendance management, results management, events management .As the user registers it displays the modules. By this student can choose his/her desired module and can the get the information he/she is looking for.If user want to know information about attendance by giving student -id, branch-id,year- id and sem id, he/she can know his attendance percentage .in same manner by giving required ids he /she can know the internal and external, regular and supplementary results. If user want to know about the events conducted in college by selecting the events module he/she can know which types of events? at which place?at what time? Can be known in a easy and efficiency manner.. Using this application user can save his time.FUTURE ENHANCEMENTS: In future we can provide notifications regarding attendance updates, results updates, events updates..

In future by need of user, we will add information about the faculty.

We can provide the total information about infrastructure, transportation etc..,

REFERENCES:

1) http://developer.android.com/index.html

2) http://www.ayokasystems.com/enterprise-systems-solutions/mobileapplications-

for-manufacturing

3) http://www.maketick.com/enterprise-mobility/impact-of-mobile-applicationson-

health-sector-in-2012.php

4) http://www.loc-aid.com/node/525) http://www.onjava.com/

6) http://www.oracle.com/technetwork/java57

Documents

final doc