✳flâneur — a map of the web's best reading

Information distribution aspects of design methodology | the morning paper

blog.acolyer.org · 1,265 words · saved by 1 readers

We’re continuing with Liskov’s listthis week, and today’s paper is another classic from David Parnas in which you can see some of the same thinking as in ‘On the criteria….’ Parnas talks about the modules of a system (for contemporary feel, we could call them ‘microservices’ once more), how we end up with inadvertent tangling / coupling between microservices, and what we can do to prevent that. One of his key recommendations is that information about a microservice be carefully controlled – releasing information about how it works internally outside of the team that are working on it is not just unhelpful, it is positively harmful. Writing in 1971, this information communication was primarily through documentation, and so this is what Parnas discusses. I wonder if in 2016 he would make the claim “making the source code for a microservice available outside of the team working on it is harmful” ??? That would certainly be a statement likely to cause robust debate! Update: David Parnas hi

Information distribution aspects of design methodology Parnas, 1971 We’re continuing with Liskov’s list this week, and today’s paper is another classic from David Parnas in which you can see some of the same thinking as in ‘ On the criteria… .’ Parnas talks about the modules of a system (for contemporary feel, we could call them ‘microservices’ once more), how we end up with inadvertent tangling / coupling between microservices, and what we can do to prevent that. One of his key recommendations is that information about a microservice be carefull

Explore this link on the map →

related reading