User talk:Mmulawa

The objective of this research is to build a standard structure, which will be appropriate to apply to the real life scenarios, then identify and evaluate set of rules and steps to justify quality of the reusable web UI components. Last step would be separation of rules that will create a standard. The existing component should be checked if it meets the standard requirements and norms. Some of the norms would apply only to the development process of the control. The Standard would consist of different levels of compatibility, so rules should be divided into groups. Each rule should have its own scale and weight of the rule. Not every rule would be of the same importance. List below shows topics that might be a part of the web UI component standard:

1.	Design Time support of major development environments (VS.NET 2002, 2003, 2005, Borland products). 2.	Applied programming best practices and “Design Guidelines for Class Library Developers” (ex. naming consistency, common design patterns). 3.	Technology frameworks widely supported (e.g. .NET Framework version supported 1.*, 2.0.) 4.	NUnit testing performed. 5.	Web standards supported (HTML 4.1, XHTML 1.0.). 6.	Component cooperation with HTML and CSS related to style and layout. Templates supported by the component. 7.	Web cross-browser support based on global research or local research, mobile browser support. 8.	User, developer friendly interface, (checking API and UI usability). 9.	Supported proper component interactions with architecture of the web technology. 10.	Control interaction with data sources. 11.	Performance of controls. 12.	Security (obfuscating assemblies, signing with public key, defence in depth) and licensing issues. 13.	Documentation, samples and technical support provided. 14.	Globalisation and localization support. 15.	Accessibility support based on WCAG - W3C accessibility guidelines.

Not all topics might be included into the standard, because it might be difficult to incorporate some of them into norms and rules.

Defining development standards for reusable user interface (UI) web components.
The objective of this research is to build a standard structure, which will be appropriate to apply to the real life scenarios, then identify and evaluate set of rules and steps to justify quality of the reusable web UI components. Last step would be separation of rules that will create a standard. The existing component should be checked if it meets the standard requirements and norms. Some of the norms would apply only to the development process of the control. The Standard would consist of different levels of compatibility, so rules should be divided into groups. Each rule should have its own scale and weight of the rule. Not every rule would be of the same importance. List below shows topics that might be a part of the web UI component standard:

Not all topics might be included into the standard, because it might be difficult to incorporate some of them into norms and rules.

Test
Test