Gangada Lokesh Project On Implementation of Product Lifecycle Management System With Special Reference To SAP 19 Apr 2023
Gangada Lokesh Project On Implementation of Product Lifecycle Management System With Special Reference To SAP 19 Apr 2023
ON
IMPLEMENTATION OF PRODUCT LIFECYCLE
MANAGEMENT SYSTEM WITH SPECIAL REFERENCE
TO SAP
SUBMITTED BY:
GANGADA LOKESH
ENROLLMENT NO. 21A1016856
SPECIALIZATION: BUSINESS ANALYTICS
SUBMITTED TO:
I Gangada Lokesh, certify that this project work titled “Implementation of Product
Lifecycle Management System with special reference to SAP” submitted by me for
the partial fulfilment of the requirement for the award of Post Graduate Diploma In
Management is my own bonafide work and carried out by me under the supervision of
Mr. Ampilli Sambhu. The work embodied in this project report has not been submitted
for the award of any other degree or diploma to any Institute or University.
I hereby declare that I have faithfully acknowledged and given credits to published work
that I have referred from other published sources, by citing and mentioning the credits in
bibliography. I further declare that the work presented in this report is original and has
not been copied from any other sources. If my work is found copied or plagiarized, the
institution holds the right to reject my submitted project report.
Date: 19/04/2023
Gangada Lokesh
21A1016856
ii
CERTIFICATE
This is to certify that Mr. Gangada Lokesh, a Student of IMT- Centre for
Distance Learning, Ghaziabad has completed the project work on
“Implementation of Product Lifecycle Management System with special
reference to SAP” under my guidance and supervision.
I certify that this is an original work and has not been copied from any
source.
(Signature of Guide)
Mr. Ampilli Sambhu
Email ID:
sambhu.ampilli@jsw.in
iii
ACKNOWLEDGEMENT
I would like to give my sincere thanks to a host of friends and the teachers who, through
their guidance, enthusiasm and counselling helped me enormously. Apart from this, I
hope this study paper would stimulate the need of thinking and discussion on the topics
like this one.
Gangada Lokesh
21A1016856
iv
EXECUTIVE SUMMARY
This report is prepared during training is life’s greatest learning experience, as it is full of
learning, knowledge into a practical implementation. This period also provide a chance to
give theoretical knowledge into a practical shape. This report is a result of four months
that I have spends on this project.
I whole heartedly thank the organization as well as their IT Department for giving me the
opportunities to work on the latest technology & bringing out the best in me and
developing my talent & improving my skills, not only in the technical field but also in my
over personality. CO-operating and assisting each other in the department helped me to
explore my potential & perform much better
This report deals with the management of requests send for the change in the application.
I have also included the screenshots so that it would become easier to understand the
working.
v
TABLE OF CONTENTS
Declaration ............................................................................. ii
Acknowledgement ................................................................. iv
1. Introduction ............................................................................ 1
7. Bibliography/References ....................................................... 70
vi
INTRODUCTION
Introduction
Product Life Cycle Management is software that deals to automate the service provider
organizations. It deals to maintain job card, customer’s problem and make report according to the
requirement. The major part of the project is to deal with product and provide satisfaction to
customers. At the time of product purchase, Company provide product Id that works like a
primary key and at the time of service, we make transactions on this key.
Other module of the project is to keep the track record of engineer’s through engineer id and
record every day cases done by engineer. Another phase of the project is Spare parts, software
deal with this module.
Problem statement
In order to avoid any confusion, our work is not addressing all PLM deployment but system
engineering framework for PLM integration. In this respect, our approach is on the linkage
between product and enabling product. Actually SE (System Engineering) offers the possibility
to link the development of product and the development of enabling product in a unified
framework. Hence the PLM offers such integration solution to design and implement the linkage
approach and the implementation approach. This work is a part of a project in deploying systems
engineering; we address two issues; the first one is on maintenance and the second is on PLM
which is the subject in this paper; our PLM is seen as sub product in the manufacturing structure
and also as a tool for the linkage concept in systems engineering.
The Need!
Product Life Cycle Management (PLM) is to automate an L.G. Product service center which
provides it’s customer with all repair/maintenance facilities for the Products owned by them. The
service centre offers many different jobs for passenger cars, which include Product painting,
washing, basic servicing, wheel alignment, repairs etc. Around 100-130 customers visit the
service centre on daily basis. The customers ask for different types of jobs and the company thus
1
has to ensure the quality of job done and timely delivery of the Product to customer’s
satisfaction.
Earlier, there was no automated process to organize the series of activities that take place. The
customer has to wait for a long time to be entertained by an executive. An executive could not
differentiate which customer to entertain first. There was no procedure to monitor the efficiency
of the workers. Long queue used to exist, just for getting the invoice. There was no process
which could recheck the work that has been done for a particular Product (when required, the
official would browse through all the slips and related documents. This was error-prone and time
consuming).
Despite of heavy investment and all modern facilities, the company faced decline in sales and
profits.
2
COMPANY PROFILE
Historical references include Systems, Applications, and Products in Data Processing, SAP
AG and SAP SE.
Company overview
3
Europaea (SE); as such, its former German corporate identity is now a subsidiary, SAP
Deutschland SE & Co. KG.
History
Formation
When Xerox exited the computer hardware manufacturing industry in 1971, it asked IBM to
migrate its business systems to IBM technology. As part of IBM's compensation for the
migration, IBM was given the rights to the Scientific Data Systems (SDS)/SAPE software,
reportedly for a contract credit of $80,000.
Five IBM engineers from the AI department (Dietmar Hopp, Klaus Tschira, Hans-Werner
Hector, Hasso Plattner, and Claus Wellenreuther, all from Mannheim, Baden-Württemberg) were
working on an enterprise-wide system based on this software, only to be told that it would no
longer be necessary. Rather than abandoning the project, they decided to leave IBM Tech and
start another company.
In June 1972, they founded the SAP Systemanalyse und Programmentwicklung ("System
Analysis and Program Development" / "SAPD") company, as a private partnership under the
German Civil Code.
Their first client was the German branch of Imperial Chemical Industries in Östringen, where
they developed mainframe programs for payroll and accounting. Instead of storing the data
on punch cards mechanically, as IBM did, they stored it locally in the Electronic System while
using a common Logical database for all activities of Organization. Therefore, they called their
software a real-time system, since there was no need to process the punch cards overnight (for
this reason their flagship product carried an R in its name until the late 1990s). This first version
was also a standalone software that could be offered to other interested parties. [
4
Enterprise resource planning
In 1973, the first commercial product was launched. SAP completed its first financial
accounting system - RF. This system served as the cornerstone in the ongoing development of
other software modules of the system that eventually bore the name SAP R/1. This offered a
common system for multiple tasks. This permitted the use of a centralized data storage,
improving the maintenance of data. From a technical point of view, therefore, a database was
necessary.
In 1976, SAP GmbH Systeme, Anwendungen und Produkte in der Datenverarbeitung ("Systems,
Applications, and Products in Data Processing") was founded as a sales and support subsidiary.
Five years later, the private partnership was dissolved and its rights were passed on to SAP
GmbH.
The headquarters moved the following year to Walldorf, Germany. Three years later, in 1979,
SAP launched SAP R/2, expanding the capabilities of the system to other areas, such as material
management and production planning. In 1981, SAP brought a re-designed product to market.
However, SAP R/2 did not improve until the period between 1985 and 1990. SAP released the
new SAP R/3 in 1992. SAP developed and released several versions of R/3 through 1995. By the
mid-1990s, SAP followed the trend from mainframe computing to client–server architectures.
The development of SAP's internet strategy with mySAP.com redesigned the concept of business
processes (integration via Internet). As a result, R/3 was replaced with the introduction of SAP
ERP Central Component (ECC) 5.0 in 2004. Architectural changes were also made to support an
enterprise service architecture to transition customers to a service-oriented architecture. The
latest version, SAP ERP 6.0, was released in 2006. SAP ERP 6.0 has since then been updated
through SAP enhancement packs, the most recent: SAP enhancement package 8 for SAP ERP
6.0 in 2016.
Corporate restructuring
In August 1988, SAP GmbH became SAP AG, and public trading started on 4 November 1988.
Shares were listed on the Frankfurt and Stuttgart stock exchanges. In 1995, SAP was included in
the German stock index DAX and, on 22 September 2003, SAP was included in the STOXX
Europe 50.
5
SAP AG era
The company's official name became SAP AG (a public limited company) after the 2005 annual
general meeting.
SAP SE era
On 21 May 2014, SAP AG announced during the Annual General Meeting of Shareholders that
99% of the shareholder votes approved the conversion of legal form to a European stock
corporation (Societas Europaea, SE) and at the same time, elected the first supervisory board of
SAP SE. The conversion of the company's legal form would take place upon entry in the
commercial register, expected to be in July 2014.
On 7 July 2014, SAP announced it had changed its legal form to a European Company (Societas
Europaea, SE). As a result, its German subsidiary was renamed to SAP Deutschland SE & Co.
KG. The conversion cost the company approximately €4 million.
Focus on cloud
Since 2012, SAP has acquired several companies that sell cloud-based products, with several
multi-billion-dollar acquisitions seen by analysts as an attempt to challenge competitor Oracle. In
2016 SAP bought Concur Technologies, a provider of cloud-based travel and expense
management software, for $8.3 billion, SAP's most expensive purchase to that date. Analysts'
reactions to the purchase were mixed, with Thomas Becker of Commerzbank questioning
whether Concur was the right choice for SAP, while Credit Suisse called the acquisition an
"aggressive" move.
In 2014, IBM and SAP began a partnership to sell cloud-based services. Likewise, in 2015, SAP
also partnered with HPE to provide secure hybrid cloud-based services running the SAP
platform. Both HPE and IBM provide infrastructure services to SAP, and SAP runs its SAP
HANA cloud solution on top. SAP has announced additional partnerships with Microsoft in
order to give customers tools for data visualization, as well as improved mobile applications.
SAP exceeded its revenue projections due to the expansion in its cloud business and the success
of SAP HANA. The growth can also be partially attributed to the acquisitions of Concur and
6
Fieldglass. Since 2017, SAP is a founding member of the EU Cloud Code of Conduct. Since
May 2021 SAP has listed selected Cloud Service adherent to the EU Cloud Code of Conduct as
one of the first Cloud Service Providers.
The company announced plans in 2016 to invest heavily into technology relating to the Internet
of things (IoT) as part of a strategy to capitalize on the growth in that market. For that purpose,
€2 billion is planned for investment in relevant sectors by the end of 2020. SAP will also launch
a new product line called SAP IoT, which "will combine large amounts of data from things
connected to the Internet with machine learning and SAP's real-time database S/4 HANA."
On 29 January 2019, SAP announced plans to cut approximately 4,000 positions at the company
in a strategic plan to shift to more modern cloud-based technologies such as blockchain, quantum
computing, machine learning, Internet of Things, and artificial intelligence.
On 13 April 2021, SAP announced the formation of the joint venture SAP Fioneer, a dedicated
Financial Services Industry (FSI) Unit between SAP and investment company Dediq
GmbH. Dediq GmbH invested over €500 million in the newly formed unit and received an 80
percent share in return. SAP brought its products, organizational units and the sales network into
the business and holds 20 percent of the shares.
Products
o By Category
Financial Management
Spend Management
Business Network
7
Human Capital Management
Sustainability Management
o By Industry
Automotive
Banking
Consumer Products
Retail
Artificial Intelligence
Integration
8
SAP Store
Success Experiences
Success Extensions
Success Services
My Support Overview
Knowledge Base
Product Support
Software Downloads
Maintenance 2040
9
Business and markets
As of 2016, SAP is the world's fourth-largest software and programming company. The
corporation operates in Europe, Asia, Africa, the Middle East, North America, and South
America.
SAP focuses on 25 industries and six industry sectors: process industries, discrete industries,
consumer industries, service industries, financial services and public services. It offers integrated
product sets for large enterprises, mid-sized companies and small businesses.
Partnerships
SAP partners include Global Services Partners with cross-industry multinational consulting
capabilities, SAP University Alliances, Global Software Partners providing integrated products
that complement SAP Business Suite solutions, and Global Technology Partners providing user
companies with a wide range of products to support SAP technology, including vendors of
hardware, database, storage systems, networks, and mobile computing technology.
Extensions partners are companies which provide functionality that complements SAP product
capabilities. Their products are certified, sold, and supported by SAP. These partner companies
include Adobe, CA Technologies, GK Software, Tricentis, Hewlett-Packard, IDS
Scheer, Mendix, OpenText, Knoa Software, and BackOffice Associates.
SAP has also partnered with Apple to work on the mobile experience for SAP enterprise
customers. As part of the partnership, a new SAP HANA Cloud Platform SDK would be
delivered exclusively for iOS. As a result, developers can build applications based on the SAP
HANA Cloud Platform for the iPhone and iPad devices. The partnership was announced in May
2016.
In 2019, SAP announced a three-year partnership "Embrace" with Microsoft that should allow its
clients to move their business process into the cloud, although significant portions of that
partnership were reduced to two years. SAP teams up on cloud sales with Microsoft
In 2020 SAP announced that together with Wipro it will co-develop and market "solutions for
the retail and fashion industry."
10
Organization
SAP uses a two-tier structure of boards, with an executive board and a supervisory board. In
October 2019, Jennifer Morgan and Christian Klein were appointed as co-CEOs of SAP. In April
2020, it was announced that Jennifer Morgan will leave SAP and Christian Klein will continue to
operate as the sole CEO, citing that the current environment of the COVID-19 recession requires
"companies to take swift, determined action which is best supported by a very clear leadership
structure".
The majority of the company's employees are in Germany and United States. About 20,000
employees are based in Germany and about 19,311 employees are based in the United States.
In 2022, 45 employee representatives were elected to the SAP SE Works Council, including 15
candidates from the Ver.di and IG Metall trade union lists. They represent 17,000 employees of
Germany.
Headquarters is responsible for overall management as well as core engineering activities related
to product development. Worldwide customer support is not provided by the field organizations
but by a unified organization called Active Global Support (AGS).
11
LITERATURE REVIEW
SYSTEM ANALYSIS
The system analysis is the most important part in the software development life cycle. It is the
first stage in the software development life cycle. The system analysis should be conducted with
the following objectives in the mind:
Allocate function to hardware, software, people, database and other system element.
Presently the product life cycle management system is being maintained manually.
At first concerned customer has to fill the complete information manually and the service
center has to keep it in the record. The result is the wastage of time and demands more
paper work.
If concerned officer demand for certain information all the information is to be searched
in order to get the right information, the result wastage of time.
Since all the information is filled manually, there are certain problems in the existing system.
These are as follows:
12
Different records are maintained regarding their profile and present status.
Proposed System
It is felt significant can be brought about by a comprehensive system, which integrated the entity
core and peripheral system with a single point entry of data. The proposed system has the
following advantage over the existing manual system:
As the present system is web based, the controlling officer can view the profile and
present status with the help of the computer terminal which is connected to Product Life
Cycle Management System internet.
Since all the records are maintained in the database, it is easy for an official to update any
information easily.
A better security is provide at login level so that a user authorized to view the reports can
only view profile or present status of a report.
One user (Administrator) is given the authority to add/ delete the user according the
requirement of the authorization.
FEASIBILITY STUDY
The result of the feasibility study is a formal proposal. This is simply report-a formal document
detailing the nature and the scope of the proposed solution. The proposals summarize what is
known and what is going to be done. Three key considerations are involved in the feasibility
analysis: economic, technical and operational behavior.
Economic Feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness of a
candidate system. More determine the benefits and the saving that are expressed from a
candidate system and compare those costs. If benefits outweigh costs. Otherwise, further
13
justification or alterations in the proposed system will have to be made if it is to have a chance of
being approved. This is an ongoing effort that improves in accuracy at each phase of the system
life cycle.
Technical Feasibility
Technical feasibility center on the existing computer system hardware etc. and to what extent it
can support the proposed addition. For example, if the current computer is operating at 80%
capacity - an arbitrary ceiling – then running another application could over load the system or
require additional hardware. This involves financial consideration to accommodate technical
enhancements. If the budget is a serious constraint then the project is judged not feasible.
Operational Feasibility
It is common knowledge that computer installations have some thing to do with turnover,
transfers, retraining and changes in employee job status. Therefore, it is understandable that the
introduction of a candidate system requites special efforts to educate, sell, and train the staff on
new ways of conducting business.
Choice of Platform?
In any organization a lot of data is generated as result of day-to-day operations. In the past, all
kind of data – be it business of a company. Since the task was performed manually, it was time
consuming and error prone. With the advent of computer, the task of maintaining large amount
of data has undergoes a sea change.
Today computer system have become so user friendly that even first time users can create their
own application with the help of tools such as MS-Access, Fox-Pro and SQL Server. These tools
are very visual and hence user friendly. They provide a point and click environment for building
applications that can interact with large amount of data.
14
SOFTWARE REQUIREMENT SPECIFICATION
This system was developed under window 2000XP/Windows 2000 NT. It is complete with all
32-bit versions of windows operating system. Windows is a popular and largest used operating
system in the world because it is easy to understand and provides an easy interface to users.
The .NET Framework is a new computing platform that simplifies application development in
the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the
following objectives:
15
1. To provide a consistent object-oriented programming environment whether object code is
stored and executed locally, executed locally but Internet-distributed, or executed
remotely.
5. To make the developer experience consistent across widely varying types of applications,
such as Windows-based applications and Web-based applications.
6. To build all communication on industry standards to ensure that code based on the .NET
Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and the .NET
Framework class library.
The common language runtime manages memory, thread execution, code execution, code safety
verification, compilation, and other system services. These features are intrinsic to the managed
code that runs on the common language runtime.
With regards to security, managed components are awarded varying degrees of trust, depending
on a number of factors that include their origin (such as the Internet, enterprise network, or local
computer). This means that a managed component might or might not be able to perform file-
access operations, registry-access operations, or other sensitive functions, even if it is being used
in the same active application.
16
The runtime enforces code access security. For example, users can trust that an executable
embedded in a Web page can play an animation on screen or sing a song, but cannot access their
personal data, file system, or network. The security features of the runtime thus enable legitimate
Internet-deployed software to be exceptionally featuring rich.
The runtime also accelerates developer productivity. For example, programmers can write
applications in their development language of choice, yet take full advantage of the runtime, the
class library, and components written in other languages by other developers. Any compiler
vendor who chooses to target the runtime can do so. Language compilers that target the .NET
Framework make the features of the .NET Framework available to existing code written in that
language, greatly easing the migration process for existing applications.
The runtime is designed to enhance performance. Although the common language runtime
provides many standard runtime services, managed code is never interpreted. A feature called
just-in-time (JIT) compiling enables all managed code to run in the native machine language of
the system on which it is executing. Meanwhile, the memory manager removes the possibilities
of fragmented memory and increases memory locality-of-reference to further increase
performance.
The .NET Framework class library is a collection of reusable types that tightly integrate with the
common language runtime. The class library is Object Oriented, providing types from which
your own managed code can derive functionality. This not only makes the .NET Framework
types easy to use, but also reduces the time associated with learning new features of the .NET
Framework. In addition, third-party components can integrate seamlessly with classes in the
.NET Framework.
17
.NET Framework to develop the following types of applications and services:
Console applications.
ASP.NET applications.
Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that vastly
simplify Windows GUI development. If you write an ASP.NET Web Form application, you can
use the Web Forms classes.
The following illustration shows a basic network schema with managed code running in different
server environments. Servers such as IIS and SQL Server can perform standard operations while
your application logic executes through the managed code.
18
ASP.NET is the hosting environment that enables developers to use the .NET Framework to
target Web-based applications. However, ASP.NET is more than just a runtime host; it is a
complete architecture for developing Web sites and Internet-distributed objects using managed
code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing
mechanism for applications, and both have a collection of supporting classes in the .NET
Framework.
Microsoft the No. one company in the software that produces the most widely used, front end
and Server based Multi user RDBMS. The SQL Server is a program installed on the Server’s
hard disk driver. This program must be loaded in RAM so that it can process user requests. The
SQL Server Server product is either called SQL Server Professional or SQL Server Enterprise.
Optimizing queries.
4. System Design
The most creative and challenging phase of the system life cycle is system design. The term
design describes a final system and the process by which it is developed. It refers to the technical
specifications that will be applied in implementing the candidate system.
19
The first step is to determine how the output is to be produced and in what format.
Samples for the output (and input) are also presented.
The second step is input data and master files (data base) have to be designed to meet the
requirements of the proposed output.
The operational (processing) phases are handled through program construction and testing
including a list of the programs needed to meet the system’s objective and complete
documentation. Finally, details related to justification of the system on the user and the
organization are documented and evaluated by management as a step toward implementation. To
design the system we must note the following points:
In this component the software components and relevant interfaces such as, interactions with
existing internal and external systems, network connections, and standard input an output
formats are to be identified.
Network Connections.
Program Specification:
20
Function called.
Program Security.
Field Details.
Program Functions.
From Analysis
Detailed
System
Output Cost
Documentation
Design Justification
and Candidate
design
Input Design
Design submitted to
management
for approval
File
Design
Processing No
Design Abandon project
Design accepted
Yes
Test
Programs
21
STEPS IN SYSTEM DESIGN
Databases and database technology are having a major impact on the growing use of computers.
It is fair to say that databases will play critical role: in almost all areas where computers are used.
Including business, engineering, medicine, law, education and library, science to name a few. A
database is a collection of related data. By data we mean known facts that can be recorded and
that have implicit meaning for example, consider, the names, telephone numbers and addresses
of the people you know. You may have recorded this data in an indexed address, book, or you
may have stored it on a diskette. Using a personal computer and software such as DBASE IV or
V,PARADOX, MS EXCEL OR MS ACCESS. This is a collection of related data with an
implicit meaning and hence is a database.
A database represents some aspects of the real world. Sometimes called the mini-world or the
universe of discourse (UOD). Changes to the mini-world are reflected in the database.
A database is designed, built and populated with data for the specific people. It has an intended
group of users and some preconceived applications in which the users are interested.
A database can be of any size and of varying complexity. For example, the list of names and
addresses referred to earlier may consist of only a few hundred records, each with simple
structure. On the other hand the card catalog of a large library may contain half a million cards
stored under different categories by primary author’s last name, by subject, by book title with
each category organized in alphabetic order.
A database may be generated and maintained or by machine. The library card catalog is an
example of a database that may be created and maintained either by a group of application
programs written specially for that task or by a database management system.
A database management system (DBMS) is a collection of programs that enables users to create
and maintained a database. The DBMS is hence a general-purpose software system that facilities
tile processed of defining, constructing and manipulating database for various applications.
Defining a database involves specifying the data types, structures and constraints for the data to
22
be stored in the database. Constructing the database is the process of storing the data itself on
some storage medium that is controlled by the DBMS. Manipulating a database includes such
functions as querying the database to reflect changes in the mini-world, and generating reports
form the data.
With the advent of the graphical operating system like windows, the world of imputing went
through a dramatic change. It opened up a whole new world of graphics. Interfaces that use
graphics came to known so graphical user interface (GUI). These became very popular because
the users could identify with images than words. Mention tile word print to a person and it
invokes the image of a printer. The primary requirements for an interface are that it is easy to
use. We must be able react intuitively to an interface presented to us. This is possible if the
interface presented is such that is it emulates real life.
Table Description
Employee details of employee
Customer details of customers
Product details of products
Entry Tag information of entries
Job Order information of job performs
Assignment details of assigned job
Part Consumed information of consumed parts
Invoice keeps bill information
Job details of jobs
Part details of available parts
23
Employee :
This table maintains the information of all the employees working in the service center.
24
Customer :
This table deals with the information of all the customers who visits the service center for their
problems.
25
Product:
This table keeps the information of the products.
Entry Tag :
This table keeps the information of the entry tag, issued to each customer for the solution of their
problems.
26
Job Order :
This table is used to maintain the information of job orders issued by the service center.
27
Assignment :
This table maintains the information of all assignments which was given to an engineer by
another employee of the service center.
28
Parts Consumed :
This table keeps the information of all parts consumed by each product.
Invoice :
This table keeps the information of all bills paid to the service center.
29
Job :
This table is used to store the information of all jobs performed at the service center.
Parts :
This table maintains the information of all parts available at the service center.
30
Relation among Tables
31
CONTEXT DIAGRAM
Admin/login
Approval Access
Product life
cycle
Enquiry Enquiry
management
CUSTOMER Feed back Response
EMPLOYEE
SYSTEM
Purchase order
Goods supplied
Product service request
Serviced goods
32
LEVEL ‘1’ DFD
Enquiry
Access Response 2.0
Admin/login
Approval
Employee
validation
process
11
Enquiry 1.0 Response
CUSTOMER Feedback Enquiry Employee
Product
Purchase order
service
Goods supplied
automation
Product service request
Serviced goods
33
LEVEL ‘2’ DFD
Request
Access Enquiry Response Database
Admin/login 2.0
Approval Response
Employee
validation
process
Enquiry Enquiry
Feedback Data
CUSTOMER 1.0 Employee
Purchase order Response
Order supplied Product request
Product service request service tag generated
automation
Request response
Database
D
1.2
Request retrieve 1.1 request a request
Tag entry
Request request t request
Service / process
Retrieve a retrieve
Repair
Serviced Goods b
Process a
s
e
34
LEVEL ‘3’ DFD
Database
Database 2.1
Job status
Admin/login
2.0
Employee
validation
process
1.0
CUSTOMER Employee
Product
service
automation
Database
1.3 1.5
Invoice Report
generation generation
1.1
Service/
Database Response repair
1.2
process
Request
Goods
purchased
process
Database
Database
1.2.1
1.4
35 Shipment
Tag entry process
process
DATAFLOW CHART
CUSTOMER
64800
Brings
Product
97200
Is Issued
ENTRY TAG
INVOICE
Is Billed
On 60
21600
PART
Is Issued
On 2000
COMPLAINT
Is
64800 Consumed
JOB ORDER For
Records
21600
X:
36
X:
Engg JOB
ASSIGNMENT
72
90
37
38
ER-DIAGRAM
City
Street
Customer id
State
Product no M
date
Product Modal
Brings First Last
date
Customer id
brand M
Product Make
Product
1
Invoice Total
Is Issued
Cost
Date
Date 1 Entry Tag No
Part Description
Date 1
Part Charges
1
Is Issued
On PART
ORORDER
M
Date Part id
M Quantity
Is Consumed
for
1
JOB ORDER
fof _For
ORORDER Date
Job Order ID
Job order Time est
39 X:
Job Charges
Employee_Name X:
Job Description
Employee_Designation
1 1
EMPLOYEE ASSIGNMENT JOB
Assignment By
Assignment Completion time
Assignment To
Assignment Completion Date
Assignment Time
Assignment_Date
6. SYSTEM IMPLEMENTATION
Implementation is the process of having systems personnel check out and put new equipment
into use, train users, install the new application and construct any files of data needed to use it.
This phase is less creative than system design. Depending on the size of the organization that
will be involved in using the application and the risk involved in its use, systems developers may
choose to test the operation in only one area of the firm with only one or two persons.
Sometimes, they will run both old and new system in parallel way to com-pare the results. In still
other situations, system developers stop using the old system one day and start using the new one
the next.
40
EVALUATION
The evaluation phase ranks vendor proposals and determines the one best suited, Evaluation of
the system is performed to identify its strengths and weaknesses. The actual evaluation can occur
along any of the following dimensions:
Operational Evaluation: Assessment of the manner in which the system functions, including case
of use, response time, overall reliability and level of utilization.
User Manager Assessment Evaluation of the attitudes of senior and user manager within
the organization, as well as end-users.
TESTING
Testing plays a critical role in quality assurance of the software. Testing is a dynamic method for
verification and validation. With the help of testing we observe the failure of the system in terms
of logical and runtime errors. The testing process can deduce the presence of fault in the system;
however, separate activities have to be performed to identify the faults.
As the goal of testing is to detect any errors in the programs, different flavor of testing are often
used. Unit testing are used to test module or a small collection of modules and the focus is on
detecting coding errors in modules. During integration testing modules are combined into sub-
41
system, which are then tested. The goal here is to test the system design. In system testing and
acceptance testing, the entire system is tested. The goal here is to test the fulfillment of the
requirement. Structural testing can be used for unit testing while at higher level mostly functional
testing is used.
The objective for test case design is to derive asset of test that has the highest likelihood for
uncovering errors in the software. To accomplish this objective, two different categories of test
case design techniques are used. White-box testing and black-box testing.
White-box test focuses on the program control structure. Test cases are derived to ensure that all
statement in the program has been executed at least once during testing and that all logical
conditions have been exercised. Basic path testing, a white box technique, makes use of program
graphs (or graph matrices) to derive the set of linearly independent test that will ensure coverage.
Condition and data flow testing further exercising degrees of complexity.
Black-box test are designed to uncover errors functional requirement without regard to the
internal workings of a program. Black-box testing techniques focus on the information domain of
the software, deriving test cases by partitioning the input and output domain of a program in
manner that provides through test coverage. The black-box test is used to demonstrate that
software functions are operational, that input is properly produced, and that the integrity of
external information is maintained. A black-box test examines some fundamental aspect of a
system with little or no regard for the integral logical structure of the software.
Graph based testing methods explore the relationship between and behavior of program objects.
Equivalence partitioning divides the input classes of data are likely to exercise specific software
function. Boundary values analysis probes the program’s ability to handle data at the limits of
acceptability.
Specialized testing methods encompass broad arrays of software capabilities and application
areas. Graphical user interface, client/server architectures documentation and help facilities, and
real-time systems each require specialized guidelines and techniques for software testing.
42
Test Information Flow
Software Evaluation
Configuration Test Results
Evaluation
Error Rate Errors
Data
A strategy for software testing may also be viewed in the context of the spiral. Unit testing
begins at the vortex of the spiral and, concentrates on each unit, component of the software as
implemented in source code. Testing progresses moving outward along the spiral to integration
testing, where the focus is on designed the construction of the software architecture. Taking
another turn outward on spiral, we encounter validation testing, where requirements established
as part of software requirements analysis are validated against the software that has been
constructed. Finally, we arrive at system testing, where the software and other system elements
are tested as a whole. To test computer software, we spiral out along stream lines that broaden
the scope of testing with each turn.
Considering the process from a procedural point of view, testing within the context of software
engineering is actually a series of four steps that are implemented sequentially. The steps are
shown in Figure. Initially, tests focus on each component individually, ensuring that it functions
properly as unit. Hence, the name unit testing. Unit testing makes heavy use of white-box testing
43
techniques, exercising specific paths in module’s control structure to ensure complete coverage
and maximum error detection.
Nest, components must be assembled or integrated to form the complete software package.
Integration testing addresses the issues associated with the dual problems of verification and
program construction. Black-box case design techniques are the most prevalent during
integration, although a limited amount of white-box testing may be used to ensure coverage of
major control paths. After the software has been integrated (constructed), a set of high-order tests
conducted. Validation criteria (established during requirements analysis) must be tested.
Validation testing provides final assurance that software meets all functional, behavioral, and
performance requirements. Black-box testing techniques are used exclusively during validation.
MAINTENANCE
The maintenance of existing software can account for over 30 percent of all effort expended by a
development organization, and the percentage continues to rise as more software is produced.
Uninitiated readers may ask why so much maintenance is required and why so much effort is
44
expended. Much of the software we depend on today is on average 10 to 15 years old. Even
when these programs were created using the best design and coding techniques known at the
time and most were not, they were created when program size and storage space were principle
concerns. They were then migrated to new platforms, adjusted for changes in machine and
operating system technology and enhanced to meet new user needs-all without enough regard to
overall architecture.
The result is the poorly designed structures, poor coding, poor logic, and poor documentation of
the software systems we are now called on to keep running. The ubiquitous nature of change
underlies all software work. Change is inevitable when computer-based systems are built;
therefore, we must develop mechanisms for evaluating, controlling, and making modifications.
Software maintenance is, of course, far more than “fixing mistakes.” We may define
maintenance by describing four activities that are undertaken after a program is released for use.
There are four different maintenance activities: collective maintenance, adaptive maintenance,
perfectly maintenance or enhancement, and preventive maintenance or reengineering. Only about
20 percent of all maintenance
Work is spent “fixing mistakes”. The remaining 80 percent is spent adapting existing systems to
changes in their external environment, making enhancements requested by users, and re
engineering an application for future use. When maintenance is considered to encompass all of
these activities, it is relatively easy to see why it absorbs so much effort.
A procedure for protecting systems makes sure that facility is physically secure. Provides
recovery/restart capability, and has access to back up files. Software integrity has become
increasingly important in the age of hackers and firewall the attribute measure a system’s ability
to withstand attack (both accidental and intentional) to its security. Attacks can be made on all
three components of software: program, data and documents.
To measuring integrity, two additional attribute must be defined: threat and security. Threat is
the probability (which can be estimated or derived from evidence) that an attack of specific type
45
will occur within a given time. Security is the probability (which can be estimated or derived
from empirical evidence) that the attack of a specific type will be repelled. The integrity of a
system can then be defined as
Integrity
And security = summation
is summed [(1-threat)
over each type ofx attack.
(1-security)]
If a Web App resides on network, it is open to unauthorized access. In some cases, unauthorized
access may be attempted access for sort, for profit, or with more malevolent intents. A variety of
security measures for provided by the network infrastructure, encryption techniques, firewall,
and other measures.
REPORTS
Report Design is the final section of this project which had covered the following
formalities:
Input design shows how user originated input in converted to a computer-based format. After
input data are identified, approximate input media are selected for processing.
In addition to determining the record media, the analyst must decide how input is entered &
speed of data capture. The fastest method the online data entry through a menu, a formatted
form, or a prompt.
Two approaches to designing data on a CRT screen are manual print layout charts and a software
utility provided by the software vendor.
A form is a physically carrier of data. It can carry authority for action. It is classified by what is
done in the system.
Standards for printed output suggest given output a name title, providing a sample of the layout,
and specifying the procedure the providing the accuracy of output data.
In the designing a form, attention is given to proper identification and wording, readability and
use composition and layout, order of data items and clarity of instructions.
46
Forms classified as flat snap out, fanfold, NCR and preprinted. Fanfold forms are ideal for
computer output.
Forms can be printed on papers of different colors; grades & weights colors distinguish among
copies.
In his project we make all the reports, Crystal Reports which are only system dependent and
when an authorized user wants a printing report then he just to print a particular option for a
particular report the system automatically generates the report and does all the calculation
itself.
47
RESEARCH OBJECTIVES & METHODOLOGY
The staff thus strongly felt the need of a computer system that would assist them to achieve the
following objectives:
To identify the customer needs and the product lifecycle management w.r.t. SAP.
To improve the efficiency and provide better customer care, by abolishing the
possibility of negligence and mismanagement by the service centre.
To maintain all data that can be used for further study and analysis on periodic
basis.
To monitor the sales on periodic basis in order to plan improvement strategies. Keeping above
objectives in mind the solution would automate the existing process right from the entry of
Product in the service centre, till the time of job completion.
48
Research Methodology:
Secondary Data:
News articles,
Journals,
Magazine,
A comprehensive of the collected data will be presented with the help of tables, charts and
graphs.
Tools of analysis:
We will present the data with the help of pie charts and bar charts.
49
DATA ANALYSIS
LOGIN PAGE
50
ADMIN HOME PAGE
51
ADD EMPLOYEE PAGE
52
ADD CUSTOMER PAGE
53
ADD CUSTOMER PAGE
54
MODYFY JOB PAGE
55
GENERATE ENTRY TAG PAGE
56
ADD PRODUCT DETAILS PAGE
57
ADD PRODUCT PAGE
58
CREATE JOB ORDER PAGE
59
CREATE ASSIGNEMENT PAGE
60
CREATE ASSIGNMENT PAGE
61
ADD PART TO PRODUCT PAGE
62
ADD PART TO PRODUCT PAGE
63
BILL DETAILS PAGE
64
INFORMATION PAGE
65
INFORMATION
66
SAMPLE CRYSTAL REPORTS
67
EMPLOYEE ANALYSIS REPORT
68
CONCLUSION & SUGGESTIONS
Conclusion:
1. All the procedure in this project is automatic accept the entry of data from the user.
2. The project gives the user-friendly environment, which gives the way of working in more
efficient manner.
It is connected with the network for easily retrieved data and many
4. All the informat ion can be easily accessed the Customer like their details, booking status,
stock, Transact ion. It can be modify and the others details can be easily provided to
customer.
5. System date for the project is like as backbone for the human, i.e. proposed system is
depends on system date so it must be correct.
69
Suggestions:
Adding new product features or support services to grow your market share
70
BIBLIOGRAPHY
Abramovici, M., Richter, K., Krause, L., and Sieg, O., (2001), “PDMax! – Maximize the
Value of Integrated Product Data Management as a Key for eBusiness,” International
Study by ITM – Ruhr – University Bochum, Germany, and McKinsey&Company, Inc.,
McKinsey Press, Munchen.
Ameri, F. and D. Dutta, (2005), “Product Lifecycle Management: Closing the Knowledge
Loops.,” Computer-Aided Design & Applications”, Vol.2 (5), pp.577-590.
Deif AM. (2011), “A system model for Green manufacturing. Advances in Production
Engineering & Management” 2011; 6(1): 27-36
French, Michael, (1999), “Conceptual Design for Engineers 3rd edition,” 1999, London:
Springer-Verlag, pp. 1
Jayal AD, Badurdeen F, Dillon OW, Jawahir IS”. (2010), Sustainable manufacturing:
Modeling and optimization challenges at the product, process and system levels”. CIRP
Journal of Manufacturing Science and Technology 2010; 2(3): 144-152.
Nasr N, Hilton B, and German R. (2011), “A framework for sustainable production and a
strategic approach to a key enabler: remanufacturing”. In: Seliger G, Khraisheh MMK,
71
Jawahir IS, editors. Advancees in Sustainable Manufacturing. Berlin: Springer-Verlag;
2011. p. 191-196.
Nagl, M., Westfechtel, B., and Schneider, R., (2003), "Tool support for the management
of design processes in chemical engineering," Computers and Chemical Engineering,
Vol. 27, Issue 2, pp. 175- 197.
ASP.NET Unleashed.
http://www.dotnetspider.com
http://www.google.com
https://www.sap.com/india/about/company.html
https://en.wikipedia.org/wiki/SAP
72