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 TechnologyFaculty of Computer and Mathematical Sciences

April 2012

APPROVAL

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

by

NUR FARHANA BINTI SAAD2011481902

A thesis submitted toFACULTY OF COMPUTER AND MATHEMATICAL SCIENCESUNIVERSITI TEKNOLOGI MARA

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

Approved by the examining committee:

EN AHMAD ZAMBRI SHAHUDDINProject Supervisor

July 2012

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 SAAD2011481902

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.

ISI KANDUNGAN

KANDUNGAN PAGEKELULUSANiiPENGISTIHARANiiiPENGAKUAN ivTABLE OF CONTENTSvLIST OF FIGURESviiLIST OF TABLEixLIST OF ABBREVIATIONSxABSTRACTxiCHAPTER 1: RESEARCH OVERVIEW11.0 Research Background11.1 Problem Statement21.2 Research Aim31.3 Research Requirements31.4 Research Objectives41.5 Research Scope41.6 Research Significance41.7 Research Design5CHAPTER 2: LITERATURE REVIEW72.0 Introduction72.1 Review of the current existing Android News applications82.2 Approaches done by other researchers projects152.2.1 Navigation on Mobile News152.2.2 An approach to find out users interests based on 17mobile personalized news service system2.2.3 Efficient Summarization-Aware Search for Online 18News Articles2.3 Development techniques 232.3.1 Waterfall Model232.3.2 Prototype252.3.3 Rapid Application Development27CHAPTER 3: METHODOLOGY313.0 Introduction313.1 Phase 1: Requirements Planning323.2 Phase 2: User Design333.2.1 Determine the user needs333.2.2 Use Case Diagram343.2.3 Activity Diagram353.2.4 System Requirements383.2.5 Interface Design403.3 Phase 3: Construction463.4 Phase 4: Implementation / Cutover46CHAPTER 4: RESULTS AND FINDINGS504.0Introduction504.1 Survey Result504.2Test Result56CHAPTER 5: CONCLUSION AND RECOMMENDATION655.0Introduction655.1Conclusion655.2Limitation665.3Recommendation66REFERENCES67APPENDIX69

List of figures

NoFigurePage

2.1Screenshot of the Pulse News App8

2.2Screenshot of CNN Android9

2.3Screenshot of the CNET News App10

2.4Screenshot of MSNBC Android11

2.5Screenshot of Yahoo! News Android12

2.7BHN & CLN Structure (Su, Chan, & Chan, 2005)14

2.8Online Summarization Clustering Method (Dakka & Gravano, 2007)16

2.10Example of the Waterfall Model (QSQA, 2009)24

2.112.12Experimental Prototype Model (Mahil & June)RAD Model on Iterative Basis (Reece, 2007)2528

3.1The Rapid Application Development Model for this project31

3.2Screenshot of the online survey at Google Doc33

3.3NETME Use Case Diagram34

3.4NETME Browsing Events Activity Diagram36

3.5NETME View Tagged Events Activity Diagram37

3.6Screenshot of the Eclipse Indigo39

3.7NETME Main Menu Interface Design41

3.8NETME Events Browsing Interface Design42

3.9NETME Events Details Interface Design43

3.10NETME Tagged Events Interface Design45

3.11NETME Tagged Event Details Interface Design45

4.2Spreadsheet of the Google Survey about NETME wanted functions.51

4.2Part 1 of the result conducted on Google Survey about NETME wanted functions.

52

4.4Part 2 of the result conducted on Google Survey about NETME wanted functions.

53

4.5Main Menu of the NETME application on 4.0.3 Android Device56

4.6Events browsing page (first page)

57

4.7Tag button located at the bottom of the browsing page58

4.8Events browsing page (middle page)59

4.9Events details page60

4.10Events tagging confirmation window61

4.11Successfully tagged the event62

4.12Menu for the tracking the tagged events

63

4.13Details menu for the tagged events64

Tables

NoTablePage

1.1Research Design and relevant information5

2.6Review of the current existing Android News applications13

2.9Approaches done by other researchers projects20

2.13Development techniques and models29

3.12Summarized Details and Descriptions of the RAD Model for NETME Project47

4.4Survey questions and answers posted on Google Doc54

LIST OF ABBREVIATIONS

FSKMFaculty of Computer and Mathematic ScienceHTML 5Hyper Text Markup Languages 5ICSIce Cream SandwichNETMENews and Events Tag Mobile EditionOSOperating System

ABSTRAK

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

5

BAB 1PENDAHULUAN

