This presentation shows how to do frontloading in software development in fundamental level, also called shift-left technique or W model. The main topic is software trap analysis / software failure mode analysis, a method of root cause analysis of (part of) software FMEA, which extracts patterns of bugs.
This slide describes an internal community on software engineering at Hitachi corporate group. Originally revealed at XP祭り2019 - conference on eXtreme Programming in Japan.
https://nagasaki-it-engineers.connpass.com/event/67240/ 3rd 長崎 Software Quality and Development Gathering にて行ったセッションのスライドです。セミナーではなく勉強会なので「私にはソフトウェアビジネスのコラボレーションはこう見えているけど皆さんはどうでしょう」というスタイルで話しました。あまりテクニカルなことは書いてありません。また、うまくいかない理由は多岐に渡りますが、おそらく皆さんが案外見ていないことを話しました。
Invited keynote on Software Symposium 2010 Japan. Talk about history of software engineering and the role of agile. Corrected recent words from Tom DeMarco, Ed Yourdon, Mary Poppendiec, Tom Gilb, Ivar Jacobson, ... and my thoughts.
This presentation shows how to do frontloading in software development in fundamental level, also called shift-left technique or W model. The main topic is software trap analysis / software failure mode analysis, a method of root cause analysis of (part of) software FMEA, which extracts patterns of bugs.
This slide describes an internal community on software engineering at Hitachi corporate group. Originally revealed at XP祭り2019 - conference on eXtreme Programming in Japan.
https://nagasaki-it-engineers.connpass.com/event/67240/ 3rd 長崎 Software Quality and Development Gathering にて行ったセッションのスライドです。セミナーではなく勉強会なので「私にはソフトウェアビジネスのコラボレーションはこう見えているけど皆さんはどうでしょう」というスタイルで話しました。あまりテクニカルなことは書いてありません。また、うまくいかない理由は多岐に渡りますが、おそらく皆さんが案外見ていないことを話しました。
Invited keynote on Software Symposium 2010 Japan. Talk about history of software engineering and the role of agile. Corrected recent words from Tom DeMarco, Ed Yourdon, Mary Poppendiec, Tom Gilb, Ivar Jacobson, ... and my thoughts.
2. Overengineering (or over-engineering,
[1]
or over-kill) is the act of designing a product or providing a solution to a problem in an overly
complicated manner, where a simpler solution can be demonstrated to exist with the same efficiency and effectiveness as that of the original
design.[2]
Overengineering differs from Planned Obsolescence which seeks to alter a design to produce an artificial limit on a product's lifespan or
otherwise make it unfashionable. Overengineering is often identified with design changes that increase a factor of safety, add functionality,
or overcome perceived design flaws that most users would accept.
Overengineering can be desirable when safety or performance is critical (e.g. in aerospace vehicles and luxury road vehicles), or when
extremely broad functionality is required (e.g. diagnostic and medical tools, power users of products), but it is generally criticized in terms of
value engineering as wasteful of resources such as materials, time and money.
wikipedia(英語版)より