Presentation is loading. Please wait.

Presentation is loading. Please wait.

CS 160: Software Engineering September 10 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak www.cs.sjsu.edu/~mak.

Published byLambert Garrett Modified over 9 years ago

Similar presentations

Presentation on theme: "CS 160: Software Engineering September 10 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak www.cs.sjsu.edu/~mak."— Presentation transcript:

1 CS 160: Software Engineering September 10 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak www.cs.sjsu.edu/~mak

2 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 2 Model-View-Controller Architecture (MVC)  The Model-View-Controller (MVC) architecture is used for client-server applications that include a user interface. _

3 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 3 Three Types of MVC Objects  Model objects Maintain the data and knowledge of your application.  View objects Display the model to the user. The presentation layer.  Controller objects Manage the application flow. Handle user interactions.

4 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 4 Model-View-Controller Operation  The user interacts with the controller to send it commands. Via buttons, text fields, mouse actions, etc.  The commands may tell the controller to modify the view directly, or the controller may alter the state of the model.  The altered model causes the view to update how it displays the model’s data.  The user may react to changes in the view by interacting with the controller to send new commands. The user never manipulates the model directly, only through the controller.

5 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 5 Model-View-Controller Example alter state update CONTROLLER MODEL VIEW #1VIEW #2 User send command

6 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 6 MVC Implementation for Web Applications  Implement the controller with servlets. Goal: Reduce the amount of Java code in the JSPs. Move control logic into servlets. Servlets are multi-threaded and can be shared.  Implement the view with JSPs. view = web pages JSPs should look like HTML as much as possible. Include tags for dynamically generated data. _

7 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 7 MVC Implementation, cont’d  Implement the model with JavaBeans. Persist the data maintained by the JavaBeans into a backend data repository, such as a MySQL database. _

8 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 8 MVC Implementation: Loose Coupling  Keep the implementations of the three objects types separate.  Each type of objects does not depend on how the other types are implemented.  Your application is more robust (resilient to change). _

9 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 9 MVC Implementation: Parallel Development  Controller (servlets) Java programmers  View (JSPs) Web page designers  Model (JavaBeans and database) Java programmers Database developers _

10 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 10 Handle User Interactions with Servlets  Forms on HTML pages should send user data to servlets. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> Murach's Java Servlets and JSP Join our email list To join our email list, enter your name and email address below. Then, click on the Submit button.... Servlet

11 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 11 Handle User Interactions with Servlets, cont’d  Map a servlet name in the application file WEB-INF/web.xml... AddToEmailListServlet music.email.AddToEmailListServlet... AddToEmailListServlet /addToEmailList... NetBeans will automatically create this mapping for you.

12 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 12 Servlet  Servlet  JSP  After a servlet has done its work (possibly including interactions with the model components), it may want to pass data to another servlet for more work, or to a JSP to display the next web page. Servlets are shared, multi-threaded code!

13 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 13 Servlet  Servlet  JSP, cont’d  The originating servlet stores the data into the request object: User user = new User(firstName, lastName, emailAddress); request.setAttribute("userObj", user);

14 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 14 Servlet  Servlet  JSP, cont’d  The servlet forwards the request to a target servlet or JSP: String url = "/cart/displayUserInfo.jsp"; RequestDispatcher dispatcher = getServerContext().getRequestDispatcher(url); dispatcher.forward(request, response);

15 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 15 Servlet  Servlet  JSP, cont’d  The target servlet or JSP retrieves the data from the request object: User user = (User) request.getAttribute("userObj");

16 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 16 Analysis  Identifying the three types of objects of a MVC application architecture is part of analysis. _

17 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 17 Analysis Goal  Build an analysis model of the application that you’re developing that is correct, complete, consistent, and unambiguous.  Model building is a highly iterative and incremental activity.  The model describes the application domain.  Developers work with clients to update the functional specification as they discover new requirements. Don’t confuse the uses of the word model in Model-View-Controller and analysis model.

18 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 18 Analysis Model Submodels 1. Functional model Use cases and scenarios UML use case diagrams and descriptions 2. Object model Derive objects from the use cases Precursor for system design UML class and object diagrams 3. Dynamic model Behavior of the system UML sequence diagrams and statecharts

19 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 19 MVC Model Objects  Represent persistent information maintained by your application. AKA entity objects  Examine the participating objects in your use case descriptions. Map parts of speech (nouns, ‘doing’ verbs, ‘having’ verbs, ‘being’ verbs, adjectives, etc.) to model components (classes, objects, operations, attributes, relationships, etc.) _

20 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 20 MVC Model Objects, cont’d Color, size, positionAttributeAdjective Must be, shall beConstraintsModal verb Has a, consists of, includesAggregation‘Having’ verb Is a kind of, is one of eitherInheritance‘Being’ verb Creates, submits, selectsOperation‘Doing’ verb PolicemanClassCommon noun AliceObjectProper noun ExampleModel ComponentPart of Speech

21 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 21 MVC View Objects  System interface with the actors. View objects represent user interface components. Continue to use user-level terms.  In each use case, each actor interacts with at least one view object. A view object collects information from the actor in a form that the model and controller objects can use. _

22 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 22 MVC Controller Objects  Coordinate the model and view objects. Often have no physical counterpart in the real world. Closely related to a use case. Collect information from view objects for dispatch to model objects.  This is how user-entered data can update the model  Represent application control flows. _

23 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 23 Example: Bank ATM System Log in customer Display balance Shut down ATM Start up ATM Log out customer Withdraw cash Operator Customer Bank

