You are on page 1of 18

[Project Name] Technical Architecture System Design Template

..............................................doc Page 2 of 18 Template Rev...........................................5 3...............14 5...........................................3 2....................................Technical Architecture Submission for [project name] Table of Contents 1.......................................................................................................................................... DETAIL SYSTEM DESIGN SECTION...............3 1..................................................................................................................................1 SYSTEM DESIGN SECTIONS ....................2 TS OFFERS ASSISTANCE TO DEPARTMENTS ................................................................10 4............................................................................................................1 PRELIMINARY SYSTEM CHECKLIST................................................................................3 3.................................... PRELIMINARY SYSTEM DESIGN SECTION.........................................5 3.................................................................... CONCEPTUAL SYSTEM DESIGN SECTION..................11 4..18 Print Date:9/18/2012 109684635............2 FUNCTIONAL SYSTEM DESCRIPTION................................................................................................................................................11 4...........................2 DETAIL SYSTEM DESIGN DESCRIPTION............................14 5............................................................................................9 3..... SYSTEM DESIGN CHANGE LOG.................................................. Date: 3/07/2007 ...........................................................................................3 1..............13 5................ INTRODUCTION..................................1 CONCEPTUAL SYSTEM CHECKLIST................................................1 DETAIL SYSTEM DESIGN CHECKLIST.......................................3 CONCEPTUAL SYSTEM DESIGN DESCRIPTION .....2 PRELIMINARY SYSTEM DESIGN DESCRIPTION.....

in addition. •Updated Detail System Design Section: An update to the detail design is required to be submitted. reviewed. •Detail System Design Section: This section of the document is required to be submitted. prior to receiving Gate 3 (Implementation) Project Approval. and approved by TS.2 TS Offers Assistance to Departments One of the primary services that TS offers to the Departments is system design review and assistance. this template has been separated into three sections. •Preliminary System Design Section: This section of the document is required to be submitted. Departments requesting Project Approval will be required to complete this template.doc Page 3 of 18 Template Rev. TS 1.Technical Architecture Submission for [project name] 1. To facilitate this process. prior to receiving Gate 2 (Execute and Build) Project Approval.g. this documentation would be submitted as soon as the Detail System Design has been completed. Once this approval has been issued. and approved by TS. However. Involving TS as early as possible in the project (e. the Implementation phase may begin. Normally. section by section. then To Be Determined (TBD) should be specified. •Conceptual System Design Section: This section of the document is required to be submitted. prior to completing Gate 2 (Execute and Build) Project Approval.1 System Design Sections Each section of the template must be completed to the extent possible for the Project Approval Gate being requested. and approved by TSTS. The sections of this template are described below in greater detail. Project Approval Gate Requirement Gate 2 Project Approval Gate 2 Project Approval Prior to completing Gate 2 Gate 3 Project Approval Template Section to be Completed Conceptual System Design Preliminary System Design Detail System Design Updated Detail System Design Table 1: Project Approval Requirements 1. they are summarized in Table 1: Project Approval Requirements. Introduction The System Design Template has been designed to enable Departments to provide an increasing amount of detail to Technology Strategies (TS) over the life of a project. 2. when the next section of the document is completed. reviewed. and approved by TS. prior to receiving Gate 2 (Execute and Build) Project Approval. reviewed. Any changes to the system design based on pilot testing must be incorporated. reviewed. Date: 3/07/2007 . In most cases. during the various phases of a project. It also facilitates Project Approval. the review and approval of any Print Date:9/18/2012 109684635. during RFP creation or system design) is key factor to the overall success of a project. System Design Change Log Any moderate or significant changes to the system design must be resubmitted to TS for review and approval prior to making any actual change(s) to the design. If information is requested in a particular section that cannot be provided at the time of completion. This type of early involvement helps to ensure that the Department is complying with the organizations’ Technical Architecture. then the information that was previously unavailable must be provided.

