HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 One-hit Wonder Project Overview Framework"

From IS480
Jump to navigation Jump to search
 
(3 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
{| style="background-color:none; color:#ffffff; border-bottom:3px dotted #FFF7B7; border-top:3px dotted #FFF7B7; border-left:3px dotted #FFF7B7; border-right:3px dotted #FFF7B7;" width="100%" cellspacing="0" cellpadding="0" valign="top" |
 
{| style="background-color:none; color:#ffffff; border-bottom:3px dotted #FFF7B7; border-top:3px dotted #FFF7B7; border-left:3px dotted #FFF7B7; border-right:3px dotted #FFF7B7;" width="100%" cellspacing="0" cellpadding="0" valign="top" |
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; " width="6%" |
 
| style="padding:0.3em; font-size:100%; background-color:#ffffff; text-align:center; " width="6%" |
[[Image:HomeOHW.png]][[IS480_Team_wiki:_2012T1_One-hit_Wonder_Home | <font color="#000000">Home</font>]]
+
[[Image:HomeOHW.png]][[IS480_Team_wiki:_2012T1_One-hit_Wonder | <font color="#000000">Home</font>]]
  
 
| style="background:none;" width="1%" |
 
| style="background:none;" width="1%" |
Line 32: Line 32:
  
 
<!--Sub Navigation-->
 
<!--Sub Navigation-->
{| style="background-color:none; color:#ffffff; font-weight: bold; border-bottom:0px solid #FFF7B7; border-left:0px solid #000000; border-right:0px solid #000000;" width="100%" cellspacing="0" cellpadding="0" valign="top" |
+
{| style="background-color:none; color:#ffffff; font-weight: bold; border-bottom:0px solid #FFF7B7; border-left:0px solid #000000; border-right:0px solid #000000;" width="80%" cellspacing="0" cellpadding="0" valign="top" |
 
| style="padding:0em; font-size:100%; background-color:#ffffff; border-top-left-radius: 10px; border-top-right-radius: 10px; border-bottom:0px solid #000000; border-top:0px solid #000000; border-left:2px solid #000000; border-right:2px solid #000000; -webkit-box-shadow: 0px 0px 0px #FFF7B7; text-align:center; " width="15%" |
 
| style="padding:0em; font-size:100%; background-color:#ffffff; border-top-left-radius: 10px; border-top-right-radius: 10px; border-bottom:0px solid #000000; border-top:0px solid #000000; border-left:2px solid #000000; border-right:2px solid #000000; -webkit-box-shadow: 0px 0px 0px #FFF7B7; text-align:center; " width="15%" |
 
[[IS480_Team_wiki:_2012T1_One-hit_Wonder_Project_Overview | <font color="#000000">Description</font>]]
 
[[IS480_Team_wiki:_2012T1_One-hit_Wonder_Project_Overview | <font color="#000000">Description</font>]]
Line 41: Line 41:
 
| style="padding:0em; font-size:100%; background-color:#ffffff; border-top-left-radius: 10px; border-top-right-radius: 10px; border-bottom:0px solid #000000; border-top:0px dotted #FFF7B7; border-left:2px solid #000000; border-right:2px solid #000000; -webkit-box-shadow: 0px 0px 0px #FFF7B7; text-align:center; color:#ffffff" width="15%" |  
 
| style="padding:0em; font-size:100%; background-color:#ffffff; border-top-left-radius: 10px; border-top-right-radius: 10px; border-bottom:0px solid #000000; border-top:0px dotted #FFF7B7; border-left:2px solid #000000; border-right:2px solid #000000; -webkit-box-shadow: 0px 0px 0px #FFF7B7; text-align:center; color:#ffffff" width="15%" |  
 
[[IS480_Team_wiki:_2012T1_One-hit_Wonder_Project_Overview_Scope | <font color="#000000">Scope & Deliverables</font>]]
 
[[IS480_Team_wiki:_2012T1_One-hit_Wonder_Project_Overview_Scope | <font color="#000000">Scope & Deliverables</font>]]
 
| style="padding:0em; font-size:100%; background-color:#ffffff; border-top-left-radius: 10px; border-top-right-radius: 10px; border-bottom:0px solid #000000; border-top:0px dotted #FFF7B7; border-left:2px solid #000000; border-right:2px solid #000000; -webkit-box-shadow: 0px 0px 0px #FFF7B7; text-align:center; color:#ffffff" width="15%" |
 
[[IS480_Team_wiki:_2012T1_One-hit_Wonder_Project_Overview_Usability_Studies | <font color="#000000">Usability Studies</font>]]
 
  
 
| style="padding:0em; font-size:100%; background-color:#FFF7B7; border-top-left-radius: 10px; border-top-right-radius: 10px; border-bottom:0px solid #000000; border-top:0px dotted #FFF7B7; border-left:0px solid #000000; border-right:0px solid #000000; -webkit-box-shadow: 0px 0px 6px #FFF7B7; text-align:center; color:#ffffff" width="15%" |  
 
| style="padding:0em; font-size:100%; background-color:#FFF7B7; border-top-left-radius: 10px; border-top-right-radius: 10px; border-bottom:0px solid #000000; border-top:0px dotted #FFF7B7; border-left:0px solid #000000; border-right:0px solid #000000; -webkit-box-shadow: 0px 0px 6px #FFF7B7; text-align:center; color:#ffffff" width="15%" |  
Line 60: Line 57:
 
| style="background: #FFF7B7; border:1px solid #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 10px 0px 15px; font-size: 14px;" valign="top"  |  
 
| style="background: #FFF7B7; border:1px solid #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 10px 0px 15px; font-size: 14px;" valign="top"  |  
 
|-
 
|-
| style= "background: #FFFCE3; border-left:2px solid #ffffff; border-right:2px solid #ffffff; border-bottom:2px dotted #FFF7B7; opacity:1; color: #000000; padding: 10px 10px 10px 15px; font-size: 15px; text-align: justify;" valign="top"  |
+
| style= "background: #FFFCE3; border-left:2px solid #ffffff; border-right:2px solid #ffffff; border-bottom:2px dotted #FFF7B7; opacity:1; color: #000000; padding: 10px 10px 10px 15px; font-size: 13px; text-align: justify;" valign="top"  |
  
 
'''Framework Comparison'''<br>
 
'''Framework Comparison'''<br>
Line 87: Line 84:
 
4. The flip side of the benefit that Struts encourages a consistent approach to MVC is that Struts makes it difficult (but by no means impossible) to use other approaches.<br>
 
4. The flip side of the benefit that Struts encourages a consistent approach to MVC is that Struts makes it difficult (but by no means impossible) to use other approaches.<br>
 
<br>
 
<br>
<u>PLAY! Framework</u> - Chosen Framework<br>
+
<u>PLAY! Framework</u> - <b>Chosen Framework</b><br>
 
Pros:<br>
 
Pros:<br>
 
1. Play is built for a ‘share nothing’ architecture (think about it as a Stateless framework).<br>
 
1. Play is built for a ‘share nothing’ architecture (think about it as a Stateless framework).<br>

Latest revision as of 18:50, 6 October 2012

HomeOHW.png Home

Users24.png Team / Stakeholders

Info24.png Project Overview

Calendar 2 icon&48.png Project Management

Folder fav24.png Project Documentation

TeamRef.png Team Reflection

Res&Ref.png Resource & References


Description

Motivation

Scope & Deliverables

Framework

Framework

Framework Comparison

Spring Framework
Pros:
1. Easy Configuration with Annotations and Conventions
2. Integrates with many view options seamlessly: JSP/
3. Excellent REST Support
Cons:
1. Instant reload not built-in, need JRebel or Spring Roo
2. No open development process, need to be SpringSource
3. Ajax requires 3rd-party library

Struts Framework
Pros:
1. Many Struts values are represented in XML or property files. This loose coupling allows wholesale changes to be made by editing a single file.
2. Apache Struts provides a set of custom JSP tags, particularly bean:write, which allows user to easily output the properties of JavaBeans components.
3. Apache Struts provides a set of custom JSP tags to create HTML forms that are associated with JavaBeans components. This allows user to get initial form-field values from Java objects, and redisplay forms with previously entered data intact.
4. Apache Struts has built-in capabilities for checking that form values are in the required format.
5. Consistent approach in terms of framework through application.
Cons:
1. Steeper learning curve because to use MVC with Struts, you have to be comfortable with the standard JSP and servlet APIs and a large and elaborate framework.
2. Poor documentation and Struts has fewer online resources.
3. With Struts applications, there is a lot more going on behind the scenes than with normal Java-based Web applications. Hence harder to understand.
4. The flip side of the benefit that Struts encourages a consistent approach to MVC is that Struts makes it difficult (but by no means impossible) to use other approaches.

PLAY! Framework - Chosen Framework
Pros:
1. Play is built for a ‘share nothing’ architecture (think about it as a Stateless framework).
2. It does not really rely on the so-called Java Enterprise standards.
3. Play framework enables scalability. It is usable even if you need to serve a very high traffic.
4. Play is standard Java, so any standard Java library can easily be used.
5. Manages dependencies without the need to learn the complexities of Maven

Cons:
1. Unless the library you want to use relies on the Servlet API, there won’t be any problem.
2. Play 2.0 lacks the connectivity and authorization framework to interface with different social media service provider API such as Facebook, Twitter, LinkedIn and other prominent social media networks.