Heute ist es soweit, Gert Heidenreich ist zu Gast auf der 50. Bücherschau in München.

Seine Autorenlesung zu seinem neuesten Buch: „Fest der Fliegen“ findet in der Black Box um 19.00 Uhr statt.

Gert Heidenreich bekannt als Schriftsteller, Journalist, Regisseur und Dramaturg wurde u.a. 1986 mit dem Adolf-Grimme-Preis ausgezeichnet. 1990 folgte der Literaturpreis der Stadt München. Seine Veröffentlichungen umfassen zahlreiche Romane, Gedichte, Essays und verschiedenste Theaterstücke.

Gert Heidenreichs großartige Stimme ist auf den verschiedensten Hörbuchproduktionen zu finden, u.a. lieh er seine Stimme den Tolkin-Hörbüchern DIE ZWEI TÜRME , DIE WIEDERKEHR DES KÖNIGS & DER HOBBIT.

Auf der Frankfurter Buchmesse trafen wir Gert Heidenreich zu einem Interview.

Weitere Autoreninterviews und Berichte von der Frankfurter Buchmesse: hier

Bom pra quem é fã de Need for Speed como eu que está sempre atrás de novidades desse grande sucesso da EA , ja pode se prepara pois não deve demorar mto para o lançamento final de Need for Speed online ,este terá estilo MMO, as configurações da tela de jogo visam favorecer as particularidades do PC — já que, como já é bem sabido no momento, o título não deve aparecer nos consoles tão cedo. Segundo o produtor Scott Henshaw, “a chave para o conceito de NFS World Online é a interface com o usuário, que foi desenvolvida a partir do zero para levar vantagem com a arquitetura do PC”.

Descrição do game que traduzi no site da EA.com

Need for Speed Mundo on-line para o PC é a maior  Game de mundo de Need for Speed, com uma lista extensa de carros licenciados e modos de jogo – tudo em um ambiente online multiplayer.

Os jogadores irão competir, comparar e colaborar no clássico Need for Speed modos, bem como thrilling novos eventos, a fim de adquirir e personalizar seus carros de sonho. Need for Speed mundo online é uma nova experiência de entretenimento que oferece excelente jogabilidade, gráficos impressionantes, sofisticados e recursos on-line que enfatizam a interação social entre os jogadores.
Mundo Online irá iniciar o processo de beta neste inverno e será aberto a jogadores de todo o mundo no outono de 2010. Need For Speed World Online é um jogo de computador multiplayer desenvolvido em conjunto pela Black Box, o desenvolvedor da franquia Need for Speed, e em estúdio da EA em Cingapura.

No dia 05/10, a EA Taiwan inicio de uma nova fase de testes para o Need for Speed World Online que deve permanecer ativa até o dia 14 deste mesmo mês. O Open Beta é exclusivo para usuários orientais previamente cadastrados e tem como objetivo testar um novo patch que implementará algumas correções no cliente do jogo.De acordo com a EA Taiwan, este patch deverá solucionar problemas encontrados pelos usuários durante o primeiro Open Beta como perdas de conexão com o servidor, logoffs aleatórios e lentidão.

Na minha opnião este game tem tudo para dar certo,no video poremos ver boa qualidade de graficos e a maior interatividade trazida de MMO vai dar um ar a mais no jogo!

E agora pra finalizar confira o trailer de Need For Speed online.

by Shadow Wave:

©2009 Ben Cadwallader:

Today is the day that many gamers will wake up with a knife in their hand, the day they speak with a foreign accent and the day that they will sit on a bench with people they do not know.

Sound vaguely familiar?

Well it should, Assassins Creed 2 is out today!

It’s the day many Assassins Creed players have been waiting for: a chance to finally understand that ‘WTF’ ending of the original title! And maybe learn a bit more about Desmond and his Animus adventures.

And while Assassins Creed is out today, and I’m sure it’s selling very well, there is a special version that comes with an additional $50 on the price tag that sold out here in Australia well before release.

The Black Edition:

1. Rare “Master Assassin” Ezio Figurine
2. 3 in-game bonus quests
3. Conspiracy Book (its an art book)
4. Game Soundtrack
5. All inside a sleek black box

Let’s open her up shall we?

1) The black box: I’m sure most people will notice when they pick theirs up how light the box feels to hold. This could be bad….

In Depth Impression:

The most alarming thing about this is that the entire package is so light weight, and as it turns out the figurine is not a statue. It’s not made of hard plastic, it’s made of a kind of a squishy, flexible/soft plastic.

And while the detail of the figurine is quite good when placed on a shelf, it does feel very cheap to hold… especially when you’ve paid quite a premium cost for it.

You can bend his sword with your finger etc., the stand on my figure does not sit flat so there is a slight wobble on both sides, and though it’s nothing huge it once again adds to that feeling of cheapness.

I guess the value of this figurine will depend on the eye of the beholder. It looks good, but it feels cheap. It’s a good size, but it could break easily. I personally think I would have preferred a higher quality plastic or metal with the size of the figurine sacrificed just a bit.

The art book is very nice. It’s leather wrapped, and has a lot of pages of art, and if you’re a fan of art books this is one of the best art books I have seen for a long time.  It feels classy and is detailed enough to maybe make the extra price tag worth it for you, if that’s your thing.

The bonus DVD has yet to be tested, looks a bit gimmicky, so not getting my hopes up for whenever I get around to testing it.  The cardboard case is very dodgy- it’s scratched the disc up a little, and I have had the disc fall out multiple times already as it sits very loose in there.  Be careful when you open yours!

The bonus In-Game Quests are simply redeemed in the games’ redemption system which simply unlocks the content that is already on the disc.

Finally, I was disappointed that the actual game itself is the same as the  standard edition.  For all this ‘Black Edition’ I don’t get why we didn’t get a black box art or tin or something. It feels very dodgy that they just threw in the standard edition with a white cover and everything.

It would have been great to see something that showed what collector’s edition you had.  I honestly would have hoped for a tin case to go along with my Assassins Creed 1 case.

Overall, this collectors edition is a mixed bag, and I think its value will be determined by each person as it has its ups and downs.  The best thing by far in this black box is its art book, full of detail.

The figurine I think some will love and some won’t be impressed by its flexible plastic etc.  And finally, I think the rest of people will just want to play the damn game.

If we are talking about full RRP prices I’m willing to say that the extra $50 on the price tag (it cost AUD$150) might be worth it depending on who you are.

