✍️
Team FitBob
  • Introduction and Foreword
  • Motivation
  • Features
  • Tech Stack
  • Software Engineering Practices
    • Requirements
    • Software Design Patterns
      • Model View Controller (MVC)
      • Abstraction Occurrence Pattern
  • Deployments
    • Trying Our App
  • Activity diagram
  • Frontend
    • Login
    • User Registration
    • Client Screens
      • Client Dashboard
      • Client Profile
      • Eating History
      • Meals
    • Personal Trainer screens
      • Personal Trainer Profile
      • Personal Trainer Dashboard
        • Clients
        • Meal plans
        • Meals
    • Recipe screens
    • Search screen
    • Searching for Restaurants
    • Notes on BeautifulSoup and Flask
    • Request/Success/Failure Cycle
  • Backend
    • Notes on Django
    • API
    • Entity relationship diagram
  • Testing
    • User Testing
    • Backend
  • Project Limitations and Constraints
  • Closing Thoughts.
  • Project log
  • Poster
Powered by GitBook
On this page

Was this helpful?

  1. Software Engineering Practices
  2. Software Design Patterns

Abstraction Occurrence Pattern

Creating multiple components that mostly share the same properties.

PreviousModel View Controller (MVC)NextDeployments

Last updated 3 years ago

Was this helpful?

In our application, we often create similar components.

A good example would be rendering "food items" in a

Each "food item" is a component, with the following information:

  • title

  • calories

To achieve this, we created a component titled FoodItem, which is repeatedly used by the FlatList to create new components on the user's screen.

We made use of this design pattern in other parts of our application, and have collated a collection of such components in .

FlatList
this folder