Scribd
Upload
51 views

"LG Electronics": Project Report ON

This document provides a summary of a project report on LG Electronics. It discusses the methodology adopted for the project, which was the waterfall model. The document also outlines some of the system requirements and design constraints for the project, such as the need to use fonts that are properly visible and limiting the number of forms to avoid complexity. The software system attributes of maintainability and dependability are also mentioned.

Uploaded by

pavneetsinghraina
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
51 views

"LG Electronics": Project Report ON

This document provides a summary of a project report on LG Electronics. It discusses the methodology adopted for the project, which was the waterfall model. The document also outlines some of the system requirements and design constraints for the project, such as the need to use fonts that are properly visible and limiting the number of forms to avoid complexity. The software system attributes of maintainability and dependability are also mentioned.

Uploaded by

pavneetsinghraina
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 26

PROJECT REPORT

ON

LG ELECTRONICS

PROJECT REPORT SUBMITTED IN PARTIAL FULFILLMENT OF

THE REQUIREMENT OF
BACHELOR OF BUSINESS ADMINISTRATION(B&I)

By:

Pavneet Singh

Enrollment No. 02590201815

Under the guidance of

Ms. Sarabjit Kaur

SRI GURU TEGH BAHADUR INSTITUTE OF MANAGEMENT

&INFORMATION TECHNOLOGY

(Affiliated to GGSIP University Delhi)(2015-2018)


DECLARATION

I hereby declare that the project report LG ELECTRONICS submitted by me


to Guru Gobind Singh Indraprastha University , Delhi in partial fulfillment of
the requirement for the award of degree of Bachelors Of Business
Administration (Banking & Insurance) is a record of bonafide project work
carried out by me under the guidance of Ms. Sarabjit Kaur

I further declare that the work reported in this project has not been submitted and
will not be submitted, either in part or in full, for the award of other degree or
diploma in this institute or any other institute or university.

..

Place : Signature Of Candidate

Date : Pavneet Singh

BBA(B&I)-5THSEM

Enrol. No. 02590201815


CERTIFICATE
This is to certify that Pavneet Singh student of Sri Guru Tegh Bahadur Institute of
Management & Information Technology of course BBA(B&I) Batch (2014-2017),
has completed her research work titled LG ELECTRONICS under my
guidance and supervision .The work submitted is genuine and authentic.

.
Signature of Director
Prof. (Dr) Navneet Kaur

.
Signature of H.O.D
Ms. Bipasha Chaudhary

...
Signature of Guide
Ms. Sarabjit Kaur

....
Place: Delhi Signature of Scholar
Date: Pavneet Singh
ACKNOWLEDGEMENT

With profound sense of gratitude and regard, I express my sincere thanks to my


guide and mentor Ms. Sarabjit Kaur for her valuable guidance and the confidence
she instilled in me, that helped me in the successful completion of this project
report. Without her help, this project would have been a distant affair, her thorough
understanding of the subject and professional guidance was indeed of immense
help to me.

I am also greatly thankful to the faculty members of our institute who co-operated
with me and gave me their valuable time.

..

Signature of the scholar

Place: Delhi Pavneet Singh

Date: Enrollment no.02590201815


CONTENTS
S. Title Page No.
No.
1 INTRODUCTION 1
1.1. What is html? 1
1.2. Advantages of html 1
1.3. Disadvantages of html 2
1.4 Need for system 2
2 SYSTEM REQUIREMENT ANALYSIS 2
2.1. Project Category 3
2.2. Methodology adopted for project 4
2.3. Design Constraints 5
2.4 Software System Attributes 5
2.5 Features of the system 6
2.6 System Requirements 6
3 SYSTEM ANALYSYS & METHODOLOGY ADOPTED 12
3.1. Use Case Diagrams 12
3.2. Entity Relationship Diagram 15
3.3 Normalization 15
4 SOFTWARE DESIGN 16
5 TEST REPORT 18
5.1 White Box Texting 18
5.2 Black Box Texting 20
6 MY ROLES & RESPONSIBILITIES 22
7 CONCLUSION & ACHIEVEMENTS 23
8 BIBLIOGRAPHY 24
9 APPENDIX 25
Screen shots 25
Coding 65
CHAPTER 1 INTRODUCTION

