Software construction IP 2

profilewilden
wilden_project.docx

21 | Page

Conference Android Application

Software Reengineering Project Document

SWE400-1402B-01 Software Construction

Project Proposal

· Approved

· Not Approved

Sr.#

Student ID

Student Name

*Signature

1

ID

Name1

2

ID 2

Name 2

3

*The candidates confirm that the work submitted is their own and appropriate credit has been given where reference has been made to work of others

Supervisor Name:

Designation: ____________________

Signature: ____________________

Co-Supervisor Name: ____________________

Designation: ____________________

Signature: ____________________

Abstract

My Conference android application is used to book meetings between attendees in the conferences and seminars. Attendees can book meetings with other users in the conference. Attendees have to register in the application.

Introduction

My Conference application is used by different seminars and conferences to assist users to book meetings with each other. The attendees in the conference need to be registered in the application. These users can login and see other registered users in the conference. They can access name, company and details of other users. These users can book meeting with other attendees. The other attendee will see who has booked meeting with him. Meetings can be booked with meetings names, meeting details and time. The application interacts with java server (J2EE project) to receive request from application. Requests are processed in MySQL database and response is sent back to application.

Application has the following modules to be made:

1. Registration

2. Sending password to Email

3. Attendees list display

4. Book Meetings

5. Database management

Motivation and Scope

My Conference android application streamlines the meeting appointments process traditional reporting systems. It replaces the manual meeting booking system which consumes time. This advanced software can eliminate all time constraints. It allows users to check other user’s company’s names and their designations before meeting. You do not have to do special meetings.

System Architecture

Our system will be java web and mobile platform based.

Goals and Objectives

The goal and objective of our project is:

· To optimize the meetings appointment process in the conferences.

· It will be simple and user friendly

· As its paperless system and it will be web based. So can be access from anywhere.

· Using new technologies and tools to make it efficient.

Future Work

We are building conference application in such a way that it can be extended for modules other than meetings that are required in the conference. For example along with meeting appointment we can extend it to perform meetings via video conferencing.

Tools and Technologies

The tools and technologies which will be using are

· Android Platform.

· J2EE based server

· MySQL server

· My SQL workbench

· Eclipse for Android

· Eclipse (J2EE enabled) for java server

· Tomcat server apache-tomcat-7.0.30 to run server

