solution architecture template gate 1 - mita home€¦ · web viewshared service providing access...

Insert project nameSolution Architecture Template – Basic Solution Profile

■Gate 1

Date: Insert publish date of this documentVersion: 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 1 Solution Architecture Submission for Insert project name

01. Submission Details

Project

Name Insert

Target Completion Date Insert

Submission

Name and Surname Insert

Ministry / Department / Organisation Insert

Title (CTO / CIO / Officer / IMU / Supplier) Insert

Email Insert

Telephone Insert

Supplier


Organisation Insert

Email Insert

Telephone Insert

Client


Ministry / Department / Organisation Insert

Email Insert

Telephone Insert

02. Basic Solution Profile 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: 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.

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 [email protected] for clarification.

Solution Architecture Document Template Version: 7.0 Select a classification for this document from confidential, restricted, unclassified, public

Malta Information Technology Agency - Technology and Systems GovernanceTelephone: (+356) 21234710 Fax: (+356) 21234701

Website: www.mita.gov.mt

http://www.mita.gov.mt/

mailto:[email protected]


Maintain a summary of changes in the table below.

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

03. Basic Solution Profile

The Basic Solution Profile Section has been designed to capture only the most essential information required for the Initial Project Approval.

03.1 High Level Business Scope of Solution

Business Context Checklist






3.1.1 Business Description: Insert

Provide basic information on the purpose of the solution and what business areas the solution must cover. Clearly highlighting benefits, assumptions, dependencies, risks.

3.1.2 EU Initiative/Obligations: Is the creation of the solution mandated by EU laws/directives/initiatives?

Yes/Noo Which EU laws/directives/initiatives mandate the creation of the solution?

Insert/NA

3.1.3 Mission Criticality (in the context of Government’s business): Is the creation of the solution mandated by local laws/directives?

Yes/Noo Which local laws/directives mandate the creation of the solution?






Insert / NA

What are the repercussions of not implementing the solution?InsertExample: Penalties, disruption to Government’s ICT/Business strategy. Clearly provide the necessary documentation to substantiate your case.

By when does the solution need to be live / available for use?Insert

o Provide reason why the solution is required to be live / available for use by this date:Insert

3.1.4 Monetary Value/Budget Allocated:NOTE: If breakdown of the below values is available, kindly attach with the submission.

Capital Expenditure (CAPEX):InsertSuch as: procurement, deployment, etc.

Operational Expenditure (OPEX):InsertSuch as: maintenance and support, recurring license costs, etc.

o Specify the number of years on which OPEX was calculated:Insert

Kindly also highlight the budget sources funding the solution:InsertN.B. Budget sources can also be referred to a pre-defined contract. In this case kindly highlight the number of hours being utilised.

3.1.5 Solution Scope: International:

Yes/No/NAInter-governmental: Solution which will be shared or is common amongst governments; implemented across EU member states.

Government Wide:Yes/No/NAInterdepartmental: Solution which will be shared or is common amongst local Government departments.

Local:Yes/No/NADepartmental: Solution which will be only used by the specific Government department.

3.1.6 Solution Delivery: Solution is to be delivered all at once:

Yes/No

Solution is to be delivered over time:Solution Architecture Document Template Version: 7.0

Select a classification for this document from confidential, restricted, unclassified, publicMalta Information Technology Agency - Technology and Systems Governance

Telephone: (+356) 21234710 Fax: (+356) 21234701Website: www.mita.gov.mt



Yes/No

3.1.7 Solution Major Milestones: Specify the solution major milestones together with their respective target delivery

date within the table below:A detailed project plan can be submitted instead of the details below.

Major Milestone Delivery Date

Insert Insert






03.2 Basic Solution 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.

Conceptual Solution Checklist - Select all that apply

3.2.1 Project Type: New Solution:

Yes/No

Upgrade Solution:Yes/No

Solution Migration:Yes/NoEither migration of solution from one hosting environment to another OR migration of server from one data centre to another.

3.2.2 Solution Interactions: Government to Citizen (G2C):

Yes/NoServices offered to the public.

Government to Business (G2B):Yes/NoServices offered to the third party organizations which are not controlled by the Government.

Government to Government (G2G):Yes/NoServices intended to be used by ministries, Government departments and/or entities.

Government to Other Government (G2OG):Yes/NoServices that will be used by other Governments, such as other EU member states.







3.2.3 Business Domain Information Classification: What is the classification of the information which will be retained by the solution:

The solution can have more than one applicable classification.

Confidential – Significant impact if information is disclosed to unauthorised recipients.In this regard the following is recommended:

• Data should be encrypted at rest,• All point-to-point communication channels should be encrypted,• 2-factor Authentication should be used,• Should not be published publicly over the internet,• Preferably hosted on infrastructures which are governed by ISO 27001 (or similar)

certifications

Restricted – Undesirable consequences if information is disclosed to unauthorized recipientsIn this regard the following is recommended:

