cs442 group 1 project - rishabhpshah.com · cs442 –group 1 project rishabh shah shruti gupta yani...

CS442 –Group 1 Project

Rishabh Shah Shruti Gupta Yani Mihaylov Richard Agama

11/14/2016

CS442 – Mobile Application Development IIT BOOKSTORE

Fall2016 1 Project- Group1 NOTE: - Points marked blue are the one which are modified after the phase1

Version Date Description

1.0 10/23/2016

● Designed Database Dictionary ● Added idea of functionality of email integration

and notifications ● Added and modified idea of search by

department, modified wait-listing functionality. ● Added more XML screens.

1.1 10/30/2016

● Individual work assignment for each of the project team

members.

● Design Database structure.

● Implemented signup and login functionality using local

database which is in project.zip

● Implementing Navigation drawer in project using activity so

that there are very less app conflict.

● Studying various backend server to implement in out

project one which we have fully gone through is kinvey

backend server.

● Implemented book due view functionality using fragment

class which is in libraraymanagement.zip and fully running

without no crash. It shows user what are its past due and

the due which are very near there is a check mark on it.

1.2 11/06/2016

● Added validations to previously designed xml’s.

● Made UI more user friendly.

● Made UI using background images of IIT so that it feels like

library application of Illinois tech.

● Had Talked to the library member and known the rules and

regulations of ILLINOIS TECH LIBRARY.

● Implemented functionality of adding new book to the

library by admin.

● Implemented functionality of viewing the total number of

books in the library.

● Designed Navigation drawer using Fragment Activity.

● Trying to implement notification activity.

● Designed various xml’s and implemented.

● Updated the individual work assignment for project team

members.

● Added Test Cases.

1.3 11/27/2016 ● Changed look and feel of UI ● Started Implemented email functionality. ● Implemented search book by name functionality.



● Implemented search book by ISBN functionality. ● Implemented search book by author functionality. ● Implemented request book functionality. ● Added new XML’s ● Changed some database structure. ● Started implementing shared preference for managing

session.



Table of Contents

Objective

Members

Features

Mandatory Features

Additional Features

Use Case

UI Design

UI Screens

UI Transition Flow

UI Sample Screens

Work Distribution

Database Structure

UserData

PartyData

PartyInviteeList

UserLocationData

Test Cases



Objective

IIT Bookstore is an android app by which a user (Students and faculty members) can access

information about the books they issued from the Paul galvin library. User can know about its pass

due and future due about all the books it issued from the library. User can search for the books and

know which books are available and which are not if some books are not available so user can

register itself for the waitlist and when the books became available it will be assigned to the user

who first registered for the waitlist.

Members ● Rishabh Shah(Team Leader)

● Shruti Gupta

● Yani Mihaylov

● Richard Agama

Features

The below list includes the mandatory features that will be implemented. Additionally, we

also list some other features

● There are two users in this system: -

1. Student or faculty member

2. Library Administration

2.1 USER (STUDENT OR FACULTY MEMBER):

● User Sign-up and Login: User must signup first using the hawk Id and its

personal information. Then user will be able to sign in using hawk Id and

password. ● View books list, book description: User can see all the list of books which

are available in library. User can view list of books from A-Z. Book

description detail page. ● Search Books: User can also search for the book and if user doesn’t know the

name of book then user can also search the book by name of its author. Other

searching options include by department or class, ISBN.



● Check Book Status and Request book: User can check whether the book to

borrow is available or not in the library and make a request for it. ● User can issue book from the library it will be reflected in his account. ● Waitlist: If user wants to issue some book and it’s not available at a time, then

he/she can register himself in waitlist for the book. ● Re-issue: User can also reissue the book from the app only when there are no

other users who want the same book then user can reissue the book, otherwise

waitlist. ● E-mail notifications: User will get email notifications on every action that

has been performed or issues that require attention. Ex: User will get mail before the 3days due of the book.

● View past, current and future upcoming dues: An indicator will categorise

