【软件工程英文版】SystemArchitectureandDesignI.pptVIP

06z8254: Software Engineering System Architecture and Design A. Data Intensive Systems Example 1: Electricity Utility Billing Criticisms of First Attempt Transaction Types Typical Requirements Batch Processing: Validation Batch Processing: Master File Update Benefits of Batch Updating Online Inquiry Example 2: A Small-town Stockbroker A Database Architecture Database Architecture Real-time Transactions Real-time Transactions Batch Processing Architectural considerations Example 3: Merger of Two Banks Merger of Two Banks: Options Merger of Two Banks: Architectural Options Discussion of Pfleeger, Chapter 5 Question 1: Design Review Question 2: Architectural Styles Question 3: Collaboration Question 4: Components Question 5: Techniques for Improving Design 20-* 06z8254 Spring 2004 Lecture 12 System Architecture and Design I The overall design of a system: ? Computers and networks (e.g., monolithic, distributed) ? Interfaces and protocols (e.g., http, CORBA) ? Databases (e.g., relational, distributed) ? Security (e.g., smart card authentication) ? Operations (e.g., backup, archiving, audit trails) ? Software environments (e.g., languages, source control tools) Examples ? Electricity utility customer billing ? Telephone company call recording and billing ? Car rental reservations ? Stock market brokerage ? E-commerce (e.g., A) First attempt: Data input Master file Transaction Bill Each transaction handled as it arrives. Where is this first attempt weak? A bill is sent out for each transaction, even if there are several per day Bills are not sent out on a monthly cycle No way to answer customer queries No process for error checking and correction All activities are triggered by a transaction The requirements have not been specified!!! ? Create account / close account ? Meter reading ? Payment received ? Other credits / debits ? Check cleared / check bounced ? Account query ? Correction of error ? etc.,