Welcome, Guest: Register On Nairaland / LOGIN! / Trending / Recent / NewStats: 3,194,726 members, 7,955,746 topics. Date: Sunday, 22 September 2024 at 02:13 PM |
Nairaland Forum / Science/Technology / Programming / Sales And Invoicing Application (1522 Views)
Sales And Installations Of Wallpaper And 3D Wall Panels (2) (3) (4)
Sales And Invoicing Application by rukie(f): 12:55pm On Nov 30, 2011 |
How can I create an application for sales and invoicing |
Re: Sales And Invoicing Application by Nobody: 2:17pm On Nov 30, 2011 |
A very big question really. What language are you planning to use? |
Re: Sales And Invoicing Application by Chimanet(m): 3:14pm On Nov 30, 2011 |
Do u knw OOP well ? if so u wont have a problem, think of the invoicing system as consisting of objects such as stocks, invoice, invoiceLineitem, Sales, Customer etc. You will need a data store (example a database to help u persist ur domain objects, access will be ok), then with a good business logic and nice interface u will be done i no time, ok start lyk this: Usecase Overview 1. what are ur use cases ? what do u want the user to do with the app? i. add item to stock ii. view items in stock iii.update item in stock iv. add a new customer(if u decide to model the customer may be u want to keep track of ur customers like opening a ledger for each customer it depends on the kind of business) v.view daily sales vi.view all customers(if u decide to model the customer) vii. create invoice viii. save invoice ix.print receipt x.refund customer his money xi.etc, Analyse ur use case very well so that u will discover some other requirements that the software will satisfy. [color=#000099]Design and implementation overview[/color] From the usecase, you will discover Classes with various methods and attributes, find a way to collaborate the various objects to achieve the various usecases specified.Confine each object to its particular duty eg ur InvoiceLineItem will have to calculate the price of each line in the invoice, while the invoice class which have a collection of InvoiceLineItem will take care of calculating the total price of all items, adding and removing item in the invoice etc. ur payment object will have to take care of all payments and report back to tell the invoice Object if the customer has paid or not.before an invoice adds an item it has to confirm from the data store if the specified item and amount of quantity requested exist in the database, the invoice supplies the receipt object with information it will use to do the print reciept method, the invoice will have a save method that will use to call the data store object to update the records in the database to reflect the completed transaction, the data store does all talking with the database and gives out public interfaces to client objects lyk invoice and sales object. When designing, find ways of implementing polymorphism so that u can easily change ur code codes if u want improvement in the future the interface should be fairly simple with labels, text fields, combo box,Table,buttons Forms,dialogs to display errors etc,add button, remove button, commit transaction button,print receipt,Refund form with text fields and buttons etc create a database of tables lyk Stocks,Sales,refunds finally test ur codes to make sure it perfectly satisfy ur use case requirements. |
Re: Sales And Invoicing Application by rukie(f): 3:41pm On Nov 30, 2011 |
Planning to use phpmysql. |
Re: Sales And Invoicing Application by Chimanet(m): 5:33pm On Nov 30, 2011 |
Do u knw OOP well ? if so u wont have a problem, think of the invoicing system as consisting of objects such as stocks, invoice, invoiceLineitem, Sales, Customer etc. You will need a data store (example a database to help u persist ur domain objects, access will be ok), then with a good business logic and nice interface u will be done i no time, just java or csharp will be better if u intend to develop for windows ok start lyk this: Usecase Overview 1. what are ur use cases ? what do u want the user to do with the app? i. add item to stock ii. view items in stock iii.update item in stock iv. add a new customer(if u decide to model the customer may be u want to keep track of ur customers like opening a ledger for each customer it depends on the kind of business) v.view daily sales vi.view all customers(if u decide to model the customer) vii. create invoice viii. save invoice ix.print receipt x.refund customer his money xi.etc, Analyse ur use case very well so that u will discover some other requirements that the software will satisfy. Design and implementation overview From the usecase, you will discover Classes with various methods and attributes, find a way to collaborate the various objects to achieve the various usecases specified.Confine each object to its particular duty eg ur InvoiceLineItem will have to calculate the price of each line in the invoice, while the invoice class which have a collection of InvoiceLineItem will take care of calculating the total price of all items, adding and removing item in the invoice etc. ur payment object will have to take care of all payments and report back to tell the invoice Object if the customer has paid or not.before an invoice adds an item it has to confirm from the data store if the specified item and amount of quantity requested exist in the database, the invoice supplies the receipt object with information it will use to do the print reciept method, the invoice will have a save method that will use to call the data store object to update the records in the database to reflect the completed transaction, the data store does all talking with the database and gives out public interfaces to client objects lyk invoice and sales object. When designing, find ways of implementing polymorphism so that u can easily change ur code codes if u want improvement in the future the interface should be fairly simple with labels, text fields, combo box,Table,buttons Forms,dialogs to display errors etc,add button, remove button, commit transaction button,print receipt,Refund form with text fields and buttons etc create a database of tables lyk Stocks,Sales,refunds finally test ur codes to make sure it perfectly satisfy ur use case requirements. |
Re: Sales And Invoicing Application by Nobody: 6:46pm On Nov 30, 2011 |
So what exactly is the problem here? Is it that you are looking for the algorithm or you dont have enough skills to do it or what? You must be clear on what kind of help you need. Yes, you can code it with phpmysql. |
Re: Sales And Invoicing Application by Chimanet(m): 6:58pm On Nov 30, 2011 |
Spam bot wahalla. hw i go solve am house? |
Re: Sales And Invoicing Application by Chimanet(m): 7:01pm On Nov 30, 2011 |
Do u know OOP well ? if so u wont have a problem, think of the invoicing system as consisting of objects such as stocks, invoice, InvoiceLineitem, Sales, Customer etc. You will need a data store (example a database to help u persist ur domain objects, access will be OK), then with a good business logic and nice interface u will be done i no time, just java or Csharp will be better if u intend to develop for windows OK start like this: Use case Overview 1. what are your use cases ? what do u want the user to do with the app? i. add item to stock ii. view items in stock iii.update item in stock iv. add a new customer(if u decide to model the customer may be u want to keep track of your customers like opening a ledger for each customer it depends on the kind of business) v.view daily sales vi.view all customers(if u decide to model the customer) vii. create invoice viii. save invoice ix.print receipt x.refund customer his money xi.etc, Analyse your use case very well so that u will discover some other requirements that the software will satisfy. Design and implementation overview From the use case, you will discover Classes with various methods and attributes, find a way to collaborate the various objects to achieve the various use cases specified.Confine each object to its particular duty example your InvoiceLineItem will have to calculate the price of each line in the invoice, while the invoice class which have a collection of InvoiceLineItem will take care of calculating the total price of all items, adding and removing item in the invoice etc. Your payment object will have to take care of all payments and report back to tell the invoice Object if the customer has paid or not.before an invoice adds an item it has to confirm from the data store if the specified item and amount of quantity requested exist in the database, the invoice supplies the receipt object with information it will use to do the print receipt method, the invoice will have a save method that will use to call the data store object to update the records in the database to reflect the completed transaction, the data store does all talking with the database and gives out public interfaces to client objects like invoice and sales object. When designing, find ways of implementing polymorphism so that u can easily change your code codes if u want improvement in the future the interface should be fairly simple with labels, text fields, combo box,Table,buttons Forms,dialogs to display errors etc,add button, remove button, commit transaction button,print receipt,Refund form with text fields and buttons etc create a database of tables like Stocks,Sales,refunds finally test your codes to make sure it perfectly satisfy your use case requirements. |
Re: Sales And Invoicing Application by Chimanet(m): 8:47pm On Nov 30, 2011 |
Do u know OOP well ? if so u wont have a problem, think of the invoicing system as consisting of objects such as stocks, invoice, InvoiceLineitem, Sales, Customer etc. You will need a data store (example a database to help u persist ur domain objects, access will be OK), then with a good business logic and nice interface u will be done i no time, just java or Csharp will be better if u intend to develop for windows OK start like this: Use case Overview 1. what are your use cases ? what do u want the user to do with the app? i. add item to stock ii. view items in stock iii.update item in stock iv. add a new customer(if u decide to model the customer may be u want to keep track of your customers like opening a ledger for each customer it depends on the kind of business) v.view daily sales vi.view all customers(if u decide to model the customer) vii. create invoice viii. save invoice ix.print receipt x.refund customer his money xi.etc, |
Re: Sales And Invoicing Application by Nobody: 11:54pm On Nov 30, 2011 |
^^^Are spam bots disturbing your forum? |
(1) (Reply)
My Personal Performance Test On PHP7 VS Facebook HHVM & New Features / Creating An Android Book Bank / Web Developer Need That A Create A Site Like This.
(Go Up)
Sections: politics (1) business autos (1) jobs (1) career education (1) romance computers phones travel sports fashion health religion celebs tv-movies music-radio literature webmasters programming techmarket Links: (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) Nairaland - Copyright © 2005 - 2024 Oluwaseun Osewa. All rights reserved. See How To Advertise. 35 |