UNIVERSITI TEKNOLOGI MARA MALAYSIA

Android Application : News and Events Notifier for FSKM ( NETME )

NUR FARHANA BINTI SAAD

Thesis submitted in fulfilment of the requirements for Bachelor of Science (Hons.) Information Technology Faculty of Computer and Mathematical Sciences

April 2012

I

APPROVAL

News and Events Notifier (NETME) for Faculty of Computer and Mathematical Sciences (FSKM)

by

NUR FARHANA BINTI SAAD 2011481902

A thesis submitted to FACULTY OF COMPUTER AND MATHEMATICAL SCIENCES UNIVERSITI TEKNOLOGI MARA

In fulfilment of requirement for the BACHELOR OF SCIENCE (Hons.) INFORMATION TECHNOLOGY

Approved by the examining committee: ………………………………………… EN AHMAD ZAMBRI SHAHUDDIN Project Supervisor

July 2012

II

PENGISTIHARAN

Saya dengan ini mengaku bahawa kajian ini bersama-sama dengan semua kandungannya tidak lain daripada yang kerja saya sendiri, kecuali untuk beberapa maklumat yang diambil daripada sumber-sumber lain yang telah dikredit atas penulisnya sendiri.

…………………………………..

NUR FARHANA BINTI SAAD 2011481902

III

PENGHARGAAN

Alhamdullilah, saya benar-benar bersyukur kepada Allah SWT kerana berkat saya dengan pengetahuan dan masa untuk melengkapkan dengan jayanya tahun akhir projek tesis saya dalam masa yang dinyatakan. Saya juga ingin menyatakan sekalung penghargaan kepada suami Encik Khairul Bin Ismail atas sokongan dan kesabaran bagi menyiapkan projek tesis saya ini. Disamping itu ribuan terima kasih buat rakan-rakan sekerja dan sahabat handai yang sudi memberikan idea bernas ke atas projek, dari awal sehingga tamat tesis ini. Akhir sekali, terima kasih buat kesemua yang membantu saya secara terus menerus dalam penyiapan projek ini. Hanya Allah S.W.T sahaja yang boleh membalas jasa kalian.

Terima kasih. Semoga diberkahi Allah SWT.

IV

ISI KANDUNGAN

KANDUNGAN KELULUSAN PENGISTIHARAN PENGAKUAN TABLE OF CONTENTS LIST OF FIGURES LIST OF TABLE LIST OF ABBREVIATIONS ABSTRACT CHAPTER 1: RESEARCH OVERVIEW 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 Research Background Problem Statement Research Aim Research Requirements Research Objectives Research Scope Research Significance Research Design

PAGE ii iii iv v vii ix x xi 1 1 2 3 3 4 4 4 5 7 7 8 15 15 17

CHAPTER 2: LITERATURE REVIEW 2.0 2.1 2.2 Introduction Review of the current existing Android News applications Approaches done by other researcher’s projects 2.2.1 2.2.2 Navigation on Mobile News An approach to find out user’s interests based on mobile personalized news service system

V

0 5.3 3.2.2 2.3.0 4.4 3.0 3.3 3.3 Waterfall Model Prototype Rapid Application Development 23 23 25 27 31 31 32 33 33 34 35 38 40 46 46 50 50 50 56 65 65 65 66 66 67 69 CHAPTER 3: METHODOLOGY 3.2.2.2 Introduction Phase 1: Requirements Planning Phase 2: User Design 3.2 5.2.2.3.1 4.2.3 Development techniques 2.3.5 3.1 2.4 Determine the user needs Use Case Diagram Activity Diagram System Requirements Interface Design Phase 3: Construction Phase 4: Implementation / Cutover CHAPTER 4: RESULTS AND FINDINGS 4.3 Efficient Summarization-Aware Search for Online News Articles 18 2.1 5.3 Introduction Conclusion Limitation Recommendation REFERENCES APPENDIX VI .1 3.2 3.1 3.2 Introduction Survey Result Test Result CHAPTER 5: CONCLUSION AND RECOMMENDATION 5.2.

