‎2008 May 30 1:20 PM
HI ,
When a program can be say as a good program?
When it is executing fine or when it satisfies the user requirement or execting fastly ?
Thanks,
Agalya
‎2008 May 30 1:37 PM
Hi,
Which report have good optimization in the execution time as well as statisfies the user requirement then we can call it as good program. If not we can make it as good program:)
Regards,
Kumar.
‎2008 May 30 1:37 PM
Hi,
Which report have good optimization in the execution time as well as statisfies the user requirement then we can call it as good program. If not we can make it as good program:)
Regards,
Kumar.
‎2008 May 30 1:43 PM
- it does what it's supposed to do
- it has an almost linear runtime even when facing a growing database
- it uses database and memory resources efficiently
- it is clearly structured and has no redundant coding
- it does not use any global variables (except maybe in the main program)
- it is well-commented and easy to understand and maintain, also for the non-author
- it has a well-written documentation
wait...that's my programs!
‎2008 May 30 1:44 PM
a program which does not a least something which is useful (usually for the user, sometimes for the programmer) is a no-sense program.
a program which does something but incorrectly is a bad and maybe dangerous program
a program which does something useful without major bugs, but very slowly is an annoying program
only a program which fulfills all three is a good program
‎2008 May 30 3:50 PM
As far as user requirements are fulfilled(ofcourse which inclues fast execution too.User may not satisfy a program if it takes longer time than usual. Ultimately he should be happy.That is the aim.) and maintenance is easy for the program then it is good program.
reward points if helpful
RamaKrishna C
‎2008 Jun 02 6:22 AM
Hello Agalya,
There are different views of being a good program:
From the "Manager"-perspective a good program has to adhere the given requirements and the performance has to look acceptable - at least on the development machine.
From the Developers standpoint all criteria Thomas Zloch mentioned are to consider. My personal emphasis is focused on the proper use of events (ABAP is an event driven language) like INITIALIZATION, AT SELECTION-SCREEN , well structured Subroutines etc. and to comply with naming conventions.
There are no fixed rules. Every developer is his own artist.
And: you have to have luck when your manager evaluates your work!
Have fun with your art,
Heinz
‎2008 Jun 02 7:08 AM
Hi!!
First point to judge any code/program is user's point of view.
If user's requirement are meant and he is satisfied then everything is fine.
Others factors like time taken etc also matters but they are secondary things.
kindly reward points if helpful.