1.0 PENGENALANKeselamatan di tempat kerja dalam sesebuah organisasi adalah penting bagi semua pekerja untuk menjalani pekerjaan yang selesa dan selamat. Tambahan lagi, ramai yang merasakan bekerja di ruang pejabat adalah tempat yang paling selamat. Hal ini kerana ruang pejabat juga dilihat sebagai satu kawasan atau ruang yang tidak mempunyai risiko bagi pekerja yang membuatkan seseorang cedera mahupun sakit. Beberapa punca utama berlakunya kemalangan di tempat kerja adalah orang terjatuh, terhempap oleh benda yang terjatuh serta terkena benda-benda pegun atau tidak bergerak seperti yang dilaporkan oleh Pertubuhan Keselamatan Sosial Malaysia (PERKESO, 2006). Seperti yang dilaporkan, hal ini menunjukan punca utama sesuatu kemalangan di tepmat kera yang menimbulkan kecederaan aalah jarang sekali dan tidak berkala. 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. Tambahan lagi ruangan pejabat juga bukanlah satu ruangan yang menyimpan bahan radiasi, cecair kimia, sampel-sampel bacteria ataupun serangga dan sebagainya yang mampu mengancam keselamatan pekerja. 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.

1.1 PENYATAAN MASALAHMenurut senario hari ini, beberapa masalah berkaitan dengan keselamatan bekerja ruang pejabat boleh dibangkitkan. Perkara utama yang akan dibangkitkan juga adalah peranan majikan tentang tanggungjawab mereka untuk mengawal keselematan di ruang pejabat.i) Tidak mengambil endah tentang keselamatan pekerja yang bertugas di ruangan pejabat.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.iii) Keselamatan yang boleh dikategorikan kepada beberapa jenis keselamatan iaitu dari aspek kimia., biologi, fizikal dan ernogomik. 1.2 OBJEKTIF KAJIAN

1.1.1 OBJEKTIF UMUMSecara umumnya, objektif kajian ini adalah untuk mengkaji perihal keselamatan di tempat kerja yang menekankan keselamatan diruang pejabat.

1.1.2 OBJEKTIF KHUSUSBagi objektif khusus untuk kajian ini ianya akan ditumpukan kepada beberapa objektif dibawah :

1) Mengenalpasti tentang penekanan keselamatan pekerja di tempat kerja bahagian ruangan pejabat.

2) Menganalisia tentang kepentingan polisi keselamatan dan keperluan mengetahui akta dan undang-undang keselamatan di tempat kerja.

3) Mengkaji kategori-kategori keselamatan ditempat kerja dari aspek fizikal, kimia, biologi dan ernogomik.

1.3 KEPENTINGAN KAJIANKajian ini amat penting kerana ianya dapat memberi kesedaran kepada pekerja yang bekerja di ruangan pejabat. Selain itu ia juga dapat mengenalpasti tentang penekanan pihak bertanggungjawab dalam membantu menguruskan keselamatan di tempat kerja dalam ruangan pejabat. Tambahan lagi, kajian ini juga dapat memberi satu analisa tentang pentingnya untuk seseorang pekerja mengetahui tentang akta dan undang-undang yang berkaitan dengan keselamatan pekerja di dalam ruangan pejabat. Diharapkan kajian ini juga dapat memenuhi keperluan pekerja dalam mengetahui tentang kepentingan selain risiko berbangkit keselamatan di tempat kerja dalam ruangan pejabat. Tambahan lagi, beberapa ciri-ciri keselamatan dari segi kimia, biologi, fizikal dan ernogomik juga akan dikupas dengan lebih lanjut.

1.4 SKOP KAJIANPerbincangan tentang kesedaran pekerja tentang keselamatan mereka dan undang-undang yang berkaitan dengan keselamatan di tempat kerja lebih-lebih lagi di ruangan pejabat yang kurang risiko kecedaran. Bagi tujuan ini fokus kajian akan tertumpu kepada beberapa orang responden yang bekerja di dalam ruangan pejabat.Oleh yang demikian, seramai 10 orang responden akan dipilih sebagai sampel penyelidikan ini.

1.5 STRUKTUR KAJIANKajian yang dijalankan akan menumpukan kepada dua permasalahan keselamatan di tempat kerja dalam ruangan pejabat serta bertindak untuk mencapai objektif yang di nyatakan. Dalam kajian ini akan merangkumi perbandingan literatur yang menfokuskan kepada tanggungjawab majikan dalam menentukan keselamatan di tempat kerja, pentingnya keselamatan di tempat kerja, keselamatan di ruangan pejabat, kaedah keselamatan di ruangan pejabat dan kepentingan dan kesedaran keselamatan di ruangan pejabat. BAB 2LITERATUR

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

