Object-oriented software engineering As one of the primary sources of the Unified Modeling Language (UML), concepts and notation from OOSE have been incorporated into UML. The methodology part of OOSE has since evolved into the Rational Unified Process (RUP). The OOSE tools have been replaced. State-of-the-art coverage of Object-Oriented software engineering shows students how to use the most practical aspects of software engineering including the basic elements of UML (Unified Modeling Language), Java, Distributed Development, Rationale Management, Configuration Management, and Build- and Release Management.
Object-oriented software engineering (commonly known by acronym OOSE) is an object-modeling language and methodology.
OOSE was developed by Ivar Jacobson in 1992 while at Objectory AB. It is the first object-oriented design methodology to employ use cases to drive software design. It also uses other design products similar to those used by Object-modeling technique.
It was documented in the 1992 book Object-Oriented Software Engineering: A Use Case Driven Approach, ISBN0-201-54435-0
The tool Objectory was created by the team at Objectory AB to implement the OOSE methodology. After success in the marketplace, other tool vendors also supported OOSE.
After Rational Software bought Objectory AB, the OOSE notation, methodology, and tools became superseded.
- As one of the primary sources of the Unified Modeling Language (UML), concepts and notation from OOSE have been incorporated into UML.
- The methodology part of OOSE has since evolved into the Rational Unified Process (RUP).
- The OOSE tools have been replaced by tools supporting UML and RUP.
OOSE has been largely replaced by the UML notation and by the RUP methodology.
Main issues[edit]
Object Oriented Software Engineering Tutorial
- Software products can get very complex.
- High-quality results are expected.
- The development team can be large and distributed.
- Most projects add functionality to an existing product.
- OOSE produced a high level language.