This document outlines an enterprise architecture master plan for a government organization. It includes an 8-phase architecture development method to guide the creation of the enterprise architecture. It also establishes several architecture principles for the business, data, application, and technical architectures. Finally, it assesses the organization's current enterprise architecture capability as a Level 3, with the goals of advancing to Level 4 upon completing the architecture development phases and eventually reaching Level 6 with continuous improvements.

1. yyyyyyyy
xxxxx
zzzzzzzzzzzzzzz
Orgnization Architecture
Enterprise Architecture
Submitted by
Submitted to:

2. WORD OF THANKS
PART 1: INTRODUCTION
 E-GovernmentEnterpriseArchitectureMasterPlan
o MISSION
o VISION
o PROJECTBACKGROUND
o E-GOVERNMENTPROJECTKEYENABLERS
o E-GOVERNMENTMASTER PLAN SCOPEOFWORK
PART 2: ARCHITECTUREDEVELOPMENTMETHOD
 PreliminaryPhase
 PhaseA:ArchitectureVision
 PhaseB:BusinessArchitecture
 PhaseC:InformationSystemsArchitectures
o DataArchitecture:
o ApplicationArchitecture:
 PhaseD:TechnologyArchitecture
 PhaseE:OpportunitiesandSolutions
 PhaseF:MigrationPlanning
 PhaseG:ImplementationGovernance
 PhaseH:ArchitectureChangeManagement
 RequirementsManagement

3. PART 3: ENTERPRISEARCHITECTURE PRINCIPLES
 GovernmentPrinciples
 Architecture Principles
 Business Architecture Principles
 Data Architecture Principles
 Application Architecture principles
 Technical Architecture Principles (Include integrations,infrastructure and security)
PART 4 :CAPABILITY ASSESSMENT
 MaturityLevel 1.
 MaturityLevel 2.
 MaturityLevel 3.
 MaturityLevel 4.
 MaturityLevel 5.
 MaturityLevel 6.
 Assessment
PART 4 :ORG NAMECASE STUDY
 Scope
 Background
 Purpose
 Problem
 Solution

4.  Objective
 Successcriteria
 SolutionRoadmap
o BusinessArchitecturephaseB
o Businessprocessreengineering
o Informationsystem ArchitecturephaseC
 ApplicationArchitecture
 DataArchitecture
o TechnicalArchitecturephaseD

5. Part 1: Introduction
Org name is a governmental entity which serves as hub of the services the Egypt
government provides to the citizens in Cairo. The org name has achieved a good
Maturity level in its IT operation and services, this has happened due to many reasons
1. The clear mission and vision that adopt ICT as success factor
2. Management support and commitment to org name mission and vision
3. The adoption of the standard frameworks (ITIL,PMI,TOGAF,COBIT)
E-GovernmentEnterprise Architecture MasterPlan
E-Government Missionstatementis
To – Improve the quality of people’s life without any discrimination, transcending regional and
racial differences, and realize socio-economic development by building a transparent
government and providing value added quality services through ICT.
E-Government Vision
Is the ―The Value Networking Government through
1.Citizen-centered service .
2.Transparent service .
3.Networked government.
4.Knowledge based society .
ProjectBackground
To realize e-Government vision and mission of providing a ―Value Networking
Government by building efficient, transparent and citizen centric government services,
termed as e-Services through ICT.
Defining the ―Government Enterprise Architecture has been one of the key priority
projects identified.
The Government Enterprise Architecture (GEA) project has been envisioned to deliver a
common integrated interoperability platform or service delivery gateway for information
exchange and host the national portal that will act as the single window (one-stop-shop)for

6. all government e-Services and electronic information to be delivered to citizens (G2C),
business (G2B) and government employees (G2E).
E-GovernmentProject Key enablers
Any architecture project rests on 4 key enablers
1. People
2. Process
3. Technology
4. Environment
Those enablers must be developed and managed in parallel and continuously
improved to maximize the revenue of any IT investment while achieving business IT
alignment.
E-GovernmentMasterPlanscope ofwork
 Review of business strategy drivers.
 Identification of critical services across the various departments.
 Current state assessment of the short-listed services.
 Business process re-engineering with recommendation of re-engineered process
design principles.
 Defining the EA:
o Principles.
o Standards.
o Polices.
o Specifications.
o Guidelines.
Across various architectural segments i.e. business,data,application, technology,
security & integration based on SOA.
 Defining the e-Government interoperability framework (As Yasser)
o GIF provides a framework to share, collaborate and integrate information and
organization processes by adopting and customizing the minimum required set of
collection of ICT standards and frameworks governing the communication of
systems,flow of information, as well as the exchange of data and business processes
that relates to Government Ministries, agencies and departments.

7.  Conceptualize and implement the national portal.
Part 2: Architecture Development Method
This is the core of TOGAF. It provides a 10 phased step-by-step approach to develop and use
enterprise architecture.
The ADM comprises a series of linked phases which enable :
 The full life-cycle management of an Enterprise Architecture.
 From planning to operational deployment and change.
PreliminaryPhase
Objective:
 Prepare the enterprise for successfulPreliminary Enterprise Architecture
 Establish organizational context
 Identify sponsor(and other) stakeholders
 Gain commitment to the approach

8.  Define enterprise scope
 Define ―architecture footprint
 Define framework and detailed methods
 Confirm governance framework
 Select supporting tools and infrastructure
 Define architecture principles
Phase A:Architecture Vision
Objective:
 Initiate a cycle of the ADM
 Ensure this evolution has recognition and support
 Define and organize an architecture development cycle
 Validate business principles,goals, drivers
 Establish Enterprise Architecture KPIs
 Define scope and components
 Define relevant stakeholders,their concerns and objectives
 Define key business requirements to be addressed
 Articulate an Architecture Vision
 Create a comprehensive plan
 Secure formal approval to proceed
 Understand the impact on and of other parallel architecture development cycles
Phase B: Business Architecture
Objectives:
 Describe the Baseline Business Architecture
 Develop a Target Business Architecture
 Product/service strategy
 Organizational, functional, process,information, geographic aspects
 Analyze the gaps
 Select and develop relevant Architecture Viewpoints
 Select relevant tools and techniques to be used
Phase C:InformationSystems Architectures
Objectives:
 Develop Target Architectures covering either or both (depending on project scope) of the
data and application systems domains

9.  Focuses on identifying and defining the applications and data considerations that support
an enterprise‘s Business Architecture
 Data Architecture:
 Define the major types and sources of data
 Understandable by stakeholders
 Complete and consistent
 Stable
 Application Architecture:
 Define the major kinds of application systemnecessary
 To process the data
 To support the business
Phase D:Technology Architecture
Objectives:
 Map application components into a set of technology components
 Software
 Hardware
 Defines the physical realization of an architectural solution.
Phase E:Opportunities andSolutions
Objectives:
 Review target business objectives and capabilities
 Consolidate gaps from Phases B to D
 Organize groups of building blocks to address these capabilities
 Review and confirm the enterprise's current parameters for, and ability to, absorb change
 Derive a series of Transition Architectures that deliver continuous business value
 Generate and gain consensus on an outline Implementation and Migration Strategy
Phase F:Migration Planning
Objectives:
 Co-ordinate the Implementation and Migration Plan with management frameworks
 Prioritize all work packages, projects, and building blocks
 Assign business value
 Conduct cost/businessanalysis
 Finalize the Architecture Vision and Architecture Definition Documents, in line with the
agreed implementation approach
 Confirm the Transition Architectures with stakeholders
 Create, evolve, and monitor the detailed Implementation and Migration
Phase G:ImplementationGovernance
Objectives:
 Formulate recommendations for each implementation project
 Govern and manage an Architecture Contract covering the overall implementation and
deployment process

10.  Perform appropriate governance functions while the solution is being implemented and
deployed
 Ensure conformance with the defined architecture
 Ensure that the program of solutions is deployed successfully,as a planned program of
work
 Ensure conformance of the deployed solution with the Target Architecture
 Mobilize supporting operations that will underpin the future working lifetime of the
deployed solution
Phase H:Architecture Change Management
Objectives:
 Ensure that baseline architectures continue to be fit-for-purpose
 Assess the performance of the architecture and make recommendations for change
 Assess changes to the framework and principles set up in previous phases
 Establish an architecture change management process for the new enterprise architecture
baseline that is achieved with completion of Phase G
 Maximize the business value from the architecture and ongoing operations
 Operate the Governance Framework
Requirements Management
Objectives:
 Define a process to manage requirements
 Identify
 Store
 Feed into and out of relevant ADM phases