2.1 KESELAMATAN DI TEMPAT KERJA Jabatan Keselamatan dan Kesihatan telah menggubal satu akta pada tahun 1994 (AKKP 1994), 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, kerajaan mahupun badan berkanun akta ini digunakan dalam menjadikan sesuatu persekitaran tempat kerja itu kurang risikonya. Kewajiban dalam menjaga keselamatan di tempat kerja bukan bergantung pada majikan sahaja, malahan pekerja juga perlu ada kesedaran yang tinggi dalam diri pekerja untuk memastikan kemalangan sifar dalam kalangan pekerja.

BAB 3 METODOLOGI

3.0 IntroductionThis project is being carried out within a year, starting from September 2011 until July 2012. Within this one short year, several plans and scheduling have been made to ensure the progress of this project. The timeframe for this project can be viewed through the Gantt chart available at the Appendix section (Appendix A). 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. As mentioned earlier, RAD has been chosen as the development method for this project. RAD model will consist mainly of four (4) steps which best described through the figure below.

Figure 3.1: The Rapid Application Development Model for this project

Rapid Application Development or RAD is a software development process which introduced by James Martin during the early 90s. His argument stated that a software development module should be designed to ensure the developers build a system that the user really needs (Reece, 2007). Therefore, RAD model will consist of four stages which are requirement planning, user design, construction and implementation.

3.1Phase 1: Requirements Planning Determining the requirement to develop the system such as information gathering and knowledge basis needed to develop the project. During this phase, several relevant references have been searched and reviewed and being used as main references. The references are consists of journals, books, magazines, articles and any other relevant information materials like the websites. Resources would include on the numbers of events and news that need to be synthesized. It is also important to integrate the knowledge learned from the research as a foundation for developing the system.During this phase, methods to determine the system concept and capabilities are also conducted. Capabilities will determine on how can the system deliver the concept and how would it function at its maximum capacity. Later on, the phase continued with the finding of the initial system requirement. This phase reaches its final stage through the verification of the system restrictions. 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.Outputs that are obtained from conducting all of the steps are complete literature resources regarding the project, well established knowledge and information for developing the system, understood on how to develop and handle the system, system concept and capabilities are determined and the system requirement and restrictions are thoroughly verified.

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

Figure 3.2 Screenshot of the online survey at Google Doc3.2.2 Use Case DiagramUse case diagram describe the system from the users point of view. It shows the interaction between users and systems functions. In some cases, the system itself or time period could be the actor as well. Since mobile application only have small amount of functionality, this use case diagram is miniature compare to the other contemporary systems.

Figure 3.3 NETME Use Case DiagramThe figure above showed the general view of the case study diagram for the system. For the NETME scope, there are two actors which are users and system administrators. Users would consist of every user that uses the NETME system, locally or externally. They are needed to download the application first at Google Play to use the application. Each user then will install the application in their Android mobile device and launch the system when the installation is complete. After installation users will be able to view the events on the application and tag as per needed. The system is behaving locally meaning that if the users tag or view the event in their phone, they will not be able to view the event they tag at other Android devices. In other words the system is offline and only need to be online when the users need to update or download it at the first place. The administrator is the person in the system community that will handle the system updates and patches. If there is a new event available, the administrators are assigned to update the system and upload it into Google Play. The user will be informed via Google Play that a new update is available and they will need to update their application once again.3.2.3 Activity DiagramNETME is a local application, which is not directly interacting with the administrators of the system. The administrators would only update new events or changes in the information for certain events as per needed. Administrators will upload the updates through Google Play and users would require retrieve the updates whenever they have internet access. This will enable several users that did not have data line or internet connection to use the application. The events are being listed by weeks per months, meaning that the users only need to update the events once every month. There also will be a case where new events are constantly update through the system, as for that the users will need to constantly update their NETME via internet connection. 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. Its a drawback for the system in order to enable all users to use the system without any restrictions. Some users may not be able to obtain the latest events via Google Play, but they can retrieve the updates via other Android Devices that already have the updates. NETME Activity Diagram has two major activities which the application would handle. Each of the activities is inter-related to one another. One of the major activities is browsing for the events while the other is viewing the tagged events which they want to attend.

Figure 3.4 NETME Browsing Events Activity DiagramIn figure 3.4 above shows the NETME browsing events activity diagram for the system. When starting the application, the system will display a simple main menu for the users to navigate. At the main menu, 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. Through that option, users are able to browse through the events listed by the application and view the events details by selecting the poster. In the event details, each of events will list important information and particulars about the event. The information will include date, venue and the purpose of the event. Users will be able to choose whether want to tag the event into the NETME Events Tag which functioned as to inform them any relevant changes about the event and when the event will begin.

