Customer feedback on CricMantra

The application developed met the requirements given. And we are extremely happy with the product we got. We are planning for enhancements to this application in the near future. As we are satisfied with your work, we will get back to you once we consolidate the enhancements required on this application. Once again thank you very much for the quality work provided.

Regards,

Cricmantra.

User guide for "Galaxy Book Suppliers" application

This is an application for the use of different departments in "Galaxy Book Suppliers". 

Different departments present in the company are

1. Sales Department
2. Inventory management Department
3. Finance department

These departments can use different pages of this application according to the permissions they have on those pages (can be used by providing required authentication for that page). Any department can see all the pages, but cannot use them until they provide required authentication

Sales department can use the following pages

• Make an Order
• Add a Privileged Customer
• Edit a Privileged Customer

Inventory Management Department can use the following pages

• Add a Book
• Edit a Book's quantity
• Deliver Books

Finance department can use the following pages

• Confirm payment
• Edit a Book's Price

The different flows that can happen in the application are

• Make an Order (Sales Dep) --> Confirm payment for an order (Finance Dep) --> Deliver Books in an Order (Inventory management Dep)
• Add a book to inventory when a new book comes (Inventory maangement Dep) --> Edit Quantity of a Book when ever extra no. of already existing books come (Inventory management Dep)
• Edit a Book's price whenever needed (Finance Dep)
• Add a Privileged customer into the system based on his previous purchases from the company so that he can get discount (Sales Dep) --> Edit the details (such as discount) of an already existing privileged customer based on his recent purchases from the company (Sales Dep)

Detailed description of each page is as follows

Add a Book:

Inventory management department can add a book into the system whenever a new book comes by providing Name, author, quantity available and price of the book. This is the base form through which any book should enter into the system initially. Only those books entered through this form will be available in the system. Name of books being entered should be unique. Each and every different book will be recognized by its name.

Edit a Book's Quantity:

Inventory management department can edit the quantity of an available book using this page whenever new issues come to shop. Only books available in the system will be shown in the book dropdown

Edit a Book's Price:

Finance department can edit the price of an available book using this page whenever required. Only books available in the system will be shown in the book dropdown

Add a Privileged Customer:

Sales department can add a privileged customer into the system by providing name of the customer, no. of orders made, value of orders and discount available to that customer. This is based on previous interaction of that customer with the book shop. Each Privileged customer should be uniquely recognized by his name. i.e., name of each and every privileged customer should be different.

Edit a Privileged Customer: 

Sales department can edit the details of an existing privileged customer such as no. of orders, value, and discount. This is based on his/her recent interaction with book shop.

Make an Order: 

Whenever customer makes a call or directly approaches a sales person (Sales Dep), he can make an order for that customer using this form. 

• Order ID will be automatically generated in this page and cannot be changed
• When a customer name has been entered in this form, if it matches (exactly - case sensitive) with any of the existing privileged customer, discount allowed for him will be automatically generated in this form. If not discount will be zero
• And then user needs to select one of the available books. When a book has been selected, the price of the book and quantity available will be automatically displayed
• And then user needs to enter the quantity of books customer needs
• And then total amount customer needs to pay will be automatically generated based on price, quantity ordered and discount available to customer

In this way sales person can make an order for a customer using this form

Confirm payment: 

When a customer pays the total amount regarding a particular order, Finance department can confirm payment for that order by specifying the mode of payment. Upon selecting an existing order, name of the customer and total amount will also be displayed in the form which cannot be edited. Only those orders whose payment is not confirmed yet will be available in this form

Deliver Books: 

Whenever Finance department confirms payment for an order, Inventory management department can deliver books for that order. Only those orders whose payment is confirmed and Delivery is pending will be available in this form. If available inventory is less than the number of books need to be delivered for that order, then user cannot deliver that order (System will not allow). If available inventory is sufficient to deliver that order, then user can deliver that order. And in this case after successful delivery of that order, inventory remaining will be updated correspondingly.

General information regarding the Application:

This application can be accessed in the following location Galaxy Book Suppliers

