The document provides functional specifications for the first phase of redesigning the Trane Commercial Site (TCS). It outlines standards for templates, both dynamic and static, and content types that will be managed through different systems. Navigation patterns and templates are specified for different sections and levels of the site. The specifications are intended to guide front-end development while allowing flexibility in implementation.
The document provides details of the detailed design stage of an autonomous cleaning robot project. It includes engineering drawings of all components and assemblies using CAD software. Drawings include exploded views, bills of materials, and part lists. Failure modes and effects analysis was performed and issues identified were addressed in the design. The functioning of the team is described as satisfactory with all members participating and contributing to the project.
BPMN 2.0 is a standard for business process modeling notation that was developed by BPMI and is now maintained by OMG. BPMN 2.0 extends the capabilities of BPMN 1.2 by formalizing business process execution semantics, defining extensibility mechanisms, and extending the definition of human interaction. The key modeling elements in BPMN 2.0 include pools, lanes, activities, events, gateways, sequence flows, message flows, and associations.
http://rational-tools.info
The CMC-Visualizer for Team Concert module is developed for user-friendly provision of data about change requests stored in IBM Rational TeamConcert. The CMC-Visualizer for Team Concert features include the visualization of the tree of request states, display of the requests hierarchy as a Gantt chart, and generation of reports on change requests in PDF format.
The document discusses modeling and validating BPMN diagrams. It proposes a simplified metamodel for BPMN 1.1 that addresses weaknesses in the original specification such as inconsistent hierarchical structure and lack of validation support. The proposed metamodel includes a self-validating XML serialization and automated checks to validate BPMN diagrams. It also discusses how the approach could be adapted for BPMN 2.0.
This document provides a summary of improved mapping and modeling of defense domain architectures. It contains 22 slides summarizing concepts related to the Department of Defense Architecture Framework (DoDAF), including the DoDAF meta-model, views, concepts and issues. It also discusses mapping information sets and ontologies between different frameworks and challenges doing so.
software engineering with uml- activity diagramrahmantoyuri
This document discusses activity diagrams, interaction overview diagrams, and business process models. It provides an overview of the key notations and uses of activity diagrams, including modeling business processes, use case flows, and system flows. The document also discusses interaction overview diagrams and business process model and notation (BPMN). Finally, it provides examples of activity diagrams for a hospital management system to illustrate how they can be used to model specific processes like registering a patient, maintaining a calendar, booking a consultation, and paying a bill.
There are two major pitfalls in the development of extensions to the BPMN 2.0 metamodel.
First, there is a lack of methodological guides considering the extensibility approach supported by the extension mechanism of the language.
Second, BPMN does not provide any graphical notation for the representation of extensions.
This work proposes a method based on Model-Driven Architecture for the development of extensions to the BPMN 2.0 metamodel. It enables the conceptual modeling of extensions by using UML, their graphical representation in terms of the BPMN extension mechanism, and their transformation into XML Schema documents that can be processed by BPMN tools. A tool supporting the proposed method is also presented.
This document provides an overview of the general store inventory system design project. It includes sections that describe the context diagram, data flow diagrams, entity relationship diagram, class diagram, activity diagram, sequence diagrams, and architecture design. The document also lists the various forms and reports that will be used in the system, such as products, customers, suppliers, transactions, sales, and stock management.
The document provides details of the detailed design stage of an autonomous cleaning robot project. It includes engineering drawings of all components and assemblies using CAD software. Drawings include exploded views, bills of materials, and part lists. Failure modes and effects analysis was performed and issues identified were addressed in the design. The functioning of the team is described as satisfactory with all members participating and contributing to the project.
BPMN 2.0 is a standard for business process modeling notation that was developed by BPMI and is now maintained by OMG. BPMN 2.0 extends the capabilities of BPMN 1.2 by formalizing business process execution semantics, defining extensibility mechanisms, and extending the definition of human interaction. The key modeling elements in BPMN 2.0 include pools, lanes, activities, events, gateways, sequence flows, message flows, and associations.
http://rational-tools.info
The CMC-Visualizer for Team Concert module is developed for user-friendly provision of data about change requests stored in IBM Rational TeamConcert. The CMC-Visualizer for Team Concert features include the visualization of the tree of request states, display of the requests hierarchy as a Gantt chart, and generation of reports on change requests in PDF format.
The document discusses modeling and validating BPMN diagrams. It proposes a simplified metamodel for BPMN 1.1 that addresses weaknesses in the original specification such as inconsistent hierarchical structure and lack of validation support. The proposed metamodel includes a self-validating XML serialization and automated checks to validate BPMN diagrams. It also discusses how the approach could be adapted for BPMN 2.0.
This document provides a summary of improved mapping and modeling of defense domain architectures. It contains 22 slides summarizing concepts related to the Department of Defense Architecture Framework (DoDAF), including the DoDAF meta-model, views, concepts and issues. It also discusses mapping information sets and ontologies between different frameworks and challenges doing so.
software engineering with uml- activity diagramrahmantoyuri
This document discusses activity diagrams, interaction overview diagrams, and business process models. It provides an overview of the key notations and uses of activity diagrams, including modeling business processes, use case flows, and system flows. The document also discusses interaction overview diagrams and business process model and notation (BPMN). Finally, it provides examples of activity diagrams for a hospital management system to illustrate how they can be used to model specific processes like registering a patient, maintaining a calendar, booking a consultation, and paying a bill.
There are two major pitfalls in the development of extensions to the BPMN 2.0 metamodel.
First, there is a lack of methodological guides considering the extensibility approach supported by the extension mechanism of the language.
Second, BPMN does not provide any graphical notation for the representation of extensions.
This work proposes a method based on Model-Driven Architecture for the development of extensions to the BPMN 2.0 metamodel. It enables the conceptual modeling of extensions by using UML, their graphical representation in terms of the BPMN extension mechanism, and their transformation into XML Schema documents that can be processed by BPMN tools. A tool supporting the proposed method is also presented.
This document provides an overview of the general store inventory system design project. It includes sections that describe the context diagram, data flow diagrams, entity relationship diagram, class diagram, activity diagram, sequence diagrams, and architecture design. The document also lists the various forms and reports that will be used in the system, such as products, customers, suppliers, transactions, sales, and stock management.
Tata Consultancy Services (TCS) is an Indian multinational information technology service and consulting company headquartered in Mumbai, India. It is a subsidiary of Tata Group and has over 226,751 employees. Some key people mentioned are S. Ramadorai as Vice Chairman, Dr. Vijay Kelkar as Director, Ishaat Hussain as Director, and Phiroz Vandrevala as Director. TCS has many branches and campuses located across India in cities like Lucknow, Hyderabad, Chennai, Pune, and Kolkata.
Tata Consultancy Services (TCS) is an Indian multinational information technology service and consulting company founded in 1968, providing a wide range of IT services and software engineering. TCS operates in 46 countries with over 400,000 employees and has become the largest IT services company in India. The document provides an overview of TCS's vision, history, services, products, growth, offices globally, and opportunities for careers with the company.
13th Sep, Drupal 7 advanced training by TCS DrupalMumbai
This document provides an overview and introduction to Drupal module development. It discusses Drupal hooks like hook_menu(), hook_permission(), hook_form(), and the Entity API. It also covers creating modules, forms, variables, blocks, and interacting with the database. The event is for a Drupal Global Training Day in Mumbai, India hosted by Drupal Mumbai and Tata Consultancy Services.
Ppt 6weeks tcs i_on_summer training for b.e._b.tech._mca_2016Ashish Arora
The document outlines a 6-week or 6-month summer training program offered by TCS iON that includes 3 levels of training. Level I focuses on technology training in areas like Java, .NET, mobile apps, databases, and more. Level II involves working on minor or major projects. Level III is for project documentation and submission. Trainees will receive guidance from experienced faculty, certification from TCS iON, and the training program offers wide industry recognition.
1. Tata Consultancy Services (TCS) is a leading global IT services, consulting and business solutions organization with over 335,000 employees worldwide.
2. TCS believes in maintaining an open and collaborative work culture for employees and providing benefits such as training programs, medical insurance, loans, and cultural activities.
3. TCS uses a rigorous selection process for recruiting and promoting employees that includes written tests, interviews, presentations and assessing leadership qualities at different levels from entry-level to top management.
The document discusses the importance of predictive analytics for business agility. It outlines how predictive analytics can help businesses address challenges in areas like customer satisfaction, consumer behavior, pricing, and inventory management. The document also provides examples of how TCS has helped clients in various industries like retail, banking, manufacturing, and media leverage predictive analytics to improve outcomes in domains such as marketing ROI, risk assessment, demand forecasting, and customer churn. TCS's analytics as a service model aims to provide an integrated and global team to help clients derive value from analytics.
Design of Industrial Automation Functional Specifications for PLCs, DCs and S...Living Online
This manual will be useful to both specifiers and implementers providing a theoretical grounding for preparing a control system functional specification for implementation on Industrial control systems consisting of PLC (Programmable Logic Controllers), HMI (Human Machine Interfaces / SCADA devices) or DCS (Distributed Control Systems).
FOR MORE INFORMATION: http://www.idc-online.com/content/design-industrial-automation-functional-specifications-plcs-dcss-and-scada-systems-15
This document is a functional specification for a project with the purpose of describing the functions and scope. It includes sections for an introduction, scope overview, and a list of functions. The introduction defines the purpose and references other documents. The scope overview describes the project and lists any constraints or assumptions. The list of functions section defines each function with a description, process flow, and field details.
This document discusses Tata Consultancy Services' (TCS) business model and strategies between 2007-2008 and 2013-2014. It analyzes TCS' business model using PESTEL analysis and external factor evaluation matrices for the two time periods. The analysis shows that TCS has strategically built advantages related to cost efficiency and service efficiency over time through business choices that created interrelated positive consequences and sustained competitive advantages.
TCS offers IT and IT-enabled consulting services globally using their Global Network Delivery Model. They see growth opportunities in the growing IT services market where they have a small market share. Their strategy is to expand geographically, increase industry coverage, and deepen client relationships through innovation, acquisitions, and non-linear business models like software products and platform-based services. Key elements are customer-centricity, a full services portfolio, the Global Network Delivery Model for seamless global delivery, and strategic acquisitions.
The document provides an overview of Cadbury Schweppes PLC, including its operations strategy, processes, human resource management, capacity planning, lean systems, supply chain design, and location planning. Cadbury originated in Birmingham in 1824 and has since expanded globally, operating in over 60 countries with around 65,000 employees. It faces competition from other large confectionery companies and must manage various constraints in its business operations.
This report analyzes the IT industry in India and Tata Consultancy Services' (TCS) business strategy. It provides an overview of the growing Indian IT industry and its competitive advantages. It then performs a PESTLE analysis of the external environment, Porter's Five Forces analysis, and a SWOT analysis of the industry. For TCS, it describes the company's profile, financial performance, resources, service offerings, and growth strategies. It analyzes TCS' strategies using the BCG matrix and provides recommendations to strengthen TCS' position, such as focusing on higher value services and intellectual property.
1) Tata Consultancy Services (TCS) is a global IT services company and India's largest exporter, with revenues of $7.21 billion in 2011.
2) TCS aims to be among the top 3 IT services companies worldwide through a culture of accountability and delivering certainty to customers.
3) TCS has strong ethics and compliance programs, including oversight by an Ethics and Compliance Committee and designation of an Ethics Counselor.
Tata Consultancy Services (TCS) is the largest Indian multinational information technology services and consulting company. It has over 200,000 employees across 47 countries. TCS aims to be a top 10 global IT company by focusing on innovative solutions, strong vertical expertise, and a wide global presence across industries like banking, telecom, manufacturing and more. In the past 2 years, TCS has grown revenues by 32% and profits by 62% through strategies like expanding in emerging markets and new technologies like cloud computing.
TCS is one of India's largest private sector employers with over 250,000 employees. The document discusses TCS's compensation strategy, including its components such as basic wages, incentives, and employee benefits. It also describes TCS's EVA compensation model which measures operating and financial performance to determine employee compensation. Surveys show high levels of employee satisfaction at TCS compared to industry averages, particularly regarding training, appraisal systems, and overall satisfaction. TCS uses a combination of fixed pay and variable pay linked to performance to incentivize employees.
The document summarizes different types of functional strategies that support corporate and business unit objectives. It discusses marketing, research and development, human resource management, financial, and information management strategies. The strategies focus on maximizing productivity of resources within each functional area to provide competitive advantages.
Tata Consultancy Services (TCS) is one of the leading global IT services, consulting and business solutions organizations. It aims to be among the top 10 global IT companies by 2010 in terms of revenue, profitability, customers and technology leadership. TCS provides innovative consulting, IT solutions and services across industries, with a workforce of over 74,000 professionals spread across many global delivery centers. It helps customers optimize business processes and create resilient IT infrastructure to ensure faster business results. Some of its key competitors include Infosys, IBM, Wipro and Cognizant.
This low level design document outlines the tax payer registration functionality with details of the navigation flow, UI implementation, client and server side validations, components design, data design with key tables and access levels, and testing approach. It provides developers with a reference to develop the system with minimal effort.
This document provides a technical design specification for a process implementation at Company ABC. It includes an overview of the process with definitions of terms and acronyms. Process models are presented for the main and sub-processes along with descriptions. The scope outlines what is included, such as the technical solution, error handling, security, logging, and external interactions. Out of scope items are also listed.
CMGT/410 v19
Business Requirements Template
CMGT/410 v19
Page 2 of 14Business Requirements TemplateHow to Use This Document
This document is a template for creating a Business Requirements Document (BRD); it includes instructions and examples for guidance. As you complete your BRD using the template, only include sections pertinent to your project.Table of Contents
How to Use This Document1
Table of Contents1
1.Executive Summary2
1.1Project Overview2
1.2Purpose and Scope of this Specification2
2.Product/Service Description3
2.1Product Context3
2.2User Characteristics3
2.3Assumptions3
2.4Constraints3
2.5Dependencies3
3.Requirements4
3.1Functional Requirements4
3.2User Interface Requirements5
3.3Usability5
3.4Performance6
3.4.1Capacity6
3.4.2Availability6
3.4.3Latency6
3.5Manageability/Maintainability6
3.5.1Monitoring6
3.5.2Maintenance6
3.5.3Operations7
3.6System Interface/Integration7
3.6.1Network and Hardware Interfaces7
3.6.2Systems Interfaces7
3.7Security8
3.7.1Protection8
3.7.2Authorization and Authentication8
3.8Data Management8
3.9Standards Compliance9
3.10 Portability9
4.User Scenarios/Use Cases9
5.Deleted or Deferred Requirements9
6.Requirements Confirmation/Stakeholder Sign-Off10
Appendices11
Appendix A: Definitions, Acronyms, and Abbreviations11
Appendix B: References11
Appendix C: Requirements Traceability Matrix12
Appendix D: Organizing the Requirements131. Executive Summary
1.1 Project Overview
Describe this project or product and its intended audiences, or provide a link or reference to the project charter.
1.2 Purpose and Scope of this Specification
Describe the purpose of this specification and its intended audience. Include a description of what is within the scope what is outside of the scope of these specifications.
Example:
In Scope
This document addresses requirements related to Phase 2 of Project A:
· Modification of Classification Processing to meet legislative mandate ABC
· Modification of Labor Relations Processing to meet legislative mandate ABC
Out of Scope
The following items in Phase 3 of Project A are out of scope:
· Modification of Classification Processing to meet legislative mandate XYZ
· Modification of Labor Relations Processing to meet legislative mandate XYZ
(Phase 3 will be considered in the development of the requirements for Phase 2, but the Phase 3 requirements will be documented separately.)2. Product/Service Description
In this section, describe the general factors that affect the product and its requirements. This section should contain background information, not state specific requirements (provide the reasons why certain specific requirements are later specified).
2.1 Product Context
How does this product relate to other products? Is it independent and self-contained? Does it interface with a variety of related systems? Describe these relationships or use a diagram to show the major components of the larger system, interconnections, and external interfaces.
2.2 User Characteristics
Create gen.
Super applied in a sitecore migration projectdodoshelu
This document describes using a business process model and ontology for a Sitecore migration project. It discusses key Sitecore concepts like items, templates, fields and presentation components. An ontology is proposed to model Sitecore concepts and help answer competency questions during content creation. Integrating the business process model with SUPER could provide semantic tools and services to help manage the migration, increasing flexibility and reducing costs and time. Potential disadvantages include challenges developing an accurate ontology and hiding complex IT implementation details.
Tata Consultancy Services (TCS) is an Indian multinational information technology service and consulting company headquartered in Mumbai, India. It is a subsidiary of Tata Group and has over 226,751 employees. Some key people mentioned are S. Ramadorai as Vice Chairman, Dr. Vijay Kelkar as Director, Ishaat Hussain as Director, and Phiroz Vandrevala as Director. TCS has many branches and campuses located across India in cities like Lucknow, Hyderabad, Chennai, Pune, and Kolkata.
Tata Consultancy Services (TCS) is an Indian multinational information technology service and consulting company founded in 1968, providing a wide range of IT services and software engineering. TCS operates in 46 countries with over 400,000 employees and has become the largest IT services company in India. The document provides an overview of TCS's vision, history, services, products, growth, offices globally, and opportunities for careers with the company.
13th Sep, Drupal 7 advanced training by TCS DrupalMumbai
This document provides an overview and introduction to Drupal module development. It discusses Drupal hooks like hook_menu(), hook_permission(), hook_form(), and the Entity API. It also covers creating modules, forms, variables, blocks, and interacting with the database. The event is for a Drupal Global Training Day in Mumbai, India hosted by Drupal Mumbai and Tata Consultancy Services.
Ppt 6weeks tcs i_on_summer training for b.e._b.tech._mca_2016Ashish Arora
The document outlines a 6-week or 6-month summer training program offered by TCS iON that includes 3 levels of training. Level I focuses on technology training in areas like Java, .NET, mobile apps, databases, and more. Level II involves working on minor or major projects. Level III is for project documentation and submission. Trainees will receive guidance from experienced faculty, certification from TCS iON, and the training program offers wide industry recognition.
1. Tata Consultancy Services (TCS) is a leading global IT services, consulting and business solutions organization with over 335,000 employees worldwide.
2. TCS believes in maintaining an open and collaborative work culture for employees and providing benefits such as training programs, medical insurance, loans, and cultural activities.
3. TCS uses a rigorous selection process for recruiting and promoting employees that includes written tests, interviews, presentations and assessing leadership qualities at different levels from entry-level to top management.
The document discusses the importance of predictive analytics for business agility. It outlines how predictive analytics can help businesses address challenges in areas like customer satisfaction, consumer behavior, pricing, and inventory management. The document also provides examples of how TCS has helped clients in various industries like retail, banking, manufacturing, and media leverage predictive analytics to improve outcomes in domains such as marketing ROI, risk assessment, demand forecasting, and customer churn. TCS's analytics as a service model aims to provide an integrated and global team to help clients derive value from analytics.
Design of Industrial Automation Functional Specifications for PLCs, DCs and S...Living Online
This manual will be useful to both specifiers and implementers providing a theoretical grounding for preparing a control system functional specification for implementation on Industrial control systems consisting of PLC (Programmable Logic Controllers), HMI (Human Machine Interfaces / SCADA devices) or DCS (Distributed Control Systems).
FOR MORE INFORMATION: http://www.idc-online.com/content/design-industrial-automation-functional-specifications-plcs-dcss-and-scada-systems-15
This document is a functional specification for a project with the purpose of describing the functions and scope. It includes sections for an introduction, scope overview, and a list of functions. The introduction defines the purpose and references other documents. The scope overview describes the project and lists any constraints or assumptions. The list of functions section defines each function with a description, process flow, and field details.
This document discusses Tata Consultancy Services' (TCS) business model and strategies between 2007-2008 and 2013-2014. It analyzes TCS' business model using PESTEL analysis and external factor evaluation matrices for the two time periods. The analysis shows that TCS has strategically built advantages related to cost efficiency and service efficiency over time through business choices that created interrelated positive consequences and sustained competitive advantages.
TCS offers IT and IT-enabled consulting services globally using their Global Network Delivery Model. They see growth opportunities in the growing IT services market where they have a small market share. Their strategy is to expand geographically, increase industry coverage, and deepen client relationships through innovation, acquisitions, and non-linear business models like software products and platform-based services. Key elements are customer-centricity, a full services portfolio, the Global Network Delivery Model for seamless global delivery, and strategic acquisitions.
The document provides an overview of Cadbury Schweppes PLC, including its operations strategy, processes, human resource management, capacity planning, lean systems, supply chain design, and location planning. Cadbury originated in Birmingham in 1824 and has since expanded globally, operating in over 60 countries with around 65,000 employees. It faces competition from other large confectionery companies and must manage various constraints in its business operations.
This report analyzes the IT industry in India and Tata Consultancy Services' (TCS) business strategy. It provides an overview of the growing Indian IT industry and its competitive advantages. It then performs a PESTLE analysis of the external environment, Porter's Five Forces analysis, and a SWOT analysis of the industry. For TCS, it describes the company's profile, financial performance, resources, service offerings, and growth strategies. It analyzes TCS' strategies using the BCG matrix and provides recommendations to strengthen TCS' position, such as focusing on higher value services and intellectual property.
1) Tata Consultancy Services (TCS) is a global IT services company and India's largest exporter, with revenues of $7.21 billion in 2011.
2) TCS aims to be among the top 3 IT services companies worldwide through a culture of accountability and delivering certainty to customers.
3) TCS has strong ethics and compliance programs, including oversight by an Ethics and Compliance Committee and designation of an Ethics Counselor.
Tata Consultancy Services (TCS) is the largest Indian multinational information technology services and consulting company. It has over 200,000 employees across 47 countries. TCS aims to be a top 10 global IT company by focusing on innovative solutions, strong vertical expertise, and a wide global presence across industries like banking, telecom, manufacturing and more. In the past 2 years, TCS has grown revenues by 32% and profits by 62% through strategies like expanding in emerging markets and new technologies like cloud computing.
TCS is one of India's largest private sector employers with over 250,000 employees. The document discusses TCS's compensation strategy, including its components such as basic wages, incentives, and employee benefits. It also describes TCS's EVA compensation model which measures operating and financial performance to determine employee compensation. Surveys show high levels of employee satisfaction at TCS compared to industry averages, particularly regarding training, appraisal systems, and overall satisfaction. TCS uses a combination of fixed pay and variable pay linked to performance to incentivize employees.
The document summarizes different types of functional strategies that support corporate and business unit objectives. It discusses marketing, research and development, human resource management, financial, and information management strategies. The strategies focus on maximizing productivity of resources within each functional area to provide competitive advantages.
Tata Consultancy Services (TCS) is one of the leading global IT services, consulting and business solutions organizations. It aims to be among the top 10 global IT companies by 2010 in terms of revenue, profitability, customers and technology leadership. TCS provides innovative consulting, IT solutions and services across industries, with a workforce of over 74,000 professionals spread across many global delivery centers. It helps customers optimize business processes and create resilient IT infrastructure to ensure faster business results. Some of its key competitors include Infosys, IBM, Wipro and Cognizant.
This low level design document outlines the tax payer registration functionality with details of the navigation flow, UI implementation, client and server side validations, components design, data design with key tables and access levels, and testing approach. It provides developers with a reference to develop the system with minimal effort.
This document provides a technical design specification for a process implementation at Company ABC. It includes an overview of the process with definitions of terms and acronyms. Process models are presented for the main and sub-processes along with descriptions. The scope outlines what is included, such as the technical solution, error handling, security, logging, and external interactions. Out of scope items are also listed.
CMGT/410 v19
Business Requirements Template
CMGT/410 v19
Page 2 of 14Business Requirements TemplateHow to Use This Document
This document is a template for creating a Business Requirements Document (BRD); it includes instructions and examples for guidance. As you complete your BRD using the template, only include sections pertinent to your project.Table of Contents
How to Use This Document1
Table of Contents1
1.Executive Summary2
1.1Project Overview2
1.2Purpose and Scope of this Specification2
2.Product/Service Description3
2.1Product Context3
2.2User Characteristics3
2.3Assumptions3
2.4Constraints3
2.5Dependencies3
3.Requirements4
3.1Functional Requirements4
3.2User Interface Requirements5
3.3Usability5
3.4Performance6
3.4.1Capacity6
3.4.2Availability6
3.4.3Latency6
3.5Manageability/Maintainability6
3.5.1Monitoring6
3.5.2Maintenance6
3.5.3Operations7
3.6System Interface/Integration7
3.6.1Network and Hardware Interfaces7
3.6.2Systems Interfaces7
3.7Security8
3.7.1Protection8
3.7.2Authorization and Authentication8
3.8Data Management8
3.9Standards Compliance9
3.10 Portability9
4.User Scenarios/Use Cases9
5.Deleted or Deferred Requirements9
6.Requirements Confirmation/Stakeholder Sign-Off10
Appendices11
Appendix A: Definitions, Acronyms, and Abbreviations11
Appendix B: References11
Appendix C: Requirements Traceability Matrix12
Appendix D: Organizing the Requirements131. Executive Summary
1.1 Project Overview
Describe this project or product and its intended audiences, or provide a link or reference to the project charter.
1.2 Purpose and Scope of this Specification
Describe the purpose of this specification and its intended audience. Include a description of what is within the scope what is outside of the scope of these specifications.
Example:
In Scope
This document addresses requirements related to Phase 2 of Project A:
· Modification of Classification Processing to meet legislative mandate ABC
· Modification of Labor Relations Processing to meet legislative mandate ABC
Out of Scope
The following items in Phase 3 of Project A are out of scope:
· Modification of Classification Processing to meet legislative mandate XYZ
· Modification of Labor Relations Processing to meet legislative mandate XYZ
(Phase 3 will be considered in the development of the requirements for Phase 2, but the Phase 3 requirements will be documented separately.)2. Product/Service Description
In this section, describe the general factors that affect the product and its requirements. This section should contain background information, not state specific requirements (provide the reasons why certain specific requirements are later specified).
2.1 Product Context
How does this product relate to other products? Is it independent and self-contained? Does it interface with a variety of related systems? Describe these relationships or use a diagram to show the major components of the larger system, interconnections, and external interfaces.
2.2 User Characteristics
Create gen.
Super applied in a sitecore migration projectdodoshelu
This document describes using a business process model and ontology for a Sitecore migration project. It discusses key Sitecore concepts like items, templates, fields and presentation components. An ontology is proposed to model Sitecore concepts and help answer competency questions during content creation. Integrating the business process model with SUPER could provide semantic tools and services to help manage the migration, increasing flexibility and reducing costs and time. Potential disadvantages include challenges developing an accurate ontology and hiding complex IT implementation details.
The document provides an architectural overview of the Center Management System. It includes 4 views: use case, logical, process, and deployment. The logical view focuses on packages, flow diagrams for key use cases like login, student registration and enrollment, and architecture patterns. The architecture uses a layered pattern with packages for presentation, business logic, and data access.
Appendix b functionaldesignphasebusinessequirementsdocument021805Udaya Kumar
This document outlines the business requirements for a new application. It includes sections for project overview, assumptions and scope, current process workflows, a business requirements matrix listing over 50 numbered requirements across various categories, acceptance criteria, and an issues log. The requirements matrix establishes priorities for the requirements and provides descriptions and comments. The document also identifies business owners, signatories, and a revision history.
This document is a template for a USS GM NACCL Requirements Specification. It provides instructions and examples for documenting requirements for a product or service, including sections for an executive summary, product description, requirements, user scenarios, and appendices. The format can be tailored to suit different projects, and the requirements can be organized in the most effective way.
PURPOSE of the project is Williams Specialty Company (WSC) reque.docxamrit47
The document provides a design specification for a business automation application requested by Williams Specialty Company. The application will allow employees to automate customer service, inventory, and quality control processes. It will include features to create, modify, and store customer orders, access a database, create and save internal communications, validate orders, and mark orders as complete. The design specification defines the system and its major functions. It describes using an Oracle or SQL database and constraints of conforming to the company's Windows infrastructure. It provides data modeling, data flow diagrams, a program architecture diagram, and detailed design sections for each application component.
According to an article published in Forbes in 2010, the 10 essent.docxnettletondevon
The document discusses the requirements for a project that involves analyzing the layout and effectiveness of websites for different product types based on 10 essential elements of an effective website. It provides 4 questions to evaluate the overall effectiveness of the websites visited, requiring a minimum 2-page double-spaced response referencing additional sources in APA style.
The document mentions additional transformation support was added in Advanced Document Transformation Services 6.7 but does not provide details on what specific additional transformations were supported.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introduction, purpose, project summary, requirements definition, considerations, and a document change log. The project summary section provides an executive overview with objectives, scope, references, and outstanding issues. The requirements definition section outlines goals, usability requirements, security requirements, business questions, data requirements, and design constraints. The purpose is to help define and document the project scope and requirements.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introducing the project, stating its purpose and objectives, defining requirements, and considering constraints. The document was created by Rasananda Behera on February 11, 2016 as an initial version to standardize how requirement specifications are documented for financial data warehouse projects at CUNA Mutual Group.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introducing the project, stating its purpose and objectives, defining requirements, and considering constraints. The document was created by Rasananda Behera on February 11, 2016 as a version 1.0 template for financial data warehouse specification documents.
This document discusses software product lines and component-based software architecture. It defines a software product line as a set of software systems that share common features to satisfy market needs. Product lines allow for significant reuse of common assets across products. The document also discusses challenges like architectural mismatch that can occur when integrating components, and techniques for avoiding, detecting, and repairing mismatches. It frames architecture development as an ongoing business process and discusses how commercial components impact architectural design decisions.
The document provides instructions for a software design specification (SDD) project. It asks the student to design an SDD for a bed and breakfast software system based on previous analysis models. The SDD should include:
1) An updated data model and architectural context diagram from the previous project
2) A software interface description, including a graphical user interface design and information flow description
3) An updated data flow diagram to illustrate the major processes to implement functionality
The SDD will form the basis for subsequent projects to develop and test the software system.
This document provides a template for a Software Requirements Specification (SRS) document. It outlines the typical sections included in an SRS, including an introduction, overall description of the system, specific requirements, and additional sections for change management, approvals, and supporting information. The template offers explanatory comments and examples of the types of information that would be included in each section to help specify the requirements for a software project.
The document discusses software configuration management (SCM), including its definition, need, elements, roles and access levels, and version numbering. SCM involves managing project items like software, code, and artifacts in a structured way, securing them for privileged users only, and controlling modifications. It establishes configuration identification, control over elements like libraries and access, and change management.
Similar to Tcs functional spec all rounds (final) (20)
This document discusses user experience design documentation capabilities including competitive analysis, concept modeling, content audits, experience mapping, functional specifications, gap analysis, information architectures, mental modeling, persona development, user research, site heuristics reviews, user scenarios, process flows, and wireframes. It provides an example of documentation for finding and friending other users on a social platform, including exploring recommended users, searching, accepting or declining friend requests, and removing other users as friends. The example discusses notification of friend requests and the access privileges associated with friend status.
This document provides a draft discussion guide for usability testing of the Tourism WA website. It outlines a general introduction, four scenarios to test participants' ability to navigate and find information on the site, and issues to consider throughout testing. The scenarios include finding climate/weather information, whale watching in Rottnest, travel information like airports, and getting personal advice. The guide aims to understand participants' expectations, navigation behaviors, and feedback on the site's design and content.
The document provides a test script for user testing of a Tourism BC Australian website prototype. It outlines segments of target Australian travelers, including keen skiers, older travelers seeking once-in-a-lifetime experiences, and independent travelers. The script details tasks for participants to complete on the prototype website to evaluate usability and usefulness for an Australian audience. Questions are provided to gather user feedback on site impressions, information finding, and booking travel products.
00. twa recruitment brief corporate 2nd round.v.02Jef Davis
This recruitment brief provides instructions for recruiting participants for user testing of Tourism Western Australia's new corporate website. It outlines the objectives of testing the design, navigation, and content of the prototype website. It specifies recruiting 8 participants total in Perth and Sydney between April 28 - May 4, with 2 from the tourism industry, 2 investors, 1 government representative, and 2 media professionals. Each 1.5 hour session will evaluate the usability of the prototype website with one facilitator and one participant.
This recruitment brief provides guidelines for recruiting participants for user testing of Tourism Western Australia's new consumer website. A total of 12 participants are needed over two rounds of testing in March and April. Participants should represent three target user groups: self-challengers, comfort adventurists, and grey nomads. The document specifies demographic details, incentives, location, and dates for the one-on-one 1.5 hour testing sessions, which will evaluate the website's naming, navigation, usability and ability to meet user needs.
The document provides a test script for user testing of a Tourism WA website prototype. It outlines a two-part user testing process: 1) Introduction and signing release forms, and 2) Questions to understand the test participant's internet usage, travel habits, and familiarity with Western Australia. The test aims to understand user needs to inform development of an Australian version of an overseas tourism association's website. Participants will explore mockup pages and provide feedback on the design and usefulness.
This document appears to be from a usability study where participants were asked to complete tasks on the American Standard and Lennox HVAC websites. It records information about each participant, the tasks they were assigned, which pages/sections they visited on each site, and their feedback and impressions. Key details include participant demographics, their level of research for purchases, which site sections they visited to learn about different products/issues, and their opinions on layout, navigation, content and comparisons between the two sites.
1. Participants had mixed reactions to the American Standard and Lennox websites. While some liked the organized layout of the American Standard site and search feature, others felt the Lennox site was cluttered.
2. For learning about products, most found the American Standard site easy to navigate but disliked the first product page layout. Participants preferred the Lennox product summary page and inclusion of energy ratings and prices.
3. Locating troubleshooting information differed between sites - most easily found it on the American Standard site but all struggled on Lennox. Overall, participants wanted more intuitive interfaces and consistent information across pages.
The document summarizes consumer feedback from testing the Trane and Carrier HVAC websites. For Trane, consumers liked the clean layout but had trouble finding the troubleshooting section. They wanted easier product comparisons, pricing, and more noticeable ways to locate a dealer. For Carrier, consumers preferred the product comparison format but had questions about the rating system. In general, consumers wanted clearer terminology, more competitive comparisons, and pricing information on manufacturer websites.
This document outlines a scope matrix for updating an Australian tourism website. It lists 34 proposed changes and updates to the website, including redesigning pages like the homepage and about page, adding new pages for seasonal information and suggested itineraries, and updating existing pages like those covering regions, activities, and travel information. Many of the proposed changes aim to tailor the website more specifically to Australian travelers by including Australian terminology, currency, and legal/privacy policies. The document assigns priorities and determines whether each proposed change is in scope or requires new content.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Tcs functional spec all rounds (final)
1. Trane.com Commercial Redesign
Phase I
Functional Specification – All Delivery Rounds
final
January 29, 2015
Author: Bryan Keller
Confidential
S
2. Functional Specification – All Rounds – final TCS Redesign Phase I
Table of Contents
February 27, 2007 i Confidential
3. Functional Specification – All Rounds – final TCS Redesign Phase I
TRANE.COM COMMERCIAL REDESIGN.....................................................................................................................1
PHASE I.......................................................................................................................................................................... 1
Functional Specification – All Delivery Rounds.............................................................................................................1
final 1
1 DOCUMENT STANDARDS.......................................................................................................................................... 1
1.1 Scope....................................................................................................................................................................... 1
1.1.1 Non-Goals.................................................................................................................................................. 1
1.1.2 Content Sections........................................................................................................................................1
1.2 Templates................................................................................................................................................................ 1
1.2.1 Dynamic Templates...................................................................................................................................1
1.2.2 Static Templates........................................................................................................................................1
1.2.3 Naming Convention...................................................................................................................................1
1.3 Recommendation Changes.....................................................................................................................................2
1.4 Document Conventions............................................................................................................................................ 2
2 TECHNICAL REQUIREMENTS....................................................................................................................................3
2.1 Content Management Tool......................................................................................................................................3
2.2 Browser Compatibility.............................................................................................................................................. 3
2.3 Flash........................................................................................................................................................................ 3
2.4 JavaScript................................................................................................................................................................ 3
3 BEST PRACTICES: USABILITY..................................................................................................................................4
3.1 Resizable text.......................................................................................................................................................... 4
3.2 Image “Alternate” text.............................................................................................................................................. 4
3.3 Meta Data................................................................................................................................................................ 4
3.4 Dynamic Layers....................................................................................................................................................... 4
3.5 Link Styles............................................................................................................................................................... 4
3.6 Submit Form Buttons............................................................................................................................................... 4
3.7 PDF links................................................................................................................................................................. 4
4 CATEGORY NAMING................................................................................................................................................... 5
5 CONTENT TYPES........................................................................................................................................................ 6
5.1 DNA Managed Content............................................................................................................................................ 6
5.2 CPS Managed Content............................................................................................................................................ 6
5.3 Manually Managed Content.....................................................................................................................................6
5.4 Trane Legacy Material............................................................................................................................................. 6
5.5 Content Groups and Management...........................................................................................................................6
6 LEFT NAVIGATION FUNCTIONALITY........................................................................................................................8
7 RIGHT SIDEBAR FUNCTIONALITY............................................................................................................................9
8 TEMPLATE: D1T6DYN............................................................................................................................................... 10
8.1 Applicable Content Sections..................................................................................................................................10
February 27, 2007 ii Confidential
4. Functional Specification – All Rounds – final TCS Redesign Phase I
Version History
Date Version Author Changes
11/1/2006 draft a Bryan Keller N/A
11/15/2006 Draft c Bryan Keller Revised front-end specs for dynamic layers
February 27, 2007 iii Confidential
5. Functional Specification – All Rounds – final TCS Redesign Phase I
1 DOCUMENT STANDARDS
1.1 Scope
This document presents functional specifications for Delivery Round 1 of the redesign and enhancement of the Trane Commercial
Site (“TCS”). These specifications are non-technical in nature and only involve the way a user is meant to interact with the system, not
particular database configurations, specific graphic treatments, copy or most other technical considerations. For detailed design
information and field character limits, please refer to the Style Guide.
1.1.1 Non-Goals
This document does not present a specific technical plan for implementation of FCBi-supplied templates, nor does it specify
particular coding techniques (in most cases), browser compatibility hacks or other highly technical techniques. This document
does not provide a recommendation as to how to integrate different types of content from a technical perspective. These types
of decisions are left to eBusiness’ and FCBi developers’ discretion.
1.1.2 Content Sections
Delivery Round 1 will cover the following sections:
1.0 HVAC Systems
2.0 Building Services
3.0 Controls
4.0 Products
6.0 Training and Reference
9.0 Financing
1.2 Templates
There are really two types template deliverables described in these pages: Static and Dynamic Templates. Static templates are
created as individual pages by FCBi and do not make use of recyclable templates connected to a CMS on a field level.
1.2.1 Dynamic Templates
These are designed to be reused in the context of a CPS or DNA. These are mapped to sections and navigational levels only,
not specific pages.
1.2.2 Static Templates
These are designed for specific content pages and exist due to design requirements that are not possible in CPS or DNA.
1.2.3 Naming Convention
D = Delivery Round Number
T = Template Number
Stat = Static Content
Dyn = Dynamic Content
Example: D1T3Stat = Delivery Round 1, Template 3, Static Content
February 27, 2007 1 Confidential
6. Functional Specification – All Rounds – final TCS Redesign Phase I
1.3 Recommendation Changes
This document supersedes any earlier revisions and specifications for previous versions of the TCS functional specification. In the
event that there is a conflict between this specification and other functional requirements, the conflict must be resolved by eBusiness
and FCBi.
1.4 Document Conventions
In general this document uses screenshots combined with callouts that describe the intended functionality of the various page
elements. Screenshots are not to be used for checking the copy. It is assumed that all copy on the screenshots is out of
date, including page titles, navigational text and positioning, category naming, etc. Copy should only be included from and
proofed against the copy deck.
February 27, 2007 2 Confidential
7. Functional Specification – All Rounds – final TCS Redesign Phase I
2 TECHNICAL REQUIREMENTS
2.1 Content Management Tool
A large portion of the site must be compatible with Trane’s content management tool (“CPS/DNA”) that is currently in place. Other
sections of the site will be maintained updated periodically.
2.2 Browser Compatibility
Site must function in the following browsers:
Microsoft XP SP2: IE 6, Firefox 1.5
Windows 2000 SP2: IE 6
Macintosh 10.4 + 2: Safari (note: FCBi uses the following for testing: 10.3.6 OS, 1.2 safari, 1.5 firefox. Browser requirements
can be determined by Trane, based on evaluation of metrics).
2.3 Flash
• All Flash content is to be developed to be compatible with Flash version 7
• The homepage will be developed in both flash and non-flash versions. The non-flash version links to a page where the user
can download Flash.
2.4 JavaScript
The site is to be compatible with JavaScript either enabled or disabled. If JavaScript is disabled, a warning homepage should be
presented explaining that the site works best with JavaScript enabled.
February 27, 2007 3 Confidential
8. Functional Specification – All Rounds – final TCS Redesign Phase I
3 BEST PRACTICES: USABILITY
This section is the closest this document will get to recommending certain coding techniques. These techniques are considered best
practices for usability and web presence.
3.1 Resizable text
All of the text is resizable by the user, except of course in case of text contained in images, such as in the left navigation.
3.2 Image “Alternate” text
Wherever text appears in an image, alt tags should mirror this text, if the text is of a reasonable length. Alternate text is useful for
search engines and users with slow connection and/or images turned off, as well as users needing special accessibility.
3.3 Meta Data
Where possible, pages should include relevant keyword and description meta data in the header for indexing by search engines.
3.4 Dynamic Layers
When dynamic layers appear on top of the base layer containing regular page information (for example in navigational breakout
menus), they should close when the user clicks on the “close” link.
3.5 Link Styles
Links should always have “visited” styles so that users know if they have been to a page or not. For this site this applies to links
included in main body text and main body navigation items (not necessarily in left menu items).
3.6 Submit Form Buttons
All buttons whose function is to submit a form are activated both by a user click or hitting the ‘return’ or ‘enter’ key.
3.7 PDF links
Links to PDFs should open the PDF in a new window in most cases.
February 27, 2007 4 Confidential
9. Functional Specification – All Rounds – final TCS Redesign Phase I
4 CATEGORY NAMING
FCBi has adjusted the naming and organization of a number of categories. Below is a grid mapping new top-level categories and source
categories.
These category names are subject to change.
New Category Name Old Category Name Description/Notes
HVAC Systems Systems
Building Services Building Services
Controls Products -> Controls &
Automation
This becomes a top-level category and is renamed.
Products Products
Parts & Supplies Parts and Supplies
Educational Resources Bookstore, Training, Engineers
Newsletter
These three top-level categories have been merged into one.
Featured Case Studies Case Studies
Energy, IAQ & The
Environment
Industry Issues
Financing Financing Category naming remains the same. Sub categories are reorganized.
Design & Analysis Tools Products -> Software This is renamed and becomes a top-level category
Explore by [Industry] N/A New: points to different pages for each industry
Explore by [Building Type] N/A New: points to different pages for each building type
February 27, 2007 5 Confidential
10. Functional Specification – All Rounds – final TCS Redesign Phase I
5 CONTENT TYPES
Because of the legacy content management systems that are in place, as well as flat-file, manually updated material and HTML legacy
material, content falls into several distinct technical buckets.
5.1 DNA Managed Content
This content lives in the DNA tool and includes Parts & Supplies, Training & Reference and Financing.
5.2 CPS Managed Content
This content live in any number of CPS instances including Products, Controls, Design & Analysis Tools, and Find Classes (under
Training & Reference).
5.3 Manually Managed Content
This is content that is custom built by FCBi and exists outside of any CMS. Updates to this content are coordinated by Trane
marketing and handled by FCBi and eBusiness. This includes HVAC Systems, Building Services, Featured Solutions, High
Performance Building Issues, Explore by [Industry] and Explore by [Building Type]
5.4 Trane Legacy Material
This includes older, flat-file content that is mainly technical and not managed inside of any CMS. This content is to be identified by
FCBi and a plan for implementing a “Trane Legacy” template will be provided.
5.5 Content Groups and Management
New Top Level Category Managing Application Description/Notes
HVAC Systems Manual
Building Services Manual
Controls CPS Part of Products instance. Renders on front-end in separate top-level category
Products CPS Renders all sub-levels on front end except for Controls which is its own top-level
category
Parts & Supplies DNA
Educational Resources DNA
Featured Case Studies Manual
Energy, IAQ & the Manual
February 27, 2007 6 Confidential
11. Functional Specification – All Rounds – final TCS Redesign Phase I
Environment
Financing Manual
Design & Analysis Tools CPS CPS instance is called C.D.S.
Explore by [Industry] Manual
Explore by [Building Type] Manual
Country Sales Offices DNA
About Trane Landing page: manual
Sub-pages: DNA
News Room CPS
Search eBusiness’ discretion
February 27, 2007 7 Confidential
12. Functional Specification – All Rounds – final TCS Redesign Phase I
6 LEFT NAVIGATION FUNCTIONALITY
Not for copy or element order
February 27, 2007 8 Confidential
Top-Level Categories
These link labels are fixed images. Alt
tags use image text
Second-Level Categories
display automatically when user clicks on top-
level category
HTML Text
Can be populated by CMS
Remain in place, highlighted, and clickable as
user navigates 2nd
level down.
Drop Down Menus
Jump to landing pages for Industry and Building
Type
Drop Menus Label
Display as image. Alt tag uses image text.
13. Functional Specification – All Rounds – final TCS Redesign Phase I
7 RIGHT SIDEBAR FUNCTIONALITY
February 27, 2007 9 Confidential
Contact a Sales Engineer
HTML Text
persistent element.
always displays except where
differently noted
Sidebar Header Names
HTML text
selectable in CMS
CMS associates icons
REQUIRED element in sidebar box
Sidebar Descriptions
HTML text
can be entered by user in CMS
system(s)
OPTIONAL element if links
exist
REQUIRED element if no links
exist
Sidebar Links
Minimum # of links if Required: 1
Maximum # of Links: 10
OPTIONAL element if Description
exists
REQUIRED element if description
does not exist
Display below description, if
exists
Right Sidebar Boxes
stacked vertically below
persistent “Contact a Sales
Engineer” object
OPTIONAL element
Maximum Boxes: 4
14. Functional Specification – All Rounds – final TCS Redesign Phase I
8 TEMPLATE: D1T6DYN
Delivery Round 1, Template 7, Dynamic Content
8.1 Applicable Content Sections
3.0 Controls, 4.0 Products
8.2 Navigational Levels
Top Level
February 27, 2007 10 Confidential
Page Header
HTML Text
Descriptive Text
HTML Text
Copy source: section
description
Navigation Buttons
HTML Text
Max. lines of text per
button: 1
Included Static Content
Displays contents of
template D1T7Stat,
matched with relevant
copy and image.
15. Functional Specification – All Rounds – final TCS Redesign Phase I
8.3 Dynamic Breakout Layer
February 27, 2007 11 Confidential
Title
HTML Text
Uses Link label from
button
On click, close layer
Close link
On click, closes
breakout layer
Breakout Description
Exposes text from
category description
field
OPTIONAL element
“Grandchild” links
Exposes page labels 2
levels down, if they exist
Breakout layer
Only exists if there is
description and/or
“grandchild” objects
Link: “See all [category name]”
Last Link
Last link is “See all
[category name]”
Links to child category
16. Functional Specification – All Rounds – final TCS Redesign Phase I
9 TEMPLATE: D1T11DYN
Delivery Round 1, Template 12, Dynamic Content
9.1 Applicable Content Sections
3.0 Controls, 4.0 Products
9.2 Navigational Levels
Section contains 4 or more levels: 2nd
level from top through to 3rd
level from bottom.
Less than 4 levels: templates D1T10DYN and D1T9DYN supersede this template.
February 27, 2007 12 Confidential
Description
Uses copy from
category description
in CPS
Sub Category Nav
Full width nav buttons
Max. lines per button:
1
Top Level Header
HTML Text
Displays top level
category
Current Page Header
HTML Text
Displays current
category name
17. Functional Specification – All Rounds – final TCS Redesign Phase I
10 TEMPLATE: D1T10DYN
Delivery Round: 1, Template 10, Dynamic Content
10.1 Applicable Content Sections
3.0 Controls, 4.0 Products
10.2 Navigational Level
2nd
Level from bottom
February 27, 2007 13 Confidential
Top Level Header
HTML Text
Displays top level
category
Current Page Header
HTML Text
Displays current
category name
Description
Uses copy from
category description
in CPS
Category Image
Displays image
associated with
current category
Child Category Links
18. Functional Specification – All Rounds – final TCS Redesign Phase I
11 TEMPLATE: D1T9DYN
Delivery Round 1, Template 9, Dynamic Content
11.1 Applicable Content Sections
3.0 Controls, 4.0 Products
11.2 Navigational Level
Bottom level
February 27, 2007 14 Confidential
Product/Control Image
Displays image
associated with
current product or
control
Line drawing and text
are contained in image
Sibling Products Drop
Down
If sibling products exist,
standard browser drop
down provides text
links to sibling
products
Top Level Header
HTML Text
Displays top level
category
Current Page Header
HTML Text
Displays current
category name
Product Copy
HTML text
Displays copy
associated with
current product or
control
19. Functional Specification – All Rounds – final TCS Redesign Phase I
12 TEMPLATE: D1T8DYN
12.1 Applicable Content Section
3.2.2 (Tracer Summit v17) only
12.2 Navigation Level
Not applicable
February 27, 2007 15 Confidential
Top Level Header
HTML Text
Displays top level
category
Current Page Header
HTML Text
Displays current
category name
Tracer Summit Image
Line drawing and text
are displayed as
image
Tracer Summit Copy
HTML Text
Displays copy
associated with
Tracer Summit
control
Child Links
HTML Text
Displays child links
On click, links open
breakout layers.
20. Functional Specification – All Rounds – final TCS Redesign Phase I
12.3 Breakout Layer
February 27, 2007 16 Confidential
Header
HTML Text
Child control name
On click, closes layer
Close Box
Dynamic layer closes on
click
If user clicks anywhere
else on page, dynamic
layer closes
Summary
Displays summary of
child control
Entire summary and
“MORE” link is linked
to child page.
21. Functional Specification – All Rounds – final TCS Redesign Phase I
13 STATIC TEMPLATES
Static content templates are mapped to content in the copy deck using site map numbering. These templates are scripted to allow
insertion of custom content.
Template Number Page # Working Page Name
D1T1Stat 1.1 Chilled Water to Air Systems
1.2 Refrigerant to Air Systems
D1T2Stat 1.3 Earthwise Design Approach
1.4 Systems Integration
1.4.1 Integrated Comfort Solutions
D1T3Stat 2.0 Building Services
D1T4Stat 2.1 Plan & Design
2.2 Install
2.3 Operated and Maintain
2.4 Restore and Modernize
D1T5Stat 2.3.1 National Account Service
D1T7Stat 3.0 Controls (bottom middle column content)
4.0 Products (bottom middle column content)
D1T12Stat 9.0 Financing
D1T13Stat 6.1.1 Find Classes
February 27, 2007 17 Confidential
22. Functional Specification – All Rounds – final TCS Redesign Phase I
14 DYNAMIC TEMPLATES
Template Number Page # Working Page Name
D1T6Dyn 3.0, 4.0 [Products and Controls top level pages]
D1T7Dyn 3.0 4.0 [Products and Controls content section below the child links]
D1T8Dyn 3.2.2 Tracer Summit V17
D1T9Dyn 3.x.x.x, 4.x.x.x [bottom level Products and Controls pages]
D1T10Dyn 3.x.x, 4.x.x [2nd
from bottom level Products and Controls pages]
D1T11Dyn 3.x, 4.x [2nd
level from top Products and Controls pages]
D1T15Dyn 6.x, etc. Standard sub-page template with no child links
D1T11bDyn 6.0, etc. Educational Resources and standard sub-pages with child links
February 27, 2007 18 Confidential
23. Functional Specification – All Rounds – final TCS Redesign Phase I
15 APPENDIX
15.1 Financing Deliverables (section 9.0)
As per the recent agreement, Financing templates and copy will be delivered as part of Round 1. Subsequent drafts of this documents
will include discussion of these templates.
15.2 Training and Reference Deliverables (section 6.0)
Additionally Training and Reference template specifications will be included in subsequent drafts of this document.
15.3 Parts (section 5.0)
Templates and copy of this section have been pushed back to Delivery Round 2.
February 27, 2007 19 Confidential
24. Functional Specification – All Rounds – final TCS Redesign Phase I
TEMPLATE: D2T1STAT
Delivery Round 2, Template 1, Static Content
15.4 Applicable Content Sections
0.1 About Trane
February 27, 2007 20 Confidential
Flash Video w/Control
To be provided by FCBi
25. Functional Specification – All Rounds – final TCS Redesign Phase I
16 TEMPLATE: D2T2STAT
Delivery Round 2, Template 2, Static Content
16.1 Applicable Content Sections
0.1.2 History
February 27, 2007 21 Confidential
Flash Module
To be provided by FCBi
26. Functional Specification – All Rounds – final TCS Redesign Phase I
17 TEMPLATE: D2T3DYN
Delivery Round: 2, Template 3, Dynamic Content
17.1 Applicable Content Sections
0.1.4 Client List
February 27, 2007 22 Confidential
Client Entries
Client Name (company) on one
line
Link to client case study (if
exists) on next line. Link label
is case study name
Sorting/Columns
Clients are listed alphabetically,
ascending, by Client Name
Clients are listed sequentially
vertically
Equal number of clients per
column. 3rd
column can
contain fewer items.
27. Functional Specification – All Rounds – final TCS Redesign Phase I
18 TEMPLATE: D2T4STAT
Delivery Round 2, Template 4, Static Content
18.1 Applicable Content Sections
0.5 Advanced Search
February 27, 2007 23 Confidential
Advanced Search
Fields
Fields are to be
processed by the
search engine
collectively
28. Functional Specification – All Rounds – final TCS Redesign Phase I
19 TEMPLATE: D2T4BSTAT
Delivery Round 2, Template 4b, Static Content
19.1 Applicable Content Section
0.6 Search Literature
February 27, 2007 24 Confidential
Search Literature
Fields
Search terms passed to
eLibrary search
engine, collectively.
29. Functional Specification – All Rounds – final TCS Redesign Phase I
20 TEMPLATE: D2T5STAT
Delivery Round 2, Template 5, Dynamic Content
20.1 Applicable Content Section
0.11 Search Results - TCS, 0.12 Search Results – Literature
February 27, 2007 25 Confidential
Page Title
Indicates which
repository was
searched, TCS or
Literature
Keywords
User-entered search
terms are presented
here.
Link to Alternate
Search
Keywords are linked to
search results for
alternate repository.
Refine Search Link
Links to search form
associated with
current search results
(Site Search or
Literature Search)
30. Functional Specification – All Rounds – final TCS Redesign Phase I
20.2 Search Feedback
20.2.1 “Yes” submission
Page reloads with current search results and “Thank You” copy below form (see Search Copy Deck)
20.2.2 “No” submission
Browser loads Search Feedback page (0.13) with “No” response copy (see Search Copy Deck)
February 27, 2007 26 Confidential
“Yes” Submission Copy
If the user submits a “Yes”
answer, page reloads with
current search results,
with “Yes” copy here (see
copy deck).
31. Functional Specification – All Rounds – final TCS Redesign Phase I
21 TEMPLATE: D2T6DYN
Delivery Round 2, Template 6, Dynamic Content
21.1 Applicable Content Section
0.10 Search Results – Both
21.1.1 No Results
If there are no results returned for a repository (Site or Literature), the following message is displayed instead of search results
February 27, 2007 27 Confidential
Dual Repository
Search Results
Top 5 results from each
repository (site and
literature)
Search Results
Page/Document name
is linked to
page/document
Summary displays first
250 characters of
page/document
returned
URL is linked to
page/document below
summary text
32. Functional Specification – All Rounds – final TCS Redesign Phase I
and “more results…” link: “No matches found.”
February 27, 2007 28 Confidential
33. Functional Specification – All Rounds – final TCS Redesign Phase I
22 TEMPLATE: D2T7DYN
Delivery Round 2, Template 7, Dynamic Content
22.1 Applicable Content Section
10.x Design & Analysis Tools – 2nd
Level
February 27, 2007 29 Confidential
Links to Child Pages
34. Functional Specification – All Rounds – final TCS Redesign Phase I
23 TEMPLATE: D2T8DYN
Delivery Round 2, Template 8, Dynamic Content
23.1 Applicable Content Section
10.x.x Design & Analysis Tools – bottom level
February 27, 2007 30 Confidential
Download Links
If downloads related to
software product are
available, they are
rendered on the page.
Links are primarily
sorted by type,
updates then demos.
Secondary sort: date,
most recent to least
recent
35. Functional Specification – All Rounds – final TCS Redesign Phase I
24 TEMPLATE: D2T9DYN
Delivery Round 2, Template 9, Dynamic Content
24.1 Applicable Content Section
10.3.2 Online CAD Templates
February 27, 2007 31 Confidential
Tabs
Tabs link to CAD pages
for different products
types
CAD Template Links
Product Illustrations
linked
Product Name linked
Number of available
templates displayed,
unlinked
36. Functional Specification – All Rounds – final TCS Redesign Phase I
25 TEMPLATE: D2T10DYN
Delivery Round 2, Template 10, Dynamic Content
25.1 Applicable Content Section
10.3.2.x Online CAD Templates – Download Page
25.1.1 “Options Not Selected” JavaScript Alert Box
If the user has not made a selection for one of the drop down menus, a JavaScript alert box is displayed with the following
February 27, 2007 32 Confidential
Unit Specifications
Dropdowns are populated by
product information in db
“Select another Product Line”
links to Online CAD
Templates page (10.3.2)
Available Downloads
Upon form submission, this
page data is displayed.
37. Functional Specification – All Rounds – final TCS Redesign Phase I
message: “Please indicate the following Unit Specification[s]: [Specification name], [Specification name], [etc]”. Browser
focuses on first drop down menu that requires selection.
25.1.2 JavaScript Confirm Alert Box
On user click on CAD template link system prompts user with JavaScript confirm alert box with the following copy:
”Terms of Use
Trane, in offering the Trane Product Templates, accepts no responsibility or liability: for any use made of the Product
Templates including any modification thereto made by the user, for the design of buildings and related systems made using
the Product Templates, or for the accuracy of the Product Templates or any data resulting from the use thereof . While Trane
strives to ensure that its Product Templates are accurate, this accuracy is not guaranteed. The user is responsible to review
the Product Template and to determine if use of the Product Template is appropriate to and meets the requirements of the
user's application. In accordance with its policy of continuous improvement, Trane reserves the right to modify its Product
Templates at any time without notice. Trane makes no warranty whatsoever, express or implied and including, but not limited
to, any warranty of merchantability or fitness for a particular purpose with respect to the Trane Product Templates or their use
and in no event shall Trane be liable for any incidental or consequential damages relating to such Product Templates or their
use.
I accept these Terms of Use:”
25.1.2.1 User Click “Yes”
System initiates CAD Template download
25.1.2.2 User Click “No”
Confirm Alert box disappears, no download, page redirect, or reload
February 27, 2007 33 Confidential
38. Functional Specification – All Rounds – final TCS Redesign Phase I
26 TEMPLATE: D2T11STAT
Delivery Round 2, Template 11, Static Content
26.1 Applicable Content Section
10.8 Design & Analysis Tools - Online Order Form
26.1.1 Form Submit: Required Fields Validation
February 27, 2007 34 Confidential
Help Content
Help content is displayed in
dynamic layers
Reformatted Form Data
Current form:
https://www.trane.com/commercial/software/cds_order
_admin_s.asp
Software Selection Grid
39. Functional Specification – All Rounds – final TCS Redesign Phase I
JavaScript checks for at least one product ordered, as well as all required fields (fields denoted with red asterisks).
26.1.1.1 Missing Required Field
JavaScript Alert displayes the following message: “Please enter the required information: [field name], [field name],
[etc.]” On user click on “OK” button, browser focuses cursor on first required field left blank.
26.1.1.2 No product ordered
JavaScript Alert displays the following message: “You have not selected a product to order. Please select the
product(s) that you wish to order.”
26.1.2 Cancel
If user clicks the cancel button, browser redirects to Software landing page
26.1.3 New Software Purchase option button
On page load, this option button is selected by default. All fields including the software selection grid are loaded.
26.1.4 License Renewal option button
Browser reloads form without software selection grid (see current form:
https://www.trane.com/commercial/software/cds_order_admin_s.asp).
26.1.4.1 Customer ID becomes required field
Red asterisk appears as last character of fields label “Customer ID”. Form validation checks for Customer ID as well
as fields required for New Software Purchase. Form validation functions as indicated in requirement 17.1.1.1
26.1.4.2 Backend Identifies Customer Software Renewal
As per current business rules and software functionality, the backend identifies the customer, and processes renewal.
26.1.5 Form Process Error Messages
All current error messages (unknown customer ID, invalid financial information, etc.) are handled using current system rules
and output. System output uses site design and styles associated with this redesign.
February 27, 2007 35 Confidential
40. Functional Specification – All Rounds – final TCS Redesign Phase I
27 TEMPLATE: D2T12STAT
Delivery Round 2, Template 12, Static Content
27.1 Applicable Content Section
8.0 Energy, IAQ & the Environment
February 27, 2007 36 Confidential
41. Functional Specification – All Rounds – final TCS Redesign Phase I
28 TEMPLATE: D2T13DYN
Delivery Round 2, Template 13, Dynamic Content
28.1 Applicable Content Section
7.0 Featured Case Studies
February 27, 2007 37 Confidential
Case Studies by Category
First three are displayed,
alphabetically, ascending
Highlighted Case Study
HTML layer highlights
noteworthy case study.
Content for Round 1 to be
decided with case study
delivery. Please use lorem
ipsum for development
purposes.
42. Functional Specification – All Rounds – final TCS Redesign Phase I
29 TEMPLATE: D2T14DYN
Delivery Round 2, Template 14, Dynamic Content
29.1 Applicable Content Section
7.x Featured Case Studies – 2nd
Level
February 27, 2007 38 Confidential
2 Column Rendering
Case Studies are sorted
alphabetically, ascending,
vertically sequential.
Equal number of case studies
per column. Right column
can contain one fewer in the
case of an odd number of
case studies.
43. Functional Specification – All Rounds – final TCS Redesign Phase I
30 APPENDIX
30.1 Parts & Supplies Deliverable (section 5.0)
As per the recent agreement, Parts & Supplies templates and copy will be delivered as part of Round 2.5. Subsequent drafts of this
documents will include discussion of these templates.
February 27, 2007 39 Confidential
44. Functional Specification – All Rounds – final TCS Redesign Phase I
31 TEMPLATE: D2.5T1STAT
Delivery Round 2.5, Template 1, Static Content
31.1 Applicable Content Sections
0.0 non-Flash Homepage
February 27, 2007 40 Confidential
Download Flash
link and text
display if Flash not
detected, or
version below
Flash 7 is detected
45. Functional Specification – All Rounds – final TCS Redesign Phase I
32 TEMPLATE: D2.5T2DYN
Delivery Round 2.5, Template 2, Dynamic Content
32.1 Applicable Content Sections
5.x Parts and Supplies – 2nd
& 3rd
Level Pages
32.2 Child Links
If there are child categories, links appear bulleted, below descriptive text and above Literature links.
February 27, 2007 41 Confidential
Child Links
If child links exist, they will be
rendered below introductory
copy and above literature
links.
Find a Parts Dealer drop down
50 States are listed. One menu
change, browser loads parts
stores listing for selected state
46. Functional Specification – All Rounds – final TCS Redesign Phase I
32.3 Content Styles
Most of the content in these pages is bulleted text, sub-divided by headings. Follow style guide for content formatting.
February 27, 2007 42 Confidential
47. Functional Specification – All Rounds – final TCS Redesign Phase I
33 TEMPLATE: D2.5T3STAT
Delivery Round: 2, Template 3, Dynamic Content
33.1 Applicable Content Sections
5.8 Parts Store Search Results
February 27, 2007 43 Confidential
State Dropdown
Selected state is default
selected option in drop
down menu.
Sorting/Columns
Stores are listed
alphabetically, by city.
Equal number of stores per
column. 2nd
column can
contain 1 fewer items.
48. Functional Specification – All Rounds – final TCS Redesign Phase I
34 TEMPLATE: D2.5T4STAT
Delivery Round 2.5, Template 4, Static Content
34.1 Applicable Content Sections
7.x.x Featured Case Studies
February 27, 2007 44 Confidential
49. Functional Specification – All Rounds – final TCS Redesign Phase I
35 TEMPLATE: D2.5T5DYN
Delivery Round 2.5, Template 5, Dynamic Content
35.1 Applicable Content Section
0.13 Search Results Feedback
35.2 Page Text (based on user path)
35.2.1 User arrives at page by clicking “No” to Search
Results Feedback question
February 27, 2007 45 Confidential
Dynamic conditional
text
Text is displayed based
on user path to this
page
Form Submit
Form submission returns
Search Results
Feedback Thank You
text.
50. Functional Specification – All Rounds – final TCS Redesign Phase I
Text above text area box: “We’re sorry your search was not successful. Please leave feedback to let us know how we can
better help you next time. [new paragraph] Please provide specific comments; tell us what you were searching for.”
35.2.2 User arrives at page by answering “Yes” to Search
Results Feedback question, and clicks on “leave feedback” link
Text above text area box: “Please leave us feedback to help us improve our search results.”
35.2.3 Text above email text input box
“If your comments require a response, please provide your e-mail address”
35.2.4 Required field
JavaScript checks for user entry in the “comments” text area box. If the field is blank, system displays JavaScript Alert: “Please
leave comments so that we can address your concerns. Thank you.” On user click “OK”, browser focuses cursor on
“comments” text area box.
35.2.5 Successful Form Submission
Browser displays text: “Thank you for your comments. We will address your feedback as soon as possible.”
February 27, 2007 46 Confidential
51. Functional Specification – All Rounds – final TCS Redesign Phase I
36 TEMPLATE: D3T1STAT
Delivery Round 3, Template 1, Static Content
36.1 Applicable Content Sections
0.4 Contact a Sales Engineer
February 27, 2007 47 Confidential
State Selection
On selection of state,
browser loads
Sales Office page
with results for
selected state.
Zip Code Search
User can enter zip
code and click
“Go”. Zip code
search back end
functionality can
be reused from
current site
Country/Province
Selections
Same functionality
as state selector
for international
locations.
52. Functional Specification – All Rounds – final TCS Redesign Phase I
37 TEMPLATE: D3T2DYN
Delivery Round 3, Template 2, Dynamic Content
37.1 Applicable Content Sections
0.4.1 United States Sales Office Results
February 27, 2007 48 Confidential
Maintain Zip Code Entry
If user entered a zip code, value
is default in text input box on
results page.
Maintain State Selection
If user selected a state, value is
default selection in drop down
menu on results page.
Sales Office Results
Two columns. 2nd
column can
contain 1 less result, if odd
number of results are
returned.
Sales Office Name
Bolded first line of sales office
info should be [City], [State],
where state uses the two
letter abbreviation.
53. Functional Specification – All Rounds – final TCS Redesign Phase I
37.2 Maintain Search Info
37.2.1 Zip Code Search
If user enters a zip code, zip code is displayed in text input box on results page.
37.2.2 State Listing
If user selects a state on the drop down menu, that state is selected by default in the drop down menu on the results page.
37.3 Results Display
Results are displayed in two columns, sequenced vertically. 2nd
column can contain one fewer result if odd number of results is
returned.
37.3.1 Zip Code Results
System returns 10 closest sales offices.
37.4 Results – 1st
Line
The 1st
line of the results should display the city and state of the sales office, as follows [City], [State], where State is displayed as the
two-letter abbreviation.
37.5 Sorting
37.5.1 Zip Code Search
Results are sorted closest to farthest from zip code entered.
37.5.2 State Selection
Results are sorted alphabetically by city.
February 27, 2007 49 Confidential
54. Functional Specification – All Rounds – final TCS Redesign Phase I
38 TEMPLATE: D3T3DYN
Delivery Round: 3, Template 3, Dynamic Content
38.1 Applicable Content Sections
0.4.3, 0.4.4 Canadian and International Sales Office Results
February 27, 2007 50 Confidential
Country/Province Drop
down
Selected country/province
is default selected option
in drop down menu.
On menu change, page
reloads with results for
selected country or
province.
Sorting/Columns
Stores are listed
alphabetically, by city.
Equal number of stores per
column. 2nd
column can
contain 1 fewer items.
55. Functional Specification – All Rounds – final TCS Redesign Phase I
39 TEMPLATE: D3T4STAT
Delivery Round 3, Template 4, Static Content
39.1 Applicable Content Sections
0.3 Career Opportunities
February 27, 2007 51 Confidential
Check boxes
Users can select multiple
categories and Locations
for display.
Search/Reset
Click on Search button
requests search results
Reset button clears
checkbox selections
Search Results
Display only when user
manually clicks search
button.
56. Functional Specification – All Rounds – final TCS Redesign Phase I
40 TEMPLATE: D3T5STAT
Delivery Round 3, Template 5, Static/Dynamic Content
40.1 Applicable Content Section
0.2 News Room
February 27, 2007 52 Confidential
Featured Story
Specially marked news or
published article story
appears as featured story
in this space.
News Stories
News stories sorted by date,
newest to oldest,
populated by DNA.
News Update Sign-
Up
Form is processed as
existing sign-up form
is.
57. Functional Specification – All Rounds – final TCS Redesign Phase I
40.2 Featured Story
Flagged news item in DNA is displayed at top of page in Featured Story area.
40.3 Child Page Links
Links to Published Articles, Photos and Advertisements categories appear in middle of page along with associated images and
descriptive text.
40.4 News Items
News items are displayed below child category links, sorted by date, newest to oldest. This page only displays stories from the current
year, unless the number of stories is less than 10. In that case, page displays any stories from current year, followed by most recent
stories from previous year so that total number of stories is equal to 10.
40.5 News Update Signup Form
40.5.1 Validation
On submit, JavaScript checks to see that email address entered by user is valid (* “@” * “.” *). If email address is invalid,
JavaScript alert appears with this text: “The email address you entered is invalid. Please enter a valid email address.” On user
click “OK”, browser focuses cursor on text input box for email entry.
40.6 Submission
Form submission is handled using extant form handling business rules, and returns thank you message using new look and feel.
February 27, 2007 53 Confidential
58. Functional Specification – All Rounds – final TCS Redesign Phase I
41 TEMPLATE: D3T6STAT
Delivery Round 3, Template 6, Dynamic Content
41.1 Applicable Content Section
0.2.2 Photos, 0.2.4 Advertisements
February 27, 2007 54 Confidential
Photos
Photo links and meta
data maintained
manually
News Update Sign-
Up
Form is processed as
existing sign-up form
is.
59. Functional Specification – All Rounds – final TCS Redesign Phase I
42 TEMPLATE: D3T7DYN
Delivery Round 3, Template 7, Dynamic Content
42.1 Applicable Content Section
0.2.3, 0.2.5, 0.2.6, 0.2.7, 0.2.8, 0.2.9, 0.2.10 – Press Release Page, Press Release and Published Article Archives
February 27, 2007 55 Confidential
Type of Links
Indicates whether
page contains Press
Releases or
Published Articles
Content Identifier
If page contains
archived material,
use “Archive:” and
year
60. Functional Specification – All Rounds – final TCS Redesign Phase I
43 TEMPLATE: D3T8DYN
Delivery Round 3, Template 8, Dynamic Content
43.1 Applicable Content Section
0.4.x.x – Sales Office Pages
February 27, 2007 56 Confidential
Right Sidebar Items
These items are populated
by CPS the same way
they are populated in
extant system. Use
generic icon for these
items.
Formatting
Apply new formatting to
field values displayed on
these pages.
61. Functional Specification – All Rounds – final TCS Redesign Phase I
44 TEMPLATE: D3T9STAT
Delivery Round 3, Template 9, Static Content
44.1 Applicable Content Section
11.0, 12.0 - Explore [Industry], Explore [Building Type]
February 27, 2007 57 Confidential
Drop down menu default
Drop down should default
to selected Industry or
Building Type
62. Functional Specification – All Rounds – final TCS Redesign Phase I
45 TEMPLATE: D3T11DYN
Delivery Round 3, Template 11, Dynamic Content
45.1 Applicable Content Section
0.101 Site Map
February 27, 2007 58 Confidential
Site Map Formatting
XML file of site map is
rendered using indent
formatting and links to
pages/categories
displayed.
63. Functional Specification – All Rounds – final TCS Redesign Phase I
46 TEMPLATE: D3T12STAT
Delivery Round 3, Template 12, Static Content
46.1 Applicable Content Section
0.100 Privacy Policy
February 27, 2007 59 Confidential
64. Functional Specification – All Rounds – final TCS Redesign Phase I
47 TEMPLATE: D3T13STAT
Delivery Round 3, Template 13, Static Content
47.1 Applicable Content Section
7.1.1 Bren Hall (Tier 2) Case Study
February 27, 2007 60 Confidential
Flash Content
This tier of case study
contains a flash module
here.
Expand Link
On click, layer expands to
reveal all of “Specifics”
content
Contact a Sales Engineer
Links to page # 0.4