Register now or log in to join your professional community.
All systems are becoming more and more dominated by software. The software applications are also becoming entities that are totally decoupled from the physical hardware that they run on. Yet software can not be seen as items interacting with each other without something else that enables the physical connection. Therefore they are not strictly systems as per INCOSE definition. How should we then think and handle software dominated systems?
Thanks for invitation, and I am really sorry for my late, because I were had a lot of work.
Yes it can .
Much of the thinking behind systems design / development is the same as with software design /development e.g. what’s the overall requirements, what interfaces do I have to handle, what are the performance criteria, how will I verify my end solution and get it accepted etc
.However, it is conditional upon the engineer in question having worked at a sufficiently high-level within his / her software development environment e.g. an engineer that had just been coding in assembler and has only operated at that level would find it more difficult to transition, whereas a software architect / designer would find it easier.
YES, the software can be seen as a whole system and its deployed security and functionality features need to be managed well with regards to system/software development lifecycle.