But in Australia, if you take into account the price of the standard edition which is on sale for as low as AUD$78, and the fact the Black Edition is an EB Games Exclusive, which means there is no price matching available,  it makes the Black Edition potentially up to $72 more expensive than the standard edition…

So is this worth it you? Your comments and thoughts in the box below.

©2009 Ben Cadwallader

• Other games in genre at discount $’s for ALL OXCGN readers + Bonus Points

Conheça antes…

Gostou?Então comenta!
O seu comentário é muito importante!

André Diogo

A mechanic in Redditch lived the Ferris Bueller dream when a customer left a high power car for a service. While admittedly not a Ferrari, the cheeky grease monkey managed to get it up to 125mph when he took it for a spin round the local area. Unfortunately, the owner had a black box camera system, his high speed trip round the A435 is now on YouTube.

This story may seem like science fiction, but we assure you the details are real. FN Herstal has created a new electronic device, appropriately named the “Black Box”, which can record and store a rifle’s round count and firing sequences. In addition, the FN Black Box contains digital identifiers for the weapon. This means that, when coupled to a GPS, the FN Black Box can transmit the gun’s ID and location to a military command or other monitoring authority.

Black Box Technology Limited to Military… For Now
The technology is exciting, though the ramifications for gun control are chilling to say the least. At present, FN Herstal envisions its Black Box as an add-on for military or law enforcement weapons. No one has yet suggested that black boxes be fitted to civilian arms.

The FN Black Box can record multiple types of firing data: round count, burst rates, burst lengths, and firing sequences. The digital sensors can even detect stoppages due to failures to cycle. FN evisions that this information can alert armorers when weapons require maintenance. In addition, by tracking the numbers of rounds fired, military commanders can determine when ammunition resupply is required or when barrels need replacement.

The Say Uncle Blog notes that while this kind of digital recorder may seem novel for weapons, “the same concept is often applied to industrial machines”, allowing factory owners to optimize maintenance schedules.

It there a black box in your future? We don’t see much application for Benchrest or High Power events, but this kind of round counter might prove useful in speed shooting disciplines. We do worry about the potential application of “black box” technology to defensive firearms. The digital records of shots fired as well as the sequence of those shots could be used as evidence in trials of gun owners. Imagine being on trial and having your testimony “impeached” by a digital chip removed from your gun.

Es ist nicht nur der Betonklotz, der mich an dieser Stadt stört.

Mich stört Vieles dort.

Kein Stören im Sinne von, dass ich es nicht mag.

Stören im Sinne von bedrohlich wirken.

Mir macht diese Stadt Angst.

Früher war sie schön.

Und ich mochte sie gern.

Dann sind Dinge passiert, die verbinde ich heute damit.

Peng!

Unter anderem.

Ich weiß nicht ob das Geräusch wirklich so beschrieben werden kann.

Ist schon gut so.

Ich bin nicht gern alleine unterwegs in dieser Stadt.

Ich mag es nicht in ihr allein irgendwo sein und auf etwas oder jemanden warten.

Ich mag es nicht wenn Menschen in ihr mich ansehen oder mich ansprechen.

Das stört mich allerdings auch nicht.

Dann fällt mir jedes Mal aufs Neue ein, dass ich zu Besuch bin.

Ich bin Touristin.

Tourist ist etwas, das man sein kann, ohne dass es einem gefallen muss.

Here’s my playlist from last Friday’s radio show.

KXCI 91.3 FM Tucson, AZ
kxci.org
“Clearstatic” – Fridays 8p-10p AST
November 13, 2009
9:00:00PM
White Lies
Death (Chase & Status Remix)
Death (single)
Fiction
easily one of my favorite songs of this year

9:05:00PM
Black Box
Ride on Time (Bass Weazel Dub Remix)
Ride on Time (single)
After the great treatment of Morgan Page’s “Fight For You,” Bass Weazel returns with a slick remix of this classic Black Box tune

9:15:00PM
Und
Fox in the Box (Christian Martin Remix)
Trapez 100
Trapez

9:20:00PM
Chemical Brothers
Do It Again (Oliver Hunteman Dub)
We Are The Night
Astralwerks

9:22:00PM
Deepchild
Death Panel My Ass Ms Palin
Trapez 100
Trapez

9:30:00PM
Fedde Le Grand
Let Me Be Real (Kraak & Smaak Remix)
Let Me Be Real (single)
Net’s Work International

9:30:00PM
Maxi Valvona
Revolve (Darin Epsilon Remix)
Night EP
Low Battery

9:35:00PM
Subotic
Shamari
Showdown EP
Beatmodul

9:41:00PM
Kerowack
A (FC Kahuna Remix)
A (single)
Thunderfin

9:40:00PM
Kenny Large & Jason McRiod
Get Dirty (N.O.T & F-dub Remix)
Day & Night
Episode

9:48:00PM
Wildchild
Renegade Master (Fatboy Slim Remix)
Renegade Master (single)
Hi Life

9:51:00PM
RQM
Barely Evil (Bass Weazel Remix)
Barely Evil (single)
OMG

9:54:00PM
Uberzone
I No You (Original Mix)
I No You (single)
Gizmonik

9:56:00PM
Dr Kucho
Nexus 2009 (Original Mix)
Nexus (single)
Beatmodul

9:58:00PM
Autokratz
Can’t Get Enough (Fine Cut Bodies Remix)
Can’t Get Enough (single)
Chi

posted by Corbin Dooley, Monday November 16, 2009

When I posted my interview with Kevin Martin (aka The Bug), I mentioned that the gig was a total belter. Here’s the review.

THE BUG AND DADDY FREDDY
BLACK BOX, BELFAST

In our last issue, Kevin Martin (for The Bug is he) promised that the live show would be “fucking all over the shop”, “confrontational” and “physical” but “enjoyable”. He wasn’t kidding, as tonight deserves to go down as one of the gigs of the year. It’s nearly over before it begins, though. A deafening blast of noise announces his arrival and demands attention before Martin, alone behind a desk of equipment at the back of the stage, powers into versions of ‘Angry’ and ‘Poison Dart’ from last year’s extraordinary London Zoo album. And then, as abruptly as it starts, the sound and lights cut out. Oops. 10 minutes of uncomfortable shuffling about later, Martin is back and this time there are no familiar bangers to cling on to. For half an hour until ragga MC Daddy Freddy arrives, it’s a sonic battlefield of harsh noise, dancehall beats and teeth-rattling bass – aggressive and deafeningly loud, yes, but compellingly danceable as well.

