<div style='background-color: none transparent;'><a href='http://www.rsspump.com/?web_widget/rss_ticker/news_widget' title='News Widget'>News Widget</a></div>

Me And My Angel

Dia melangkah kecil ke utara selatan,kadang berlari, kadang melambaikan tangan seolah diminta mendekat dan akhirnya ketika dekat dia berlari(mungkin dalam fikirannya: "abiy ayo main kejar kejaran", dalam hatiku : "siap yah abiy kejar")

Me And My Angel

Khonsa tau tidak?siapa yang menciptakan hamparan ombak dilautan?"Allah". Tau sekarang ombak itu sedang melakukan apa?"Bertasbis memuji keagungan Allah". Pinter...

Me And My Angel

Khonsa tau tidak?siapa yang menciptakan hamparan ombak dilautan?"Allah". Tau sekarang ombak itu sedang melakukan apa?"Bertasbis memuji keagungan Allah". Pinter...

Jasa pembuatan Sistem Informasi

Kami menerima jasa pembuatan sistem informasi berbasis pemrograman PHP dan menggunakan database MySQL serta keamanannya menggunakan algoritma enkripsi yang disesuaikan kebutuhan pengguna

Produk Kami

Kami juga menyediakan berbagai macam produk seperti: Alat Peraga Pendidikan semisal Magic Disk dan permainan untuk balita batita, Kuliner ala Merapi semisal buah salak, Perlengkapan bayi semisal pampers, Kebutuhan Rumah Tangga semisal clean ball yang hebat dll

Rabu, 29 Agustus 2012

Konversi Acces ke MySql

Bagi seorang programmer, salah satu hal yang membuat repot adalah ketika menjumpai permintaan menggunakan database yang berbeda. Misal data suatu perusahaan ingin membuat sistem informasi dengan menggunakan MySql, setelah berjalan ternyata data yang dia punya berupa Acces, maka mau tidak mau programmer harus mengkonversi data tersebut ke MySql dan atau sebaliknya.

Berikut Tips untuk mengubah dari Acces ke MySql :
1. Download program bernama "bullzip" di Sini.
2. Install program tersebut dan jalankan untuk percobaan. Untuk menjalankan lakukan langkah-langkah mudah berikut:
a.  Pastikan program sudah berjalan kemudian klik "next". Tanda program berjalan bila muncul gambar berikut :

b. Cari source data acces yang akan dikonversi ke MySql, jika acces anda menggunakan password maka masukkan passwordnya dan jika tidak tinggal klik "next".

c. Masukkan username(defaultnya : "root") dan password untuk verifikasi ke Sql anda, serta pada "destination database" masukkan alamat tujuan yang akan anda konversikan.

d. Mana table yang akan anda pilih untuk dikonversikan, kemudian klik "next".


Sederhana bukan???

Rabu, 15 Agustus 2012

Serangan Yang Membawa Harapan (Kemampuan Tobi)

Pertarungan Naruto, ALis Tebal, Bee dan Hatake Kakashi melawan Tobi(Manusia bertopeng) sudah mulai terlihat hasilnya. Analisa yang dilakukan Kakashi terhadap kemampuan yang dimiliki oleh Tobi mulai menampakkan hasil dimana naruto dan rekans sudah mampu melukai Tobi yang memiliki kemampuan khusus yang membuat bingung Naruto dan Tim.

Rabu, 11 Juli 2012

Me and My Angel

Ada kisah yang sering disampaikan oleh Ust. Cahyadi Takariwan dalam beberapa kesempatan bertemu dengan beliau  "Akhi beberapa ikhwah sering dikomplain oleh anaknya, "kok abiynya jarang pulang sih, siang sibuk bekerja, malam keluar lagi, sabtu ahad keluar kota dsb"....". (Nasehat bagi para orang tua).

Hari minggu,disela-sela acara outbond anak yatim yang bertempat di pantai gua cemara bantul...sy dan putri tercinta menikmati indahnya pantai dan rimbunnya pohon cemara di wilayah selatan Jogjakarta. Senyum kecil dan keceriaan di rona wajahnya menunjukkan bahwa dia begitu sangat menikmati buaian angin pantai dan gulungan ombak yang menari tepat didepan matanya yang kecil. Dia melangkah kecil ke utara selatan,kadang berlari, kadang melambaikan tangan seolah diminta mendekati dan akhirnya ketika didekati dia pasti lari(mungkin dalam fikirannya: "abiy ayo main kejar kejaran", dalam hatiku : "siap yah abiy kejar") -- itulah kebiasaan putri kecilku.