1.1. What is html?

Hyper text markup language is the main markup language for displaying web
pages and other information that can be displayed in a web browser.

HTML is written in the form of HTML elements consisting of tags enclosed in


angle brackets (like <html>), within the web page content. HTML tags most
commonly come in pairs like <h1> and </h1>, although some tags, known as
empty elements, are unpaired, for example <img>. The first tag in a pair is the start
tag, the second tag is the end tag (they are also called opening tags and closing
tags). In between these tags web designers can add text, tags, comments and other
types of text-based content.

1.2. Advantages of html

The basic format that is utilized on the World Wide Web is HTML. To display
web pages with a broad range of colors, shapes and objects, HTML is used. In
developing, the following the advantages of using HTML:

1. Usage is easy.

2. Syntax is loose (Flexibility help complying with standards).

3. If not all, it is supported on almost all browsers.

4. Flexibility is high in HTML.

5. If not on all websites, it has been established on most websites and is used
widely.

6. It can also be used increasingly for data storage as it is like XML syntax.
1.3. Disadvantages of Html

1. It can created only static and plain pages

2. Need to write lot of code

3. Security features are not good

4. If we need to write long code for making a webpages than it produce


some complexity

1.4 Need for system

It is used to deliver globally renowned products that are best in quality


and of high quality.

It is used for quick and reliable response to their esteemed customer.

It is used to being market driven with focus on their customers.

It is used for creating and maintaining their customer delight.

It is used to provide the best service which is prompt and reliable

It is used to valuing the rights of their customers above something else.


CHAPTER 2 SYSTEM REQUIREMENT ANALYSIS

2.1. Project Category

The main aim to design this project is to provide graphical user interface that helps
the user to access information without any complexity and with minimum
operation. We categorize this project for commercial usage. This document also
describes the various interfaces i.e. the hardware, software and the user interfaces.
Along with that the document also describes the various functions and some
general constraints. This project is cost efficient as well as highly optimized as per
the requirement of user.

Assumptions and Dependencies:

We assume all users have basic knowledge. We also assume that the users will be
given software training, documentation and reference material

Future:

The doors for the amendments and improvements are always wide to any system.
In order to get better services out of it; desire modification can be made to the
system without much effort. As and when required new modules can easily be
incorporated into existing system. But this is sure that provided system does not
show any problem

2.2. Methodology adopted for project

Methodology is generally a guideline system for solving a problem, with specific


components such as phases, tasks, methods, techniques and tools. It can be defined
also as follows:
1. "The analysis of the principles of methods, rules, and postulates employed by a
discipline";

2. "The systematic study of methods that are, can be, or have been applied within a
discipline"
3. "The study or description of methods".
4. The systematic study of methods that are, can be, or have been applied within a
discipline"

5. "The study or description of methods".

A methodology can be considered to include multiple methods, each as applied to


various facets of the whole scope of the methodology.

We adopted methodology of water fall model:

Fig. 1: Water Fall Model


2.3. Design Constraints

In our professional training design phase we have come across following


constraints:

Technology-We have used html for our project. Regarding it we have to be


careful about following things:-

Fonts-We have to use fonts that are properly visible.

Forms-Number of forms used in our project are need to be less to


avoid complexity

GUI- User interface should be easy to operate.

Requirements-While designing we need to change design of project


according to requirements of library

Policies of institute- according to new policies of institute. We need to


change our modules

2.4 Software System Attributes

There are following software system attributes:


Maintainability
Our software is maintainable according toenvironmental changes
- Maintainability Index -67

Dependability
Our software is dependable on adobe, dream weaver and vvscipt

Performance
Our software performs in a efficient manner i.e.; it is User friendly

Lines Of Code
- LOC-9,222
2.5 Features of the system
Sends e-mails (if enabled and internet is available) to the newly registered
members of the system as a notification and also sends e-mails in different
modules.
Maximum amount of training is required to use the system.
Saves the errors occurred in the system in a file that can be used to
troubleshoot the problems.

It is very user friendly

2.6 System Requirements

To be used effectively, all computer software needs certain hardware components


or software resources to be present on computer the perquisites are known as
system requirements. The MIS project requires a certain minimum system
requirement

HARDWARE

