SAAASの記述をする
Closed this issue · 4 comments
結局資源評価は、その都度行われる「作業」ではなく、「サービス」なのだ。という認識を持つことが新しい資源評価におけるワークフローに必要だと考えています。作業や対応策ならその都度動けばいいだけですが、サービスは、保守やカスタマーの求める内容へのアップデートやフィードバックがしっかりサイクルの中に置かれるので、より頑健な資源評価につながると考えています。そういうStock assessment as a serviceを最後にいれたいところです。
Originally posted by @akimanabe in #5 (comment)
ところが本文ではSAaaSについては”あまり”語られていないのだ。
\subsection{Sustainable stock assessment}
We created a framework for using software development methodology in a fish stock assessment, not only for reporting but also for project management.
Because we implemented the report as a buildable document under the CI system,
every update to the source files triggered a build on a cloud computer,
and the generated report in HTML format (Fig \ref{fig:report}) was uploaded to a cloud storage service.
The CI system kept our report up to date with the source code and data.
The organization of the program and directory was kept clean because we branched our scenario using a version control system.
Issue-driven iterative development (\ref{table:glossary}) made our work traceable in terms of specific issues.
The branch-based workflow (\ref{table:glossary}) allowed us to compare multiple scenarios on pull requests and to review all decision-making processes;
it also helped us correct fundamental defects even after scenario branching.
By clarifying our tacit knowledge about the year lag between the data and the assessment,
we made our project maintainable for future updates.
@akimanabe たしかに、あまり触れていないですね。最後の最後に検討しましょう。
これももはやCloseでいいかもですね