MIS 385/MBA 664 Systems Implementation with DBMS/ Database ManagementInformation Systems ArchitectureArchitecture exampleA more sophisticated example...Slide 5Information EngineeringSlide 7Top-Down vs. Bottom-UpInformation engineeringSystems Development Life CycleDatabase SDLCPlanning MatrixesBusiness Function-to-Data Entity Planning MatrixInformation System-to-Objective Planning MatrixFunctional DecompositionEnterprise Data ModelingEnterprise Data ModelConceptual Database ModelingLogical Database DesignPhysical Database DesignDatabase implementationDatabase MaintenanceDocumentationSome Keys to Success...Three Schema Architecture for Database Development3-schema architectureConceptual SchemaExternal SchemaPhysical Schema3-schema development processRapid application development (RAD)RADThe RAD lifecycleWithin the time box...Barriers to overcome...Pine Valley FurnitureSlide 37MIS 385/MBA 664Systems Implementation with DBMS/Database ManagementDave [email protected] (email)http://www.davesalisbury.com/ (web site)Information Systems ArchitectureA conceptual blueprint or plan that expresses the desired future structure for the information systems in an organization.Architecture exampleCIMEDIExternal database accessBusiness OperationsCustomers& SuppliersExternal EventsData validation and retentionIntegrated data warehouseAccess analysis & presentation ToolsInformationdelivery systemDecision makersCustomers, SuppliersA more sophisticated example...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 processingInformation EngineeringAn Information Systems Architecture is developed by IS planners following a particular methodology such as Information Engineering.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 objectivesTop-Down vs. Bottom-Up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 opportunitiesInformation 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ImplementationSystems Development Life CycleProject Identification & SelectionProject Initiation & PlanningAnalysisLogical DesignPhysical DesignImplementationMaintenanceDatabase SDLCDatabase DevelopmentActivitiesIdentify ProjectInitiate and PlanAnalyzeLogical DesignPhysical DesignImplementationMaintenanceEnterpriseModelingConceptualData ModelingLogicalDB DesignPhysical DBDesign/CreationDBImplementationDBMaintenanceSDLCPlanning MatrixesShow interrelationships between objects. Location-to-FunctionUnit-to-FunctionInformation System-to-Data EntitySupporting Function-to-Data EntityInformation System-to-ObjectiveBusiness Function-to-Data Entity Planning MatrixInformation System-to-Objective Planning MatrixFunctional DecompositionEnterprise Data ModelingThe first step in database development, in which the scope and general contents of organizational databases are specified.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)EnterpriseModelingConceptualData ModelingLogicalDB DesignPhysical DBDesign/CreationDBImplementationDBMaintenanceConceptual Database ModelingDetermine user requirementsDetermine business rulesBuild conceptual data modeloutcome is an entity-relationship diagram or similar communicationtoolpopulation of repository EnterpriseModelingConceptualData ModelingLogicalDB DesignPhysical DBDesign/CreationDBImplementationDBMaintenanceLogical Database DesignSelect logical database modelcommit to a database alternativeMap Entity-Relationship DiagramsNormalize data structuresSpecify business rulesEnterpriseModelingConceptualData ModelingLogicalDB DesignPhysical DBDesign/CreationDBImplementationDBMaintenancePhysical Database DesignSelect DBMSSelect storage devicesDetermine access methodsDesign files and indexesDetermine database distributionSpecify update strategiesEnterpriseModelingConceptualData ModelingLogicalDB DesignPhysical DBDesign/CreationDBImplementationDBMaintenanceDatabase implementationCode and test database processing programsComplete documentationInstall database and convert dataEnterpriseModelingConceptualData ModelingLogicalDB DesignPhysical DBDesign/CreationDBImplementationDBMaintenanceDatabase MaintenanceAnalyze database and applications to ensure evolving information requirements are being metTune database for improved performanceFix errorsProvide data recovery when neededEnterpriseModelingConceptualData ModelingLogicalDB DesignPhysical DBDesign/CreationDBImplementationDBMaintenanceDocumentation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 acceptedSome Keys to Success...accurate requirements definitioncommitmenteffective change managementmanageable sizechampionThree 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 phase3-schema architectureConceptual SchemaDescribes the logical structure of the entire databaseIndependent of a specific DBMSAvoids details of physical designStated