Eventually, Daddy Freddy does turn up and the mood changes, taking us from confrontation and aural punishment to a chaotic dance party. The familiar tunes are back – ‘Jah War’, ‘Warning’, the peerless ‘Skeng’ and reprises of both ‘Angry’ and ‘Poison Dart’, each with Daddy Freddy completely ignoring the original vocal and letting rip over the top in his own ultra-fast style. It’s a total riot, the MC’s charisma matched to the mood of the crowd and Martin solemnly going about the business of making us move, hard. They are originally scheduled to play for an hour, but once the hour is up the encores begin – largely led by Daddy Freddy, it must be said. Running out of his own material, Bug (as the MC addresses him) starts to DJ, playing fucked-up, noisy versions of dubstep producer 2562’s smooth, spacious ‘Techno Dread’ and even Dawn Penn’s classic ‘No, No, No’. Thought you’ve never heard it quite as gnarled as this before. We hit 2am and the lights come up, closing support act Filaria not even getting a chance to play. It’s a shame, but how would you follow that anyway?

Black Box

Setiap kecelakaan yang menimbulkan korban jiwa selalu menimbulkan duka dan juga tanya. Apa penyebabnya?, terlebih lagi bila kecelakaan tersebut menimpa sebuah pesawat terbang. Pasalnya seringkali kecelakaan pesawat terbang membawa korban puluhan bahkan ratusan korban tewas. Meskipun sebenarnya pesawat terbang justru merupakan alat transportasi yang paling aman dibandingkan alat transportasi lainnya. Statistik menunjukkan, korban jiwa akibat kecelakaan moda transportasi darat jauh lebih besar dibandingkan dengan alat transportasi udara pada suatu kurun waktu yang sama.

Faktor keselamatan merupakan faktor utama da-lam pengoperasian pesawat terbang. Berbagai macam regulasi dan peraturan harus ditaati, tapi kecelakaan tetap saja terjadi juga. Ada tiga faktor utama penyebab terjadinya kecelakaan yaitu faktor manusia, material dan alam, serta beberapa faktor lain diantaranya faktor manajemen dan operasional yang pada akhirnya faktor manusia juga yang paling ber-peran dalam setiap kecelakaan pesawat terbang.

Ada beberapa cara untuk mengetahui penyebab terjadinya suatu kecelakaan, diantaranya adalah dengan memasang alat perekam penerbangan yang sering disebut Black Box atau kotak hitam sebagai alat untuk menguak tabir penyebab kecelakaan.

