System and Software Requirements - SPICE & IEEE

[Geert Bellekens]

So I was bound to work with a non-existing meta-model and bloated processes that were once designed for a different department and a stack of dozents of Word templates which had to be filled with useless words just for the sake of being filled and once that happened they could report that we have reached a new milestone.  

Oh, I couldn't have said it better. Can I pls use this quote?

Geert

[ebeb]

Oh, I couldn't have said it better. Can I pls use this quote?

Geert

Sure!

...

...Damn...I should have spell-checked before  


EDIT: Funny, this forum replaces d.a.m.n with d.a.r.n I didn't know that it is such a bad word  

[Geert Bellekens]

thx,

Yeah, I've noticed the "darn" thing as well. Probably some kind of puritan US thing build into YABB

Geert

[ebeb]

Yeah, I've noticed the "darn" thing as well. Probably some kind of puritan US thing build into YABB

Yeah, crazy people...  8-)

*duck my head*

[ebeb]

Ok,

here's another question: Where to put the UI design/prototyping? IEEE says SRS, I'd say SyRS because its the interface to the system for the user (eventhough its mainly implemented by software).

Any other opinions?

[beginner]

SyRS and SRS are two different views of your model. Place the GUI design in your model. The view is irrelevant as long as it is visible at all.

b.

[ebeb]

SyRS and SRS are two different views of your model. Place the GUI design in your model. The view is irrelevant as long as it is visible at all.

Yes, to generate a RS, I can simply grab any package a need and feed it to the rtf generator. But, I'd like to have my models well-structured within my project. And that's why I started this discussion because I think SPICE offers a good way of structuring according to its engineering and other processes.

I don't want to have a couple models like e.g. "customer requirements", "use case model", "UI model", "class model" and so on in the highes level of hierarchy eventhough it doesn't matter for the resulting document or what you call view.

[beginner]

I wasn't talking about EA View Model Element, but General Views. A View is a Perspective. You define what the view is. For EA (and other modelling tools) this means you select those elements (for a printout) which suit you. Your SyRS will focus on requirements. Your SRS more on the logical design elements.

b.

[Geert Bellekens]

Oh, I couldn't have said it better. Can I pls use this quote?

Geert

Sure!

...

...darn...I should have spell-checked before  


EDIT: Funny, this forum replaces d.a.m.n with d.a.r.n I didn't know that it is such a bad word  

Jan,

I've used your quote on my article about modelling methods at http://themodelfactory.org/Modelling_Method

I just removed an extra "t" in "dozents"  

Geert

[ebeb]

I've used your quote on my article about modelling methods at http://themodelfactory.org/Modelling_Method

I feel honoured! Thanks!

I just removed an extra "t" in "dozents"

Oops, I knew there must be something...

Cheers,

Jan

[son-of-sargasso]

Yeah, fine.  Now what am I going to with my dozents of word templates?
 

[ebeb]

burn 'em!  [smiley=evil.gif]

[Dave.B]

What's the reference to the SPICE book that has been cited?

Regards
Dave B.

[ebeb]

It's a very helpful book - but it's in german And it's not a translation from english so I doubt you will find it in english.

SPICE Book