Satu hal yang selalu kami ajarkan kepadanya "Tidak boleh ada rasa takut kepada apapun, takut hanya kepada Allah saja". Kugendong dia mendekati pantai,awalnya takut kuajak bermain dengan air, tapi akhirnya lama kelamaan dia begitu sangat menikmati sentuhan lembut air pantai di sela-sela jemarinya. Tawa riang kami berdua memecah kebisingan deru ombak besar pantai selatan, "Ombak besar ayo kesini...,ni khonsa mau bermain dengan mu",seruku.


"Sketsa catatan harian abiy"

Rabu, 27 Juni 2012

Hasil Lengkap Perempat Final Euro 2012 "True Competition" (Spain Vs Portugal & Jerman Vs Italia)

Donetsk - Setelah melewati 90 menit waktu normal dan dua kali extra time, akhirnya Spanyol mampu melaju ke final Piala Eropa 2012 usai menundukkan Portugal lewat adu penalti dengan skor 4-2.

Dalam laga yang dihelat di Donbass Arena, Kamis (28/6/2012) dinihari WIB, baik Spanyol dan Portugal bermain tanpa gol di babak pertama dan kedua plus 2x15 menit perpanjangan waktu.

Akhirnya laga harus diselesaikan lewat adu penalti. Di babak tos-tosan, dua penendang Portugal gagal menunaikan tugas sementara hanya Xabi Alonso yang gagal dari kubu Spanyol.

Sepakan Cesc Fabregas akhirnya mengirimkan Spanyol ke final kedua beruntun, setelah empat tahun lalu mereka jadi juara. Di final, La Furia Roja akan menghadapi pemenang laga Jerman kontra Italia.

Jalannya pertandingan

Portugal ambil inisiatif serangan di menit-menit awal dan mereka mendapat sepak pojok di menit ke-2. Eksekusi Miguel Veloso nyaris menjebol gawang andai Iker Casillas tak menepis bola.

Spanyol baru bisa mendapat peluang pertamanya di menit ke-9. Diawali pergerakan Andres Iniesta, bola berhasil mencapai kaki Alvaro Negredo yang kemudian menyodorkan ke Alvaro Arbeloa. Bola lantas disepak namun masih melayang tipis di atas gawang Rui Patricio.

Portugal berhasil membuat Spanyol kesulitan mengembangkan permainannya dan lebih banyak memainkan bola-bola panjang, yang bukan ciri khas Spanyol.

Satu peluang lagi didapat Spanyol di menit 29 ketika Iniesta yang mendapatkan bola di sisi kanan pertahanan Portugal melepaskan sepakan melengkung ke tiang jauh, tapi sayang masih tak menemui sasaran.

Ronaldo! Kapten Portugal di menit 31 nyaris menjebol gawang Spanyol. Mendapat bola di depan kotak penalti, sepakan kerasnya masih menyamping di sisi kiri gawang.

Tak ada lagi peluang hingga berakhirnya babak pertama dan skor 0-0 pun mengirim kedua tim memasuki ruang ganti.

Babak kedua dimulai kedua tim masih belum bisa membuat peluang berbahaya di depan gawang gawang.

Peluang pertama on target hadir di menit 67 ketika Xavi Hernandez yang menggiring bola hingga mendekati kotak penalti melepaskan sepakan keras tapi masih tepat di pelukan Rui Patricio.

Portugal mendapat tendangan bebas di jarak sekitar 40 meter dari gawang Spanyol di menit 70. Ronaldo menyepak keras-keras bola namun masih melayang di atas mistar Casillas.

Di menit 89 Portugal mendapat peluang emas lewat sebuah counter attack. Ronaldo mendapat bola terakhir dari rekannya. Berada cukup bebas di sisi kanan, sepakan Ronaldo melambung jauh dari gawang.

Kembali tak ada gol yang tercipta di babak kedua ini hingga laga harus berlanjut ke extra time. 2x15 menit.

Iniesta! Di menit 103 gelandang lincah itu punya peluang emas di depan gawang. Mendapat umpan dari Alba, Iniesta langsung menyepak bola dan ditepis oleh Patricio.

Spanyol mendapat peluang mencetak gol dua menit setelahnya dari situasi bola mati. Free kick Sergio Ramos dan bola disepaknya keras tapi masih melayang tipis di atas mistar.