Figure 3.5 NETME View Tagged Events Activity Diagram

In figure 3.5 previously shows the activity of a NETME user viewing the tagged events in the system. Likewise, when starting the application the system will display a main menu for the users to navigate. Only this time the users will need to select the second option within the main menu. That option will lead the users to a list of events which the user already tagged in during their browsing on the previous activity. Clicking on one of the events will lead the users into a new window that will display the tagged events details. 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. Users can simply instead view the events they wanted to partake in and check the details as a reminder. 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.

3.2.4 System RequirementsThis section will discuss on the hardware and software specification. There are two types of hardware, one is the computer itself and the other is the Android device. Software would be the tools required to develop this project. 1) Hardwarea) PC Desktopi) CPU : Pentium Dual Core @ 3.06 GHzii) OS: Windows 7 Ultimate 64-bitiii) HD: 120GB ( 1GB used for the project )b) HTC One V ( Android Device )i) OS:4.0.3 ICSii) SD:8GB (1 MB used for the project)

2) Softwarea) JDK for Android OSb) Eclipse with PhoneGap Pluginc) Adobe Dreamweaverd) Microsoft Office ( Word, Excel, Powerpoint )e) Online UML Design Tool Gliffy

The hardware requirement is the fundamental requirement in order to build and run the application. The application is being built on a PC Desktop with Pentium Dual Core as the main processing unit. The hard disk space allocated for this project was one gigabyte. Most of the spaces were occupied by the system interface design and early built versions of the application. The hardware requirement for the android device is being line out by a HTC smartphone called One V. The smartphone is running on Ice Cream Sandwich version (4.0.3). The android device has 8 gigabyte of space and only 1 MB is being used for the application.

Figure 3.6 Screenshot of the Eclipse IndigoFor the software requirement, there are several software are being used to build the system. The main application would be the JDK, Java Development Kit for Android OS. The JDK will serve as the main tool for developing the NETME application. To engineer the JDK, there is an application which is used as the main tool to program the application. The tool is called Eclipse (Figure 3.6). Eclipse is a powerful tool which enables Android Developers to develop Android App using native language. The version of Eclipse being used in this project is the Indigo Version. This project also embeds HTML 5 codes onto the building of the application. To handle the HTML 5 codes, two application tools are being used. First is the PhoneGap, a plugin which enables Eclipse to handle HTML 5 codes and converts them into native language. Second is the Adobe Dreamweaver which is to engineer the HTML 5 codes.Microsoft Office is the main suite application being used for documentation and presentation purpose. Microsoft Word is the main word processing software which is used as the platform to write documentations and this thesis. Microsoft Excel is being used as the spreadsheet for collection information and survey from the users. Microsoft Powerpoint is being used as the main presentation tool for the Final Year Project presentation at UiTM Shah Alam.

3.2.5 Interface DesignThe early design of NETME will consist of several menu selection that are made in order to enable users navigate through the application smoothly. This system would require internet access for updates. However, NETME still can be used even without having any internet access. The design changed after users requested that the system needs to be simpler and direct to its functions. The screen orientation is locked on portrait, meaning the screen would not rotate to the widescreen or landscape view. The screen is locked that way to avoid complications on other version of Android devices.

Figure 3.7: NETME Main Menu Interface DesignThe interface design of NETME Main Menu is as shown in Figure 3.6. 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. From the design, there are two options will be available for the users. The first option, namely Event will direct the users towards the event selection, where the users able to view all the events which are listed by the application (Figure 3.7). The second option will direct the users to the Tagged Events. 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.8)

Figure 3.8: NETME Events Browsing Interface DesignFigure 3.7 shows the View Events page, for the Events Browsing function. This page will enable the users to navigate and browse through the events. 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, simply press the Back button on the top left to go to the previous event page. The large square in the middle will show the events poster related to the event. By pressing that poster, the application will redirect the users onto a new page which is the Events Details. Below the poster is a button where the user can initiate to tag the events displayed on that page. Pressing that button will direct the users towards a new sub window that asks for the users confirmation. 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, which is located on another page. Pressing No instead will lead the users back to the event page.

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

