Drilldown: references
- Choose a table:
- acronyms (148)
- references (162)
references > article
:
The Paradox of Software Architecture and Design
or
None
& date
:
1981
or
1990
or
2001
or
2009 ![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
![](/extensions/Cargo/drilldown/resources/filter-x.png)
Click on the filter values below to narrow your results.
Discovering Requirements: How to Specify Products and Services (1) ·
IEEE Std. 1069-2009 Standard for Information Technology—Systems Design—Software Design Descriptions (1) ·
Managing and Leading Software Projects (4) ·
Peer Reviews in Software: A Practical Guide (1) ·
Requirements Engineering: From System Goals to UML Models to Software Specifications (1) ·
Software Engineering Economics (1) ·
Towards a Business Maintenance Model, Proc. Int’l Conf. Software Maintenance (1) ·
What Engineers Know and How They Know It (1)
Showing below up to 11 results in range #1 to #11.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)