| |
|
Home » Process » Industry Standard Tools |
|
| |
Overview
During the software development
cycle, productivity and efficiency depends on the tools
and technologies deployed for the purpose. Using industry
standard tools ensures inherent compliance to prevailing
industry wide standards and principles. It also provides
ready access to well-researched and time-tested means
of development.
Eon Technologies identifies and uses appropriate tools
to accelerate the software development life cycle and
produce high quality software solutions. We draw from
the best available tools and combine toolsets and technologies
to generate efficient and cost effective development
environments.
These tools are used to develop solutions tailored for
the client who gets the additional benefits of evolving
technologies, improved productivity and lower project
time. Most of all, these toolsets integrate with one
another such that the entire development life cycle
is covered to provide true Rapid Application Development
capabilities.
Eon Technologies continuously evaluates upcoming tools
and software in addition to extensive research before
identifying the most suitable combination to generate
efficient and cost effective development environments.
Modelling Tools
Modelling tools embody software engineering best practices
and span the entire software development life cycle. These
tools provide a visual blueprint that enables analysts,
designers and developers to create, analyse, design, view,
modify and manipulate various project elements while conducting
proactive feasibility studies and benefits analysis of
the proposed system.
These tools also offer varied levels of granularity to
suit different audiences and project life cycle stages.
They enable bird’s eye views of system requirements
and the linkages shared by them as well as detailed perspectives
on the entire implementation architecture.
They provide a visual interface coupled with innate intelligence
that not only improves the quality of software development
life cycle through integrity checks but also helps project
teams identify upfront the risks, issues and problems
inherent in the given approach.
Different modelling tools are employed to suit specific
purposes such as process modelling, data modelling, business
modelling etc.
Eon Technologies uses the following Industry Standard
Tools for modelling:
Process Tools
Process tools embellish the
generic software development process with definition
and customisation parameters. These packages envelop
the key concepts of widely used software development
processes such as RUP, DSDM etc. Typical process tools
include Profilers, Configuration and Version Control
Tools, Requirement Management Tools, Bug Tracking Tools
and Risk/Issues Management Tools.
Testing & Quality Assurance
Software testing processes
check any given software for usability and functionality
metrics. This involves a thorough understanding of the
entire software development process on the part of the
tester. The testing process involves running an application
under controlled conditions and evaluating the test
results through the verification and validation processes.
Testing levels include unit testing, integration testing
and system testing: these are performed throughout the
development process.
Functional testing makes sure that all required functionality
is present in the application and works as designed.
Load testing tests whether an application can handle
the required transactions and is usually performed by
software.
Quality Assurance (QA) processes at Eon Technologies
cover the entire software development process. The QA
process comprises detailed process documentation and
procedures that is tightly integrated with constant
monitoring and enhancements following preset standards
while summarily dealing with all development problems.
IDEs
An Integrated Development Environment
(IDE) is a set of programs that incorporates a text
editor, a compiler/assembler, a linker, a debugger,
a project manager, and other development tools under
the control of a single main application. The IDE can
automatically run each of these applications as needed
saving the application developer the need to learn different
sets of commands for each of the components needed to
build an application. Typically, an IDE is devoted to
a specific programming language but most IDEs available
in the market provide for inherent support for cross
platform environments, encouraging component/multi-tier
architecture-based application development. IDEs feature
sophisticated visualisation tools and an easy-to-use
interface, and provide a fully integrated environment
to design, build and test enterprise applications.
The central component of most IDEs is the editor and
project manager. A project in a typical IDE is a related
collection of files that contain information needed
to build a complete application. This could include
assembly language source files, header files, object
files, libraries, resource files, and binary data files.
The point of an IDE project is to collect and manage
these files to make it easy to keep track of them. Most
IDEs manage the files specific to a given project by
placing those files in a single subdirectory. Shared
files (such as library and shared object code files)
may appear elsewhere but the files that are only used
for the project generally appear within the project
directory. This makes for easier manipulation of the
project.
|
|
|
|
|
