Essential systems analysis
Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Software aspects of strategic defense systems
Communications of the ACM
Functional documents for computer systems
Science of Computer Programming
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Automated consistency checking of requirements specifications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Formal refinement patterns for goal-driven requirements elaboration
SIGSOFT '96 Proceedings of the 4th ACM SIGSOFT symposium on Foundations of software engineering
Software engineering: an unconsummated marriage
Communications of the ACM
What we teach software engineers in the university: do we take engineering seriously?
ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Object-Oriented Software Construction
Object-Oriented Software Construction
Computer
A Formal Specification of an Oscilloscope
IEEE Software
Taking more of the soft out of software engineering
IWSSD '93 Proceedings of the 7th international workshop on Software specification and design
System development (Prentice-Hall International series in computer science)
System development (Prentice-Hall International series in computer science)
Hints for Computer System Design
IEEE Software
Proposal for evaluation of software reusability assessment approach employing a mixed method
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
Software engineering is discussed with particular reference to software-intensive application systems--those whose fundamental purpose is to bring about desired effects in a physical and human problem world by interaction with a programmed machine . Such systems bring together a problem world--typically composed of non-formal heterogeneous domains--and the formal or semi-formal domain of the machine. Clean engineering separation of the two is rarely, if ever, possible; and treating the problem world as an extension of the formal machine is hard because of its non-formal nature. Software engineers can learn from the structure and practices of the established branches of engineering--their treatment of formal analysis and reasoning, their practice of intense specialisation, and their attention to particular instances no less than to general concerns. Above all we can learn from their reliance on normal artifact design and normal design disciplines--both the golden fruit of specialisation.