Top Banner
yyyyyyyy xxxxx zzzzzzzzzzzzzzz Orgnization Architecture Enterprise Architecture Submitted by Submitted to:
43

Togaf project

Jan 25, 2017

Download

Software

Mohammed Omar
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Togaf project

yyyyyyyyxxxxxzzzzzzzzzzzzzzz

Orgnization Architecture

Enterprise Architecture

Submitted by

Submitted to:

Page 2: Togaf project

WORD OF THANKS

PART 1: INTRODUCTION

E-Government Enterprise Architecture Master Plan O MISSION O VISION O PROJECT BACKGROUND O E-GOVERNMENT PROJECT KEY ENABLERS O E-GOVERNMENT MASTER PLAN SCOPE OF WORK

PART 2: ARCHITECTURE DEVELOPMENT METHOD Preliminary Phase Phase A: Architecture Vision Phase B: Business Architecture Phase C: Information Systems Architectures

o Data Architecture: o Application Architecture:

Phase D: Technology Architecture Phase E: Opportunities and Solutions Phase F: Migration Planning Phase G: Implementation Governance Phase H: Architecture Change Management Requirements Management

PART 3: ENTERPRISE ARCHITECTURE PRINCIPLES

Government Principles Architecture Principles

Business Architecture Principles Data Architecture Principles Application Architecture principles Technical Architecture Principles (Include integrations,

infrastructure and security)

Page 3: Togaf project

PART 4 : CAPABILITY ASSESSMENT Maturity Level 1. Maturity Level 2. Maturity Level 3. Maturity Level 4. Maturity Level 5. Maturity Level 6. Assessment

PART 4 : ORG NAMECASE STUDY Scope Background Purpose Problem Solution Objective Success criteria Solution Road map

o Business Architecture phase B o Business process reengineering o Information system Architecture phase C

Application Architecture Data Architecture

o Technical Architecture phase D

Page 4: Togaf project

Part 1: IntroductionOrg 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-Government Enterprise Architecture Master Plan

E-Government Mission statement is

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 .

Project Background

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

all government e-Services and electronic information to be delivered to citizens (G2C),

business (G2B) and government employees (G2E).

Page 5: Togaf project

E-Government Project 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-Government Master Plan scope of work

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.

Conceptualize and implement the national portal.

Page 6: Togaf project

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.

Preliminary Phase Objective:

Prepare the enterprise for successful Preliminary Enterprise Architecture

Establish organizational context

Identify sponsor (and other) stakeholders

Gain commitment to the approach

Define enterprise scope

Define ―architecture footprint

Define framework and detailed methods

Confirm governance framework

Page 7: Togaf project

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: Information Systems Architectures Objectives:

Develop Target Architectures covering either or both (depending on project scope) of the

data and application systems domains

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

Page 8: Togaf project

Application Architecture: Define the major kinds of application system necessary 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 and Solutions 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/business analysis 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: Implementation Governance Objectives:

Formulate recommendations for each implementation project Govern and manage an Architecture Contract covering the overall implementation and

deployment process 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

Page 9: Togaf project

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

Page 10: Togaf project

Part 3: Enterprise Architecture Principles

Principles must be established at multiple levels:

Government Principles 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 guesswork out 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 of adopting or

Page 11: Togaf project

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

Architecture Principles 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

Page 12: Togaf project

Technical 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

Page 13: Togaf project

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)

Page 14: Togaf project

Maturity Level 1: None

No Enterprise Architecture program. No Enterprise Architecture to speak of.

Maturity Level 2: 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 or business 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 personnel in the enterprise

architecture process. Little or no adherence to existing Standards.

Maturity Level 3: Under Development – Enterprise Architecture Process is under 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.

Page 15: Togaf project

Governance of a few architectural standards 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 Level 4: Defined – Defined Enterprise Architecture Including Detailed Written Procedures and Technical Reference 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 Model and 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

Page 16: Togaf project

Maturity Level 5: Managed – Managed and Measured 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.

Feedback on architecture process from all Operating Unit elements is used to drive

architecture process improvements.

Page 17: Togaf project

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.

AssessmentLevel 1The Government EA capability was at level 1 before the beginning of

the GEA project.Level 2The Government EA capability was at level 2 before the

start of Preliminary PhaseLevel 3The Government EA capability was at level 3 after the completion of

the Preliminary Phase of the GEA project.Level 4The Government EA capability is at Maturity level 4 as one full cycle

of ADM 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 5The Government EA capability will achieve these levels after the complete roll out of and adoption GEA. This will be the next Maturity level for the Government to target.

Level 6The Government EA capability will achieve these levels when the improvement cycles are planned, measured and implemented over the existing architecture process. The Government these levels after achieving Level 5.

Page 18: Togaf project

PART 4 : Org name Case Study

