Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #31205

Software life cycle

Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From Ramine <ramine@1.1>
Newsgroups comp.lang.java.programmer
Subject Software life cycle
Date Tue, 24 Feb 2015 16:08:08 -0800
Organization A noiseless patient Spider
Lines 45
Message-ID <mcip56$mnc$6@dont-email.me> (permalink)
Mime-Version 1.0
Content-Type text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding 7bit
Injection-Date Tue, 24 Feb 2015 21:06:46 +0000 (UTC)
Injection-Info mx02.eternal-september.org; posting-host="d6dfe40a1c4bf4f2f24d15fd0d206698"; logging-data="23276"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1879GDg1s2cPfnACQavDUvE"
User-Agent Mozilla/5.0 (Windows NT 6.0; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
Cancel-Lock sha1:vEIdmPDN6xFAFBJJlrxs1f4YETM=
Xref csiph.com comp.lang.java.programmer:31205

Show key headers only | View raw


Hello...


As you have seen me talking here, i have talked in my previous post
about "software quality and programming", what you have seen me saying
is that we have to take into account many critera in software quality,
such us:

- Reliability
- Efficiency
- Security
- Maintainability
- Identifying critical programming errors
- and portability
- expressivness

But I have forget to talk about the modifiability's criterion ,  because 
modifiability is important also, that means if you do modify a method or 
an object inside the software , this modification must have as a 
"consequence" to create a "localized" modification to the method or to 
the object to easy also maintenance and to improve "maintainability", so 
this is the criterion called modifiability that we must take into 
account and this is the goal that we must attain by using object 
oriented programming etc. Anyway, what's i want to say in this post, is 
that what you have seen me talking about is how to attain a good 
software quality by setting the goals that are to score high on those 
criterions above , but to score high on those criterions above is a 
necessary but not a sufficient condition, because in software lifecycle 
we must also use a methodology like agile methodology that is more 
optimal to be able to deliver a software with minimal "costs", "waste", 
and "time", thus enabling companies to be competitive and achieve gains.



Thank you,
Amine Moulay Ramdane,.








Back to comp.lang.java.programmer | Previous | Next | Find similar | Unroll thread


Thread

Software life cycle Ramine <ramine@1.1> - 2015-02-24 16:08 -0800

csiph-web