1 2.3 3.List of figures No 2.8 3.4 2. 2005) Online Summarization Clustering Method (Dakka & Gravano.5 2.12 3.10 2. & Chan.2 2. Chan.11 2. 2007) Example of the Waterfall Model (QSQA.9 3. 2007) The Rapid Application Development Model for this project Screenshot of the online survey at Google Doc NETME Use Case Diagram NETME Browsing Events Activity Diagram NETME View Tagged Events Activity Diagram Screenshot of the Eclipse Indigo NETME Main Menu Interface Design NETME Events Browsing Interface Design NETME Events Details Interface Design NETME Tagged Events Interface Design NETME Tagged Event Details Interface Design Page 8 9 10 11 12 14 16 24 25 28 31 33 34 36 37 39 41 42 43 45 45 VII .6 3.7 3. 2009) Experimental Prototype Model (Mahil & June) RAD Model on Iterative Basis (Reece.2 3.10 3.4 3.3 2.1 3.7 2.5 3.8 2.11 Figure Screenshot of the Pulse News App Screenshot of CNN Android Screenshot of the CNET News App Screenshot of MSNBC Android Screenshot of Yahoo! News Android BHN & CLN Structure (Su.

11 56 57 58 59 60 61 62 63 64 4.4.10 4.6 4.7 4.12 4.8 4.9 4.2 4. Part 1 of the result conducted on Google Survey about NETME wanted functions.13 VIII . Main Menu of the NETME application on 4.4 53 4.5 4. Part 2 of the result conducted on Google Survey about NETME wanted functions.3 Android Device Events browsing page (first page) Tag button located at the bottom of the browsing page Events browsing page (middle page) Events details page Events tagging confirmation window Successfully tagged the event Menu for the tracking the tagged events Details menu for the tagged events 51 52 4.2 Spreadsheet of the Google Survey about NETME wanted functions.0.

4 Table Research Design and relevant information Review of the current existing Android News applications Approaches done by other researcher’s projects Development techniques and models Summarized Details and Descriptions of the RAD Model for NETME Project Survey questions and answers posted on Google Doc Page 5 13 20 29 47 54 IX .9 2.6 2.Tables No 1.13 3.1 2.12 4.

LIST OF ABBREVIATIONS FSKM HTML 5 ICS NETME OS Faculty of Computer and Mathematic Science Hyper Text Markup Languages 5 Ice Cream Sandwich News and Events Tag Mobile Edition Operating System X .

majikan mahupun pihak bertanggungjawab itu sendiri. kaedah-kaedah keselamatan juga akan dibincangkan dalam kajian ini. Dalam kajian ini tanggungjawab seseorang majiikan akan ditekankan dalam menyediakan ruang pejabat yang kondusif untuk para pekerja secara langsung mengekalkan keselamatan buat mereka. Ini akan membuatkan mereka tidak terdedah dengan kemalangan mahupun penyakit yang berkaitan dengan pekerjaan mereka . XI . Kepekaan pekerja dalam isu keselamatan di tempat kerja akan di beri perhatian secara menyeluruh oleh semua pihak tidak kira pekerja. Dengan menyediakan kemudahan yang lengkap dan teratur bagi mengurangkan risiko pekerja yang bekerja di ruang pejabat. isu yang akan dibincangkan dalam kajian ini adalah kepentingan dalam menjaga keselamatan di tempat kerja.ABSTRAK Dengan adanya kesedaran tentang keselamatan di tempat kerja terutamanya di ruangan pejabat membuktikan bahawa seseorang pekerja itu peka dengan hak mereka sebagai pekerja. lebih-lebih lagi pada mereka yang bekerja di ruangan pejabat. Selain dari itu. Kepentingan dan kesedaran keselamatan dalam ruangan pejabat juga akan dikupas dalam kajian ini. Keselamatan di dalam ruang pejabat juga akan Tambahan lagi.

Tambahan lagi. Tambahan lagi ruangan pejabat juga bukanlah satu ruangan yang menyimpan bahan radiasi. Beberapa punca utama berlakunya kemalangan di tempat kerja adalah orang terjatuh. hal ini menunjukan punca utama sesuatu kemalangan di tepmat kera yang menimbulkan kecederaan aalah jarang sekali dan tidak berkala. Hal ini kerana ruang pejabat juga dilihat sebagai satu kawasan atau ruang yang tidak mempunyai risiko bagi pekerja yang membuatkan seseorang cedera mahupun sakit. 2006). ramai yang merasakan bekerja di ruang pejabat adalah tempat yang paling selamat. cecair kimia. terhempap oleh benda yang terjatuh serta terkena benda-benda pegun atau tidak bergerak seperti yang dilaporkan oleh Pertubuhan Keselamatan Sosial Malaysia (PERKESO. 1 . Berdasarkan pandangan mata kasar ruangan pejabat merupakan ruangan yang kurang risiko dari segi keselematannya dan adakah benar jika ruang pejabat tidak perlu diberi penekanan dari segi keselamatannya? Dengan kajian tentang isu keselamatan di tempat kerja ini akan cuba difokuskan pada sekitar ruang pejabat dengan membuat perbandingan antara penemuan literature dengan kajian literature lain.BAB 1 PENDAHULUAN 1.0 PENGENALAN Keselamatan di tempat kerja dalam sesebuah organisasi adalah penting bagi semua pekerja untuk menjalani pekerjaan yang selesa dan selamat. sampel-sampel bacteria ataupun serangga dan sebagainya yang mampu mengancam keselamatan pekerja. Selain itu ruangan pejabat juga tidak dianggap boleh mengancam keselamatan pekerja dimana ruangan pejabat merupakan antara ruangan yang paling selesa dan persekitarannta dikawal oleh penghawa dingin. Seperti yang dilaporkan.

iii) Keselamatan yang boleh dikategorikan kepada beberapa jenis untuk mengawal keselematan di keselamatan iaitu dari aspek kimia.2 OBJEKTIF KAJIAN 1. beberapa masalah berkaitan dengan keselamatan bekerja ruang pejabat boleh dibangkitkan.1 PENYATAAN MASALAH Menurut senario hari ini.1. ii) Tidak maklum tentang kepentingan dan keperluan undang-undang yang tertulis di bawah Akta Keselamatan dan Kesihatan 1994 yang menekankan akta tentang kepentingan menyediakan polisi keselamatan untuk pekerja meskipun yang bekerja di ruangan pejabat. biologi. Perkara utama yang akan dibangkitkan juga adalah peranan majikan tentang tanggungjawab mereka ruang pejabat. i) Tidak mengambil endah tentang keselamatan pekerja yang bertugas di ruangan pejabat.1 OBJEKTIF UMUM Secara umumnya. 2 . 1.1. fizikal dan ernogomik. 2) Menganalisia tentang kepentingan polisi keselamatan dan keperluan mengetahui akta dan undang-undang keselamatan di tempat kerja. 1. objektif kajian ini adalah untuk mengkaji perihal keselamatan di tempat kerja yang menekankan keselamatan diruang pejabat.1..2 OBJEKTIF KHUSUS Bagi objektif khusus untuk kajian ini ianya akan ditumpukan kepada beberapa objektif dibawah : 1) Mengenalpasti tentang penekanan keselamatan pekerja di tempat kerja bahagian ruangan pejabat.

