The document provides an overview of an online food ordering system project. It includes:
- A project overview describing an online system that allows customers to order food from their favorite restaurants through a website or app.
- Details of the key project features such as online menus, restaurant registration, customer reviews and ordering food 24/7.
- Diagrams including a context diagram, three levels of data flow diagrams and an entity relationship diagram that model the system.
- Additional sections on use cases, the current project view, future plans and limitations of the initial system.
Face to Face Communication and Text Based Communication in HCIAbdullah Khosa
This document compares face-to-face communication and text-based communication. Face-to-face communication involves non-verbal cues like body language, eye contact, and gestures that aid in conveying meaning. It allows for more natural turn-taking and feedback. However, text-based communication lacks these cues and is more important for self-esteem. While text is less engaging, it is more efficient in terms of speed and saves time compared to face-to-face interaction.
This document outlines an analysis for an online restaurant reservation system. It includes objectives to provide a convenient reservation process. The scope covers allowing online reservations and providing availability updates. Stakeholders include customers, restaurants, owners, and media. Requirements include booking, payment, availability searches, and confirmation emails. Use case diagrams, data flow diagrams, and user stories model interactions like making reservations, updating statuses, and cancellation scenarios. The analysis provides a foundation for developing the reservation system.
This document provides an overview and introduction to a proposed web service to help farmers in India. The proposed service would allow farmers, suppliers, and administrators to login separately and would include features like a complaints page for farmers, advertisement pages for suppliers, and SMS notifications to farmers about new ads. The service aims to improve communication and transparency between farmers and suppliers. It describes the motivation as addressing issues with middlemen and proposes the service could connect multiple villages. The document then outlines the methodology, technologies used like HTML, Java, CSS, JavaScript, and MySQL, and the scope which includes ensuring greater farmer profitability and bringing transparency to the agricultural system.
Client/server communication involves clients sending requests to a server and receiving responses. There are three main communication methods: sockets use IP addresses and port numbers to transfer unstructured data between processes; remote procedure calls allow clients to make function calls to remote servers; and pipes provide one-way or two-way interprocess communication by entering data from one endpoint and consuming it from the other.
The document discusses referential integrity in relational databases. It explains that referential integrity requires primary keys and foreign keys to be consistent, so that foreign keys always match existing primary keys in linked tables. This prevents issues like orphaned records or adding records that reference nonexistent keys. Referential integrity guarantees consistency between linked tables and helps maintain data integrity.
This document provides an overview of an online food delivery system project. It describes using the Rational Unified Process (RUP) model to implement the system in an iterative and incremental way. Key elements include functional requirements like online ordering and payment, non-functional requirements like security, and UML diagrams to model the system. Testing strategies include unit, integration, system, and acceptance testing.
The document provides an overview of an online food ordering system project. It includes:
- A project overview describing an online system that allows customers to order food from their favorite restaurants through a website or app.
- Details of the key project features such as online menus, restaurant registration, customer reviews and ordering food 24/7.
- Diagrams including a context diagram, three levels of data flow diagrams and an entity relationship diagram that model the system.
- Additional sections on use cases, the current project view, future plans and limitations of the initial system.
Face to Face Communication and Text Based Communication in HCIAbdullah Khosa
This document compares face-to-face communication and text-based communication. Face-to-face communication involves non-verbal cues like body language, eye contact, and gestures that aid in conveying meaning. It allows for more natural turn-taking and feedback. However, text-based communication lacks these cues and is more important for self-esteem. While text is less engaging, it is more efficient in terms of speed and saves time compared to face-to-face interaction.
This document outlines an analysis for an online restaurant reservation system. It includes objectives to provide a convenient reservation process. The scope covers allowing online reservations and providing availability updates. Stakeholders include customers, restaurants, owners, and media. Requirements include booking, payment, availability searches, and confirmation emails. Use case diagrams, data flow diagrams, and user stories model interactions like making reservations, updating statuses, and cancellation scenarios. The analysis provides a foundation for developing the reservation system.
This document provides an overview and introduction to a proposed web service to help farmers in India. The proposed service would allow farmers, suppliers, and administrators to login separately and would include features like a complaints page for farmers, advertisement pages for suppliers, and SMS notifications to farmers about new ads. The service aims to improve communication and transparency between farmers and suppliers. It describes the motivation as addressing issues with middlemen and proposes the service could connect multiple villages. The document then outlines the methodology, technologies used like HTML, Java, CSS, JavaScript, and MySQL, and the scope which includes ensuring greater farmer profitability and bringing transparency to the agricultural system.
Client/server communication involves clients sending requests to a server and receiving responses. There are three main communication methods: sockets use IP addresses and port numbers to transfer unstructured data between processes; remote procedure calls allow clients to make function calls to remote servers; and pipes provide one-way or two-way interprocess communication by entering data from one endpoint and consuming it from the other.
The document discusses referential integrity in relational databases. It explains that referential integrity requires primary keys and foreign keys to be consistent, so that foreign keys always match existing primary keys in linked tables. This prevents issues like orphaned records or adding records that reference nonexistent keys. Referential integrity guarantees consistency between linked tables and helps maintain data integrity.
This document provides an overview of an online food delivery system project. It describes using the Rational Unified Process (RUP) model to implement the system in an iterative and incremental way. Key elements include functional requirements like online ordering and payment, non-functional requirements like security, and UML diagrams to model the system. Testing strategies include unit, integration, system, and acceptance testing.
The document discusses prototyping techniques for software development. It defines prototyping as an essential element of user-centered design that involves testing design ideas with users early in the development process. Different types of prototyping are appropriate for different stages, from paper-based prototypes to test initial ideas to software-based prototypes that provide limited functionality for further testing. The goal of prototyping is to identify and address design errors and user requirements before significant development effort.
The document discusses types and roles in UML. Types are conceptual classes used during analysis to identify possible object types in a system. They do not have methods or instances. Roles represent the behaviors of entities in particular contexts. An object can play different roles depending on the context, presenting different properties based on its role. Types and roles are modeling concepts in UML used to describe the abstraction of classes and behaviors before implementation.
This document discusses relationships in database management systems. It begins by introducing relationships and how they are established through primary and foreign keys. It then describes different types of relationships: one-to-one, one-to-many, many-to-one, and many-to-many. For each relationship type, it provides examples and descriptions of how the relationships are implemented in tables. The document emphasizes that relationships are important for reducing data redundancy, organizing the database, and ensuring referential integrity. It concludes by reiterating the importance of properly defining relationships for effective database functioning.
The document discusses three types of relationships between tables in a database: one-to-one, one-to-many, and many-to-many. In a one-to-one relationship, each record in one table is linked to only one record in another table. A one-to-many relationship occurs when each record in one table links to only one record in another table, but records in the second table can link to multiple records in the first. A many-to-many relationship exists when records in one table can link to multiple records in another table and vice versa; this requires a junction table.
Performance tuning and optimization (ppt)Harish Chand
The document discusses various ways to improve client/server performance at both the client and server level. It addresses:
1) Client performance can be improved by optimizing hardware and software. Hardware optimizations include using the fastest available components, while software optimizations involve improving the operating system and applications.
2) Server performance can also be improved through hardware upgrades like adding network cards, as well as implementing high-performance file systems and offloading processing to servers.
3) Database performance optimizations involve efficient index design, query design, and database normalization to minimize network traffic and process data faster.
This document provides a tutorial on component diagrams. It defines component diagrams as diagrams that visualize the organization and dependencies of system components. It describes common component diagram symbols like components, interfaces, ports, and dependencies. It also provides steps for drawing a component diagram, including identifying system artifacts, creating relationships between elements, and adding additional elements and notes. Examples of component diagrams for different systems are included.
Mapping cardinality describes the number of entities in one set that can be associated with entities in another set via a relationship. There are four types of mapping cardinality: one-to-one, where each entity is associated with exactly one entity in the other set; one-to-many, where an entity can be associated with multiple entities but each entity can only be associated with one entity; many-to-one, the inverse of one-to-many; and many-to-many, where each entity can be associated with multiple entities in the other set.
The document provides an overview of elements that make up an analysis model, including:
- Use case text, diagrams, activity diagrams, swim lane diagrams, and other modeling techniques.
- The overall objectives of the analysis model are to describe customer requirements, establish a basis for software design, and define requirements that can be validated.
- Scenario-based modeling represents the system from the user's perspective using use case text and diagrams. Elements of use cases and examples of use case diagrams are also described.
Guía Rápida de Microsoft - Usar Office 365 en AndroidMICProductivity
Este documento proporciona una guía para usar Office 365 en un teléfono Android. Explica cómo configurar el correo electrónico, calendario y contactos de Office 365, y cómo acceder y colaborar en documentos, blocs de notas y sitios desde aplicaciones como Outlook, OneDrive, OneNote, SharePoint y Lync. También recomienda instalar aplicaciones de Office para Android como Office Mobile y Lync para seguir trabajando de forma remota.
Bug Tracking System is a web-based application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. Bugs will be assigned to a person with a bug id, flag, description, project name.
Operating System : Windows XP or above
User Interface : HTML, CSS
Client-side Scripting : PHP
Back End : MySQL
Web Server : Apache Tomcat 7.0.22
IDE : NetBeans 7.1
Este documento presenta el modelo de diseño de un sistema de nóminas. Describe la arquitectura por capas del software, incluyendo una capa de presentación, una capa de procesamiento de datos y una capa de almacenamiento de datos. Explica los casos de uso del sistema como inicio de sesión, gestión de empleados, registro de ingresos y egresos, consulta de reportes y administración de nómina. Además, define los scripts y tecnologías utilizadas en cada capa como PHP, SQL y CSS.
15.secure keyword search and data sharing mechanism for cloud computingVenkat Projects
The document proposes a ciphertext-policy attribute-based mechanism called CPAB-KSDS that allows encrypted data stored in the cloud to be securely searched and shared. Existing solutions only support either search or sharing of encrypted data, not both. CPAB-KSDS supports both attribute-based keyword search and data sharing while also enabling keyword updates during sharing without interacting with the private key generator. The system architecture requires a processor, 40GB hard disk, 2GB RAM, Windows OS, Java/J2EE coding, MySQL database, and Netbeans IDE.
this this only for flight booking, not for taxi , bus or train. and all the contact details you will found in this document is totally wrong. so please don't try to contact with that details.
The document is a software requirements specification for a café management system. It describes the purpose, scope, and features of the system. The system will manage customer orders and payments, food preparation, and generate reports to help the café owner evaluate business performance. It will have a user-friendly interface for customers to order via a mobile app and management functions for staff. The system is intended to facilitate customers and staff at a university café by providing efficient service and deals.
Normalisation is a process that structures data in a relational database to minimize duplication and redundancy while preserving information. It aims to ensure data is structured efficiently and consistently through multiple forms. The stages of normalization include first normal form (1NF), second normal form (2NF), third normal form (3NF), Boyce-Codd normal form (BCNF), fourth normal form (4NF) and fifth normal form (5NF). Higher normal forms eliminate more types of dependencies to optimize the database structure.
This document provides an introduction to SOAP, WSDL, and UDDI, which together define the architecture for big web services. It discusses what a web service is, the roles of SOAP, WSDL, and UDDI in the web service architecture, how web services differ from conventional middleware like CORBA, an overview of SOAP including its message exchange mechanism and use of RPC, how WSDL is used to describe a web service's interface, and how UDDI allows for service discovery.
Smart Health Disease Prediction django machinelearning.pptxsaiproject
This document presents a smart health disease prediction system that uses machine learning. The system allows users to input their symptoms and predicts the potential illness. It uses data mining techniques like Naive Bayes classification to match symptoms with diseases. Key features include doctors accessing patient details, administrators adding disease data, and a user-friendly interface for disease prediction and searching doctors. The system aims to provide timely medical guidance when users specify symptoms. It was developed using Python, Django, SQLite, HTML, CSS and machine learning algorithms like Naive Bayes, Random Forest and Support Vector classifiers.
The document discusses the prototyping lifecycle model in software engineering. It describes prototyping as creating early versions of a software application to gather requirements and refine the design. The key steps are: gathering requirements through user interviews, creating a preliminary design, building a prototype, assessing the prototype with users, refining it based on their feedback, and developing the final product. There are different types of prototyping like throwaway, evolutionary, incremental, and extreme. Prototyping helps produce systems that better meet user needs and finds problems earlier in the development cycle.
The document discusses prototyping techniques for software development. It defines prototyping as an essential element of user-centered design that involves testing design ideas with users early in the development process. Different types of prototyping are appropriate for different stages, from paper-based prototypes to test initial ideas to software-based prototypes that provide limited functionality for further testing. The goal of prototyping is to identify and address design errors and user requirements before significant development effort.
The document discusses types and roles in UML. Types are conceptual classes used during analysis to identify possible object types in a system. They do not have methods or instances. Roles represent the behaviors of entities in particular contexts. An object can play different roles depending on the context, presenting different properties based on its role. Types and roles are modeling concepts in UML used to describe the abstraction of classes and behaviors before implementation.
This document discusses relationships in database management systems. It begins by introducing relationships and how they are established through primary and foreign keys. It then describes different types of relationships: one-to-one, one-to-many, many-to-one, and many-to-many. For each relationship type, it provides examples and descriptions of how the relationships are implemented in tables. The document emphasizes that relationships are important for reducing data redundancy, organizing the database, and ensuring referential integrity. It concludes by reiterating the importance of properly defining relationships for effective database functioning.
The document discusses three types of relationships between tables in a database: one-to-one, one-to-many, and many-to-many. In a one-to-one relationship, each record in one table is linked to only one record in another table. A one-to-many relationship occurs when each record in one table links to only one record in another table, but records in the second table can link to multiple records in the first. A many-to-many relationship exists when records in one table can link to multiple records in another table and vice versa; this requires a junction table.
Performance tuning and optimization (ppt)Harish Chand
The document discusses various ways to improve client/server performance at both the client and server level. It addresses:
1) Client performance can be improved by optimizing hardware and software. Hardware optimizations include using the fastest available components, while software optimizations involve improving the operating system and applications.
2) Server performance can also be improved through hardware upgrades like adding network cards, as well as implementing high-performance file systems and offloading processing to servers.
3) Database performance optimizations involve efficient index design, query design, and database normalization to minimize network traffic and process data faster.
This document provides a tutorial on component diagrams. It defines component diagrams as diagrams that visualize the organization and dependencies of system components. It describes common component diagram symbols like components, interfaces, ports, and dependencies. It also provides steps for drawing a component diagram, including identifying system artifacts, creating relationships between elements, and adding additional elements and notes. Examples of component diagrams for different systems are included.
Mapping cardinality describes the number of entities in one set that can be associated with entities in another set via a relationship. There are four types of mapping cardinality: one-to-one, where each entity is associated with exactly one entity in the other set; one-to-many, where an entity can be associated with multiple entities but each entity can only be associated with one entity; many-to-one, the inverse of one-to-many; and many-to-many, where each entity can be associated with multiple entities in the other set.
The document provides an overview of elements that make up an analysis model, including:
- Use case text, diagrams, activity diagrams, swim lane diagrams, and other modeling techniques.
- The overall objectives of the analysis model are to describe customer requirements, establish a basis for software design, and define requirements that can be validated.
- Scenario-based modeling represents the system from the user's perspective using use case text and diagrams. Elements of use cases and examples of use case diagrams are also described.
Guía Rápida de Microsoft - Usar Office 365 en AndroidMICProductivity
Este documento proporciona una guía para usar Office 365 en un teléfono Android. Explica cómo configurar el correo electrónico, calendario y contactos de Office 365, y cómo acceder y colaborar en documentos, blocs de notas y sitios desde aplicaciones como Outlook, OneDrive, OneNote, SharePoint y Lync. También recomienda instalar aplicaciones de Office para Android como Office Mobile y Lync para seguir trabajando de forma remota.
Bug Tracking System is a web-based application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. Bugs will be assigned to a person with a bug id, flag, description, project name.
Operating System : Windows XP or above
User Interface : HTML, CSS
Client-side Scripting : PHP
Back End : MySQL
Web Server : Apache Tomcat 7.0.22
IDE : NetBeans 7.1
Este documento presenta el modelo de diseño de un sistema de nóminas. Describe la arquitectura por capas del software, incluyendo una capa de presentación, una capa de procesamiento de datos y una capa de almacenamiento de datos. Explica los casos de uso del sistema como inicio de sesión, gestión de empleados, registro de ingresos y egresos, consulta de reportes y administración de nómina. Además, define los scripts y tecnologías utilizadas en cada capa como PHP, SQL y CSS.
15.secure keyword search and data sharing mechanism for cloud computingVenkat Projects
The document proposes a ciphertext-policy attribute-based mechanism called CPAB-KSDS that allows encrypted data stored in the cloud to be securely searched and shared. Existing solutions only support either search or sharing of encrypted data, not both. CPAB-KSDS supports both attribute-based keyword search and data sharing while also enabling keyword updates during sharing without interacting with the private key generator. The system architecture requires a processor, 40GB hard disk, 2GB RAM, Windows OS, Java/J2EE coding, MySQL database, and Netbeans IDE.
this this only for flight booking, not for taxi , bus or train. and all the contact details you will found in this document is totally wrong. so please don't try to contact with that details.
The document is a software requirements specification for a café management system. It describes the purpose, scope, and features of the system. The system will manage customer orders and payments, food preparation, and generate reports to help the café owner evaluate business performance. It will have a user-friendly interface for customers to order via a mobile app and management functions for staff. The system is intended to facilitate customers and staff at a university café by providing efficient service and deals.
Normalisation is a process that structures data in a relational database to minimize duplication and redundancy while preserving information. It aims to ensure data is structured efficiently and consistently through multiple forms. The stages of normalization include first normal form (1NF), second normal form (2NF), third normal form (3NF), Boyce-Codd normal form (BCNF), fourth normal form (4NF) and fifth normal form (5NF). Higher normal forms eliminate more types of dependencies to optimize the database structure.
This document provides an introduction to SOAP, WSDL, and UDDI, which together define the architecture for big web services. It discusses what a web service is, the roles of SOAP, WSDL, and UDDI in the web service architecture, how web services differ from conventional middleware like CORBA, an overview of SOAP including its message exchange mechanism and use of RPC, how WSDL is used to describe a web service's interface, and how UDDI allows for service discovery.
Smart Health Disease Prediction django machinelearning.pptxsaiproject
This document presents a smart health disease prediction system that uses machine learning. The system allows users to input their symptoms and predicts the potential illness. It uses data mining techniques like Naive Bayes classification to match symptoms with diseases. Key features include doctors accessing patient details, administrators adding disease data, and a user-friendly interface for disease prediction and searching doctors. The system aims to provide timely medical guidance when users specify symptoms. It was developed using Python, Django, SQLite, HTML, CSS and machine learning algorithms like Naive Bayes, Random Forest and Support Vector classifiers.
The document discusses the prototyping lifecycle model in software engineering. It describes prototyping as creating early versions of a software application to gather requirements and refine the design. The key steps are: gathering requirements through user interviews, creating a preliminary design, building a prototype, assessing the prototype with users, refining it based on their feedback, and developing the final product. There are different types of prototyping like throwaway, evolutionary, incremental, and extreme. Prototyping helps produce systems that better meet user needs and finds problems earlier in the development cycle.
[Ignite LG 2016 Spring] Cultural Observations, David Seperson 부장 Life's Good
Koreans are very polite people. After work, Koreans enjoy comfort foods like chimaek (chicken and beer) with friends to relax and gossip. The document discusses cultural observations made by Dave Seperson about Korean politeness and popular after work activities like eating chimaek with friends as a way to feel at home.
South Korea has a diversified industrial base led by electronics and has an excellent education system. Its economy has grown steadily in recent years at around 3-4% annually due to construction investment and private consumption, though exports have weakened. Inflation has remained low around 1.5-3% while the government runs small budget deficits around 0.3% of GDP and pursues monetary policies of inflation targeting, currently holding interest rates around 2-3%.
Study: The Future of VR, AR and Self-Driving CarsLinkedIn
We asked LinkedIn members worldwide about their levels of interest in the latest wave of technology: whether they’re using wearables, and whether they intend to buy self-driving cars and VR headsets as they become available. We asked them too about their attitudes to technology and to the growing role of Artificial Intelligence (AI) in the devices that they use. The answers were fascinating – and in many cases, surprising.
This SlideShare explores the full results of this study, including detailed market-by-market breakdowns of intention levels for each technology – and how attitudes change with age, location and seniority level. If you’re marketing a tech brand – or planning to use VR and wearables to reach a professional audience – then these are insights you won’t want to miss.
Artificial intelligence (AI) is everywhere, promising self-driving cars, medical breakthroughs, and new ways of working. But how do you separate hype from reality? How can your company apply AI to solve real business problems?
Here’s what AI learnings your business should keep in mind for 2017.
안녕하십니까. 중아 지역본부 러닝센터에 근무하고 있는 전찬국 과장입니다.
오늘 제가 Ignite LG에서 5분동안 여러분들과 나누고자 하는 주제는 바로
‘중동 아프리카에게 LG란?‘ 입니다.
먼저 여러분께 묻고 싶습니다. 여러분들에게 중동 아프리카는 무엇인가요? 그냥 일반적으로 중동 아프리카라는 말을 들었을때 그려지는 이미지는 뭔가요?
아마도 대부분의 사람들은 중동 아프리카 하면 먼저 무슬림(테러리스트)들을 떠올리거나 얼마전 한국을 공포에 떨게 만들었던 메르스, 혹은 아프리카의 굶주린 어린 아이들의 모습, 그리고 아프리카 초원의 야생동물을 떠올릴지도 모르겠습니다.
그렇다면 현재 중동 아프리카는 어떠한 모습일까요? 몇몇 국가의 예를 들어 현재의 상황을 살펴보겠습니다.
LG전자 중동 아프리카 지역본부가 위치한 국가 UAE의 두바이는 세계의 중심이 되어 가고 있다
그러나 이러한 두바이에서 국제전화를 할수 없는 국가(법인)가 하나 있습니다. 어딘지 아세요?
바로 이스라엘입니다. 이유는 간단합니다. 이스라엘은 바로 적국이기 때문이다.
왜? 간단히 우리가 북한에 전화 할수 없는 것과 같이 이유다. 당연히 이스라엘 사람들은 두바이 입국이 금지이며 두바이 사람들도 이스라엘에 갈수가 없다.
우리 LG비즈니스에 이름도 이스라엘이라고도 부를수 없어서 유국이라고 부른다. (유대인 국가). 이러한 이스라엘은 종교적인, 이념적인 차이에서 비롯하여 끊임없이 팔레스타인 및 다른 중동 아프리카 국가들과 대립하고 있습니다. 수니파와 시아파로 나뉘어 싸우는 무슬림들도 이스라엘을 얘기할 때는 한 목소리를 낸다.
그리고 2015년 10월 28일, 지금도 이스라엘과 팔레스타인은 교전중에 있습니다. 이스라엘은 중동의 영원한 화약고라고 할수 있습니다.
중동의 맹주. 한때 중동 대부분의 나라를 차지했던 페르시아인들. 현재 핵보유와 관련하여 미국과 치열하게 대립하고 있는 중동국가입니다. 사실 이란사람들은 철저한 반미주의로서 미국에 대한 혐오증을 가지고 있습니다. 최근 미국과의 핵협상을 통해 경제제건을 꿈꾸고 있긴 하지만 지난주 미사일 실험을 함으로서 다시금 비난을 받고 있습니다.
중동에서 가장 중요한 국가 중 하나인 이슬람교가 태어난 곳 사우디 아라비아.
메카로 유명하며 이로 인해 매년 예배를 드리기 위한 인파가 몰리고 이슬람 최대 명절인 하지에는 방문인구가 폭발적으로 늘어나 가끔 사고가 나기도 함 – 그러나 무슬림들은 이러한 사고로 숨지는것 또한 순교라고 생각함
무슬림들은 일생에 한번은 의무적으로 메카를 방문해야 합니다. 그럼으로 인해 메카는 항상 사람들로 붐빕니다.
중동에서 최근 가장 골칫거리중 하나인 곳. 방문금지 국가. 시리아.
내전으로 인해 국민의 절반이상이 난민이 되어 유럽으로 가고 있습니다. 또한 최근 시리아내 IS와의 전쟁으로 인해 국가이미지 및 모든 국토가 초토화 되어 가고 있습니다.
이외 파키스탄의 테러단체인 알카에다, 나이지리아의 테러단체인 보코하람, 소말리아의 해적 등 중동아프리카에는 현재 다양한 위험과 이슈가 산재해 있다.
이러한 중동 아프리카 현재의 이슈들을 종합해 보면, 종교적, 정치적, 사회적, 이념적인 갈등이 서방 국가들의 이익과도 복잡하게 섞여 있어 중동 아프리카 나라들을 평화롭게 다시금 연결하기는 쉽지 않다
지금까지 언급했던 모든 나라들의 공통점이 있습니다. 그게 뭘까요?
언급했던 모든 나라에 현재 LG전자 제품이 수출되고 있다는 점. 즉, 이들의 종교, 정치, 이념적 사상은 다르지만 이들은 모두 우리 LG전자 제품을 사용하고 있다는 공통점이 있습니다. 다시말해 내전이나 혹은 전쟁으로 많은 이들 나라는 분리되어 있지만 이미 LG라는 이름으로 연결되어 있다는 것.
즉, 한겨울인 12월에도 온도가 35인 사막국가인 사우디아라비아와 같은 곳에서의 LG전자 에어컨은 보다 나은 삶의 질을 의미한다.
음악과 춤을 좋아하는 아프리카 인들에게 LG전자 오디오는 삶의 기쁨을 의미한다.
내전과 전쟁으로 파괴된 도시에 LG전자 제품은 새로운 삶의 시작 그 자체를 의미한다
중동 아프리카에게 LG전자란? 즉, 현재의 삶을 하나의 점으로 본다면 보다 나은 삶이라는 다른 점으로의 connecting dot을 가능하게 하는 연결 고리다. 이들에게 LG전자 사람들은 또다른 연결고리를 가지고 온 사람들인 것이다.
이것은 중동아프리카에 살면서 LG라는 이름을 가지고 출장을 다니면서 느꼈던 희열이다.
2011년 9월… 시리아 내전이 시작되고 얼마되지 않아. 대한민국에서는 여행자제 지역으로 시리아를 분류한 상태. 시리아에 있는 거래선사장으로부터 직원교육을 해달라는 요청이 왔다. 고민중에 결국 방문한 시리아의 수도 다마스커스에서는 외국인들이 모두 빠져나가고 전쟁의 긴장감이 감돌았다. 전쟁중이었던 시리아의 거리를 거래선 사장과 함께 걸었던 것은 아마도 평생 잊지 못할 기억이 될것이다. 교육은 무사히 마쳤고 나도 두바이로 무사히 돌아왔다. 이후 시리아 내전은 보다 심각하게 변했고 IS와의 전쟁까지 터지면서 이제는 여행금지 국가로 변했으며 전 세계 그 누구도 입국 할 수가 없게 되었다.
그러나 그때 만난 거래선 사장은 아직도 내게 연락을 해오며 시리아 전쟁이 끝나고 국가재건시에는 LG제품을 꼭 모든 국민에게 전파하겠다는 메시지를 주었다.
이렇게 당신의 회사, LG전자는 보다 나은 삶으로의 연결고리 입니다.
중동아프리카 어딘가에서는 오늘도 한 생명이 LG전자 제품으로 인하여 보다 나은 삶을 접하고 있습니다.
. 중동아프리카 어딘가에서는 오늘도 한 생명이 LG전자 제품으로 인하여 보다 나은 삶을 접하고 있습니다.
LG제품을 전달하는 사람도, 받는 사람도, 중동아프리카에서는 LG제품, 즉 LG는 좀더 다른 의미입니다.
중동 아프리카에게 LG란? 보다 나은 삶으로의 기회, 새로운 삶의 시작을 의미합니다.
LG…. 혹시 LG가 너무나도 가까이 있어 그 소중함을 잊어버리지는 않았는지요?
당신이 너무나도 당연하게 생각하는 LG가 어떤 사람에게는 또다른 인생을, 새로운 삶을 의미함니다.
2015년 10월 28일 오늘…당신에게 LG란 무엇입니까?
감사합니다.