• If data is stored on shared tenancy storage then it should be encrypted at rest,• Outside MAGNET communication should be encrypted.

Unclassified – Negligible impact if information is disclosed to unauthorised recipients.

Public – This information is available to the general public.

Security Classification Select Indicate which information is classified under the respective category including the respective key business scenarios

Yes / No Insert

Confidential

Restricted

Unclassified

Public

Is the solution going to process / store personal information?Example: use of credit card details during a payment process, processing/storing of health related information, etc.Yes / No

3.2.4 ICT Policies/Directives: Highlight any deviations (providing detailed description) to the Policies/Directives

found in the following URL: http://ictpolicies.gov.mt/ Insert / NA

Such as: GMICT X 0071:2010 Adopted Specifications, CIMU S0051 Website Standard, CIMU P 0012:2003 Third party Web hosting services Policy.





http://ictpolicies.gov.mt/



3.2.5 Estimated Total Number of Consumers that will be using the solution:

Total number of consumers:

By Audience:Total Number

Citizen

Government Employees

Businesses (Private Sector)

Specify who/which are the other consumers (if any)

NOTE: For solutions were functionality will be delivered overtime specify amounts by implementation phase.

3.2.6 Estimated Total Number of Concurrent Consumers that will be making use of the solution: Total number of concurrent consumers:

By Audience:Total Number

Citizen



Other: Specify who/which are the other consumers

NOTE: For solutions were functionality will be delivered over time specify amounts by implementation phase.

3.2.7 Estimated Annual Consumer Growth Rate: Percentage consumer growth rate:

By Audience:

Percentage

Citizen



Other: Specify who/which are the other consumers

NOTE: For modular delivery specify amounts by implementation phase.







3.2.8 Solution Availability: Specify the required uptime for the solution:

Availability % Unscheduled Downtime (Over a non–leap Year) Yes / No

99% (Two Nines) 3.65 Days

99.9% (Three Nines) 8.76 Hours

99.99% (Four Nines) 52.56 Minutes

99.999% (Five Nines) 5.26 Minutes

Specify other (if any) Specify other (if any)

NOTES:- The specified downtime is the exact yearly period whereby the solution is allowed to be

unavailable based on the respective availability percentage.- Any solution being hosted within Government’s data centres requiring an availability of 99.9%

or more per annum should be implemented in a redundant fashion across both data centres. - Please indicate how the SLA shall be monitored.

You may make use of the following Service Availability Calculator for a quick calculation in terms of un-scheduled downtime and guaranteed uptime. In addition, this tool features actual availability representation when introducing scheduled downtime.

Recovery Time Objectives (RTO): What is the maximum acceptable length of time from the occurrence of a downtime, that may elapse before the lack of business functionality severely impacts its beneficiary/beneficiaries:Insert Time

MTBF (Mean Time Between Failure): What is the minimum acceptable length of time between two consecutive failures, that is acceptable to the business?Insert Time

IMPORTANT: When compiling the Service Level Agreement (SLA) for solutions, It is recommended that the above values are clearly identified, i.e.: (a) Availability, (b) Recovery time objectives and (c) MTBF. By having these specified and articulated in the service contract, the business owner may ensure minimal impact from possible failures.

For example: 99% availability with a maximum RTO of five hours and having an MTBF of 2 days.

What are the repercussions if the solution fails?InsertFor example the above must gauge whether the solution has financial, health, political, etc. repercussions.

Highlight any peaks and troughs of the service being rendered?Insert







3.2.9 Production Hours of Operation:

Audience24 X 7

Normal Business Hours(e.g. 8:00 to 17:00)

Extended Business Hours

Yes / No Yes / No Specify the hours / N/A

Citizen



Specify other (if any)

3.2.10 Solution Delivery Model/Business Model: Traditional:

Yes/No

As a Service:Subscription based.Yes/No

NOTE: Prior to considering cloud based offerings it is appropriate that the following considerations are evaluated: Please refer to Cloud Considerations check list: https://mita.gov.mt/en/Technology/EnterpriseArchitecture/Documents/ArchivedTemplates/TSG-REP-Cloud-Common-Assessment-and-Considerations-v2 0.pdf





https://mita.gov.mt/en/Technology/EnterpriseArchitecture/Documents/ArchivedTemplates/TSG-REP-Cloud-Common-Assessment-and-Considerations-v2%200.pdf

https://mita.gov.mt/en/Technology/EnterpriseArchitecture/Documents/ArchivedTemplates/TSG-REP-Cloud-Common-Assessment-and-Considerations-v2%200.pdf



3.2.11 Target Hosting Environment: Shared eGovernment Web Hosting Environment managed and supported by MITA:

Yes/NoThis applies for existing solutions only i.e. solution updates/upgrades.

