Aspect-orientated software engineering certainly seems useful. We've looked at a number of software engineering projects that failed due to poor organization, planning, and communication. Aspect-orientated software engineering seems to directly combat that by identifying relationships between requirements and components, beyond the level of a simple T chart or a bunch of circles connected with lines.
The separation of concerns concept is something that we've been taught since the beginning, as methods and subroutines do exactly that. We were taught to make each function do one thing, and if something in a program appears multiple times, we should probably make a subroutine out of it. And while it may be more time consuming to piece together a puzzle with smaller pieces instead of big pieces, you can get a much tighter and problem free fit from the smaller pieces.
No comments:
Post a Comment