The sciences of the artificial (3rd ed.)
The sciences of the artificial (3rd ed.)
Guide to the Software Engineering Body of Knowledge - SWEBOK
Guide to the Software Engineering Body of Knowledge - SWEBOK
Conceptual designing as a sequence of situated acts
Artificial Intelligence in Structural Engineering, Information Technology for Design, Collaboration, Maintenance, and Monitoring.
Model data management: towards a common solution for PDM/SCM systems
Proceedings of the 12th international workshop on Software configuration management
A general model of software architecture design derived from five industrial approaches
Journal of Systems and Software
An ontologically-based evaluation of software design methods
The Knowledge Engineering Review
Handshaking between software projects and stakeholders using implementation proposals
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Strategies for a creative future with computer science, quality design and communicability
HCITOCH'10 Proceedings of the First international conference on Human-computer interaction, tourism and cultural heritage
An assessment framework for identifying information technology programs
Proceedings of the 2011 conference on Information technology education
CORM: A reference model for future computer networks
Journal of Network and Computer Applications
Comparing two software design process theories
DESRIST'10 Proceedings of the 5th international conference on Global Perspectives on Design Science Research
| Hi-index | 0.00 |
How does software design compare with design in other disciplines? Using a general design framework--John Gero's Function-Behavior-Structure framework--as a reference, the author contrasts the software engineering process with processes in other engineering disciplines. The author summarizes FBS, then maps the elements and processes in the framework to artifacts and processes in the Rational Unified Process. He notes that software engineers use certain common terms, such as design, analysis, and documentation, in significantly different ways from other engineers. Moreover, the author finds that "design" in software engineering is more limited in scope than in other fields. Having a broader understanding of other engineering disciplines--and software engineering's place among them--can benefit software engineers involved in multidisciplinary projects. The author also discusses lessons applicable to research and to other aspects of software engineering.