MIDTERM_REVIEW.docx.pdf | Download for quality grades |

Document Content and Description Below

o MODEL  Describe what this model has to do  Model information, starter (finish this model function) o CONTROLLER  Describe what this controller does  Given some code, finish this con... troller o VIEW  Describe what this view needs to do  Finish the view code o DDL  SQL code that creates a table  Model 1 vs. Model 2 o Model 1 code for application database and display logic is intermixed in a single monolithic page. Difficult to decipher. Spaghetti code very tanged set of interactions. o Mix of things in same space. o Good for simple applications o Becomes messy when:  Application logic is complicated  Error/security reporting requirements are robust  It needs to be debugged or changes made o Problem: solving three issues in one place Database logic, presentation logic, business logic o Solution: separate three issues into three places o Model 2- Model View Controller  Model: interacts with the database, queries, inserts, updates, deletes  View: presents data to the user, usually html  Controller- encapsulates “business logic”, validation parameters, interacts with model and view o Flow of a web request [Show More]

Last updated: 1 year ago

Preview 1 out of 3 pages