HeaderSIS.jpg

Dpenz Final Wiki

From IS480
Jump to navigation Jump to search

Project Progress Summary

Final slides link: To be added
Deployed site link: http://202.161.45.128/Final%20Year%20Project

Login Details
User Role Name XPID Password
Procurement Staff Tom 9003 INGBank
Head of Procurement Matthias 9010 INGBank
Functional Owner Marlie 9112 INGBank
Functional Owner Dany 9113 INGBank
Functional Owner Mandy 9002 INGBank
*Note: any Functional Owner can be an approver of a project.

Project status

All functions have been completed, with 5 user tests conducted in total.

Changes since Midterm

  • Fully implemented changes from Midterm feedback (i.e. Field validations, currency code, archiving, etc.)
  • Fully implemented remaining functions (Admin panel, Export project details, Export report)
  • UT5 with client side
  • Fully implemented changes from UT5 (i.e. Aesthetic improvements such as terminology)

Project Highlights:

  • Started out coding in java as client was unable to confirm programming language that was supported in the bank. Upon being updated on the language, we took 3 weeks to learn ASP.NET which we all did not have prior experience in.
  • Additional requirements included based on midterm feedback:
    • Archiving
    • Importing of users via CSV file
    • We relooked at our schedule and catered in more man-hours (within our capacity) to add in these functions, as they were necessary for our system.
  • In our final UT5 with the client side, they were pleased with our system as it exceeded their expectations and this made our efforts all worth it.

Project Challenges:

  • We were behind time for a few of our sprints and it was not easy to catch up for subsequent sprints, but we dedicated more man-hours and managed to be early for Sprint 8.
  • Revamped the entire Approval process as clients were unable to confirm the exact process flow previously. We constantly communicated with the client so we were able to make the changes as soon as the correct process was released to us.

Project Achievements:

  • One of our main selling points was the flexible and scalable Procurement Approval Form (PAF) template. It allowed for dynamically adding/removing/re-ordering the various phases and fields contained in the PAF. We successfully catered for our database structure to accommodate the constant changes in the PAF template.
  • As we were behind time for a few sprints, we had to compensate by adding in more man-hours. We helped each other with our parts whenever we could as the one who knows how to solve the bug might not be the one who was responsible for coding it. This teamwork paid off when we finally caught up to end Sprint 8 early.

Project Management

Current project status:
Dpenz Timeline.jpg

Project Schedule (Plan Vs Actual):

This is a chart of how our schedule lines up. There were some delays in the middle, but since midterm, we have put in extra man hours a day and slowly caught up to our planned sprint end dates. We have even ended our sprint early in Sprint 8. More details of our schedule is on our Project Schedule page.

Regarding the scope, we have implemented some additional features based on feedback from midterm, our supervisor and our sponsor, and we have evaluated that these features can value add to our system and it can fit within our project time frame. These change requests have been documented in our Change Management section.

Dpenz Sprints Overview.JPG

Project Metrics:

More details of the metrics can be found on the Metrics Management page.

Schedule metrics

Dpenz SM values absolute.JPG

Dpenz Current SM values.JPG



Effort metrics

Dpenz Current EM values.JPG



Bug Metrics

More details in Bug Metrics section.

Dpenz Bug Chart.JPG

Quality of product

We designed our system with usability as our priority. As such, we allow for customisability such as customizing the PAF template and some report generation fields. The highlight of our product is that we provide a flexible structure for our clients to customize their project form template so that they can configure the form template using the user interface instead of going through the IT department. To make the Edit PAF Template easier to use, we also implemented the drag and drop functionality. On all tables, we have also implemented the sortable function so users can find their desired data easily. We also have several search bars to make locating information easier.

Design Considerations

  • In the design of our UI, we made sure to use the the principles we have learnt in IDP. For example, Nielsen's 10 heuristics. We conducted heuristic testing, received feedback during our user testings and made changes according to feedback received, and we conducted an AB testing to improve our design further.

Project Deliverables:

Stage Specification Modules
Project Management Minutes Meeting Minutes
Metrics Metrics Management
Project Schedule Project Schedule
Product Burndown Chart Product Burndown Chart
Risk Management Risk Management
Change Management Change Management, Change Log
Requirements Project Description Project Description, Requirements List
Analysis Use case Overall Use Case Diagram
Architecture & Deployment Diagram Architecture Diagram
Project Process Flow Process Flowchart
Design Class Diagram Class Diagram
Testing User tests User Tests Conducted
Bug metrics and trackers Bug Metrics
Handover Manuals


Quality:

Technical Complexity (will be up soon but for now please refer here to our slides)

User Testing:

The whole set of our user testing results can be seen on our User Testing page.

User Test 5

UT5 was the last user testing performed with our client before the end of our IS480.

Goal: Functional testing of our system with all required features implemented. Testing was done with real data (real XPIDs, dummy project data) to test the usefulness and content validation of our system.

Please view more details of this on our User Testing page.

Dpenz UT5 Photo1.jpg
Dpenz UT5 Photo2.jpg

Reflection

- new skills: new domain knowledge, technology...etc - improving existing skills: any further development of existing skills? - challenge: wad challenges? How u overcome? How u learn on ur own? Compile common lessons and reflection for the team and for each team member. Be brief.

Team Reflection:

We have learnt how to work with a new language and framework: ASP.NET MVC4. We have shared our resources on the Knowledge Base page here.
In our project, we have also learnt how to work with our difference and be aware of each other's strength and weaknesses so that we can work most efficiency for our project.

Individual Reflection:

Bing Huan (Dex): As the QA lead, I ensure the high quality of our system. I now think that quality assurance is an important aspect in software development that cannot be neglected and proper planning for the testing process is needed to ensure a high-quality product. Through QA, I have become better in debugging issues and communicating problems to the rest of my team who will help with resolving the problems.

Ching Png: As the lead developer, I have learnt the importance of building a strong architectural framework for my team members to work on. I also learnt the importance of learning from each other and helping one another out as we all have strengths in different areas. This project has really honed my technical skills and I am glad that we used ASP.NET as it is really helps us to build a system very quickly. If I were to develop a system rapidly in future, I would use ASP.NET

Malique: As the assistant PM and developer, I have learnt more about using the Scrum framework in project management. It will be a framework that I will consider in future for software project managements. I have also improved my technical skills through this project as we got to try out new technology that we have never used before, such as ASP.NET and other packages such as iText.

Mei Hui (Nicole): As the business analyst, I have improved in my communications with the client. I learnt how to be firm and tactiful when interacting with the client, especially so at times where we have to persistently bug our clients for actionable items and rejection of change requests. I have learnt that my role is important in helping the team define the scope of our project and to ensure that we deliver what the client really wants.

Zoey: As the project manager, I learnt how to look at the big picture of the project and manage the different aspects that would contribute to the success of the project. I learnt the importance of planning and managing all the resources well, as well as all the stakeholders involved in the project such as the client, supervisor and most importantly, my team members. Through times when we faced delays from administrative issues and restrictions or constant changes, I have learnt to be adaptable in re-allocating our schedule and resources accordingly, and plan out workarounds for the problems we face.