System Design Template

[Insert Agency Name] [Insert Project Name] System Design Template Project Sponsor Submission Contact Name Submission Contact Title Submission Contact Phone Submission Contact Fax Submission E-Mail Date Submitted to ETS _________________________________________ Agency CTO/IT/MIS Director Signature _________________________________________ Agency Technical Lead Signature _________________________________________ Submission Contact Signature ____________ Date ____________ Date ____________ Date Technical Architecture Submission for [insert project name] Table of Contents 1. INTRODUCTION .................................................................................................................................3 1.1 1.2 2. 3. SYSTEM DESIGN SECTIONS ...............................................................................................................3 ETS OFFERS ASSISTANCE TO AGENCIES ..........................................................................................4 SYSTEM DESIGN CHANGE LOG ....................................................................................................4 CONCEPTUAL SYSTEM DESIGN SECTION .................................................................................5 3.1 3.2 3.3 CONCEPTUAL SYSTEM CHECKLIST ...................................................................................................5 FUNCTIONAL SYSTEM DESCRIPTION .................................................................................................7 CONCEPTUAL SYSTEM DESIGN DESCRIPTION ...................................................................................8 4. PRELIMINARY SYSTEM DESIGN SECTION................................................................................9 4.1 4.2 4.3 PRELIMINARY SYSTEM CHECKLIST ..................................................................................................9 PRELIMINARY SECURITY CHECKLIST .............................................................................................11 PRELIMINARY SYSTEM DESIGN DESCRIPTION ................................................................................13 5. DETAIL SYSTEM DESIGN SECTION ...........................................................................................14 5.1 5.2 5.3 5.4 5.5 PRESENTATION TIER (C LIENT SIDE) CHECKLIST ............................................................................14 PRESENTATION TIER (SERVER SIDE) CHECKLIST ...........................................................................15 BUSINESS RULE TIER CHECKLIST ...................................................................................................15 DATA TIER CHECKLIST...................................................................................................................16 DETAIL SYSTEM DESIGN DESCRIPTION ..........................................................................................19 6. NORTH CAROLINA STATEWIDE TECHNICAL ARCHITECTURE – DOMAINS ...............20 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 NETWORK DOMAIN: .......................................................................................................................20 APPLICATION DOMAIN: ..................................................................................................................20 DATA DOMAIN: ..............................................................................................................................20 SYSTEMS INTEGRATION DOMAIN: ..................................................................................................20 GROUPWARE DOMAIN: ...................................................................................................................20 PLATFORM DOMAIN: ......................................................................................................................20 ENTERPRISE MANAGEMENT DOMAIN: ............................................................................................20 SECURITY DOMAIN:........................................................................................................................20 System Design Template V1.0 Page 2 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 1. Introduction The System Design Template has been designed to enable agencies to provide an increasing amount of detail to Enterprise Technology Services (ETS) and the Information Resource Management Commission (IRMC) over the life of a project. Agencies requesting IRMC Project Certification will be required to complete this template, section by section, during the various phases of a project. To facilitate this process, this template has been separated into three sections. The sections of this template are described below in greater detail; in addition, they are summarized in Table 1: IRMC Project Certification Requirements. 1.1 System Design Sections Each section of the template must be completed to the extent possible for the SDLC phase that is being performed. If information is requested in a particular section that cannot be provided at the time of completion, then To Be Determined (TBD) should be specified. However, when the next section of the document is completed, then the information that was previously unavailable must be provided.  Conceptual System Design Section: Prior to ending the Requirements Phase of a project, this section of the document is required to be submitted, reviewed, and approved by ETS. Typically, at this point-in-time, many of the design requirements are not known. However, there should be sufficient high-level information available to obtain ETS approval of the Conceptual System Design. Preliminary System Design Section: Prior to ending the Preliminary Design Phase of a project, this section of the document is required to be submitted, reviewed, and approved by ETS. At this point-in-time, many of the technical details about the system are known. Therefore, there should be sufficient technical information available to obtain ETS approval of the Preliminary System Design. Detail System Design Section: Prior to ending the Detailed Design Phase of a project, this section of the document is required to be submitted, reviewed, and approved by ETS. At this point-in-time almost all of the technical details about the system are known. Information provided at this stage in the process must be comprehensive and accurate. Completion of this section should enable the agency to obtain ETS approval of the Detail System Design. Once this approval has been issued, the Implementation phase may begin. Note: Prior to beginning the Installation Phase an updated version of the Detailed System Design must also be approved. IEEE SDLC Project Phase Concept Requirements Design   Preliminary Detail Preliminary System Design Detail System Design Conceptual System Design Approval of deliverable required prior to beginning next phase   Implementation  Coding  Testing Updated Detail System Design Installation Operation and Maintenance Table 1: IRMC Project Certification Requirements System Design Template V1.0 Page 3 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 1.2 ETS Offers Assistance to Agencies One of the primary services that ETS offers to the agencies is system design review and assistance. Involving ETS as early as possible in the project (e.g. during RFP creation or system design) is key factor to the overall success of a project. This type of early involvement helps to ensure that the agency is complying with the North Carolina Statewide Technical Architecture (NCSTA). It also facilitates IRMC Project Certification approval. If you would like to request ETS assistance, or have any questions concerning the completion of this document, please contact ETS staff at (919) 981-5510. 2. System Design Change Log Any moderate or significant changes to the system design must be resubmitted to ETS for review and approval prior to making any actual change(s) to the design. In most cases, the review and approval of any changes would be performed internally within ETS. If IRMC Certification Review is required, ETS will coordinate providing the information to the IRMC for review and approval. Notes: 1. Use of a word processing automated tracking change feature is required when resubmitting this document 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 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 ETS that the project be de-certified by the IRMC. 3. If there are any questions as to whether or not a change is substantive enough to warrant review and approval, please contact ETS staff at (919) 981-5510 for clarification. 4. Maintain a summary of changes in the table below. Change Log Summary – Version and Description (For instructional purposes an example has been provided) V1.0 - Conceptual System Design V1.1 - Added Web Services and made other minor changes V2.0 - Preliminary System Design V3.0 - Detailed System Design V4.0 – Updated Detail System Design Date submitted to ETS for review 12/1/2003 2/1/2004 4/1/2004 7/1/2004 10/1/2004 Date approved by ETS 12/15/2003 2/13/2004 4/16/2004 7/16/2004 10/15/2004 System Design Template V1.0 Page 4 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 3. Conceptual System Design Section The Conceptual System Design Section has been designed to capture only the most essential information required for IRMC Initial Project Certification in a quick and concise manner. 3.1 Conceptual System 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 ETS. Conceptual System Checklist Reviewed and approved by Agency CTO Agency Architecture Compliance NCSTA Compliance IRMC Policies and Standards Compliance Project Type Response - Select all that apply __Yes __No (explain): __Yes __No (specify rationale below) __Yes __No (specify rationale below) __Yes __No (specify rationale below) __ New System __ Upgrade System __ New Infrastructure __ Upgrade Infrastructure __ Other (specify): __ COTS: Modification Level: __ Low __ Medium __ High __ Custom __ Other (specify): __ Yes __ No __ Yes __ No __ State Employee Staff (specify estimated percentage): __ Contracted Staff (specify estimated percentage): __ Yes __ No __ NA __ Waterfall __ Iterative __ Spiral __ Other (specify): __ Yes __ No __ Government to Citizen (G2C) __ Government to Employee (G2E) __ Government to Government (G2G) __ Government to Business (G2B) __ Other (specify): __ Yes: __ Credit Card __ ACH __ EFT __ Other (specify): __ No Project Solution Business Process Re-Engineering Business Process Modeling Project Staffing RFP Approved by ITS State IT Procurement Office SDLC Methodology SDLC Methodology consistent with current IEEE standards Application Pattern(s) Electronic Payment Functionality System Design Template V1.0 Page 5 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Conceptual System Checklist System Integration Requirements Response - Select all that apply __ State Government: __ Intra-Agency __ Inter-Agency __ Local Government __ Federal Government __ Business __ Other (specify): __ HIPAA __ FERPA __ GPEA __ Other (specify): __ Yes __ No __ Yes __ No Specify: Specify: Specify: Specify: Specify: __ Citizen __ Normal Business Hours (i.e. 8:00 am to 5:00 pm) __ Extended Business Hours (specify): __ 24 X 7 __ Employee __ Normal Business Hours (i.e. 8:00 am to 5:00 pm) __ Extended Business Hours (specify): __ 24 X 7 __ Government/Business Partner(s) __ Normal Business Hours (i.e. 8:00 am to 5:00 pm) __ Extended Business Hours (specify): __ 24 X 7 __ Yes __ No __ Yes __ No Special Legal or Privacy Requirements W3C Accessibility Compliance Section 508 Accessibility Compliance Total Number of Anticipated Users Maximum Number of Concurrent Users Anticipated Annual User Growth Rate Average Number of Transactions/Day Average Transaction Response Time (Round Trip in Seconds) Production System Availability Requirements Statewide Rollout Conduct Pilot before Statewide Rollout System Design Template V1.0 Page 6 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 3.2 Functional System Description Provide a diagram (or diagrams) that depicts the functional aspects of the application. Corresponding narrative that describes each major functional area of the application must also be supplied. Describe how the system will be used and operated. Describe both the type of users of the system as well as any business interfaces that may be necessary. Leverage existing system design documentation whenever possible. For example, information from the Project Initiation and Implementation Document (PIID) or a Request For Proposal (RFP) would be appropriate for use in this section. Note: The diagram below has been provided for illustrative purposes only. Agencies should delete the diagram provided and supply information specific to the application requesting certification. Financial Management Application (Functional Design) Employees Purchasing Accounts Payable Accounts Receivable Fixed Assets Internal Agency Interfaces (e.g Payroll, And HR) External Agency Interfaces (Specify) General Ledger Direct Deposits Billing Bank Reconciliation Shipping Business Citizens Reporting Note: Narrative describing the functional design of the application must be provided immediately following the diagram(s). System Design Template V1.0 Page 7 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 3.3 Conceptual System Design Description Provide a diagram (or diagrams) that depicts an accurate description of the conceptual design for the entire application. 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 NCSTA . Leverage existing system design documentation whenever possible. For example, information from an RFP response would be appropriate for use in this section. Note: The diagram below has been provided for illustrative purposes only. Agencies should delete the diagram provided and supply information specific to the application requesting certification. Financial Management Application – Conceptual Design Internet DMZ Internal Network Hardened Internal Network Firewall 3 Firewall 1 Firewall 2 Citizen Web Server Employee Application Server Database Server Firewall 3 Single (or Reduced) Sign-on Service EDI Messaging Middleware External Agency Application Credit Card Processing Service External Business Partner Note: Narrative describing the conceptual design of the application must be provided immediately following the diagram(s). System Design Template V1.0 Page 8 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert 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 IRMC Preliminary Design Certification Review 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 an application, it does reflect some of the more common choices as well as important items that should be considered during the design phase. 4.1 Preliminary System 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 ETS. Preliminary System Checklist Application Architecture Processing Type Application Access Requirements Development Platform Architectural Framework(s) (e.g. STRUTS, JATO, JSF) Architectural Pattern(s) (e.g. MVC, Factory, Controller, DAO, DTO) Service Interface Techniques Responses – Select all that apply __ SOA __ 3/N Tier __ Other (specify): __ OLTP __ OLAP __ Other (specify): __ Internet __ Intranet __ Extranet__ Other (specify): __ J2EE __ .NET __ Other (specify): Specify: Specify: Orchestration or Choreography System Integration Technologies Source Code Management Tools Source Code Reuse Application Testing Tools Specialized Testing Team __ Web Services (i.e. HTTP, XML, SOAP, WSDL, UDDI, etc.) __ Interface Located on Web Server in TZ __ Interface Located on Application Server in Z2/Z3 __ .NET Remoting __ Binary over HTTP/S __ Binary over TCP __ EJB/RMI - IIOP __ Yes __ No __ XML __ Web Services __ Messaging __ EDI __ CORBA __IIOP __ Connectors/Adaptors __ Secure FTP __ Other (specify): __ Yes (specify): __ No Specify (estimated percentage): __ Yes (specify): __ No __ Yes __ No System Design Template V1.0 Page 9 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Preliminary System Checklist Software Testing Stages Responses – Select all that apply General: __ Subroutine __ New Function __ Regression __ Integration __ System Specialized: __ Stress __ Error Handling __ Application Recovery __ Disaster Recovery __ Security __ Performance __ Platform __ Accessibility: __ WCAG V1.0: __ Priority 1 __ Priority 2 __ Priority 3 __ WCAG V2.0 Draft: __ Level 1 __ Level 2 __ Level 3 __ Section 508 User-Participation: __ Alpha __ Beta __ User Acceptance __ Other (specify): __ Classroom __ CBT __ Internet __ Train the Trainer __ Practice/Sand Box __ Other (specify): __ Yes __ No __ Less than $50,000 __ $50,001 to $100,000 __ $100,001 to $500,000 __ $500,001 to $1,000,000 __ $1,000,000 or more __ Less than $50,000 __ $50,001 to $100,000 __ $100,01 to $500,000 __ $500,001 to $1,000,000 __ $1,000,000 or more __ ITS __ Agency __ Other: (specify location): __ Yes __ No __ Yes __ No __ Development __ Test __ Production __ Other (specify): __ Shares Servers with other applications __ Separate Servers from other applications __ Common Payment Service __ Identity Access Management System (IAMS) __ NC @Your Service __ NCMail __ NC Service Broker __ Mainframe __ MaPS __ Network __ Firewall __ Call Center __ Other (specify): __ Yes (specify): __ No User Training Help Desk Support Provided Additional Hardware Purchases Required for Implementation Additional Software Purchases Required for Implementation Hosting Service Provider Formalized SLA with Business Owner Formalized SLA with Service Provider Dedicated Environments Production Application Environment Use of State Common Services by this Application System Management Tools System Design Template V1.0 Page 10 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Preliminary System Checklist Asset Management Tools Directory Services Business Continuity Capabilities Responses – Select all that apply __ Yes (specify): __ No __ Novell __ Microsoft __ Other (specify): __ Yes: __ Test Twice/Year __ Test Once/Year __ Other (specify): __ No 4.2 Preliminary Security Checklist Preliminary Security Checklist Security Technologies Responses – Select all that apply __ Identity and Access Management: __ COTS (specify product/service): __ Custom __ Hardware Firewall(s) __ Software Firewall (on client devices) __ Network IDS/IPS __ Host IDS/IPS __ Anti-Virus Software __ File Integrity Software __ PKI __ Remote Access: __ VPN (IPSEC) __ VPN (SSL) __ RADIUS __ TACACS __ Other (specify): __ SSL/TLS (communication between Browser and Web Server) __ Remote Admin __ SSH __ Telnet __ Remote Control Software __Other (specify): __ Secure FTP __ Secure Copy __ FTP __ Other (specify): __ Database Encryption __ Provided by Database __ Third Party Product (specify): __ Column __ Row __ Table __ Database __ Cookie Encryption __ DES __ 3DES __ AES __ Other (specify): __ Wireless __ WPA __ WEP __ 802.1X __ Other (specify): Other (specify): Production Environment: __ Minimal __ Moderate __ Extensive Employee Desktop: __ Minimal __ Moderate __ Extensive Formalized Physical Access Controls System Design Template V1.0 Page 11 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Preliminary Security Checklist NCSTA Security Architecture Compliance IRMC Security Policies and Standards Compliance IRMC Security Checklist Submitted IRMC Security Risk Assessment Submitted Responses – Select all that apply __ Yes __ No __ Yes __ No __ Yes __ No __ Yes __ No System Design Template V1.0 Page 12 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 4.3 Preliminary System Design Description Provide a diagram (or diagrams) that depicts an accurate and detailed description of the preliminary design for the entire application. The design must document how each of the requirements specified in the conceptual design will be logically accomplished. The preliminary design must align with the Principles, Practices, and Standards that are published in the NCSTA . At this point, details such as scalability, availability, and secureability should be reflected. External network connection speeds (for both the citizen and employee) should be documented. The supporting application should perform at acceptable levels when utilizing lowest common access speeds. Specify any known hardware and software details (brand, model, version, etc) for clients, servers, and other network infrastructure; programming languages selected, and deployment location (i.e. server location where code is deployed). Interfaces must be identified. Leverage existing system design documentation whenever possible. Note: The diagram below has been provided for illustrative purposes only. Agencies should delete the diagram provided and supply information specific to the application requesting certification. 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) VPN VPN Zone 3 (Hardened Internal Network) Zone 3 Firewall Load Balancer Web Server Employee Desktop (N=300) Appl. Server (Cluster) DB Server (Mirror) Remote Access Employees (N=50) Zone 3 Firewall VPN VPN WAN Identity Access Management System EDI Dedicated Circuit 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). System Design Template V1.0 Page 13 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 5. 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 IRMC Detailed Design Certification Review 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 an application, it does reflect some of the more common choices as well as important items that should be considered during the design phase. 5.1 Presentation Tier (Client Side) 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 ETS. Presentation Tier (Client Side) Checklist Client Platforms Client Operating Systems Client Footprint Recommended Client Connection Speed Amount of Client’s Recommended Bandwidth Required for this Application Utilizes Wireless Technologies Responses – Select all that apply __ Desktop __ Laptop __ Tablet __ Thin Client __ PDA __ Web/Smart Phone __ Other (specify): __ Apple __ Microsoft __ Linux __ Unix __ Palm __ Microsoft CE __ Other (specify): Specify size in KB or MB: Specify speed in kbps or mbps: Specify percentage: __ WLAN: __ 802.11b __ 802.11g __ Other (specify): __ WWAN: __ Point-to-Point __ Point-to-Multi-Point __ Commercial Service Provider __ CJIN MDN __ Other (specify): __NA __ Internet Explorer (specify versions): __ Netscape Navigator (specify versions): __ AOL (specify versions): __ Other (specify product and versions): __ HTML __ XHTML __ Server Side Includes __ ActiveX Controls __ Java Applets __ Java Applications __ JVM (specify details): __ Other (specify): __ HTML __ XML __ XSL __ XLST __ C __ C++ __Visual C++ __ VB.NET __C# __ Java Applets __ Java Application __ JavaScript __ VBScript __ Other (specify): Browsers and Versions Supported Browser Technologies Client Side Languages (Presentation Tier – Client Side) System Design Template V1.0 Page 14 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Presentation Tier (Client Side) Checklist Application State Responses – Select all that apply __ Cookies: __ Non-Persistent Cookies __ Persistent Cookies __ Encrypted __ Session Ids __ Hidden Fields __ Other (specify): 5.2 Presentation Tier (Server Side) Checklist Presentation Tier (Server Side) Checklist Network Backbone Speed Web Server Location Web Server Hardware Web Server Operating System Web Server Software Web Server Languages (Presentation Tier - Server Side) Responses – Select all that apply __ Gigabit __ 100 mbps __ 10 mbps __ Other (specify): __ Zone 1 __ Zone 2 __ Transaction Zone __ Zone 3 __ Compaq __ Dell __ HP __ IBM __ Sun __ Other (specify): __ Windows __ Linux __ Unix __ Other (specify): Specify Version: __ Apache __ Microsoft __ Sun __ Oracle__ Other (specify): Specify Version: __ Server Side Extensions __ C __ C++ __Visual C++ __ VB.NET __ ASP.NET __C# __ JSP __ Java __ Java Servlets __ Java/EJB __ Other (specify): __ UPS __ Load Balanced __ Clustered __ Dual Power Supply __ Dual NIC __ Dual Processor __ RAID __ Mirror __ 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: ____ Web Server Redundancy Web Server Specifications 5.3 Business Rule Tier Checklist System Design Template V1.0 Page 15 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Business Rule Tier Checklist Application Server Location Application Server Separation Application Server Hardware Application Server Operating System Application Server Software Application Server Languages (Business Rule Tier) Responses - Select all that apply __ Zone 1 __ Zone 2 __ Transaction Zone __ Zone 3 Separate physical server(s) from Web Server: __ Yes __ No __ Compaq __ Dell __ HP __ IBM __ Sun __ Other (specify): __ Windows __ Linux __ Unix __ Other (specify): Specify Version: __ Microsoft __ IBM __ Sun __ Oracle __ BEA __ Other (specify): Specify Version: Total Estimated Number Lines of Code (#LOC): __________ __ C __ C++ __Visual C++ __ VB.NET __ ASP.NET__C# __ JSP __ Java __ Java Servlets __ Java/EJB __ Other (specify): __ Microsoft Enterprise Services __ Oracle Object Container __ Java Transaction Server __ IBM WebSphere __ IBM CICS __ Other (specify): __ UPS __ Load Balanced __ Clustered __ Dual Power Supply __ Dual NIC __ Dual Processor __ RAID __ Mirror __ 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: ____ Application Server Transaction Monitor Application Server Redundancy Application Server Specifications 5.4 Data Tier Checklist Data Tier Checklist Database Server Location Database Server Separation Database Server Hardware Database Server Operating System Responses - Select all that apply __ Zone 1 __ Zone 2 __ Transaction Zone __ Zone 3 Separate physical server(s) from Application Server: __ Yes __ No __ Compaq __ Dell __ HP __ IBM __ Sun __ Other (specify): __ Windows __ Linux __ Unix __ Other (specify): Specify Version: System Design Template V1.0 Page 16 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Data Tier Checklist Database Server Software Database Server Access Responses - Select all that apply __ Microsoft __ IBM __ Oracle __ Other (specify): Specify Version: __ ADO.NET __ ODBC _OLE/DB __ SQL*NET __ JDBC __ SQLJ __ DB2 Connect __ Other (specify): __ T/SQL __ PL/SQL __ Other (specify): Total Estimated Number Lines of Code (# LOC): ____ Stored Procedures used for Business Rules: __ Yes __ No Stored Procedures used for Data Access only: __ Yes __ No __ UPS __ Load Balanced __ Clustered __ Dual Power Supply __ Dual NIC __ Dual Processor __ RAID __ Mirror __ 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: ____ __ Local Disk __ RAID __ SAN __ NAS __ Other (specify): Specify in MB, GB, or TB: Specify in MB, GB, or TB: __ Yes __ No __ Full Frequency: ___________ Est. Time Required: ___________ __ Real Time from Mirror __ Real Time by Database __ Offline __ Incremental Frequency: ___________ Est. Time Required: ___________ __ Real Time from Mirror __ Real Time by Database __ Offline Full: Est. Time Required: ___________ Incremental: Est. Time Required: ___________ Database Languages (Data Tier) Database Server Stored Procedures (Data Tier) Database Server Redundancy Database Server Specifications Database Server Storage Type Database Size (Estimated) Database Annual Growth Rate (Estimated) Data Migration Planned Database Backup Database Recovery System Design Template V1.0 Page 17 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] Data Tier Checklist Database Userids defined by user role Responses - Select all that apply One Database Userid for entire application: __ Yes __ No One Database Userid for each user role: __ Yes __ No: One Database Userid for each user: __ Yes __ No: Other (specify): Passwords comply with IRMC Password Policy and Standard: __ Yes __ No Passwords are not exposed in any way in application code: __ Yes __ No Database Userid Passwords System Design Template V1.0 Page 18 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 5.5 Detail System Design Description Provide a diagram (or diagrams) that depicts an accurate, detailed, 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. The detailed design must align with the Principles, Practices, and Standards that are published in the NCSTA . Almost all details should be known at this point in the design process. 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 webphone, PDA, or Blackberry) should be documented. Leverage existing system design documentation whenever possible. Note: The diagram below has been provided for illustrative purposes only. Agencies should delete the diagram provided and supply information specific to the application requesting certification. Note: Narrative describing the detail design of the application must be provided immediately following the diagram(s). System Design Template V1.0 Page 19 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008 Technical Architecture Submission for [insert project name] 6. North Carolina Statewide Technical Architecture – Domains The architecture domains for the State of North Carolina are listed below. Please provide any significant architectural information (that has not been previously provided) for this application. 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 or NCSTA Principles, Standards, or Best Practices. 6.1 Network Domain: [Specify any additional information] 6.2 Application Domain: [Specify any additional information] 6.3 Data Domain: [Specify any additional information] 6.4 Systems Integration Domain: [Specify any additional information] 6.5 Groupware Domain: [Specify any additional information] 6.6 Platform Domain: [Specify any additional information] 6.7 Enterprise Management Domain: [Specify any additional information] 6.8 Security Domain: [Specify any additional information] System Design Template V1.0 Page 20 of 20 39781754-e1ea-498a-8562-9f99e98de598.doc Print Date: 8/12/2008