Premium
4.1.0 Panel 4.1.0: Requirements Engineering for Software vs. Systems in General?
Author(s) -
Kaindl H.,
Griego R.,
Hause M.,
Hood C.,
Mannion M.
Publication year - 2007
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2007.tb02896.x
Subject(s) - software requirements , computer science , software engineering , requirement , requirements engineering , social software engineering , software development , requirements analysis , enterprise software , software system , software requirements specification , systems engineering , software , software construction , engineering , knowledge management , programming language
Requirements Engineering is dealt with concurrently and largely separately by a software‐based requirements engineering community anchored in the IEEE and by the INCOSE Requirements Working Group. Apart from such organizational issues, are there fundamental technical differences between Requirements Engineering for software vs. systems in general? It seems as though even functional requirements can mean something more general for a system including mechanical parts than for software alone. Quality requirements on safety deal with humans and their relationship with some real artifacts in their environment, so they cannot be dealt with by software alone. However, reliability of underlying software will be important in this context. While the internal structure of software will not normally be specified in its requirements, structure of a more general system may well be. These are just examples of what should be discussed. With regard to intelligent enterprises, there exist defined methodologies for enterprise modeling. Much as any other complex system, an enterprise may be better understood through modeling. Once an enterprise is better understood, it may be easier to make it intelligent. Whatever technical system is to be developed in an enterprise, it needs to fit into. By connecting enterprise modeling and requirements engineering, the likelihood of such a fit is increased. For software development, such connections have been worked out and are part of defined methodologies, some of them based on object‐oriented modeling. Are they applicable to the development of general systems? The software‐based requirements engineering community and the INCOSE Requirements Working Group have been slowly getting in touch with each other recently. This panel should help to discover more common ground and to exchange ideas on the commonalities and the differences of their respective tasks and methodology.