Lumaktaw sa nilalaman

Aralin 6/13 · 17 salita · 0 natutunan

Software development process

Proseso ng software development

  1. 1

    estimate(verb)

    /ˈestɪmeɪt/

    tantiyahin, tayahin

    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.

    Tinantiya ng mga developer na tatlong sprint ang aabutin ng migrasyon.

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

    Kasingkahuluganapproximatecalculategaugejudgeassessevaluatepredictreckon
    Kasalungatmeasurecalculatedetermineascertainexact
  2. 2

    prototype(noun)

    /ˈprəʊtətaɪp/

    prototype, unang modelo

    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.

    Ipinakita namin sa kliyente ang isang clickable na prototype bago magsulat ng anumang code.

    Users tested the prototype and suggested several changes.

    Kasingkahuluganmodelsamplemock-uparchetypeoriginalprecursor
    Kasalungatfinal versionfinished productend result
  3. 3

    milestone(noun)

    /ˈmaɪlstəʊn/

    milestone, mahalagang yugto

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

    Finishing the beta version is the next major milestone.

    Ang pagtatapos ng beta version ang susunod na pangunahing milestone.

    The client pays 30 percent at each project milestone.

    Kasingkahuluganlandmarkwatershedbenchmarkturning pointkey event
    Kasalungatsetbackregressionfailure
  4. 4

    specification(noun)

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

    espesipikasyon, detalyadong paglalarawan

    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.

    Binuo ng mga developer ang feature nang eksakto ayon sa espesipikasyon.

    Please send us the technical specifications for the new API.

    Kasingkahuluganrequirementdetailscriteriablueprintplan
    Kasalungatgeneralityvaguenessambiguity
  5. 5

    SDLC(abbreviation)

    /ˌes diː el ˈsiː/

    SDLC, siklo ng pagbuo ng programa

    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.

    Dapat magkaroon ng pagsubok sa bawat yugto ng SDLC, hindi lang sa dulo.

    The training course covers each phase of the SDLC.

  6. 6

    requirement(noun)

    /rɪˈkwaɪəmənt/

    pangangailangan, rekisito

    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.

    Dalawang linggong nangalap ng mga requirement ang business analyst mula sa sales team.

    Changing the requirements late in the project caused serious delays.

  7. 7

    waterfall model(noun)

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

    modelong talon

    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.

    Madalas gamitin ng mga proyekto ng gobyerno ang waterfall model dahil nakatakda na nang maaga ang saklaw.

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

  8. 8

    Agile(noun)

    /ˈædʒaɪl/

    Agile, maliksing pamamaraan

    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.

    Mula nang lumipat kami sa Agile, naglalabas kami ng mga bagong feature kada dalawang linggo.

    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.

    Ang aming Scrum team ay may anim na developer, isang tester at isang product owner.

    The Scrum master removes problems that slow the team down.

  10. 10

    sprint(noun)

    /sprɪnt/

    sprint, maikling yugto ng gawain

    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.

    Tatapusin namin ang payment feature sa susunod na sprint.

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

  11. 11

    product backlog(noun)

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

    talaan ng nakabinbing gawain ng produkto

    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.

    Inilipat ng product owner ang reporting feature sa pinakataas ng product backlog.

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

  12. 12

    user story(noun)

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

    kuwento ng gumagamit

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

    Bawat user story ay nagsisimula sa mga salitang: “Bilang isang customer, gusto kong...”

    The team estimated twelve user stories for this sprint.

  13. 13

    daily stand-up(noun)

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

    pang-araw-araw na maikling pulong

    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.

    Sa daily stand-up, binanggit kong nahaharangan ako ng problema sa server.

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

  14. 14

    release(noun)

    /rɪˈliːs/

    pagpapalabas, inilabas na bersyon

    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.

    Kasama sa susunod na release ang dark mode at mas mabilis na paghahanap.

    We postponed the release because of a critical bug.

  15. 15

    documentation(noun)

    /ˌdɒkjumenˈteɪʃn/

    dokumentasyon

    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.

    Natutulungan ng mahusay na dokumentasyon ang mga bagong developer na mabilis maunawaan ang sistema.

    Please update the documentation whenever you change the API.

  16. 16

    technical debt(noun)

    /ˌteknɪkl ˈdet/

    utang na teknikal

    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.

    Ang pagmamadali sa mga feature para matugunan ang mga deadline ay lumikha ng maraming technical debt.

    We spend 20 percent of each sprint reducing technical debt.

  17. 17

    scope creep(noun)

    /ˈskəʊp kriːp/

    unti-unting paglawak ng saklaw

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

    Scope creep pushed the launch date back by two months.

    Dahil sa scope creep, naurong nang dalawang buwan ang petsa ng paglulunsad.

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