Strategic Board
Design Division
Transition Division
Operations Division
Improvement Division


ITIL-V3 Bookcase
Table of Contents
Close this Page

Change Manager
Project Manager
Development Manager
Deployment Manager
Valdation Manager
Configuration Manager
Knowledge Manager


Transition Division

ITIL : 3.3 Application Development and Customization Manager

Application Development Manager
  01 Business Rules...  
  10 Information Engineering Methodology...  
  11 IEM Data Model...  
  12 IEM Field Dictionary...  
  13 IEM List Options...  
  14 Model Portfolio...  
  15 IE Service...  
  20 IEM Image Library...  
  30 IEM Database...  
  31 IEM Record Views...  
  32 IEM Key Assignments...  
  33 IEM Look Up Value...  
  34 IEM Count Value...  
  40 IEM Functions...  
  41 IEM Web Page Design...  
  42 IEM State Transition...  
  43 IEM Workflow Design...  
  50 IEM Layout...  
  51 IEM Form Design...  
  52 IEM Document Design...  
  53 IEM Report Design...  

Development Manager:
The Project Manager works with a team of developers for a finite number of days - this is not a long lasting relationship.
People from all parts of the world may be employed to develop a component and in most cases, those doing the development will have little idea of the overall application.
A software factory is used to churn out reusable components according to strict architectural guidelines - any component that fails to meet its architectural standards is rejected.
Quality is measured and developers who are good tend to be very-very good and people who do not perform are never used again.

Project Framework:
Conversion projects are best treated as a normal development project where the specification of business requirements is well specified in the form of existing source code.
We are highly skilled in the rapid delivery of demonstrable online services, the critical starting point is the scope of business requirement.
Existing source code has significant benefits in that the pedantic detail of field size and permitted values can be derived by inspection or automation.
A potention problem is that the old system design may unduly influence the user interface.
It is very difficult to design a simple solution and where hundreds of existing user interfaces exist it is too easy to replicate what existed into an overly complex service.

Computing in the cloud:
Our web-based application services have considerable benefits over old windows-based systems that should not be influenced by a conversion project.
Application in the cloud are scalable to any number of users with only modest database administration costs.
Applications are free of any dependent computer of smart phone restrictions - any browser on any computer with any operating system can be used.
Applications may be used by authorized people from any location; in the office, with a client, one the road and from home.
Costs are reduced by eliminating the need to install software on computers, by making certain that all user are always using the very latest version of the application and automating business continuity from multiple remote data centers.

Cost Profile:
It costs more to test a facility than it costs to develop it.
It costs ten times more to maintain a facility than it costs to develop it in the first place.
These cost comparators dictate that (1) defects must be eliminated and (2) facilities must be maintainable (easy to change).
We have very simple targets; zero defect software that is extremely flexible (easy to change).
This can only be achieved with our advanced Fourth Generation architecture that is a trade secret.

Multiple Language Support:
Built into the infrastructure of all our web application services is support for multiple human languages.
Implementation is generally where each authorized user selects the language that they choose to work with and this is stored in their user profile.   When that user signs in, the user interface uses the human language that they have pre-selected.
Many people using different human languages can use the application service at the same time and share data as if they were all using the same human language.   Multiple language support carries no processing overhead as only one language file is loaded to process any one transaction.

Translation:
Data is stored in the database in the language that the data is entered.
Business notes and comments can be translated into another human language in a simply way that may be adequate for internal business use.   Translation is not to legal quality and should not be used in external correspondance that is subject to terms and conditions.
Management information may be generated in different languages from data stored in the database, but that information canot be translated again into another language.   True round-trip translation facilities are not provided.

 
Conversion:
We have had a lot of experience in converting Microsoft Windows-based client-server systems to modern web-based application services.
Where existing Visual Studio, Visual Basic or C++ source code exists with Access, Sequal, ADO or SQL Server; then a good deal of automatic conversion can take place to generate modern web page and MySQL specifications.
Dialogue flow can be hard to visualize from source code, so some test data can have a dramatic impact in bringing the system to life so behaviour can be fully understood.   Where the old and new applications can be demonstrated side-by-side, then the scope of business requirements is well and truely verified.

Skills:
We do not write lines of programming code that could have bugs - all program code is generated using artificial intelligence with zero-defects.
Users experience all web pages as Hypertext Markup Language (HTML) including Cascade Style Sheets (CSS) with optional Javascript in accordance with W3 International standards.
As a policy, no specially installed software is needed on any local computer, so propriatory tools like Adobe Flash and Microsoft Silverlight must be excluded.
Sequal (SQL) is employed for Data Definition Language (DDL) and Data Manipulation Language (DML) services in accordance with International standards for all encrypted database operations.
By avoiding old programming languages like Java, Perl, C+, C#, Python and VB, the defects and vulnerabilities in these languages that are known to hackers are avoided.