Figure 3.10: NETME Tagged Events Interface DesignFigure 3.10 is an interface design for the tagged events. This menu can be accessed through the main menu only. In Figure 3.7, it is the second option which will redirect the users to the Tagged Events page (Figure 3.10). At this page users will be able to select several events that they have already tagged previously at the Events Browsing page. The listed events are all buttons, which the users can interact with. By pressing one of the buttons will direct the users onto a new page which display the events details (Figure 3.11). Users can return back to the main menu by pressing the back button located on the top left of the screen.As of currently there are no limitations for the events listed at that page. However there is an idea to design the Tagged Events by limiting four events per page. To browse the next tagged events lists, 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 the few numbers of events currently available by the UiTM Shah Alam Computer and Mathematics Science Faculty. The extra function can be added by the administrators in the future if needed. As for now, the Events Tag page is only one page that can be scroll up or down.

Figure 3.11: NETME Tagged Event Details Interface DesignFigure 3.11 will display the events details same as Figure 3.8. The only difference is that the button at the bottom of the screen will enable the users to un-tag the event. The button is located at the bottom of the page. Pressing the button will initiate the Un-Tag function. Un-tag the events will cause an event to be removed from the Tagged Events list. Pressing that button will display a sub menu, that asks for confirmation from the users whether to un-tag the event or not. Pressing Yes will un-tag the event while pressing No will redirect back the users to the Tagged Event Details page. Users are also able to return back to the Tagged Events list by pressing the top right button.3.3Phase 3: ConstructionDuring this phase, the hardware and development tools requirement are determined. The system is later built using the appropriate programming language for developing an Android application. The language that is being used to develop the system was Android Native Language and HTML 5. The application was built through the Developer Tools called Eclipse Indigo, a multi native language compiler. The HTML 5 codes were used as the interface and front system design. The HTML 5 codes can only being used through the plugin of PhoneGap which is implemented onto the Eclipse. After several codes programming, the initial prototype of the system is developed.There are four versions of NETME have been developed, three of them are alpha types and only one made as beta version. The first version is to test the NETME events browsing system. The second version is to test the NETME events details. The third version is to test the NETME tagging system, while the fourth version, which is the current beta version, is the integration of the whole NETME test system. The test system consists of the three functioned built by the previous versions. The beta version is marked as version 1.0.NETME version 1.0 would be the release candidate for this project. That version of NETME is installed on the Android device for testing.3.4Phase 4: Implementation / CutoverThis will mark the final phase of the Rapid Application Development methodology. During this phase the first step is to implement and install the application on an Android based device. The test device is Android One V by HTC, an Android Device running on the latest version of Android OS (4.0.3 Ice Cream Sandwich). The test run have been conducted and its progress results are constantly recorded. Results from the NETME Project are thoroughly described at Chapter 4.

Table 3.12: Summarized Details and Descriptions of the RAD Model for NETME ProjectPhases

ActivitiesDetailsOutput

Requirements Planning

1. Find Journals, Books, Magazines, Articles and any other relevant information materials

2. Integrate the knowledge learned as a foundation for developing the system

3. Determine the system concept and capabilities

4. Find the initial system requirement

5. Verify the system restrictions

6. Determining the requirement to develop the system such as information gathering and knowledge basis needed to develop the project.

7. Resources would include on the numbers of events and news that need to be synthesized

8. Capabilities will determine on how can the system deliver the concept and how would it function at its maximum capacity

9. Determine the scope and foundation of the system

10. Restrictions would be the boundary of the system11. A complete literature resources regarding the project

12. Well established knowledge and information for developing the system

13. Understand on how to develop and handle the system

14. System concept and capabilities are determined

15. System requirement and restrictions are verified

Phases

ActivitiesDetailsOutput

User Design

16. Determine what kind of application were the users expecting

17. Develop a system model

18. Use Case diagram

19. Activity diagram

20. Interface Design21. Will determine the user needs and use it as a baseline in developing the system

22. Develop a system model to show the system processes, inputs and possibly output

23. This will be closely related on how the user would want the system to be and how would the system deliver its functions

24. A complete extracted information based on the survey conducted

25. A system model is established

Construction

26. Determine the hardware and development tools requirement

27. Develop the system using the JDK for Android Application28. Build the system using the appropriate programming language for developing an Android application

29. Might require users feedback to ensure the system usability is within scope and users expectations30. Initial prototype of the system is developed

Phases

ActivitiesDetailsOutput

Implementation / Cutover

31. Implement the application on a Android based device

32. Test run the system and record its results

33. The final phase which includes testing

34. Testing will be done thoroughly as to guarantee the system concept is fully utilize

35. The system is successfully implemented

BAB 4PEMERHATIAN