Di 15 menit kedua perpanjangan waktu pun tak ada gol yang tercipta meskipun Spanyol mampu menguasai jalannya laga. Alhasil laga harus ditentukan melalui adu penalti.

Di fase ini Spanyol akhirnya menang 4-2 setelah tembakan Cesc Fabregas dari titik putih menjebol gawang Patricio setelah sebelumnya membentur tiang dalam.

Susunan pemain

Portugal: Rui Patricio, Pereira, Pepe, Bruno Alves, Coentrao, Veloso (Custodio 105'), Meireles, Moutinho, Nani, Cristiano Ronaldo, Almeida (Oliveira 80')

Spanyol: Casillas, Arbeloa, Ramos, Piqué, Jordi Alba, Busquets, Xabi Alonso, Xavi (Pedro 86'), Iniesta, Silva (Navas 60'), Negredo (Fabregas 53')

Selasa, 19 Juni 2012

Analisa, Evaluasi dan Hasil Lengkap Babak Penyisihan Grup EURO 2012

Sudah hampir 2 pekan perhelatan akbar EURO 2012 berlangsung di Ukraina dan Polandia. Perhelatan ini akan menentukan siapakah sebenarnya Kings Of Europe(Raja Bola eropa) tahun ini. Evaluasi EURO 2012 menyisakan banyak momen yang tak terlupakan, analisa yang diluar banyak dugaan, kesedihan yang mendalam, serta beberapa keputusan wasit yang menurut penulis kontroversial.

Analisa diluar dugaan
Sejak awal grup A yang ditempati oleh Rusia, Polandia, Cekoslowakia, dan Yunani ini para analis menempatkan dan menjagokan Rusia sebagai pemenang dari grup ini, dan terbukti sejak 2 kali pertandingan awal Rusia membuktikan analisa itu dengan memberikan bukti bahwa Rusia sebagai raja grup, tetapi ternyata analisa itu salah ketika di akhir pertandingan Rusia harus menelan kekalahan ketika dipencundangi Yunani yang bisa dikatakan sebagai tim underdog.

Belanda Yang Menyedihkan
Hampir semua pengamat bola sepakat bahwa yang akan keluar ke babak selanjutnya adalah Jerman dan Belanda iika dilihat dari pemain kedua tim yang sudah ditunjukkan bersama klub masing masing. Dan diluar dugaan, Belanda tersingkir dengan sangat memalukan tanpa meraih satu poin pun dalam semua pertandingan alias Kalah Telak.

Berikut Hasil Lengkap Babak Penyisihan Grup EURO 2012 :

Group A
Win
Draw
Lose
F - A
Point
Czech Republic
2
0
1
4 - 5
6
Greece
1
1
1
3 - 3
4
Russia
1
1
1
5 - 3
4
Poland
0
2
1
2 - 3
2
Group B
Win
Draw
Lose
F - A
Point
Germany
3
0
0
5 - 2
9
Portugal
2
0
1
5 - 4
6
Denmark
1
0
2
4 - 5
3
Netherlands
0
0
3
2 - 5
0
Group C
Win
Draw
Lose
F - A
Point
Spain
2
1
0
6 - 1
7
Italy
1
2
0
4 - 2
5
Croatia
1
1
1
4 - 3
4
Republic of Ireland
0
0
3
1 - 9
0
Group D
Win
Draw
Lose
F - A
Point
England
2
1
0
5 - 3
7
France
1
1
1
3 - 3
4
Ukraine
1
0
2
2 - 4
3
Sweden
1
0
2
5 - 5
3

Skema Perempat Final :

Download Soal dan Pembahasan Ujian Poltekkes DepKes 2012

Di Indonesia, seseorang yang ingin masuk ke lingkungan pendidikan tinggi harus melewati lagi serangkaian tes yang diadakan oleh pendidikan tinggi tersebut, baik lingkungan PTN, PTS, dan Kedinasan dengan tingkat kesulitan yang berbeda-beda antara ujian satu dan yang lainnya.

Hal tersebut dilakukan karena instansi pendidikan tinggi belum sepenuhnya percaya terhadap hasil UNAS di tingkat SMU/SMK/MA.

Atas dasar pertimbangan di atas, maka pada postingan kali ini, kami akan membuat pembahasan terkait ujian masuk Politeknik Kesehatan Departemen Kesehatan tahun 2012. Berikut pembahasanannya, dan semoga bermanfaat.



Download Soal dan Pembahasan

Minggu, 17 Juni 2012

Software Project Planning (Software Project Management)

History
Companies quickly understood the relative ease of use that software programming had over hardware circuitry, and the software industry grew very quickly in the 1970s and 1980s.
To manage new development efforts, companies applied proven project management methods, but project schedules slipped during test runs, especially when confusion occurred in the gray zone between the user specifications and the delivered software. To be able to avoid these problems, software project management methods focused on matching user requirements to delivered products, in a method known now as the waterfall model. Since then, analysis of software project management failures has shown that the following are the most common causes:
  1. Unrealistic or unarticulated project goals
  2. Inaccurate estimates of needed resources
  3. Badly defined system requirements
  4. Poor reporting of the project's status
  5. Unmanaged risks
  6. Poor communication among customers, developers, and users
  7. Use of immature technology
  8. Inability to handle the project's complexity
  9. Sloppy development practices
  10. Poor project management
  11. Stakeholder politics
  12. Commercial pressures
The first three items in the list above show the difficulties articulating the needs of the client in such a way that proper resources can deliver the proper project goals. Specific software project management tools are useful and often necessary, but the true art in software project management is applying the correct method and then using tools to support the method. Without a method, tools are worthless. Since the 1960s, several proprietary software project management methods have been developed by software manufacturers for their own use, while computer consulting firms have also developed similar methods for their clients. Today software project management methods are still evolving, but the current trend leads away from the waterfall model to a more cyclic project delivery model that imitates a Software release life cycle.

Software development process

A software development process is concerned primarily with the production aspect of software development, as opposed to the technical aspect, such as software tools. These processes exist primarily for supporting the management of software development, and are generally skewed toward addressing business concerns. Many software development processes can be run in a similar way to general project management processes. Examples are:
  • Risk management is the process of measuring or assessing risk and then developing strategies to manage the risk. In general, the strategies employed include transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or all of the consequences of a particular risk. Risk management in software project management begins with the business case for starting the project, which includes a cost-benefit analysis as well as a list of fallback options for project failure, called a contingency plan.
  • A subset of risk management that is gaining more and more attention is Opportunity Management, which means the same thing, except that the potential risk outcome will have a positive, rather than a negative impact. Though theoretically handled in the same way, using the term "opportunity" rather than the somewhat negative term "risk" helps to keep a team focused on possible positive outcomes of any given risk register in their projects, such as spin-off projects, windfalls, and free extra resources.
  • Requirements management is the process of identifying, eliciting, documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. New or altered computer system[1] Requirements management, which includes Requirements analysis, is an important part of the software engineering process; whereby business analysts or software developers identify the needs or requirements of a client; having identified these requirements they are then in a position to design a solution.
  • Change management is the process of identifying, documenting, analyzing, prioritizing and agreeing on changes to scope (project management) and then controlling changes and communicating to relevant stakeholders. Change impact analysis of new or altered scope, which includes Requirements analysis at the change level, is an important part of the software engineering process; whereby business analysts or software developers identify the altered needs or requirements of a client; having identified these requirements they are then in a position to re-design or modify a solution. Theoretically, each change can impact the timeline and budget of a software project, and therefore by definition must include risk-benefit analysis before approval.
  • Software configuration management is the process of identifying, and documenting the scope itself, which is the software product underway, including all sub-products and changes and enabling communication of these to relevant stakeholders. In general, the processes employed include version control, naming convention (programming), and software archival agreements.
  • Release management is the process of identifying, documenting, prioritizing and agreeing on releases of software and then controlling the release schedule and communicating to relevant stakeholders. Most software projects have access to three software environments to which software can be released; Development, Test, and Production. In very large projects, where distributed teams need to integrate their work before release to users, there will often be more environments for testing, called unit testing, system testing, or integration testing, before release to User acceptance testing (UAT).
  • A subset of release management that is gaining more and more attention is Data Management, as obviously the users can only test based on data that they know, and "real" data is only in the software environment called "production". In order to test their work, programmers must therefore also often create "dummy data" or "data stubs". Traditionally, older versions of a production system were once used for this purpose, but as companies rely more and more on outside contributors for software development, company data may not be released to development teams. In complex environments, datasets may be created that are then migrated across test environments according to a test release schedule, much like the overall software release schedule.

Project planning, monitoring and control

The purpose of project planning is to identify the scope of the project, estimate the work involved, and create a project schedule. Project planning begins with requirements that define the software to be developed. The project plan is then developed to describe the tasks that will lead to completion.
The purpose of project monitoring and control is to keep the team and management up to date on the project's progress. If the project deviates from the plan, then the project manager can take action to correct the problem. Project monitoring and control involves status meetings to gather status from the team. When changes need to be made, change control is used to keep the products up to date.

Issue

In computing, the term issue is a unit of work to accomplish an improvement in a system. An issue could be a bug, a requested feature, task, missing documentation, and so forth. The word "issue" is popularly misused in lieu of "problem." This usage is probably related.[citation needed]
For example, OpenOffice.org used to call their modified version of BugZilla IssueZilla. As of September 2010, they call their system Issue Tracker.
Problems occur from time to time and fixing them in a timely fashion is essential to achieve correctness of a system and avoid delayed deliveries of products.

Severity levels

Issues are often categorized in terms of severity levels. Different companies have different definitions of severities, but some of the most common ones are:
Critical
High
The bug or issue affects a crucial part of a system, and must be fixed in order for it to resume normal operation.
Medium
The bug or issue affects a minor part of a system, but has some impact on its operation. This severity level is assigned when a non-central requirement of a system is affected.
Low
The bug or issue affects a minor part of a system, and has very little impact on its operation. This severity level is assigned when a non-central requirement of a system (and with lower importance) is affected.
Cosmetic
The system works correctly, but the appearance does not match the expected one. For example: wrong colors, too much or too little spacing between contents, incorrect font sizes, typos, etc. This is the lowest severity issue.
In many software companies, issues are often investigated by Quality Assurance Analysts when they verify a system for correctness, and then assigned to the developer(s) that are responsible for resolving them. They can also be assigned by system users during the User Acceptance Testing (UAT) phase.
Issues are commonly communicated using Issue or Defect Tracking Systems. In some other cases, emails or instant messengers are used.

Philosophy

As a subdiscipline of project management, some regard the management of software development akin to the management of manufacturing, which can be performed by someone with management skills, but no programming skills. John C. Reynolds rebuts this view, and argues that software development is entirely design work, and compares a manager who cannot program to the managing editor of a newspaper who cannot write.[3]

Non Determinisme (NFA Vs DFA) ~ Teori Komputasi

Menerima: jika terdapat paling sedikit satu path yang berakhir di state Final di pohon trace eksekusi.
Menolak: jika semua path yang mungkin “terhenti” (stuck, halt) atau berakhir di state yang bukan Final.
Interpretasi:
  1. NFA selalu mengambil pilihan yang benar untuk memastikan penerimaan (asumsi: path yang berakhir di state Final memang ada),
  2. NFA membuat copy dirinya sendiri untuk menelusuri semua path yang mungkin,
  3. NFA menjelajahi semua path secara parallel.
Untuk lebih lengkapnya silakan baca slide di bawah ini :
Tk Slides01

Senin, 11 Juni 2012

Download Kunci dan Pembahasan SNMPTN 2012 Terbaru


Silakan Download kunci dan pembahasan SNMPTN 2012 di link di bawah ini :

Kunci Jawaban Matematika Dasar Kode Soal 724
No
Jawaban

No
Jawaban

No
Jawaban
1
D
6
B
11
D
2
C
7
A
12
C
3
D
8
A
13
D
4
D
9
C
1
B
5
A
10
E
15
B

Kunci Jawaban Matematika Dasar Kode Soal 723
No
Jawaban

No
Jawaban

No
Jawaban
1
D
6
B
11
E
2
C
7
A
12
B
3
D
8
D
13
E
4
A
9
C
1
E
5
D
10
B
15
A

Kunci Jawaban Matematika Dasar Kode Soal 421
DOWNLOAD FILE
No
Jawaban

No
Jawaban

No
Jawaban
1

6

11

2

7

12

3

8

13

4

9

1

5

10

15


Note : 
  • Untuk kode soal yang lain silakan di kirim ke email : indrajs_alquds@yahoo.com. Insya Allah secepatnya akan kami buatkan pembahasan.
  • Password seperti biasanya .:. Jika tidak/Belum tau sms ke nomer hp sy atau silakan tinggalkan pesan beserta alamat email.

By : Indra Juniarma S
Terima Kasih

Related Posts Plugin for WordPress, Blogger...