12. Part 3: Enterprise Architecture Principles
Principles must be established at multiple levels:
GovernmentPrinciples
Government Architecture principles are general rules and guidelines that support the way
in which a Government organization sets about fulfilling its mission.
Architecture principles also provide the anchor for effective Architecture Governance, through a
set of principles related to the government, corporation, regulations, IT etc.
An enterprise-wide architecture tries to create a framework for effective decision making across
multiple departments. Otherwise, independent groups decide alone resulting in inconsistency,
information islands, isolated business processes,and inefficient technologies.This mixture is a
recipe for poor performance.
To get consistent behavior,the government must create a framework of guiding principles to
define what is most important to the enterprise. Guiding principles define the government‘s
strategy for certain business and technical functions.They balance department and agency
mandates on the one hand and government-wide interests on the other. They filter decision
making, eliminating solutions that don‘t meet the government‘s objectives.This clarity of
executive intent takes the guessworkout of lower-level decisions.Clear, well-understood and
sanctioned principles, combined with an executive commitment to enforce them, help drive
change across disparate departments and programs.
Each of the architecture principles for the government has four parts: a statement of principle,
brief description,the rationale for the principle, and implications or consequences ofadopting or

13. ignoring the principle. Other managerial and technical principles may exist. Ministries and its
department‘s technical officials are expected to adopt these principles, and identify department-
specific ones that express the same shared focus.
Principle 1: The government focuses on citizens
Principle 2: The government is a single, unified enterprise
Principle 3: The Government architecture is mission-driven
Principle 4: Security, privacy and protecting information are core government needs
Principle 5: Information is a national asset
Principle 6: The architecture simplifies government operations
ArchitecturePrinciples
Architectural principles provide a set of general rules and overarching guidelines
intended to support the long-term development and governance of the enterprise
architecture. The goal of these principles is to apply constraints such that decisions
reflect a balance of these elements, while providing maximum benefit to the
organization.
 Business Architecture Principles
1. Service Orientation: Identify & Deliver Government Services that are Critical,
Flexible & Reusable.
2. Compliance with Legislation, Government Regulations and Standards .
 Data Architecture Principles
1. Data is an Asset
2. Data is shared
3. Data is created, accessible and shareable
4. Data has an owner/trustee
5. Data security and permission
6. Standard, Common vocabulary and data / metadata definitions.
 Application Architecture principles
1. Modular and component based
2. Ease of use and re-use

14.  T echnical Architecture Principles (Include integrations,infrastructure
and security)
1. Interoperability
2. Confidentiality
3. Open standards based
4. ESB based national service delivery gateway
5. Web services for information exchange and granular service.
6. Scalability, Availability, Backup & Archival
7. Security Control Compliance, Selection & Standardization
8. Levels of Security
9. Security Measurement
10. Use of common User Authentication Framework

15. PART 4 : Capability Assessment
The Government and its departments have been implementing IT systems. The capability
assessment helps to identify the current capability and with the establishment of Enterprise
architecture, how it would improve the capability in the area of development and application
of enterprise architecture and communicate its level of capability to its business partners. The
architecture maturity models are used in enabling an enterprise to determine the state of
enterprise architecture and to evaluate risks and options during the development of the
enterprise architecture.
Capability Maturity Model Objectives:
1. To enable an organization to determine how capable they are in a particular area : In
this case the development and application of enterprise architecture.
2. To enable an organization to set targets for the development of capabilities in a
particular area.
3. To enable an organization to communicate its level of capability to a business partner.
Architecture capability maturity model (ACMM)

16. Maturity Level1: None
No Enterprise Architecture program. No Enterprise Architecture to speak of.
Maturity Level2: Initial – Informal Enterprise Architecture Process underway
 Processes are ad hoc and localized. Some Enterprise Architecture processes are defined. There
is no unified architecture process across technologies or business processes.Success depends
on individual efforts.
 Enterprise Architecture processes,documentation and standards are established by a variety of
ad hoc means and are localized or informal.
 Minimal or implicit linkage to business strategies orbusiness drivers.
 Limited management team awareness or involvement in the architecture process.
 Limited Operating Unit acceptance of the Enterprise Architecture process.
 IT Security considerations are ad hoc and localized.
 No explicit governance of architectural standards.
 Little or no involvement of strategic planning and acquisition personnelin the enterprise