4.0 IntroductionThis 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, NETME for the Faculty of Computer Science and Mathematics. The phases start from the initial phase until the final phase of the development. This chapter will also include several screen shots taken from the Android device which have NETME installed. Hence the screenshots that are being displayed within this chapter is the actual view of the application developed by this project.4.1 Survey ResultAs always before developing an application, it is compulsory to determine what kind of features and functionality that the users were expecting. An online survey has been conducted at Google Doc to determine what is the most wanted features are for NETME. The survey is consists of five simple questions which are asked casually at the users on how NETME should behave. The questions asked are mostly general on what kind of application that the users were expecting. The surveys have been conducted online via email and social networks. 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 answers generally differs from Yes, Slightly Yes, No and Definitely No. The answers are being asked by words and casual as possible. 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. Only one of the four answers can be selected.

Figure 4.1 Spreadsheet of the Google Survey about NETME wanted functions.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. Figure 4.0 shows an early result of the survey where eight users have put their opinion via the online survey. The spreadsheet will keep track of the survey results and record the date it was submitted. This will ensure the integrity of the survey information as it being posted on the internet. From the result of the survey, most of the users are student or staffs which are directly related with the campus itself. The second highest community to be within the campus grounds are people which are somewhat have business to attend there. They are mostly parents, spouses and part-time lecturers. These people also supported the survey by answering all of the survey questions earnestly. The second question will ask the users regarding the scenario of noticing the events which are being held within the campus. During the survey, any events related to the campus is fine not just the ones being held within the FSKM grounds. 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 highest survey stated that the advertisement system for the events or any announcement is as fine as it is. These users were the user that stayed within the campus grounds. The users that stayed outside are within the users that answered no for this question.The third question is concerning the events advertising methods that are being held within the campus are acceptable. Most survey have answered that it is acceptable, while the second highest survey stated that there are some improvements need to be made. An observation has been made regarding this situation, and the result obtained from the observation was truly expected. 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.

Figure 4.2 Part 1 of the result conducted on Google Survey about NETME wanted functions.

Figure 4.3 Part 2 of the result conducted on Google Survey about NETME wanted functions.The fourth question was self-explanatory, as it is merely asks the users whether they have Android phone or not. This is to determine the number of Android users within the community. 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. Mostly have answered yes on this question and the second majority wants it only of it is free. The last question asks the users preferences whether the users likes simple concepts or complex concepts. Most users wanted simple concepts; hence the system is built as simple as possible.Table 4.4 Survey questions and answers posted on Google DocQuestion

Answer OneAnswer Two

Answer ThreeAnswer FourBest Answer

1.Are you related to the university / college environment?

Yes, I am a student / staffYes, regularly I have business therePerhaps, sometimes I went there if neededNo, I have no relation to it whatsoeverYes, I am a student / staff(42%)

2.Are you aware of the events that are currently being held at your university / college?

Yes, my university / college events are fairly noticeablePerhaps, but there are some that I missedNo, unless someone told me-No, unless someone told me(48%)

3.Do you think the events advertising methods in your university / college is acceptable?

Yes, it isYes, but it needs some improvements No, it is too troublesome at the moment

-Yes, it is(42%)

Question

Answer OneAnswer Two

Answer ThreeAnswer FourBest Answer

4.Do you have an Android Phone?

Yes, why?No, but I would want oneNo, I am an iPhone userNo, I don'tYes, why?(45%)

5.Do you want a phone app that can tell you all the events in your university / college / workplace?

Sure, why not?Yes, if its freeNo, it is not like I would use it anywayNo, I don'tSure, why not?(74%)

6.One last question: You like simple things or complex things?

Simple, because I am a simple personComplex, as long it is understandableNeither, sometimes I'm both-Simple, because I am a simple person(74%)

4.2 Test ResultNETME application is being tested on an Android device running in version 4.0.3 ICS. 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 NETME application can run without any complications on the Virtual Machine. Reason being is that this application is running on HTML 5 code which is converted into native language. By logic, NETME can be used on any platform as long as its being engineered by Eclipse that have PhoneGap plugin in it.

Figure 4.5 Main Menu of the NETME application on 4.0.3 Android Device

Figure 4.6 Events browsing page (first page)Figure 4.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, which contains all the events that the users have tagged during their browsing. The main page is being designed to be as simple as possible and only use small amount of processing power. Judging from the Android device that it is being tested on, there are no performance issues or any similar scenario that makes this application runs slowly. Henceforth, this marks that this application is lightweight and compatible with lower end Android devices.As for the colour schemes, blue and yellow was selected. 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 and buttons. The colour scheme was also being used as a concern for the colour blind users that contrast is what matter most. Therefore the colour was picked to be different for every segment of the function.As for Figure 4.4, the picture shows that when the user selects the events! button, they will be redirected to the main events browsing page. From here, user can navigate their way through by viewing what events that are listed within the application. At the browsing page, when the user scrolls down a tag button will appear and user can press the button to tag that event, as shown in figure 4.5. If the event did not interest the user, simply scroll back up and press the next button which is shaped like an arrow on the top right to view the next event. The users also able to return t the main menu by pressing the menu button on the top left.