4. Date: 3/07/2007 .doc Page 4 of 18 Template Rev. Once a version of the document has been approved. This process for resubmission can then be repeated as many times as necessary until the final approval has been issued. Prior to submitting a new version of the document. Failure to resubmit changes for review and approval could result in a recommendation by TS that the project approval status be reconsidered by the State CIO. Maintain a summary of changes in the table below. Use of a word processing automated tracking change feature is required when resubmitting this document to simplify the review and approval process. TS will coordinate providing the information for review and approval to the State CIO. If Approval Review is required. please contact TS staff at (919) 981-5555 for clarification. Change Log Summary – Version and Description (For instructional purposes an example has been provided) Date submitted to TS for review Date approved by TS Print Date:9/18/2012 109684635. all tracked changes should be accepted. If there are any questions as to whether or not a change is substantive enough to warrant review and approval. then that version of the document should be saved for archival purposes. Notes: 1. 2. 3.Technical Architecture Submission for [project name] changes would be performed internally within TS.

Date: 3/07/2007 . 3.0 (Draft): __ Level 1 __ Level 2 __ Level 3 __ Yes __ No Total:__________ By Audience: Citizen: ______ Employee: _____ Business:______ Other:______ Note: For modular delivery specify amounts by implementation phase.0: __ Priority 1 __ Priority 2 __ Priority 3 __ WCAG V2. Conceptual System Design Section The Conceptual System Design Section has been designed to capture only the most essential information required for Initial Project Approval in a quick and concise manner.doc Page 5 of 18 Template Rev.Regulatory or Privacy Requirements W3C Accessibility Compliance Section 508 Accessibility Compliance Estimated Total Number of Customers Print Date:9/18/2012 109684635.Select all that apply __ New System __ Upgrade System __ Other (specify): __ Commercial Off The Shelf (COTS ) __ Government Off The Shelf (GOTS ) __ Custom Note: Customizations to COTS/GOTS solutions must be limited to 10% and be fully supported in future releases or versions __ Modular (functionality delivered over time) __ Monolithic (functionality delivered all at once) __ Government to Citizen (G2C) __ Government to Employee (G2E) __ Government to Business (G2B) __ Government to Government (G2G): __ State __ Local __ Federal __ Yes: __ Credit Card __ ACH __ EFT __ Other (specify): __ No __ Yes __ No __ HIPAA __ FERPA __ Other (specify): __ N/A __ WCAG V1. the information provided is not intended to be exhaustive nor does it indicate product endorsement by TS. Delivery of Functionality System Interactions Electronic Commerce Pilot Prior to Implementation Security .Technical Architecture Submission for [project name] 3. Conceptual System Checklist Project Type Development Approach Responses .1 Conceptual System Checklist Disclaimer: Any technologies listed below have been provided solely for convenience.

