JCart Release Planning

In our previous article JCart Requirements Analysis  we have listed out all the requirements that we need to implement for JCart application.  Now we need to come up with an implementation and release plan. As we are following iteration model, we will plan for N iterations where in each iteration we will implement some usecases.

After listing out all the implementation tasks and based on the task dependencies, we came up with the following Iteration plan.


  • Initial code setup for Admin webapp
  • Domain Modelling and Database Designing
  • Creating JPA Entities
  • Email Service SetUp
  • Admin UI Layout SetUp
  • Admin Login
  • Admin Forgot Password
  • Admin Reset Password
  • Configuring HTTPS/SSL/TLS
  • Setting up Jenkins/SonarQube


  • Security
    • Manage Privileges – List all privileges
    • Manage Roles
      • List all Roles
      • Create new Role
      • Add/Remove Permission to/from Role
    • Manage Users
      • List all Users
      • Create new User
      • Add/Remove Roles to/from User


  • Site Settings – Locale & Currency
  • Manage Categories
    • Create new Category
    • Update category
  • Manage Products
    • Create new Product
    • Update Product


  • Initial code setup for ShoppingCart webapp
  • ShoppingCart UI Layout setup
  • Configuring HTTPS/SSL/TLS
  • Home Page
  • Category Page
  • Product Page
  • Product Search Results


  • Add To Cart in HomePage/CategoryPage/ProductPage
  • Cart Page
    • View Cart Items
    • Updates Quantity
    • Remove Items


  • Mock PaymentService
  • Billing & Delivery Page
  • Customer Login
  • Customer Registration
  • Order Confirmation Page
  • Send Order Confirmation Email


  • Manage Orders
    • List all Orders
    • View Order details
    • Update Order status
  • Manage Customers
    • List all customers
    • Search customers
    • View customer details


  • Customer MyAccount Page
    • Profile
    • Order History

So, for now these are all the usecases we have identified and added to our iterations. We may come to know few more usecases going forward.
Looks like we are good to start the implementation. But before jumping on to coding let us take a look at our development environment setup in next article.

Leave a Reply

Your email address will not be published. Required fields are marked *