Figure 4.7 Tag button located at the bottom of the browsing page

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

Figure 4.9 Events details page By pressing the event poster during the events browsing, the application will send the users into a new page which gives the users several information regarding of the event (Figure 4.7). The information will consist of date, venue, time, event organizer and the event coupon. 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. Mostly was for the academic sake thus it was added into the events details. Like previously, this page also have the tag button which the user can press to tag the event and add it to the tagged event list. When pressing that button a sub menu will appears to ask the user for confirmation (Figure 4.8). The confirmation is designed to prevent any accidental tagging that the users might have done while navigating the page.The confirmation window will ask a simple question to ensure that the user want to tag the event or not. By pressing yes, a notification window will appear to tell the user that the tagging was successful (Figure 4.9). If the users press no, the system will simply cancel the tagging operation and send the user back to the previous page.

Figure 4.10 Events tagging confirmation window

Figure 4.11 Successfully tagged the event

Figure 4.12 Menu for the tracking the tagged eventsPreviously at the main menu (Figure 4.3), there is another option the users can select besides then browsing for the events. The second option will lead the users to a new page that is called the Tag Tracker. This page will list the events which the users have tag previously on the events browsing. Only events that is been tag will be displayed here. 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. 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 page again. Users will be able to scroll down the page to view more of the events that the users have tagged. However as of the current version of NETME, the users are only limited to tag four events. This is done to reduce the memory consumption when using the application. Future release will enable the users to tag more than four events at one time.

Figure 4.13 Details menu for the tagged eventsDifferent from the previous page where viewing the details enable the user to tag the event, this page instead will enable the user to un-tag the event. Pressing the button will again asks for the user confirmation. If the user wants to un-tag the event, 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.

BAB 5KESIMPULAN DAN CADANGAN5.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. 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. Hopefully this recommendation would justify this projects intention overall.

5.1 ConclusionIn brief, 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. Users can simply download the application via Google Play (when the final version is released) and install the application on their Android phones. The first objective of this application was to identify the primary user requirement to build the application. That is completed through the online survey and the observation conducted during the early stage of this research. Completing the first objective will cause the second objective to commence, which is build a thorough design to achieve the main features of the application. The design was consisting all of the necessary compartments which covers all of the NETME main functionality. Having less function will render the application entirely thus the design was a crucial stage to ensure none of such scenario might occur. Relevant with the second objective, the research finally done its third objective which is develop an application with the functionality of news and events tracking system. The application was NETME, and it is successfully being implemented on an Android device.With all the objectives satisfied, 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. As of for now, 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.

5.2 LimitationAdmittedly there are several limitations of this research. It is important to define the limitation as they should be considered when other relevant findings are interpreted. Basically, the application was built for the concept for FSKM only. Meaning the events tagging system might not be that effective for other faculties, let alone other than UiTM. Another limitation is including the real events details in the system because in this study, all are the dummy data. This might limit the accuracy required the events information to be collected.

5.3 RecommendationAfter developing this system, there are several suggestions to make this system is easier to manage and maintain by the administrator and friendly to the users. For future work, NETME should be integrated with existed online system in UiTM that handles event or portals specifically for events. As of currently there are no centralized events system available for the UiTM. All are plainly being listed as normal text string or being kept as not in the highlights. When NETME is integrated with an online portal handled by UiTM itself, the application would not need to go through Google Play and can be constantly updated at the portal. Users would only need to synchronize their NETME application via the portal and can be used both online and offline. When there is a database available at the events portal, it will help to eliminate entirely the size issues for the application. Since this project using a HTML 5 codes, it is possible that this application can be imported to different platforms such as iOS, Windows 7 Mobile, Symbian and Bada. Hopefully this application can be made as the main platform for UiTM events notification in the later days.

Rujukan

