BAM2.ppt

402 views
381 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
402
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

BAM2.ppt

  1. 1. Information Engineering <ul><li>Information Engineering was developed in the late 70’s and early 80’s </li></ul><ul><li>James Martin set up a number of companies based upon the methodology </li></ul><ul><li>IE claims to be a comprehensive methodology covering all the life-cycle </li></ul>
  2. 2. <ul><li>Data centric view </li></ul><ul><li>Still recognises that processes are important </li></ul><ul><li>Emphasises diagrams as a communication tool </li></ul><ul><li>Diagrams are the deliverables </li></ul><ul><li>IE model consists of data, activity and the interaction of the two </li></ul><ul><li>Automated support is a basic requirement of the methodology (CASE) </li></ul>
  3. 3. Top Down Plan Analysis Design Construct
  4. 4. Four Levels of IE <ul><li>Information Strategy Planning </li></ul><ul><li>Business Area Analysis </li></ul><ul><li>Systems Planning and Design </li></ul><ul><li>Construction and Cutover </li></ul>
  5. 5. Description <ul><li>Starts with a top management overview of the enterprise </li></ul><ul><li>An enterprise view </li></ul><ul><li>More detail added as analysis progresses </li></ul><ul><li>Divide and conquer approach </li></ul>
  6. 6. Four levels <ul><li>Information Strategy Planning - an information architecture and strategy which supports the organisational objectives </li></ul><ul><li>Conducted at the enterprise level </li></ul><ul><li>Business area analysis - objective is to understand the individual business areas and determine requirements </li></ul>
  7. 7. <ul><li>System Planning and Design </li></ul><ul><ul><li>to establish the behaviour of the systems that the user wants and is achievable using technology </li></ul></ul><ul><li>Construction and cutover </li></ul><ul><ul><li>build and implement the systems </li></ul></ul><ul><li>First two levels ate technology independent </li></ul>
  8. 8. Information Strategy Planning <ul><li>Concerned with corporate objectives </li></ul><ul><li>IS designed to meet corporate objectives - business goals and structure </li></ul><ul><li>Quantitative! </li></ul><ul><li>ISP provides an overview of objectives, major business functions and information needs </li></ul>
  9. 9. <ul><li>The result is the information architecture </li></ul><ul><li>This ensures consistency and coherence between developments </li></ul><ul><li>The plan documents the business requirements and allocates priorities </li></ul><ul><li>Often left out of other SD methodologies </li></ul><ul><li>Involvement of senior staff at all levels </li></ul>
  10. 10. Four Tasks in ISP <ul><li>Current situation analysis </li></ul><ul><ul><li>strengths and weaknesses with current systems and business </li></ul></ul><ul><li>Executive requirements analysis </li></ul><ul><ul><li>information needs, priorities, responsibilities and problems </li></ul></ul><ul><ul><li>Goals of the business </li></ul></ul><ul><ul><li>Critical success factors are identified for the business and for parts of business </li></ul></ul>
  11. 11. <ul><li>Architecture Definition </li></ul><ul><ul><li>Information - global entity types and functions </li></ul></ul><ul><ul><li>Distribution of data and functions </li></ul></ul><ul><ul><li>business systems architecture - requirements (an ideal view) </li></ul></ul><ul><ul><li>technical architecture - h/w, s/w, and communications </li></ul></ul><ul><ul><li>organisation of IS function (dept or distributed) to support strategy </li></ul></ul>
  12. 12. <ul><li>Information strategy plan </li></ul><ul><ul><li>identifies business areas </li></ul></ul><ul><ul><li>and architectures for each </li></ul></ul><ul><ul><li>migration plans </li></ul></ul><ul><ul><li>preparation of the plan itself </li></ul></ul><ul><li>In recent years it has included BPR </li></ul>
  13. 13. Business Area Analysis <ul><li>Each business area is treated in detail </li></ul><ul><li>Data and function analysis performed </li></ul><ul><li>End user involvement </li></ul><ul><li>Tasks </li></ul><ul><li>Entity and function analysis </li></ul>
  14. 14. Data-ActivityMatrix Cust Order Order Line Matrix Receipt Customer R C - Create R - Read U - update D - Delete Validation Order RU C
  15. 15. <ul><li>Current systems analysis </li></ul><ul><ul><li>The current system is modeled in the same way and the two compared </li></ul></ul><ul><li>Use of CASE </li></ul>
  16. 16. Questions <ul><li>What is the aim of an Information Architecture? </li></ul><ul><li>What are the advantages of an Information Architecture? </li></ul><ul><li>Is an effective I. A. ever acheivable? </li></ul><ul><li>What are the principles that IE is based upon? </li></ul><ul><li>Do you think the methodology is sound? </li></ul>

×