Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject: Re: python first project
Date: Sat, 11 Jan 2014 12:17:13 -0500
Organization: IISS Elusive Unicorn
References: <ae47738d-b16a-4567-bdd9-07d18db5fc77@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.5335.1389460629.18130.python-list@python.org>
Lines: 58
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:63718

On Fri, 10 Jan 2014 20:18:32 -0800 (PST), ngangsia akumbo
<ngangsia@gmail.com> declaimed the following:

	Taking this as a serious programming assignment...
>
>i am programming a system that will be giving details about finance, purchase(bills pending bills and paid bill), employees record and salary details, warehouse records.
>
	Do you have a requirements or use-case documentation, or even a manual
paper system which you would be "duplicating" on the computer? This
document should provide the information what/how the system should operate
(use-cases will be narratives showing how a user would interact with the
system, with a use-case for each potential operation [add new client, add
billing, correct errors, produce reports]).

	How familiar are you with double-entry bookkeeping (accounts
receivable, etc. -- or is this just client billing application which may or
may not feed into the main company accounting system)? Tax laws? (Or is
"salary details" really just the human resources record of promotions/pay
raises, and NOT actual payroll production).

	Are you familiar with relational database design and normalization?
While an object-relational mapper [ORM] may take out the need to know SQL,
they don't help you design efficient/usable databases. Or is their an
existing system/database you have to interface with.

>That is just all i intend to do this all on one GUI application window and to make it to be able to keep records for all the transaction which has been done inputted.  
>
	You have three separate applications defined: stock/warehouse, human
resource/payroll, and billing/accounting. You probably do not want a single
GUI application for this (the people updating warehouse records should have
no access to employee/salary/payroll, nor to the billing system).

>I am also looking for guides and sources which can help me complete it.
>
	Text books on accounting principles, relational database design
concepts, system analysis (if there are no requirements/use-cases) which
may cross over with Object-Oriented Analysis (Object-Oriented Design would
come in AFTER the system has been analyzed; it is a bit closer to the
programming level than requirements).

>
	<snip intro code>

	So far all you show appears to be a "fill-in the form and print" sort
of application... Pretty much any spreadsheet software supports this level
of functionality.

	There is no persistence between runs (that is, no tracking of
information from one run to another). Your "financial sector" basically
requires the user to already know what their balance is and is just telling
them if it is positive or negative. No ability to save a balance and later
have them add or subtract an amount from it.


-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/