1.a diagramatic representation of activities for next 1 hr with goal
the diagram should have each component numbered
2.placeholder programming,abstract progra..
when the idea is not concrete building a framework
it would involve functions and statics and visitors
a use case is when rearranging an existing code anticipating changes to incorporate
in next version.the existing code is supposed to fit in the current framework
3.refactoring code may be crude,rigid
issues, if layered code then
will have to shift one function from one layer to anoter,this means moving all dependendent functions in other layer.
this will break layer opaqueness, lower layer becomes visible in upper.
mostly happens when loop nuller(progressers) one is in top layer antother is in bottom
4.another way for a quick solution to above problem is ,
reduntant state and data structures, it will mirror the state in either layers and hence
can be used explicitly in a layer
sometimes to get a quick work around, we may have to shift processing of 1 layer to another
this would involve movement of 1 .c file and only implementing guest layer functions in it
