Chapter27 - 27 Object-oriented analysis F ocused initially...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
27 Object-oriented analysis F ocused initially on the implementation aspects of software construction, the object- oriented method quickly expanded to cover the totality of the software lifecycle. Of particular interest has been the application of O-O ideas to the modeling of software systems, or even of non-software systems and issues. This use of object technology to present problems rather than solutions is known as object-oriented analysis. In the past few years, many books have appeared on the topic and many specific methods of object-oriented analysis have been proposed. The bibliography section lists some of the best-known books, and Web addresses for some of the best-known methods. Most of the concepts introduced in the preceding chapters are directly relevant to object-oriented analysis. Here we will briefly review what make object-oriented analysis special among other object-oriented topics, and what makes object-oriented analysis different from other analysis methods. Two points of terminology to avoid imagining differences where none exist. First, you will encounter, as a synonym for “analysis”, the term system modeling , or just modeling . Second, the computing science community tends to use the word specification where information modeling folks talk about analysis; in particular, computing scientists have devoted considerable efforts to devising methods and languages for formal specification using mathematical techniques for purposes of system modeling. The goals are the same, although the techniques may differ. In the past few years the two communities — information modelers and formal specifiers — have been paying more attention to each other’s contributions. 27.1 THE GOALS OF ANALYSIS To understand analysis issues we must be aware of the roles of analysis in software development and define requirements on an analysis method. Tasks By devoting time to analysis and producing analysis documents we pursue seven goals:
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
OBJECT-ORIENTED ANALYSIS § 27.1 904 If analysis is being applied to a non-software system, or independently of a decision to build a software system, A1 , A2 and A3 may be the only relevant goals. For a software system, the list assumes that analysis follows a stage of feasibility study which has resulted in a decision to build a system. If, as sometimes happens, the two stages are merged into one (not an absurd proposition, since you may need an in-depth analysis to determine whether a satisfactory result is conceivable), the list needs another item: A0, deciding whether to build a system. Although related, the goals listed are distinct, prompting us in the rest of this chapter to look for a set of complementary techniques; what is good for one of the goals may be irrelevant to another. Goals
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 20

Chapter27 - 27 Object-oriented analysis F ocused initially...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online