The major steps of ARID areThe desi

The major steps of ARID are

The designer who has commissioned the review works with the ARID facilitator to identify the best reviewers. These are usually the software engineers who will be expected to use the design, as they are in the best position to judge its adequacy.
The designer prepares a briefing explaining the design, which is reviewed by the ARID facilitator. The designer presents the overview to the reviewers and walks through examples of using the design. A scribe captures questions and answers.
The reviewers brainstorm scenarios for using the design to solve problems they expect to face. After a facilitated prioritization, the resulting set of scenarios operationally defines what it means for the design to be usable: If it performs well under the adopted scenarios, then it must be agreed that the design has passed the review.
The reviewers begin to jointly craft code (or pseudo-code) that uses the design's services to solve the problem posed by each high-priority scenario. The scribe records issues, problems, and places where the stakeholders get stuck.

The major steps of ARID are

The designer who has commissioned the review works with the ARID facilitator to identify the best reviewers. These are usually the software engineers who will be expected to use the design, as they are in the best position to judge its adequacy.
The designer prepares a briefing explaining the design, which is reviewed by the ARID facilitator. The designer presents the overview to the reviewers and walks through examples of using the design. A scribe captures questions and answers.
The reviewers brainstorm scenarios for using the design to solve problems they expect to face. After a facilitated prioritization, the resulting set of scenarios operationally defines what it means for the design to be usable: If it performs well under the adopted scenarios, then it must be agreed that the design has passed the review.
The reviewers begin to jointly craft code (or pseudo-code) that uses the design's services to solve the problem posed by each high-priority scenario. The scribe records issues, problems, and places where the stakeholders get stuck.

0/5000

From: -

To: -

Results (Indonesian) 1: [Copy]

Copied!

The major steps of ARID areThe designer who has commissioned the review works with the ARID facilitator to identify the best reviewers. These are usually the software engineers who will be expected to use the design, as they are in the best position to judge its adequacy.The designer prepares a briefing explaining the design, which is reviewed by the ARID facilitator. The designer presents the overview to the reviewers and walks through examples of using the design. A scribe captures questions and answers.The reviewers brainstorm scenarios for using the design to solve problems they expect to face. After a facilitated prioritization, the resulting set of scenarios operationally defines what it means for the design to be usable: If it performs well under the adopted scenarios, then it must be agreed that the design has passed the review.The reviewers begin to jointly craft code (or pseudo-code) that uses the design's services to solve the problem posed by each high-priority scenario. The scribe records issues, problems, and places where the stakeholders get stuck.

Being translated, please wait..

Results (Indonesian) 2:[Copy]

Copied!

Langkah-langkah utama ARID adalah

para desainer yang telah menugaskan ulasan bekerja dengan fasilitator ARID untuk mengidentifikasi pengulas terbaik. Ini biasanya para insinyur perangkat lunak yang akan diharapkan untuk menggunakan desain, karena mereka berada dalam posisi terbaik untuk menilai kecukupan.
Desainer menyiapkan briefing menjelaskan desain, yang ditinjau oleh fasilitator ARID. Desainer menyajikan gambaran kepada pengulas dan berjalan melalui contoh menggunakan desain. Sebuah juru menangkap pertanyaan dan jawaban.
The pengulas brainstorming skenario untuk menggunakan desain untuk memecahkan masalah yang mereka harapkan untuk menghadapi. Setelah prioritas difasilitasi, set yang dihasilkan dari skenario operasional mendefinisikan apa artinya untuk desain untuk dapat digunakan: Jika ia melakukan dengan baik di bawah skenario diadopsi, maka harus disepakati bahwa desain telah lulus review.
The pengulas mulai bersama-sama kerajinan kode (atau pseudo-code) yang menggunakan jasa desain untuk memecahkan masalah yang ditimbulkan oleh masing-masing skenario prioritas tinggi. Juru tulis mencatat masalah, masalah, dan tempat-tempat di mana para pemangku kepentingan terjebak.

Being translated, please wait..

Results (Indonesian) 3:[Copy]

Copied!

Being translated, please wait..

Other languages

The translation tool support: Afrikaans, Albanian, Amharic, Arabic, Armenian, Azerbaijani, Basque, Belarusian, Bengali, Bosnian, Bulgarian, Catalan, Cebuano, Chichewa, Chinese, Chinese Traditional, Corsican, Croatian, Czech, Danish, Detect language, Dutch, English, Esperanto, Estonian, Filipino, Finnish, French, Frisian, Galician, Georgian, German, Greek, Gujarati, Haitian Creole, Hausa, Hawaiian, Hebrew, Hindi, Hmong, Hungarian, Icelandic, Igbo, Indonesian, Irish, Italian, Japanese, Javanese, Kannada, Kazakh, Khmer, Kinyarwanda, Klingon, Korean, Kurdish (Kurmanji), Kyrgyz, Lao, Latin, Latvian, Lithuanian, Luxembourgish, Macedonian, Malagasy, Malay, Malayalam, Maltese, Maori, Marathi, Mongolian, Myanmar (Burmese), Nepali, Norwegian, Odia (Oriya), Pashto, Persian, Polish, Portuguese, Punjabi, Romanian, Russian, Samoan, Scots Gaelic, Serbian, Sesotho, Shona, Sindhi, Sinhala, Slovak, Slovenian, Somali, Spanish, Sundanese, Swahili, Swedish, Tajik, Tamil, Tatar, Telugu, Thai, Turkish, Turkmen, Ukrainian, Urdu, Uyghur, Uzbek, Vietnamese, Welsh, Xhosa, Yiddish, Yoruba, Zulu, Language translation.