HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 One-hit Wonder MT Technical Complexity"

From IS480
Jump to navigation Jump to search
Line 77: Line 77:
 
</ul>
 
</ul>
 
|-
 
|-
<br>
+
  
 
{| class="wikitable" cellpadding="15"
 
{| class="wikitable" cellpadding="15"

Revision as of 19:11, 7 October 2012

Undo-icon.png Main Wiki

HomeOHW.png Home

Calendar 2 icon&48.png Project Management

Chart line icon&24.png Project Metrics

18px‎ Technical Complexity

Users24.png Usability Studies

TeamRef.png Team Reflection

Technical Complexity

Technical complexity of the task/function are shown below:

No Task/ Function Description
1 Play! Framework
  • Besides the knowledge on the MVC framework, our team did not have any previous background knowledge on utilising frameworks in the development of web applications.
  • Play community is still new.
  • Their documentation is not entirely completed
  • Difficult to find solutions to problems online
  • Help found was on previous versions however we are using the newer version of the framework
  • Compatibility between Twitter Bootstrap
2 Implementation of resume creation
  • Creation of additional fields in the resume form is difficult to implement due to the constraint of the play framework
  • Resume form is made up of many forms embedded in it, this increased the complexity of the creation of additional fields in the resume form, as it is harder to process the request in the back-end
  • Team spent a considerable large amount of time trying to resolve the issue
3 Cross browser support
  • Need to detect the version and type of browser user is currently using
  • Images and layouts have to be fluid enough so as to provide optimum and similar display settings across all browsers
Quality of Product

blah blah blah