Insert project name

Solution Architecture Template – Detailed Solution Design

■Gate 3

Date: Insert publish date of this document

Version: Insert current version number of this document

Security Classification: Select classification for this document from confidential, restricted, unclassified or public

Insert company name / Insert company logo
■Gate 3 / Solution Architecture Submission for Insert project name

01.Detailed Solution Design Change Log

Any moderate or significant changes to the solution design must be resubmitted to TSG for review and approval prior to making any actual implementation change(s). In most cases, the review and approval of any changes would be performed internally within TSG.

Notes:

  1. Use of a word processing automated change tracking feature is required when resubmitting this document in order to simplify the review and approval process. Once a version of the document has been approved, then that version of the document should be saved for archival purposes. Prior to submitting a new version of the document, all prior tracked changes should be accepted. This process for resubmission can then be repeated as many times as necessary until the final approval has been issued.
  2. Failure to resubmit changes for review and approval could result in a recommendation by TSG that the project approval status be reconsidered. If there are any questions as to whether or not a change is substantive enough to warrant review and approval, please send an email on for clarification.
  3. Maintain a summary of changes in the table below.

1.1 Change Log Summary – Description / Version / Date
Insert description of the changes / Insert / Insert

02.Detail Solution Design

The Detail Solution Design Section has been designed to capture only the most essential information required at this point to obtain Detailed Design approval. While the items listed are not intended to be an exhaustive list of the possible technologies that may be utilized in the implementation of a solution, it does reflect some of the more common choices as well as important items that should be considered during the design phase.

02.1Detail Solution Design Checklist

Disclaimer: Any technologies listed below have been provided solely for convenience, the information provided is not intended to be exhaustive nor does it indicate product endorsement by TSG.

Detail Solution Checklist – Select all that apply
2.1.1 / Client Platform Information:
Standard Desktop:
Yes/No
Refer to Desktop Software and Configuration standard - GMICT S 0002:2009; Desktop Hardware standard - GMICT S 0001:2007.
If the platform differs from the standard Government Hardware and Desktop Configuration, then please fill in the below part - Non Standard Desktop.
Non Standard Desktop:
Yes/No
  • Type:
Insert
Such as: PDA, Smartphone etc.
  • OS:
Insert
Such as: Linux, Android, Palm etc.
  • OS Version:
Insert
2.1.2 / Client Application Footprint by Platform:
  • Specify size of application footprint in KB or MB:
Insert
N.B This information will serve as an indication in case the solution needs to be virtualised / streamed.
2.1.3 / Client Connection Speed:
Specify bandwidth in kbps or mbps:
  • Minimum:
Insert
  • Recommended:
Insert
Considerations depend on the client platform type including whether the connection is wired or wireless.
2.1.4 / Client Richness:
  • Browser Based:
Yes/No
  • Rich Internet:
Yes/No
Such as: AJAX, Flash etc.
  • Rich Client:
Yes/No
2.1.5 / Browser Support:
The solution must be compatible and support the Major Internet Web Browsers. Specify the compatible web browsers and their respective versions:
Yes / No / NA / Insert Version
Mozilla Firefox
Internet Explorer
Google Chrome
Opera
Safari
Specify other (if any)
2.1.6 / Application State:
  • Is the solution keeping cookies?
Please refer to Processing of Personal Data Regulation
Yes/No
  • Cookie Name:
Insert
  • Non-Persistent:
Yes/No
  • Persistent:
Yes/No
  • If yes, include expiry date:
Insert
  • First Party Cookies:
Yes/No
  • Third Party Cookies:
Yes/No
  • Provide Description of cookie:
Insert
  • Specify the information that is being kept by the respective cookies:
Insert / NA
  • Are the respective cookies mandatory for solution to operate?
Yes/No
  • Is the solution obtaining consent to place cookies in the user’s browser?
Yes/No
  • Session Ids:
Yes/No
  • State Stored in Hidden Fields:
Yes/No
  • Other:
