Difference between revisions of "IS480 Team wiki: 2016T2 Remix final wiki"
Yx.yuan.2013 (talk | contribs) |
Yx.yuan.2013 (talk | contribs) |
||
Line 173: | Line 173: | ||
|- | |- | ||
|} | |} | ||
+ | |||
+ | === 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:=== | ===Deployment:=== |
Revision as of 23:29, 10 April 2016
Home | Midterm | Final |
---|
Project Progress Summary
Final Product:
- Final slides link: <to be updated>
- Deployed site address:
- Internal Users: http://52.76.235.20/ <domain name to be updated>
- Username: ttwang
- Password: password
- External Users: http://52.76.235.20/customer_authentication <domain name to be updated>
- Internal Users: http://52.76.235.20/ <domain name to be updated>
- Pitch video: https://youtu.be/a7Ro0ozKYzU
Project Highlight:
What unexpected events occurred?
- We did not consider the client's impact (delay, new change request etc.) on the project process. Overload alert function was delayed.
- Extremely high bug metrics happened in Iteration 4 <before midterm>
- List of requirement changes - As shown above in "Process based on Functions --> Change in Scope" <before midterm>
Project Challenges:
- Integration with Bitbucket API:
- Speed limitation on issue retrieving
- Unexpected changes happened in API provider: delete function was removed in Feburary
- Learning curve in React Js
- Lack of understanding of business process and basic analytical knowledge
Project Achievements:
- Successfully integrated with Bitbucket, a third party issue tracking tool
- Beta version released in January. Used data collected to improve the urgency calculation formula.
- Successfully built real time chat function using React js, together with user search and offline email alert functions.
- Successfully designed and implemented several analytical functions that helps our sponsor improve the efficiency
Project Management
Project Schedule (Plan Vs Actual):
Following is the planned VS actual hour per iteration.
Project Metrics:
- Schedule Metrics: Not applicable since we are using time boxing.
- Bug Metrics:
Technical Complexity:
Message notification and updates
To handle complicated components that are:
- Ajax enabled
- have multiple states
- have multiple data sources
- responsible for computing data and rendering its own UI independently
- responsible for distributing data to other components that require it
The nodes on the graph above represent components from our messaging services. There is a total of 10 different data flows. Additionally, depending on the data received or computed, nodes can have multiple states.
(e.g. File upload component with file attached or no files attached)
This was a big problem as it caused our UI to be unresponsibe and our code to be unmaintainable.
Bitbucket Oauth 2.0 authentication
We integrated Bitbucket into application. For this, we have to help developers and project managers log in to Bitbucket from our application.
This is difficult as we not only have to manage an extra level of authentication but also also synchronize both sessions (TSPMS and Bitbucket). Synchronization of the sessions was crucial for the user interface to be rendered correctly.
We felt that an additional complexity of managing and storing the API keys was that the keys have short lifespans; they expire after 30 minutes to an hour.
Scheduled events
We collect data from multiple sources for our custom Remix Analytics module. This process is tedious as we need to be precise for the calculation of accurate metrics. Additionally, the process is computationally intensive as well.
Quality of product
Project Deliverables:
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | 19Internal Meeting; 13Sponsor Meeting; 14Supervisor Meeting |
Metrics | Bug metrics | |
Analysis | Use case | Use Cases |
Business Process Diagram | Here | |
Design | ER Diagram | Here |
Class Diagram | Here | |
Testing | Testing plan | Here |
User testing | UT1 | |
UAT | Here | |
Handover | Manuals | Instruction on connecting to Bitbucket |
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:
- Internal Users: http://52.76.235.20/
- Username: ttwang
- Password: password
- External Users: http://52.76.235.20/customer_authentication
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 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.