the books borrowed previously as already due, upcoming due date, already

returned or status ok. ● Review User Profile: It will display user details and the books borrowed,

returned with future due and account status.

2.2 Library Admin: -

● Admin Login: Admin of library will sign in into the system.

● Admin Signup: We have removed the admin signup functionality as we

find it vague for every admin to login and request of every admin signup

goes to admin who is sign in. So, we removed that functionality. ● View/Search Books List: Admin can see the list of the books which are in the

library. ● Check Book Availability status: Admin can view the status of the books

whether its available or it is not available in the library. ● Adding a new book: Admin can add new books. ● Removing book: Admin can remove existing books. ● Admin add the books issued by the user. So basically, admin makes the entry

of the book issued by the user. ● Check status and assign book: Admin can view waitlist of each book and

will assign the book to the first person in waitlist just like issuing. ● Review Dues: Admin can view the list of books which are due this week i.e.

which books will be coming back this week. ● Admin can also view which books are due today and in future. ● Highlight Defaulters: Admin can remove the user which is not punctual in

submitting the books and can suspend him/her from using iit library resources.

Email notifications: At each stage wherever required the user will be notified with email

notifications for the status availability for requested books and other dues related information.

Additional Features ● Bar-code scanning functionality ● Statistics for whole day library trading.



UI Design Here we define all the user screens for the app.

UI Screens

I. Splash Screen: When we run the app firstly logo of iit will be popped up using animation we

have created splash activity.



II. Signup Screen: This screen will collect basic user information, Name, CWID, hawk id and also

lets user to setup new password and successfully register the new users.



III. Login Screen: This screen will collect basic user information, Name, Address, E-mail id and

also lets user to setup new password and successfully register the new users.



IV. Dashboard Screen Admin: This screen will display all the major activities like add book ,

issue book, view total books and Admin profile. When admin wants to issue the book to the

student it will click on the issue book and will enter the details of the user and will issue the

book.



V. Add Book: This screen will display the details which admin will add and finally book will be

added in the database so that when user logins they can view the book and search for it.



VI. View Book Screen: This screen lets the admin view the name and author name of the books

which the admin has added successfully.



VII. Issue book Screen: This screen lets the user to view the list of the ‘starred’ party locations.



VIII. Book list view user: -



IX. Book description view user: -

X. User and Admin profile view screen : -



XI. Search Book Screen: -



XII. Search book screen updated: -



XIII. Searching by book name screen: -



XIV. Search Book name result screen: -



XV. Book list view admin A-Z: -



➔ After implementing these functionalities, we changed the look and feel of the

Application which is as follows: -

➔ Home Screen: -



➔

➔ Search Book look and feel



➔ Login Page for admin and user: -



➔ Registration page for user: -



➔ Home page for Admin: -



Book Detail View: -



Admin View Waitlist Functionality: -



UI Transition Flow Here we explain the UI transition flow of the app.

I. User will be asked to provide the credentials for authentication using the Login screen.

II. If it’s a new user, the user can click on the Signup button to navigate to the Signup screen.

III. In the Signup screen, the user will provide all the necessary information and create an

account for accessing the app.

IV. Once the user is successfully logged in to the app, the Dashboard screen will be displayed

listing all the major functionalities like View books, Get books , user profile.

V. When user wants some book from the library he/she will go to view book section look for

the books which are available and click on the request book so notification will be send to

admin to issue the book.

VI. User can also see it’s past dues by clicking on the view dues button.

VII. User can see its profile and also edit its profile by changing username and password.

VIII. Admin is ask to provide the credentials for authentication using the Login screen.

IX. When admin is successfully logged in , it will be taken to Dashboard screen.

X. In Dashboard Admin can add books , issue books and also view books.

XI. When any new book comes to library admin will add the book by clicking on add book.

XII. When admin wants to issue the book to the user then it will click on the issue book section

and enter the A number of the student and issue the book.

XIII. Admin can also view the book added previously.

