Aspect-Oriented Design Risk
"Donisthorpe C (AT)" <[email protected]> Fri, 2 Oct 2009 11:30:00 +0100
| Newsgroups | gmane.comp.programming.aspect.general |
|---|---|
| Message-ID | <0BA7EE4D4646E0409D458D347C508B78055DE7C7@MAILSERV1.uni.glam.ac.uk> |
This is a multi-part message in MIME format. --===============2573077376925576863== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA434B.4BB1C7B5" This is a multi-part message in MIME format. ------_=_NextPart_001_01CA434B.4BB1C7B5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi =20 Research into the causes of software fault scenarios show that conflicts = between crosscutting requirements and concerns during early development = contribute to software failure. This problem can be attributed to = mistakes made during early software development, whilst weaving together = requirements and architecture, and a failure to recognise adverse = crosscutting concerns. Despite an awareness of crosscutting concerns = existing risk management techniques using tools such as ATAM have failed = to properly address the problem during early development. Thus, = successful analysis and risk management of these problems using current = development methods remains difficult during the development of software = intensive systems. This is partly because Aspect Oriented Requirements = analysis (AORE) does not yet completely reveal these conflicts. In = addition, AORE is not always clear about managing the evolution of early = aspects from crosscutting requirements or how this can effect early = separation of concerns. This is a critical omission because it ignores = potential risk from early aspects when design from crosscutting = requirements and an early separation of concerns are developed. =20 =20 I am curious about other views in the community on this matter. =20 =20 Charles =20 ------_=_NextPart_001_01CA434B.4BB1C7B5 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <HTML dir=3Dltr><HEAD>=0A= <META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A= <META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18813"></HEAD>=0A= <BODY>=0A= <DIV dir=3Dltr id=3DidOWAReplyText73554>=0A= <DIV dir=3Dltr><FONT color=3D#000080 size=3D2 face=3D"Comic Sans MS">=0A= <P style=3D"TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt" = class=3DMsoNoSpacing><FONT color=3D#000000 size=3D3 = face=3DCalibri>Hi</FONT></P>=0A= <P style=3D"TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt" = class=3DMsoNoSpacing><FONT color=3D#000000 size=3D3 = face=3DCalibri></FONT> </P>=0A= <P style=3D"TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt" = class=3DMsoNoSpacing><FONT color=3D#000000 size=3D3 = face=3DCalibri>Research into the causes of software fault scenarios show = that conflicts between crosscutting requirements and = concerns during early development contribute to software failure. = This problem can be attributed to mistakes made during early software = development, whilst weaving together requirements and architecture, and = a failure to recognise adverse crosscutting concerns. <SPAN = style=3D"mso-spacerun: yes"> </SPAN>Despite an = awareness of crosscutting concerns existing risk management techniques = using tools such as ATAM have failed to properly address the problem = during early development. Thus, successful analysis and risk management = of these problems using current development methods remains difficult = during the development of software intensive systems.<SPAN = style=3D"mso-spacerun: yes"> </SPAN>This is partly because Aspect = Oriented Requirements analysis (AORE) does not yet completely reveal = these conflicts.<SPAN style=3D"mso-spacerun: yes"> </SPAN>In = addition, AORE is not always clear about managing the evolution of early = aspects from crosscutting requirements or how this can effect early = separation of concerns. </FONT><SPAN style=3D"LINE-HEIGHT: 115%; = FONT-FAMILY: 'Calibri','sans-serif'; FONT-SIZE: 11pt; = mso-fareast-font-family: Calibri; mso-bidi-font-family: 'Times New = Roman'; mso-fareast-language: EN-US; mso-ansi-language: EN-GB; = mso-bidi-language: AR-SA"><FONT color=3D#000000>This is a critical = omission because it ignores potential risk from early aspects when = design from crosscutting requirements and an early separation of = concerns are developed.<SPAN style=3D"mso-spacerun: yes"> = </SPAN></FONT></SPAN></FONT></P></DIV>=0A= <DIV dir=3Dltr><FONT size=3D2></FONT> </DIV></DIV>=0A= <DIV dir=3Dltr id=3DidSignature18631>=0A= <DIV><FONT color=3D#000000 face=3DCalibri>I am curious about other views = in the community on this matter.</FONT></DIV>=0A= <DIV> </DIV>=0A= <DIV><FONT color=3D#0000ff size=3D2><EM></EM></FONT> </DIV>=0A= <DIV><FONT color=3D#0000ff size=3D2><EM>Charles</EM></FONT></DIV>=0A= <DIV><FONT size=3D2 face=3DArial></FONT> </DIV></DIV></BODY></HTML> ------_=_NextPart_001_01CA434B.4BB1C7B5-- --===============2573077376925576863== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ discuss mailing list - [email protected] To unsubscribe and change options, go to: http://aosd.net/mailman/listinfo/discuss_aosd.net Check out the AOSD.net Wiki: http://aosd.net/wiki --===============2573077376925576863==--