[Image Processing Engineer Column] Specification Document
アポロ精工 アポロ精工 新横浜オフィス（旧ケーアイテクノロジー/旧市川ソフトラボラトリー）
"Since it was outsourced, only the source code and circuit diagrams remain, and there is no specification document." Looking at this theme, I think many people can relate, so I wanted to share it. First of all, we also want to avoid getting involved in the above situation. I want to convey that. While it is possible to create a "pseudo specification document" by diligently stepping through the source code and circuit diagrams, we cannot trace back to understand "why that method was implemented." When we design ourselves, we create a specification document first, so when we are unsure about the means of implementation, we can refer back to the specification to understand "which method should be used for implementation." Of course, since it is the initial specification document, there are times when we realize "this specification is better" or "this specification has contradictions" while designing, and it is quite common to revise the specification document after completing the design (it is rare not to revise it). I believe it is smoother to think of it as something that cannot be reversed, like finding a dam when going upstream. *News is distributed through our company's newsletter.
Related product information