Work Distribution

Team

Member

Responsibilities Further Details

Rishabh

Shah

Admin UI and functionality

implementation

Admin Login, Check status and

assign book requests, Book Search

Shruti

Gupta

Admin UI and functionality

implementation

Book Description, Book search,

Check status and assign book

requests

Yani User functionality Signup, login, view book

Richard User functionality Issue book, checkout, dues

7.0 Work distribution until now: -



TEAM MEMBER RESPONSIBLITIES

SHAH RISHABH ● Gave idea for various

projects. ● Chicago Tourist

application idea and

project proposal. ● Shared views on

designing screens for

Chicago guide. ● Prepared xml screens

for IIT BOOKSTORE. ● Prepared version 1.0

proposal for IIT

BOOKSTORE. ● Prepared phase1 report

for IIT bookstore. ● Prepared draft for

database structure. ● Prepare data dictionary

for IIT BOOKSTORE. ● Design screen for book

view. ● Learning and studying

various backend servers

to implement the most

efficient one. ● Implementing

functionality of login

and signup in the

original project. ● Implementing Login

Functionality of admin

in the original project. ● Prepared Phase2-02

report. ● Implemented

Validations for Login

and signup. ● Implemented

functionality for add

data to the book and

upload image. ● Implemented

Validations for add

book. ● Prepared list view for

the admin panel



booklist. ● Prepared phase 3.0

report. ● Designed 3 xml for

search book by name

author and ISBN. ● Designed xml for view

book a-z and view

detail view. ● Implemented 3

functionality of search

book by name isbn and

author. ● Implemented

functionality of view

book from a-z with

image. ● Implemented

functionality of view

detail view of book. ● Implemented waitlist

functionality for the

admin side including

xml.

● Implemented issue book

functionality for the

admin side.

● Prepared report for

phase 4.0

● Merged all

functionalities.

● Managed shared

preferences for all data

SHRUTI GUPTA ● Prepared version1.0

proposal for IIT

bookstore. ● Prepared draft for

database structure. ● Shared views on screen

designing. ● Implemented xml files

for admin dashboard

and user dashboard. ● started implementing

list view for book view

user. ● Designed and prepared



test cases for phase 3.0

report. ● Started Implementing

assign book for admin

side. ● Prepared test cases for

phase 3.0 report. ● Tried implementing

search book

functionality. ● Design xml for issue

book, remove book and

view past due. Richard Agama ● Gave idea for various

projects like maze

game. ● Gave idea for

developing app IIT

BOOKSTORE. ● Prepared draft for IIT

bookstore. ● Shared views on screen

designing. ● Implemented user

profile view. Yani Mihaylov ● Gave idea for various

projects. ● Assisted in preparing

proposal for Chicago

guide app. ● Shared views on

designing screen for

Chicago guide app. ● Prepared draft for

database structure. ● Shared views on screen

designing. ● Implemented Signup

and login functionality. ● Creating backend web

server for the system. ● Implemented

validations for the

system. ● Testing the code which

are developed. ● Implemented



functionality for

fetching data from the

database and showing

the book list view to the

user. ● Merged the

functionality of search

book and view book in

the user side. ● Started Implemented

functionality of request

book in user side. ● Changed the look and

feel of app. ● Changed look and feel

xml of home page,

login , registration,

admin home. ● Implementing

functionality of user

view book due. ● Implemented

functionality for user

waitlist.

● Implemented

functionality for user

search by name author

and ISBN.

● Changed look and feel

of APP.

● Design new xml’s.

Test Cases Test Case Id : 1 Launch/User Activity

Input App Run instantiated

Expected Result Splash Activity runs and the main activity runs just after this activity.

Actual Result Splash Activity runs and the main activity runs just after this activity.



Test Status Successful.

Test Case Id : 2 Admin Login

Input Enter values and click on Register button

Expected Result On successful entry the user will be registered and values are stored in the database.

Actual Result On successful entry the user will be registered and values are stored in the database.

