PowerPoint PresentationApplication Architecture & ModelingChapter MapApplication ArchitectureSlide 5Physical Data Flow Diagrams (DFDs)Sample Physical Data Flow DiagramPhysical ProcessesPhysical Process NotationSamples of Physical ProcessesPossible Computer Process ImplementationsSample Physical Process ImplementationsMultiple Implementation of the Same Physical ProcessorSlide 14Physical Data FlowsSample Physical Data FlowsSlide 17Physical External Agents and Data StoresPhysical Data Store NotationPhysical Data Store ImplementationsInformation Technology ArchitectureDistributed versus Centralized SystemsWhy Distributed Systems?Distributed Systems at What Price?Distributed Computing LayersFlavors of Distributed ComputingFile Server ArchitectureSlide 28Client/Server Architecture—The ClientsClient/Server Architecture—The ServersClient/Server—Distributed PresentationSlide 32Client/Server—Distributed DataSlide 34Client/Server—Distributed Data and ApplicationSlide 36Internet- and Intranet-based ArchitecturesSlide 38Internet- and Intranet TechnologiesData ArchitecturesSlide 41Types of Data(base) DistributionData Partitioning versus Data ReplicationInterface ArchitectureInterface ArchitecturesSlide 46MiddlewareBatch Inputs and OutputsOn-Line Inputs and OutputsRemote BatchKeyless Data Entry (and Automatic Identification)Pen InputElectronic Data Interchange (EDI)Process ArchitectureProcess ArchitecturesSDEsSDE’sApplication Architecture Design StrategiesA Method for Application Architecture DesignThe Network Architecture DFDData Distribution ArchitectureSoundStage Data Distribution DFDProcess AssignmentsDesign UnitsRecording a Person/Machine BoundaryA Manual Design Unit DFDSlide 6713C H A P T E RAPPLICATION ARCHITECTURE AND MODELINGApplication Architecture & ModelingDefine an information system’s architecture in terms of Knowledge, Processes, and Communications–building blocks will be distributed across a network.Differentiate between logical and physical data flow diagrams,Describe both centralized and distributed computing alternatives Describe database and data distribution alternatives Describe user and system interface alternatives Describe various software development environments Describe strategies for developing or determining the architectureDraw physical data flow diagrams for an information system’s architecture and processes.Chapter MapApplication ArchitectureSpecifies the technologies to be used to implement –information systems in terms •Knowledge•Processes•Communications–and how these components interact across a network.Serves as an outline or blueprint for detailed design and implementation.Application ArchitectureInformation Processing–Centralized–DistributedData Storage–Centralized–DistributedImplementation Technologies–Programming Languages–User interfaceIntegration –COTS integration–Other Systems integrationPhysical Data Flow Diagrams (DFDs)Model the technical and human decisions to be implemented Communicate technical choices and other design decisions to those who will actually construct and implement the system.–Recall from Chapter 9 that Logical DFDs are a type of process model.Sample Physical Data Flow DiagramPhysical Processes–Logical processes• assigned to physical processors such as PCs, servers, mainframes, people, or devices in a network. •physical DFD models that network structure.–Each logical process • implemented as one or more physical processes. – a logical process may be split into multiple physical processes:•To define those aspects that are performed by people or computers.•To define those aspects to be implemented by different technologies.•To show multiple implementations of the same process.•To add processes for exceptions and internal control (e.g., security).Physical Process NotationI D ( o p t i o n a l )A c t i o n V e r b+N o u n o r O b j e c tP h r a s eI m p l e m e n t a t i o nSamples of Physical ProcessesPossible Computer Process ImplementationsA purchased application software package–Also called commercial off-the-shelf (COTS) softwareA system or utility program–Exchange Server–Netscape Commerce SeverAn existing application program–May require modificationA program to be writtenSample Physical Process ImplementationsMultiple Implementation of the Same Physical ProcessorI D ( o p t i o n a l )A c t i o n V e r b+N o u n o r O b j e c tP h r a s eI m p l e m e n t a t i o nI D ( o p t i o n a l )A c t i o n V e r b+N o u n o r O b j e c tP h r a s eI m p l e m e n t a t i o nI D ( o p t i o n a l )A c t i o n V e r b+N o u n o r O b j e c tP h r a s eI m p l e m e n t a t i o nI D ( o p t i o n a l )A c t i o n V e r b+N o u n o r O b j e c tP h r a s eI m p l e m e n t a t i o nPhysical ProcessesNumber will almost always be greater than the number of logical processes–Data collection–Date Filtering–Data Forwarding–Preparation–Quality ControlPhysical Data FlowsA physical data flow represents any of the following:–The planned implementation of an input to, or output from a physical process.–A database command or action such as create, read, update, or delete.–The import of data from, or the export of data to another information system across a network.–The flow of data between to modules or subroutines (represented as physical processes) in a program.Sample Physical Data FlowsSample Physical Data FlowsPhysical External Agents and Data StoresPhysical external agents are carried over from the logical DFD models.–If scope changes, the logical models should be changed before the physical models are drawn.A physical data store represents the planned implementation of one of:–A database–A table in a database–A computer file–A tape or media backup of anything important–A temporary file or batch–Any type of noncomputerized filePhysical Data Store NotationID(opt)Implementation Method:Data Store NameID(opt)Data Store Name(Implementation Method)Physical Data Store ImplementationsInformation TechnologyInformation TechnologyArchitectureArchitectureDistributed versus Centralized SystemsA distributed system–DATA, PROCESS, and INTERFACE –distributed to multiple locations in a computer network –the processing workload is distributed across the network.In centralized systems–a central, multi-user computer hosts all the DATA,