A critical factor in efficient product development is defining the system requirements in a product development team environment. This paper describes the implementation of a strategy for defining meaningful system and subsystem requirements within a predominantly hardware-oriented engineering culture.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.