Specify other
2.1.7 / Web Server Location:
  • Public Facing:
Yes/No
  • Internal Facing:
Yes/No
2.1.8 / Virtualization Technologies:
Yes / No / NA / Insert Vendor
Server Virtualization
Storage Virtualization
Application Virtualization
VDI
Specify other (if any)
2.1.9 / Data Access – Connectivity Methods:
Yes / No
ADO.NET
ODBC
OLE/DB
JDBC
JDO
DB2 Connect
Specify other (if any)
2.1.10 / SQL Languages:
Yes / No
T/SQL
PL/SQL
Specify other (if any)
Use of SQL ANSI 92/99 (and appropriate successors) compliant constructs.
2.1.11 / Stored Procedures Utilization:
Use of stored procedures:
Yes/No
  • Data Access only:
Yes/No
  • Business Rules and Data Access:
Yes/No
Note: The implementation of propriety procedural logic (i.e. vendor specific SQL syntax/feature usage hence non SQL ANSI Compliant) should be strictly avoided unless there is a formally substantiated need to do otherwise. This excludes the specific application of back-office, batch type processes which are isolated to limited instances.
2.1.12 / Licenses:
  • Specify how are the licenses for the operating system and software being procured:
Insert
2.1.13 / Operating System:
Yes / No / Insert Version
Windows
Linux
Unix
Other
Windows
Linux
Unix
Other
Windows
Linux
Unix
Other
2.1.14 / Software:
Yes / No / Insert Edition & Version
Web Server / Apache
Microsoft
Sun
Oracle
Other
Application Server / Microsoft
Sun
Oracle
BEA
IBM
Other
Database Server / Microsoft
Oracle
IBM
Other
2.1.15 / High Availability:
Yes / No
Web Server / Clustered
Load Balanced
Other
Application Server / Raid Supported
SAN Supported
Mirroring Supported
Clustering Supported
Grid/On Demand Supported
Other
Database Server / Raid Supported
SAN Supported
Mirroring Supported
Clustering Supported
Grid/On Demand Supported
Other
2.1.16 / Specifications – Roll Out Configuration:
Insert
Web Server / Number of Servers
CPUs per Server
CPU Type
CPU Speed
Amount of RAM
Application Server / Number of Servers
CPUs per Server
CPU Type
CPU Speed
Amount of RAM
Database Server / Number of Servers
CPUs per Server
CPU Type
CPU Speed
Amount of RAM
2.1.17 / Specifications – Maximum Configuration:
Insert
Web Server / Number of Servers
CPUs per Server
CPU Type
CPU Speed
Amount of RAM
Application Server / Number of Servers
CPUs per Server
CPU Type
CPU Speed
Amount of RAM
Database Server / Number of Servers
CPUs per Server
CPU Type
CPU Speed
Amount of RAM
2.1.18 / Processor Architecture:
Yes / No
Web Server / 32 bit
64 bit
Application Server / 32 bit
64 bit
Database Server / 32 bit
64 bit
2.1.19 / Presentation and Business Rule Languages:
Yes/No
Web Server / HTML
DHTML
XML
XHTML
VB.NET
C#
Flash
Java Applets
Java
JVM: Specify Details
JavaScript
VBScript
C++
Specify other (if any)
Application Server / ASP.NET
VB.NET
C#
Java
JVM: Specify Details
C++
Servlets
Server Side Includes (SSI)
Specify other (if any)
Database Server / VB.NET
C#
Java
JVM: Specify Details
C++
Specify other (if any)

02.2Detail Solution Design Description

Provide a diagram (or diagrams) with corresponding narrative with that depicts an accurate, detailed, and complete description of the detail design for the entire solution. The design must document how each of the requirements specified in the preliminary design will be physically accomplished. The detailed design must align with the Principles, Practices, and Standards that are published in the and portals respectively.

