Bibliotheca - Neslihan Kalayci: Difference between revisions
No edit summary (change visibility) |
No edit summary (change visibility) |
||
| Line 20: | Line 20: | ||
==== '''Stages''' ==== |
==== '''Stages''' ==== |
||
'''Week 1-5''' |
===== '''Week 1-5''' ===== |
||
- Determining Project Scope and Requirements |
- Determining Project Scope and Requirements |
||
| Line 37: | Line 37: | ||
- Working with user interface elements; Textbox Usage, Button Click, Layout, Frame Layout, Relative Layout, Toolbar, Side view , Recycler View etc. |
- Working with user interface elements; Textbox Usage, Button Click, Layout, Frame Layout, Relative Layout, Toolbar, Side view , Recycler View etc. |
||
'''Week 6''' |
===== '''Week 6''' ===== |
||
- User Interface design |
- User Interface design |
||
| Line 54: | Line 54: | ||
- Adding new book also have two possible outcome; failed and succeed. If a problem occurred, the system wants to readjustment for book's info. Otherwise, pop-up message will appear which says that '' 'Saved Successfully!' ''. |
- Adding new book also have two possible outcome; failed and succeed. If a problem occurred, the system wants to readjustment for book's info. Otherwise, pop-up message will appear which says that '' 'Saved Successfully!' ''. |
||
'''Week 7''' |
===== '''Week 7''' ===== |
||
'''Week 8''' |
===== '''Week 8''' ===== |
||
== Project Costs/Budget == |
== Project Costs/Budget == |
||
Revision as of 02:37, 10 October 2015
Introduction
Creating native Android app in C#.
About Bibliotheca
Bibliotheca is a mobile application that enable users to keep their own collection of books. It can be also evaluated as a book journal. By using this application, users can have a mobile library that keep tracks of their reading habits.
Objectives of Bibliotheca
The objectives of Bibliotheca to give users a platform that creates their own virtual library. Bibliotheca will work on Android mobile operating system. User can create their own profile and add/delete/update books on the system. The application consists of four different pages to meet the different demands; 'Books to Read'(like a wish list), 'Reading Now', 'Have Read' and 'Favorites'. In this virtual library system, each book has their own book cover, brief description etc. Each page will have different attributes to keep book's data with regarding user's preferences.
Requirements
Xamarin Studio
Approach
Project Strategy
The Project Schedule
Based on weekly stages
Stages
Week 1-5
- Determining Project Scope and Requirements
- Xamarin Studio configuration
- Xamarin user account validating
- Investigate Xamarin Android Guides [1]
- Understanding of Application Fundamentals
- Becoming familiar with User Interface & Elements
- Working with user interface elements; Textbox Usage, Button Click, Layout, Frame Layout, Relative Layout, Toolbar, Side view , Recycler View etc.
Week 6
- User Interface design
- Outlining pages and subpages in the mobile application
- Determining the user interface elements to fulfill the demand
- Starting with 'Have Read' page design & Determining Page Features;
This page will get information about book from user by asking the book title, author name, book cover, and brief description of book. After saving the new book, books can be listed on the grid view or list view format. Books also can be rated by user in the adding new book page.
- While choosing book cover page, user will have two options which are 'Select from gallery' or 'Take a new picture' .
- Adding new book also have two possible outcome; failed and succeed. If a problem occurred, the system wants to readjustment for book's info. Otherwise, pop-up message will appear which says that 'Saved Successfully!' .
