Wednesday, February 25, 2015

Digest for comp.programming.threads@googlegroups.com - 25 updates in 2 topics

Ramine <ramine@1.1>: Feb 25 12:16PM -0800

Hello,
 
 
What you have seen me saying in my preivousi posts 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
 
 
And how to attain a "good" software quality is by setting the goals that
are to score high on those criterions above, and to score high on those
criterions above is a necessary but not a sufficient condition, because
in software lifecycle we must also use a project management like agile
project management and 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.
 
Agile Project Management reduces complexity by breaking down the
many-months-long cycle of building requirements for the whole project,
building the entire product and then testing to find hundreds of product
flaws. Instead small, usable segments of the software product are
specified, developed and tested in manageable, two- to four-week cycles.
 
And you have to set the project goals, adapting to changing project
requirements and setting priorities for product features.
 
You have also to prioritize the tasks and removes impediments to
handling tasks.
 
And you have to handle most of the task assignment, daily detail
management, progress reporting and quality control for the product.
 
Agile project management continuously evaluates time and cost as primary
constraints. Rapid feedback, continuous adaptation and QA best practices
are built in to the team's committed schedules, ensuring top-quality
output and proven processes.
 
 
 
 
Thank you,
Amine Moulay Ramdane.
asetofsymbols@gmail.com: Feb 25 12:05PM -0800

U don't know how use Ng...
Too many post, too many main
threads as new arguments
bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

bleachbot <bleachbot@httrack.com>: Feb 25 09:00PM +0100

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com.

No comments: