Developing programs with flowchart

[javapenguin]

---

im just curious, unsa diay nga application imong gi program mr. penguin!??

I'm programming the Back Office of one the Supermart here in Cebu using Java and Linux as OS, composing of purchasing, receiving, stock transfer, sales report, pos, p.o. analysis . . .

[jerx d great]

OT:

@mr. javapenguin,

are u a regular employee on that particular supermart?? and if so, how much is ur salary?? cn i ask u that?

[javapenguin]

I am in a semi project base, I receive monthly salary but overall compensation will depend on the performance of the program, program is still in progress but prototype is almost ready for deployment. Ask me again by the end of this year.

[ComputerTech]

I'm programming the Back Office of one the Supermart here in Cebu using Java and Linux as OS, composing of purchasing, receiving, stock transfer, sales report, pos, p.o. analysis . . .

bro unsay back-end database imo gamit? mysql or sqlserver etc...
ru the only one developing this project or a group

[BadDudes]

hey guys can we just stick to the topic ...
WARNING :
ComputerTech
javapenguin
jerx d great

currently we dont use the traditional flowcharting on our development but it goes thru diff process like ERD / Tech Specification / Code Inspection and user testing ... so basically it all rooted out from flowchart I guess.

[menatsu]

flowchart makes the programming part a whole lot easier if you ask me...

[knight26]

flowchart, DFD and UML is the easiest way in building an enterprise program. mao man gud na ang blueprint sa system. kung sa database modelling, dapat naa say ERD aron dili ka ma confuse sa relationships sa imong mga tables.

[silent-kill]

maybe fragment/part lang sa entire program.. himo-an og flowchart... labi na kon libog libog na hehee..

[cen]

Wala na ko kabantay aning flowchart karon. UML state machine diagram or FSM ra.

[dlanyer77]

flowchart, DFD and UML is the easiest way in building an enterprise program. mao man gud na ang blueprint sa system. kung sa database modelling, dapat naa say ERD aron dili ka ma confuse sa relationships sa imong mga tables.

i agree with your reply bro. you're a pro gyud bro. no offense ha sa matamaan ha but i think kanang mga systems nga walay "flowchart" sure ko wala gyud nay quality. Flowchart is not an old fashioned style but its a must to produced a quality system. ug ga develop kag system nga walay flowchart selfish ka nga developer kay if time comes nga lain na ang mag maintain sa imo system siguro ko nga mamatay ug sinubay ang gasunod. instead nga ma promote ka dili na hino-on kay ikaw raman nakahibalo sa imo gibuhat nga system so programmer ka hangtud ka matigulang then ang worse part pa gyud is that dili sa tanan panahon imo ma remember ang Flow sa System. "Flowchart" is a very important piece of documentation for a quality system gyud. ngilngiga gyud diay ug imagination sa mga developer nga wala mogamit ug flowchart ug magbuhat ug system. ang resulta sige nalang release ug new version kay nayabag na ang system then gamiton dayon ang rason nga maayo man ni pag testing ngano pag deploy nayabag man sir/mam sige lang mag release lang new version nga naa fixed ani and thats bcoz walay klaro ang documentation nga pwede matan-aw.