Mau kecelakaan pesawat terbang apapun, akan banyak pertanyaan tentang apa yang menyebabkan suatu pesawat jatuh. Pemeriksaan akan terfokus pada FDR (Flight Data Recorder) dan CVR (Cockpit Voice Recorder yang dikenal juga dengan nama “Black Box”. Pada pesawat 261 Alaska yang jatuh tanggal 31 Januari 2000 di lautan Pasific, FDR mengandung 48 parameter  flight data dan CVR merekam lebih dari 30 menit percakapan dan bunyi lain di kokpit.

Black Box Flight 261 Alaska

Harga dari alat perekam ini berkisar $10.000-$15.000 perbuah.

Perekaman dan Penyimpanan

Penggunaan “Magnetic Tape” sebagai perekam diperkenalkan pada era 60 an, sampai sekarang masih ada juga penerbangan yang menggunakan system ini, baru pada tahu 90 an, beralih ke system “solid-state memory boards”.  “Magnetic Tape” bekerja seperti tape recorder yang kita kenal.

Magnetic Tape yang didapat pada Perusahaan Egypt Air Flight 990, yang jatuh tanggal 31 Oktober 1999

Magnetic Tape Egypt Air Flight 990

FDR saja dirasa tidak cukup untuk memberikan informasi tentang suatu kecelakaan, maka diperlukan alat perekam suara di Cockpit dengan memasang beberapa mikrofon, untuk merekam percakapan pilot, komunikasi dengan Air Traffic Control (ATC). Untuk itu, CVR yang berbasis Magnetic Tape juga dikembangkan pada kurun waktu tersebut, guna melengkapi FDR dalam mengungkap kecelakaan sehingga pada tahun 1965, CVR wajib dipasang di semua pesawat terbang komersial. Pada tahun 1990, mulai dikembangkan FDR generasi ketiga yang berbasiskan teknologi Solid State, disusul dengan CVR pada tahun 1992. Keunggulan Black Box generasi ketiga ini adalah kemampuannya untuk merekam lebih banyak parameter dan waktu yang lebih lama, biaya perawatan yang lebih rendah dan pembacaan data yang lebih mudah dibandingkan dengan Magnetic Tape. Kebanyakan pesawat terbang komersial yang beroperasi saat ini menggunakan Black Box jenis Magnetic Tape atau Solid State Memory Boards, dan beberapa tahun mendatang, per-usahaan pembuat Black Box merencanakan juga untuk dapat membuat Cockpit Video Recorder.

Solid-state Technology sudah pasti lebih andal daripada technologi sebelumnya. Solid state menggunakan kumpulan dari “memory chip”, sehingga tidak mempunyai bagian-bagian yang dapat dilepaskan. Dengan system yang begini, hanya diperlukan sedikit perawatan dan dapat dicegah kerusakan yang parah waktu kecelakaan.

Data dari CVR dan FDR disimpan di “memory board” di dalam CSMU (crash-survivable memory unit). Di dalam recorder yang dibuat oleh perusahaan yang bernama L-3 Communication, CSMU berbentuk silinder. Memory board berukuran diameter 4.45 cm dan tinggi 2.54 cm.

Memory board mempunyai space yang dapat menyimpan 2 jam data audio CVR dan 25 jam data flight FDR.

Ada sensor yang mencatat kecepatan udara, ketinggian, setting kepakan sayap, suhu luar, suhu kabin, tekanan dan lain-lainnya. Magnetic –tape recorders bisa mencatat 100 parameter dan solid-state recorders bisa mencatat 700 parameter.

Data yang terkumpul dikirim ke FDAU (Flight-data acquisition unit) yang terdapat di depan pesawat terbang. Alat ini biasanya dijumpai di “electronic equipment bay” di bawah kokpit.  Unit “Flight-data acquisition “ adalah yang memanage keseluruhan perekaman data dan  melalui sensor mengirimnya ke “Black Box”

Kedua Black box mengambil sumber tenaga dari mesin pesawat.  generator 28 volt DC dan yang satu 115 volt, 400 Hz AC.

LOKASI PENEMPATAN

PEREKAMAN SUARA DI KOKPIT

Di setiap pesawat komersil. Ada beberapa microphone yang sengaja dipasang utnuk mencatat percakapan dari crew pesawat. Mikrophone ini didesain sehingga peka dengan segala macam suara, seperti suara switch, ketukan dan atau suara gedebuk. Mungkin sampai ada 4 mikrophone di kokpit yang bersambungan dengan CVR.

Lokasi keempat microphone

1. Headset pilot
2. Headset co-pilot
3. Headset crew member yang lain (bila ada)
4. Di tengah-tengah kokpit, untuk merekam suara lain atau suara tanda bahaya

Data yang direkam FDR

1. Waktu
2. Pressure altitude
3. Airspeed
4. Kecepatan vertical
5. Magnetic heading
6. Posisi “control-column”
7. Posisi “rudder-pedal”
8. Posisi “control-wheel”
9. Kestabilan horizontal
10. Aliran bahan bakar

Di dalam suatu kecelakaan yang selamat pasti CSMU, CSMU berbentuk silinder besar yang dibautkan kepadanya bagian datar dari perekam. Di desain untuk tahan terhadap panas, kecelakaan yang hebat dan tekanan yang besar. Lapisannya antara lain :

1. Bagian luar dari bahan alumunium, ada lapisan tipis aluminium di sekeliling memory card
2. Penyekat pelindung tekanan tinggi, dari material “dry-silica”, ketebalan 1 inchi yang melindungi dari suhu panas yang tinggi. Melidungi memory board dari kebakaran waktu kecelakaan
3. Pelindung stainless-steel, yang membalut penyekat tadi dengan ketebalan 0.64. Titanium juga digunakan pada bagian ini, dan hasilnya lebih baik.

BLACK BOX

POTONGAN BLACK BOX

TES-TES PADA CSMU YANG DILAKUKAN AGAR MEMENUHI SYARAT

1. Crash Impact, ditembakkan ke angkasa dengan meriam untuk mendapatkan dampak 3.400 Gravitasi, jadi CSMU menerima beban sebesar 3.400 kali beratnya.
2. Pin drop, peneliti menjatuhkan pin besi  berukuran 0.25 inch seberat 227 kg, dari ketinggian  3 m. dijatuhkan pada bagian yang dirasa ringkih.
3. Static crush, ditumbukkan beban sebesar 5000 psi ke enam bagian utama titik axis selama 5 menit
4. Fire test, dengan pengetesan memakai fire burner bersuhu 1100 c selama 1 jam
5. Deep-sea submersion, dengan menempatkan pada tangki berisi air laut bertekananselama 24 jam
6. Salt-water submersion, dengan menempatkan pada tangki air laut selama 30 hari
7. Fluid immersion, ditempatkan pada jenis cairan penerbangan, termasuk bahan bakar pekat dan bahan kimia pemadam api.

INFORMASI

Mengapa namanya “black box” atau kotak hitam, sebenarnya berwarna oranye terang yang dicat strip-strip reflektif. Ada beberapa sumber yang mengatakan mungkin warna awalnya memang hitam, atau mungkin sudah oranye dari dulu tetapi menjadi hitam karena efek dari kecelakaan.

UNDERWATER LOCATOR BEACON(ULB)

Bila pesawat jatuh keair beacon ini akan mengirimkan signal ultrasonic yang tidak dapat didengarkan oleh telinga manusia tetapi dengan menggunakan sonar dan perlengkapan akustik lokasi. Ada submergence sensor di beacon (yang kayak sasaran) kalau terkena air akan mengaktifkan beacon

Signal yang dikirimkan beacon di 37.5 kHz dan dapat mengirimkan di kedalaman 4267 m. ditenagai oleh batere yang dapat bertahan selama 6 tahun.

UNDERWATER LOCATOR BEACON

MENDAPATKAN INFORMASI

Diperlukan waktu seminggu sampai sebulan. Jika FDR tidak rusak pemeriksa dapat mengakses data secara cepat. Dengan solid-state recorders. Pemeriksa dapat mengambil data dan memindahkan data menit permenit. Biasanya kebanyakan rusak, terpaksa memory board di cabut, dibersihkan dan dipasang kabel memory interface yang baru. Dengan software khusus dikumpulkan data-datanya.

This portable interface can allow investigators quick access to the data on a black box

TIM-TIM PENYELIDIK

Biasanya dilakukan satu tim yang terdiri dari pakar-pakar untuk menterjemahkan rekaman dalam CVR. Termasuk perwakilan dari perusahaan penerbangan, perwakilan dari pabrik pembuat pesawat, NTSB transportation-safety spesialis dan NTSB air-safety investigator. Termasuk juga pihak dari FBI dan penterjemah bahasa.

Baik FDR maupun CVR adalah alat yang sangat berharga untuk penyelidikan kecelakaan pesawat udara yang mana pun. Semakin teknologi berkembang, kotak hitam akan terus memainkan tugas luar biasa di pemeriksaan kecelakaan dan katanya akan dikembangkan suatu black box yang menyimpan data audio dan visual.

Letak black box sendiri terletak jauh diatas vertical fin / sirip tegak, dan coba perhatikan, setiap pesawat crash, bagian sirip tegak ini yang paling jarang hancur. makanya black box ini bisa disebut indestructible karena memang posisi nya paling jarang kena hard impact.

Boundary value analysis and Equivalence partitioning, explained with simple example:

Boundary value analysis and equivalence partitioning both are test case design strategies in black box testing.

Equivalence Partitioning:

In this method the input domain data is divided into different equivalence data classes. This method is typically used to reduce the total number of test cases to a finite set of testable test cases, still covering maximum requirements.

In short it is the process of taking all possible test cases and placing them into classes. One test value is picked from each class while testing.

E.g.: If you are testing for an input box accepting numbers from 1 to 1000 then there is no use in writing thousand test cases for all 1000 valid input numbers plus other test cases for invalid data.

Using equivalence partitioning method above test cases can be divided into three sets of input data called as classes. Each test case is a representative of respective class.

So in above example we can divide our test cases into three equivalence classes of some valid and invalid inputs.

Test cases for input box accepting numbers between 1 and 1000 using Equivalence Partitioning:
1) One input data class with all valid inputs. Pick a single value from range 1 to 1000 as a valid test case. If you select other values between 1 and 1000 then result is going to be same. So one test case for valid input data should be sufficient.

