IS480 Team wiki: 2011T2 iNstaNex Mid Term Wiki Page

From IS480
Jump to navigation Jump to search

Project Progress Summary

Project Highlights

As for midterm, we have completed our core functionality such as the
1. Product Catalogue,
2. Product Catalogue Quotation,
3. Retrieval of Job List and
4. Intranet System for Inventory Management.

We have completed about 50 percent of our core functionality.
The remaining functionality such as the
1. Geo-location of Delivery Teams,
2. Digital Signature on Order Receipt, and
3. Google Calender for Scheduling
is scheduled to be done after mid-term.

We also faced a few unexpected events like having a team member leave the team shortly after the Initial Acceptance Phase, client changing / removing core functionality [SMS notification to customers removed], the absence of another team member for 3 weeks, and the incorrect system architecture of iPhone application.
However, all these unfortunate events have been resolved and we have moved on with our progress to prevent further delay on schedule.

Project Management

Project Status

System Function Status Confidence Level Comment
iPhone Application
Administrative Functions

• Login/Logout Functionality

• Login/Logout Validation

• Locate Us

• Contact Us

• About Us

• Electromax website

Fully deployed and tested 100% 1
Product Catalogue Fully deployed and tested 100% 1
Product Catalogue Quotation Fully deployed and tested 100% 1
Job List Retrieval Fully deployed and tested 100% 1
SMS Notification to customers Removed - Client's request
Intranet System Inventory Management

• Update Installer Retrieval

• Update Bracket Stock

• Update TV Stock

• View Installer Retrieval History

• Report Spoilt Brackets

• Return Failed Delivery Brackets

Fully deployed and tested 100% 1
Scheduled after Mid Term
iPhone Application
Delivery Scheduling

• Google Calendar

• Bulletin Board

25/02/12 - 02/03/12 - -
Geo Location for Delivery Teams

• Delivery Team location update

03/03/12 - 23/03/12 - -
Digital Signature 23/03/12 - 05/04/12 - -

Project Schedule (Planned vs Actual)

Iterations Project Tasks Planned Duration Actual Duration Schedule Metric Remarks:
1 • Gathering of business requirements

• Generation of project ideas

05/10/11 - 10/10/11 05/10/11 - 10/10/11 100% On Time
2 • Finalize project proposal

• Proposal Submission

11/10/11 - 24/10/11 11/10/11 - 24/10/11 100% On Time
3 • Refine project scope

• User interface design mock up

• Use case diagram

• Wiki design

• Business process workflow diagram

25/10/11 - 06/11/11 25/10/11 - 06/11/11 100% On Time
4 ( Shifted to after Acceptance Test ) • Setting up connection to database

• Connect application to database

• Read/retrieve/edit/delete of data in database

07/11/11 - 16/11/11 - -
5 ( Shifted to after Acceptance Test ) • Login/Logout function

• Login\Logout UI

17/11/11 - 23/11/11 - - Postpone
6 ( Shifted to after Acceptance Test ) • Product Catalogue

• Add/filter of product catalogue

• Algorithm of product catalogue quotation

User Acceptance test 1.0

Acceptance Presentation

24/11/11 - 15/12/11 - - Postpone
5 • Login/Logout of different users

• Login\Logout Validation

• Login\Logout User interface

16/12/11 - 25/12/11 16/12/11 - 10/01/12 38.5% Behind Schedule
6 • Product Catalogue

• Add/filter of product catalogue

• Algorithm of product catalogue quotation

26/12/11 - 12/01/12 26/12/11 - 31/01/12 22.7% Behind Schedule
7 • Schedule appointment notification

• Access Google calender for scheduling through Application

• Announcement board for LG representatives

13/01/12 - 27/01/12 - - Postpone
8 • Intranet system for inventory management

• Inventory database design and setup

• Intranet system user interface

28/01/12 - 6/02/12 28/01/12 - 6/02/12 100% On Time
9 • SMS notification of installer delivery

• Call notification to customer

7/02/12 - 12/02/12 - - Removed (Client's request)
10 • Retrieval of current date's job list

• Confirmation update of job status

13/02/12 - 16/02/12 13/02/12 - 16/02/12 100% On Time
11 • System Integration and testing 17/02/11 - 24/02/12 In Progress

Project Metrics

Schedule Metric

Schedule metric graph instanex.JPG

View Calculation of Team Schedule Metric here

As shown in the graph, our team is on schedule from iterations 1 to 3.

However, we faced some difficulties during iteration 4 where we were supposed to set up the database for our application. While planning this schedule, we have assigned the setting up of database connection to the iPhone application for iteration 4. Our team then realised it was a mistake to assign it as an iteration because iPhone application database connection should not be consider as a functionality.

We shouldn't put it under a iteration because every core functionality in our iPhone app would require the developer to develop his function on the PHP script and the XCode platform and every core function that is to be developed would require its own PHP script to connect to the database. Since database connection is done continuously when core functionality is being developed, iteration 4 is not feasible.

The period in iteration 4 is spent researching and exploring how an iPhone application is being connected to the database before realising our mistake.

As for iteration 5 and 6, we were behind schedule due to the unfamiliarity with XCode. Much time was taken reading up the guide book for XCode before the actual start of the development. On top of that, the team was in disarray due to the reshuffling of group members, and roles and responsibilities. The schedule metric score for iteration 5 was 38.5%. According to the schedule metric, we should have dropped all tasks and review the entire project schedule. However, we did not do so, and concurrently started on the functionality of iteration 6. This is because the team knows that this delay in schedule is not due to the team's technical inability.

When we were halfway through iteration 6, one of our team member was uncontactable and did not turn up for our FYP meetings. The team member had already did research and have experienced in the functionality we planned to implement in iteration 7 so his disappearance was a disruption to our flow.

We then decided to postpone the whole functionality in iteration 7 and start working on the iteration 8. This action was done because we were giving the team member time to return. Furthermore, we did not want to disrupt the schedule any further as we were already behind time.

Fortunately, we were able to complete iteration 8 within the time scheduled and we were back on track. We have decided to postpone the functionality in iteration 7 after mid term.

In iteration 9, we were researching and exploring the SMS notification functionality. However, when we updated our client on our progress and the unfortunate events that had happened in the previous iterations, we were informed that our client had already outsourced the SMS notification function to a more experienced partner so we were told to drop that functionality. That explains why there is no metrics recorded in iteration 9.

Bug Metric

Bug metric graph (bug level) instanex.JPG Number of bugs and their bug level per iteration

Bug metric graph (bug points) instanex.JPG Total Number of Bug Points for each iteration.

Bug metric combined instanex.jpg Total Number of Bug Points Fixed for each iteration

View Calculation of Team Bug Metric here

The above graphs display the number of bugs and their bug levels. Till date, all the bugs found have already been fixed.

View our Bug Log here

Project Risks

Team/Project Management Risk

Team Project Management Risk instanex midterm.jpg

Technology/Design Risk

Technology Design Risk isn.JPG

View our Risk Log here

Technical Complexity

The technical complexity we have faced are ranked starting with the highest level of difficulty.

1. Developing the application to run on both online and offline mode.
In an event where the iPhone has lost 3G/wireless connection, user is still able to access certain functions of the application.
This ensures that the application is more robust and does not constantly rely on 3G/wireless to function.

2. Team is coding on Xcode 4.2.1 while most online tutorials are based on older versions of Xcode.

3. Team had decided to develop based on creating custom controllers of each function.

4. Development of application is an integration of knowledge based on 3 SIS modules - Enterprise Integration - Data Management - Software engineering

Quality of product

Intermediate Deliverables

Stage Specifications Modules

Project Management
Instanex Team Minutes Team Meeting Minutes
Instanex Supervisor Minutes Supervisor Meeting Minutes
Instanex Client Minutes Client Meeting Minutes
Schedule Metric Schedule Metric
Bug Metric Bug Metric
Acceptance Presentation Slides Instanex Acceptance Presentation
Mid Term Presentation Slides Mid Term Presentation Slides

Storyboard Storyboard (1)
Use Case Diagram Instanex Use Case Diagram
Business Process Diagram Proposed Business Process Diagram
System Architecture Diagram System Architecture Diagram
ER Diagram ER Diagram

Inventory Management UAT Inventory System UAT Document
iPhone UAT iPhone UAT Document


Electro Max IT systems are outsourced to external IT vendors and the IT vendor is in the midst of creating a test database which is a exact duplicate of the current database for the team to deploy on.

The team have registered a domain: www.electromaxiphone.com with Bluehost to upload PHP scripts of both the iPhone application & the inventory system. Bluehost is able to provide services such as phpmyadmin and web domains. Since the test database is not available at the moment, the team is using phpmyadmin service from Bluehost as a temporary database.

Once the test database is available, iPhone application and inventory database will be connected to the test database with the web domain serving as a web service in connecting both systems to the test database.

Deployment link: www.electromaxiphone.com/emintranet/login.php


As for mid term, we have 2 UATs done.
They are namely:
1. UAT for Inventory Management (Intranet System, and
2. UAT for iPhone Application

We have a total number of 30 testers.
Our 30 testers include:
- Adalene [Electromax Director]
- Yan [Electromax Inventory Manager]
- Electromax Staffs
- SMU Students

The total number of questions in each UAT:
- Inventory Management -> 23
- iPhone Application -> 19

The overall feedback we have received from both UAT is:
1. UI can be improved further
2. Professionalism for the both application can be improved

As our UAT is done on hardcopy, we have collated the results in a single document for each app.
To have a more detailed information on our UAT results, please view:
1. Inventory System UAT Collated Results
2. iPhone Application UAT Collated Results


Team Reflection

Click to view Team Member's Individual Reflection