search

oldcai / ITPMAssignment

0 stars 1 forks source link

Collecting Requirements #3

Open oldcai opened 4 years ago

oldcai commented 4 years ago

Hi, since we have chosen the loyalty plan, we can start to collect requirements now.

GitHub is a better place than chatbox since the topics are separated in a organized way.

Nagasubramaniyan commented 4 years ago

Business Requirements:

The customer logs into the loyalty program web application to check for the offer information and redeems. There can be a flat-file system or a Database management system to handle the customer information and offer information for each customer respectively.

There will be two categories of offers listed to the customer one is general (such as first time user, Credit card offers, Cashbacks,etc.,) and another one user-specific (such as special discounts, wallet offers, etc.,) displayed based on the frequency factor which is the key filter for providing the offers.

The frequency factor can be determined by the organization as the customer ticket booking and travel criteria (more than 5 ticket bookings then for 3 more tickets, the offer may be updated and also based on the membership (silver, gold, platinum)). Once the coupon is selected by the customer for any ticket booking then the offer is updated as used and not valid anymore in the data source.

Reference links: https://www.openloyalty.io/ https://antavo.com/blog/customer-loyalty-programs https://www.voucherify.io/blog/architecture-of-customer-loyalty-software-a-guide-for-product-managers

Technology recommended: Front end: Bootstrap, Javascript, and jQuery Back end: Spring Boot Database: H2

Reference link: https://spring.io/projects/spring-boot

oldcai commented 4 years ago

Business Requirements:

The customer logs into the loyalty program web application to check for the offer information and redeems. There can be a flat-file system or a Database management system to handle the customer information and offer information for each customer respectively.

There will be two categories of offers listed to the customer one is general (such as first time user, Credit card offers, Cashbacks,etc.,) and another one user-specific (such as special discounts, wallet offers, etc.,) displayed based on the frequency factor which is the key filter for providing the offers.

The frequency factor can be determined by the organization as the customer ticket booking and travel criteria (more than 5 ticket bookings then for 3 more tickets, the offer may be updated and also based on the membership (silver, gold, platinum)). Once the coupon is selected by the customer for any ticket booking then the offer is updated as used and not valid anymore in the data source.

Reference links: https://www.openloyalty.io/ https://antavo.com/blog/customer-loyalty-programs https://www.voucherify.io/blog/architecture-of-customer-loyalty-software-a-guide-for-product-managers

Technology recommended: Front end: Bootstrap, Javascript, and jQuery Back end: Spring Boot Database: H2

Reference link: https://spring.io/projects/spring-boot

I agree with the front end part. But I recommend using Django as the backend solution since it needs less code to implement the same functions, and I had 8 years of experience of using it. PostgreSQL or MySQL are both databases that can be easily integrated with Django.

By the way, those links are quite informative, thank you for sharing that.

oldcai commented 3 years ago

image This might be helpful when implementing the system.