Test Status Successful. Testing for Sign-up registration. If the user enters a username or password then it validates the same from the database and throws exception message and passes if entered correctly in right format.

Test Case Id : 3 User Login

Input Click on the login button without the user being signed up before.

Expected Result Error message generated as user not registered.

Actual Result Error message generated as user not registered.

Test Status Successful. Tests for invalid user. If the user enters a username or password then it validates the same from the database and throws exception message and passes if entered correctly in right format and values.

Test Case Id : 4 User Registration

Input Click on the login button but with some changed user details that were not used for

Expected Result Error message pops up saying invalid user credentials.

Actual Result Error message pops up saying invalid user credentials.

Test Status Successful. Tests for invalid username and password. If the user enters a username or password then it validates the same from the database and throws exception message and passes if entered correctly in right format and values.

Test Case Id : 5 User View book

Input Try login in again with same already registered user

Expected Result Error message pops up saying user already existing.

Actual Result Error message pops up saying user already existing.

Test Status Successful. Tests for already existing user .

Test Case Id : 6 (Admin) Add Book

Input After login, click on add book button and in that enter the required fields for the book that needs to be added.

Expected Result Book added to the database and displayed.

Actual Result Book added to the database and displayed.

Test Status Successful. Tests for adding a new book to the database.



Test Case Id : 7 (Admin) View Books

Input Click on view book button

Expected Result the list will display all the books added to the database.

Actual Result the list will display all the books added to the database.

Test Status Successful. Tests whether the book added can be viewed here.

Test Case Id : 8 (Admin) Search/View Books

Input Click on view book button

Expected Result The list will display the results from after typed characters in the text box finds the match in the database.

Actual Result The list will display the results from after typed characters in the text box finds the match in the database.

Test Status Successful. Tests whether the typed characters in the text box returns required book results.

Test Case Id : 9 Navigation Drawer

Input When the user goes on to any other screen apart from the main screen and clicking on that button corresponds with the Navigation Drawer menu.

Expected Result It runs on all screens except main screen

Actual Result It runs on all screens except main screen

Test Status Successful. Tests whether the navigation drawer functionality works on any other screen except the main screen.

Test Case Id : 10 Email notifications

Input Check your email/inbox after registering for the first time in the system.

Expected Result Email is received by the user upon registeration.

Actual Result Email is received by the user upon registeration.

Test Status Successful. Tests email is sent or not just after user/admin registered into the system.

Test Case Id : 11 User search book by isbn, author and book name

Input Enter the text characters to search from the book name, author or isbn

Expected Result If the text matches with the database results it shows those lists.

Actual Result If the text matches with the database results it shows those lists.

Test Status Successful. Tests whether the output search result is as expected from the entered text or not.



Test Case Id : 12 User request book

Input Enter the book details required by the user and submit

Expected Result If the book is available to be assigned it will be notified and a request is generated into the database.

Actual Result If the book is available to be assigned it will be notified and a request is generated into the database.

Test Status Successful. Tests whether the book request is sent to the admin and is created in database or not.

Test Case Id : 13 Admin assign book

Input Enter the book details as requested by the user and submit

Expected Result If the book is available to be assigned it will be notified and will be assigned to the user and generated in the database.

Actual Result If the book is available to be assigned it will be notified and will be assigned to the user and generated in the database.

Test Status Successful. Tests whether the book as requested by the user has been assigned to the user or not based on the availability.

Test Case Id : 14 Admin profile

Input Click on Admin Profile

Expected Result Admin details will be displayed

Actual Result Admin details will be displayed

Test Status Successful. Tests admin profile

Test Case Id : 15 Remove Book

Input Click on remove button for the specific book

Expected Result Book will be deleted from the database

Actual Result Book will be deleted from the database

Test Status Successful. Tests deletion of the book from database.

cs442 group 1 project - rishabhpshah.com · cs442 –group 1 project rishabh shah shruti gupta yani...

Documents