128 MB of RAM or higher recommended (64 MB minimum supported).

Super VGA (1024 X768) or higher resolution video adapter and monitor.

Keyboard and Microsoft mouse or compatible pointing device.

SOFTWARE

OS: Windows XP minimum or higher.


Internet Explorer 8

LANGUAGE

Hyper Text Mark up Language(HTML)


Technologies used:

FRONT END:
User interface or that part of a software of website that a user sees on the
screen, and acts on to enter commands or to access other parts of the
software or website is known as front end.

HTML/FRONT PAGE

It is front page of the website

Features

Some of the features in the last version of FrontPage include:

FrontPage 2003 consists of a Split View option to allow the user to code in
Code View and preview in Design View without the hassle of switching
from the Design and Code View tabs for each review.

Dynamic Web Templates (DWT) were included for the first time in
FrontPage 2003 allowing users to create a single template that could be used
across multiple pages and even the whole Web site.

Interactive Buttons give users a new easy way to create Web graphics for
navigation and links, eliminating the need for a complicated image-editing
package such as adobe Photoshop.

The accessibility checker gives the user the ability to check if their code is
standards-compliant and that their Web site is easily accessible for people
with disabilities. An HTML optimizer is included to aid in optimizing code
to make it legible and quicker to process.

Intellisense, which is a form of auto completion , is a key feature in


FrontPage 2003 that assists the user while typing in Code View. When
working in Code View, Intelligence will suggest tags and/or properties for
the code that the user is entering which significantly reduces the time to
write code. The Quick Tag Editor shows the user the tag they are currently
in when editing in Design View. This also includes the option to edit the
specific tag/property from within the Tag Editor.

Code Snippets give users the advantage of creating snippets of their


commonly used pieces of code allowing them to store it for easy access
whenever it is next needed.

FrontPage 2003 includes support for programming in ASP.Net a server side,


scripting language that adds interactivity to Web sites and Web pages.

FrontPage 2003 includes support for macros in VBA

SCRIPTING LANGUAGE
A scripting language or script language is a programming language that
supports the writing of scripts. Environments that can be automated through
scripting include software applications, web pages within a web browser, the
shells of operating systems (OS), and several general purpose and domain-specific
languages such as those for embedded systems. Scripting is usually a property of
the primary implementations of a language, rather than a language per se, although
many languages are not very suited to this kind of implementation. For example,
C++ interpreters do exist, but C++ is generally not considered a scripting
language, as not only are these implementations rarely used, but the time taken to
write a script in C++ would be far in advance of that required to write in a
language like Python.

Typically, a scripting language is characterized by the following properties:

Ease of use. Scripting languages are intended to be very fast to pick up and
author programs in. This generally implies relatively simple syntax
&semantics.

OS facilities - especially file system and related, built in with easy


interfaces. Scripting is usually aimed at desktop, limiting the portability
needs of the pre-built libraries.
Interpreted from source code - to give the fastest turn around from script to
execution. On a desktop, the performance of even a slow interpreter is often
non-problematic. In comparison, non-scripting languages intended for large
programs are often precompiled in at least some sense for superior
performance.

Relatively loose structure. It would be difficult to use java as a scripting


language due to the rules about which classes exist in which files - contrast
to Python, where it's possible to simply define some functions in a file.

VBSCRIPT
VBScript (Visual Basic Scripting Edition) is an Active Scripting language
developed by Microsoft that is modeled on Visual Basic. It is designed as a
lightweight language with a fast interpreter for use in a wide variety of
Microsoft environments. VBScript uses the Component Object Model to access
elements of the environment within which it is running; for example, the File
System Object (FSO) is used to create, read, update and delete files

JAVA SCRIPT
A scripting language developed by Netscape to enable Web authors to design
interactive sites. Although it shares many of the features and structures of the full
Java language, it was developed independently. Java script can interact with
HTML source code, enabling Web authors to spice up their sites with dynamic
content. JavaScript is endorsed by a number of software companies and is an open
language that anyone can use without purchasing a license. It is supported by
recent browsers from Netscape and Microsoft, though Internet Explorer supports
only a subset, which Microsoft calls Jscript.

