レッスン6/13 · 17語 · 覚えた単語 0
Software development process
ソフトウェア開発プロセス
見積もる, 工数を見積もる
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.
開発者たちは、移行作業に3スプリントかかると見積もった。
It is hard to estimate a task when the requirements are unclear.
類義語approximatecalculategaugejudgeassessevaluatepredictreckon対義語measurecalculatedetermineascertainexactプロトタイプ, 試作品, 試作機
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マイルストーン, 節目, 中間目標
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仕様書, 仕様, スペック
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ソフトウェア開発ライフサイクル, 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.
要件, 要求
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.
ウォーターフォールモデル, ウォーターフォール開発
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.
アジャイル, アジャイル開発
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.
プロダクトバックログ
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.
デイリースクラム, 朝会, スタンドアップミーティング
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.
ドキュメント, ドキュメンテーション, 文書
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.



