Showing posts with label design. Show all posts
Showing posts with label design. Show all posts

Saturday, May 30, 2009

Symfony of Love Day 2: Business Case

On the day 1, I already defined the simple requirements for my new project. Now, going further to define the business case. I made an observation on how my wife running the business. Below are the scenario,

1. Items are coming from the supplier.

a. When items are coming from supplier, their information should be recorded into the system. The important information are Item name, description, weight, photo (yes, it would be nice to have the picture of it), purchase price, quantity, minimum stock level for re-ordered and also the storage location if already decided. Otherwise, a default location would be supplier by the system.

b.When the item is not yet in the system, there should be a new window displayed to record the information of the new item.

c. After all items have been recorded, a summary page is displayed listing all items received from a supplier, then supplier information is also entered including the shipping cost.

d. Next step is to determine the sale price. The items are displayed in a table contains information about purchase price, shipping cost, suggested sale price (5% profit, 10%profit, 15% profit, 20% profit, 25% profit, 30% profit, 40% profit and 50% profit). The last column would be final sale price.

e. After sale prices are determined. The process is finished and back to main menu.


2. Customer makes a purchase.

a. When customer makes a purchase, a window displayed to provide the operator to record the items to be delivered to the customer. The information needed is item id/name, quantity and delivery date, due payment date, the customer information and also the payment method.

b. After all information required are recorded, operator should be able to print out the invoice. Two invoices are generated. One with the "Copy" watermark and the other one is "Paid" watermark.


3. Management.

a. CRUD of items (stock management), customers and payment method.


I know, probably this is what I would not do in the real business case. However, I am short of time at the moment ;( so that's all for today.

Thursday, May 28, 2009

Symfony of Love Day 1: Introduction

Why I called this project as Symfony of love? There are two reasons, first and the most important one is because I dedicated this project to my wife and second, I hope I can learn Symfony.


Background:

It has been few years that my wife is running her business from home. She sometimes asks for a software to help her in managing her business to replace her old excel system. I called it an excel system, since it is actually a system that is utilizing excel. Not the excel is the core of the system, but how she defined the procedures and utilized the sheets to do the calculation are the core of the system. Remember, excel is only the tool. One day, when we do not have access to excel, she can open and run it in OpenOffice Calc (good to hear!).


Objective:

Create a system to help small business in managing stock, price and orders. I know there are many and probably better solution for her (and others) but making one for your special one is very special!!!


Requirements:

I make it as simple as possible for the version 0.1:

R1. The system shall be able to be used to manage the stock of a product including its location. A notification will be issued when an item has reached a certain level thus need to be reordered.

R2. The system shall be able to be used to manage orders from clients including the their payment information.

R3. The system shall be able to be used to help in calculating the selling price.


I know they are still very broad requirements and i will make them more detail and clear in the business case on the next day.