HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T2 Silicon Geeks Final Presentation"

From IS480
Jump to navigation Jump to search
Line 166: Line 166:
 
|bgcolor="#D8FFC5"|90% Completed and tested
 
|bgcolor="#D8FFC5"|90% Completed and tested
 
|bgcolor="#D8FFC5"|1
 
|bgcolor="#D8FFC5"|1
|bgcolor="#D8FFC5"|Chun Fatt, Jeremy/ Problems with connecting to printer from a server side application
+
|bgcolor="#D8FFC5"|Chun Fatt, Jeremy/ Left alignment for remaining passes
 
|- align="left"
 
|- align="left"
 
|bgcolor="#D8FFC5"|Caml Query
 
|bgcolor="#D8FFC5"|Caml Query
Line 306: Line 306:
 
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.
 
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 Site:===
+
===Deployment:===
  
{| cellpadding="2" style="margin: 1em auto 1em auto" "height: 100px"  width="750px"
+
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]].
! scope="col" width="500" bgcolor="#E6E6E6"|<font color="black">Deployment</font>
 
! scope="col" width="500" bgcolor="#E6E6E6"|<font color="black">Information</font>
 
|- align="center"
 
|bgcolor="#D8FFC5"|
 
[http://202.161.45.124/SitePages/Home.aspx Link to Site]
 
|bgcolor="#D8FFC5"|
 
*Username: win2008_machine16
 
*Password: P@ssw0rd480
 
|}
 
  
 
===Testing:===
 
===Testing:===
Line 352: Line 343:
 
|1
 
|1
 
|align="center"| Tan Shu Han
 
|align="center"| Tan Shu Han
|align="left"| My biggest takeaway from this FYP is that I have to learn how to be an independent thinker, and a good coordinator. Many changes took place in this journey, including member's unprecedented commitments, overseas trips and school commitments, as well as changes to project scope. It is important to be able to decide quickly on what's the next step and how to keep the team and project going. Consistent follow-ups with the team members and client are also very important attributes in this project to ensure project is working according to the timeline given. Perhaps I could have done better in communicating with the team members, as the main mode of communication is Whatsapp/Facebook outside of meetings, messages may have been misinterpreted and causing errors. I would have called them up or look for them personally outside meetings if there are urgent matters for the project if I have to do this again.  
+
|align="left"| My biggest takeaway from this was the importance of linking the test cases to the business requirements rather than just testing on the technical components of functionality. In addition, I have also learnt to conduct usability test more efficiently through finding users which are close to our actual users and asking them to play the role of the actual user. It is also important that we explain the business scenario properly, which was a major challenge during testing.
 
|-
 
|-
  

Revision as of 21:12, 20 November 2014

Final logo.PNG

Home Team Description Project Overview Project Management Project Documentation Project Testing Key Milestones


Acceptance Presentation   Mid Term Presentation   Final Presentation



Project Progress Summary

Deliverable

Final Presentation Slide

Deployment Information

Link to Site

  • Username: win2008_machine16
  • Password: P@ssw0rd480
Current Phase

Current Iteration: 13
Development: 90% Of Core Modules and 100% Completion of Secondary Modules
Starts: 9 November 2014
Ends: 23 November 2014
Current Status: Slight delay in our current iteration because the printing code is not working on the client side but working on local computer.

Iterations Remaining (Excluding Current Iteration)

1

Project Highlights:

Iteration Features Description Action
5 First Printing First Printing of card was unsuccessful Relook at the codes. Decide to take a look at the printer SDK instead of using javascript
6 Local Deployment Acceptance Feedback that deployment was not done for reviewers to look at our application Approach Fiona for obtaining a school VM
7 Merging of Forms Acceptance Feedback given that the webparts should be merged Merge the webparts together. Feature pushed forward to this iteration.
7 Local Deployment Obtaining of school's VM took longer than expected -
8 Caml Query Jason proposed to ask about finding a more efficient way of retrieving the data Introduce new function - Caml Query
9 Create New Pass Type Sponsor proposed the flexibility of the user to create any new pass type that he wants Added as new functionality for Iteration 11 and 12
9 Tableau Analytics Sponsor interested in obtaining a connection from Tableau to SharePoint Added as new functionality for Iteration 11 and 12
9 Printing Module Troublesome to do testing with Sentosa printer during office hours Printer was brought home over the weekend for testing.
10 Change in Sponsor Angeline (Sponsor) officially step down and a new sponsor (Fayyaz) took over. Update Supervisor and Project Coordinator on the new changes
10 Printing Module Difficulty in obtaining the printer to carry on alignment testing for the rest of the card type Lead to a delay in the iteration. Rest of modules still carry on in schedule as per normal.
11 UI Module Midterm Feedback about the lack of UI Design UI Module added. Create New Pass Type functionality dropped.
11 Tableau Analytics Face some technical issues and we were unable to connect SharePoint lists to Tableau. Hence we focus on priority functions Tableau Functionality dropped.
11 Usability Testing 2 Usability Testing 2 to be done with the new revamp design User Testing 2 postponed to Iteration 13
12 Client Deployment Jquery features all not working Debugging to be carried out immediately
13 Client Deployment 2 Codes that accesses the printer API is run on the server side, but the printer is connected locally via USB cable. Hence the code cannot access the printer Currently in the midst of debugging

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.

  • Connecting the printer to the network that Sharepoint server can recognise. Currently the printer is connected to a standalone computer which the is only recognisable by the particular computer with the old card printing software. However, our application is deployed in the Sharepoint server and the printing process is done through the backend of our application. Thus, we had to work closely with the external vendor of Sentosa to solve this issue as we were afraid that we might crash the system if we were to connect it without any help.

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.

  • Despite the challenges faced, our team managed to deploy the application on to the server and the users were satisfied with our progress and work done.

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):