50% utilized) Average File Size = 30Kb 90% of transactions occur in ___ seconds or less 95% of transactions occur in ___ seconds or less 99% of transactions occur in ___ seconds or less Platform = Windows 2000 Pro.2Ghz. Date: 3/07/2007 . Platform = Windows 2000 Pro. Estimated Annual Customer Growth Rate Average Transaction Response Time Requirements Print Date:9/18/2012 109684635. PIII 850Mhz. PIII 850Mhz. 512MB RAM Bandwidth = LAN (10Mb. and Average File Size specifications as necessary to accurately reflect the expected or planned environments. PIV 1.doc Page 6 of 18 Template Rev. Percentage: _________ By Audience: Citizen: ______ Employee: _____ Business:______ Other:______ Note: For modular delivery specify amounts by implementation phase.Select all that apply Total: _________ By Audience: Citizen: ______ Employee: _____ Business:______ Other:______ Note: For modular delivery specify amounts by implementation phase. 50% utilized) Average File Size = 30Kb 90% of transactions occur in ___ seconds or less 95% of transactions occur in ___ seconds or less 99% of transactions occur in ___ seconds or less Note: Change Platform. 256MB RAM Bandwidth = DSL/Cable (1Mb. 50% utilized) Average File Size = 30Kb 90% of transactions occur in ___ seconds or less 95% of transactions occur in ___ seconds or less 99% of transactions occur in ___ seconds or less Platform = Windows XP Pro. 256MB RAM Bandwidth = Dial-in (56Kb.Technical Architecture Submission for [project name] Conceptual System Checklist Estimated Total Number of Concurrent Customers Responses . Bandwidth.

8:00 am to 5:00 pm) __ Extended Business Hours (specify): __ 24 X 7 Uptime => Downtime/year (i.999 (5 Nines) => 000d 00h 05m 15s __ Other (specify): Full Backup: __ Real Time __ Daily __ Weekly Incremental Backup: __ Hourly __ Daily __ Weekly Recovery Time Objective: __ Minutes (specify amount):________ __ Hours (specify amount):__________ Recovery Time Objective: __ Hot Site: __ hour(s) or less (specify amount):________ __ Warm Site: __ days(s) or less (specify amount):________ __ Cold Site: __ days(s) or less (specify amount):________ __ NC OITS __ Agency __ Outsource (specify location/vendor): Production Availability Expectations Application Backup Requirements Application Recovery Requirements Disaster Recovery Requirements Hosting Location Print Date:9/18/2012 109684635.Technical Architecture Submission for [project name] Conceptual System Checklist Production Hours of Operation Responses . 8:00 am to 5:00 pm) __ Extended Business Hours (specify): __ 24 X 7 __ Employee __ Normal Business Hours (e. unplanned) __ 99 (2 Nines) => 003d 15h 36m 00s __ 99. Date: 3/07/2007 .doc Page 7 of 18 Template Rev.g. 8:00 am to 5:00 pm) __ Extended Business Hours (specify): __ 24 X 7 __ Government/Business Partner(s) __ Normal Business Hours (e.g.99 (4 Nines) => 000d 00h 52m 33s __ 99.Select all that apply __ Citizen __ Normal Business Hours (e.g.e.9 (3 Nines) => 000d 08h 45m 36s __ 99.

Technical Architecture Submission for [project name] Conceptual System Checklist System Usage of NC Shared Services – NC ITS Service Catalog Responses .Select all that apply __ Enterprise Services __ iWise __ NCID __ NCMail __ Class A LAN __ Project Mgmt __ Common Payment Services __ E-Rate __ Web Services __ Hosting Services __ Mainframe __ Distributed __ Middleware __ Database __ Directory __ Storage __ Programming Tools __ Network Services __ WAN __ Remote Access __Network Security __ Structured Cabling for Voice. and Video __ Telephony Services __ Local Access Line __ Centrex __ Contact Call Center __ Enterprise IP Telephony __ Small Telephone System __ Long Distance Calling Card __ Long Distance Telephone __ Toll-Free Long Distance __ Cellular Telephone __ Pay Telephone __ MAC and Maintenance __ Multimedia and Conferencing __ Video Conferencing __ Web Conferencing __ Streaming Media __ Event Production Print Date:9/18/2012 109684635. Data. Date: 3/07/2007 .doc Page 8 of 18 Template Rev.

Departments should delete the diagram provided and supply information specific to the application requesting approval. Date: 3/07/2007 . Financial M anagem ent A pplication (Functional D esign) E m ployees P urchasing A ccounts A ccounts Fixed Payable R eceivable A ssets Internal A gency Interfaces (e. Note: The diagram below has been provided for illustrative purposes only. Describe how the system will be used and operated.2 Functional System Description Provide a diagram (or diagrams) with corresponding narrative that depicts the functional aspects of the application.g Payroll. Corresponding narrative that describes each major functional area of the application must also be supplied. Print Date:9/18/2012 109684635.doc Page 9 of 18 Template Rev. A nd H R ) E xternal A gency Interfaces (Specify) G eneral L edger B usiness D irect D eposits B illing B ank R econciliation Shipping C itizens R eporting Note: Narrative describing the functional design of the application must be provided immediately following the diagram(s).Technical Architecture Submission for [project name] 3. Describe both the type of users of the system as well as any business interfaces that may be necessary.

Departments should delete the diagram provided and supply information specific to the application requesting approval. Practices. and Standards . Print Date:9/18/2012 109684635. Note: The diagram below has been provided for illustrative purposes only. The conceptual design must align with the Principles. The design must document how each of the requirements specified in the functional design will be conceptually accomplished.Technical Architecture Submission for [project name] 3. Financial M anagem ent A pplication – Conceptual D esign Internet DMZ Internal N etw ork H ardened Internal N etw ork Firewall 1 Firewall 2 Firewall 3 C itizen W eb Server Employee A pplication D atabase Server Server Firew all 3 Single (or R educed) Sign-on Service ED I M essaging M iddlew are E xternal A gency A pplication C redit C ard Processing Service External B usiness Partner Note: Narrative describing the conceptual design of the application must be provided immediately following the diagram(s).3 Conceptual System Design Description Provide a diagram (or diagrams) with corresponding narrative that depicts an accurate description of the conceptual design for the entire application. Date: 3/07/2007 .doc Page 10 of 18 Template Rev.

NET Remoting __ EJB/RMI – IIOP __ Other (specify): __ XML __ Web Services __ Messaging __ EDI __ CORBA __ IIOP __ Adaptors __ Secure FTP __ Other (specify): System Integration Technologies Print Date:9/18/2012 109684635. Date: 3/07/2007 . the information provided is not intended to be exhaustive nor does it indicate product endorsement by TS. SOAP.Technical Architecture Submission for [project name] 4. Preliminary System Design Section The Preliminary System Design Section has been designed to capture only the most essential information required to obtain Preliminary Design approval. WSDL. UDDI) __ Public Facing __ Internal Facing __ Messaging Platform Specific: __ . XML.1 Preliminary System Checklist Disclaimer: Any technologies listed below have been provided solely for convenience. 4. it does reflect some of the more common choices as well as important items that should be considered during the design phase. Preliminary System Checklist Architectural Approach Processing Type Development Platform Architectural Framework(s) Architectural Pattern(s) Application Communication Technologies Responses – Select all that apply __ SOA __ 3/N Tier __ Other (specify): __ OLTP __ OLAP __ Other (specify): __ J2EE __ .NET __ Other (specify): __ STRUTS __ JATO __ JSF Other (specify): __ MVC __ Factory __ Controller __ Data Access Object Other (specify): Service Interface: __ Web Services (HTTP.doc Page 11 of 18 Template Rev. While the items listed are not intended to be an exhaustive list of the possible technologies that may be utilized in the implementation of an application.

0: __ Priority 1 __ Priority 2 __ Priority 3 __ WCAG V2.doc Page 12 of 18 Template Rev.0 (Draft): __ Level 1 __ Level 2 __ Level 3 __ Section 508 User-Participation: __ Beta __ User Acceptance __ Other (specify): __ Identity and Access Management __ Integrated __ Externalizable __ Externalized __ SSL/TLS __ Data Encryption Level Supported: __ Column __ Row __ Table __ Database __ Cookie Encryption __ DES __ 3DES __ AES __ Other (specify): __ Other (specify): Security Technologies Print Date:9/18/2012 109684635. Date: 3/07/2007 .Technical Architecture Submission for [project name] Preliminary System Checklist Software Testing Responses – Select all that apply General: __ Functional __ Regression __ System __ Integration Specialized: __ Performance __ Load __ Stress __ Error Handling __ Security __ Platform __ Accessibility: __ WCAG V1.

Departments should delete the diagram provided and supply information specific to the application requesting approval. At this point. The supporting application should perform at acceptable levels when utilizing lowest common access speeds. details such as scalability. server location where code is deployed). and other network infrastructure. servers. Note: The diagram below has been provided for illustrative purposes only. The design must document how each of the requirements specified in the conceptual design will be logically accomplished. and Standards that are published in the NCSTA . Server Server (Mirror) (Cluster) Remote Access VPN Employees (N=50) WAN Zone 3 Firewall Identity Access Management System EDI Dedicated Circuit VPN Service Broker External Agency Application Common Payment Service (CC and ACH) VPN Field Employees (N=100) External Business Partner Credit Card Authorization Note: Narrative describing the preliminary design of the application must be provided immediately following the diagram(s). version. model. Practices. availability.2 Preliminary System Design Description Provide a diagram (or diagrams) with corresponding narrative that depicts an accurate and detailed description of the preliminary design for the entire application.Technical Architecture Submission for [project name] 4. Interfaces must be identified. and secureability should be reflected. Specify any known hardware and software details (brand. etc) for clients. External network connection speeds (for both the citizen and employee) should be documented. The preliminary design must align with the Principles. programming languages selected. Print Date:9/18/2012 109684635. Line of Business Application Logical Design – Zone 0/1 Internet Citizen (5000 Transactions Per day SSL Transaction Zone Firewall Transaction Zone (Hardened DMZ) Zone 2 Firewall VPN VPN Zone 2 (Internal Network) Zone 3 Firewall VPN VPN Zone 3 (Hardened Internal Network) Load Balancer Web Server Employee Desktop (N=300) DB Appl. Date: 3/07/2007 .e.doc Page 13 of 18 Template Rev. and deployment location (i.

doc Page 14 of 18 Template Rev.Technical Architecture Submission for [project name] 5. While the items listed are not intended to be an exhaustive list of the possible technologies that may be utilized in the implementation of an application. Detail System Checklist Client Operating Systems Responses – Select all that apply __ Apple __ Microsoft __ Linux __ Unix __ Palm __ Microsoft PocketPC __ Other (specify): __ Desktop/Laptop __ Tablet __ PDA __ Smart Phone __ Other (specify): Specify size of footprint in KB or MB: Desktop/Laptop: ___ Tablet: ___ PDA: ___ Smart Phone: ___ Other (specify): ___ Specify speed in kbps or mbps: Minimum: _____ Recommended: ________ __ Browser Based __ Rich Client __ Rich Internet (AJAX) __ Internet Explorer (specify versions): __ Netscape Navigator (specify versions): __ Other (specify product and versions): Client Platforms Client Footprint by Platform Client Connection Speed Client Richness Browsers and Versions Supported Print Date:9/18/2012 109684635. it does reflect some of the more common choices as well as important items that should be considered during the design phase. Date: 3/07/2007 .1 Detail System Design Checklist Disclaimer: Any technologies listed below have been provided solely for convenience. Detail System Design Section The Detail System Design Section has been designed to capture only the most essential information required at this point to obtain Detailed Design approval. 5. the information provided is not intended to be exhaustive nor does it indicate product endorsement by TS.

NET __C# __ JSP __ Servlets __ Java __ JVM (specify details): __ Server Side Includes (SSI) __ C++ __ Other (specify): __ Windows __ Linux __ Unix __ Other (specify): Specify Version: __ Microsoft __ IBM __ Sun __ Oracle __ BEA __ Other (specify): Specify Edition and Version: Application State Virtualization Web Server Location Web Server Operating System Web Server Software Web Server .Client Side Languages Responses – Select all that apply __ HTML __ DHTML __ XML __ XHTML __ VB. Date: 3/07/2007 .Specifications Presentation – Server Side Languages Application Server Operating System Application Server Software Print Date:9/18/2012 109684635.Technical Architecture Submission for [project name] Detail System Checklist Presentation .doc Page 15 of 18 Template Rev.High Availability Web Server .NET __ VB.NET __C# __ ActiveX Controls __ Java Applets __ Java __ JVM (specify details): __ JavaScript __ VBScript __ C++ __ Other (specify): __ Cookies: __ Non-Persistent Cookies __ Persistent Cookies __ Session Ids __ State Stored in Hidden Fields __ Other (specify): __ Server __ Storage __ Public Facing __ Internal Facing __ Windows __ Linux __ Unix __ Other (specify): Specify Version: __ Apache __ Microsoft __ Sun __ Oracle__ Other (specify): Specify Edition and Version: Load Balanced: __ Yes __ No Processor Architecture: __ 64 Bit __ 32 Bit Processor Cores: __ Double __ Single Other (specify): Rollout Configuration: Number of Servers: __ CPUs/Server: __ CPU Type: _________ CPU Speed: _____ Amount of RAM: ____ Maximum Configuration: Number of Servers: __ CPUs/Server: __ CPU Type: __________ CPU Speed: _____ Amount of RAM: ____ __ ASP.

Specifications Data Access – Connectivity Methods Print Date:9/18/2012 109684635.Technical Architecture Submission for [project name] Detail System Checklist Application Server – High Availability Responses – Select all that apply Processor Architecture: __ 64 Bit __ 32 Bit Processor Cores: __ Double __ Single RAID Supported: __ Yes __ No SAN Supported: __ Yes __ No Mirroring Supported: __ Yes __ No Clustering Supported: __ Yes __ No Grid/On Demand Supported: __ Yes __ No Other (specify): Rollout Configuration: Number of Servers: __ CPUs/Server: __ CPU Type: _________ CPU Speed: _____ Amount of RAM: ____ Maximum Configuration: Number of Servers: __ CPUs/Server: __ CPU Type: __________ CPU Speed: _____ Amount of RAM: ____ __ VB.Specifications Business Rule – Application Languages Database Server Operating System Database Server Software Database Server – High Availability Database Server .NET __ ODBC __ OLE/DB __ JDBC __ JDO __ DB2 Connect __ Other (specify): Application Server . Date: 3/07/2007 .NET __C# __ Java (J2SE) __ Java/EJB (J2EE) __ JVM (specify details): __ C++ __ Other (specify): __ Windows __ Linux __ Unix __ Other (specify): Specify Version: __ Microsoft __ IBM __ Oracle __ Other (specify): Specify Version: Processor Architecture: __ 64 Bit __ 32 Bit Processor Cores: __ Double __ Single RAID Supported: __ Yes __ No SAN Supported: __ Yes __ No Mirroring Supported: __ Yes __ No Clustering Supported: __ Yes __ No Grid/On Demand Supported: __ Yes __ No Other (specify): Rollout Configuration: Number of Servers: __ CPUs/Server: __ CPU Type: _________ CPU Speed: _____ Amount of RAM: ____ Maximum Configuration: Number of Servers: __ CPUs/Server: __ CPU Type: __________ CPU Speed: _____ Amount of RAM: ____ __ ADO.doc Page 16 of 18 Template Rev.

Date: 3/07/2007 .Technical Architecture Submission for [project name] Detail System Checklist SQL Languages Stored Procedures Utilization Responses – Select all that apply __ T/SQL __ PL/SQL __ Other (specify): __ No __ Yes __ Data Access only __ Business Rules and Data Access Print Date:9/18/2012 109684635.doc Page 17 of 18 Template Rev.

Note: The diagram below has been provided for illustrative purposes only. detailed. security. and integration architecture. Almost all details should be known at this point in the design process. All aspects of the application. channel support for the numerous client form factors such as webphone. Date: 3/07/2007 . and use of Common Infrastructure should be adequately reflected in the physical design.g. Interoperability. or Blackberry) should be documented. and complete description of the detail design for the entire application. The design must document how each of the requirements specified in the preliminary design will be physically accomplished. Print Date:9/18/2012 109684635. Secureability. as well as any other pertinent uses of technology to solve specific business requirements (e. Note: Narrative describing the detail design of the application must be provided immediately following the diagram(s).Technical Architecture Submission for [project name] 5. including specific hardware related information utilized by the hosting service provider. Scalability. Departments should delete the diagram provided and supply information specific to the application requesting approval.2 Detail System Design Description Provide a diagram (or diagrams) with corresponding narrative with that depicts an accurate. network. Design objectives such as Reliability.doc Page 18 of 18 Template Rev. The detailed design must align with the Principles. Availability. document imaging. PDA. and Standards that are published in the NCSTA . Practices.