<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE ArticleSet PUBLIC "-//NLM//DTD PubMed 2.7//EN" "https://dtd.nlm.nih.gov/ncbi/pubmed/in/PubMed.dtd">
<ArticleSet>
		<Article>
		<Journal>
			<PublisherName>Majlesi Journal of Electrical Engineering</PublisherName>
			<JournalTitle>Improvement of Electronic Correspondence of Inter-enterprise with Service Component of ECES</JournalTitle>
			<Issn></Issn>
			<Volume>Volume 12 (2018)</Volume>
			<Issue>Issue 1, March 2018</Issue>
			<PubDate PubStatus="epublish">
                <Year>2024</Year>
                <Month>02</Month>
                <Day>15</Day>
			</PubDate>
		</Journal>
		<ArticleTitle>Improvement of Electronic Correspondence of Inter-enterprise with Service Component of ECES</ArticleTitle>
		<VernacularTitle></VernacularTitle>
		<FirstPage></FirstPage>
		<LastPage></LastPage>
		<ELocationID EIdType="doi"></ELocationID>
		<Language>EN</Language>
		<AuthorList>
            			<Author>
                				<FirstName>Mohammad</FirstName>
				<LastName>Hadi Emtehani</LastName>
				<Affiliation>Department of Computer Engineering, Yazd Branch, Islamic Azad University, Yazd, Iran</Affiliation>
				<Identifier Source="ORCID"></Identifier>
			</Author>
            			<Author>
                				<FirstName>Sima</FirstName>
				<LastName>Emadi</LastName>
				<Affiliation>Department of Computer Engineering, Yazd Branch, Islamic Azad University, Yazd, Iran</Affiliation>
				<Identifier Source="ORCID"></Identifier>
			</Author>
            		</AuthorList>
		<PublicationType>Journal Article</PublicationType>
		<History>
			<PubDate PubStatus="received">
				<Year>2024</Year>
				<Month>02</Month>
				<Day>15</Day>
			</PubDate>
		</History>
		<Abstract>by development of using software of Enterprise Content Management (ECM), necessity of improving electronic Correspondence of inter-enterprise is felt more than before in order to enterprise cooperation. Despite existence of some bases for enterprise content management such as ECE protocol still there are some problems such as user intervention, delay, consumption of paper, parallelism, impossibility of tracking Correspondence and security problems and possibility of enterprise cooperation is not provided well. Using architecture of service component which has advantages of service-oriented approach such as simplicity, reusability, interoperability and flexibility produces an optimal solution for interoperability between systems and heterogeneous substrates by increasing the agility of integration of Web services meanwhile it doesn’t have overload due to services and minimizes costs of development and maintenance. Component service of ECES which is implemented by using architecture of service component supports ECE standards and makes doing electronic Correspondence possible between enterprises of Iran.  </Abstract>
		<ObjectList>
            			<Object Type="keyword">
				<Param Name="value">Electronic Correspondence Exchange (ECE)</Param>
			</Object>
						<Object Type="keyword">
				<Param Name="value">Enterprise Content Management (ECM)</Param>
			</Object>
						<Object Type="keyword">
				<Param Name="value">Service Oriented Architecture (SOA)</Param>
			</Object>
						<Object Type="keyword">
				<Param Name="value">Electronic Correspondence Exchange Service (ECES)</Param>
			</Object>
						<Object Type="keyword">
				<Param Name="value">Genetic Algorithm</Param>
			</Object>
					</ObjectList>
	</Article>
	</ArticleSet>
