HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 LOCK FinalWiki"

From IS480
Jump to navigation Jump to search
Line 74: Line 74:
  
 
<h3>Project Schedule</h3>
 
<h3>Project Schedule</h3>
[[File:TEAMLOCK_Schedule_Final.png|center|800px]]
+
[[File:TEAMLOCK_Schedule_Final.png|center|950px]]
 
<h4> Highlights of Changes Made in Schedule </h4>
 
<h4> Highlights of Changes Made in Schedule </h4>
 
*
 
*

Revision as of 18:26, 18 April 2016

LockLogo3.jpg


LockHouse.png   HOME LOCK-About Us.png   ABOUT US LockGraph.png   PROJECT OVERVIEW LockManage.png   PROJECT MANAGEMENT LockDocuments.png   DOCUMENTATION

 


OUR PROJECT PROGRESS

Team LOCK FINALS Documentation

Final Slides Pitch Poster
Rhinos finals slides.jpg Rhinos finals pitch.png Rhinos finals poster.png

Summary of Project

Lock Final wiki.png


Our Development Progress

Lock Final Progress.PNG

OUR PROJECT MANAGEMENT

Project Scope

Acceptance Midterms
LOCK-Scope.png
TeamLockScope.jpg

Final Project Scope!

Final TeamLockScope.png





Highlights of Changes Made in Scope

  • Dropped Secondary Functions I
  • Dropped Good-To-Have Functions


Project Schedule

TEAMLOCK Schedule Final.png

Highlights of Changes Made in Schedule


Metrics

Schedule Metric

TeamLOCK Schedule Metrics FINAL.PNG


Highlights of Schedule Metrics
Iteration Planned (Days) Actual (Days) SM Score Action Status
- - - - - -



Bug Metric

iOS Android
Ios Bug Metrics.PNG Android bug Metrics.PNG



Highlight of Changes in Collection of Bugs

There was a huge spikes of bugs found in iteration 7 & 8 (both iOS & Android). This was largely due to the fact this was the period where our team was solely focusing on cleaning up our application(Fixing of bugs/UI) in preparation for Soft-Launch.

Iteration Bug Score Summary of Bugs and Issues Action Taken
- - - -


Full documentation of our issue tracker is available on our Test Documents which can be found here!(Android) & here!(iOS)

Project Risks

LOCK Risk 1.PNG
LOCK Risk2.PNG


LOCK Risk3.PNG

Technical Complexity

How we design our Architecture?

Android Arc.png
LOCK IOS Arc.PNG

Project Complexity

1.
LOCK Tech Spring.PNG
2.
LOCK CUS UI.PNG
3.
Tech Swift.png

OUR QUALITY ASSURANCE

Deliverables

Type Decription Documentation
Requirement Gathering Market Research Market Research
Project Management Minutes, Metrics, Risks, Change

Meeting Minutes
Metrics
Risk Management
Change Management

Analysis and Design Use Case, Architectural Diagram, ER Diagram, Technology and Tools Used Use Case, Architectural Diagram, ER Diagram, Technology and Tools Used
Testing User Test Plan

User Testing 1
User Testing 2

Testing

As at 20th February 2016, we have completed 2 User Testing. These activities are primarily conducted to ensure that the StaffOnDemand Mobile satisfies the needs of our target group as agreed upon with our Sponsors and provides confidence of its use.

User Testing 1

  • Number of Users: 30
  • Venue: SOE-SR3.1
  • Date: 3rd – 5th November 2015
  • Duration: 15 minutes per user
  • Test Platform: Android Mobile Device , iOS

Objective:User Testing is conducted to ensure that StaffOnDemands satisfies our target consumer group and meets the expectations of sponsors and users. In this User Testing, we are primarily focusing on :

  • Usability and intuitiveness of functions
  • Find bugs / defects in the application


User Testing 2

  • Number of Users: 42
  • Venue: SOE-SR-3.1 | SOE SR-2.7
  • Date: 15th January 2015
  • Duration: 15 minutes per user
  • Test Platform: Android Mobile Device , iOS

Objective:User Testing is conducted to ensure that StaffOnDemands satisfies our target consumer group and meets the expectations of sponsors and users. In this User Testing, we are primarily focusing on :

  • Gathering feedback from potential stakeholders with regards to the heuristics and design of the existing functions of the current application
  • Identify any usability issues that persist in the application
  • Improvement of our application based on the results

OUR LEARNING OUTCOMES

LOCK Reflection.PNG