Tambahan lagi. biologi. keselamatan di ruangan pejabat.5 STRUKTUR KAJIAN Kajian yang dijalankan akan menumpukan kepada dua permasalahan keselamatan di tempat kerja dalam ruangan pejabat serta bertindak untuk mencapai objektif yang di nyatakan. 1. Diharapkan kajian ini juga dapat memenuhi keperluan pekerja dalam mengetahui tentang kepentingan selain risiko berbangkit keselamatan di tempat kerja dalam ruangan pejabat.3 KEPENTINGAN KAJIAN Kajian ini amat penting kerana ianya dapat memberi kesedaran kepada pekerja yang bekerja di ruangan pejabat. biologi dan ernogomik. seramai 10 orang responden akan dipilih sebagai sampel penyelidikan ini. fizikal dan ernogomik juga akan dikupas dengan lebih lanjut. 3 . 1.4 SKOP KAJIAN Perbincangan tentang kesedaran pekerja tentang keselamatan mereka dan undangundang yang berkaitan dengan keselamatan di tempat kerja lebih-lebih lagi di ruangan pejabat yang kurang risiko kecedaran. Dalam kajian ini akan merangkumi perbandingan literatur yang menfokuskan kepada tanggungjawab majikan dalam menentukan keselamatan di tempat kerja. Selain itu ia juga dapat mengenalpasti tentang penekanan pihak bertanggungjawab dalam membantu menguruskan keselamatan di tempat kerja dalam ruangan pejabat.3) Mengkaji kategori-kategori keselamatan ditempat kerja dari aspek fizikal. beberapa ciri-ciri keselamatan dari segi kimia. 1. Bagi tujuan ini fokus kajian akan tertumpu kepada beberapa orang responden yang bekerja di dalam ruangan pejabat. kimia. Tambahan lagi. pentingnya keselamatan di tempat kerja. kajian ini juga dapat memberi satu analisa tentang pentingnya untuk seseorang pekerja mengetahui tentang akta dan undangundang yang berkaitan dengan keselamatan pekerja di dalam ruangan pejabat. kaedah keselamatan di ruangan pejabat dan kepentingan dan kesedaran keselamatan di ruangan pejabat.Oleh yang demikian.

