HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
 
(44 intermediate revisions by the same user not shown)
Line 37: Line 37:
 
|}
 
|}
  
Technical complexity of the task/function are shown below:
+
<b>Technical complexity of the task/function are shown below:</b>
 +
 
 +
{| border="1"
 +
|- style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#007fb1', endColorstr='#02507c'); background: -webkit-gradient(linear, left top, left bottom, from(#33527E), to(#00275E)); background: -moz-linear-gradient(top,  #007fb1,  #02507c); color:White"
 +
|width="50" align="center"|'''No'''
 +
|width="200" align="center"|''' Task/ Function '''
 +
|width="650" align="center"|'''Description'''
 +
|-
 +
 
 +
|width="50" valign = middle align="center"|1
 +
|width="200" valign = middle align="left"|Play! Framework
 +
|width="650" valign = middle align="left"|
 +
<ul>
 +
<li> 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.
 +
<li> Play community is still new.
 +
<li> Their documentation is not entirely completed
 +
<li> Difficult to find solutions to problems online
 +
<li> Help found was on previous versions however we are using the newer version of the framework
 +
<li> Compatibility between Twitter Bootstrap
 +
</ul>
 +
|-
 +
 
 +
|width="50" valign = middle align="center"|2
 +
|width="200" valign = middle align="left"|Implementation of resume creation
 +
|width="650" valign = middle align="left"|
 +
<ul>
 +
<li> Creation of additional fields in the resume form is difficult to implement due to the constraint of the play framework
 +
<li> 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
 +
<li> Team spent a considerable large amount of time trying to resolve the issue
 +
</ul>
 +
|-
 +
 
 +
|width="50" valign = middle align="center"|3
 +
|width="200" valign = middle align="left"|Cross browser support
 +
|width="650" valign = middle align="left"|
 +
<ul>
 +
<li> Need to detect the version and type of browser user is currently using
 +
<li> Images and layouts have to be fluid enough so as to provide optimum and similar display settings across all browsers
 +
</ul>
 +
|-
 +
 +
 
 +
{| class="wikitable" cellpadding="15"
 +
|-
 +
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 10%; font-size:22px; border: 1px solid #ffffff" valign="top" | <b>Quality of Product</b>
 +
|-
 +
 
 +
| style="background: #000000; border:1px solid #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 10px 0 15px; font-size: 14px;" valign="top"  |
 +
|-
 +
|}
 +
 
 +
{| border="1"
 +
|- style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#007fb1', endColorstr='#02507c'); background: -webkit-gradient(linear, left top, left bottom, from(#FF6600), to(#FEB729)); background: -moz-linear-gradient(top,  #007fb1,  #02507c); color:White"
 +
|width="350" align="center"|'''Feature Implemented'''
 +
|width="550" align="center"|''' Description '''
 +
|-
 +
 
 +
|width="350" valign = middle align="center"|Customization of Resume (Part 1)
 +
|width="550" valign = middle align="left"|
 +
<ul>
 +
<li>Job seekers are able to rearrange the different components of their resume into the sequence they like
 +
<li>Versioning of resumes
 +
<li>Job seekers are able to change the naming of each components in the resume form.
 +
</ul>
 +
|-
 +
 
 +
|width="350" valign = middle align="center"|Formatting of Resume Information
 +
|width="550" valign = middle align="left"|
 +
<ul>
 +
<li>After job seekers enter information in the resume form, all data are formatted into a PDF upon a click
 +
</ul>
 +
|-
 +
 
 +
|width="350" valign = middle align="center"|Interactive User Interface
 +
|width="550" valign = middle align="left"|
 +
<ul>
 +
<li>Easy navigation
 +
<li>Clean and sleek layout
 +
<li>Helps users recognize, diagnose and recover from errors
 +
</ul>
 +
|-
 +
 
 +
|width="350" valign = middle align="center"|System Feedback
 +
|width="550" valign = middle align="left"|
 +
<ul>
 +
<li>Keep users informed about what is going on
 +
<li>Indicative pop-out messages after user completes a major action
 +
<li>Client side validation helps in error prevention. It also provides user with instant feedback if there is an error in the input data
 +
</ul>
 +
|-
 +
 
 +
{| class="wikitable" cellpadding="15"
 +
|-
 +
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 10%; font-size:22px; border: 1px solid #ffffff" valign="top" | <b>Immediate Deliverables</b>
 +
|-
 +
| style="background: #000000; border:1px solid #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 10px 0 15px; font-size: 14px;" valign="top"  |
 +
|-
 +
|}
 +
 
 +
{| border="1"
 +
|- style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#007fb1', endColorstr='#02507c'); background: -webkit-gradient(linear, left top, left bottom, from(#9C1C6B), to(#CA278C)); background: -moz-linear-gradient(top,  #007fb1,  #02507c); color:White"
 +
|align="center" width ="250"| Stage
 +
|align="center" width ="250"| Specification
 +
|align="center" width ="300"| Modules
 +
|-
 +
 
 +
|rowspan="3" valign="top"|Project Management
 +
|rowspan="3" valign="top"|Meeting Minutes
 +
|| Team Meeting: [[IS480 Team wiki: 2012T1 One-hit Wonder Project Management Minutes|Minutes 1-18]]
 +
|-
 +
|| Supervisor Meeting: [[IS480 Team wiki: 2012T1 One-hit Wonder Project Management Minutes| Minutes 1-5]]
 +
|-
 +
|| Client Meeting: [[IS480 Team wiki: 2012T1 One-hit Wonder Project Management Minutes| Minutes 1-7]]
 +
|-
 +
 
 +
|rowspan="1" valign="top"|Requirements
 +
|rowspan="1" valign="top"|Storyboard
 +
||[[IS480 Team wiki: 2012T1 One-hit Wonder Project Documentation Mock Ups|UI Mock Ups ]]
 +
|-
 +
 
 +
|rowspan="1" valign="top"|Analysis
 +
||Use Case
 +
||[[IS480 Team wiki: 2012T1 One-hit Wonder Project Documentation|Use Case Diagram & Descriptions]]
 +
|-
 +
 
 +
 
 +
|rowspan="2" valign="top"|Design
 +
||System Architecture Diagram
 +
||[[IS480 Team wiki: 2012T1 One-hit Wonder Project Documentation Technical Diagrams| System Architecture Diagram]]
 +
|-
 +
 
 +
||Database Diagram
 +
||[[IS480 Team wiki: 2012T1 One-hit Wonder Project Documentation Database Diagrams| Logical Diagram & ERD]]
 +
|-
 +
 
 +
|rowspan="1" valign="top"|Heuristic Evaluation
 +
||Heuristic Evaluation Feedback Report
 +
||[[Media:Heuristic Evaluation Report-One hit Wonder(Final).pdf | One-hit Wonder Heuristic Evaluation Report]]
 +
|-
 +
 
 +
|rowspan="3" valign="top"|User Testing 1
 +
||UT 1 (Internal) Test Cases
 +
||[[Media:One-hit Wonder Test Cases (Internal).xlsx | One-hit Wonder Internal Test Cases]]
 +
|-
 +
||UT1 Test Cases & Overall Experience Feedback (For Testers)
 +
||[[Media:UT1 One-hit Wonder (Final).pdf | One-hit Wonder UT1 Test Cases]]
 +
|-
 +
||UT 1 Results and Analysis
 +
||[[Media:OHW-UT1 Result.xlsx | UT 1 Results]]
 +
|-
 +
 
 +
|rowspan="1" valign="top"|Slides
 +
||FYP Mid-Term Presentation Slides
 +
||[[Media:OHW_Mid-Term.pdf | One-hit Wonder Mid-Term Presentation Slides]]
 +
|-
 +
|}
 +
<br>
 +
 
 +
{| class="wikitable" cellpadding="15"
 +
|-
 +
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 10%; font-size:22px; border: 1px solid #ffffff" valign="top" | <b>Deployment</b>
 +
|-
 +
 
 +
| style="background: #000000; border:1px solid #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 10px 0 15px; font-size: 14px;" valign="top"  |
 +
|-
 +
|}
 +
 
 +
<br>
 +
[[Image:OHW- System Overview.png |600px]]

Latest revision as of 14:12, 8 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
Feature Implemented Description
Customization of Resume (Part 1)
  • Job seekers are able to rearrange the different components of their resume into the sequence they like
  • Versioning of resumes
  • Job seekers are able to change the naming of each components in the resume form.
Formatting of Resume Information
  • After job seekers enter information in the resume form, all data are formatted into a PDF upon a click
Interactive User Interface
  • Easy navigation
  • Clean and sleek layout
  • Helps users recognize, diagnose and recover from errors
System Feedback
  • Keep users informed about what is going on
  • Indicative pop-out messages after user completes a major action
  • Client side validation helps in error prevention. It also provides user with instant feedback if there is an error in the input data
Immediate Deliverables
Stage Specification Modules
Project Management Meeting Minutes Team Meeting: Minutes 1-18
Supervisor Meeting: Minutes 1-5
Client Meeting: Minutes 1-7
Requirements Storyboard UI Mock Ups
Analysis Use Case Use Case Diagram & Descriptions
Design System Architecture Diagram System Architecture Diagram
Database Diagram Logical Diagram & ERD
Heuristic Evaluation Heuristic Evaluation Feedback Report One-hit Wonder Heuristic Evaluation Report
User Testing 1 UT 1 (Internal) Test Cases One-hit Wonder Internal Test Cases
UT1 Test Cases & Overall Experience Feedback (For Testers) One-hit Wonder UT1 Test Cases
UT 1 Results and Analysis UT 1 Results
Slides FYP Mid-Term Presentation Slides One-hit Wonder Mid-Term Presentation Slides


Deployment


OHW- System Overview.png