22 CRITERIA FOR OBJECT ORIENTATION $2.2 Only you,the reader,can answer this question relative to your own context.Several reasons suggest that some compromises may be necessary: "Object-oriented"is not a boolean condition:environment A,although not 100% O-O,may be"more"O-O than environment B;so if external constraints limit your choice to A and B you will have to pick A as the least bad object-oriented choice. Not everyone will need all of the properties all the time. Object orientation may be just one of the factors guiding your search for a software solution,so you may have to balance the criteria given here with other considerations. All this does not change the obvious:to make informed choices,even if practical constraints impose less-than-perfect solutions,you need to know the complete picture,as provided by the list below. Categories The set of criteria which follows has been divided into three parts: Method and language:these two almost indistinguishable aspects cover the thought processes and the notations used to analyze and produce software.Be sure to note that (especially in object technology)the term "language"covers not just the programming language in a strict sense,but also the notations,textual or graphical, used for analysis and design. Implementation and environment:the criteria in this category describe the basic properties of the tools which allow developers to apply object-oriented ideas. Libraries:object technology relies on the reuse of software components.Criteria in this category cover both the availability of basic libraries and the mechanisms needed to use libraries and produce new ones. This division is convenient but not absolute,as some criteria straddle two or three of the categories.For example the criterion labeled "memory management"has been classified under method and language because a language can support or prevent automatic garbage collection,but it also belongs to the implementation and environment category;the"assertion"criterion similarly includes a requirement for supporting tools. 2.2 METHOD AND LANGUAGE The first set of criteria covers the method and the supporting notation. Seamlessness The object-oriented approach is ambitious:it encompasses the entire software lifecycle. When examining object-oriented solutions,you should check that the method and language,as well as the supporting tools,apply to analysis and design as well as implementation and maintenance.The language,in particular,should be a vehicle for thought which will help you through all stages of your work.22 CRITERIA FOR OBJECT ORIENTATION §2.2 Only you, the reader, can answer this question relative to your own context. Several reasons suggest that some compromises may be necessary: • “Object-oriented” is not a boolean condition: environment A, although not 100% O-O, may be “more” O-O than environment B; so if external constraints limit your choice to A and B you will have to pick A as the least bad object-oriented choice. • Not everyone will need all of the properties all the time. • Object orientation may be just one of the factors guiding your search for a software solution, so you may have to balance the criteria given here with other considerations. All this does not change the obvious: to make informed choices, even if practical constraints impose less-than-perfect solutions, you need to know the complete picture, as provided by the list below. Categories The set of criteria which follows has been divided into three parts: • Method and language: these two almost indistinguishable aspects cover the thought processes and the notations used to analyze and produce software. Be sure to note that (especially in object technology) the term “language” covers not just the programming language in a strict sense, but also the notations, textual or graphical, used for analysis and design. • Implementation and environment: the criteria in this category describe the basic properties of the tools which allow developers to apply object-oriented ideas. • Libraries: object technology relies on the reuse of software components. Criteria in this category cover both the availability of basic libraries and the mechanisms needed to use libraries and produce new ones. This division is convenient but not absolute, as some criteria straddle two or three of the categories. For example the criterion labeled “memory management” has been classified under method and language because a language can support or prevent automatic garbage collection, but it also belongs to the implementation and environment category; the “assertion” criterion similarly includes a requirement for supporting tools. 2.2 METHOD AND LANGUAGE The first set of criteria covers the method and the supporting notation. Seamlessness The object-oriented approach is ambitious: it encompasses the entire software lifecycle. When examining object-oriented solutions, you should check that the method and language, as well as the supporting tools, apply to analysis and design as well as implementation and maintenance. The language, in particular, should be a vehicle for thought which will help you through all stages of your work