architecture process.Little or no adherence to existing Standards.
Maturity Level3: Under Development – Enterprise Architecture Process isunder development
 Basic Enterprise Architecture Process program is documented. The architecture
process has developed clear roles and responsibilities.
 IT Vision, Principles, Business Linkages, Baseline, and Target Architecture are
identified. Architecture standards exist, but not necessarily linked to Target
Architecture. Technical Reference Model(TRM) and Standards Profile framework
established.
 Explicit linkage to Department processes.
 Management awareness of Architecture effort.
 Responsibilities are assigned and work is underway.
 The Governing body of Enterprise Architecture updates the Web Pages periodically
and is used to document architecture deliverables.
 IT Security Architecture has defined clear roles and responsibilities.

17.  Governance of a few architecturalstandards and some adherence to existing
Standards Profile.
 Little or no formal governance of IT Investment. Operating Unit demonstrates some
adherence to existing Standards Profile.
Maturity Level4: Defined –Defined Enterprise Architecture Including Detailed Written Procedures and TechnicalReference
Model
 The architecture is well defined and communicated to IT staff and business
management with Operating Unit IT responsibilities.
 Gap Analysis and Migration Plan are completed. Fully developed Technical
Reference Modeland Standards Profile. IT goals and methods are identified.
 Enterprise Architecture is integrated with capital planning and investment control.
 Senior-management team aware of and supportive of the enterprise-wide architecture
process. Management actively supports architectural standards.
 Most elements of Operating Unit show acceptance of or are actively participating in
the Enterprise Architecture process.
 Architecture documents updated regularly on Departments Enterprise Architecture
Web Page.
 IT Security Architecture Standards Profile is fully developed and is integrated with
Enterprise Architecture.
 Explicit documented governance of majority of IT investments.
On Completion of Preliminary phase of GEA Project, the Architecture Capability was Level 3
On Completion of 1 full successful cycle of Architecture development methods which happens in the
end of Implementing Governance takes the Government to Level 4

18. Maturity Level5: Managed– ManagedandMeasured Enterprise Architecture Process
 Enterprise Architecture process is part of the culture. Quality metrics associated with
the architecture process are captured.
 Enterprise Architecture documentation is updated on a regular cycle to reflect the
updated Enterprise Architecture. Business, Data,Application and Technology
Architectures defined by appropriate de-jure and de-facto standards.
 Capital planning and investment control are adjusted based on the feedback received
and lessons learned from updated Enterprise Architecture. Periodic re-examination of
business drivers.
 Senior-management team directly involved in the architecture review process.
 The entire Operating Unit accepts and actively participates in the IT Architecture
process.
 Architecture documents are updated regularly, and frequently reviewed for latest
architecture developments/standards
 Performance metrics associated with IT Security Architecture are captured.
 Explicit governance of all IT investments. Formal processes for managing variances
feed back into Enterprise Architecture.
 All planned IT acquisitions and purchases are guided and governed by the Enterprise
Architecture.
Maturity Level 6: Measured - Continuous Improvement of Enterprise
Architecture Process
 Concerted efforts to optimize and continuously improve architecture process.
 A standards and waivers process is used to improve the architecture development
process.
 Architecture process metrics are used to optimize and drive business linkages.
Business involved in the continuous process improvements of Enterprise
Architecture.
 Senior management involvement in optimizing process improvements in Architecture
development and governance.

19.  Feedback on architecture process from all Operating Unit elements is used to drive
architecture process improvements.
 Architecture documents are used by every decision maker in the organization for
every IT-related business decision.
 Feedback from IT Security Architecture metrics are used to drive architecture process
improvements.
 Explicit governance of all IT investments. A standards and waivers process is used to
improve governance-process improvements.
 No unplanned IT investment or acquisition activity.
Assessment
Level 1 The Government EA capability was at level 1 beforethe beginning ofthe GEA
project.
Level 2 The Government EA capability was at level 2 before the start of
Preliminary Phase
Level 3 The Government EA capability was at level 3 after the completion ofthe
Preliminary Phase ofthe GEA project.
Level 4 The Government EA capability is at Maturity level 4 as one full cycle ofADM
has been successfully completed. Moving beyond maturity level 4 requires
changes to people, processes and culture.This would be current level with
respect architecture maturity.
Level 5 The Government EA capability will achieve theselevels afterthe complete roll
out ofand adoption GEA. This will be the next Maturity level for the
Government to target.
Level 6 The Government EA capability will achieve theselevels when the improvement
cycles are planned, measured and implemented over the existing architecture
process. The Government theselevels after achieving Level 5.

