tag:blogger.com,1999:blog-5644053343415781270.post4561792116076739938..comments2023-11-02T12:20:59.889+01:00Comments on Managing Automotive Software Architectures: Architecture for small systems?Ulrikhttp://www.blogger.com/profile/15831528373591728862noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5644053343415781270.post-18558235735969558352010-10-30T21:14:35.606+02:002010-10-30T21:14:35.606+02:00It is not such a wild idea at all! Maybe we could ...It is not such a wild idea at all! Maybe we could collect whatever resources we can find on architecture for "small" systems? In case there's nothing, then yeah, you should probably write a book ;) If I remember correctly 37signals have some ideas in their first book (available online). <br /><br />It would be interesting to see how architecture descriptions (formal or the back of a napkin kind) differs between small and large. How is, for example, traceability addressed in smaller systems? Are all parts of a SA Description applicable and of similar importance in small systems as in large systems?<br /><br />Btw, the issue of course literature only being applied to large scale systems is not limited to the SA course. Professors in general, and your colleagues, would do good with this realisation once in a while. Large is good, but most of us start out working on small(er) systems, or subsystems.Marcus Ljungbladhttp://ljungblad.nunoreply@blogger.com