본문으로 건너뛰기

레슨 6/13 · 17단어 · 외운 단어 0

Software development process

소프트웨어 개발 프로세스

  1. 1

    estimate(verb)

    /ˈestɪmeɪt/

    추정하다, 견적하다, 산정하다

    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.

    개발자들은 마이그레이션에 스프린트 세 번이 걸릴 것으로 추정했다.

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

    유의어approximatecalculategaugejudgeassessevaluatepredictreckon
    반의어measurecalculatedetermineascertainexact
  2. 2

    prototype(noun)

    /ˈprəʊtətaɪp/

    프로토타입, 시제품, 시안

    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.

    코드를 작성하기 전에 고객에게 클릭 가능한 프로토타입을 보여 주었습니다.

    Users tested the prototype and suggested several changes.

    유의어modelsamplemock-uparchetypeoriginalprecursor
    반의어final versionfinished productend result
  3. 3

    milestone(noun)

    /ˈmaɪlstəʊn/

    마일스톤, 주요 일정, 이정표

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

    Finishing the beta version is the next major milestone.

    베타 버전 완료가 다음 주요 마일스톤입니다.

    The client pays 30 percent at each project milestone.

    유의어landmarkwatershedbenchmarkturning pointkey event
    반의어setbackregressionfailure
  4. 4

    specification(noun)

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

    명세서, 사양서, 스펙

    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.

    개발자들은 명세서에 기술된 그대로 해당 기능을 구현했다.

    Please send us the technical specifications for the new API.

    유의어requirementdetailscriteriablueprintplan
    반의어generalityvaguenessambiguity
  5. 5

    SDLC(abbreviation)

    /ˌes diː el ˈsiː/

    소프트웨어 개발 생명주기, 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.

    테스트는 마지막에만 하지 말고 SDLC의 모든 단계에서 이루어져야 한다.

    The training course covers each phase of the SDLC.

  6. 6

    requirement(noun)

    /rɪˈkwaɪəmənt/

    요구사항

    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.

    비즈니스 분석가는 영업팀에서 요구사항을 수집하는 데 2주를 보냈다.

    Changing the requirements late in the project caused serious delays.

  7. 7

    waterfall model(noun)

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

    폭포수 모델, 워터폴 모델

    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.

    정부 프로젝트는 범위가 미리 확정되어 있기 때문에 폭포수 모델을 사용하는 경우가 많다.

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

  8. 8

    Agile(noun)

    /ˈædʒaɪl/

    애자일, 애자일 개발 방법론

    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.

    애자일로 전환한 이후 우리는 2주마다 새로운 기능을 출시하고 있다.

    Agile helps the team respond quickly when customer needs change.

  9. 9

    Scrum(noun)

    /skrʌm/

    스크럼

    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.

    우리 스크럼 팀은 개발자 6명, 테스터 1명, 프로덕트 오너 1명으로 구성되어 있다.

    The Scrum master removes problems that slow the team down.

  10. 10

    sprint(noun)

    /sprɪnt/

    스프린트

    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.

    결제 기능은 다음 스프린트에서 완료할 예정이다.

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

  11. 11

    product backlog(noun)

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

    프로덕트 백로그, 제품 백로그

    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.

    프로덕트 오너는 보고서 기능을 프로덕트 백로그의 최상단으로 옮겼다.

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

  12. 12

    user story(noun)

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

    사용자 스토리, 유저 스토리

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

    모든 사용자 스토리는 '고객으로서 나는 ~을 원한다'라는 문장으로 시작한다.

    The team estimated twelve user stories for this sprint.

  13. 13

    daily stand-up(noun)

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

    데일리 스탠드업, 일일 스탠드업 미팅

    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.

    데일리 스탠드업에서 나는 서버 문제 때문에 작업이 막혀 있다고 말했다.

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

  14. 14

    release(noun)

    /rɪˈliːs/

    릴리스, 배포, 출시

    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.

    다음 릴리스에는 다크 모드와 더 빠른 검색 기능이 포함될 것이다.

    We postponed the release because of a critical bug.

  15. 15

    documentation(noun)

    /ˌdɒkjumenˈteɪʃn/

    문서화, 기술 문서

    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.

    좋은 문서는 신입 개발자가 시스템을 빠르게 이해하는 데 도움이 된다.

    Please update the documentation whenever you change the API.

  16. 16

    technical debt(noun)

    /ˌteknɪkl ˈdet/

    기술 부채

    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.

    마감 기한을 맞추려고 기능을 서둘러 개발하다 보니 기술 부채가 많이 쌓였다.

    We spend 20 percent of each sprint reducing technical debt.

  17. 17

    scope creep(noun)

    /ˈskəʊp kriːp/

    스코프 크리프, 범위 확대

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

    Scope creep pushed the launch date back by two months.

    스코프 크리프로 인해 출시일이 두 달 뒤로 밀렸다.

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