20. PART 4 : Org name Case Study
Purpose
The purpose of this Document is to address and analyze systemrequirements of the group1 of
Projects for the Org name in Egypt Arabia. This document is based on the EA roadmap provided
during the requirements gathering sessions conducted in the Org name premises..
Background
Org name is a governmental entity which serves as hub of the services the Egypt
government provides to the citizens in Cairo. The org name is looking for an Information
Technology Solution consists of 20 Information Systems to support their business
processes of their Business Department and Units. Parts of these systems are to automate
the processes of handling the correspondences and documents, and archiving business
data. Other parts are to develop integrated information systems to support business
department’s manual activities. The remaining part of is an ERP modules.
Scope
The Scope is detailed systemanalysis based on the study ofthe business process requirements,
including use cases,logical models, and interface and integration requirements, for the following
systems:
 Correspondences& Document Management System
 RegulationsMaintenance System
 Admin Module
In the previous section we shared our customized EA framework which relay on TOGAF
methodology.

21. In phase F migration planning we were able to identify and list a group of ICT Projects
That will fill the gap between the AS-IS and TO-BE and reduce the organization pain.
The prioritized list ofprojects:
Project priority
Prisoners Case Management
system
high
Internet Portal high
middleware high
Correspondence system medium
Among those projects is the Prisoners Case Management System with one with high priority

22. Problem
It takes a long time (days and in some cases months)to finalize the condemned after
finishing his penalty due to manual work and the need to exchange many
information between Org name ,MOI ,and Authority of prisoners.
Solution
Utilize the EA framework to deploy new solution to automate the process
Objective
1. Reduce the time required to release the prisoner.
2. Automate the work in the pensioners department.
3. Integrate with the prisoner authority and MOI to exchange information.
Successcriteria
Reduce the time needed to release the prisoner to 2 days and in case of volition this
period send notification to Managers to take actions