2) Input data class with all values below lower limit. I.e. any value below 1, as a invalid input data test case.

3) Input data with any value greater than 1000 to represent third invalid input class.

So using equivalence partitioning you have categorized all possible test cases into three classes. Test cases with other values from any class should give you the same result.

We have selected one representative from every input class to design our test cases. Test case values are selected in such a way that largest number of attributes of equivalence class can be exercised.

Equivalence partitioning uses fewest test cases to cover maximum requirements.

Boundary value analysis:

It’s widely recognized that input values at the extreme ends of input domain cause more errors in system. More application errors occur at the boundaries of input domain. ‘Boundary value analysis’ testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain.

Boundary value analysis is a next part of Equivalence partitioning for designing test cases where test cases are selected at the edges of the equivalence classes.

Test cases for input box accepting numbers between 1 and 1000 using Boundary value analysis:
1) Test cases with test data exactly as the input boundaries of input domain i.e. values 1 and 1000 in our case.

2) Test data with values just below the extreme edges of input domains i.e. values 0 and 999.

3) Test data with values just above the extreme edges of input domain i.e. values 2 and 1001.

Boundary value analysis is often called as a part of stress and negative testing.

Note: There is no hard-and-fast rule to test only one value from each equivalence class you created for input domains. You can select multiple valid and invalid values from each equivalence class according to your needs and previous judgments.

E.g. if you divided 1 to 1000 input values in valid data equivalence class, then you can select test case values like: 1, 11, 100, 950 etc. Same case for other test cases having invalid data classes.

This should be a very basic and simple example to understand the Boundary value analysis and Equivalence partitioning concept.

Join Lyfeliek and Xcalybr for game talk and more from the midnight launch of Modern Warfare 2 in Washington, Pennsylvania! The second segment was lost to the podcast production ether, but The Gamesmen have still salvaged a great show for you! Topics discussed are EA layoffs, Dragon Age, interviews from people called to play MW2 early, the Activision Minute, your Twitter #TheGamesmenCheck submissions, and more!

• Intro Music Composed By gamertag “TheHoleyMoley”
• Featured Interlude Music- God of War
• Outro Music “Over Now” by Alice In Chains

If you want to lay claim to the Ratchet & Clank Future: A Crack In Time codes, PS3 NHL 10 codes, or the Uncharted 2 code, post below- first come, first served!

We appreciate the feedback, so keep it coming! Contact us at TheGamesmenRPG@gmail.com or simply comment below!

Direct Download | The Gamesmen On iTunes (01:42:43)

(baogame.vn) – Mặc dù đang nắm trong tay rất nhiều tựa game đình đám, với số lượng tiêu thụ hàng triệu bản. Tuy nhiên, trong một động thái mới nhất nhằm cải thiện doanh thu tài chính, EA đã quyết định sa thải hàng loạt nhân viên. Ngoài ra, hãng này cũng cho biết thêm là họ sẽ chỉ tập trung vào các tựa game lớn và cắt giảm ngân sách cho những dự án không khả thi.

Source: EA cắt giảm nhân lực mạnh mẽ

From a learning and pedagogical perspective, I would not, not, not want to entertain the notion of downloading a prepackaged virtual machine. The most frustrating thing I can think of, at least in this IRLS672/675 realm, would be a black box experience. Of course I wouldn’t have known any better. But tech life is full of black boxes for the curious and uninformed these days. It’s Just More Fun Doing It Myself. Doing with my own ten fingers eyes glued to screen with held breath is how I learn, best.

These courses are, IMHO, all about understanding how to take the lid off the black box and at least burn the memory of having once seen the contents revealed, if not how to remove them and replace them each nut and bolt by nut and bolt in perfect reverse sequence. At least being able to talk to the doers, if not be the doer. I like the idea of getting in there from the beginning and building the thing, setting the stage for tweaking and downloading and unpacking to come. Given that there are always ways to retrace much further back, back to zeroes and ones in the end, so our VM is really itself an artificial starting point, but. It’s hard these days to get much further back than the web; that’s one of the reasons this program so appealed to me. And from a digital library standpoint, I can see saying to Customer A, Hey, I can show you what I mean, unpacking the laptop and firing up the VM. Possible without having built it, but probably not so I could explain to Customer A what a virtual machine is. Not that Customer A asked. That was Customer B who had some programming experience and questioned me about this DigIn experience listed on my résumé.

Then there’s the bounceback effect. The virtual machine is a lovely, harmless way of learning how the rather more easily harmed home machine works…can I count the ways in which I’ve learned how my Mac works from running the VM through paces? No I cannot. But they are many. Not just because of the Linux/Unix heritage. From the start, the idea that this is not my Mac, this is another entity cohabiting the aluminum casing, that would have been hard to get across to me without all the startup; by now I might have slipped into thinking of it as an application. Mystified by my inability to open a Word doc inside it.

Perhaps these are not generalized courses in computer science…but as archivist, librarian, information professionista, I would prefer to be able to say that I built a VM than that I’ve seen a VM. No doubt there would have been time for other things had we skipped straight in (that’s assuming the large file issue of a prefab was not an issue–got a feeling there’d always be something to troubleshoot, though). Maybe the time freed up (which I’m not persuaded would have been much) could have been spent more carefully preparing a collection for use and reuse across IR software so that we’d have, I don’t know, more experience with different file formats or import/construction of sturdy metadata. I wouldn’t trade it in.

Then again: I’ve had a pretty easy time with the VMs. Let those speak who have not.

Do you know “Most of the bugs in software are due to incomplete or inaccurate functional requirements?” The software code, doesn’t matter how well it’s written, can’t do anything if there are ambiguities in requirements.

It’s better to catch the requirement ambiguities and fix them in early development life cycle. Cost of fixing the bug after completion of development or product release is too high.  So it’s important to have requirement analysis and catch these incorrect requirements before design specifications and project implementation phases of SDLC.

How to measure functional software requirement specification (SRS) documents?
Well, we need to define some standard tests to measure the requirements. Once each requirement is passed through these tests you can evaluate and freeze the functional requirements.

