My bias is toward "printable" documents. I like the idea of an HTML document that is directly printable. I've used tools like Flying Saucer (and appropriate CSS) to guarantee printability.
I like using ReStructured Text to create HTML and LaTeX that match precisely.
When I think of Literate Programming, I'm biased toward print.
However, HTML has a lot of power. Taking off the blinkers for a moment, one can see that rich HTML and Javascript may be a really workable approach.
Take a look at the Literate Molly Module: another tool for Literate Programming. This is an example of using rich HTML as a vehicle for literate programming.
Software Architect's Key Responsibility Areas(...
Prashant S Akerkar<noreply@blogger.com>
2010-04-29 06:28:23.075000-04:00
Software Architect's Key Responsibility Areas(KRA) 1.Identifying Business Needs. 2.Designing - High and Low Level Designs. 3.Creating Prototyping Model. 4.Possess Excellent Functional Domain Knowledge. 5.Identifying Technology,API,Framework viz Open Source, Microsoft, Sun Microsystems for the solution 6.Identifying SDLC Model viz Waterfall,Iterative,Agile for Project Execution 7.Write System Test Cases 8.Adhering to Quality Processes Standards for Software Products Development. Thanks & Regards, Prashant S Akerkar http://www.linkedin.com/in/prashantakerkar