To use different pages of this application, different passwords required are as follows

SalesRep Password: SalesRep
InventoryDep Password: InventoryDep
FinanceDep Password: FinanceDep

sample

Online Form powered by

Requirements for Zoho application

Cric Mantra

As a cricket fan, I want to maintain my own data of each match in two aspects. First being all the details of the match and second being performance of each player. So I want two interfaces to add the corresponding details.

Interface to add Match details:

The columns it should contain are Match ID, Match Type, Date, Venue, Team1, Team2, Umpire1, Umpire2, Winner, Man of the Match

Some rules that this interface should follow are 

- It should not allow to enter a Match ID which already exists

- Match Type should be a dropdown

- Date should not allow future date

- Team1 and Team2 should be dropdowns which should be populated from a list which can be dynamically modified

- Team1 and Team2 should not be same

- Winner should be one of the playing teams

- Umpire1 and Umpire2 cannot be same person

- On a same date no team can play more than one game and no umpire can attend more than one game

- On successfully adding a match details interface should redirect the user to the second interface where he can add player performance detail.

Interface to add player performance details: 

It should contain two columns. The Match ID and Performance. The Performance dropdown should contain Team1 Batting, Team2 Batting, Team1 Bowling, Team2 Bowling and the man of the match. Selecting each should take you to the required form to enter the player details. After entering each player detail, the form should take you back to the Performance page.

Team1 and Team2 Batting interfaces:

The columns which these interfaces should contain are Match ID, Batsman, Out, Bowled, Caught By, Run Out By, Stumped By, Description, Runs, Balls, 6’s and 4’s.

-The Match ID should be populated from a drop down which contains values entered in the Match Details form.

-Same batsman cannot be entered twice for the same Match ID.

-There are 10 ways in which a batsman can be out. All these should be populated in the drop down for Out column. In addition, it should contain Not Out and Did Not Bat status.

-The Bowled, Caught By, Run Out By and Stumped By columns should be accordingly for the different selections in the drop down for Out column.

-Description column should be auto updated on input in the above columns.

-The number of 4’s and 6’s hit should aggregate to less than or equal to the total runs taken.

-The Batsman should at least face one ball to score a run.

-The batsman should face at least two balls to score runs and be out by Bowled, Caught, Stumped, LBW, Hit the ball twice, Handling the ball or Hit wicket.

-The batsman should face at least one ball to be out by Bowled, Caught, Stumped, LBW, Hit the ball twice, Handling the ball or Hit wicket.

-There can only be a maximum of two not outs and 11 players entered for one Match ID.

Team1 and Team2 Bowling interfaces:

The columns which these interfaces should contain are Match ID, Bowler, Overs, Maidens, Runs and Wickets.

-The Match ID should be populated from a drop down which contains values entered in the Match Details form.

-Same bowler cannot be entered twice for the same Match ID.

-The maximum number of overs bowled by a bowler is 10 and total overs are 50 for a Match.

-The overs can be incomplete and it should be of the form x.y where y in [0, 5]. Y should not be greater than 5.

-The number of maidens bowled cannot be greater than the number of overs bowled. The maidens should be integer value.

-The total number of wickets cannot exceed 10 for a Match ID.

-Maidens cannot be less than overs-runs.

Man Of the Match interface:

The columns it should contain are Player Name, Match ID, Role, Runs, 6's, 4's, Overs bowled, Maidens Bowled and Wickets.

Some rules that this interface should follow are 

- Match ID should be a dropdown populated from the existing Match IDs which were already entered using the first interface

- Role should be a dropdown whose values can be Batsman, Bowler, All-rounder, Batsman/WK and Bowler/WK.

- When the role selected is a batsman, the following fields should not be shown to user. They are Overs bowled, Maidens Bowled and Wickets taken.

-Similarly if the role selected is bowler Runs, 4’s and 6’s should not be shown to the user.

- No two man of the Match is possible for the same match.

Develop an application satisfying the above requirements. Please contact in case of any ambiguity and add any sensible features if missed after confirming.