top of page

Application Development Standards Sample

  • Writer: Angtoni
    Angtoni
  • Oct 8, 2019
  • 3 min read

Web Interface Standards

1. The Provider shall ensure that the System conforms to the Web Interface Standards (WIS).

Web Client Standards

2. Support for Browsers

a) If the System is designed for Intranet use, it shall be accessible using Microsoft Internet Explorer XX and above.

b) If the System is designed for Internet use, it shall be accessible using Microsoft Internet Explorer X.X and above, FireFox X.X and above, Google Chrome X.X and above, Safari X.X and above, and Opera X.X and above.

c) The System shall be accessible using mobile devices.

d) The System should not be optimized for a particular web browser at the expense of the other. The difference in time taken to load the same web page using either of these web browsers should not exceed X seconds.

3. If additional presentation capabilities are needed, the System shall make use of one or more of the following standard plug-ins to deliver the required capability:

a. HTML X or above

b. Adobe Acrobat Reader X or above

If the System requires a plug-in or helper application that is not listed above, such a plug-in or helper application must be supported by the web browsers specified in clause 3.

The use of such a plug-in or helper application shall be subjected to the approval.

4. The technologies used for client-side presentation shall be limited to the following:


a. Hypertext Markup Language (HTML) X.X or Extensible Hypertext Markup Language (XHTML) X.X or above

b. Extensible Markup Language (XML) X.X X Edition or above

c. Javascript Object Notation (JSON) (ECMA-404 and RFC 7159 compliant)

d. Document Object Model (DOM) Level X or above

e. Cascading Style Sheet (CSS) Level X.X or above

f. Javascript X.X (ECMAScript X compliant) or above

g. Jscript

h. Synchronized Multimedia Integration Language (SMIL) X.X or above

If the System is intended for Internet use, it shall adopt a common denominator approach where it uses those features/functions that are supported by both web browsers. Where this is not possible, the application shall detect the browser type prior to generating the client-side presentation.

Where it is totally necessary for the System to use technology for the client-side presentation that is not listed above, such usage shall be subject to approval.



Web Server Standards

5. The Provider shall propose the server platform and add-on server software/engines for the System based on open standards which shall be subjected to approval.

6. The System shall be designed in a way that processing shall be done mainly at the server.

If processing at the client is absolutely required (eg: complex presentation), it shall be kept to a minimum. Such processing shall be subjected to approval.

7. Directory-related data (e.g. user-ids and passwords) shall be stored in a Lightweight Directory Access Protocol (LDAP)-compliant directory or in a manner that allows the data to be migrated to an LDAP-compliant directory without major modification to the Application. Such modification shall be defined as major when the effort required (either represented as man-days or cost) exceeds X% of the total effort required to implement the software aspects of the Application. The design of the directory-related data shall be confirmed before with the development of the System.

8. The technology standards that may be used by the System shall include:


Networking

  • Transport Control Protocol / Internet Protocol (TCP/IP)

Web

  • HTTP X.X

  • Hypertext Transport Protocol (Secure) (HTTPS)

  • File Transfer Protocol (FTP)

  • HTML X.X

  • XHTML X.X

  • DOM Level X or above

  • CSS Level X.X or above

  • XML X.X X Edition or above

  • SMIL X.X  Representational State Transfer (REST)

  • Simple Object Access Protocol (SOAP) X.X or above

  • Web Services Description Language (WSDL) X.X or X.X

  • Universal Description, Discovery and Integration (UDDI) X.X

  • Web Services Initiative (WS-I) Basic Profile X.X


Security

  • Transport Layer Security (TLS) X.X

  • X.509 vX certificate

  • WS-Security X.X Messaging

  • Simple Mail Transport Protocol (SMTP)

  • Secure SMTP

  • Multipurpose Internet Mail Extensions (MIME)

  • Secure / Multipurpose Internet Mail Extensions (S/MIME)


Directory Services

  • LDAP version X

  • Active Directory Service Interface (ADSI) X.X

  • Java Naming and Directory Interface (JNDI) in J2EE X or higher


Database Access

  • Open Database Connectivity (ODBC) X.X

  • Java Database Connectivity (JDBC) X.X or above


Application Integration

  • Java Native Interface (JNI) in J2EE X or higher

  • Java Message Service (JMS) in J2EE X or higher

  • J2EE Connector Architecture (JCA) in J2EE X or higher

9. It shall be assumed that there are firewalls implemented between different machines.

The firewall ports that are required to be opened for the transmission of the protocols required for the System shall be specified. The opening of these firewall ports shall be subjected to approval.

Recent Posts

See All
Tech Specification Sample Part 2

2. System Performance General Requirements 2.1.1 The System shall support online transactions, scheduled batch jobs as well as ad hoc...

 
 
 
Application Design Guidelines Sample

1 Application Design Principles 1.1 Design Application to be Loosely Coupled - The design shall be highly granular and loosely coupled,...

 
 
 

Comments


© 2019 by Angtoni.Ang

bottom of page