Xref: utzoo comp.software-eng:5452 comp.infosystems:233
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!tamuts.tamu.edu
From: n067az@tamuts.tamu.edu (Michael Futrell)
Newsgroups: comp.software-eng,comp.infosystems
Subject: integration ...
Message-ID: <15256@helios.TAMU.EDU>
Date: 24 Apr 91 18:06:54 GMT
Sender: usenet@helios.TAMU.EDU
Followup-To: comp.software-eng
Organization: Texas A&M University
Lines: 24



Integrated Information Systems, Integrated CaSe Tools,
Integrated Project Management Systems, Integrated hardware/software
systems ....

"Integration" is a popular term these days.  We're trying to get a
working definition of what constitutes an "integrated system" from an
industrial point of view.  We've come up with some issues that we
feel an integrated system should consider, including:

- Sharing of Common Data (and protection of private data)
- Look and Feel (common across all tools, or unique?)
- Change propogation (information consistency)
- Flexibility to change (system expansions and evolution)

What basic functionality would you expect from an integrated system?  
What types of operations would you expect to be able to perform?
What about the underlying architecture (object manager?  conceptual schema?)
Your opinions would be appreciated ...

Thanks,
Mike Futrell
mtf4051@summa.tamu.edu  <-**** NOTE address, please.