Software Design Flashcards
(6 cards)
Software Design levels
Architecture: Defines components and their relations.
High level design : defines interactions between components.
Detailed Design: Defines logical structure of each module.
Why software design
Enables multiple developers to work in parallel
Smaller components are easier to maintain
Ensures better software performance
Desired level of abstraction can be brought in the program
Components with high cohesion can be re - used again
Concurrent execution can be made possible
Ensures security objectives are met
Cohesion
Vs
Coupling
Cohesion: The degree of intra - dependability within elements
of a module . The greater the cohesion , the better is
the program design .
Coupling: The level of inter - dependability among modules of a
program . It tells at what level the modules interfere
and interact with each other . The lower the coupling ,
the better the program .
Front End
Vs
Back End
Front End: Also called “ client - side “ , is what happens in the
browser . It’s everything the user sees and interacts
with .
Backend : Also called “ server - side “ , happens on the server and
the database . It’s the machinery that works behind
the scenes to power those fancy features users
interact with on the client - side .
Native
Vs
Hybrid
Native :
Faster Performance
Better User Experience
Easier access to device ( GPS , Calendar , … )
Hybrid:
Faster to Market
Lower development cost
Less maintenance cost
( Also known as Cross - Platform )
What is an API
Application Programming Interface
An API is a software - to - software interface , not a user
interface . With APIs , applications talk to each other
without any user knowledge or intervention .
Amazon released its API so that developers could access
Amazon’s product information . Using the Amazon API , a
third - party website can post direct links to Amazon
products with updated prices and an option to “ buy now . “
