How to do inormation architecture (in 20 days)

Friday, February 27, 2009

Enterprise Architecture General Software Development

After understanding what is information architecture (http://www.theeagroup.net/ea/Default.aspx?tabid=1&newsType=ArticleView&articleId=142 ) and what needed to be modelled (http://www.theeagroup.net/ea/Default.aspx?tabid=1&newsType=ArticleView&articleId=143 ) let’s see how to do information architecture. Basic EA Information architecture for certain LOB can be done within 20 business days . Following is a description of the activities and tasks on a day-by-day basis.

1.1 Work Day 1 -2

1.1.1 Define Information Meta-model

· Repository-based Enterprise architecture status discussion covering current Architecture (“As-Is”) and “To-Be” status· Reference Model Architecture discussion covering current status · Identification of initial roles and responsibilities, including stakeholders· Identification of the appropriate work participants and portions that they should attend· Review of current collected data(intended for the Architecture to be implemented) and identify which data will be upload into an EA tool · Identify Impact analysis scenarios that will be implemented · Identify reporting needs that will be implemented· Setting the LOB that the work will be focused on

1.1.2 Common Definitions

· Information Components· Information Objects / Entities· GDT / attributes· Schema· Role (User, Owner)· Business Function· Application· Service· Principles· Constraints· Requirements

1.1.3 Common Diagrams

· Conceptual information view· Logical information view· Information flow (between business)· Information flow (between Apps)· Security View· Service View· Dissemination View

1.1.4 Common matrixes

· Information to Business capabilities· CRUD matrix

1.1.5 Deliverables:

· Information Meta-model· Project schedule including scope and domains, roles and participants

1.2 Work Day 3 - 5

1.2.1 Identify Information objects / entities and create relevant Diagrams

· Introduce methodology and using it to identify Information Object· Creating automating mechanism to upload existing data into EA tool· Creating relevant diagrams

1.2.2 Identify Information components and create relevant Diagrams

· Introduce methodology and using it to identify Information components· Creating automating mechanism to upload existing data into EA TOOL· Creating relevant diagrams · Related Information components to Information Objects

1.2.3 Identify Information attributes / GDT and create relevant Diagrams

· Introduce methodology and using it to identify GDT· Creating automating mechanism to upload existing data into EA TOOL· Creating relevant diagrams · Related Information attributes / GDT to Information Objects

1.2.4 Deliverables:

· populated instances of Information components, Objects (Entities) and GDT (Attributes)· Diagrams to depict Information core definitions (Information components, Objects (Entities) and GDT (Attributes))

1.3 Work Day 6 – 7

1.3.1 Information classification

· Introduce and follow methodology to classify information on a basis of:o Master data vis Operational datao Core, Context and supportive data

1.3.2 Deliverables:

· Classification of Information Objects and components

1.4 Work Day 8-10

1.4.1 Modelling information flow between Business Functions

· Set information (usually component) owner and users· Using the selected methodology and diagram to model information flow between business functions

1.4.2 Modelling information flow between Applications

· Set information (usually component) owner application and using applications· Using the selected methodology and diagram to model information flow between business Applications

1.4.3 Deliverables:

· Information to Business function matrix · Information flow diagram (Business functions)· Information flow diagram (Applications)· Dissemination View· Information blueprint

1.5 Work Day 11 - 12

1.5.1 Identify Information non-functional requirements

· Define non-functional requirements for information objectso Accessibilityo Audit and Controlo Availabilityo Maintainabilityo Performanceo Reliability· Set the non-functional values for each information object / entity

1.5.2 Deliverables:

· Enrich EA TOOL with Information objects / Entities non functional requirements.· Information principles· Information Constraints

1.6 Work Day 13 - 15

1.6.1 Build CRUD matrix

· Interview business users to get their CRUD perspective on Information Components/ entities or Information components· Integrate all the data into one matrix· Analyze the matrix and present Information risks

1.6.2 Deliverables:

· CRUD matrix· List of Information “as-is” risks (Data duplication, duplication of ownership, non supported data, etc’)· Plan to fill the gaps between “to-be” and “as-is”· Security View

1.7 Work Day 16 - 17

1.7.1 Related Information to business capabilities / function

· Validating Information mapping to business function by using business functions Input / output and information objects / attributes· Note that mapping to roles (owner/users) has been done in previous task.

1.7.2 Related Information to Application

· Validating Information mapping to application function by using application services Input / output and information objects / attributes· Use Business functions and Information objects / entities to identify business services needed from business perspective· Validate information mapping to applications that use it

1.7.3 Related Information to Technology

· Map Information components to supported technologies· Map Information Objects / Entities to DB schemas that implement them

1.7.4 Deliverables:

· Service View· Relations to business domains· Relations to Application domains· Related to technology domain