Let’s take an example. You are working on a web based application. Requirement is as follows:
“Web application should be able to serve the user queries as early as possible”

How will you freeze the requirement in this case?
What will be your requirement satisfaction criteria? To get the answer, ask this question to stakeholders: How much response time is ok for you?
If they say, we will accept the response if it’s within 2 seconds, then this is your requirement measure. Freeze this requirement and carry the same procedure for next requirement.

We just learned how to measure the requirements and freeze those in design, implementation and testing phases.

Now let’s take other example. I was working on a web based project. Client (stakeholders) specified the project requirements for initial phase of the project development. My manager circulated all the requirements in the team for review. When we started discussion on these requirements, we were just shocked! Everyone was having his or her own conception about the requirements. We found lot of ambiguities in the ‘terms’ specified in requirement documents, which later on sent to client for review/clarification.

Client used many ambiguous terms, which were having many different meanings, making it difficult to analyze the exact meaning. The next version of the requirement doc from client was clear enough to freeze for design phase.

From this example we learned “Requirements should be clear and consistent”

Next criteria for testing the requirements specification is “Discover missing requirements”

Many times project designers don’t get clear idea about specific modules and they simply assume some requirements while design phase. Any requirement should not be based on assumptions. Requirements should be complete, covering each and every aspect of the system under development.

Specifications should state both type of requirements i.e. what system should do and what should not.

Generally I use my own method to uncover the unspecified requirements. When I read the software requirements specification document (SRS), I note down my own understanding of the requirements that are specified, plus other requirements SRS document should supposed to cover. This helps me to ask the questions about unspecified requirements making it clearer.

For checking the requirements completeness, divide requirements in three sections, ‘Must implement’ requirements, requirements those are not specified but are ‘assumed’ and third type is ‘imagination’ type of requirements. Check if all type of requirements are addressed before software design phase.

Check if the requirements are related to the project goal.
Some times stakeholders have their own expertise, which they expect to come in system under development. They don’t think if that requirement is relevant to project in hand. Make sure to identify such requirements. Try to avoid the irrelevant requirements in first phase of the project development cycle. If not possible ask the questions to stakeholders: why you want to implement this specific requirement? This will describe the particular requirement in detail making it easier for designing the system considering the future scope.

But how to decide the requirements are relevant or not?
Simple answer: Set the project goal and ask this question: If not implementing this requirement will cause any problem achieving our specified goal? If not, then this is irrelevant requirement. Ask the stakeholders if they really want to implement these types of requirements.

In short requirements specification (SRS) doc should address following:
Project functionality (What should be done and what should not)
Software, Hardware interfaces and user interface
System Correctness, Security and performance criteria
Implementation issues (risks) if any

Conclusion:
I have covered all aspects of requirement measurement. To be specific about requirements, I will summarize requirement testing in one sentence:
“Requirements should be clear and specific with no uncertainty, requirements should be measurable in terms of specific values, requirements should be testable having some evaluation criteria for each requirement, and requirements should be complete, without any contradictions”

Testing should start at requirement phase to avoid further requirement related bugs. Communicate more and more with your stakeholder to clarify all the requirements before starting project design and implementation.

It’s a every testers question. How to be a good tester? Apart from the technical knowledge, testing skills, tester should have some personal level skills which will help them to build a good rapport in the testing team.

What are these abilities , skills which make a tester as a good tester? Well, I was reading Dave Whalen’s article “Ugly Baby Syndrome!” and found it very interesting. Dave compared software developers with the parents who deliver a baby (software) with countless efforts. Naturally the product managers, architectures, developers spent their countless time on developing application for the customer. Then they show it to us (testers) and asks: “ How is the baby (Application)? “ And testers tell them often that they have and ugly baby. (Application with Bugs!)

Testers don’t want to tell them that they have ugly baby, but unfortunately its our job. So effectively tester can convey the message to the developers without hurting them. How can be this done? Ya that is the skill of a good tester!

Here are the tips sated by Dave to handle such a delicate situation:

Be honest and Responsive:
Tell developers what are your plans to attack their application.

Be open and available:
If any dev ask you to have a look at the application developed by him before the release, then politely give feedback on it and report any extra efforts needed. Don’t log the bug’s for these notes.

Let them review your tests:
If you have designed or wrote some test cases from the requirement specifications then just show them those test cases. Let them know your stuff as you are going to critic on developers work!

Use of Bug tracker:
Some testers have habit to report each and everything publicly. This attitude hurts the developers. So if you have logged any bug then let the bug tracking system report it to respective developers and managers. Also don’t each time rely on bug tracker, talk personally to developers what you logged and why you logged?

Finally some good personal points:

Don’t take it personally:
Do the job of messenger. You could be a close target always. So build a thick skin!

Be prepared:
A good message in the end, Be prepared for everything! If worst things might not happened till now but they can happen at any moment in your career. So be ready to face them.

[Thougt of the Day: When a virtually flawless application is delivered to a customer, no one says how well tested it was. Development teams will always get the credit. However, if it is delivered with bugs, everyone will wonder who tested it! - - Dave Whalen]

Introduction

As more and more vital data is stored in web applications and the number of transactions on the web increases, proper security testing of web applications is becoming very important. Security testing is the process that determines that confidential data stays confidential (i.e. it is not exposed to individuals/ entities for which it is not meant) and users can perform only those tasks that they are authorized to perform (e.g. a user should not be able to deny the functionality of the web site to other users, a user should not be able to change the functionality of the web application in an unintended way etc.).

Some key terms used in security testing

Before we go further, it will be useful to be aware of a few terms that are frequently used in web application security testing:

What is “Vulnerability”?
This is a weakness in the web application. The cause of such a “weakness” can be bugs in the application, an injection (SQL/ script code) or the presence of viruses.

What is “URL manipulation”?
Some web applications communicate additional information between the client (browser) and the server in the URL. Changing some information in the URL may sometimes lead to unintended behavior by the server.

What is “SQL injection”?
This is the process of inserting SQL statements through the web application user interface into some query that is then executed by the server.

What is “XSS (Cross Site Scripting)”?
When a user inserts HTML/ client-side script in the user interface of a web application and this insertion is visible to other users, it is called XSS.

What is “Spoofing”?
The creation of hoax look-alike websites or emails is called spoofing.
Security testing approach:

