Article Discussion: Architectured RAD: Tackling the Challenges of on Demand Business

If you have any questions or comments on this article then please post them here.

This forum post relates to this article

I have few questios to the authors of these interesting articles:

Formalism is crucial in developing software for critical systems, but the limits of modeling reality must be taken into account: (a) the actual system has properties beyond the model, and (b) mathematical methods cannot handle all aspects of system development. No comprehensive approach to developing critical systems will, in the foreseeable future, be entirely formal while informal approaches alone cannot provide adequate confidence. Our approaches must be driven by the need to systematically and realistically balance and integrate mathematical and nonmathematical aspects of software development.

Question 1:
How ARAD process adresses these issues?


As an example, the Space Shuttle software, one of the largest and most ambitious software development projects of the 1970's, contains about 400,000 lines of code. NASA put enormous amounts of money into its development and still spends approximately $100,000,000 a year to maintain it.

Question 02:
If Space shuttle software were created in the year, say 2002. How much money NASA could save to maintain it?