BACK END:
Back end languages are the languages used to write the parts of the program used
to interact with the hardware. Thus game engines, browser engines and so forth
are often written in C++ because first it is a compiled language which provides
straightforward tools for modeling any device logically you don't already have a
driver for and because it has many features of data security which make it easier to
keep track of many variables.
DATABASE
Database are designed to offer an organized mechanism for storing,
managing and retrieving information. They do so through the use of tables.
If youre familiar with spreadsheets like Microsoft Excel, youre probably
already accustomed to storing data in tabular form. Its not much of a stretch
to make the leap from spreadsheets to databases.
CHAPTER 3 SYSTEM ANALYSYS
& METHODOLOGY ADOPTED

3.1 Use Case Diagrams

A use case diagram at its simplest is a representation of a user's interaction with the
system and depicting the specifications of a use case. A use case diagram can
portray the different types of users of a system and the various ways that they
interact with the system. This type of diagram is typically used in conjunction with
the textual use case and will often be accompanied by other types of diagrams as
well.

While a use case itself might drill into a lot of detail about every possibility, a use-
case diagram can help provide a higher-level view of the system. It has been said
before that "Use case diagrams are the blueprints for your system".They provide
the simplified and graphical representation of what the system must actually do.

Use case diagrams depict:

Use cases. A use case describes a sequence of actions that provide

something of measurable value to an actor and is drawn as a horizontal

ellipse.

Actors. An actor is a person, organization, or external system that plays a


role in one or more interactions with your system. Actors are drawn as stick
figures.

Associations. Associations between actors and use cases are indicated in use
case diagrams by solid lines. An association exists whenever an actor is
involved with an interaction described by a use case. Associations are
modeled as lines connecting use cases and actors to one another, with an
optional arrowhead on one end of the line. The arrowhead is often used to
indicating the direction of the initial invocation of the relationship or to
indicate the primary actor within the use case. The arrowheads are typically
confused with data flow and as a result I avoid their use.

System boundary boxes (optional). You can draw a rectangle around the
use cases, called the system boundary box, to indicates the scope of your
system. Anything within the box represents functionality that is in scope and
anything outside the box is not. System boundary boxes are rarely used,
although on occasion I have used them to identify which use cases will be
delivered in each major release of a system.

Packages (optional). Packages are UML constructs that enable you to


organize model elements (such as use cases) into groups. Packages are
depicted as file folders and can be used on any of the UML diagrams,
including both use case diagrams and class diagrams. I use packages only
when my diagrams become unwieldy, which generally implies they cannot
be printed on a single page, to organize a large diagram into smaller ones.

3.1.1 Use Case Diagram


USE CASE DIAGRAM:
CUSTOMER
SURFING
CONTACT
INFORMATION
REGISTERATION
3.2. Entity Relationship Diagram
It is a detailed logical representation of data for an organization and uses three
main constructs.

Entities
It is a fundamental thing about which data may be maintained. Each entity has its
own identity.

Entity Type is the description of all entities to which a common definition and
common relationships and attributes apply.

3.3 Normalization

Normalization usually involves dividing a database into two or more tables and
defining relationships between the tables. The objective is to isolate data so that
additions, deletions, and modifications of a field can be made in just one table and
then propagated through the rest of the database via the defined relationships.

There are three main normal forms, each with increasing levels of normalization:

First Normal Form (1NF): Each field in a table contains different information.

Second Normal Form (2NF): Each field in a table that is not a determiner of the
contents of another field must itself be a function of the other fields in the table.

Third Normal Form (3NF): No duplicate information is permitted.


CHAPTER 4 SOFTWARE DESIGN

HOME page >> welcome to your site


On clicking the home page a page will open which will tell about the site and
training

At homepage we will find the links of


About Us
Products
Offers
Contact us
Feedback
CHAPTER 5 TEST REPORT

Executing a program with the intent of finding errors is called testing. Testing is
vital to the success of any system. Testing is done at different stages within the
development phase. System testing makes a logical assumption that if all parts of
the system are correct, the goals will be achieved successfully. Inadequate testing
or no testing at all leads to errors that may come up after a long time when
correction would be extremely implementation. The testing of the system was done
on both artificial and live data. In order to test data test cases are developed.
Following are the various methods that are employed for testing:

5.1 WHITE-BOX TESTING

