SENIOR PROJECT 2007-2008
(Introduction to the ekoSign project)

1. Introduction
Use of XML Signatures to Success
Document Flow in Supply Chain

Project team members

Hüseyin Çakır, Mehmet Mesut Özışık, Yılmaz Kaya

Abstract:This paper gives some brief information about the project in three sections. First section defines
the project name. Second section defines the project objectives and on what motivation the project was
started. Third section describes the importance and benefits of using software engineering standards.
Keywords:Project name, project objectives, project standards.

http://groups.google.com/group/digitalsignature
digitalsignature@googlegroups.com
PRINT DATE: 05/06/08

1
1.1 Introduction
This paper belongs to the inception phase of the unified process and it mainly represents the scope
of the project. Figure 1.1 shows the steps of the unified process and which step the introduction
paper belongs to.
Inception

Elaboration

Construction

Transition

1.Introduction
Figure 1.1 Steps of Unified Process.

1.2 Project Name
This project's name is "Use of XML Signatures to Success Document Flow in Supply Chain".
The ekoSign stands for an acronym name of the project.
1.3 Project Objectives
This project's main goal is to develop a XML based software that:
•
•
•
•

fits the IEEE Software Engineering Standards in terms of documentation and processes,
adopts XML Signature technology to supply chain concept,
allows flow of documents under predefined policies,
applies partial document ownership with motivation to the points that Alok Gupta mentioned
in his research [1].

Following points that Gupta guidelines, using XML signatures provide several advantages to the
business:
•
•
•
•
•

eliminate the need for printing out documents for signing,
reduce storage of paper copies,
improve management and access of electronic versus paper documents,
eliminate of need for faxing or overnight mailing-reduction of cycle time,
enhance management processes outside the “final signature” step.

2
1.4 Project Standards
In this project, Institute of Electrical and Electronics Engineers (IEEE) standards will be used to
cover project steps. The IEEE is a leading developer of standards that underpin many of today’s
technologies. This standards are developed in a unique environment that builds consensus in an
open process based on input from all interested parties. With nearly 1,300 standards either
completed or under development, they are a central source of standardization in both traditional and
emerging fields, particularly telecommunications, information technology and power generation [2].
IEEE Software Engineering standards are used throughout industry today to put software
development processes into acceptable standard. Covering software engineering terminology,
processes, tools, reuse, project management, plans, documentation and measurement IEEE Software
Engineering standards are implemented in an array of disciplines, including: Computer Science,
Quality Management, Project Management, Systems Engineering, Dependability and Safety.
Together, the standards that comprise IEEE software engineering standards collection excel in
technical integrity on an individual basis and each can take its place within a suite of standards that
may be adopted in totality or in part by interested organizations [3].
The reason for using IEEE standards in this project, is to construct a project that is developed under
the standards that are widely accepted by the software engineering community. Moreover by using
these collection of standards, our project guarantees the steps that are need to be covered in
software engineering methodologies.

3
1.5 References
[1]. A. Gupta., Y.A. Tung, J.R. Marsten, “Digital signature: use and modification to achieve success
in next generational e-business processes”, Science Direct, p.571, June 2003. [Online]. Available:
http://www.sciencedirect.com. [Accessed October 17, 2007].
[2].Institute of Electrical and Electronics Engineers, “About IEEE”, [Online].Available:
http://www.ieee.org. [Accessed October 17, 2007].
[3].IEEE Software Engineering Standards Zone, “Software Engineering”, [Online].Available:
http://standards.ieee.org [Accessed October 17, 2007].

4

Introduction

  • 1.
    SENIOR PROJECT 2007-2008 (Introductionto the ekoSign project) 1. Introduction Use of XML Signatures to Success Document Flow in Supply Chain Project team members Hüseyin Çakır, Mehmet Mesut Özışık, Yılmaz Kaya Abstract:This paper gives some brief information about the project in three sections. First section defines the project name. Second section defines the project objectives and on what motivation the project was started. Third section describes the importance and benefits of using software engineering standards. Keywords:Project name, project objectives, project standards. http://groups.google.com/group/digitalsignature digitalsignature@googlegroups.com PRINT DATE: 05/06/08 1
  • 2.
    1.1 Introduction This paperbelongs to the inception phase of the unified process and it mainly represents the scope of the project. Figure 1.1 shows the steps of the unified process and which step the introduction paper belongs to. Inception Elaboration Construction Transition 1.Introduction Figure 1.1 Steps of Unified Process. 1.2 Project Name This project's name is "Use of XML Signatures to Success Document Flow in Supply Chain". The ekoSign stands for an acronym name of the project. 1.3 Project Objectives This project's main goal is to develop a XML based software that: • • • • fits the IEEE Software Engineering Standards in terms of documentation and processes, adopts XML Signature technology to supply chain concept, allows flow of documents under predefined policies, applies partial document ownership with motivation to the points that Alok Gupta mentioned in his research [1]. Following points that Gupta guidelines, using XML signatures provide several advantages to the business: • • • • • eliminate the need for printing out documents for signing, reduce storage of paper copies, improve management and access of electronic versus paper documents, eliminate of need for faxing or overnight mailing-reduction of cycle time, enhance management processes outside the “final signature” step. 2
  • 3.
    1.4 Project Standards Inthis project, Institute of Electrical and Electronics Engineers (IEEE) standards will be used to cover project steps. The IEEE is a leading developer of standards that underpin many of today’s technologies. This standards are developed in a unique environment that builds consensus in an open process based on input from all interested parties. With nearly 1,300 standards either completed or under development, they are a central source of standardization in both traditional and emerging fields, particularly telecommunications, information technology and power generation [2]. IEEE Software Engineering standards are used throughout industry today to put software development processes into acceptable standard. Covering software engineering terminology, processes, tools, reuse, project management, plans, documentation and measurement IEEE Software Engineering standards are implemented in an array of disciplines, including: Computer Science, Quality Management, Project Management, Systems Engineering, Dependability and Safety. Together, the standards that comprise IEEE software engineering standards collection excel in technical integrity on an individual basis and each can take its place within a suite of standards that may be adopted in totality or in part by interested organizations [3]. The reason for using IEEE standards in this project, is to construct a project that is developed under the standards that are widely accepted by the software engineering community. Moreover by using these collection of standards, our project guarantees the steps that are need to be covered in software engineering methodologies. 3
  • 4.
    1.5 References [1]. A.Gupta., Y.A. Tung, J.R. Marsten, “Digital signature: use and modification to achieve success in next generational e-business processes”, Science Direct, p.571, June 2003. [Online]. Available: http://www.sciencedirect.com. [Accessed October 17, 2007]. [2].Institute of Electrical and Electronics Engineers, “About IEEE”, [Online].Available: http://www.ieee.org. [Accessed October 17, 2007]. [3].IEEE Software Engineering Standards Zone, “Software Engineering”, [Online].Available: http://standards.ieee.org [Accessed October 17, 2007]. 4