İçeriğe geç

Ders 6/13 · 17 kelime · Öğrenilen: 0

Software development process

Yazılım geliştirme süreci

  1. 1

    estimate(verb)

    /ˈestɪmeɪt/

    tahmin etmek, efor tahmini yapmak

    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.

    Geliştiriciler geçişin üç sprint süreceğini tahmin etti.

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

    Eş anlamlılarapproximatecalculategaugejudgeassessevaluatepredictreckon
    Zıt anlamlılarmeasurecalculatedetermineascertainexact
  2. 2

    prototype(noun)

    /ˈprəʊtətaɪp/

    prototip, ilk örnek

    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.

    Müşteriye tek satır kod yazmadan önce tıklanabilir bir prototip gösterdik.

    Users tested the prototype and suggested several changes.

    Eş anlamlılarmodelsamplemock-uparchetypeoriginalprecursor
    Zıt anlamlılarfinal versionfinished productend result
  3. 3

    milestone(noun)

    /ˈmaɪlstəʊn/

    kilometre taşı, ara hedef

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

    Finishing the beta version is the next major milestone.

    Beta sürümünü tamamlamak bir sonraki önemli kilometre taşıdır.

    The client pays 30 percent at each project milestone.

    Eş anlamlılarlandmarkwatershedbenchmarkturning pointkey event
    Zıt anlamlılarsetbackregressionfailure
  4. 4

    specification(noun)

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

    şartname, spesifikasyon, teknik şartname

    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.

    Geliştiriciler özelliği tam olarak spesifikasyonda tarif edildiği gibi geliştirdi.

    Please send us the technical specifications for the new API.

    Eş anlamlılarrequirementdetailscriteriablueprintplan
    Zıt anlamlılargeneralityvaguenessambiguity
  5. 5

    SDLC(abbreviation)

    /ˌes diː el ˈsiː/

    yazılım geliştirme yaşam döngüsü, SDLC

    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.

    Test, yalnızca sonunda değil, yazılım geliştirme yaşam döngüsünün (SDLC) her aşamasında yapılmalıdır.

    The training course covers each phase of the SDLC.

  6. 6

    requirement(noun)

    /rɪˈkwaɪəmənt/

    gereksinim, yazılım gereksinimi

    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.

    İş analisti, satış ekibinden gereksinimleri toplamak için iki hafta harcadı.

    Changing the requirements late in the project caused serious delays.

  7. 7

    waterfall model(noun)

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

    şelale modeli, çağlayan modeli

    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.

    Kamu projelerinde kapsam önceden belirlendiği için genellikle şelale modeli kullanılır.

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

  8. 8

    Agile(noun)

    /ˈædʒaɪl/

    çevik yöntem, Agile, çevik yazılım geliştirme

    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.

    Agile'e geçtiğimizden beri yeni özellikleri her iki haftada bir yayınlıyoruz.

    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.

    Scrum ekibimizde altı geliştirici, bir test uzmanı ve bir ürün sahibi var.

    The Scrum master removes problems that slow the team down.

  10. 10

    sprint(noun)

    /sprɪnt/

    sprint

    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.

    Ödeme özelliğini bir sonraki sprintte bitireceğiz.

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

  11. 11

    product backlog(noun)

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

    ürün biriktirme listesi, product backlog

    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.

    Ürün sahibi, raporlama özelliğini ürün biriktirme listesinin en üstüne taşıdı.

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

  12. 12

    user story(noun)

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

    kullanıcı hikâyesi

    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...

    Her kullanıcı hikâyesi şu sözlerle başlar: Bir müşteri olarak ... istiyorum.

    The team estimated twelve user stories for this sprint.

  13. 13

    daily stand-up(noun)

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

    günlük ayakta toplantı, daily stand-up

    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.

    Günlük ayakta toplantıda sunucu sorunu yüzünden engellendiğimi belirttim.

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

  14. 14

    release(noun)

    /rɪˈliːs/

    sürüm, yayın, yayınlama

    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.

    Bir sonraki sürümde karanlık mod ve daha hızlı arama olacak.

    We postponed the release because of a critical bug.

  15. 15

    documentation(noun)

    /ˌdɒkjumenˈteɪʃn/

    dokümantasyon, belgelendirme

    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.

    İyi bir dokümantasyon, yeni geliştiricilerin sistemi hızla anlamasına yardımcı olur.

    Please update the documentation whenever you change the API.

  16. 16

    technical debt(noun)

    /ˌteknɪkl ˈdet/

    teknik borç

    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.

    Özellikleri teslim tarihlerine yetiştirmek için aceleye getirmek çok fazla teknik borç yarattı.

    We spend 20 percent of each sprint reducing technical debt.

  17. 17

    scope creep(noun)

    /ˈskəʊp kriːp/

    kapsam kayması, kapsam genişlemesi

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

    Scope creep pushed the launch date back by two months.

    Kapsam kayması, yayın tarihini iki ay geriye itti.

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