Lecture_Note_13.pptVIP

* Managing Software Requirements Software Architecture Case Study School of Computer Software Tianjin University Purpose this Unit Through a simple case to see how we design the system via the Software Architecture Managing Software Requirements – Software Architecture Case Study Software Architecture For the purpose of demonstration, the case given here is simple: Customer browses the retailer’s catalog of items from the Web Customer selects one or more items Customer pays the retailer for the items Managing Software Requirements – Software Architecture Case Study Software Architecture For the demonstration purpose, the case given here is simple: Customer browses the retailer’s catalog of items from the Web Customer selects one or more items Customer pays the retailer for the items Managing Software Requirements – Software Architecture Case Study High Level Business Logic View Refined Logic View Try to give more detailed info: Layered structure Conscious thinking connectors ie Save() Technique required, in this case .Net Managing Software Requirements – Software Architecture Case Study Business Process View ? This can be done by drawing a process flow chart even not UML (Sequence Diagram better) 1) Registration/Login 2) Browse Catalog 3) Search Catalog 4) Ordering 5) Payment 6) Employee Checking 7) Employee shipping 8) Notifying the user Variations: Login process /New Account at any time and Credit Card issue Managing Software Requirements – Software Architecture Case Study Application Domain Level ? Static view: class diagram Managing Software Requirements – Software Architecture Case Study Further Refined Static View: relationship defined SKU: Stock Keeping Unit Managing Software Requirements – Software Architecture Case Study Static View Final Go! Managing Software Requirements – Software Architecture Case Study Physical View Managing Software Requirements – Software Architecture Case Study In this stage, mapping software into the OS