Object Oriented Software Engineering   View all facts   Glossary   Help
subject > criterion > principle > approach to identifying generalizations > bottom-up approach to identifying generalizations
Next approach to identifying generalizationstop-down approach to identifying generalizations    Upapproach to identifying generalizations, bottom-up design

bottom-up approach to identifying generalizations
subjectfact 
bottom-up approach to identifying generalizationsgroups similar classes creating a new superclass2001-08-30 14:54:42.0
is a subtopic of 5.8 - The Process Of Developing Class Diagrams2001-08-30 14:54:42.0
is an instance of approach to identifying generalizations2001-08-30 14:54:42.0
is an instance of bottom-up design2001-08-30 14:54:42.0
bottom-up designhas advantage normally useful so that reusable components can be created; these can then be used in several places in the overall system2001-08-30 14:54:42.0
designdetermines how components will be implemented in a system2001-08-30 14:55:14.0
has goals
  • Increasing profit by reducing cost and increasing revenue
  • Ensuring that we actually conform with the requirements, thus solving the customers' problems
  • Accelerating development, which helps reduce short-term costs, and may also ensure the software reaches the market soon enough to effectively compete
  • Increasing qualities such as usability, efficiency, reliability, maintainability, and reusability which can help reduce costs and also increase revenues
2001-08-30 14:55:14.0
has part detailed design2001-08-30 14:55:14.0
has part modelling2001-08-30 14:55:14.0
has part programming2001-08-30 14:55:14.0
has part software architecture^22001-08-30 14:55:14.0
has part systems engineering2001-08-30 14:55:14.0
has part user interface design2001-08-30 14:55:14.0
requires considerable experience2001-08-30 14:55:15.0
see also design^22001-08-30 14:55:15.0