Krutchten’s 4+1 View Model of Java Pet Store
Krutchten’s 4+1 View Model
Of
Java Pet Store
By
Baitar Jones
Introduction
The purpose of this paper is to discern what design decisions where made in the making of the Java Pet Store Demo. I will use Krutchten’s 4+1 View Model to describe the design decisions.
The documentation on the pet store mentioned 5 key design decisions. These are
• Use of application framework
• Web-tier business logic vs. enterprise beans components
• Local vs. distributed architecture
• Declarative vs. programmatic transaction control.
• Synchronous vs. asynchronous communication.
These design decisions and others will be covered in detail.
Scenario View
User Creation : This scenario depicts how a new customer is created.
[pic]
Signon : This scenario depict how a customer logs on to the system.
[pic]
Order Placement : This scenario depict how one places a order.
[pic]
Logical View
The Top Level components that I identified are
• Order Component : This Component is responsible for keeping a track of the order. i.e. the order number, state of the order, date created, total price, customer, shipping address and items in order.
• Cart Component : This keeps a track of what the customer has selected.
• Customer Component : Keeps a track of the customers detail, account, credit card and billing address.
• Catalog Component : This lists all items available and sorts items via category.
• Supplier Component : This keeps a track of all suppliers and what products they provide.
[pic] This Figure 1 shows the Logical top level design.
Process View
[pic]
Figure 2 : This shows how the top level components communicate with each other.
Figure 2 shows the communication between modules. The control modules is in the heart of it all waiting to update the screen.
Communication
Of
Java Pet Store
By
Baitar Jones
Introduction
The purpose of this paper is to discern what design decisions where made in the making of the Java Pet Store Demo. I will use Krutchten’s 4+1 View Model to describe the design decisions.
The documentation on the pet store mentioned 5 key design decisions. These are
• Use of application framework
• Web-tier business logic vs. enterprise beans components
• Local vs. distributed architecture
• Declarative vs. programmatic transaction control.
• Synchronous vs. asynchronous communication.
These design decisions and others will be covered in detail.
Scenario View
User Creation : This scenario depicts how a new customer is created.
[pic]
Signon : This scenario depict how a customer logs on to the system.
[pic]
Order Placement : This scenario depict how one places a order.
[pic]
Logical View
The Top Level components that I identified are
• Order Component : This Component is responsible for keeping a track of the order. i.e. the order number, state of the order, date created, total price, customer, shipping address and items in order.
• Cart Component : This keeps a track of what the customer has selected.
• Customer Component : Keeps a track of the customers detail, account, credit card and billing address.
• Catalog Component : This lists all items available and sorts items via category.
• Supplier Component : This keeps a track of all suppliers and what products they provide.
[pic] This Figure 1 shows the Logical top level design.
Process View
[pic]
Figure 2 : This shows how the top level components communicate with each other.
Figure 2 shows the communication between modules. The control modules is in the heart of it all waiting to update the screen.
Communication