hamper kesemua dari pekerja akan menghabiskan masa di tempat kerja dari dalam rumah. Selain itu.BAB 2 LITERATUR 2. 2010). malahan dalam ruangan pejabat juga menjadi punca utama sesuatu kemalangan berlaku. Majikan juga perlu lebih peka dalam aspek keselamatan pekerja dengan menyediakan fasiliti dan ruang yang kondusif buat mereka. Di mana pekerja seringkali terdedah pada risiko bahaya. 4 .0 PENGENALAN Sebagai seorang pekerja. Kemalangan jiwa yang berlaku bukan sahaja di luar tempat kerja. Hal ini menunjukkan kebanyakkan lagi syarikat tidak mengambil endah perihal keselamatan pekerja di tempat kerja. Sekitar Jun 2010 lebih dari 10 buah syarikat telah diheret ke mahkamah atas sabitan tidak memiliki polis keselamatan yang ditetapkan pada pekerja (Utusan Malaysia. Dalam kajian literature ini beberapa kaedah. factor dan kepentingan keselamatan akan dibincangkan. Mengambil tindakan sewajarnya terhadap isu keselamatan di tempat kerja dalam ruangan pejabat. Kesimpulannya. Tempat kerja yang kurang selamat akan memudaratkan pekerja untuk bersosial dan kewangan mereka. Hampir separuh dari tempat kerja di negara Malaysia ini tidak menyediakan polisi keselamatan disamping tidak menwujudkan Jawatankuasa Keselamatan dan Kesihatan. keselamatan dan kesihatan di tempat kerja merupakan satu perkara penting dan berkait rapat dengan kesihatan yang boleh mendatangkan risiko pada pekerja. pekerja juga wajib mengambil tahu langkah-langkah dalam menjaga keselamatan mereka di tempat kerja dan mempunyai kesedaran yang tinggi dalam memahami isu keselamatan tempat kerja.

RAD model will consist mainly of four (4) steps which best described through the figure below. Kewajiban dalam menjaga keselamatan di tempat kerja bukan bergantung pada majikan sahaja. This chapter also confers on the methods necessary to execute this project. thus this chapter is being organized into several segment such as the flowchart for Rapid Application Development (RAD) model. details of the RAD model. the system requirement and the interface design for this system. RAD has been chosen as the development method for this project. The timeframe for this project can be viewed through the Gantt chart available at the Appendix section (Appendix A). 5 . several plans and scheduling have been made to ensure the progress of this project. kerajaan mahupun badan berkanun akta ini digunakan dalam menjadikan sesuatu persekitaran tempat kerja itu kurang risikonya. di mana akta ini dibentuk untuk memberi kaedah dan cara-cara kepada majikan dan pekerja mengenai tanggungjawab masing-masing seterusnya menwujudkan satu persekitaran tempat kerja yang sihat dan selamat (Hapriza. 1999). Setiap majikan tidak kira di sector swasta.1 KESELAMATAN DI TEMPAT KERJA Jabatan Keselamatan dan Kesihatan telah menggubal satu akta pada tahun 1994 (AKKP 1994).2. Within this one short year. malahan pekerja juga perlu ada kesedaran yang tinggi dalam diri pekerja untuk memastikan kemalangan sifar dalam kalangan pekerja. BAB 3 METODOLOGI 3. starting from September 2011 until July 2012. As mentioned earlier.0 Introduction This project is being carried out within a year.

0 Construction Figure 3.1.1: The Rapid Application Development Model for this project 6 .0 Requirements planning 4.0 Cutover 2.0 User Design 3.

7 . Outputs that are obtained from conducting all of the steps are complete literature resources regarding the project. RAD model will consist of four stages which are requirement planning. articles and any other relevant information materials like the websites. understood on how to develop and handle the system. His argument stated that a software development module should be designed to ensure the developers build a system that the user really needs (Reece. books. user design. The references are consists of journals. methods to determine the system concept and capabilities are also conducted. system concept and capabilities are determined and the system requirement and restrictions are thoroughly verified. well established knowledge and information for developing the system. It is also important to integrate the knowledge learned from the research as a foundation for developing the system. Resources would include on the numbers of events and news that need to be synthesized. Later on. During this phase. several relevant references have been searched and reviewed and being used as main references. This consists of determining the scope and foundation of the system and also the identifying other form of restrictions which becomes the boundary of the system. Therefore. 2007). 3.1 Phase 1: Requirements Planning Determining the requirement to develop the system such as information gathering and knowledge basis needed to develop the project. Capabilities will determine on how can the system deliver the concept and how would it function at its maximum capacity. This phase reaches its final stage through the verification of the system restrictions.Rapid Application Development or RAD is a software development process which introduced by James Martin during the early 90’s. the phase continued with the finding of the initial system requirement. magazines. During this phase. construction and implementation.

The online document is a survey that has been conducted at Google Doc.3.2 Phase 2: User Design This phase determined the nature and scope of this project. To retrieve the feedback and response from the audience or users. Therefore there are three steps that have been conducted to determine the complete user design for this project.2.2 Screenshot of the online survey at Google Doc 8 . Several steps have been conducted to ensure the wholesome of the system. Figure 3. an online document have been created to be as a platform for the developer to communicate with the users. This survey has served as the main interaction with the users as to determine what kind of application that the users were expecting. 3.1 Determine the user needs The first steps that have been executed during this phase are determining what kind of application the users were expecting.

this use case diagram is miniature compare to the other contemporary systems.3. the system itself or time period could be the actor as well. They are needed to download the application first at Google Play to use the application. In other words the 9 . Each user then will install the application in their Android mobile device and launch the system when the installation is complete. locally or externally.3 NETME Use Case Diagram The figure above showed the general view of the case study diagram for the system. there are two actors which are users and system administrators. Figure 3. In some cases. Since mobile application only have small amount of functionality. they will not be able to view the event they tag at other Android devices. After installation users will be able to view the events on the application and tag as per needed. For the NETME scope. The system is behaving locally meaning that if the users tag or view the event in their phone.2. It shows the interaction between users and system’s functions. Users would consist of every user that uses the NETME system.2 Use Case Diagram Use case diagram describe the system from the user’s point of view.

the administrators are assigned to update the system and upload it into Google Play. The only difference that by not updating the system is their NETME will only have the events which they already download but not the newer ones that are added to the system. but they can retrieve the updates via other Android Devices that already have the updates.3 Activity Diagram NETME is a local application. The user will be informed via Google Play that a new update is available and they will need to update their application once again. One of the major activities is browsing for the events while the other is viewing the tagged events which they want to attend. Administrators will upload the updates through Google Play and users would require retrieve the updates whenever they have internet access. which is not directly interacting with the administrators of the system. If there is a new event available. The events are being listed by weeks per months. It’s a drawback for the system in order to enable all users to use the system without any restrictions. 10 . There also will be a case where new events are constantly update through the system. Each of the activities is inter-related to one another. as for that the users will need to constantly update their NETME via internet connection. The administrator is the person in the system community that will handle the system updates and patches. meaning that the users only need to update the events once every month. This will enable several users that did not have data line or internet connection to use the application.system is offline and only need to be online when the users need to update or download it at the first place. NETME Activity Diagram has two major activities which the application would handle. Some users may not be able to obtain the latest events via Google Play. 3. The administrators would only update new events or changes in the information for certain events as per needed.2.

At the main menu. The 11 . Through that option. users are able to view the events listed by the system by selecting the Browsing Events option that are listed as the first option at the main menu.4 above shows the NETME browsing events activity diagram for the system. each of events will list important information and particulars about the event. the system will display a simple main menu for the users to navigate.4 NETME Browsing Events Activity Diagram In figure 3. users are able to browse through the events listed by the application and view the events details by selecting the poster. When starting the application.Figure 3. In the event details.

information will include date. Users will be able to choose whether want to tag the event into the NETME Event’s Tag which functioned as to inform them any relevant changes about the event and when the event will begin. venue and the purpose of the event. Figure 3.5 NETME View Tagged Events Activity Diagram 12 .

Only this time the users will need to select the second option within the main menu. one is the computer itself and the other is the Android device. That option will lead the users to a list of events which the user already tagged in during their browsing on the previous activity. Software would be the tools required to develop this project.In figure 3. The tag function is very useful whenever there are new updates about the event and the users can simply use the tag options to view what the updates are. when starting the application the system will display a main menu for the users to navigate. Clicking on one of the events will lead the users into a new window that will display the tagged events details. 3. Likewise.06 GHz Windows 7 Ultimate 64-bit 120GB ( 1GB used for the project ) ii) OS iii) HD b) HTC One V i) OS ( Android Device ) : : 4. There are two types of hardware.4 System Requirements This section will discuss on the hardware and software specification. Powerpoint ) e) Online UML Design Tool Gliffy 13 .2. Users can simply instead view the events they wanted to partake in and check the details as a reminder.0. 1) Hardware a) PC Desktop i) CPU : : : Pentium Dual Core @ 3.3 ICS 8GB (1 MB used for the project) ii) SD 2) Software a) JDK for Android OS b) Eclipse with PhoneGap Plugin c) Adobe Dreamweaver d) Microsoft Office ( Word.5 previously shows the activity of a NETME user viewing the tagged events in the system. The difference between this activity than the browsing activity is that the users will not require to browse all of the events within the application library. Excel.

there are several software are being used to build the system. To engineer the JDK. Java Development Kit for Android OS.0. Figure 3. there is an application which is used as the main tool to program the 14 . The JDK will serve as the main tool for developing the NETME application. The main application would be the JDK. Most of the spaces were occupied by the system interface design and early built versions of the application. The android device has 8 gigabyte of space and only 1 MB is being used for the application.The hardware requirement is the fundamental requirement in order to build and run the application. The hard disk space allocated for this project was one gigabyte.3). The hardware requirement for the android device is being line out by a HTC smartphone called One V.6 Screenshot of the Eclipse Indigo For the software requirement. The smartphone is running on Ice Cream Sandwich version (4. The application is being built on a PC Desktop with Pentium Dual Core as the main processing unit.

two application tools are being used. Microsoft Excel is being used as the spreadsheet for collection information and survey from the users.6). Microsoft Office is the main suite application being used for documentation and presentation purpose.2. a plugin which enables Eclipse to handle HTML 5 codes and converts them into native language. The design changed after users requested that the system needs to be simpler and direct to its functions. This project also embeds HTML 5 codes onto the building of the application. Microsoft Powerpoint is being used as the main presentation tool for the Final Year Project presentation at UiTM Shah Alam. Second is the Adobe Dreamweaver which is to engineer the HTML 5 codes.application. The tool is called Eclipse (Figure 3. Microsoft Word is the main word processing software which is used as the platform to write documentations and this thesis. The screen orientation is locked on ‘portrait’. Eclipse is a powerful tool which enables Android Developers to develop Android App using native language. However. To handle the HTML 5 codes. This system would require internet access for updates. 3. 15 . The screen is locked that way to avoid complications on other version of Android devices.5 Interface Design The early design of NETME will consist of several menu selection that are made in order to enable users navigate through the application smoothly. meaning the screen would not rotate to the widescreen or ‘landscape’ view. NETME still can be used even without having any internet access. The version of Eclipse being used in this project is the Indigo Version. First is the PhoneGap.

Figure 3. From the design. That option will take the users to a page where the users can view their events and check any updates or announcements regarding the events they have tagged (Figure 3. The second option will direct the users to the ‘Tagged Events’. there are two options will be available for the users. The first option. The main menu will have two interactive buttons which will be the options that the users can choose to navigate while using the NETME application.7: NETME Main Menu Interface Design The interface design of NETME Main Menu is as shown in Figure 3.8) 16 .7). where the users able to view all the events which are listed by the application (Figure 3.6. namely ‘Event’ will direct the users towards the event selection.

which is located on another page.7 shows the View Events page. This page will enable the users to navigate and browse through the events. Pressing ‘No’ instead will lead the users back to the event page.8: NETME Events Browsing Interface Design Figure 3. the application will redirect the users onto a new page which is the Event’s Details. Below the poster is a button where the user can initiate to tag the events displayed on that page. The confirmation window will ask the user whether they really want to tag that event or not. By pressing ‘Yes’ the application will register the event into the ‘Tagged Events’. simply press the ’Back’ button on the top left to go to the previous event page. Pressing that button will direct the users towards a new sub window that asks for the user’s confirmation. for the Events Browsing function. Users can browse through the events by pressing the ‘Next’ button on the top left or if the users wants to view the previous events.Figure 3. The large square in the middle will show the event’s poster related to the event. 17 . By pressing that poster.

The confirmation window and asks for confirmation for the user whether they want to tag the event or not. At this page. The button will function the same way it did on the previous menu. Users will only able to view one event and its details.8) by pressing the return button. Users will not be able to navigate their way to another event from this page. time and other relevant information.9: NETME Events Details Interface Design Figure 3. located on top left. users also will be viewing a poster located at the center of the page but pressing it will not initiate any form of functions. Below the poster will show a list about the events information. 18 . users can return to the previous page (Figure 3. which lists several important information regarding of the application. The information will consists of the events venue. which is direct the users towards a new sub window that asks for the user’s confir mation. However.Figure 3.9 shows the View Events Details page. The information is text based hence clicking the particulars would not serve any function. At this page the poster only functioned as a display. Below of the events information is a button that will function to tag the events.

7. As of currently there are no limitations for the events listed at that page.Figure 3. However there is an idea to design the Tagged Events by limiting four events per page. which the users can interact with. The listed events are all buttons. This menu can be accessed through the main menu only. users will need to go to the next page the same way as the users did while browsing the events previously. This idea was not implemented due to 19 .11).10 is an interface design for the tagged events. In Figure 3. At this page users will be able to select several events that they have already tagged previously at the Events Browsing page. By pressing one of the buttons will direct the users onto a new page which display the events details (Figure 3. Users can return back to the main menu by pressing the back button located on the top left of the screen.10: NETME Tagged Events Interface Design Figure 3. To browse the next tagged events lists.10). it is the second option which will redirect the users to the ‘Tagged Events’ page (Figure 3.

11 will display the events details same as Figure 3. Pressing ‘Yes’ will un-tag the event while pressing ‘No’ will redirect back the users to the Tagged Event Details page. 20 . Figure 3. Pressing that button will display a sub menu. The extra function can be added by the administrators in the future if needed. As for now.8. the Events Tag page is only one page that can be scroll up or down.the few numbers of events currently available by the UiTM Shah Alam Computer and Mathematics Science Faculty.11: NETME Tagged Event Details Interface Design Figure 3. Un-tag the events will cause an event to be removed from the Tagged Events list. Users are also able to return back to the Tagged Events list by pressing the top right button. The button is located at the bottom of the page. Pressing the button will initiate the ‘Un-Tag’ function. that asks for confirmation from the users whether to un-tag the event or not. The only difference is that the button at the bottom of the screen will enable the users to un-tag the event.

NETME version 1. while the fourth version. The HTML 5 codes can only being used through the plugin of PhoneGap which is implemented onto the Eclipse. The test system consists of the three functioned built by the previous versions. The beta version is marked as version 1.0.0 would be the release candidate for this project. Results from the NETME Project are thoroughly described at Chapter 4. After several codes programming.0. an Android Device running on the latest version of Android OS (4. The first version is to test the NETME events browsing system.3 Ice Cream Sandwich). which is the current beta version. 21 . the initial prototype of the system is developed. the hardware and development tools requirement are determined.4 Phase 4: Implementation / Cutover This will mark the final phase of the Rapid Application Development methodology. There are four versions of NETME have been developed. is the integration of the whole NETME test system. The test device is Android One V by HTC. The language that is being used to develop the system was Android Native Language and HTML 5. The second version is to test the NETME events details. The application was built through the Developer Tools called Eclipse Indigo. a multi native language compiler. During this phase the first step is to implement and install the application on an Android based device. three of them are alpha types and only one made as beta version. The HTML 5 codes were used as the interface and front system design. The test run have been conducted and its progress results are constantly recorded. That version of NETME is installed on the Android device for testing.3. The third version is to test the NETME tagging system. 3. The system is later built using the appropriate programming language for developing an Android application.3 Phase 3: Construction During this phase.

System concept 9. Understand on how to develop and handle the system 3. 11. Find the initial system requirement foundation of the system 10.Table 3. Determining the requirement to develop the system such as information gathering and knowledge basis needed to develop the project. Articles and any other relevant information materials 6. System requirement and restrictions are verified 5. Verify the system restrictions 22 . Integrate the knowledge learned as a foundation for developing the system on the numbers of events and news that need to be synthesized 8. Magazines. Determine the scope and and capabilities are determined 4. A complete literature resources regarding the project 12. Determine the system concept and capabilities how would it function at its maximum capacity 14. Restrictions would be the boundary of the system 15. Resources would include knowledge and information for developing the system 2. Find Journals. Well established 7.12: Summarized Details and Descriptions of the RAD Model for NETME Project Phases Activities Details Output Requirements Planning 1. Capabilities will determine on how can the system deliver the concept and 13. Books.

Develop a system 17. Might require users feedback to ensure the system usability is within scope and users expectations 23 . Develop the system using the JDK for Android Application 29. Will determine the user needs and use it as a baseline in developing the system 24. Use Case diagram 23. A system model is established Construction 26. Interface Design the system deliver its functions output 25. This will be closely 19. Activity diagram related on how the user would want the system to be and how would 20.Phases Activities Details Output User Design 16. A complete extracted information based on the survey conducted 22. Build the system using the appropriate programming language for developing an Android application 30. Determine what kind of application were the users expecting 21. inputs and possibly 18. Initial prototype of the system is developed 27. Develop a system model model to show the system processes. Determine the hardware and development tools requirement 28.

Test run the system and record its results guarantee the system concept is fully utilize 24 . Testing will be done thoroughly as to 32.Phases Activities Details Output Implementation / Cutover 31. The system is successfully implemented 34. Implement the application on a Android based device 33. The final phase which includes testing 35.

Hence the screenshots that are being displayed within this chapter is the actual view of the application developed by this project. The survey is consists of five simple questions which are asked casually at the users on how NETME should behave. NETME for the Faculty of Computer Science and Mathematics. 25 . The casual terms are being used instead of formal wordings as it is easier for the users to understand what kind of questions that is being asked. ‘Slightly Yes’. Only one of the four answers can be selected. ‘No’ and ‘Definitely No’. The answers generally differs from ‘Yes’. The documentation of the survey was left open for a month and there were thirty one respondents for the online survey. The six questions within the survey have four different answers the users have chosen. The surveys have been conducted online via email and social networks. The answers are being asked by words and casual as possible. The questions asked are mostly general on what kind of application that the users were expecting.BAB 4 PEMERHATIAN 4. The phases start from the initial phase until the final phase of the development. 4.0 Introduction This chapter will further explain the details of all the function and interface design for the system that is related to the project development of News and Events Tag Mobile Edition. it is compulsory to determine what kind of features and functionality that the users were expecting.1 Survey Result As always before developing an application. An online survey has been conducted at Google Doc to determine what is the most wanted features are for NETME. This chapter will also include several screen shots taken from the Android device which have NETME installed.

These users were 26 . The spreadsheet functions as to keep in track of the time the users use the survey and what kind of answers the user have put in. They are mostly parents. Figure 4.Figure 4. This will ensure the integrity of the survey information as it being posted on the internet. most of the users are student or staffs which are directly related with the campus itself. spouses and part-time lecturers. any events related to the campus is fine not just the ones being held within the FSKM grounds. During the survey. The second highest community to be within the campus grounds are people which are somewhat have business to attend there.1 Spreadsheet of the Google Survey about NETME wanted functions. The spreadsheet will keep track of the survey results and record the date it was submitted.0 shows an early result of the survey where eight users have put their opinion via the online survey. The second highest survey stated that the advertisement system for the events or any announcement is as fine as it is. From the result of the survey. Most users have answered that they did not know any events being held within the campus unless someone else told them there is an event available at a certain time and location. The second question will ask the users regarding the scenario of noticing the events which are being held within the campus. These people also supported the survey by answering all of the survey questions earnestly.

2 Part 1 of the result conducted on Google Survey about NETME wanted functions. An observation has been made regarding this situation. The third question is concerning the events advertising methods that are being held within the campus are acceptable. while the second highest survey stated that there are some improvements need to be made.the user that stayed within the campus grounds. Figure 4. 27 . The users that stayed outside are within the users that answered no for this question. Users were to accustomed to the poster system that is being used within the campus grounds as the main medium to being notified the presence of an event or announcement. Most survey have answered that it is acceptable. and the result obtained from the observation was truly expected.

as it is merely asks the users whether they have Android phone or not. The fourth question was self-explanatory. Most users wanted simple concepts. The last question asks the users preferences whether the users likes simple concepts or complex concepts. Most survey says that the users have Android phone while some others majorly wants one. The fifth question was asking whether the users want an Android application that can tell them what events that are available and how can it help to notify its users.3 Part 2 of the result conducted on Google Survey about NETME wanted functions. This is to determine the number of Android users within the community. 28 . Mostly have answered yes on this question and the second majority wants it only of it is free.Figure 4. hence the system is built as simple as possible.

Table 4. Are you related Yes. sometimes I went there if needed No. Do you think the events advertising methods in your university / college is acceptable? Yes. it is too troublesome Yes. I am a student / staff (42%) to the university / student / college environment? staff 2. it is Yes. Are you aware of Yes.4 Survey questions and answers posted on Google Doc Question Answer One Answer Two Answer Three Answer Four Best Answer 1. it is (42%) improvements at the moment 29 . I have no relation to it whatsoever Yes. but there are some that I missed No. regularly I have business there Perhaps. unless someone told me (48%) 3. but it needs some No. unless someone told me No. I am a Yes. my the events that are currently being held at your university / college? university / college events are fairly noticeable Perhaps.

because I am a simple person (74%) understandable I'm both 30 .Question Answer One Answer Two Answer Three Answer Four Best Answer 4. as long it is Neither. why not? Yes. why not? (74%) 6. but I would want one No. it is not like I would use it anyway No. sometimes Simple. I don't Sure. One last question: You like simple things or complex things? Simple. why? No. I am an iPhone user No. Do you have an Android Phone? Yes. because I am a simple person Complex. why? (45%) 5. Do you want a phone app that can tell you all the events in your university / college / workplace? Sure. if its free No. I don't Yes.

By logic. The NETME application can run without any complications on the Virtual Machine.3 ICS. Figure 4. Reason being is that this application is running on HTML 5 code which is converted into native language.4.3 Android Device 31 .2 Test Result NETME application is being tested on an Android device running in version 4. NETME can be used on any platform as long as its being engineered by Eclipse that have PhoneGap plugin in it.0.0.5 Main Menu of the NETME application on 4. The test was conducted on the latest version of Android in order to have future-proof that might causes the application to malfunction. NETME has yet been tested on other version of Android devices however through the Android Virtual Machine provided by Eclipse.

The colour concept was designed to be as harmony as possible as it might be easy on the user eyes. The background is colour is being dimmed and dark as possible to ensure the visibility of the application wordings 32 . The main page is being designed to be as simple as possible and only use small amount of processing power.3 shows the main menu of the application. From there users will be able to navigate into the events browsing page or the track page. Judging from the Android device that it is being tested on.6 Events browsing page (first page) Figure 4.Figure 4. there are no performance issues or any similar scenario that makes this application runs slowly. this marks that this application is lightweight and compatible with lower end Android devices. blue and yellow was selected. Henceforth. As for the colour schemes. which contains all the events that the users have tagged during their browsing.

and buttons. when the user scrolls down a tag button will appear and user can press the button to tag that event. The colour scheme was also being used as a concern for the colour blind users that contrast is what matter most.4. Therefore the colour was picked to be different for every segment of the function. as shown in figure 4. At the browsing page.5. The users also able to return t the main menu by pressing the menu button on the top left. the picture shows that when the user selects the ‘events!’ button. user can navigate their way through by viewing what events that are listed within the application. simply scroll back up and press the next button which is shaped like an arrow on the top right to view the next event. From here. As for Figure 4. Figure 4.7 Tag button located at the bottom of the browsing page 33 . they will be redirected to the main events browsing page. If the event did not interest the user.

34 .8 Events browsing page (middle page) In Figure 4. notice that the browsing page navigation on the top changes as the user moves through the events browser. The home button will take the users back to the main menu. users will only need to scroll down and press the ‘home’ button located on that page. The top navigator will remain the same till the user reached the last events that the application has to offer.6.Figure 4. To return to the main menu.

Mostly was for the academic sake thus it was added into the events details.9 Events details page By pressing the event poster during the events browsing. When pressing that button a sub menu will appears to ask the user for confirmation (Figure 4. venue.Figure 4. time. The 35 . The event coupon was the FSKM students demand that they want information whether the event that the one they would be attending have coupons or not. The information will consist of date.8). this page also have the tag button which the user can press to tag the event and add it to the tagged event list. the application will send the users into a new page which gives the users several information regarding of the event (Figure 4.7). Like previously. event organizer and the event coupon.

a notification window will appear to tell the user that the tagging was successful (Figure 4. If the users press no.confirmation is designed to prevent any accidental tagging that the users might have done while navigating the page.9). Figure 4. The confirmation window will ask a simple question to ensure that the user want to tag the event or not.10 Events tagging confirmation window 36 . By pressing yes. the system will simply cancel the tagging operation and send the user back to the previous page.

Figure 4.11 Successfully tagged the event 37 .

3). The second option will lead the users to a new page that is called the Tag Tracker.Figure 4. This page will list the events which the users have tag previously on the events browsing.12 Menu for the tracking the tagged events Previously at the main menu (Figure 4. Other events that are not being tagged would not be displayed at the Tag Tracker page. Basically this concept was used to help the users in notifying them on what events that the user wants to keep track on. there is another option the users can select besides then browsing for the events. Only events that is been tag will be displayed here. The tagged events will significantly reduce user time by directly send the user to the event which they want to view and be reminded instead of having going through the entire browsing 38 .

the event will not be listed at the tagged list and thus one slot is available for the user to tag another event onto it. This page will be the only page that enables the user to un-tag the event. Figure 4. 39 . this page instead will enable the user to un-tag the event. If the user wants to un-tag the event. However as of the current version of NETME. Users will be able to scroll down the page to view more of the events that the users have tagged. Future release will enable the users to tag more than four events at one time. the users are only limited to tag four events.13 Details menu for the tagged events Different from the previous page where viewing the details enable the user to tag the event.page again. This is done to reduce the memory consumption when using the application. Pressing the button will again asks for the user confirmation.

1 Conclusion In brief.0 Introduction This chapter will conclude what has been done by the research from defining objectives until acquiring the results of News and Event Notifier for FSKM Project. Having less function will render the application entirely thus the design was a crucial stage to ensure none of such scenario might occur. 40 . That is completed through the online survey and the observation conducted during the early stage of this research. Hopefully this recommendation would justify this projects intention overall. With all the objectives satisfied. 5. As of for now. which is build a thorough design to achieve the main features of the application. the research finally done its third objective which is develop an application with the functionality of news and events tracking system. This chapter also define any further work or subject that could be done by other researcher that are be available to enhance this research and Android mobile system of this system as a whole. the only left of this project was its expansion or future updates which will help the system to become much more solid and useful for the community. Completing the first objective will cause the second objective to commence. News and Events Tagging Mobile Edition (NETME) is a system that helps users to retrieve events information without even need to go into the notice board or any related physical presence. The application was NETME.BAB 5 KESIMPULAN DAN CADANGAN 5. Users can simply download the application via Google Play (when the final version is released) and install the application on their Android phones. The design was consisting all of the necessary compartments which covers all of the NETME main functionality. Relevant with the second objective. the system is only a concept and the concept is successfully delivered for the sake of the final year project in the year of 2012. The first objective of this application was to identify the primary user requirement to build the application. and it is successfully being implemented on an Android device.

As of currently there are no centralized events system available for the UiTM.2 Limitation Admittedly there are several limitations of this research. Another limitation is including the real events details in the system because in this study. All are plainly being listed as normal text string or being kept as not in the highlights. the application was built for the concept for FSKM only. Basically.3 Recommendation After developing this system. it will help to eliminate entirely the size issues for the application.5. It is important to define the limitation as they should be considered when other relevant findings are interpreted. let alone other than UiTM. Meaning the events tagging system might not be that effective for other faculties. it is possible that this application can be imported to different platforms such as iOS. Users would only need to synchronize their NETME application via the portal and can be used both online and offline. This might limit the accuracy required the events information to be collected. all are the dummy data. For future work. NETME should be integrated with existed online system in UiTM that handles event or portals specifically for events. the application would not need to go through Google Play and can be constantly updated at the portal. When there is a database available at the events portal. 41 . 5. there are several suggestions to make this system is easier to manage and maintain by the administrator and friendly to the users. Hopefully this application can be made as the main platform for UiTM events notification in the later days. Since this project using a HTML 5 codes. Windows 7 Mobile. Symbian and Bada. When NETME is integrated with an online portal handled by UiTM itself.

& Gravano.net/roundups/lifestyle-roundups/top-10-minimaland-elegant-android-news-reader-apps/ Kim. W... JCDL’04. Breaking the Campus Bubble: Informed.V2-143. M. Butler.. Connected. R. Advances in Computer-Human Interaction . Y. G. H.. Volume 39 Issue 1. W.gigalb.. X.. IEEE . Electronics and Information Engineering (ICEIE) . M. (2011. 4 – 7. S.-s. Information Extraction. Volume 2 Proceedings of the 21st BCS HCI Group Conference . 30 Oct. W. J. & Shin. WWW 2005.. (2007). (2010. Hussain. W. December 1-3 ).. Y.appstorm. Advanced Communication Technology (ICACT) . 498 – 502. Cheung. pp. October 23). S. Engaged. A comparison of open and closed mobile platforms.-q. Mining Events and New Name Translations From Online Daily News. Huffman user interface for full touch screen based mobile phones. October 22-24). J. Sas. August 1 . H. Pervasive Computing. Intelligent Computing and Integrated Systems (ICISS) . Umgeher.. pp. Zhou..Rujukan Azmi. Arizona. 1021 – 1026..-R. (2010. from Android Appstorm: http://android. (2008. Top 10 Minimal and Elegant Android News Reader Apps. Lam. Y. A. pp. & Luan.1 Nov. Shahzad. C.. pp. Retrieved November 27. (1996). (2010. & Lehnert. from Gigalab: http://www. (2011). 674 – 677. Lechner. & Cho.. et al. 2011. USA.. S. P.-D. (2005)... Cho. V2-141 . C. Event identification within news topics. On-line event detection from web news stream. He. & Huang. 42 . & Dix. pp. Slany. B. D. Wang.). Day. Kanan. & Sun. Nam. H. (2005. IEEE... User Interface Design for a Mobile Multimedia Application: An Iterative Approach. (2004). Cowie. (2007). Efficient summarization-aware search for online news articles. Natural Language Processing and Knowledge Engineering . Japan.com/2011/02/special-report-the-ultimate-mobile-os-comparison/ Bharat. Android: Changing the Mobile Landscape. L. N.. Milchrahm. (2011). Y. An approach to find out user's interests based on mobile personalized news service system. 2011. Dai. (2010. Fu.-Y. Communications of the ACM . JCDL '07 Proceedings of the 7th ACM/IEEE-CS Joint Conference. M.-S. J. M. The Ultimate Mobile OS Comparison. K. News in The Age of the Web. Chiba.. 189 – 194.. C. Z.. X. February 10 15).3). Lin. Retrieved October 11. February 7-10). Tucson.. 105 – 110. & Wang. Dakka.. pp. Zhou. Pervasive Computing and Applications (ICPCA) .

Proffitt. Intelligent Systems and their Applications . (n. 2011 International Conference . pp. October 29-31). & Blair-Go.. Methodology of user interfaces design based on Android. & Liu. 43 . pp.html Phuvipadawat. M. Li. IEEE 2011 . Smartphone OS Comparison. QSQA. (2005). B. Naik.com/pulse-news-reader/ Mahil. 3). B. Reece. Yang. Communications of the ACM . S.Li. Aug. SIGIR’05. Retrieved from http://www. (2011. 1 .. Open Android-For better and for worse [Tools & Toys]. (1999. K.. P. R.. Z. (2011). 32 – 43. (2010..3. A. T. pp. C.August). A Probabilistic Model for Retrospective News Event Detection. Learning approaches for detecting and tracking news events. K. Lonczak.techtree. November 15-17). 1 . University of Wolverhampton. 120 – 123. Brown.. QSQA . Hao.. S... & Fu.). Retrieved Febuary 2012. Y. J. Rapid Application Development. Carbonell. Beijing.. July . J.. & Li.. 2005 2nd International Conference . Prototyping. 31 . X.13. L. Pierce. Su. D. Web Intelligence and Intelligent Agent Technology (WI-IAT) . T.. Li. Applications and Systems. (2011. Multimedia Technology (ICMT).Sept. (2010). J. Characterizing Failures in Mobile OSes : A Case Study with Android and Symbian. F. from Pulse News Reader: http://www. (2009). Mobile Technology. Maji. January 27th).26. NewsInEssence: Summarizing Online News Topics.. W. Multimedia Technology (ICMT) . SDLC Models. SIGIR’11. & Chan. & Yan-Hui. M. (2005. IEEE 21st International Symposium on Software Reliability Engineering . Song. 6. Wang. pp. & Murata. W. & Bagchi.d. Salvador. Wang. Song. China. Brazil. (2010.. J. H. T. 408 – 411. B.. Sultana. Archibald. Spectrum. Design and Implementation of Input Method based on Embedded Multimedia Mobile Device. S. & June... Breaking News Detection and Tracking in Twitter. AndroidTapp. 2012. Prototyping and Software Development Approaches . 22 – 24. (2011). Chan. Radev. D.. A. Xia-Xia.. V. (2011). Volume 48 Issue 10. SCENE: A Scalable Two-Stage Personalized News Recommendation System. (2005). Y. 2 ..androidtapp. X. & Ma.com/India/Features/Smartphone_OS_Comparison/551-114322-899.. Navigation on Mobile News. (2007). Otterbacher. July 26-28). School of Computing. pp. Winkel. p. D..