Object-oriented analysis has become a key issue in today’s analysis paradigm. It is without question the most important element of creating what may be called the “complete” requirements of a system. Unfortunately, the industry is in a state of controversy about the approaches and tools that should be used to create object systems. This chapter will focus on developing the requirements for object systems and the challenges of converting legacy systems. Therefore, many of the terms will be defined based on their fundamental capabilities and how they can be used by a practicing analyst (as opposed to a theorist!).
KeywordsState Transition Diagram Component Object Transportation Vehicle Purchase Order Parent Object
Unable to display preview. Download preview PDF.
- 15.Grady Booch, Object Solutions: Managing the Object-Oriented Project, Addison-Wesley Publishing Co., p. 305.Google Scholar
- 16.James Martin, James Odell, Object-Oriented Methods, Prentice-Hall, p. 158.Google Scholar
- 17.A tree is a data structure containing zero or more nodes that are linked together in a hierarchical fashion. The topmost node is called the root. The root can have zero or more child nodes, connected by links; the root is the parent node to its children. Each child node can in turn have zero or more children of its own. (Microsoft Press, Computer Dictionary, 2nd ed., p. 397).Google Scholar
- 21.RAD is defined as “an approach to building computer systems which combines the Computer-Aided Software Engineering (CASE) tools and techniques, user-driven prototyping, and stringent project delivery time limits into a potent, tested, reliable formula for top-notch quality and improvement.” (James Kerr, Richard Hunter, Inside RAD, McGraw-Hill, Inc., p. 3.)Google Scholar