ABOUT US
BACKGROUND-
CZAR TECHNOLOGIES pioneer in the field of customized software development, having our office at Guwahati and very well laid dealer network over Northeastern Region backed by highly skilled software personals. CZAR TECHNOLOGIES is not only known by best quality software product but also by its prompt service at all times. Our 3D approach (Disciplined, Dedication and Devotion) towards work has not only gives us landmark of success but also great satisfaction.
OBJECTIVES
To became leader in the field of Customized Software development through constant research and innovative ideas for various application and end user. We always keep ourselves on the forefront to achieve anything that is new and can add a new dimension, which makes us stand apart from our competitors.
OUR MISSION STATEMENT
Develop easy to use tools to make your job easier, cost effective utility software solutions for everyone. Information technologies have changed the way and every organization is in need of various kind of information and maintain database of activities. We want to provide the necessary solution to those organizations by our IT skills and make management Information system.
SERVICE
CZAR TECHNOLOGIES is specialized in developing complete end-to-end software solution. We offer following services,
o In-house.
o Hospital Management.
o School management.
o Online trading for stock exchange.
o Production base industries.
o Sales.
o Real Estate Management.
o Laboratory Management.
o Inventory and Accounts.
o Quality Control.
o Web Hosting.
o Internet/Intranet Application.
o E-commerce solution etc…
SOME OF OUR PRECIOUS CLIENTS
o Magadh Stock Exchange Association, Patna
o Guahati Stock Exchange Limited, Guwahati
o Meghamallar Estates And Services Private Ltd, Guwahati
o Madhabi Biscuits Pvt. Ltd, Tezpur
o Mother Industries, Tezpur
o Gattani Biscuit Industries, Jorhat
o Lakhimpur Food Processors Pvt. Ltd, North Lakhimpur
o National Insurance Employees’ Co-operative Thrift and Credit society Ltd, Guwahati
o Wintrobe Hospital, Umbari Guwahati
o Saraf Project Pvt Ltd, Guwahati
o Advent Industries Limited, Guwahati
o Hotel Annupam, North Lakhimpur
o Kaybee’s, Tezpur
o National Educational Research & Development Program, Itanagar
o Lakhimpur Krishi Udyog Pvt. Ltd., North Lakhimpur
Software Development Skill Set
o Programming Language
o SQL
o Java Script, VB Script, JS Script
o HTML, DHTML
o ASP
o JSP & Java Servlet
o PHP
o UNIX Shell Programming
o Borland C++
Technologies
o .Net
o Win32 API
o ActiveX, OLE
o ODBC, DAO, ADODC, OLE DB
o TCP/IP, Sockets
Database / RDBMS
o MS SQL Server
o ORACLE (PL/SQL)
o Microsoft Access
o MySql
Operating System / Platform
o MS Windows NT / 95 / 98 / 2000 / XP
o Linux
Our Strength and man power
[login to view URL]: Mr. Gautam Ojah
Qualification: BE Computer Science Engineering
Field of expertise: Coding Logic, System Design, Case study
[login to view URL]: Mr. Bikram Pradhan
Qualification: BE Instrumentation Engineering
Field of expertise: System Study, Project Design, Case study
[login to view URL]: Mr. Abhilash Barooah
Qualification: BE Civil Engineering
Field of expertise: Data Base design, Module integration
4. Name: Mr. Pranjal Gohain
Qualification: BE Electrical Engineering
Field of expertise: Output Testing, Error reporting
[login to view URL]: Mr. Mrinal Ranjan Das
Qualification: BE Civil Engineering
Field of expertise: Quality Optimization, Technical writing
[login to view URL]: Mr. Parimal Kalita
Qualification: [login to view URL]
Field of expertise: Accounting module design, Account output testing
Our Work Methodology
Introduction
A methodology defines the work practices in software projects - including how to set technical and organizational direction, achieve project milestones and distribute workloads among the developers. The goal of this technology selection is to choose which software development methodology to use within this organization.
What do we really want?
There are four important goals that the chosen methodology needs to help us achieve:
o Responsive to rapidly changing customer demands - Customers are no longer prepared to wait more that a year for a particular piece of software functionality to arrive (anything that takes that long will probably be out of date by the time it arrives). Software teams need to be able to respond to new requirements with updated software in a couple of weeks/months.
o High productivity – it is a highly competitive marketplace, and the software engineering team needs to produce as much software as possible. All activities of developers must directly lead to innovative software creation.
o Quality driven – Comprehensive testing strategies are needed, at unit, integration and system test levels, so that what is delivered works first time for the customer.
o Interesting for developers – As the recent recession fades and skilled developers are again in high demand, it is critical that the organization evolves policies to keep talented staff. Developers like interesting software engineering and do not like bureaucracy, so the more time that developers can devote to the former and the less to the latter, the better.
What do we already have?
The software engineering team currently has no official documented software engineering methodology. It can be considered to use an “ad-hoc” methodology with some requirements, architecture, coding, manual testing and documentation. There is no consistency in artifacts produced and work practices among the different projects.
Positives that we wish to keep include:
o Close customer contact – developers interact directly with customers, so they build up a good understanding of the customers’ domain and the issues that are important to the customer
o Flexibility to customers’ changing requirements – customers needs are fast changing and developers strive to absorb the new/altered requirements as they become available
o Dedication to quality – the development team goes to great length to provide a quality product and, though their testing strategy needs to change from manual to automate, this quality focus needs to be maintained.
Specific problem areas include:
o Scheduling not hit often – the target dates for project milestones are not been consistently met.
o Issues with quality assurance (QA) – there are no automated unit testing/acceptance testing and sometimes bugs slip through, and manual QA is taking too long
o No/little documentation – As developers move from project to project, it is clear new developers on a project are taking too long to “get up to speed” (part of this is the widely different technologies used on each project – which is not relevant to the methodology used, but part is to do with how the methodology is set up for new project team members)
o Reluctance to change things, in case “we break anything” – on the larger projects, there is a general reluctance to make large architectural changes, for fear of how the existing code base will be affected (this is directly linked to the lack of automated testing)
What are our realistic options?
The five principal software development methodologies available to us are: “ad-hoc”, waterfall, eXtreme Programming (XP), Agile Process and Rational Unified Process (RUP). [Note that we use the generic term [Agile Process] to identify the substantially similar ideas covered in Crystal, Lean, APM, AM, SCRUM, etc.)]
We define ad-hoc as the mixture of a bit of everything, with concepts taken from many different methodologies. It is the basis of software engineering in a surprisingly large number of existing software organizations. It does deliver software, but at a higher cost, longer timescales and the resulting software is fragile when subject to changes. It also involved much more complex project management, as there is no documented set of steps to guide the project as it evolves. Using adhoc techniques is not advisable. The Waterfall methodology consists of rigid sequential steps, involving requirements, analysis, design, coding, integration and testing. Waterfall was popular in the 1980s and early 1990s but has fallen out of favour now. It is not responsive to rapidly changing customer demand. It has a late breakage problem - when the various components are integrated together near the end of the project, serious problems are only then discovered (much too late). It lacks ongoing customer involvement they participate at the beginning of the project (requirements) and near the end (acceptance testing) but have no role in the middle often leading to significant work being completed that customers dont actually want. Using the waterfall model is not advisable. XP, Agile Process and RUP are all part of a continuum of modern methodologies that encourage iterative delivery of value to customers, capturing most requirements as use cases/user stories and advocate a test-driven approach. We will treat them as three separate approaches, but acknowledge they have plenty in common. Each of these is a realistic option and needs to be considered in more depth.
Deciding how to decide
The specific selection criteria are as follows:
o Easy to implement – the chosen methodology should require little training and be clear to all how it works
o Low-cost/low infrastructure – we do not wish to have to deploy expensive tools to provision the methodology
o Productivity-enhancing – the methodology should help developers in their work, not become an obstacle with many formal administrative steps
o Quality enhancing – comprehensive automated testing needed
o Buy-in from developers - the developers themselves must agree it is the best methodology to help them complete software projects
o Practical project management – clear visibility of project status; facilitates transfer of developers between projects (fast ramp-up of developers on new projects)
o Broad industry acceptance – the chosen methodology must have widespread industry acceptance, which will likely lead to an active research community (books, conferences, innovations) and knowledge of the methodology becoming a popular skill among potential recruits
Some of Our Major Projects
1.
Name of the project: Design and development web portal [login to view URL].
Duration: 4 months.
Client name: CZAR TECHNOLOGIES.
Technologies :j2ee, weblogic8.1, Crystal Report8.0
2.
Name of the project: Design and development of application software for online trading system.
Duration: 6 months.
Client name: Guwahati Stock Exchange, Magadh Stock Exchange Association.
Front End Used: Visual Basic 6.0.
Back End Used: SQL Server 7.0.
Other Software Used: Crystal Report 8.0
3.
• Name of the project: Design and development of application software for maintaining Machine Logbook.
Duration: 2 months.
Client name: Lohit Construction.
Front End Used: Visual Basic 6.0.
Back End Used: MS Access.
Other Software Used: Crystal Report 8.0
4.
Name of the project: Design and development of application software for maintaining Inventory, Account & Central Excise.
Duration: 4 months.
Client name: Madhabi Biscuit Pvt. Ltd., Tezpur.
Mother Industries Pvt Ltd, Tezpur.
Gattani Biscuit Industries, Jorhat.
Lakhimpur Food Processors Pvt. Ltd.
Front End Used: Visual Basic 6.0.
Back End Used: MS Access
Other Software Used: Crystal Report 8.0
5.
Name of the project: Design and development of application software for maintaining Inventory and Account system for Departmental Store.
Duration: 2 months.
Client name: K.B. Store, Tezpur.
Front End Used: Visual Basic 6.0.
Back End Used: MS Access XP.
Other Software Used: Crystal Report 8.0
6.
Name of the project: Design and development of application software for maintaining accounts for National Insurance Employees Co-operative Thrift and Credit Society Limited.
Duration: 6 months.
Client name: National Insurance Employees Co-operative Thrift and Credit Society Limited.
Front End Used: Visual Basic 6.0.
Back End Used: MS Access XP.
Other Software Used: Crystal Report 8.0
7.
Name of the project: Design and development of Management Information System for Meghamallar Estates And Services Pvt Ltd for maintaining payment details of customer, project detail, inventory and budgeting.
Duration: 2 months.
Client name: Meghamallar Estates And Services Pvt Ltd
Front End Used: Visual Basic 6.0.
Back End Used: MS Access XP.
Other Software Used: Crystal Report 7.0
8.
Name of the project: Design and development of application software for Barman Diabetes Specialties Pvt Ltd for maintaining patient profile, laboratory test details, billing system and general accounts.
Duration: 2 months.
Client name: Barman Diabetes Specialties Pvt Ltd
Front End Used: Visual Basic 6.0.
Back End Used: SQL Server 7.0.
Other Software Used: Crystal Report 7.0
9.
Name of the project: Design and development of application software for software solution of CDSL (Central Depository Services India Limited) operation.
Duration: 4 months.
Client name: Magadh Stock Exchange Association
Front End Used: Visual Basic 6.0.
Back End Used: SQL Server 7.0.
Other Software Used: Crystal Report 7.0
