Book a Demo

Author Topic: Requirement Status - Mandatory  (Read 4070 times)

reinmh

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Requirement Status - Mandatory
« on: July 29, 2008, 10:12:35 pm »
What is the requirement status "mandatory" for?

If i look at the available status for a requirement i see:
- proposed
- validated
- mandatory
- approved
- implemented

For my understanding the mandatory status does not fit in this group of status. Has anyone an idea for this status?

Thanks, Harald

Frank Horn

  • EA User
  • **
  • Posts: 535
  • Karma: +1/-0
    • View Profile
Re: Requirement Status - Mandatory
« Reply #1 on: July 29, 2008, 10:25:12 pm »
Looks like one of those classical intelligence test questions ("which word does not fit"?). Maybe they just want to test us...

Transition Technologies

  • EA User
  • **
  • Posts: 85
  • Karma: +0/-0
    • View Profile
Re: Requirement Status - Mandatory
« Reply #2 on: July 29, 2008, 11:53:09 pm »
Hi Harald,

Some requirements may have more significance than others in the project. That status is made to highlight the importance of given requirement. It may also indicate the hierarchy of actions related to requirements, showing that Mandatory should be fulfilled firstly.

Maybe the example will better describe it:
At the beginning of the modeling the status of each requirement is set to proposed. Some of them can be set as mandatory. After completing them the status is changed to Approved, Implemented or Validated.
« Last Edit: July 30, 2008, 12:00:43 am by transition »
Regards,
Transition Technologies
Authorized Reseller and Training Partner of Sparx Systems
www.ea.tt.com.pl

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Requirement Status - Mandatory
« Reply #3 on: July 30, 2008, 12:38:44 am »
I think EA will let you remove a status entry. Remember that these items are reference data, and that new projects will inherit whatever is in the 'seed' project that is copied when a new project is created.

You could edit these and export them, then import them into EABase or you custom seed project. Or you could remember to set them up (by hand or import) when new projects are created.

If you do edit EABase, remember that you will need to repeat this process whenever EABase is updated. At the very least this will happen when you update to a new version of EA. If you use patch files you should check each time whether a new file is included; if you run full installations for new builds you'll need to redo the change each time.

HTH, David
No, you can't have it!