In order to perform a useful security test of a web application, the security tester should have good knowledge of the HTTP protocol. It is important to have an understanding of how the client (browser) and the server communicate using HTTP. Additionally, the tester should at least know the basics of SQL injection and XSS. Hopefully, the number of security defects present in the web application will not be high. However, being able to accurately describe the security defects with all the required details to all concerned will definitely help.

1. Password cracking:

The security testing on a web application can be kicked off by “password cracking”. In order to log in to the private areas of the application, one can either guess a username/ password or use some password cracker tool for the same. Lists of common usernames and passwords are available along with open source password crackers. If the web application does not enforce a complex password (e.g. with alphabets, number and special characters, with at least a required number of characters), it may not take very long to crack the username and password.

If username or password is stored in cookies without encrypting, attacker can use different methods to steal the cookies and then information stored in the cookies like username and password.

2. URL manipulation through HTTP GET methods:

The tester should check if the application passes important information in the querystring. This happens when the application uses the HTTP GET method to pass information between the client and the server. The information is passed in parameters in the querystring. The tester can modify a parameter value in the querystring to check if the server accepts it.

Via HTTP GET request user information is passed to server for authentication or fetching data. Attacker can manipulate every input variable passed from this GET request to server in order to get the required information or to corrupt the data. In such conditions any unusual behavior by application or web server is the doorway for the attacker to get into the application.

3. SQL Injection:

The next thing that should be checked is SQL injection. Entering a single quote (‘) in any textbox should be rejected by the application. Instead, if the tester encounters a database error, it means that the user input is inserted in some query which is then executed by the application. In such a case, the application is vulnerable to SQL injection.

SQL injection attacks are very critical as attacker can get vital information from server database. To check SQL injection entry points into your web application, find out code from your code base where direct MySQL queries are executed on database by accepting some user inputs.

If user input data is crafted in SQL queries to query the database, attacker can inject SQL statements or part of SQL statements as user inputs to extract vital information from database. Even if attacker is successful to crash the application, from the SQL query error shown on browser, attacker can get the information they are looking for. Special characters from user inputs should be handled/escaped properly in such cases.

4. Cross Site Scripting (XSS):

The tester should additionally check the web application for XSS (Cross site scripting). Any HTML e.g. <HTML> or any script e.g. <SCRIPT> should not be accepted by the application. If it is, the application can be prone to an attack by Cross Site Scripting.

Attacker can use this method to execute malicious script or URL on victim’s browser. Using cross-site scripting, attacker can use scripts like JavaScript to steal user cookies and information stored in the cookies.

Many web applications get some user information and pass this information in some variables from different pages.

E.g.: http://www.examplesite.com/index.php?userid=123&query=xyz

Attacker can easily pass some malicious input or <script> as a ‘&query’ parameter which can explore important user/server data on browser.

Important: During security testing, the tester should be very careful not to modify any of the following:

• Configuration of the application or the server
• Services running on the server
• Existing user or customer data hosted by the application

Additionally, a security test should be avoided on a production system.

The purpose of the security test is to discover the vulnerabilities of the web application so that the developers can then remove these vulnerabilities from the application and make the web application and data safe from unauthorized actions.

Security testing of web applications against SQL Injection, explained with simple examples – By Inder P Singh.

Many applications use some type of a database. An application under test might have a user interface that accepts user input that is used to perform the following tasks:

1.    Show the relevant stored data to the user e.g. the application checks the credentials of the user using the log in information entered by the user and exposes only the relevant functionality and data to the user

2.    Save the data entered by the user to the database e.g. once the user fills up a form and submits it, the application proceeds to save the data to the database; this data is then made available to the user in the same session as well as in subsequent sessions

Some of the user inputs might be used in framing SQL statements that are then executed by the application on the database. It is possible for an application NOT to handle the inputs given by the user properly. If this is the case, a malicious user could provide unexpected inputs to the application that are then used to frame and execute SQL statements on the database. This is called SQL injection. The consequences of such an action could be alarming.

The following things might result from SQL injection:

1. The user could log in to the application as another user, even as an administrator.

2. The user could view private information belonging to other users e.g. details of other users’ profiles, their transaction details etc.

3. The user could change application configuration information and the data of the other users.

4. The user could modify the structure of the database; even delete tables in the application database.

5. The user could take control of the database server and execute commands on it at will.

Since the consequences of allowing the SQL injection technique could be severe, it follows that SQL injection should be tested during the security testing of an application. Now with an overview of the SQL injection technique, let us understand a few practical examples of SQL injection.

Important: The SQL injection problem should be tested only in the test environment.

If the application has a log in page, it is possible that the application uses a dynamic SQL such as statement below. This statement is expected to return at least a single row with the user details from the Users table as the result set when there is a row with the user name and password entered in the SQL statement.

SELECT * FROM Users WHERE User_Name = ‘” & strUserName & “‘ AND Password = ‘” & strPassword & “’;”

If the tester would enter John as the strUserName (in the textbox for user name) and Smith as strPassword (in the textbox for password), the above SQL statement would become:

SELECT * FROM Users WHERE User_Name = ‘John’ AND Password = ‘Smith’;

If the tester would enter John’– as strUserName and no strPassword, the SQL statement would become:

SELECT * FROM Users WHERE User_Name = ‘John’– AND Password = ‘Smith’;

Note that the part of the SQL statement after John is turned into a comment. If there were any user with the user name of John in the Users table, the application could allow the tester to log in as the user John. The tester could now view the private information of the user John.

What if the tester does not know the name of any existing user of the application? In such a case, the tester could try common user names like admin, administrator and sysadmin. If none of these users exist in the database, the tester could enter John’ or ‘x’=’x as strUserName and Smith’ or ‘x’=’x  as strPassword. This would cause the SQL statement to become like the one below.

SELECT * FROM Users WHERE User_Name = ‘John’ or ‘x’=’x’ AND Password = ‘Smith’ or ‘x’=’x’;

Since ‘x’=’x’ condition is always true, the result set would consist of all the rows in the Users table. The application could allow the tester to log in as the first user in the Users table.

Important: The tester should request the database administrator or the developer to copy the table in question before attempting the following SQL injection.

If the tester would enter John’; DROP table users_details;’—as strUserName and anything as strPassword, the SQL statement would become like the one below.

SELECT * FROM Users WHERE User_Name = ‘John’; DROP table users_details;’ –‘ AND Password = ‘Smith’;

This statement could cause the table “users_details” to be permanently deleted from the database.

