1 / 48

Information Resources Management

Information Resources Management. January 23, 2001. Agenda. Administrivia Development Methodologies People Involved Schema Architecture CASE Tools Homework #2. Administrivia. Homework #1 Book? Web Page Registration. Development Methodologies. Information Engineering Waterfall Model

bryant
Download Presentation

Information Resources Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Information Resources Management January 23, 2001

  2. Agenda • Administrivia • Development Methodologies • People Involved • Schema Architecture • CASE Tools • Homework #2

  3. Administrivia • Homework #1 • Book? • Web Page • Registration

  4. Development Methodologies • Information Engineering • Waterfall Model • RAD Model • Phased (Incremental) • Prototyping • Spiral • Customization

  5. Information Engineering • Data-oriented • Top-down approach • Broad understanding first • Then, specific systems identified • Information systems related to business objectives

  6. Information Engineering Steps • Planning • Analysis • Design • Implementation

  7. Info. Eng. Planning Phase • Identify strategic planning factors • goals, CSFs, problems • Identify corporate planning objectives • units, locations, functions, types • Develop enterprise model • functions, data, relationships

  8. Waterfall Model (SDLC) • System Developmen Lifecycle • Linear and sequential • “Classical” • Specific, predefined phases • Definite end points for each • Historically, most widely used • Template for other models

  9. Waterfall SDLC • Single system development • Information Engineering or other approach for overall strategic systems planning

  10. Waterfall Model Identification Initiation Analysis Logical Design Physical Design Implement Maintain Time

  11. Database Lifecycle 1. Enterprise Modeling 2. Conceptual Data Modeling 3. Logical Database Design 4. Physical Database Design and Creation 5. Database Implementation 6. Database Maintenance

  12. Waterfall Model Enterprise Modeling Identification Conceptual Data Modeling Initiation Analysis Logical Data Modeling Logical Design Physical Design Physical Database Design and Creation Implement Database Implementation Maintain Database Maintenance Time

  13. Waterfall Problems • Projects aren’t so sequential • Requirements finalized early • Delay before system delivered • All or nothing • Sequential dependencies create delays forcing others to wait

  14. RAD Model • Rapid Application Development • Complete Development Approach • “RAD/FAST” or “JAD” Session • “Components” • Fully functional and useful • Completely specified, built and installed in 60-90 days • Concurrent

  15. RAD Model Team 3 Team 2 Business Modeling Team 1 Business Modeling Business Modeling Data Modeling Data Modeling Process Modeling Data Modeling Process Modeling Application Generation Application Generation Process Modeling Testing & Turnover Testing & Turnover Application Generation Testing & Turnover Time

  16. RAD Drawbacks • System requires proper “components” • Resources & skills for large number of teams • High level of user involvement and commitment required • System performance may suffer • Technical risks dramatically increase project risks

  17. Phased (Incremental) Model • System is delivered in “increments” • Initial increment is “core product” • Increments larger than RAD system pieces • Focus on specific increment - delay decisions on future increments • System revised as development progresses • Sequential

  18. Analysis Design Code Test Deliver #1 Incremental Model Analysis Design Code Test Deliver #2 Deliver #3 Analysis Design Code Test

  19. Incremental Drawbacks • System must have “increments” • Increments must be useful to users • Overall, longer (much longer) development time • Business procedure changes with each increment delivered

  20. Prototyping Model • Geared toward requirement collection, unfamiliar technology, complex interface design • Prototype is a way of managing risk as much as an exploration of new ideas Listen to Customer Customer Test Drive Build/ Revise

  21. Prototyping • Prototype: software model of system • Closed-Ended - throwaway • Open-Ended - evolutionary • Explorative - identify requirements • Experimental - try options • “Entire” System • Key elements only

  22. Prototyping Cycle • Time between prototypes • Influences number of prototypes • Shorter time between - more prototypes • More prototypes (generally) better product • Company standard of fixed number of prototypes

  23. Candidates for Prototyping • Dynamic visual displays • Heavy user interaction • Complex algorithms or calculations • Ambiguous or conflicting requirements

  24. Prototyping Considerations • User Resources • Decision Makers • IS Resources - Tools, People • User Understanding of Prototype • Time to completion • Full functionality • Performance requirements • Closed-ended • “Paper Prototype”

  25. Spiral Model • Evolutionary software development • Task Regions • Predefined tasks in each • Multiple passes • Around the spiral • Through each region • Increasing complexity and level of detail • Prototyping usually involved

  26. Spiral Model

  27. Spiral Drawbacks • Unfamiliarity - newer model • Developer training • User training • High user involvement • When do spirals end? • Management and control very important • Risk assessment is critical • Expertise is needed

  28. Methodology Customization • Fit the structure of the solution to the structure of the problem • Don’t use a hammer to drive in a screw • Customize based on system size or complexity, development risk, staff and tool availability, user experience, controls required and system risk • Customize a single approach • Combine multiple approaches

  29. People Involved • Project manager • Systems analysts & designers • Database analysts & designers • Users • Programmers • Database Administrators (DBAs) • Networking experts • Other technical experts

  30. Project Manager • Assemble project team • Build detailed project plans • Monitor people and plan • Work with other management • Ultimately held responsible for success of system development project

  31. System Analysts & Designers • Focus on business needs • “Bridge” business and technology • System functions and data • Analyst - “What should be done?” • Designer - “How should it be done?” • Greater technology focus

  32. Database Analysts and Designers • Focus on business needs • “Bridge” business and technology • Primary focus on data requirements • Analyst - “What data is needed?” • Designer - “How should it be stored?”

  33. Users • Ultimate users of new system • Provide requirements, business needs • Review documentation • Test & accept new system • Train other users • May represent “actual” users

  34. Programmers • Design programs (detailed design) • “Write” programs • Test programs • Write SQL for database access

  35. Database Administrators • Ultimately responsible for databases • current and future • Provide data and modeling expertise • Provide DBMS expertise • Monitor and tune databases

  36. Other Technical Experts • Provide expertise in specified areas • networking • operating systems • hardware • development languages • development methodologies and tools

  37. Database Schema Architecture • Schema - view or model of a database • Different views of same database • Three kinds of schemas • Conceptual • External • Physical

  38. Conceptual Schema • Logical model of database • Data model • Entity-Relationship Diagram • Independent of DBMS • Focus on data and relationships

  39. External Schema • Also, User View • Subset of conceptual schema • data for specific task • specific users • specifc programs • Independent of DBMS • Entity-Relationship Diagram

  40. Physical Schema • Description of how data will actually be stored • Structure • Data types • Based on conceptual schema • Specific process for conversion • Tied to specific DBMS

  41. Schema Relationships External Schema 1 External Schema 2 External Schema n Conceptual Schema Physical Schema

  42. Schema Development External Schemas Conceptual Data Modeling Conceptual Schema Enterprise Modeling Logical Database Design Physical Schema Physical Database Design Database Implementation & Maintenance

  43. CASE Tools • Computer-Aided Software Engineering • Computer-Automated? • Features • Types • Repository • Tools

  44. CASE Features • Diagrams • Documentation • Data Dictionary • Team Coordination • Prototyping • Code Generation • Reverse Engineering

  45. CASE Types • Full development - integrated • iCASE • Analysis & Design • upper CASE • Implementation & Maintenance • lower CASE

  46. CASE Repository • Data dictionary - data element definitions and descriptions • Ensures consistency • Repository is much more • Database with linkages for all system development products and activities • Integration • Even across different CASE tools

  47. CASE Tools • Visio 2000 - Microsoft • on laptops • Visible Analyst - Visible Systems • ER/Studio - Embarcadero • ERWin - Computer Associates • Oracle Designer - Oracle • Power Designer - Sybase

  48. Homework #2 • Database Jobs • Search any source; find 5 jobs • Review requirements • Find your job & review • Table of results • Analyze number and type of jobs and the knowledge needed

More Related