23. SolutionRoadmap
Service Oriented Architecture SOA will be used in conjunction with TOGAF for the solution
Architecture
1. BusinessArchitecture (phaseB)
From the above context diagram we can identify the root cause for the delay
that Communication between the external organization and ORG NAMEis
manual:
1. All correspondences and cases submitted to Administrative Correspondence
department .
2. The correspondence will be dispatched to the target department for handling and
taking actions.
3. The resolved correspondence with actions will be sent back to Administrative
Correspondence department.
4. Administrative Correspondence department will send it to the target organization.
O
nline
Services
)(
-
-
–
–
–
–-
Admin Module
Search –
receive
notification

24. BusinessprocessreengineeringOnline
Services
)(
-
-
–
–
–
–-
Admin Module
Search –
receive
notification
Cloud
From the above diagram we omitted the manual link the external
organization and RP
And instead we will use automated 24/7 link that will eliminate the time
wasted in manual work

25. 2. InformationsystemArchitecture(phaseC)
I-Application Architecture
USE CASENAME: ‫مراسلة‬ ‫تسجيل‬ USE CASE TYPE
Business Requirements

System Analysis

System Design

USE CASEID: CMM_UC_01.00
PRIORITY: High
SOURCE: - Requirements Document
- Requirements Review Meetings
PRIMARY BUSINESSACTOR: Management - Department - employees in the RP-
Citizen - a third-party
PRIMARY SYSTEM ACTOR: - Employee incoming correspondences (recording and external
resources)
- Employee outgoing correspondences (recording external sources)
- Secretary of department (recording incoming - outgoing internal)
DESCRIPTION: This use case describes the event when the responsible employee in the
corresp. department registers incoming, outgoing correspondences .Also
when the secretary of any internal department (including corresp.
department) wants to register an internal correspondence.
PRE-CONDITION: - The individual requesting this functionality has user privilege to the
0 Received
< >
< >
1 Sec Check
2 Sec Accepted
1
Sec
Accept
1
Sec
Accept
Comm Send
Internal
3 Assign to Div 4 Assgined to User Viewed by Use
Cancelled
4
Assign
to User
3
Assign
to Div
4
Assign
to User
Comm Send
Internal
<
>
< > < >
Request Opinion
Initially Done
13 Finsihsed
< >
<System Only
Search>
5
User
View
15
Cancel
8
Opinion
No
7
Opinion
Ok
6
Request
Opinion
||
#9
#13
8 User for Send
9 Mgr for Accept
10 Sec for Send
1 Sec for Accept2 Sec Accepted
11 Comm to be Sent
12 Comm Sent 13 Finsihsed
< >
< >
<
>
<
>
<
>
< >
< >
9
User
Send 9
User
Send
11
Rejected
17
Reassig
ned to
User
10
Approve
Send
12
Sec
Send
2
Sec
Reject
1
Sec
Accept
3
Assign
to Div
4
Assign
to User
13
Comm
Send
initially
14
Comm
Send
Finally

26. backend system – As Employee of Etsalat Edarayah, Wared Employee
for registering Incoming Correspondence, Sader Employee for
registering Outgoing Correspondence, or Department Secretary for
registering Internal Correspondence.
- The privilege of the user is for the Correspondence Type assigned to
him by the admin.
- The user has logged in to the system (Correspondences Module).
TRIGGER: This use case is initiated when the user selects the option (link) to add
(register) correspondence.
TYPICALCOURSE
OF EVENTS:
Actor Action / System Response
Step 1:Create New Correspondence .
The user requests the option to add (register) new Correspondence.
oThe system responds by displaying the Correspondence form.
oThe user selects whether the correspondence is “‫,”وارد‬ “‫,”صادر‬ or
“‫داخلي‬ ‫.”صادر‬
oThe system responds by displaying the required attributes for each
option. [ِStep1, Alt1-Step1, Alt2-Step1 describe the three options
respectively].
oThe user enters the following fields:
- ‫المراسلة‬ ‫نوع‬ : cantake one of these values:
“ ‫حكومية‬ ‫معامالت‬–‫أشخاص‬ ‫من‬ ‫عرائض‬–‫سري‬–‫برقية‬–‫الخاص‬ ‫المكتب‬
‫(األم‬)‫ير‬-‫الجمهور‬ ‫(استقبال‬ ‫الخاص‬ ‫المكتب‬ ”
[Mandatory][Each group of users of the department is
responsible to handle only one type, and so this field will be
filled automatically by the system ]
- :‫رقم‬‫المراسة‬ Generated serial per each type “‫المراسلة‬ ‫نوع‬ :”and per
each year “‫هجرية‬ ‫”سنة‬ [Mandatory]
- :‫رقم‬‫الخطاب‬ Sender’s Issuing Number [Mandatory]
- ‫تاريخ‬ :‫الخطاب‬ Sender’s Issuing Number [Mandatory]
- ‫ارد‬‫و‬‫ال‬ ‫صفـة‬ : [Mandatory][Default: “‫]”جديد‬
- ‫ع‬‫الموضو‬ ‫تصنيف‬ :[List of specified to the department –
Subject Lockup Table ]
- ‫المشفوعات‬ ‫:عدد‬ [Mandatory]
- ‫األهمية‬ ‫مستوى‬ : ‫"عاجل‬-"‫عادي‬
- ‫رد؟‬ ‫تتطلب‬ : Check box
- ‫المعاملة‬ ‫حالة‬ :Set to the default value “‫االجراء‬ ‫”تحت‬
Step 2: Define the Destination
oThe user requests to set the destination “‫إليها‬ ‫المرسل‬ ‫.”الجهة‬
[Mandatory]
oThe system responds by listing the hierarchy of departments, units
and employees.
oThe employee selects one of these items.
Step 3: Define the Source
oThe user requests to set the source “ ‫الجهة‬‫الراسلة‬ ”. [Mandatory]
oThe system responds by listing the available “external entities” in the
system (lock-up table) with ability to add new one to the list.
oThe user selects one of these items, or
- If the sender is a person or group of persons, the user enters the
name(s) in a free text.

27. Step 3: Define the Related Individuals (Citizens)
oIf the subject (Case) is related to one person, or a group of persons,
the user requests to set the concerned persons “‫بـ‬ ‫.”متعلق‬ [Option]
oThen, system displays (a form) with the following attributes for each
person:
- ‫االسم‬ [Mandatory]
- ‫االإقامة‬ / ‫السجل‬ ‫رقم‬ [Mandatory]
- ‫عليه‬ ‫مدعي‬ ‫أم‬ ‫مدعي‬ [Mandatory][Default=”‫مدعي‬ ”]
Step 4: Add Attachment(s)
oThe user selects to attach documents.
oThe system responds by displaying the Attachments form.
oFor each document, the employee scan the document enters
attachment data by filling the following fields:
- ‫الوثيقة‬ ‫رقم‬ [Mandatory]
- ‫اإلدخال‬ ‫تاريخ‬ [Mandatory][Value=Current Date/Time]
- ‫العنوان‬
- ‫ملخص‬
- ‫مالحظات‬
- ‫الصفحات‬ ‫عدد‬ [Mandatory]
- ‫الدالة‬ ‫الكلمات‬ [Editable List]
Step 5: Confirm sending the correspondence & saving the data
oThe user selects to save the information and forward (distribute) the
crosp. to the destination.
oThe system responds by validating the data and storing the data in the
system database.
oThe following Check (Status) Field “‫المراسلة‬ ‫”أستلمت‬is set to False.
Step 6: Printing Inquiry Ticket “‫خارجي‬ ‫لوارد‬ ‫مراجعة‬ ‫”تذكرة‬
oIn case of the “”,the user may request to print inquiry form.
oInvoke use case CMM_UC_08.00, Print Inquiry Ticket
ALTERNATE COURSES: Alt1-Step1: ‫خارجي‬ ‫صادر‬
If the user selects correspondence type is “‫”صادرخارجي‬ , the following
fields are changed:
- Destination will be: “ ‫جهة‬‫اإلمارة‬ ‫داخل‬ ‫موظف‬ ”. [Same as Step2]
- Source will be:”‫شخص‬ ‫أو‬ ‫خارجية‬ ‫.”جهة‬ [Same as Step3]
- Both items: “‫الخطاب‬ ‫”رقم‬ and “ ‫تاريخ‬‫الخطاب‬ ” will not exist.
- If to be send by mail [Optional], the following fields will be
enabled: “ ‫البريد‬ ‫وزن‬–‫البريد‬ ‫تكلفة‬ ” and the receipt will be scanned
and attached as a document.
- If the transaction is related to “‫أو‬ ‫أوالخاصة‬ ‫العامة‬ ‫بالحقوق‬ ‫خاصة‬ ‫قضايا‬
‫,”المتابعة‬ the following fields are displayed:
- ‫القضية‬ ‫ع‬‫نو‬
- ‫القضية‬ ‫رقم‬
- ‫التحقيق‬ ‫جهة‬
- ‫الضبط‬ ‫جهة‬
- ‫المدعى‬
- ‫عليه‬ ‫المدعى‬

28. Alt2-Step1: ‫صادر‬‫داخلي‬
If the user selects correspondence type is “‫”صادرخارجي‬ , the following
fields are changed:
- Both the Destination & the Source will be: “ ‫جهة‬‫اإلمارة‬ ‫داخل‬ ‫موظف‬ ”.
- Both items will not exist: “‫الخطاب‬ ‫”رقم‬ and “‫الخطاب‬ ‫.”تاريخ‬
- If it is transaction transfer, invoke use case: CMM_UC_06.00,
‫معاملة‬ ‫إحالة‬
Alt2-Step1: ‫إ‬‫سابقة‬ ‫بمراسلة‬ ‫لحاق‬
- If the user selects “ ‫صفة‬‫الوارد‬ ” = “‫,”إلحاقي‬ then the system allows
him to search for existing record of “‫.“وارد‬
- if the type = “‫,”صادر‬ then the system allows him to search for
existing record of “‫.“صادر‬
Alt2-Step1: ‫جواب‬‫مراسلة‬‫سابقة‬
- If the user selects “ ‫صفة‬‫الوارد‬ ” = “‫,”جوابي‬ then the system allows
him to search for existing record of “‫.“صادر‬
- The system responds by related the 2 items and uncheck “ ‫تحتاج‬
‫”لرد‬ [set to False].
- Similarly, and if the type = “‫,”صادر‬ then the system allows him to
search for existing record of “‫.“وارد‬
Alt1-Step1: Modify existing correspondence
The user search for existing record to modify data. This will be allowed
whenever the status of receiving correspondence by the destination
“‫المراسلة‬ ‫.”أستلمت‬
Alt2-Step1: Delete existing correspondence
The user search for existing record to Delete the entire record. . This
will be allowed whenever the status of receiving correspondence by the
destination “‫المراسلة‬ ‫.”أستلمت‬
Alt1-Step5: Invalid Data
If any mandatory field is missing the system will not allow the saving
operation to complete and will generate an error message with the
missing fields’ titles. The system will also validate the remaining fields
for their size and structure.
CONCLUSION: This use case concludes when the user receives a confirmation of
registering the correspondence.
POST-CONDITION: The correspondence has been recorded; related documents have been
archived, and released to the destination.
BUSINESS RULES
IMPLEMENTATION
CONTRAINTSAND
SPECIFICATIONS
‫ختم‬ ‫بطباعة‬ ‫النظام‬ ‫يقوم‬ ‫خارجى‬ ‫صادر‬ / ‫وارد‬ ‫خطاب‬ ‫كل‬ ‫على‬Stamp 1-‫أعلى‬ ‫يتم‬
: ‫على‬ ‫ويحتوى‬ ‫يسار‬ ‫األولى‬ ‫الصفحة‬
‫الوارد‬ / ‫الصادر‬ ‫رقم‬-‫التاريخ‬-‫المشفوعات‬ ‫عدد‬
.Bar Code ‫البحث‬ ‫عملية‬ ‫لتسهيل‬ ‫التاريخ‬ ‫و‬ ‫بالرقم‬
‫يتـم‬ ‫أو‬ ‫الصفحة‬ ‫يمين‬ ‫اسفل‬ ‫على‬ ‫الختم‬ ‫نفس‬ ‫طباعة‬ ‫يتم‬ ‫الداخلى‬ ‫الوارد‬ ‫حالة‬ ‫فى‬ -2
‫أولى‬ ‫صحـفة‬ ‫استخدام‬
Cover page -. ‫المعاملة‬ ‫مع‬ ‫ارشفتها‬ ‫مع‬ ‫المعلومات‬ ‫تلك‬ ‫على‬ ‫تحتوى‬
3-‫معاملة‬ ‫وجود‬ ‫حالة‬ ‫فى‬‫لنفس‬ ‫و‬ ‫الشخص‬ ‫لنفس‬ ‫النوع‬ ‫نفس‬ ‫من‬ "‫اإلجراء‬ ‫"تحت‬
‫القضية‬‫بتن‬ ‫النظام‬ ‫يقوم‬ ، ‫الموضوع‬‫ا‬ ‫اتخاذ‬ ‫فى‬ ‫الحرية‬ ‫اعطاؤه‬ ‫مع‬ ‫المستخدم‬ ‫بيه‬‫أما‬ ‫لقرار‬
. ‫بها‬ ‫السماح‬ ‫أو‬ ‫الجديدة‬ ‫المعاملة‬ ‫برفض‬

29. ASSUMPTIONS:  Each group of users of the department (“ ‫االتصاالت‬‫االدارية‬ ”) is
responsible to handle only one type, and so this field will be
filled automatically by the system.
 While, for the internal correspondence, the Secretary selects any
type of those types.
 A predefine list of subjects categorized per department(s) is exist
(lockup table). Use will not enter the subject in a free text.
 Each Department deals (handles) many subjects. Each Subject is
related to one ore more Department.
OPEN ISSUES: 1. At first, at the initiation phase, the system will be applied in the “” to
maintain all correspondences of all types where all other department
proceed on the manual basis. However, will the intention is to
provide an access to each department to use the system, and so any
employee can send a internal /external correspondences? In this case,
how the validation and the change in the business process will be?
2. In each department, will all employees use the system? Or just a data
entry employee will be responsible to register all steps (transfer,
validate, approve, and process) conducted on the manual basis?

30. II-DataArchitecture

31. ERD –Diagram for the system

32. 3. TechnicalArchitecture (phaseD)
 Dedicatedleaseline
A two dedicated leased lines from two independent sources
will be used to connect ORG NAMEto MOI secure network
to ensure 24/7 operation
 MicrosoftBizTalkserver
Will be used as middleware to publish back office
functionality as web service
 Microsoft .net
Will be used as development framework
 MS SQLsever2008
MS SQL sever2008 as database servers
 HP 3Barstorage
SAN storage
 Windows 2008andIIS
Application servers and load balancers