I am working on a project in which the launch of software (C ++ / OO) is ported to a new hardware environment. A certain percentage of software modules should be subjectively similar on the new hardware platform.
A review of the code for some of these modules showed that the port done was done with minimal effort or insight - the developers doing this work were inexperienced, as is often the case with porting. However, he also showed that the software design is missing - too complex, does not cope well with errors, or simply has a bunch of "code smells."
I asked that instead of looking at the code after the port has been "completed", we’ll first consider the design. However, I was told that this might not be very useful, probably because the existing documented projects were not updated.
Am I barking the wrong tree? Is the development process initially slow? Is there any way to avoid getting bogged down in the full design process. Or is this code always the best way to figure it out - even with inexperienced coders?
Refresh. Thanks for answers. Yes, s / w will be used in many (hopefully) future products / versions. Also, I did not mention that the code will be multi-threaded (there was previously a single streaming environment). This in itself may be good enough to indicate "consider design." I would like to proactively (yuck) see if the design review process can be ported. I don’t trust just hoping to fix something when it stops working - if something is found in testing that will be fundamentally broken, I would prefer not to redesign the time to fix the defects.
source
share