Submitted by: Submitted by medi4fun
Views: 209
Words: 580
Pages: 3
Category: Business and Industry
Date Submitted: 05/12/2012 07:28 AM
nuway5/11/12
Nuway Software | About Us
the nuway
the old way
the nuway
s olutions
c as e s tudies
what is a proc es s ?
v ideos
our proc es s
about us
c rafts mans hip
partners
c areers
guarantee
Part 1: The "Old" Way
Nuway's founders have worked in all aspects of software development:
Contractors for professional services companies
In-house development team
Independent consultants evaluating vendors & professional service
companies
We've seen it all, and haven't liked what we've seen. There is something
fundamentally wrong with the current way software is being built:
Pro fessio n al services
In this environment software is written as quickly as possible. Very often
shortcuts with short-term gain and long-term pain and are taken. This creates
a messy, difficult code base on which the solution will rely. Since customers
typically never look under the hood to see the code, they have no idea how
poorly things are running.
Software could be
consistently delivered on
time
Software always meets the
user's needs
Software could be easily
changed and extended, at
any time
Software could be built
faster
We could look at the
mistakes of the last decade
and take a different path to
avoid them
Later, when business needs change, the software changes are extremely
expensive to implement in lieu of the amount of code that must be rewritten.
The suggested solution? A complete rewrite. So who benefits from this short
sightedness?
In -h o u se d evelo p men t
Here, developers typically skip doing proper design and documentation
before coding since there are no sign off points. This makes it virtually
impossible to estimate the amount of work and stick to a schedule. This leads
to cryptic solutions that only the original author understands. In developer
circles this is often seen as job security: "I can't be laid off if no one else can
change my code."
You don't tell the quality of a
mas ter...