Professional Documents
Culture Documents
Nuway Software
Nuway Software
Some of these
What if we could look at the mistakes of the last decade and take a
different path to avoid them?
The NuwayTM
methodology with
proven
success.
This
process
was
by IBM. Because this isn't something we "just made up", our clients can
rest assured their project is in the hands of experts.
Zero Maintenance
Solutions should be self administrating: by the users, for the users. The
developer should be able to easily remove his or herself from the daily
operation of the system with no impact.
Software
Development
Process
(UP)
which
was
proprietarily
Nuway's Process
Nuway Software follows the Unified Software Development Process (UP). We
use UML to diagram and visually represent aspects of the system. Most
clients are unfamiliar with UML and we are very happy to educate them
before initiating the project.
Our proprietary NuDoc documentation technology allows us to communicate
efficiently throughout the project. This format was developed after years
of experience and client feedback. NuDoc eliminates the reading of out dated
on
the
project.
specific
road
map
is
provided
upon
commencement of a project.
Phase 1 Inception
During this phase, a good idea is developed into a vision of the end product
and the business case for the product is presented. Essentially, this phase
answers
the
following
questions:
What is the system primarily going to do for each of its major users?
What
could
an
architecture
for
that
system
look
like?
What is the plan and what will it costs to develop the product?
A simplified document that contains the most critical use cases answers the
first question. At this stage the architecture is tentative. It is typically just an
outline containing the most crucial subsystems. In this phase, the most
important risks are identified and prioritized, the elaboration phase is
planned in detail, and the whole project is roughly estimated.
Phase 2 Elaboration
During the elaboration phase, most of the product's use cases are specified
in detail. Most importantly, the system architecture is designed. The
architecture is expressed as several diagrams of the system, which together
represent the whole system. The analysis of the implementation model
includes components to prove that the architecture is executable. It is
imperative that the construction phase not begin until the architecture is
stable.
Phase 3 Construction
During the construction phase the product is built. During this phase of
development, the bulk of the required resources is expended. The
architecture of the system is stable, however, because the constructors may
discover better ways of structuring the system, they may suggest minor
architectural changes to the architects. At the end of this phase, the product
contains all the use cases that management and the customer agreed to
develop for this release.
Phase 4 Transition
This phase covers the period during which the product moves into beta
release (typically to a soft-release environment). A small number of
experienced users try the product and report defects and deficiencies.
Constructors then correct the reported problems. User documentation and
training are provided during this period.
About Craftsmanship
Nuway is committed to bringing craftsmanship and raising the bar in the
profession. Below we describe how we believe software should be written.
We unashamedly share our opinion of what is wrong within our industry.
However, criticism without care for solutions is of no more benefit than a
clanging gong or a crashing symbol: it's loud and annoying to everyone.
Many clients want to outsource a single project, but take over the support
and future changes when it is completed. In this case the quality of the code
and its ability to be easily understood by new people is of utmost
importance. A vendor who may be the cheapest up front may cost tens or
even hundreds of thousands of dollars later in wasted time and effort as the
receiving team tries to understand the code, or spends time replacing poorly
written parts.
can be done once or require several round trips. The many round trips could
be 50x slower, but it is easier to program. When many shortcuts like this are
taken the software suddenly only runs on high-end hardware, or doesn't
allow remote users to work effectively. Now poor craftsmanship is costing the
client money.
Well crafted code is easy to change and extend, even by someone who didn't
previously work on the system. When all of the classes in the code have
meaningful names and follow proper rules of encapsulation, it's a quick and
pleasurable experience to add additional functionality. If the code resembles
"spaghetti" it will take a long time to make the change and squash all the
resulting bugs. Now poor craftsmanship is costing the client money in
unnecessary effort.
Routine names describe exactly what the routine does, with VerbNoun
naming convention.
2.
Each routine performs one well-defined task. If a routine does only one
thing, it's easy to find a problem or know where to make a change.
3.
Variable names are descriptive of the business value they contain, not
things like: var, val, i, j, etc.
4.
Code Comments
When code isn't clear through self-documenting (see above), Nuway provides
the relevant comments. This is quality, not quantity. We abide by the
following principles when commenting:
1.
2.
3.
4.
5.
Refactoring
Typically your first attempt at something is never your best. A second pass
will typically show better ways of accomplishing the same goal. Rewriting
your code a second time is called refactoring. This isn't something left to the
end "when I have time", it's part of the process. You refactor as you go. The
rules used in refactoring are extensive, but the reason Nuway practices it
are:
1.
2.
3.
4.
1.
2.
team builds the total project, all the individual tests build up into an
extensive arsenal of tests that can very quickly guarantee the entire system
is operating correctly. This is critical to reducing the cost of changes in the
future. Now a change can be made, the automated tests run, and the
integrity of the system verified without copious amounts of manual labour.
Documentation
Following the UP generates a lot of working documentation. All this
documentation is in UML , the industry standard notation. Our documentation
includes:
1.
Use Case diagrams - to show stake holder ownership and system scope
2.
3.
4.
1.
2.
3.
4.
5.
6.
7.
Nuway Guarantee
Our wealth of experience fused with industry standard best practices enables
us to unashamedly guarantee:
You will only need to identify business needs, problems, and pain
points; we take care of the rest
You will know precisely when the project will complete, not a day later
You will know exactly what the project will cost, not a penny more