White-box testing (also known as clear box testing, glass box testing, transparent
box testing and structural testing) tests internal structures or workings of a
program, as opposed to the functionality exposed to the end-user. In white-box
testing an internal perspective of the system, as well as programming skills, are
used to design test cases. The tester chooses inputs to exercise paths through the
code and determine the appropriate outputs. This is analogous to testing nodes in a
circuit, e.g. in-circuit testing

While white-box testing can be applied at the unit, integration and system levels of
the software testing process, it is usually done at the unit level. It can test paths
within a unit, paths between units during integration, and between subsystems
during a systemlevel test. Though this method of test design can uncover many
errors or problems, it might not detect unimplemented parts of the specification or
missing requirements.
Techniques used in white-box testing include:

API testing (application programming interface) testing of the application


using public and private APIs
Code coverage creating tests to satisfy some criteria of code coverage (e.g.,
the test designer can create tests to cause all statements in the program to be
executed at least once)

Fault injection methods intentionally introducing faults to gauge the efficacy


of testing strategies

Mutation testing methods

Static testing methods

Code coverage tools can evaluate the completeness of a test suite that was created
with any method, including black-box testing. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important
function points software metric

Function coverage, which reports on functions executed

Statement coverage, which reports on the number of lines executed to


complete the test

100% statement coverage ensures that all code paths or branches (in terms of
control flow) are executed at least once. This is helpful in ensuring correct
functionality, but not sufficient since the same code may process different
inputs correctly or incorrectly.

5.2 BLACK-BOX TESTING

Fig. 4: Black box diagram

Black-box testing treats the software as a "black box", examining functionality


without any knowledge of internal implementation. The tester is only aware of
what the software is supposed to do, not how it does it. Black-box testing methods
include: equivalence partitioning, boundary value analysis,all-pairs testing, state
transition tables, decision table fuzz testing, model-based testing, use case
exploratory testing
Specification-based testing aims to test the functionality of software according to
the applicable requirements. This level of testing usually requires thorough test
cases functional non-functional, though usually functional.

Specification-based testing may be necessary to assure correct functionality, but it


is insufficient to guard against complex or high-risk situations.

One advantage of the black box technique is that no programming knowledge is


required. Whatever biases the programmers may have had, the tester likely has a
different set and may emphasize different areas of functionality. On the other
hand, black-box testing has been said to be "like a walk in a dark labyrinth without
a flashlight." Because they do not examine the source code, there are situations
when a tester writes many test cases to check something that could have been
tested by only one test case, or leaves some parts of the program untested.

This method of test can be applied to all levels of software testing: unit,
integration, system acceptance. It typically comprises most if not all testing at
higher levels, but can also dominate unit testing as well.
CHAPTER 6 MY ROLES & RESPONSIBILITIES

Being the leader of my team I was given the following responsibilities:-

Divide the work among the team members.

I was involved in requirement gathering with other team members .

I was responsible for coding, designing , implementation and unit testing of


modules.

I was involved in combining all modules of the professional training website


CHAPTER 7 CONCLUSION & ACHIEVEMENTS

The reason to have professional training system is to providing professional


courses, vocational training ,improve skills through internet and institutions itself.
it also saves time of students who do not want to waste time going here and there.

The project is still going on. We have released the first stable version as per our
project schedule & the work on the next version is in progress.

Achievements

The project has been an excellent learning opportunity for me and has
helped me in understanding and developing a live project.

Technical Knowledge is something one can always get sitting at home and
devouring books. But being a part of a team which is working on a
deliverable Live Project means a lot more other things apart from the
technical knowledge gained.

I learnt to implement hardware devices in the system.

I learned its the team work and working in tandem with the team,
complimenting the team efforts that hold more priority than individual
skills.

I learned how important deadlines are, and that clients are like gods, we just
have to provide them what they want .The ultimate goal is to meet clients
requirements.

I learned to take responsibilities and to handle the work pressure.


CHAPTER 8 BIBLIOGRAPHY

Books consulted:-

Essentials of dream weaver

Introduction to HTML

Websites and URLs:-

http://www.lg.com/in
http://en.wikipedia.org/wiki/LG_Corp
http://www.gsmarena.com/lg-phones-20.php
http://in.lgworld.com/index.jsp

You might also like