Segregated Environment at the Government Data Centres managed by MITA:Yes/NoThis applies for existing solutions only i.e. solution updates/upgrades.Service Hosting Catalogue TYPE 2 - refer to service hosting catalogue: https://mita.gov.mt/en/Technology/EnterpriseArchitecture/Documents/IMS-GDL-ServiceHostingCatalogue-v3.pdf

Segregated Environment at the Government Data Centres managed by 3rd parties:Yes/No

o Computing resources provided by MITA: Yes/NoService Hosting Catalogue TYPE 1B - refer to service hosting catalogue: https://mita.gov.mt/en/Technology/EnterpriseArchitecture/Documents/IMS-GDL-ServiceHostingCatalogue-v3.pdf

o Computing resources not provided by MITA: Yes/NoService Hosting Catalogue TYPE 1A - refer to service hosting catalogue: https://mita.gov.mt/en/Technology/EnterpriseArchitecture/Documents/IMS-GDL-ServiceHostingCatalogue-v3.pdf

o 3rd Party Supplier Organization: InsertNOTE: This is subject to approval i.e. involving business negotiations and appropriate discussions with the respective stakeholders.

Hosting managed and supported at 3rd parties:Yes/No

Shared: Yes/No Dedicated: Yes/No The organization providing:

o Hosting: Inserto Management and support: Insert

The country:o Where the data shall be residing: Inserto From where the service shall be rendered: Insert

NOTE: All options above are governed by OPM Circular No 29/2005 - 23 June 2005 - Reviewing the ICT Operations of Government.NOTE: If more than one hosting mode is selected please supply more information about the role of each hosting layer.





https://mita.gov.mt/en/Technology/EnterpriseArchitecture/Documents/IMS-GDL-ServiceHostingCatalogue-v3.pdf








3.2.12 Solution Usage of Government Shared Services: myBills:

Yes/NoShared Service handling online government payments.

myForms:Yes/NoShared Service for creating electronic forms and the respective workflows for the delivery of citizen centric eServices.

mGov:Yes/NoShared alerting services used to deliver Short Message Services (SMS) and email notifications.

eID:Yes/NoA shared service which allows citizens and businesses to identify themselves via the government’s Web portal or telephone contact centre to securely access any number of available e-Services, regardless of which organization provides the service.

CDR:Yes/NoShared Service providing access to Corporate Data.

Corporate Identity:Yes/NoA Shared Service for the provision of Identity to the Public Administration.

Additional information can be found on: https://mita.gov.mt/en/eGov/Pages/eGovernment.aspx

Kindly highlight any usage peaks of the service/s being consumed.

3.2.13 Solution Usage of External Services: Identify and specify any interactions required with external services:

Service Name Service Provider

Insert Insert

NOTE: For Gate 2 approval the respective service contract that includes the respective service consumption mechanism must be included. (Service Contract Template Appendix A).





https://mita.gov.mt/en/eGov/Pages/eGovernment.aspx



3.2.14 Shareable characteristics of the Solution: Is the solution going to share resources (data, processes, etc.) with other external

services/solutions?Yes/No

o What resources will be shareable?Insert

o Which external services/solutions are going or already make use of these sharable resources (if already known)?

Service Name Service Provider

Insert / NA Insert / NA

o How do you plan to share these resources (if already known)?Insert / NA

Principles:- Any shareable resources should be exposed through appropriate machine readable

mechanisms in an industry standard fashion, using open standards and interoperable engineering principle/practices.

- Specifically in the context of domain data, ownership is considered to rest within the respective legally empowered authority/authorities, unless explicitly otherwise indicated. As a matter of preference, any machine to machine (solution to solution) interaction between data consumers and providers must happen directly between the consumer and the specific information system storing and processing such domain data






03.3 Functional Solution Description

Provide a diagram (or diagrams) with corresponding narrative that depicts the functional aspects of the solution. Corresponding narrative that describes each major functional area of the application must also be supplied. Describe how the solution will be used and operated. Describe both the type of users of the solution as well as any business interfaces that may be necessary.

Note: The diagram below has been provided for illustrative purposes only. PSOs should delete the diagram provided and supply information specific to the solution requesting approval.

Note: Narrative describing the functional design of the solution must be provided immediately following the diagram(s).






03.4 Conceptual Solution Design Description

Provide a diagram (or diagrams) with corresponding narrative that depicts an accurate description of the conceptual design for the entire solution. The design must document how each of the requirements specified in the functional design will be conceptually accomplished. The conceptual design must align with the Principles, Practices, and Standards that are published in the http://ictpolicies.gov.mt and https://mita.gov.mt/en/eGov/Pages/eGovernment.aspx portals respectively.

Note: The diagram below has been provided for illustrative purposes only. PSOs should delete the diagram provided and supply information specific to the solution requesting approval.

Note: Narrative describing the conceptual design of the solution must be provided immediately following the diagram(s).





https://mita.gov.mt/en/eGov/Pages/eGovernment.aspx

http://ictpolicies.gov.mt/