Langsung ke konten

Pelajaran 6/13 · 17 kata · 0 sudah hafal

Software development process

Proses pengembangan perangkat lunak

  1. 1

    estimate(verb)

    /ˈestɪmeɪt/

    mengestimasi, memperkirakan

    to judge roughly how much time, effort or money a task or project will need

    The developers estimated that the migration would take three sprints.

    Para pengembang memperkirakan bahwa migrasi akan memakan waktu tiga sprint.

    It is hard to estimate a task when the requirements are unclear.

    Sinonimapproximatecalculategaugejudgeassessevaluatepredictreckon
    Antonimmeasurecalculatedetermineascertainexact
  2. 2

    prototype(noun)

    /ˈprəʊtətaɪp/

    prototipe, purwarupa

    an early, simple version of a product, built to test ideas before the final version is made

    We showed the client a clickable prototype before writing any code.

    Kami menunjukkan prototipe yang dapat diklik kepada klien sebelum menulis kode apa pun.

    Users tested the prototype and suggested several changes.

    Sinonimmodelsamplemock-uparchetypeoriginalprecursor
    Antonimfinal versionfinished productend result
  3. 3

    milestone(noun)

    /ˈmaɪlstəʊn/

    tonggak proyek, tonggak pencapaian

    an important point or stage in a project, often used to check progress

    Finishing the beta version is the next major milestone.

    Menyelesaikan versi beta adalah tonggak utama berikutnya.

    The client pays 30 percent at each project milestone.

    Sinonimlandmarkwatershedbenchmarkturning pointkey event
    Antonimsetbackregressionfailure
  4. 4

    specification(noun)

    /ˌspesɪfɪˈkeɪʃn/

    spesifikasi, dokumen spesifikasi

    a detailed document that describes exactly what a product or system must do and how it should be built

    The developers built the feature exactly as described in the specification.

    Para pengembang membangun fitur tersebut persis seperti yang dijelaskan dalam spesifikasi.

    Please send us the technical specifications for the new API.

    Sinonimrequirementdetailscriteriablueprintplan
    Antonimgeneralityvaguenessambiguity
  5. 5

    SDLC(abbreviation)

    /ˌes diː el ˈsiː/

    SDLC, siklus hidup pengembangan perangkat lunak

    software development life cycle: the stages of building software, from planning and design to testing, release and maintenance

    Testing should happen at every stage of the SDLC, not just at the end.

    Pengujian harus dilakukan di setiap tahap SDLC, bukan hanya di akhir.

    The training course covers each phase of the SDLC.

  6. 6

    requirement(noun)

    /rɪˈkwaɪəmənt/

    kebutuhan, persyaratan

    a feature or condition that a software system must have, as agreed with the client or users

    The business analyst spent two weeks gathering requirements from the sales team.

    Analis bisnis menghabiskan dua minggu untuk mengumpulkan kebutuhan dari tim penjualan.

    Changing the requirements late in the project caused serious delays.

  7. 7

    waterfall model(noun)

    /ˈwɔːtəfɔːl ˌmɒdl/

    model air terjun

    a traditional way of managing software projects in which each stage is finished before the next one begins

    Government projects often use the waterfall model because the scope is fixed in advance.

    Proyek pemerintah sering menggunakan model air terjun karena ruang lingkupnya sudah ditetapkan sejak awal.

    In the waterfall model, testing only starts after all coding is complete.

  8. 8

    Agile(noun)

    /ˈædʒaɪl/

    Agile, metode pengembangan tangkas

    a way of managing software projects in short cycles, with frequent feedback and changes based on what users need

    Since we moved to Agile, we release new features every two weeks.

    Sejak beralih ke Agile, kami merilis fitur baru setiap dua minggu.

    Agile helps the team respond quickly when customer needs change.

  9. 9

    Scrum(noun)

    /skrʌm/

    Scrum

    a popular Agile framework in which a small team works in short, fixed periods called sprints

    Our Scrum team has six developers, one tester and a product owner.

    Tim Scrum kami terdiri dari enam pengembang, satu penguji, dan seorang product owner.

    The Scrum master removes problems that slow the team down.

  10. 10

    sprint(noun)

    /sprɪnt/

    sprint, iterasi

    a short, fixed period, usually one to four weeks, in which a team completes a set amount of work

    We will finish the payment feature in the next sprint.

    Kami akan menyelesaikan fitur pembayaran pada sprint berikutnya.

    During sprint planning, the team chooses tasks from the backlog.

  11. 11

    product backlog(noun)

    /ˈprɒdʌkt ˈbæklɒɡ/

    backlog produk, daftar pekerjaan produk

    a prioritized list of features, fixes and tasks that the team plans to work on for a product

    The product owner moved the reporting feature to the top of the product backlog.

    Product owner memindahkan fitur pelaporan ke urutan teratas backlog produk.

    We review the product backlog every week to remove old items.

  12. 12

    user story(noun)

    /ˈjuːzə ˌstɔːri/

    cerita pengguna, user story

    a short description of a feature from the user's point of view, used to plan work in Agile teams

    Each user story starts with the words: As a customer, I want to...

    Setiap cerita pengguna diawali dengan kalimat: Sebagai pelanggan, saya ingin...

    The team estimated twelve user stories for this sprint.

  13. 13

    daily stand-up(noun)

    /ˌdeɪli ˈstænd ʌp/

    rapat harian singkat, stand-up harian

    a short team meeting held every day where members say what they did, what they will do and any problems

    In the daily stand-up, I mentioned that I was blocked by the server issue.

    Dalam rapat stand-up harian, saya menyampaikan bahwa pekerjaan saya terhambat oleh masalah server.

    Our daily stand-up starts at 9:15 and lasts no more than fifteen minutes.

  14. 14

    release(noun)

    /rɪˈliːs/

    rilis, perilisan

    a version of software that is made available to users, or the act of making it available

    The next release will include dark mode and faster search.

    Rilis berikutnya akan mencakup mode gelap dan pencarian yang lebih cepat.

    We postponed the release because of a critical bug.

  15. 15

    documentation(noun)

    /ˌdɒkjumenˈteɪʃn/

    dokumentasi

    written information that explains how software works, how to use it or how it was built

    Good documentation helps new developers understand the system quickly.

    Dokumentasi yang baik membantu pengembang baru memahami sistem dengan cepat.

    Please update the documentation whenever you change the API.

  16. 16

    technical debt(noun)

    /ˌteknɪkl ˈdet/

    utang teknis

    future work caused by choosing a quick or easy solution now instead of a better one

    Rushing features to meet deadlines has created a lot of technical debt.

    Terburu-buru mengerjakan fitur demi memenuhi tenggat telah menimbulkan banyak utang teknis.

    We spend 20 percent of each sprint reducing technical debt.

  17. 17

    scope creep(noun)

    /ˈskəʊp kriːp/

    pembengkakan lingkup, scope creep

    the gradual growth of a project's requirements beyond what was originally agreed

    Scope creep pushed the launch date back by two months.

    Pembengkakan lingkup membuat tanggal peluncuran mundur dua bulan.

    To prevent scope creep, every new request must be approved by the project manager.