Contents My Conference Android Application 1 Software Reengineering Project Document 1 Course Name 1 Project Proposal ………………………………………………………………..……………………………………………………2-4 1. Project Outline (Week 1)………………………………..……………………………………………………………………………………7 2. Software Reengineering Project..……………………………………………………………………………………………………8-10 2.2.1. User Registration 12 2.2.1.1. Description: 12 2.2.1.2 Requirement: 12 2.2.1.3 Preconditions 13 2.2.2 User Login 13 2.2.2.1 Description: 13 2.2.2.2 Requirement: 13 2.2.2.3 Preconditions 13 2.2.3 Home Page 13 2.2.3.1 Description: 13 2.2.3.2 Requirement: 14 2.2.3.3 Preconditions 14 2.2.4 Attendies list 14 2.2.4.1 Description: 14 2.2.4.2 Requirement: 14 2.2.4.3 Preconditions 15 2.2.5 Book Meetings 15 2.2.5.1 Description: 15 2.2.5.3 Preconditions 15 2.2.6 Feedback Form 16 2.2.6.1 Description: 16 2.2.6.2 Preconditions 16 3. API Evolution (Week 2 ………………..…………………………………………………………………………………………………….16 4. API Efficiency, Reliability, and Maintainability (Week 3)………………………………………………………………………………17 5. Configuration and Change Management (Week 4)………………………………………………………………………………………18 6. Software Construction Tools and Techniques (Week 5)………………………………………………………………………………19

1. Project Outline:

Application Name: My Conference Application

Languages and Technologies: Android platform, java, MySQL

My Conference application is used by different seminars and conferences to assist users to book meetings with each other. The attendees in the conference need to be registered in the application. These users can login and see other registered users in the conference. They can access name, company and details of other users. These users can book meeting with other attendees. The other attendee will see who has booked meeting with him. Meetings can be booked with meetings names, meeting details and time. The application interacts with java server (J2EE project) to receive request from application. Requests are processed in MySQL database and response is sent back to application.

The application receives user requests and send data to web based java server. The java server process requests by saving and checking data in the MySQL database. After processing requests response or required data is sent back to application which is viewed by attendees.

2. Software Reengineering:

Java Mail and servlet API are used in this project. Java Mail API is used to send email password to registered users. Servlet API is used for connection between android application and java server. Tomcat server is used to run java server.

2.1. API used in the application:

The JavaMail API provides a platform-independent and protocol-independent framework to build mail and messaging applications. The JavaMail API is available as an optional package for use with the Java SE platform and is also included in the Java EE platform.

Application screenshots are as followed:

C:\Users\USI\Desktop\Screenshot_2014-05-27-03-36-16.png

C:\Users\USI\Desktop\Screenshot_2014-05-27-03-36-36.png

C:\Users\USI\Desktop\Screenshot_2014-05-27-03-36-46.png

The general architecture of the program is shown as followed:

2.2. Details of the program flow:

2.2.1. User Registration

2.2.1.1. Description:

Attendee first needs to be registered on the application before booking of the meeting. Imei check enabled to register the user only one time. We can register only one user on one mobile.

2.2.1.2 Requirement:

Requestor

Application response

User clicks on the mobile app icon

Application displays the page that shows login and register

User clicks register button

Application navigate to registration page

User enters information required

Application enters data into fields.

User clicks register button

Application validate entered information and check imei. If imei exists or data is not validated, application returns error.To check imei data mobile imei is sent to serve which checks entry in MySql database If data is validated Application sends password to email entered and shows success message “You have been registered. Please check your email to get password.”

2.2.1.3 Preconditions

User should not registered previously with same imei (device).

Network should be available and Mobile should be connected with network

User registration should be completed and approved.

2.2.2 User Login

2.2.2.1 Description:

After registration, user can login application to access its functionalities.

2.2.2.2 Requirement:

Requestor

Application response

User clicks on the mobile app icon

Application displays the page that shows login and register

User clicks login button

Application navigate to login page

User enters login and passowrd

Application enters data into fields.

User clicks login button

Application validate entered username and password by sending data to java server. Java server checks entries in MySql database If data is not validated, application returns error. If data is validated Application navigates to homepage.

2.2.2.3 Preconditions

Network should be available and Mobile should be connected with network

User login should be approved.

2.2.3 Home Page

2.2.3.1 Description:

After registration, user can login application to access its functionalities and shows homepage.

2.2.3.2 Requirement:

Requestor

Application response

User clicks on the mobile app icon

Application displays the page that shows login and register

User clicks login button

Application navigate to login page

User enters login and passowrd

Application enters data into fields.

User clicks login button

Application validate entered username and password by sending data to java server. Java server checks entries in MySql database If data is not validated, application returns error. If data is validated Application navigates to homepage which shows About fragment which shows outline of the project.

User enters fragment button

Application shows four options to Select:

1. Attendies List

2. Meeting Scheduled

3. Feedback Form

4. About

2.2.3.3 Preconditions

Network should be available and Mobile should be connected with network

User login should be approved.

2.2.4 Attendies list

2.2.4.1 Description:

User can see all attendees in the conference and see their details. They can easily select one person to whom they want to do meeting.

2.2.4.2 Requirement:

Requestor

Application response

User clicks login button

Application validate entered username and password by sending data to java server. Java server checks entries in MySql database If data is not validated, application returns error. If data is validated Application navigates to homepage which shows About fragment which shows outline of the project.

User enters fragment button

Application shows four options to Select:

1. Attendies List

2. Meeting Scheduled

3. Feedback Form

4. About

User enter Attendies List option

Application interacts with server. Server retrieves all registered users from database and send to application. Application shows attendees names, company and details in listview.

2.2.4.3 Preconditions

Network should be available and Mobile should be connected with network

User login should be approved.

2.2.5 Book Meetings

2.2.5.1 Description:

User can view all meetings schedules and information in the conference and see their details. Requirement:

Requestor

Application response

User clicks login button

Application validate entered username and password by sending data to java server. Java server checks entries in MySql database If data is not validated, application returns error. If data is validated Application navigates to homepage which shows About fragment which shows outline of the project.

User enters fragment button

Application shows four options to Select:

5. Attendies List

6. Meeting Scheduled

7. Feedback Form

8. About

User enter Meeting Scheduled option

Application interacts with server. Server retrieves all users who have booked meetings from database and send to application. Application shows name (to whom meeting with) and dateTime of the meeting

2.2.5.3 Preconditions

Network should be available and Mobile should be connected with network

User login should be approved.

2.2.6 Feedback Form

2.2.6.1 Description:

User can send feedback about the conference and application functionalities.

Requestor

Application response

User clicks login button

Application validate entered username and password by sending data to java server. Java server checks entries in MySql database If data is not validated, application returns error. If data is validated Application navigates to homepage which shows About fragment which shows outline of the project.

User enters fragment button

Application shows four options to Select:

1. Attendies List

2. Meeting Scheduled

3. Feedback Form

4. About

User enter Feedback Form option

Application shows feedback entry page.

User answers question on feedback page

Application interacts with java server and server stores answer to database.

2.2.6.2 Preconditions

Network should be available and Mobile should be connected with network

User login should be approved.

3. API Evaluation (Week 2)

4. API Efficiency, Reliability, and Maintainability (Week 3)

5. Configuration and change Management (Week 4)

6. Software Construction Tools and Techniques (Week 5)