Deployment_Diagram

Scope Change

Add Search Pop up & Reissue functionaity

  • Priority to be on core functionality as there were some unexpected bugs and we wanted to ensure that core functionalities work as best as possible
  • Time spent on revamping the UI design for the web parts through using of Jquery and SPquery
  • Hence we drop Create new Pass Module as we realise that after our research, it will be too time consuming and complex
  • Added Reissue feature which allows the user to create multiple cards in one shot.

Dropped Tableua Functionality

  • Face some technical issues and we were unable to connect SharePoint lists to Tableau. Hence we focus on priority functions

Testing

  • Usability testing and UAT to be shifted as we wanted it to be tested after the search popup was implemented
Module Status Confidence Level In-charge / Comment
Create Pass 100% Completed and tested 1 Chun Fatt, Wen Jie
Edit Pass 100% Completed and tested 1 Alex, Shu Han
Card Design Tool 100% Completed and tested 1 Jeremy, Leonard
Merging of Create & Edit 100% Completed and tested 1 Chun Fatt
Zebra Printer Print Script 90% Completed and tested 1 Chun Fatt, Jeremy/ Left alignment for remaining passes
Caml Query 100% Completed and tested 1 Shu Han, Leonard
Reporting Functionality 100% Completed and tested 1 Wen Jie, Alex
Export 100% Completed and tested 1 Alex
Search Popup 100% Completed 1 Chun Fatt, Jeremy
Jquery Enhancement 100% Completed 1 Chun Fatt, Leonard
Reissue 100% Completed 1 Alex, Jeremy

Project Metrics:

Details about the metrics

Summary of the metrics


Iteration Number Percentage Reason Solution
4 78.57% Underestimate the time taken to complete certain modules. Re-estimate the following tasks and reschedule.
5 85.29% Picture overlay and drawing text on pictures proves to be more challenging than expected because it requires more time to learn.
  • Re-estimate following tasks and reschedule.
  • Provide more time for difficult functionalities that team members have not tried before.
9 88.23% Testing of printing code could only be tested with the specific printer. Hence, it requires more time instead to complete testing and debugging the code. Re-estimate following tasks and reschedule.
10 83.33% Alignment of cards took longer than expected to complete because of the difficulty of obtaining the printer Re-estimate following tasks and reschedule.
12 65.22% Jquery error occurs when deployed on client side. Re-estimate following tasks and reschedule.

Technical Complexity:

Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.

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:

Stage Specification Links
Project Management Meeting Minutes Meeting Minutes
Metrics Metrics
Requirements Gathering Business Requirements Project Overview
Current System Client Current System
Analysis Deployment Diagram Deployment Diagram
Use Case Use Case Diagram
Design UI Prototype UI Prototype
Testing Test Plans Internal Test Plan and Test Cases
Bug Metric Bug Metric

Deployment:

Deployment_Diagram



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 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

Team Reflection

Team Reflection
***


Individual Reflections

S/N Name Reflection
1 Tan Shu Han My biggest takeaway from this was the importance of linking the test cases to the business requirements rather than just testing on the technical components of functionality. In addition, I have also learnt to conduct usability test more efficiently through finding users which are close to our actual users and asking them to play the role of the actual user. It is also important that we explain the business scenario properly, which was a major challenge during testing.
2 Chan Chun Fatt Upon finishing FYP, I am more confident in working with large data. The project gave me an overview of how data in the real word would be, with many unmatched rows and columns, inconsistency in phrases and words. Data cleaning is time-consuming, yet I have learnt along the way how to make the progress more effective and efficient.

Being in a team, supporting each other team member is also crucial; I have improved my soft skills in working in a diverse team.

3 Chuah Li Xian This project has really prepared me for real life work experience. I have learnt an important lesson from this project. Anything that can go wrong, will go wrong. It is how we react to these sudden changes that matters. As a programmer who experienced a lot of unexpected setbacks, the only thing I can do is to stay resilient and proceed ahead with a solution.
4 Jeremy Lim Self-learning is important. There are skills and knowledge, especially regarding design tools and software, are not taught in school and I have to learn them myself. Because of time constraint, I have to train myself to be a fast learner to quickly pick up the necessary skills for the role.

In addition, I have learnt that collaboration is extremely important. There are different ideas and suggestions from supervisors, clients, project reviewers and also from other team members. I had to collaborate with not only other team members ourselves but also with clients and supervisors bring the ideas into action and to the real production.

5 Lee Wen Jie This project has taught me that in the real working world, always be prepared for many unexpected situations. Be prepared to adapt, be prepared to try harder, and be prepared for changes. It also taught me that as a PM, there are alot of planning to be done especially when it concerns a large scale project such as FYP. Time management is extremely critical in order for us to juggle between school and FYP
6 Leonard Ong Apart from the usual time management and project coordinating, one biggest takeaway will be conducting user testing efficiently. When conducting user testing in big groups, it was important for us to ensure that all participants are clear of their roles and will give useful feedbacks. That aside, time management was extremely critical in this stretch of our project as we have many pressing datelines, while having to consistently work on the FYP. Through these, i was not only able to work more efficiently, but have also learnt to be more independent when doing the project


S/N Name Reflection
1 Mohamed Fayaz Reissue Function is very helpful. Summary report functions is very efficient and save us alot of time in the preparation report for management used.
2 Adeline Kwok Search pop p feature is very useful to users, saves time searching through the list for past entries.

Being in a team, supporting each other team member is also crucial; I have improved my soft skills in working in a diverse team.

3 Remedios B. Pena Customized fields are helpful in our tracking of records. it is clear, and specific to our requirements & functions.