Essence Engineering

Effective IT Solutions

2020-10-02T14:48:00.002+03:00

Essence Engineering provides technology solutions, services and support for your business. We focus on internet and traditional technology to provide rapid, cost effective solutions for your business needs, applying industry wide standards and best practices.

Essence Engineering is solutions focused company, committed to delivering creative and challenging professional solutions. Our goal is to build positive relationships, add value, and provide highest quality of work to our customers .

Our Mission

Leveraging our people accumulated knowledge, our mission is to meet your business needs at the right cost, at the right time. Our consultants have strong and extensive experience delivering high quality technology solutions to small, medium and large business enterprises.

With a skill-set that can easily tackle requirements of the day, each individual at Essence Engineering believes in contributing to achieve the ultimate goal, which is "Optimum customer satisfaction in software solutions and web development services."

New office in Greece

2008-10-10T14:41:00.007+03:00

We are very glad to opening of our new office in Greece.
The group of skilled experts will render consulting services on area of computer science. The best engineers will provide the solutions of any on-complexit problems.

We shall be glad to cooperate with skilled experts.

Speed, the efficiency, the open approach to clients, always will be our motto.

Development Methodology

2008-10-02T17:08:00.002+03:00

Essence Engineering follows industry-accepted standard procedures and processes to ensure highest quality output for its customers. We step up a 4D's (Discover, Design, Develop and Deliver) Methodology based on widely accepted Software Development Life Cycle (SDLC).

Discover

Business requirements

This description is only intended for business and marketing managers of the customer and does not commit any details of what this system would do. This phase try to understand the customer's business needs to provide them a high-level solution portrayal and helping them understand exactly how this would benefit their business.

Software requirements

This segment illustrates all the functionality of the project that is to be implemented. The Client is the owner of this document which describes what exact functionality system should provide, from an external viewpoint. The software requirement capture phase also deals with the parts of the system that have human users, and would describe the functionality from a user's perspective. The audience of this document is first the software engineers/architects who are responsible for using this as their basis for the design of the system. Secondly, this document is intended to help Quality Assurance personnel to start thinking about how to best prepare their test plans. Third, this document is intended for the technical writers so they can start preparing for writing any user's manuals, administration manuals, online help, and more. Finally, this document is intended for the customer to use as their acceptance test before a system could be put into production.

Design

Use case analysis

This activity is purely from the perspective of software developers who are digging deep into software requirements and understanding them more effectively. The main process contains the selection of the common and representative set of software requirements, building use-cases descriptions for them and then use-case course of events for them. A use case is a general, declarative sentence that describes actions a user of the system might perform. Then, for each of these sentences, a paragraph or so of descriptive text may be added. Use case analysis is a technique for developing system specifications and design by analyzing the system from the user's point of view.

The results of use case analysis are:

· The system requirements will describe the system according to how the user will use the system.
· Customers will easily understand the system requirements document, so they can help review it to find errors.
· Designers will add to the system only what the system needs to satisfy its requirements, so the system will be as simple as possible.

Prototype

This activity is very useful but is not always required. For a GUI based system, this becomes a very effective way of understanding all the user interface behavior. Prototyping is also very beneficial for getting the end-user approval about what the final system would look like. For non-GUI parts of a system, it helps solidify software developers' understanding about how to interact with this external system and all the issues related to it. Prototyping may go in parallel with use case analysis.

System architecture & Application design

After finishing use case analysis and prototyping, the next activity is to do a high level design. This again involves various UML methodology activities including the preparation of high-level object models, sequence diagrams, collaboration diagram, and data models. The end goal is to come up with a software architecture that can break the entire system into well-defined subsystems. All the subsystems, their public interfaces, and any subsystem interactions and dependencies are discussed in detail. This is the guiding light for all further design and development of the product. Architects and senior members of the development team do this activity.

Develop

Subsystem design

Once an architectural design is finalized, work is then distributed to all the different team members who are responsible for making sure their subsystems are well designed internally and implemented with the best programming practices. During this activity, whenever an individual subsystem is implemented, it is also unit-tested to make sure it works well in isolation.
A test plan is prepared in parallel to the subsystem design and implementation and its outcome is a concise document explaining all the different ways in which the system can be tested. The Test Plan document contains all the test cases, which are to be used by the QA team. In addition to a test plan document, the QA team may also prepare test scripts to help automate some or all of the testing.
We also prepare a customer acceptance test plan, which is used to ensure that all features and functionality of the project is being handled. Passing this document is the exit criteria at the end of the project. In addition to communicating clear criteria for project completion, the acceptance test plan provides all critical delivery information to development and QA team for correct and timely implementation and testing.

Subsystem development

Development of subsystems is spread across a number of intermediate milestones. As each milestone is achieved, it demonstrates limited functionality of the system. The purpose of these milestones is to make sure the progress of the project is on-track and the client is able to comment on the content of the work during the project. Integrating the code of all these milestones crafts the whole system.

Unit testing

Each member of the development team is responsible for conducting testing on his/her output. Developers do not release their code until they have tested it thoroughly and are satisfied with its correctness and quality.

Integration testing

This activity is done most by the software developers but the software QA also gets involved in it as a prelude to their eventual alpha testing. The purpose of this testing is to see two or more subsystems working together. As more and more subsystems are implemented and unit-tested, they are also put through integration testing. This is an iterative process and in every iteration it usually contains more and more subsystems until the entire system is completed. Integration testing starts somewhere during the subsystem implementation phase and continue until we reach Alpha phase.

