The Microsoft .NET platform marks a paradigm shift in the way applications are developed for the Internet. It incorporates open standards that enable businesses to collaborate over the Internet with minimal investment. Hanu Software Solutions Inc. (HSS) is an expert in using .NET to develop solution frameworks and applications.
HSS has established a dedicated Center Of Excellence (COE) that leverages the company’s expertise in the .NET platform for the benefit of its customers. The HSS COE team delivers technical excellence through improved system architectures, applications development capabilities, and reusable enterprise components, and also focuses on building business solutions using existing and emerging .NET technologies and standards.
The .NET Center of Excellence at Hanu Software Solutions
Despite all the attention given to returns on IT investments, little progress has been made in linking all the elements of IT to what a business is trying to do. Managing IT investments, and demonstrating the value of IT to a business, are more challenging than ever, and most businesses seem to be losing ground. Often, management asks CIOs to justify the very IT components that provide value to the business.
This white paper describes strategies that HSS has developed to maximize its efficiency in delivering .NET solutions to our customers.
As a software service organization, whose business itself is IT, HSS has learned how to align its operations on technology-centric Centers Of Excellence (COEs).
What is a COE?
The term Center of Excellence (COE) is a generic phrase used across many types of institutions, mainly in education, research, and healthcare. The IT industry picked up this phrase and started using it to define the collection of tools, resources, and skills used to perform specific development and maintenance tasks by a focused team working at a single location.
Sometimes “COE” became more of a marketing term, with little substance behind it, for IT. This was because IT service organizations happen to be project-centric organizations with defined schedules and objectives, in contrast to other departments that may not have the vision, longevity, and resources to maintain a long-term delivery system focused along a common thread.
Making Business Sense
From the start, HSS has had a strategy of delivering value-added, cost-effective solutions to its customers on a continuous basis. As the company grew, HSS saw the need for a common set of processes and procedures that would allow its developers to create solutions quickly and leverage project knowledge across projects, so that the company can deliver continuously-improving services and solutions. This need also mandated that all specialized tool sets, languages, and the knowledge of how to use them be available to HSS engineers in a structured and defined system, enabling them to develop new solutions flexibly, faster, and at lowered costs. Enter the HSS Center of Excellence.
The Elements of an HSS COE
HSS has established a structure for all of its COEs, consisting of the following key elements:
1. Languages and Technologies
Languages and Technologies
Each COE includes various programming languages, technologies, development libraries, and compilers related to the particular technology domain of that COE. For example, .NET COE uses the following technologies:
· Web Services: SOAP, XML RPC, and WSDL.
· Distributed Technologies: COM/COM+/DCOM/CORBA, RPC, and NET Remoting.
The HSS development tool set is an important element of the company’s unique selling proposition, namely, its ability to deliver solutions for many different life cycles, budgets, and timelines. HSS does not believe in developing a new solution from scratch for each new project. Its tool set includes:
· Engineering tools: GUI controls, reusable components, generic data access layer, SQL data scriptor, SQL schema scriptor, SQL compare, and many more.
· Migration Tools: VB to VB.NET , VB.NET to C Sharp, ASP to ASP.NET, PHP to ASP.NET.
· Process automation tools: defect management, VSS, dashboard, line counting, MS Project.
HSS also employs tools for analysis, utilities, and controls.
Process is important at HSS. The processes that HSS uses are documented and defined in its quality management system (QMS). All HSS development engineers follow these processes. The QMS implements industry best practices and is based on ISO quality standards and on the Software Engineering Institute’s Capability Maturity Model (CMM), and includes:
· Formally documented Project Management processes, including Planning, scheduling, progress monitoring, reporting, communications, issues, delivery management and many more.
· Formally documented Engineering Processes, including configuration management, requirements development, design, construction and unit test (UT), system testing, and user documentation development.
· Comprehensive quantitative process measurements and control, including productivity measurement, schedule variance tracking, defect density reporting, and effort variation tracking.
HSS engineers follow the following best practice during a software project lifecycle to reduce the development schedules as well as the schedule volatility:
Article Source: http://EzineArticles.com/385073