24 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 24 Example: Bank ATM System (cont’d)  Model objects operator customer bank account cash  View objects display options (withdraw cash, deposit check, etc.) messages  Controller objects Start up controller (“Start up ATM” use case) User verification controller (“Log in customer” use case) Withdrawal controller (“Withdraw cash” use case) Log in customer Display balance Shut down ATM Start up ATM Log out customer Withdraw cash Operator Customer Bank

25 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 25 Example Dynamic Model: ATM Cash Withdrawal Customer “Withdraw cash”KeypadBank Account Display select notify display confirmation enter amount notify verify accept notify display bank ads notify dispense cash TIMETIME UML Sequence Diagram

26 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 26 Dynamic Model: UML Sequence Diagram  A UML sequence diagram represents how the behavior of a use case is distributed among the participating objects. _

27 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 27 Dynamic Model: UML Sequence Diagram, cont’d  Columns of the diagram represent the objects.  Horizontal arrows from one column to another represent messages or stimuli sent from one object to another (method invocations).  Receiving a message by an object triggers the object to activate an operation.  Vertical rectangles represent the duration of an operation’s activation.  Time proceeds from top to bottom.

28 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 28 Dynamic Model: UML Statechart Diagram  A UML statechart diagram represents the behavior of the system from the perspective of a single object. _

29 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 29 Dynamic Model: UML Statechart Diagram, cont’d  Developers and clients may identify new behaviors (and new requirements).  Create statechart diagrams only for objects with extended lifetimes and state-dependent behavior always for controller objects sometimes for model objects almost never for view objects _

30 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 30 Example: Customer Withdraws Cash from ATM Logged in Card accepted Reading bank ads Has cash swipe bank card enter PIN enter withdrawal amountget cash leave UML Statechart Diagram

31 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 31 Object Model Associations  An association is a relationship between two or more classes. _

32 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 32 Object Model Associations, cont’d  Draw a line between two classes in a UML class diagram to show a relationship. Clarify the object model by making relationships explicit. Discover constraints associated with relationships. An association can have a name. You can show roles and multiplicities at each end.  Do not overdo showing associations. Team member Use case writes authorartifact 1 *

33 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 33 Aggregations and Compositions  An aggregation is an “ownership” or “has a” association. Although there is a strong association between the object and its owner, the object can exist on its own. An object can change owners or have several owners.  A composition is a “made up of” association. The constituent objects generally would not exist alone. This is the strongest association. PageBook aggregationcomposition Student Shelf

34 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 34 Generalization  Generalization is a special association that consolidates common attributes or behavior among classes.  Subclasses inherit attributes and behavior from their superclasses. Person InstructorStudent subclasses superclass

35 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 35 Attributes  An attribute is a property of an object. An association with another object is not an attribute.  Attributes are the least stable part of an object model. Attributes often change or are discovered late. At the beginning, it’s not necessary for attributes to describe fine details. Student gender : {male, female} id : String year : integer Methods will go hereAttributesClass name

36 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 36 System Design  System design is the transformation of your analysis model into a system design model. This is the design of your entire web application. _

37 Computer Science Dept. Fall 2014: September 10 CS 160: Software Engineering © R. Mak 37 System Design Goal  A model that includes a subsystem decomposition and descriptions of chosen development strategies: hardware/software strategy persistent data management strategy global control flow access control policy boundary conditions handling _

Download ppt "CS 160: Software Engineering September 10 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak www.cs.sjsu.edu/~mak."

Similar presentations

Introduction to Object Orientation System Analysis and Design

Introduction to Object Orientation System Analysis and Design
Ch 12: Object-Oriented Analysis

Ch 12: Object-Oriented Analysis
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.

1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.

Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.

1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
CS 160: Software Engineering September 8 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak www.cs.sjsu.edu/~mak.

CS 160: Software Engineering September 8 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  1998-1999 Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.

OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
Interaction Diagrams Activity Diagram State Machine Diagram

Interaction Diagrams Activity Diagram State Machine Diagram
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..

Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
1 Lecture 2: Elaboration Tasks and Domain Modeling.

1 Lecture 2: Elaboration Tasks and Domain Modeling.
Requirements Analysis 2 What objects collaborate to achieve the goal of a use case?

Requirements Analysis 2 What objects collaborate to achieve the goal of a use case?
Copyright W. Howden1 Lecture 2: Elaboration Tasks and Domain Modeling.

Copyright W. Howden1 Lecture 2: Elaboration Tasks and Domain Modeling.
GREEN CORP’S Blue Team Stock Trading System Fall 2000 Software Engineering I.

GREEN CORP’S Blue Team Stock Trading System Fall 2000 Software Engineering I.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.

Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Objectives Explain the purpose and objectives of object- oriented design Develop design class diagrams Develop interaction diagrams based on the principles.

Objectives Explain the purpose and objectives of object- oriented design Develop design class diagrams Develop interaction diagrams based on the principles.
Chapter 9 Domain Models 1CS6359 Fall 2012 John Cole.

Chapter 9 Domain Models 1CS6359 Fall 2012 John Cole.
CS 160: Software Engineering August 27 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak www.cs.sjsu.edu/~mak.

CS 160: Software Engineering August 27 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
1 Lab-02. 2 Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.

1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
UNIT-V The MVC architecture and Struts Framework.

UNIT-V The MVC architecture and Struts Framework.
The Design Discipline.

The Design Discipline.

Similar presentations

Ads by Google