1. Website Oleh : Haris Munandar, ST., M.Ti PT. Solusi Sentra Mandiri

2. Definisi-Website (What?) Cara untuk merepresentasikan diri, merupakan tempat di internet yang bisa dikunjungi oleh siapapun, dimanapun dan kapanpun serta tempat berinteraksi.

3. Mengapakitamemerlukan website?(Why?) • Cepat • Murah • Mudah • Menyenangkan • Efektif • Efisien

4. SetelahAndamempunyai website,So what? • Membuat pengumuman • Memberikan pelayanan kepada masyarakat • Menerima masukan dari masyarakat • Membagi dan mendistribusikan dokumen • Berkomunikasi langsung dengan masyarakat • Memberikan informasi kepada masyarakat

5. Bagaimanacaramembuat website?(How?) Anda membutuhkan: • Alamat website  Nama Domain • Jasa Server  Jasa Web Hosting

6. Domain • gTLD • .com • .net • .org • .biz • .name • .asia • ccTLD • .us • .in • .cn • .eu • .cc • .web.id • .or.id • .co.id • .sch.id • .ac.id • .go.id • .net.id • .mil.id

7. Tips memilih web hosting • Fitur dan kapasitas yang ditawarkan • Harga yang ditawarkan • Proses aktivasi • Layanan konsumen • Periksa hardware dan jaringan • Resiko

8. Membangun Website

11. Process Product Project Plan System Proposal System Specification New System and Maintenance Plan Planning Analysis Design Implementation Processes and Deliverables

12. Proscesses • Planning • Why build the system? • How the project team will go to build it? • Analysis • Who, what, when, where will the system be? • Design • How will the system will operate, in terms of the hardware, software and infrastructure? • Implementation • The system is actually built or purchased • System delivery

13. Planning • Project Initiation • Identifying business value (how will the IS lower costs or increase revenue ?) • A system request presents a brief summary of business need, and explain how the system will create business value • Analyze feasibility (technical, economic and organizational) • Project Management • Develop work plan • Staff the project • Control and direct project

14. Technical Feasibility: Can We Build It? • Familiarity with application • Knowledge of business domain • If analysts are unfamiliar with the business application area, they have a greater chance of misunderstanding the users or missing opportunities for improvement. • Familiarity with technology • Extension of existing firm technologies • Project size • Number of people, time, and features • Compatibility with the existing technology

15. Economic Feasibility: Should We Build It? • Development costs • Annual operational costs • Annual benefits • Intangible costs and benefit

16. Organizational Feasibility: If we build it, will they come? • There are two ways to assess: • How well the goal of the project align with business objectives • Strategic alignment  the fit between the goals of the project and business strategy • Stakeholder analysis • Project champion(s) • A high-level non-IS executive who is usually but not always the person who created the system request. • Organizational management • System users

17. Analysis • Analysis Strategy • Analysis current system and new system (to-be system) • Requirement gathering • Interview or questionaires or other method • Analysis Model (Process and Data) • System Proposal • Describe what business requirements of the new system should met.

18. Design • Design Strategy • Build it, outsource or buy ? • Architectural & Interface Design • Describe h/w, s/w, network infrastructure • How the users will move through the system • Database and file specification • Program design

19. Implementation • System Construction: The system is built and tested to make sure it performs as designed. • Installation: Prepare to support the installed system. • Support Plan: Includes a post-implementation review.

20. Tips membangun website • Memilikitujuan yang jelas • Kenali audience Anda • Gunakan item yang bisadi Download secaracepat • Buat website Andamenariksecara virtual • Tatalah “isi” dengancara yang cerdas • Petakanarusinformasipadakertassebelummembangun website • Ujialah website Andasecarakeseluruhan

21. Desain Website Yang Baik

22. Desain website yang baik (1) • Kecepatandownloadadalah "kriteriadesainutama". Jadijangansampaiusermenjadisangatamat lama mendownloadhanyakarenasuatusimbolsaja. Hindaripenggunaangambar/image yang tidakperlu. Jika image /gambarfungsinyabisadigantikantext, sebaiknyamenggunakan text. • Mekanisme "search" sangatperluuntuk site yang memilikilebihdari 200 halaman. • Struktur yang baik, sertanavigasi yang mudah. • Sebisamungkinmenghindariscrolling.

23. Desain website yang baik (2) • Isi informasi adalah "raja". Artinya isi adalah lebih penting daripada tempelan seperti logo yang beranimasi, bahkan text yang scrolling bisa mengganggu user. • Jadikan website Anda menjadi suatu kebutuhan informasi bagi pengakses, dan sebaiknya Anda perlu memikirkan penampilan pertama Anda.

24. Desain website yang baik (3) • Usahakandesainwebsite Andastandar agar bisamenjangkaunetterluas. ApabilaAndamempunyaitarget audiencetersendiri, makaAndabisamenambahkannilailebihpadawebsiteAndamisalnyamenggunakantechnologi ActiveX, Shockwave, Java,dll. Selamainibanyakbrowser yang menampilkansuatuwebsitedenganberbeda. Browsersepertihalnyakacamataataualatuntukmelihatinformasi, namunsaatiniadaperbedaanstandarisasibrowser.

25. Pemeliharaan Website

26. Pemeliharaan Website (1) • Update Data • Monitoring • Manage Email Account • Reporting • JumlahPengunjung • Jumlahaktifitas update • Kondisipemakaian space • Daftar email terkini • Jumlahkomentardikotakpesan

27. Plus - Minus

28. SistemOperasi • Linux VS Windows • Huruf besar-kecil • Perbedaan path • Perbedaan konfigurasi PHP • Perbedaan konfigurasi MySQL • Script ASP menggunakan sistem operasi windows

29. Program • PHP – MySQL – CMS (Joomla, Mambo) • Open source  gratis • Ketersediaan jaminan belum pasti • ASP - ORACLE • Berbayar • Ketersediaan jaminan pasti

30. Hal Yang PerluDiperhatikanOleh User

31. Service Level Agreement (SLA) • Kejelasan peraturan antara penyedia jasa dan user • Diskusi finansial • Informasi • Flexibility

32. Sekilas Info • Generasi Web 1.0 • Generasi Web 2.0 • Generasi Web 3.0 • CMS (Content Manajement System)

33. Your Turn • If you were building a web-based system: • What is the business need? • What would be the business requirements? • What would be the business value (tangible and intangible)? • What special issues or constraints would you foresee?

34. REVIEW