Azmi, S. (2011, October 23). The Ultimate Mobile OS Comparison. Retrieved November 27, 2011, from Gigalab: http://www.gigalb.com/2011/02/special-report-the-ultimate-mobile-os-comparison/Bharat, K. (2005). News in The Age of the Web. WWW 2005. Chiba, Japan.Butler, M. (2011). Android: Changing the Mobile Landscape. Pervasive Computing, IEEE , 4 7.Cho, H.-Y., Nam, C.-S., & Shin, D.-R. (2010, August 1 - 3). A comparison of open and closed mobile platforms. Electronics and Information Engineering (ICEIE) , pp. V2-141 - V2-143.Cowie, J., & Lehnert, W. (1996). Information Extraction. Communications of the ACM , Volume 39 Issue 1.Dai, X., & Sun., Y. (2010, October 22-24). Event identification within news topics. Intelligent Computing and Integrated Systems (ICISS) , pp. 498 502.Dakka, W., & Gravano, L. (2007). Efficient summarization-aware search for online news articles. JCDL '07 Proceedings of the 7th ACM/IEEE-CS Joint Conference. IEEE.Day, N., Sas, C., & Dix, A. (2007). Breaking the Campus Bubble: Informed, Engaged, Connected. Volume 2 Proceedings of the 21st BCS HCI Group Conference .Fu, Y., Zhou, M.-q., Wang, X.-s., & Luan, H. (2010, December 1-3 ). On-line event detection from web news stream. Pervasive Computing and Applications (ICPCA) , pp. 105 110.He, Y., Lin, B., Zhou, Y., & Wang, C. (2005, 30 Oct.- 1 Nov.). An approach to find out user's interests based on mobile personalized news service system. Natural Language Processing and Knowledge Engineering , pp. 674 677.Hussain, Z., Lechner, M., Milchrahm, H., Shahzad, S., Slany, W., Umgeher, M., et al. (2008, February 10 - 15). User Interface Design for a Mobile Multimedia Application: An Iterative Approach. Advances in Computer-Human Interaction , pp. 189 194.Kanan, S. (2011). Top 10 Minimal and Elegant Android News Reader Apps. Retrieved October 11, 2011, from Android Appstorm: http://android.appstorm.net/roundups/lifestyle-roundups/top-10-minimal-and-elegant-android-news-reader-apps/Kim, J. G., & Cho, J.-D. (2010, February 7-10). Huffman user interface for full touch screen based mobile phones. Advanced Communication Technology (ICACT) , pp. 1021 1026.Lam, W., Cheung, P., & Huang, R. (2004). Mining Events and New Name Translations From Online Daily News. JCDL04. Tucson, Arizona, USA.Li, L., Wang, D., & Li, T. (2011). SCENE: A Scalable Two-Stage Personalized News Recommendation System. SIGIR11. Beijing, China.Li, Z., Wang, B., Li, M., & Ma, W. (2005). A Probabilistic Model for Retrospective News Event Detection. SIGIR05. Salvador, Brazil.Lonczak, J. (2011, January 27th). AndroidTapp. Retrieved Febuary 2012, 2012, from Pulse News Reader: http://www.androidtapp.com/pulse-news-reader/Mahil, C., & June, V. (n.d.). Prototyping. Prototyping and Software Development Approaches , pp. 2 - 13.Maji, A., Hao, K., Sultana, S., & Bagchi, S. (2010). Characterizing Failures in Mobile OSes : A Case Study with Android and Symbian. IEEE 21st International Symposium on Software Reliability Engineering .Naik, P. (2011). Smartphone OS Comparison. Retrieved from http://www.techtree.com/India/Features/Smartphone_OS_Comparison/551-114322-899.htmlPhuvipadawat, S., & Murata, T. (2010, Aug. 31 - Sept. 3). Breaking News Detection and Tracking in Twitter. Web Intelligence and Intelligent Agent Technology (WI-IAT) , pp. 120 123.Proffitt, B. (2011). Open Android-For better and for worse [Tools & Toys]. Spectrum, IEEE 2011 , 22 24.QSQA. (2009). SDLC Models. QSQA , 1 - 26.Radev, D., Otterbacher, J., Winkel, A., & Blair-Go. (2005). NewsInEssence: Summarizing Online News Topics. Communications of the ACM , Volume 48 Issue 10.Reece, J. (2007). Rapid Application Development. School of Computing, University of Wolverhampton.Song, M., Song, H., & Fu, X. (2011, July 26-28). Methodology of user interfaces design based on Android. Multimedia Technology (ICMT), 2011 International Conference , pp. 408 411.Su, K., Chan, D., & Chan, F. (2005, November 15-17). Navigation on Mobile News. Mobile Technology, Applications and Systems, 2005 2nd International Conference , p. 6.Xia-Xia, Y., & Yan-Hui, W. (2010, October 29-31). Design and Implementation of Input Method based on Embedded Multimedia Mobile Device. Multimedia Technology (ICMT) , pp. 1 - 3.Yang, Y., Carbonell, J., Brown, R., Pierce, T., Archibald, B., & Liu, X. (1999, July - August). Learning approaches for detecting and tracking news events. Intelligent Systems and their Applications , pp. 32 43.