1 / 37

MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management

MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management. Dave Salisbury salisbury@udayton.edu (email) http://www.davesalisbury.com/ (web site). Information Systems Architecture.

binta
Download Presentation

MIS 385/MBA 664 Systems Implementation with DBMS/ Database 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. MIS 385/MBA 664Systems Implementation with DBMS/Database Management Dave Salisbury salisbury@udayton.edu (email) http://www.davesalisbury.com/ (web site)

  2. Information Systems Architecture • A conceptual blueprint or plan that expresses the desired future structure for the information systems in an organization.

  3. Architecture example CIM Data validation and retention Integrated data warehouse Access analysis & presentation Tools Information delivery system Business Operations EDI Customers & Suppliers External database access External Events Decision makers Customers, Suppliers

  4. A more sophisticated example...

  5. Information Systems Architecture • Key Components: • data • processes which manipulate data • network which transports data • people who perform processes and send and receive data • events and points in time when processes are performed • reasons for events and rules which govern data processing

  6. Information Engineering • An Information Systems Architecture is developed by IS planners following a particular methodology such as Information Engineering.

  7. Information Engineering • Data-oriented methodology • Uses top-down planning in which specific information systems are deduced from a broad understanding of organization’s information needs, rather than relying on specific user information requests • Offers perspective on relationship of information systems to business objectives

  8. Top-Down Planning: A methodology that attempts to gain a broad understanding of the information system needs of the entire organization Bottom-Up Planning: A methodology that identifies and defines IS development projects based upon solving operational business problems or taking advantage of business opportunities Top-Down vs. Bottom-Up

  9. Information engineering • Information systems planning • Identify strategic planning factors (goals, CSFs, problem areas) • IT vision • Identify corporate planning objectives • Information system architecture • Develop enterprise model • Systems analysis • Systems design • Implementation

  10. Project Identification & Selection Project Initiation & Planning Analysis Logical Design Physical Design Implementation Maintenance Systems Development Life Cycle

  11. Database SDLC SDLC Database DevelopmentActivities Identify Project Enterprise Modeling Initiate and Plan Conceptual Data Modeling Analyze Logical DB Design Logical Design Physical DB Design/Creation Physical Design DB Implementation Implementation DB Maintenance Maintenance

  12. Planning Matrixes • Show interrelationships between objects. • Location-to-Function • Unit-to-Function • Information System-to-Data Entity • Supporting Function-to-Data Entity • Information System-to-Objective

  13. Business Function-to-Data Entity Planning Matrix

  14. Information System-to-Objective Planning Matrix

  15. Functional Decomposition

  16. Enterprise Data Modeling • The first step in database development, in which the scope and general contents of organizational databases are specified.

  17. Enterprise Modeling Conceptual Data Modeling Logical DB Design Physical DB Design/Creation DB Implementation DB Maintenance Enterprise Data Model • A model which includes: • overall range of organizational databases • general contents of organizational databases • Built as part of IS planning for the organization and not the design of a particular database • One part of an organization’s overall information systems architecture (ISA)

  18. Enterprise Modeling Conceptual Data Modeling Logical DB Design Physical DB Design/Creation DB Implementation DB Maintenance Conceptual Database Modeling • Determine user requirements • Determine business rules • Build conceptual data model • outcome is an entity-relationship diagram or similar communicationtool • population of repository

  19. Enterprise Modeling Conceptual Data Modeling Logical DB Design Physical DB Design/Creation DB Implementation DB Maintenance Logical Database Design • Select logical database model • commit to a database alternative • Map Entity-Relationship Diagrams • Normalize data structures • Specify business rules

  20. Enterprise Modeling Conceptual Data Modeling Logical DB Design Physical DB Design/Creation DB Implementation DB Maintenance Physical Database Design • Select DBMS • Select storage devices • Determine access methods • Design files and indexes • Determine database distribution • Specify update strategies

  21. Database implementation • Code and test database processing programs • Complete documentation • Install database and convert data Enterprise Modeling Conceptual Data Modeling Logical DB Design Physical DB Design/Creation DB Implementation DB Maintenance

  22. Database Maintenance • Analyze database and applications to ensure evolving information requirements are being met • Tune database for improved performance • Fix errors • Provide data recovery when needed Enterprise Modeling Conceptual Data Modeling Logical DB Design Physical DB Design/Creation DB Implementation DB Maintenance

  23. Documentation • most formal development methodologies are documentation based • helps managers monitor progress and quality of project • facilitates communication between team members • includes models • various stages are not complete until documentation is accepted

  24. Some Keys to Success... • accurate requirements definition • commitment • effective change management • manageable size • champion

  25. Three Schema Architecture for Database Development • Conceptual Schema • Analysis project phase • External Schema • Analysis and Logical Design phases • (subset of conceptual schema) • Internal Schema • Physical Design phase

  26. 3-schema architecture

  27. Conceptual Schema • Describes the logical structure of the entire database • Independent of a specific DBMS • Avoids details of physical design • Stated in • ERDs • metadata

  28. External Schema • Also called a user view • Specifications include screen formats, report formats, transaction definitions

  29. Physical Schema • Describes physical structure of entire database • Specifies how data from a conceptual schema are stored in secondary memory • Sometimes called internal schema • Specifications include physical file and data structures, storage organization, and index structures

  30. 3-schema development process

  31. Rapid application development (RAD) • design methodology which speeds systems delivery through a combination of speedy design iterations, data modeling, user/developer teamwork, and automated development tools. • encompasses a set of techniques that can be used to build complex, strategic, and mission-critical applications in months rather than years

  32. RAD

  33. The RAD lifecycle • requirements planning • conduct joint requirement planning workshop • design • conduct JAD workshop • construction • members of team monitor evolution, system is prototyped • cutover • installation

  34. Within the time box... Requirements planning User design construction phase Build & evolve prototype User review time box request for change Evaluate system cutover

  35. Barriers to overcome... • poor training/ tools • reluctance to leave old methods behind • mindset that RAD is not adequate for large-scale systems development • speedy delivery does not mean low quality • “scope/function creep”

  36. Pine Valley Furniture

  37. Pine Valley Furniture

More Related