Continuous design
Evolutionary design, continuous design, evolutive design, or incremental design is directly related to any modular design application, in which components can be freely substituted to improve the design, modify performance, or change another feature at a later time.
Software architects and software developers should use "fitness functions" to continuously keep the software system in check.[1]
Informatics
[edit]In particular, it applies (with the name continuous design) to software development. In this field it is a practice of creating and modifying the design of a system as it is developed, rather than purporting to specify the system completely before development starts (as in the waterfall model). Continuous design was popularized by extreme programming. Continuous design also uses test driven development and refactoring. Martin Fowler wrote a popular book called Refactoring, as well as a popular article entitled "Is Design Dead?", that talked about continuous/evolutionary design. James Shore wrote an article in IEEE titled "Continuous Design".
Industrial design Project
[edit]Modular design states that a product is made of subsystems that are joined together to create a full product.[2] The above design model defined in electronics and evolved in industrial design into well consolidated industrial standards related to platform concept and its evolution.[3]
See also
[edit]References
[edit]- ^ Fundamentals of Software Architecture: An Engineering Approach. O'Reilly Media. 2020. ISBN 978-1492043454.
- ^ Ulrich K (1995) The role of product architecture in the manufacturing firm. Res Policy 24(3):419–441. doi:10.1016/0048-7333(94)00775-3, 1995
- ^ Muffatto M (1999) Platform strategies in international new product development. Int J Opera Prod Manag 19(5/6):449–460. doi:10.1108/01443579910260766
External links
[edit]
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |