HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T2 DR.Jean Labs The Team Final Wiki"

From IS480
Jump to navigation Jump to search
Line 67: Line 67:
  
 
<!-- content -->
 
<!-- content -->
[[Image:Dr.JeanLabs Final StoryBoard.png|center|900px ]]
 
 
==Project Progress Summary==
 
 
=== Closed Beta Launch ===
 
Beta Launch released date: 20 Feb 2014, 1pm <br />
 
Beta released app link <b>(User)</b>: http://app.sqkii.com/ <br />
 
Beta released app link <b>(Advertiser</b>): http://app.sqkii.com/adv <br />
 
 
Beta released app test link <b>(User)</b>: http://test.sqkii.com/ <br />
 
Beta released app test link <b>(Advertiser</b>): http://test.sqkii.com/adv <br />
 
 
<!--
 
<gallery caption="Pictures for testing" widths="250px" heights="180px">
 
Image:Dr.JeanLabs_Picture1Demo.png|Picture 1
 
Image:Dr.JeanLabs_Picture2Demo.png|Picture 2
 
Image:Dr.JeanLabs_Picture3Demo.jpg|Picture 3
 
</gallery>
 
 
{| class="wikitable"
 
 
|-
 
|colspan = "2" align = "center"|Advertiser test account
 
<b>http://test.sqkii.com/</b>
 
 
|-
 
! style="background: #176596; color: white; text-align: center"; colspan= "1"; font-weight: bold| Username
 
! style="background: #176596; color: white; text-align: center"; colspan= "1"; font-weight: bold| Password
 
 
|-
 
|benjamin@gmail.com
 
|123123
 
 
|-
 
|alan@gmail.com
 
|123123
 
 
|-
 
|david@gmail.com
 
|123123
 
 
|}
 
 
-->
 
 
Download our Final Presentation slides [ here!]
 
 
===Project Highlights:===
 
 
What unexpected events occurred and how were they handled?
 
*A team member left the project and dropped the course
 
*List of requirement changes
 
** CRUD items replaced with CU/Sync/Archive items
 
** Business analytics replaced with iPad client
 
*Took 8 weeks to learn Ruby on Rails
 
*etc.
 
Be brief. A couple of sentences on the event and another couple on what was done is sufficient. Do not repeat the next sub sections. If there are no highlights, remove this section
 
 
===Project Challenges:===
 
 
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
 
 
===Project Achievements:===
 
 
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.
 
 
==Project Management==
 
 
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
 
 
===Project Schedule (Plan Vs Actual):===
 
 
Compare the project plan during midterm with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
 
 
Provide a comparison of the plan and  actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
 
 
{| border="1"
 
|- style="background:blue; color:white"
 
|| Iterations
 
|colspan="2" align="center"| Planned
 
|colspan="2" align="center"| Actual
 
|| Comments
 
|-
 
 
|rowspan="2"| 1
 
|| Customer CRUD
 
|| 1 Sept 2010
 
||
 
|| 25 Aug 2010
 
|| Fiona took the Sales CRUD as well.
 
|-
 
 
|| Trend Analytic
 
|| 1 Sept 2010
 
||
 
|| 15 Sept 2010
 
|| Ben is too busy and pushed iteration 1 back
 
|-
 
 
|rowspan="2"| 2
 
|| User tutorial
 
|| 1 Oct 2010
 
|colspan="2"|
 
|| Removed proposed by Ben
 
|-
 
 
|colspan="2"|
 
|| Psycho analysis
 
|| 1 Oct 2010
 
|| New module proposed by sponsor
 
|}
 
 
===Project Metrics:===
 
 
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
 
 
===Technical Complexity:===
 
 
{| border = "1"
 
|- style="background:black; color:white"
 
| align="center"| Complexity
 
| align="center"| Description
 
|-
 
 
| align="center"| Jcrop + Javascript boost (Advertiser Platform)
 
|| Image uploading is a vital function to the merchant partners of Sqkii. Thus, research has been done to find a suitable plugin to cater to the cropping of images - this is to provide a function where merchant partners are able to snap a picture of their product, and immediately crop the desired area. We decided to use jCrop, however there were many disabilities coupled with jCrop.
 
 
 
Firstly, it is the inability to execute the cropping on client side. Which means that there will be more work done on the server side, inducing more costs. To fix this problem, we employed HTML's canvas element. Drawing on a canvas element the desired cropped image. This shifted the work from the server side to the client side and will definitely save costs for Sqkii.
 
 
 
Secondly, the images uploaded unto the jCrop api does not cater to a web responsive layout. It ends up with a rigid image size that remains that size. This is fixed by using our technical expertise to manually reconfigure the uploaded image, along with the interwoven jCrop variables. This resulted in a extremely web responsive layout for the image upload function which coincides with our goal to produce a web responsive web app
 
|-
 
 
| align="center"| Pseudo Random Credit Algorithm (User Platform)
 
|| Our users are as important as our merchant partners, and we want to make their main function at Sqkii a fun and exciting one. Thus, we felt that the mundane revenue sharing concept might not necessarily keep our users interested to keep using Sqkii. Thus, we developed a crediting algorithm that randomises the crediting, at the same time it returns back to the users exactly the amount that they are entitled to. This provides with an exciting and unique where of crediting where no user will have the same path of crediting, while actually having the same path.
 
|-
 
 
|}
 
 
==Quality of product==
 
 
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
 
 
===Project Deliverables:===
 
 
List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.
 
 
{| border="1"
 
|- style="background:blue; color:white"
 
|align="center"| Stage
 
|align="center"| Specification
 
|align="center"| Modules
 
|-
 
 
|rowspan="2"| Project Management
 
|| Minutes
 
|| Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
 
|-
 
 
|| Metrics
 
|| Bug metrics
 
|-
 
 
|| Requirements
 
|| Story cards
 
|| [http://www.agilemodeling.com/artifacts/userStory.htm CRUD Customer], [http://www.agilemodeling.com/artifacts/userStory.htm Trend Analytic]
 
|-
 
 
|rowspan="4"| Analysis
 
|| Use case
 
|| [http://en.wikipedia.org/wiki/Use_case_diagram overall]
 
|-
 
 
|| System Sequence Diagram
 
|| [http://en.wikipedia.org/wiki/System_Sequence_Diagram client], [http://en.wikipedia.org/wiki/System_Sequence_Diagram server]
 
|-
 
 
|| [http://en.wikipedia.org/wiki/Business_Process_Modeling_Notation Business Process Diagram]
 
||
 
|-
 
 
|| Screen Shots
 
|| CRUD Customer, Trend Analysis
 
|-
 
 
|rowspan="2"| Design
 
|| [http://en.wikipedia.org/wiki/Entity-relationship_model ER Diagram]
 
|| 1, 2, 3
 
|-
 
 
|| [http://en.wikipedia.org/wiki/Class_diagram Class Diagram]
 
|| [http://en.wikipedia.org/wiki/Class_diagram 1], [http://en.wikipedia.org/wiki/Class_diagram 2], [http://en.wikipedia.org/wiki/Class_diagram 3]
 
|-
 
 
 
|| Testing
 
|| Test plan
 
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
 
|-
 
 
|rowspan="3"| Handover
 
|| Manuals
 
|| User tutorial, Developer manual, Setup manual
 
|-
 
 
|| Code
 
|| client server
 
|-
 
 
|| [http://en.wikipedia.org/wiki/Deployment_diagram Deployment Diagram]
 
|| [[IS480_Midterm_Wiki#Deployment: | instructions]]
 
|}
 
 
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
 
 
=== Quality:===
 
 
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
 
 
===Deployment:===
 
 
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a [[IS480_Final_Wiki#Project_Deliverables: | deployment diagram link]].
 
 
===Testing:===
 
 
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
 
 
==Reflection==
 
 
Compile common lessons and reflection for the team and for each team member. Be brief.
 
 
===Team Reflection:===
 
 
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki [[Knowledge_base | knowledge base]] and linked here.
 
 
===Individual Reflection:===
 
 
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
 
 
===Sponsor Comment:===
 
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
 

Revision as of 14:33, 8 April 2014

Agurz avatar.png
Denise avatar.png
Eleazar avatar.png
Dr.jeanlabs logo.jpg
Janan avatar.png
Nicholas avatar.png
Rafael avatar.png

HOME

 

DR.JEAN LABS

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

PROJECT DOCUMENTATION

 


{ In a nutshell } { Acceptance Wiki } { MidTerm Wiki } { Final Wiki }



<> Project Summary >> << Project Management >> << Quality of the Product >> << Our Reflections >>

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -