There very lit­tle design­ing in soft­ware designs nowa­days, or ever for that mat­ter. I will at least raise an eye­brow when some­thing writ­ten in Word is called a soft­ware design. Here’s what I think about soft­ware designing:

• Soft­ware design­ing and Microsoft Office do NOT mix.
• Soft­ware design­ing should at least have some­thing to do with pic­tures not ONLY with text
• Soft­ware design­ing is rarely per­formed well by peo­ple who are adamant on wear­ing ties

Test Dri­ven Require­ments engi­neer­ing in App­works (PDF Dutch)

Soft­ware Design EXECUTION

Achiev­ing Aligment

• Mind the Gap
• Stream­lin­ing Soft­ware Project Documentation
• Cen­tral­iz­ing Doc­u­ment Control
• Intro­duc­ing Soft­ware Requirements
• Soft­ware Require­ments & Scope Determination
• Soft­ware Require­ments & Time Estimation
• Test Dri­ven Require­ments engi­neer­ing (TDR) Lifecycle

Test Dri­ven Require­ments engi­neer­ing (TDR) Visualizations

• Reverse Engi­neered Design
• Stake­hold­ers in the Soft­ware Design Process
• The “4-minute-mile” factor
• Ben­e­fits of TDR Visualizations
• Con­struct­ing TDR Visualizations
• Step #1: Deter­min­ing Ini­tial Needs
• Step #2: Model Exist­ing Graph­i­cal User Interfaces
• Step #3: Cre­ate Your Graph­i­cal User Inter­face Template
• Step #4: Cre­ate Your TDR Visualization

Test Dri­ven Require­ments engineering

• Test Dri­ven Requirements
• Soft­ware Design Role Integration
• Reverse Engi­neer­ing Soft­ware Requirements
• The Struc­ture of Proven Principles
• The Syn­tax of Test Dri­ven Requirements