QuoteOriginally posted by: outrunQuoteOriginally posted by: CuchulainnQuoteOriginally posted by: outrunWould it be a good idea to write down some "requirements"? And then analyze some design variants that cover those?Problem requirements (1-factor, n-factor, equity, IR) or software requirements (efficiency, interoperabiliy,...)?Both, and the choices depend on who you want to service.E.g. if I would make a framework I would service the C++11 && finance sector with building blocks (libraries) that are well designed and are compatible with existing C++11 concepts. Since it's C++ I would also focus on performance.I am not a large s/w company with a bunch of progammers and a sales team so this is not one of the scenarios.
Last edited by Cuchulainn
on January 30th, 2014, 11:00 pm, edited 1 time in total.