Re: [re-online] Abstraction Level and Mapping of Requirements.

From: Ajay Unni (DSL-UOW) (ajay@uow.edu.au)
Date: Wed Feb 11 2004 - 22:06:55 EST



This is a multi-part message in MIME format.

------=_NextPart_000_0089_01C3F0EB.5C48EDD0 Content-Type: text/plain;

        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Check the NFR framework (Non-functional requirements) by John Mylopoulos = et al.
You could also do a search on google.com that will lead you to more = lit..

NFR framework provides you with a way to refine high-level requirements = to more specific requirements. The notion of a softgoal requirement as a = high-level requirements is used instead. Example if your requirement is = to build a "pretty home page " then you can use the NFR framework to = refine it by specifying colours to be uses, fonts to be used, etc to = arrive at more specific and concrete low-level (in your words) = requirements.

cheers
ajay

  Hello,

  I am investigating aspects of abstraction level of requirements, i.e. = on
  what level a requirement can/should be specified regarding the aim of = the
  requirement. Aim could be e.g. who uses the req. and for what = purpose...
  Example:
  High level -> "...open standards should be supported"   ...
  Lower level -> "...the application should be compliant to USB2.0"

  I wonder if there has been any research regarding this aspect, as well = as
  the mapping of the high-low level requirements to each other, and to   company/product strategies.

  Would appreciate any tips, references and links.

  Best regards,

  Tony B. Gorschek
  PhD Student in Software Engineering


  Blekinge Institute of Technology
  School of Engineering
  PO Box 520, SE-372 25 Ronneby Sweden

  direct : +46 457-38 58 17
  mobile : +46 708-25 46 92
  phone  : +46 457-38 50 00
  fax    : +46 457-271 25
  e-mail : tony.gorschek@bth.se, tgo@bth.se
  url    : www.bth.se/ipd and http://194.47.142.27




=

-------------------------------------------------------------------------=


  To send a message to this mailing list send it to = re-online@it.uts.edu.au.
  To unsubscribe from this mailing list, email majordomo@it.uts.edu.au = with the
  message `unsubscribe re-online' in the BODY of the mail.

------=_NextPart_000_0089_01C3F0EB.5C48EDD0 Content-Type: text/html;

        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>Check the NFR framework (Non-functional requirements) by John =
Mylopoulos et=20
al.</DIV>
<DIV>You could also do a search on google.com that will lead you to more =

lit..</DIV>
<DIV>&nbsp;</DIV>
<DIV>NFR framework provides you with a way to refine high-level = requirements to=20
more specific requirements. The notion of a softgoal requirement as a = high-level=20
requirements is used instead. Example if your requirement&nbsp;is to = build a=20
"pretty home page " then you can use the NFR framework to refine it by=20 specifying colours to be uses, fonts to be used, etc to arrive at more = specific=20
and concrete low-level (in your words) requirements.</DIV>

<DIV>&nbsp;</DIV>
<DIV>cheers</DIV>
<DIV>ajay</DIV>
<BLOCKQUOTE=20

style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">   <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>   <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20
  <A title=3Dtony.gorschek@bth.se =
href=3D"mailto:tony.gorschek@bth.se">Tony=20   Gorschek</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A = title=3Dre-online@it.uts.edu.au=20
  href=3D"mailto:re-online@it.uts.edu.au">re-online@it.uts.edu.au</A> = </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, February 11, = 2004 12:56=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [re-online] = Abstraction Level=20
  and Mapping of Requirements.</DIV>
  <DIV><BR></DIV>Hello,<BR><BR>I am investigating aspects of abstraction = level=20
  of requirements, i.e. on<BR>what level a requirement can/should be = specified=20
  regarding the aim of the<BR>requirement. Aim could be e.g. who uses = the req.=20
  and for what purpose...<BR>Example:<BR>High level -&gt; "...open = standards=20
  should be supported"<BR>...<BR>Lower level -&gt; "...the application = should be=20
  compliant to USB2.0"<BR><BR><BR>I wonder if there has been any = research=20
  regarding this aspect, as well as<BR>the mapping of the high-low level =

  requirements to each other, and to<BR>company/product = strategies.<BR><BR>Would=20
  appreciate any tips, references and links.<BR><BR>Best=20   regards,<BR><BR><BR>Tony B. Gorschek<BR>PhD Student in Software=20
=

Engineering<BR><BR>________________________________________________<BR><B=
R>Blekinge=20
  Institute of Technology<BR>School of Engineering<BR>PO Box 520, SE-372 = 25=20
  Ronneby Sweden<BR><BR>direct : +46 457-38 58 17<BR>mobile : +46 708-25 = 46=20
  92<BR>phone&nbsp; : +46 457-38 50 00<BR>fax&nbsp;&nbsp;&nbsp; : +46 = 457-271=20
  25<BR>e-mail : <A =
href=3D"mailto:tony.gorschek@bth.se">tony.gorschek@bth.se</A>,=20   <A href=3D"mailto:tgo@bth.se">tgo@bth.se</A><BR>url&nbsp;&nbsp;&nbsp; = : <A=20
  href=3D"http://www.bth.se/ipd">www.bth.se/ipd</A> and <A=20
=

href=3D"http://194.47.142.27">http://194.47.142.27><BR><BR><BR><BR><BR=
>------------------------------------------------------------------------=
-------<BR>To=20
  send a message to this mailing list send it to <A=20
=

href=3D"mailto:
re-online@it.uts.edu.au">re-online@it.uts.edu.au</A>.<BR>T= o=20
  unsubscribe from this mailing list, email <A=20   href=3D"mailto:majordomo@it.uts.edu.au">majordomo@it.uts.edu.au</A> = with=20
  the<BR>message `unsubscribe re-online' in the BODY of the=20 mail.<BR><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0089_01C3F0EB.5C48EDD0--



To send a message to this mailing list send it to re-online@it.uts.edu.au. To unsubscribe from this mailing list, email majordomo@it.uts.edu.au with the message `unsubscribe re-online' in the BODY of the mail.

This archive was generated by hypermail 2.1.6 : Mon Feb 16 2004 - 09:00:15 EST