Page 296 -
P. 296

CHAPTER 10  SYSTEM ENGINEERING                                     267

                              REFERENCES

                              [CRI92]  Christel, M.G. and K.C. Kang, “Issues in Requirements Elicitation,” Software
                              Engineering Institute, CMU/SEI-92-TR-12 7, September 1992.
                              [GRA69] Graham, R.M., in Proceedings 1969 NATO Conference on Software Engineer-
                              ing, 1969.
                              [GUT99] Guttman, M., “Architectural Requirements for a Changing Business World,”
                              Research Briefs from Cutter Consortium (an on-line service), June 1, 1999.
                              [HAR93] Hares, J.S., Information Engineering for the Advanced Practitioner, Wiley, 1993,
                              pp. 12–13.
                              [HAT87] Hatley, D.J. and I.A. Pirbhai, Strategies for Real-Time System Specification,
                              Dorset House, 1987.
                              [MAR90] Martin, J., Information Engineering: Book II—Planning and Analysis, Prentice-
                              Hall, 1990.
                              [MOT92] Motamarri, S., "Systems Modeling and Description," Software Engineering
                              Notes, vol. 17, no. 2, April 1992, pp. 57–63.
                              [SOM97] Somerville, I. and P. Sawyer, Requirements Engineering, Wiley, 1997.
                              [SPE93] Spewak, S., Enterprise Architecture Planning, QED Publishing, 1993.
                              [THA97] Thayer, R.H. and M. Dorfman, Software Requirements Engineering, 2nd ed.,
                              IEEE Computer Society Press, 1997.


                              PROBLEMS AND POINTS TO PONDER
                              10.1. Find as many single-word synonyms for the word system as you can. Good
                              luck!
                              10.2. Build a hierarchical "system of systems" for a system, product, or service with
                              which you are familiar. Your hierarchy should extend down to simple system ele-
                              ments (hardware, software, etc.) along at least one branch of the "tree."
                              10.3. Select any large system or product with which you are familiar. Define the set
                              of domains that describe the world view of the system or product. Describe the set
                              of elements that make up one or two domains. For one element, identify the techni-
                              cal components that must be engineered.

                              10.4. Select any large system or product with which you are familiar. State the
                              assumptions, simplifications, limitations, constraints, and preferences that would
                              have to be made to build an effective (and realizable) system model.
                              10.5. Business process engineering strives to define data and application architec-
                              ture as well as technology infrastructure. Describe what each of these terms means
                              and provide an example.
                              10.6. Information strategy planning begins with the definitions of objectives and
                              goals. Provide examples of each from the business domain.
   291   292   293   294   295   296   297   298   299   300   301