If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Thanks for sharing the paper. It is a nice compilation
of points to think of, thus defining a standard

To be a bit picky:
We are talking here about systems thaat cost >150k$
(15k$ maintenance a year) or are high risk.

In order to simplify life of university staff and to bring even
more structure to the process (and thus potential to reduce
costs), I would not just ask for some kind of software/system
architecture (Ch 2.3), but for a certain type of approach
(Kruchten, Hofmeister et al./Siemens Four View,...). Otherwise,
you will get an inconsistent bunch of self-defined views on
system/software architecture.

One then can say "Yes, we have that document" (thus be compliant)
but whether it can be used or not does not matter (see our recent
discussion about BCM and other standards in the DR and BCM forum )

Cheers

If the only tool you have is a hammer, you tend to see every problem as a nail.
(Abraham Maslow, Psychologist, 1908-70)