Though the above examples deal with using the SQL injection technique only the log in page, the tester should test this technique on all the pages of the application that accept user input in textual format e.g. search pages, feedback pages etc.

SQL injection might be possible in applications that use SSL. Even a firewall might not be able to protect the application against the SQL injection technique.

I have tried to explain the SQL injection technique in a simple form. I would like to re-iterate that SQL injection should be tested only in a test environment and not in the development environment, production environment or any other environment. Instead of manually testing whether the application is vulnerable to SQL injection or not, one could use a web vulnerability scanner that checks for SQL injection.

Gostou?Então comenta!
O seu comentário é muito importante!

André Diogo

Ok, so I’ve decided to live a bit more Green

I’ve gotten to the stage where I wonder why I’m suddenly eating more junk food, driving my car more, and just generally being a consumer, rather than a producer. I look at my bedroom and see it covered with clothes I’ve never worn, books I’ve never read and a general assortment of crap I don’t need, really want, or is anyway remotely useful to my daily life. My consumerist tendencies also mean that I barely save any of the money I earn, and take 30 minute showers in the middle of a drought.

Things have to change here. It’s time to start living with a bit more consideration for the planet, and my bank balance.

Hopefully along the way, I’ll learn something.

Car

I have a 1989 Toyota Cressida, and I love it, but it does cost me money to run and keep well-maintained, and while Myka is a hell of a lot more environmentally friendly than a lot of the petrol-guzzlers on the road, it still leaves quite the environmental footprint.

Living in the outer suburbs of Melbourne makes it difficult to catch public transport, with buses late and trains often cancelled without notice. Working at night also means risking life and limb on one of the most dangerous train lines in Melbourne early in the morning and late at night.

I haven’t been on a push bike in years, and my adventures lately with push bike riders getting knocked down by cars and trucks really makes me dread getting on a bike without designated bike lanes and at night.

Where possible, my goal is to use public transport, walk or carpool, especially for the short trips down the shops and the train station. It’ll reduce the wear on my car, the damage to the environment, and the risk of an accident.

Food.

I started really think about how much I spend on food today. My meals at work are rarely under the $10 each mark for what’s essentially tasteless and fatty foods full of sugar. The only food available within walking distance at 2.30am happens to be the local 24hr convenience store with it’s dazzling array of healthy options…… or not.

Starting with packing my lunch (and remembering to take it with me, or, failing that, having something in my desk instead) should save me about half the monetary cost, and about have the dietary cost. It also means I can be more lazy and not have to leave the building to walk down for a sausage roll.

My other goal is not to throw out as much food as I do now, by putting leftovers in the freezer and using slightly damaged fruit and veggies in casseroles and salads. Groups like Food, not Bombs and many freegans go hunting in those great bin rubbish bins that the supermarkets have and use the food thrown out in those to eat. And I can see why, with Australians currently spending 6 Billion on food, and throwing out about 1 Billion dollars of it annually.

I’m not at the stage of “Dumpster Diving” for my dinner, but I intend to grow a lot of my own food, making it a damn site better for the environment. Most of the fruit and veg in the supermarket is trucked thousands of kilometres from Queensland, and there’s no real guarantee of any food being “organic” unless you’ve grown it yourself.

In the garden.

Someone mentioned to me the other day that in times of financial crisis, spending on fast food goes up (along with hem lines apparently). Funny thing is, food is one thing that doesn’t have to be expensive. Growing veggies from seed is one such way to save money, help the environment, and teach the kids about how things grow.

I germinated veggies and herbs in a storage container in the backyard to plant into the veggie patch. It started out as an experiment to see if I really could grow things in one of those storage containers, and as it turns out, it’s dead easy!

I set myself a limit of $50AUD to start up, and using a 40L storage container, a bag of cheap potting mix, a water saving peat moss brick, and seven packs of seeds (Basil, cucumbers, capsicums, eggplants, radishes, pak choi and parsley), managed to keep it all around the $35 mark, although I already have a lot of gardening stuff at home, including a ready supply of rain water, a worm farm, and a compost bin.

All I did was soak the peat moss in a bucket of water, mixed it in with the potting soil in the container, planted the seeds in it, and shut the lid, leaving it in full sun. The heat from the sun, and the water that had soaked into the peat moss made the container incredibly humid, keeping the water trapped inside the container and making it ideal for germinating seeds. In 3 days I had cucumbers and basil poking up green bits, and the other plants weren’t too far behind (I know it was 3 days, because I was on 3 night shifts that week, and slept while the sun was up!).

About 10 days ago I planted the radishes, and I planted out the eggplants and the cucumbers about 2 days ago, which I’ve mulched heavily with sugar cane mulch. They are doing very well in the veggie patch.

This started as an inexpensive little experiment to see what I could grow in a box has yielded far better results than I could have hoped for! I’m pretty damn proud of the effort (or lack thereof) I’ve put into it. It’s been so successful, I started another box last week with Thai Basil, Lettuce and what was a packet of unmarked seeds. These mystery seeds have turned out to be more cucumbers.

By the way, the fertiliser I use on the plants is roughly 30mL of of seaweed or carp emulsion and the same of worm farm water (“worm juice!”) in a watering can, applied liberally once every 2 weeks. With the Sugar Cane mulch, this does wonders.

Computer

I currently own 2 computers. One is a Linux based 7 inch Eee PC (The Black Box) I go travelling with, and my other computer is a Ubuntu desktop (The Frankenputer) that I use as my everyday computer. For the geeks out there, Black Box runs on a Debian/Xandros hybrid Asus designed, while The Frankenputer is currently running Ubuntu 9.04 (old I know, I’ll be updating to Karmic Koala in the next few days). I bought Black Box on sale, and The Frankenputer was a mates that he was giving away a few days ago.

The Eee PC isn’t too bad environmentally. Being only 7-inches, it’s damage to the environment is minimal. And it pretty much runs on battery power when I use it. The Frankenputer is another story. With it’s CRT monitor, it takes up a lot of space and energy. That said, CRT monitors do use less energy than the flatscreen LCD monitors on the market by a considerable amount.

I do want a flatscreen monitor in my room for the space-saving factor, but I plan to buy the most friendly one I can find, and to hit the power switch when I’m not using it, reducing any energy wastage.

Turning off computer monitors also means saving a considerable amount of money on the energy bill….

I should have some more ideas on what I can do to save money and be more environmentally green in the next few days, til then…

Stay green!

Murasaki-Claire