Deliver

Alpha testing

When all the different subsystems of the system are completed, unit-tested, and integration tested, the system is considered complete. This stage is called Alpha and any further testing on it is called Alpha Testing. In Alpha Testing, software QA is in-charge of all testing activity and tries to test this system as if it is being used by the end-users. This testing and bug-fixing is again an iterative process and all the information generated during this phase is controlled by a bug tracking system (BTS). We have a BTS in-house that is very effective in helping manage this very crucial phase of the product life cycle.

Beta testing

Many customers release their system to a limited number of their customers and go through another phase of testing and bug fixing. This phase is called Beta Testing and is very similar to the Alpha Testing except the customers are the actual "testers" of the system. A BTS is again involved in this phase to manage all the information generated.

System Rollout

This is the last stage of the project in which we work with the customer to rollout the system to all users. We hand-off all source code and documentation to customer after which we get customer's acceptance to formally end the project.

Customized Development Services

2008-10-02T16:58:00.003+03:00

The first step toward modernizing business is the automation of the internal business processes. Many processes are highly specialized in nature and therefore require custom application development. Business processes and products are often times proprietary and confidential in nature, which give your business a competitive edge over other players in the market. In such cases, it is vital to design, develop and deploy a custom solution that would enhance your competitive edge instead of adopting commercial software solutions that your competitors also have access to.

Essence Engineering has extensive experience developing and delivering custom application projects on time and within budget. We provide one-stop service for the entire life cycle of a project. We help ensure that your projects are completed on time, within budget, and with highest possible quality.

Outsourced Development

Companies of all sizes thrive when they are filled with entrepreneurial spirit. When you come across software product ideas, you can rely on Essence Engineering expertise and experience in transforming your ideas and concepts into reality. We work collaboratively with your team to accelerate time to market, increase product quality, reduce product development cost and simplify outsourced project management.

We experience spans the design, development, testing, deployment and documentation of new software systems. We also provide ongoing support and maintenance so that you never have to employ or manage any technical resources for your software products.

Consulting Services

2008-10-02T16:55:00.002+03:00

Let's face it -- EJB, J2EE, Servlets/JSPs, and XML & Web Services are challenging to use properly.

Take the Risk Out of J2EE

We have employed a proven methodology to transfer our knowledge and skills to your team. The one thing they have in common: They are all using Enterprise Java and have projects that must not fail.

Our Goal

Our goal is quite simple: To work with your staff -- through consulting that has continuous skills-transfer. The skills-transfer element is critical because it means that your staff can maintain the deployment in the long-run, reducing your need to be dependent on external organizations We build our reputation on satisfied clients who can maintain their own systems due to our consulting and skills-transfer services.

Services Offered

If you happen to be at a turning point in your development cycle, or you're just flat stuck, we help you think outside the box. Here are just some examples of ways we have helped companies in the past:

* Choosing which J2EE technologies to use
* Design and architecture
* Specification reviews
* Prototype development
* Building a complete J2EE System
* Performance optimizations and firefighting
* Re-architecturing problematic systems

Contact Information

2008-10-02T16:46:00.013+03:00

Essence Engineering

Information:
info@es-en.org

Onsite Service Model

2008-10-02T16:00:00.002+03:00

This service model provides the most appropriate resources at customer site. Onsite service model is appropriate for projects that require work to be done completely onsite at the client premises for any reason. We can provide two types of onsite service models as described below.

Onsite Project Development

· Essence Engineering takes ownership of a project to be developed onsite and is responsible for its successful delivery.
· Essence Engineering provides its own project manager, software architect and designers, developers, and QA.
· Essence Engineering project manager reports progress to the client.
· Essence Engineering team closely works with client's staff based on project needs.
· Essence Engineering can do this as a fixed-cost project or on a time-and-material basis.

Onsite Staff Augmentation

· Essence Engineering provides highly specialized resources to become part of client's development team.
· Client is responsible for managing Essence Engineering resources including schedules, deliverables, and milestones.
· Essence Engineering charges the client on a time-and-material basis for as long as the resources are kept by the client.

Benefits of Onsite Service Model

· Ability to screen and pick desired resources.
· Lower risk.

Offshore Service Model

2008-10-02T15:02:00.002+03:00

Offshore service model provides the most cost-effective solution. This model is most suitable for projects that have a somewhat defined requirements and where the dependencies on other projects within the client’s organization are not overwhelming.

How it works

· Essence Engineering assigns a project manager located in the client area.
· Essence Engineering development and QA teams are located in its offshore development center.
· Project manager maintains close contact with the client via phone, NetMeeting, email, and onsite visits.
· Project manager captures requirements, documents and communicates them to the offshore team.
· Project manager provides frequent progress reports and demonstrates intermediate milestones to the client.
· Offshore development and QA team members use VPN for any onsite testing.
· Project manager hands over the project to the client and obtains a sign-off.

Benefits

· Most cost effective for the client
· Most resources at incredibly low offshore rates
· No travel and lodging cost
· No software development & testing infrastructure cost for the client
· No hiring and people management cost for the client
· Client pays only while the project lasts
· Highly scalable in terms of adding development and QA resources quickly.

Requirements

· Must capture and document requirements well upfront
· Should have less dependency on other systems at client site