Business Applications Using OOP

[hud039]

Can anyone give me examples of Business Applications(payroll, inventory, accounts receivables, etc) using OOP??

[NetSpook]

Not a response by way!

I was wondering if it is practical to use OO programming languages for business applications. I would also like to see one.

[Masaaki]

Hi, codeguru.

If you know UML(Unified Modeling Language) very well, this is not diffiuclt to do this.
Basically, you create the bais class to satisfy your working scope.

This time, I just did this at only the school level project, so I can't show this in detail,
and doesn't waste my time

But, for example, if you want to create Account Receveal class, what is its basic class?
Money -> Account -> Account Recevialel and Account Payable ....?
So, how do we put the member value and member function at each class.

UML can save so much time to develope the C++ or Java project.

Good luck.
-Masaaki Onishi-

[NetSpook]

Hello Masaaki,

Basically, the issue here is not on the power of UML to ease in the design of business application. Of course, intensive knowledge on UML makes it easier to design a software under development. A more appropriate question would be: Has there been a business application developed using such implementation languages such as C++, CLOS, Ada ...? Or, is it practical to use such implementation languages to build business applications? The way I see it, FoxPro, MS Access, Dbase, ... and the likes were employed.

Cheers and God Bless!

[StuTheDog]

Yes it is very practical to use OOP for bus apps. Why wouldn't it be? The key to OOD&A and the No. 1 cause for poor design is failure to iterate the abstraction and classification process enough. Most developers, particularly those coming from non-OO languages such as VB tend to rely on "gut feel" when developing a class hierarchy, hence usually end up with a highly procedural object model, etc. which is why many people shy away from it. But elegant OO code can be crafted quite well for virtually any business process if you take the time to properly analyze the problem.

In a human resources app for example, one may choose to create a person class, derive from that to implement a job applicant, once the person is hired they are promoted to employee which also derives from person, or perhaps you might choose to create an abstract employee and derive variants for salaried and hourly. All classes share the same basic behaviour/attributes of a person such as name, address, SSN, age, etc. but a job applicant might have test scores, interview information and the like whereas an employee would have pay and withholding info. Salaried personnel would accumulate vacation and sick pay via a different formula than hourly personnel.

An OO accounting app might have utilize classes that encapsulate business rules, e.g. accounts, account numbers, journals, journal entries, obligations, checks (hmmm, you have paychecks, AP checks, electronic fund transfers, another candidate for derivation!), customers and vendors (really not much different than a person since they all share name, phone, address, etc.) Lot's of opportunity for code re-use and hence, robustness.

Stu

[NetSpook]

Yes, I find it very advantageous to use OOAD w/ UML to develop software systems. In fact, I'm a PRO-OO developer. I was just wondering why there are lots of companies w/ their IT Department not taking advantage of it. Sticking to Clipper, Dbase, COBOL, ... and all those old programming tools. Cost and lack of education on the manager's maybe the reason.

What do others think of this?