PurposeThe purpose of this Document is to address and analyze system requirements 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..

BackgroundOrg 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 system analysis based on the study of the business process requirements,

including use cases, logical models, and interface and integration requirements, for the following

systems:

Correspondences & Document Management System

Regulations Maintenance System

Admin Module

In the previous section we shared our customized EA framework which relay on TOGAF

methodology.

Page 19: Togaf project

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 of projects:

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

Page 20: Togaf project

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.

SolutionUtilize the EA framework to deploy new solution to automate the process

Objective1. 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.

Success criteriaReduce the time needed to release the prisoner to 2 days and in case of volition this period send notification to Managers to take actions

Page 21: Togaf project

Solution Road map Service Oriented Architecture SOA will be used in conjunction with TOGAF for the solution Architecture

1. Business Architecture (phase B)

Online

Serv

ices

)(

- -

– -

Admin Module

Search – receive

notification

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.

Page 22: Togaf project

Business process reengineering

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

Page 23: Togaf project

2. Information system Architecture (phase C)

I-Application Architecture

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

< >

< >

< >

< >

< >

< >

< >

9User Send 9

User Send

11Rejected

17Reassigned to User

10Approve

Send

12Sec

Send

2Sec

Reject

1Sec

Accept

3 Assign to Div

4 Assign to User

13 Comm Send

initially14

Comm Send Finally

USE CASE NAME:

مراسلة تسجيل USE CASE TYPEBusiness Requirements System Analysis System Design

USE CASE ID: CMM_UC_01.00PRIORITY: HighSOURCE: - Requirements Document

- Requirements Review Meetings

PRIMARY BUSINESS ACTOR:

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- - The individual requesting this functionality has user privilege to the

Page 24: Togaf project

CONDITION: 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.

TYPICAL COURSEOF EVENTS:

Actor Action / System ResponseStep 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:- المراسلة : :can take 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] تاريخ- [”جديد“ :Default][Mandatory] : صفـة الوارد- – List of specified to the department]: تصنيف الموضوع

Subject Lockup Table ]- [Mandatory] :عدد المشفوعات- األهمية -:مستوى عادي " عاجل "- رد؟ Check box : تتطلب- المعاملة “ Set to the default value : حالة االجراء ”تحت

Step 2: Define the DestinationoThe 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 SourceoThe 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

Page 25: Togaf project

- If the sender is a person or group of persons, the user enters the name(s) in a free text.

Step 3: Define the Related Individuals (Citizens)o If 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] رقم- عليه مدعي أم [”مدعي ”=Default][Mandatory] مدعي

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] رقم- اإلدخال [Value=Current Date/Time][Mandatory] تاريخ- العنوان- ملخص- مالحظات- الصفحات [Mandatory] عدد- الدالة [Editable List] الكلمات

Step 5: Confirm sending the correspondence & saving the dataoThe 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 “ خارجي لوارد مراجعة ”تذكرةo In case of the “”,the user may request to print inquiry form.o Invoke 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 , ” أوالخاصة

- نوع القضية- رقم القضية- جهة التحقيق- جهة الضبط

Page 26: Togaf project

- المدعى- المدعى عليه

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 correspondenceThe 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 correspondenceThe 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 DataIf 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 RULESIMPLEMENTATION CONTRAINTS AND SPECIFICATIONS

بطباعة / النظام يقوم خارجى صادر وارد خطاب كل علىاألولى -Stamp1 ختم الصفحة أعلى على يساريتم ويحتوى :

المشفوعات / - - عدد التاريخ الوارد الصادر رقم.Bar Code البحث عملية لتسهيل التاريخ و بالرقم

على -2 الختم نفس طباعة يتم الداخلى الوارد حالة فىالصفحة يمين أولى أواسفل صحـفة استخدام يتـم

Page 27: Togaf project

Cover page- مع ارشفتها مع المعلومات تلك على تحتوى. المعاملة

3- " النوع " نفس من اإلجراء تحت معاملة وجود حالة فى \ النظام يقوم ، الموضوع القضية لنفس و الشخص لنفس

أما القرار اتخاذ فى الحرية اعطاؤه مع المستخدم بتنبيهبها السماح أو الجديدة المعاملة . برفض

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?

Page 28: Togaf project

II-Data Architecture

ERD –Diagram for the system

Page 29: Togaf project

3.Technical Architecture (phase D)

Dedicated lease line A two dedicated leased lines from two independent sources

will be used to connect ORG NAMEto MOI secure network

to ensure 24/7 operation

Microsoft BizTalk server Will be used as middleware to publish back office

functionality as web service

Microsoft .net Will be used as development framework

MS SQL sever2008 MS SQL sever2008 as database servers

HP 3Bar storage SAN storage

Windows 2008 and IIS Application servers and load balancers

Page 30: Togaf project