Almost all details should be known at this point in the design process, including specific hardware related information utilized by the hosting service provider. Design objectives such as Reliability, Availability, Scalability, Secureability, Interoperability, and use of Common Infrastructure should be adequately reflected in the physical design. All aspects of the application, network, security, and integration architecture, as well as any other pertinent uses of technology to solve specific business requirements (e.g. document imaging, channel support for the numerous client form factors such as smart phone, PDA etc) should be documented.

02.2.1Detail Solution Design – Infrastructure Architecture

02.2.2Required Computing Resources

Required Computing Resources
2.2.2.1 / Type 1A Hosting – Hardware Provided By Solution Provider – Data Centre Facilities:
Insert
Number of Physical Servers
Rack Space required (in rack Height Units)
Air Flow Direction (e.g. Front-bottom-up, etc)
Total Heat Dissipation (Btu/Hr)
Total Power Consumption (kVA)
Operating Temperature (degrees Celsius)
2.2.2.2 / Type 1B Hosting – Computing Resources Provided by MITA – Virtualised Environment Requirement:
Insert
Number of Guests
CPU (GHZ)
RAM (GB)
Hard disk space (GB)
Number of Network interfaces
Bandwidth needed for each interface (KBps)
Frequency of backups(daily/weekly/monthly)
Can server be shut down during the backup process?
Operating Solution (Windows Linux x64/x86)
Database Management Server (e.g. SQL; Oracle( if any)

02.2.3Network Access Requirement (Type 1A, Type 1B and Type 2 Hosting)

Network Access Requirement
2.2.3.1 / Network Access Requirement (Type 1A, Type 1B and Type 2 Hosting) Table:
Specify the required network accesses.
Note that if the solution is targeted to be hosted on the Segregated Hosting Environment the network accesses illustrated in the table below are open by default. Extra access requirements should be included in the attached spreadsheet (“Network Access Requirements Sheet”).
Access From (Source) / Access To (Destination) / ServicePort
ISA Servers / SHE VLAN / TCP 9010, 9011
Supplier VPN Profile(specify name if already provided) / SHE VLAN / TCP 80, 443, 3389, 22
NOC VLAN / SHE VLAN / ICMP Echo Request
NOC VLAN / SHE VLAN / ICMP Echo Reply
SHE VLAN / DNS Servers
192.168.11.71
192.168.11.72 / TCP/UDP 53
SHE VLAN / Internet / TCP 80,443
SHE VLAN / NTP Servers
192.168.11.71
192.168.11.72 / UDP123
SHE VLAN / Mail Servers
217.30.99.69
217.71.179.68 / TCP 25

02.2.4Detail Solution Design – Application Architecture

Provide a detailed solution design reflecting the Presentation Layer, Business Layer and Data Access Layer.

Sample Diagram

If the solution will make use of mGov the following information must be provided: (a) flow diagram illustrating the registration/de-registration processes, (b) how acknowledgements will be processed

If the solution will make use of CDR, kindly indicate the web methods that will be used

Provide the minimum account privileges required for the solution to successfully operate

02.3Technical Architecture Domains

Please provide any additional significant architectural information (that has not been provided within the previous sections) for this solution. Areas of particular interest include use of new technologies, leveraging existing infrastructure, use of new or emerging technologies, and any deviations from the Agency Architecture Principles, Standards, or Best Practices.

02.3.1Network Domain

Insert architectural information on the network domain

02.3.2Application Domain

Insert architectural information on the application domain

02.3.3Data Domain

Insert architectural information on the data domain

02.3.4Solutions Integration Domain

Insert architectural information on the solution integration domain

02.3.5Groupware Domain

Insert architectural information on the groupware domain

02.3.6Platform Domain

Insert architectural information on the platform domain

02.3.7Enterprise Management Domain

Insert architectural information on the enterprise management domain

02.3.8Security Domain

Insert architectural information on the security domain

Solution Architecture Document / Template Version: 6.0 / Page 1
Select a classification for this document from confidential, restricted, unclassified, public
Malta Information Technology Agency - Technology and Systems Governance
Telephone: (+356) 21234710 Fax: (+356) 21234701
Website: