Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/694305e8-d7f8-800e-a8d8-fbf410be6545
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== ② 実務上の対策 ==== * 書く側が安全性を担保 - 実装者が単体テスト・結合テスト・帳票桁依存まで確認 * 手順書・テスト設計の充実 - 外部レビューやQAが確認できる範囲を明確化 * 上位部門の重点チェック - 重要箇所や事故リスクの高いモジュールに絞る * 暗黙の前提として「書く側の理解・責任」が絶対 - 実務ではこれに依存せざるを得ない ===== 一言でまとめ ===== : 確認しきれない部分は現実に存在するが、事故防止や安全性はすべて「書く側の理解・テスト・責任」に依存する構造になっている 希望なら次に、誰がどこまでカバーしているか／カバーできない部分を可視化した図を作って整理することもできます。 作る？
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
