Download Object-Oriented Architecture Design: Component Deployment and Information Model and more Assignments Software Engineering in PDF only on Docsity!
- All UML Diagrams extracted from “Introduction to Object-Oriented with ArchitectureDesign, Part 2CS577a, Fall 2005” Ed ColbertUSC Center for Software EngineeringPresented by A W Brown 01/31/2007^1 2/1/
Main <> Library_User <>^ Server Introduction to Object-Oriented with Architecture Design, Part 2 Define Architecture – LCO / TIM^ <>^ System_Administrator SW Component Classifier Model ForFull-text Title Database System Decision – Client-Server Model^
Software Classifiersare optional in CS
Define Architecture – LCO / TIM^ HW Configuration forFull-Text Title Database System^ /Administrator :Workstation Local / User Station :^ ISD Server :WorkstationUnix Server Introduction to Object-Oriented with Architecture Design, Part 2
Remote / User Station :Workstation client local : Networkserver local : Network Internet : Netw...client serverclientserver
Define Architecture – LCO / TIM Component Deployment for/Administrator : Workstation <> : System_Adminstrator Introduction to Object-Oriented with Architecture Design, Part 2
<>^ : Server (from : Unix Server)
Define Architecture – LCO / TIM Component Deployment forISD / Server : Unix Server^ <>^ Server Introduction to Object-Oriented with Architecture Design, Part 2 DB Manager
Main <> Library_User <>^ Server Introduction to Object-Oriented with Architecture Design, Part 2 Define Architecture – LCO^ <>^ System_Administrator SW Component Classifier Model For Full-text Title DatabaseSystem ^ Decision^ – Client-Server Model^
Software Classifiersare optional in CS
Define Architecture – LCO System Topology for Full-Text Title Database System^ <>^ ApplicationLayer^ <>^ BusinessLayer^ <>^ MIddlewareLayer^ <>^ System LayerIntroduction to Object-Oriented with Architecture Design, Part 2 Don’t Layer orPartition in CS577unless doing alarge system (e.g.50KSLOC+) Currently only have fewclasses But^ – We’ve just started– Planning for evolution
Define Architecture – LCO System Topology for Full-Text Title Database System Application Layer^ <> <>^ System_Administrator Library_User Nothing in other layers – yet…Introduction to Object-Oriented with Architecture Design, Part 2 Business Layer^ <>^ Server Don’t Layer orPartition in CS577unless doing alarge system (e.g.50KSLOC+)
Define Architecture – LCO Component Deployment for /Administrator : Workstation <> : System_Adminstrator Introduction to Object-Oriented with Architecture Design, Part 2 <>^ : Server (from : Unix Server)
Define Architecture – LCO Component Deployment for / User Station : Workstation <> : Library_User Introduction to Object-Oriented with Architecture Design, Part 2 <>^ : Server (from : Unix Server)
Define Information Model – LCO & LCA TIM Information Model for FTTD SystemIntroduction to Object-Oriented with Architecture Design, Part 2
<acts for^ <>^ Library_User User <> Search_Request^ <>^ <>^ represents>^ Results_Form^ Search_Result 1..1..^1 1 0..10..1 ^represents^1111 produces > 1111 <> Search_Form^ 0..^ 0..^ <>^ <>^ Journal_Description^ Journal_Set^11 0..^ 0..^ <> Vendor_Profile^ <>^ acts for >^ System_Administrator <>^ Administrator Vendor_Set <>^ <>^11 collects Administrator_Set^ Administrator_Description^ 1..1..
Define Information Model – LCO TIM Information Model Mapping for FTTD System Library User System Administrator <> Introduction to Object-Oriented with Architecture Design, Part 2
<> Search_Request <> Vendor_Profile
<> <> Search Request Journal Description (from SSAD 2.2 System Artifact) (from SSAD 2.2 System Artifact)^ <> <>^ Journal List Aministrator Profile^ (from SSAD 2.2 System Artifact) (from SSAD 2.2 System Artifact)^ <>^ Journal_Set <> Database (from SSAD 2.2 System Artifact) <> Journal_Description <> <> Vendor List Vendor_Profile (from SSAD 2.2 System Artifact) (from SSAD 2.2 System Artifact) <> <> Vendor_Set <> <> Search_Form System_Administrator <> <> <> Administrator_Description Administrator_Set <>^ <>^ <> Library_User^ Administrator
<> <> Search_Result Results_Form <> <>^ <> <> User <> <>^ <> <>^ <>^ <> <><><> Defining thismapping isoptional inCS
Define Information Model – LCO Refine Object Model For Library_UserComponent Typical Configuration for a search : User Introduction to Object-Oriented with Architecture Design, Part 2
criteria LL^ P : Search_Form^ {transient}{transient}^ L : User_Agent transient request : Search_Request^ P^ {transient} L In CS577 create LCollaboration G PDiagram for form : Results_Formcomponents only result : Journal_Setif adds value Server:Business Objects:Journal_Manager :{transient} Journal_Set_Manager{transient} {persistent}
Define Information Model – LCO Refine Class Model For Server Component^ <>^ <> Change_Password_Form^ Login_Form <> Administrative_Main_Form <> Add_Profile_Form <> Delete_Profile_Form (from Journal Management) <>^ <> Modify_Profile_Form^ Update_Journals_Form Add any known attributes, operations, & relations for classesIntroduction to Object-Oriented with Architecture Design, Part 2
<> Logout_Form^ <>^ Journal_Set^ (from Business Objects AD)^11 +set <>^ Administrator_Agent^ collects Administration_Form^ <>^ +member^ 0..0..^ Adminstration_Manager^ <>^ + Add_Profile()^ Journal_Description+ Delete_Profile()^ (from Business Objects AD)+ Modify_Profile()+ Update_Journals() <> AdminResults_Form