Different Languages For Different Phases

"The industry's eternal thirst for simple solutions to complex problems (Every Complex Problem Has a Solution) drives many to declare that the best software development method would use the same notations for software representation throughout the entire development life cycle. Since this is not the case in any other engineering discipline, why should it be in software engineering?"

"Notations provide us with models that can be manipulated in our minds. The more notations and the richer and more diverse the representations used, the better we can visualize the product under construction."

For requirements engineering, select a set of optimal techniques and languages:

• Use the Right Techniques
• Use Multiple Views of Requirements

For design, select a set of optimal techniques and languages:

• Evaluate Alternatives
• Design Is Multidimensional

For coding, select an optimal language:

• Use Appropriate Languages
• Programming Language Is Not an Excuse

"Transitions between phases are difficult. Using the same language doesn't help. On the other hand, if a language is optimal for certain aspects of two phases, by all means use it."


Reference:
Matsubara, T., "Bringing up Software Designers," American Programmer, July-August 1990.