MY BOOK REVIEW

OBJECT ORIENTED ANALYSIS and DESIGN

Book

Edward Yourdon and Carl Argila

Author

QA 76.64 Y68 1996

Reference no.

CHAPTER 4

If names are not correct, language will not be in accordance with the truth of things.

                                                                                                                            - Confucius

This chapter is to apply the techniques of Chapter 3 to develop a universe of application domain concept to the case study system. These efforts, as well as the object refinement effort in the next chapter, will the foundation for all subsequent analysis and design efforts. The initial set of concept that we develop in this chapter will be reviewed, discussed, debated and eventually revised. A great deal of the thought and consideration needs to go into this process since it form the basis for software re-used, their investment in this up front analysis will have dramatic pay offs when object re used. At the conclusion of this chapter we will have a list of application domain concept for the case study systems, they will used the LIA techniques of chapter.

You should begin by reviewing the cases study description given in chapter 3. You may wish to apply PFS as describe in chapter 3. PFA has the advantage of exhaustively revealing all concepts identified from the resources. Many of these concepts may be outside of the application domain or simple irrelevant, we will deal with these concept later.

A less rigorous technique would be to manually identify, from the text, words and phrases which you fell are application domain concepts. Look for key words and phrases which may suggest candidate objects. Keep in mind the application domain in which you are working. When you identify candidate concepts, are they truly part of the problem domain of elevator and magazine subscriptions, or are they simply part of an implementation aspect of the problem?

 As more challenging applications are automated, cooperative problem solving will be an important paradigm for the next generation of industrial intelligent systems. One of the key problems to use it in engineering domain is development of a structured design method. In this paper, an evolutionary, seamless, non-domain-specific object-oriented analysis (OOA) method is derived that starts at the definition of a software system and integrated knowledge engineering needs in a new manner, especially when following a deep knowledge approach. Based on this method, an expert-supported OOA tool environment (ESA) is presented that supports an analyst starting at the collection of the requirements through the analysis of any software system. And an example of simulative transformer substation system (STSS) is introduced to present some key problems and techniques of OOA up to a preliminary high-level design.

We expect user requirement to contain redundant, ambiguous, cunfusing and contradictory information that's why we do analysis.

We attempt  to identify all concept and let the user decide which may or may not be relevant.( It's not the job of the analyst to decide “Sociopathic Passenger” is or not is important for the user view of an elevator control system.)

The linguistic technique applied in this chapter provide us with a starting points for finding objects, but further refinement is necessary.