Online Gazette Android Application

Abstract

The Main AIM of online gazette is to provide a platform for students to exhibit their talent. By this project students get more knowledge. This Online Gazette application is not only for students but also to others who want exhibit/publish their articles. This is a java based android application where student can publish their articles, read various articles by registering through their email id.

This Online Gazette application also contains national and international magazine. Every registered user can view and post their ideas because this is not a printed version as it leads to wastage of paper. Large amount of data can be stored. This is user friendly interactive place for students. This android application maintains all information in a centralized database. Students can share their ideas online. Through this application students can comment and rate the articles posted by others.

Modules

Guest: Guests can read articles, rate them.

Registered Members: Registered members can publish their own articles.

Administrator: Admin can delete the registered users, thus admin has all privileges. Can post news which will be visible at the homepage.

Hall Ticket Generation System Java Project

Abstract:

Hall ticket generation system is a project which constitute a computerized module aimed at replicating online hall ticket generation process.

Existing System:

In the existing system all activities mostly includes a lot of manual calculations and is mostly paper based. Distribution of hall tickets is also done manually which is a time wastes process. Students may loss hall ticket in some cases.

Hall Ticket Generation SystemProposed System:

The proposed system  allows  the registered students to login into the system which prevents unauthorized access.

Modules:

Student Module:

Students have to get  registered to the website which includes providing  their Personal details like Name, Address, Phone No, etc., and a photo, to the enroll himself into the System. After creating the hall ticket, the admin will mails the link of soft copy to every student who have registered.

Admin Login:

Admin can view who has enrolled into the system, and can see all the new enrolment on his login.

Software Requirements:

Languages                               : Java.

Database System                    : MYSQL

Conclusion:

This system allows students to enroll themselves into the system by registering their names or by sharing their details to admin.

Time Table Management System Java Project

Abstract:

Time table management system is a project which is developed to provide better support for lecturers and students in a college. This Time Table Management System provides a function to view timetable for the specific lecturer and the master timetable for that semester. Lecturer can inquire about classes availability and can book for the free classes. Students can view their functionality like adding and dropping subjects. Students can view and get the registration slip from the system. Timetable management system also contains a database, which stores the lecturers and students personal details.

Time Table Management System

Existing System:

The existing Time Table Management System contains a manual timetable system which is used by post graduates and under graduates. This manual system may lead to clashes of data in the timetable produced. The existing timetable always change and involved many lecturer to handle it. It’s taking too much of their time. The conclusion is they need a system to help and improve the process of preparing the timetable.

Proposed System:

The proposed Time Table Management System is a automatic timetable management system which generates time table automatically. This java project will help to manage all the periods automatically. This system will also help the faculty to view timetable from anywhere. This system also manages the timetable when any lecture is absent late coming or early going. By using this system lectures can apply online leave.

 

Android Breakout game and Application development

Problem Description:

To create a brick break out game. In the Android Breakout game  the player can be able to break statically located bricks placed on the top of the screen using a ball. The ball keeps on moving from top to bottom. A paddle at the bottom can be used to change the direction of the ball and thus avoid the ball touching the ground.  If the ball touches the ground the player will lose the game but if the player break all the bricks then the player will be a winner.

User’s Guide:

The Android Breakout game is delivered in a zip file called radnim-1_task3.zip. To run the application one must download the file and extract to a folder. Import the folder as an eclipse project (You must have android SDK installed in eclipse).

After fixing the project setup, right click the folder and run as Android Application.

When the application starts it will look like the figure 1. After all bricks are break as shown in fig.2 the player will see a winning message on the screen.
If the ball touches the ground as shown in fig.4 the player will lose the game. However the player can press Play Again to play once again.

Android Breakout game

Algorithm Description

There are 2 activities in the application. “MainActivity” which is loaded as soon as the application start. Another activity is “GameStatusActivity” which is used to display the result of the game (i.e if the player wins or lost).

The “GameView” class contains the main logic related to the creation of bricks, ball and paddle. Each of them is created as an instance of “GameObject”. The “GameObject” has an instance of bitmap and the x, y coordinates. The “GameLogic” controls the status of the game. The game has 3 statuses (Running, Win, and Lost). This class extends the “Thread” class and overrides the run method. The update method in “GameView” has the logic to move the ball to a suitable position depending on the collision with wall, block or paddle.

The collide method in the “GameObject” helps to identify if the ball is collided with other “GameObject” instances. The update method in the “GameObject” updates the x, y position of the ball.

The onTouchEvent of “GameView” handles touch screen motion events.

System Description

Limitations

There are many limitations in terms of look and feel. But one of the major limitation is sometimes the ball does not bounce back when it touch paddle. I tested several times but this occurs rarely and only once. I don’t understand the reason.  Also the ball don’t move horizontally when it touches the middle of any block or paddle. There is something to do with the x, y position of the ball, I tried but didn’t find a solution.

Discussion

Have not been in any discussions with in the forum. As I am very busy usually with my work and most of the conversations are in English. However I do read other students comments and ideas. They are really very helpful. Initially I tried to learn about the game development fundamentals. Later I followed the android forum that is very helpful.

Android Breakout game Diagram

Test runs 

No tests are available to run.

References

  1. http://developer.android.com/resources/samples/LunarLander/index.html
  2. Pro Android Games.
  3. Practical android 4 games development.
  4. Beginning Android 4 Games Development.

Shopping Cart Android Project

Introduction

Purpose

The purpose of this Shopping Cart Android Project document is to describe the architecture and system design of the Shopping Cart software described in the Shopping Cart Business Requirements Document. The intended audiences of this document are the Android developers, QA testers, and system owners that will collaboratively develop the system and possibly extend the system in the future. The Shopping Cart software is design to create and managed grocery shopping lists.

Scope

The document describes the design and implementation details of the Shopping Cart software. The major functions of the Shopping Cart software are to create and manage shopping lists/stores. The Shopping Cart software is to be developed for the Android platform using the object oriented design methodology.

  1. Shoppers must access the Shopping Cart application from an Android device (Smart Phone, etc.)
  2. The Shopping Cart application must be accessed by the shopper to create and manage shopping lists/stores.
  3. The Shopping Cart application is a standalone application with no external interfaces.
  4. All interfaces are managed by the Android system.
  5. The Android system’s local database would be used to store all data saved by the Shopping Cart application

Overview of Document

The Software Design Document is divided into five sections with subsections. The sections in this Software Design Document are:

  1. Introduction
  2. Use Case Realizations
  3. Architectural Design
  4. Data Structure Design

Glossary

Android – programming language

Business Requirements Document – a document that describes the requirements for a business process that    must be delivered to provide value.

Developers – person who writes the code or develop the software

Interfaces – a piece of software\hardware that provide access to a system’s resources

QA Tester – software tester who ensures software quality

Standalone Application – an application that does not interact with any external interfaces.

System – software to be developed 

Systems Owner – person(s) that owns the system

Testers – person(s) who perform the testing of the software to ensure quality of the end product

Use Case Realizations

The use case realizations are depicted by the use case diagram and the use case narratives.

Actors

Shopper

Information: The Shopper is a user who uses the Shopping Cart application to simplify their shopping experience by creating grocery shopping lists, creating stores, associating lists to stores, associating items to categories/aisles, and saving the list/contents for current or future use.

Use Case Diagram

Shopping Cart Use Case Diagram