Sybase PowerDesigner - Web viewSybase PowerDesigner. Object-Oriented Model Report. Model:...

Sybase PowerDesignerObject-Oriented Model Report

Model: UC_CarRentalReport: Report 1

Author: Islam GirlVersion: Date: 2/4/2010Summary:

Object-Oriented Model UC_CarRental Report Report 1

Table of Contents

The 'Table of Contents' field needs to be updated!

Sybase PowerDesigner 2/4/2010 of 31

Object-Oriented Model UC_CarRental

OOM Diagrams

I.1 Model level diagramsI.1.1 Diagram UCD_CarRental

Object-Oriented ModelModel: UC_CarRentalPackage: Diagram: UCD_CarRentalAuthor: Islam boy Date: 2/4/2010 Version:

Customer

Car

WorkShop

Driver

ManageCustomer ManageCar LetContractManageAcounts

Workshop

DealWithDriver

ManageUserAcount

ManageCarInfo

DealWithWorkShopMaintenance

MaintainCar

ManageCustomerInfo

LongIn

LogOut

LetContract

DealwithDriver

User

SupperUser

Admin

PowerDesigner 2015 Page


I.2 Package diagrams DealWithDriverI.2.1 Diagram UCD_DealWithDriver

Object-Oriented ModelModel: UC_CarRentalPackage: DealWithDriverDiagram: UCD_DealWithDriverAuthor: Islam boy Date: 2/4/2010 Version:

AddNewDriver

Edit Driver

Delet Driver

UserDriver



I.3 Package diagrams LetContractI.3.1 Diagram UCD_LetContract

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<Include>><<Include>>

AddNewContract

EditContract

DeleteContract

Car

Customer

InculdeUser

IncludeCar

IncludeCustomer Driver

IncludeDriver

User

SupperUser



I.4 Package diagrams MaintainCarI.4.1 Diagram UCD_MaintainCar

Object-Oriented ModelModel: UC_CarRentalPackage: MaintainCarDiagram: UCD_MaintainCarAuthor: Islam boy Date: 2/4/2010 Version:

Car

WorkShopSendCarReceiveCar

SupperUser



I.5 Package diagrams ManageAcountsI.5.1 Diagram UCD_ManageAccounts

Object-Oriented ModelModel: UC_CarRentalPackage: ManageAcountsDiagram: UCD_ManageAccountsAuthor: Islam boy Date: 2/4/2010 Version:

<<Extend>>

<<Extend>>

<<Extend>>

EditeUser

AddnewUser

DeleteUser

SetPrivilege

BrowseForUser

Admin

User



I.6 Package diagrams ManageCarI.6.1 Diagram UCD_ManageCarInfo

Object-Oriented ModelModel: UC_CarRentalPackage: ManageCarDiagram: UCD_ManageCarInfoAuthor: Islam boy Date: 2/4/2010 Version:

<<Extension>><<Extension>>

AddNewCarEditCarInfo

DeleteCar

NotifyUserCarAlreadyExist

Car

SupperUser



I.7 Package diagrams ManageCustomerI.7.1 Diagram UCD_ManageCustomer

Object-Oriented ModelModel: UC_CarRentalPackage: ManageCustomerDiagram: UCD_ManageCustomerAuthor: Islam boy Date: 2/4/2010 Version:

<<Extension>>

<<Extension>>

AddNewCustomer

EditCustomerInfo

DeleteCustomer

RemoveCustomerFromBL

ModifyCustomer'sRentHistory

SendCustomerToBlackList

NotifyCustomerExistance

SupperUser

User



I.8 Package diagrams WorkshopI.8.1 Diagram UCD_ManageWorkshop

Object-Oriented ModelModel: UC_CarRentalPackage: WorkshopDiagram: UCD_ManageWorkshopAuthor: Islam boy Date: 2/4/2010 Version:

WorkShop

AddNewWorkshop

DeleteWorkShop

EditWorshop

SupperUser



II Use case objectsII.1 Use case information for Package DealWithDriverII.1.1 List of use cases

Name Code ParentAddNewDriver AddNewDriver Package 'DealWithDriver'Delet Driver Delet_Driver Package 'DealWithDriver'Edit Driver Edit_Driver Package 'DealWithDriver'

II.1.2 Use case AddNewDriver

II.1.2.1 Card of use case AddNewDriverName AddNewDriverCode AddNewDriverParent Package 'DealWithDriver'

II.1.2.2 Action steps of use case AddNewDriver user requset to add new Driver CRP display Add Dialogue User enters all driver info and request to save

II.1.2.3 Pre-condition of use case AddNewDriver User Should login as superUser or admin

II.1.2.4 Post-condition of use case AddNewDriver Update DB

II.1.3 Use case Delet Driver

II.1.3.1 Card of use case Delet DriverName Delet DriverCode Delet_DriverParent Package 'DealWithDriver'



II.1.4 Use case Edit Driver

II.1.4.1 Card of use case Edit DriverName Edit DriverCode Edit_DriverParent Package 'DealWithDriver'

II.1.4.2 Action steps of use case Edit Driver User Request to Delete Driver CRP Display Deletion Dialogue user Enters DriverID and confirm theDeletion

II.1.4.3 Post-condition of use case Edit Driver Delete Driver and Update DB

II.2 Use case information for Package LetContractII.2.1 List of use cases

Name Code ParentAddNewContract AddNewContract Package 'LetContract'DeleteContract DeleteContract Package 'LetContract'EditContract EditContract Package 'LetContract'IncludeCar IncludeCar Package 'LetContract'IncludeCustomer IncludeCustomer Package 'LetContract'IncludeDriver IncludeDriver Package 'LetContract'InculdeUser InculdeUser Package 'LetContract'

II.2.2 Use case AddNewContract

II.2.2.1 Card of use case AddNewContractName AddNewContractCode AddNewContractParent Package 'LetContract'

II.2.2.2 Action steps of use case AddNewContract User request new contract from CRP CRP provide Form to Customer to fill the following info for the

Customer:



User should enter customerID and all of the personal information for the customer will be filling in contract .

enter the start date and time ,end date and time ,making contract date and time .

the available KM that allowed for customer during this time. enter the carID and car's information. If the customer needs to driver he should enter the driver

information,enter the price for the driver per day and dicount enter price per day for th car and dicount certainly user information will add to the contract.

II.2.2.3 Pre-condition of use case AddNewContract Log in to CRP

II.2.2.4 Post-condition of use case AddNewContract this contract will enter the database with new contractID

II.2.3 Use case DeleteContract

II.2.3.1 Card of use case DeleteContractName DeleteContractCode DeleteContractParent Package 'LetContract'

II.2.3.2 Action steps of use case DeleteContract User Search for the contract and get the ContractID Request to Delete CRP should ask to confirm deletion

II.2.3.3 Pre-condition of use case DeleteContract Log in as superuser or admin

II.2.3.4 Post-condition of use case DeleteContract Delete the Contract and update DB

II.2.4 Use case EditContract

II.2.4.1 Card of use case EditContractName EditContractCode EditContractParent Package 'LetContract'



II.2.4.2 Action steps of use case EditContract User Request to modify The contract the CRP show form to enter the number of the contract or to search

for it the user enter the contractID and request to open the contract the CRP open the contract user modify contract

II.2.4.3 Pre-condition of use case EditContract Log in to CRP

II.2.4.4 Post-condition of use case EditContract save contract modifications

II.2.5 Use case IncludeCar

II.2.5.1 Card of use case IncludeCarName IncludeCarCode IncludeCarParent Package 'LetContract'

II.2.5.2 Action steps of use case IncludeCar User enters the CarID CRP fill in contract CarID

II.2.6 Use case IncludeCustomer

II.2.6.1 Card of use case IncludeCustomerName IncludeCustomerCode IncludeCustomerParent Package 'LetContract'

II.2.6.2 Action steps of use case IncludeCustomer through the contract dialog user can add customer info by add the

customerID



II.2.7 Use case IncludeDriver

II.2.7.1 Card of use case IncludeDriverName IncludeDriverCode IncludeDriverParent Package 'LetContract'

II.2.7.2 Action steps of use case IncludeDriver User enters DriverID CRP fill Driver info in the contract

II.2.8 Use case InculdeUser

II.2.8.1 Card of use case InculdeUserName InculdeUserCode InculdeUserParent Package 'LetContract'

II.2.8.2 Action steps of use case InculdeUser the system should take the UserID and UserName Who made the

contract

II.3 Use case information for Package MaintainCarII.3.1 List of use cases

Name Code ParentReceiveCar ReceiveCar Package 'MaintainCar'SendCar SendCar Package 'MaintainCar'

II.3.2 Use case ReceiveCar

II.3.2.1 Card of use case ReceiveCarName ReceiveCarCode ReceiveCarParent Package 'MaintainCar'

II.3.2.2 Action steps of use case ReceiveCar User request to recieve car from workshop CRP open dialogue User enter the car ID



enter the new technicality status

II.3.2.3 Pre-condition of use case ReceiveCar User should log in as super user or customer car should send to maintenance befor it received

II.3.2.4 Post-condition of use case ReceiveCar New car technical status.

II.3.3 Use case SendCar

II.3.3.1 Card of use case SendCarName SendCarCode SendCarParent Package 'MaintainCar'

II.3.3.2 Action steps of use case SendCar user requset to send car to the maintenance CRP open Dialgue maintenance User enter the car ID CRP return all car info (will be fill in the dialogue) User enter the WorkShopID CRP return workshop info user enter the date and the expected return date

II.3.3.3 Pre-condition of use case SendCar User should login as admin or superuser

II.3.3.4 Post-condition of use case SendCar car should register in DB as broken dowenone

II.4 Use case information for Package ManageAcountsII.4.1 List of use cases

Name Code ParentAddnewUser AddnewUser Package 'ManageAcounts'BrowseForUser BrowseForUser Package 'ManageAcounts'DeleteUser DeleteUser Package 'ManageAcounts'EditeUser EditeUser Package 'ManageAcounts'SetPrivilege SetPrivilege Package 'ManageAcounts'



II.4.2 Use case AddnewUser

II.4.2.1 Card of use case AddnewUserName AddnewUserCode AddnewUserParent Package 'ManageAcounts'

II.4.2.2 Action steps of use case AddnewUser Admin requests to CRP to add new user CRP Open Add new user Dialog Admin enter the following Info Persnal Card ID, first name,middle name ,last name,address

(country ,city.street,zip code..),phone,mobile,email,dependent address,dependent phone,age ,sex,date of employed,

II.4.2.3 Post-condition of use case AddnewUser Update DB Give User New userID

II.4.3 Use case BrowseForUser

II.4.3.1 Card of use case BrowseForUserName BrowseForUserCode BrowseForUserParent Package 'ManageAcounts'

II.4.3.2 Action steps of use case BrowseForUser Open list that contain all users Admin select the certain user

II.4.3.3 Post-condition of use case BrowseForUser user info is returned

II.4.4 Use case DeleteUser

II.4.4.1 Card of use case DeleteUserName DeleteUserCode DeleteUserParent Package 'ManageAcounts'



II.4.4.2 Action steps of use case DeleteUser Admin requests to delete user from DB CRP ask UserID and shows userInfo Admin fix deletion

II.4.4.3 Extension of use case DeleteUser Browse for User

II.4.4.4 Post-condition of use case DeleteUserUptate DB

II.4.5 Use case EditeUser

II.4.5.1 Card of use case EditeUserName EditeUserCode EditeUserParent Package 'ManageAcounts'

II.4.5.2 Action steps of use case EditeUser Admin request to modify User Info. CRP opens Modify user info Dialogue box. admin enter the userID. all info for this user will appear. Admin modifies it. and request to saveDB

II.4.5.3 Extension of use case EditeUser Browse for user

II.4.5.4 Post-condition of use case EditeUser update DB

II.4.6 Use case SetPrivilege

II.4.6.1 Card of use case SetPrivilegeName SetPrivilegeCode SetPrivilegeParent Package 'ManageAcounts'



II.4.6.2 Action steps of use case SetPrivilege Admin request to modify the type of user to set the user privilege CRP open Dialogue box Admin enter the userID CRP return the current user type Admin Modify user type and request to save

II.4.6.3 Extension of use case SetPrivilege Browse for User

II.4.6.4 Post-condition of use case SetPrivilege Update DB

II.5 Use case information for Package ManageCarII.5.1 List of use cases

Name Code ParentAddNewCar AddNewCar Package 'ManageCar'DeleteCar DeleteCar Package 'ManageCar'EditCarInfo EditCarInfo Package 'ManageCar'NotifyUserCarAlreadyExist NotifyUserCarAlreadyExist Package 'ManageCar'

II.5.2 Use case AddNewCar

II.5.2.1 Card of use case AddNewCarName AddNewCarCode AddNewCarParent Package 'ManageCar'

II.5.2.2 Action steps of use case AddNewCarI.1.1.1

User request to add new car User should enter the following parameter

carID//car board number.Company manufactured car(Jakwar,Nessan..),kind(corola ,camry..)model(20005,2006,...),catogory(pichup,vehicle..),color(black,white,..),geartype(manual,automatic),Kilo meterage(the current kilometer counter ),maintenance cycle date,



replacing oil kilometer(at this number of KM car's oil must replace ),day price,max discount,allowed kilometer per day,additional kilometers price for each k,and good image for this car.car availability status(can the customer rent this car now!).car technicality status(engine status,drive wheel, wheels, body, lights, mirrors, chairs, doors,class,gear)

II.5.2.3 Extension of use case AddNewCar The CRP try to verify if this car already exsits

II.5.2.4 Pre-condition of use case AddNewCar User should log in as superuser or admin(manager).

II.5.2.5 Post-condition of use case AddNewCar new Car should regiter in DB

II.5.3 Use case DeleteCar

II.5.3.1 Card of use case DeleteCarName DeleteCarCode DeleteCarParent Package 'ManageCar'

II.5.3.2 Action steps of use case DeleteCar User request to delete car by enter CarID CRP Notify that the Car will drope from DB

II.5.3.3 Pre-condition of use case DeleteCar UserShould login as Super user or admin(manager)

II.5.3.4 Post-condition of use case DeleteCar If the user accept the car will be droped Update DB

II.5.4 Use case EditCarInfo

II.5.4.1 Card of use case EditCarInfoName EditCarInfoCode EditCarInfo



Parent Package 'ManageCar'

II.5.4.2 Action steps of use case EditCarInfo user should enter CarID or seach for it and then request edit car info CRP should provide frame that contain all car info to allow the user

editing car info user modify info and request the save.

II.5.4.3 Exceptions of use case EditCarInfo Notify the User that this CarID Already exist

II.5.4.4 Extension of use case EditCarInfo if the user modify the CarID to exist CarID in DB

II.5.4.5 Pre-condition of use case EditCarInfo

user should log in as superuser or admin

II.5.4.6 Post-condition of use case EditCarInfo Update CarInfo in DB

II.5.5 Use case NotifyUserCarAlreadyExist

II.5.5.1 Card of use case NotifyUserCarAlreadyExistName NotifyUserCarAlreadyExistCode NotifyUserCarAlreadyExistParent Package 'ManageCar'

II.5.5.2 Action steps of use case NotifyUserCarAlreadyExist send alert messege to user to add another CarID If the user cancel the request the Car will not be added to DB or

modified.

II.5.5.3 Exceptions of use case NotifyUserCarAlreadyExist If user request to over write the exist car system should modify car

info in DB

II.5.5.4 Extension of use case NotifyUserCarAlreadyExist request modify exist car



II.5.5.5 Pre-condition of use case NotifyUserCarAlreadyExist Add New Car or Edit car info and the CarID already Exist

II.5.5.6 Post-condition of use case NotifyUserCarAlreadyExist data base should be updated

II.6 Use case information for Package ManageCustomer

II.6.1 List of use casesName Code Parent

AddNewCustomer AddNewCustomer Package 'ManageCustomer'DeleteCustomer DeleteCustomer Package 'ManageCustomer'EditCustomerInfo EditCustomerInfo Package 'ManageCustomer'ModifyCustomer'sRentHistory

ModifyCustomer_sRentHistory Package 'ManageCustomer'

NotifyCustomerExistance NotifyCustomerExistence Package 'ManageCustomer'RemoveCustomerFromBL RemoveCustomerFromBL Package 'ManageCustomer'SendCustomerToBlackList SendCustomerToBlackList Package 'ManageCustomer'

II.6.2 Use case AddNewCustomer

II.6.2.1 Card of use case AddNewCustomerName AddNewCustomerCode AddNewCustomerParent Package 'ManageCustomer'

II.6.2.2 Action steps of use case AddNewCustomer User should enter Customer's personal information like

(customer type(normal customer,company),nickname,first name,mid name,last name,personal card number,type(residence or not), nationality, religion, job,address(country,state,city,zipe code).Relative person(the same personal information parameter of the customer)phone, workphone, mobile,

II.6.2.3 Extension of use case AddNewCustomer If the User inter the personal card number has already existed



II.6.2.4 Pre-condition of use case AddNewCustomer User Should login

II.6.2.5 Post-condition of use case AddNewCustomer when adding new customer ,CRP will Give CustomerID this will stay

forever for this customer. Update DB

II.6.3 Use case DeleteCustomer

II.6.3.1 Card of use case DeleteCustomerName DeleteCustomerCode DeleteCustomerParent Package 'ManageCustomer'

II.6.3.2 Action steps of use case DeleteCustomer onlly Super and manager can delete customer from database.

II.6.3.3 Pre-condition of use case DeleteCustomer User should log in as Superuser or admin

II.6.3.4 Post-condition of use case DeleteCustomer Update Database

II.6.4 Use case EditCustomerInfo

II.6.4.1 Card of use case EditCustomerInfoName EditCustomerInfoCode EditCustomerInfoParent Package 'ManageCustomer'

II.6.4.2 Action steps of use case EditCustomerInfo Inter the CustomerID modify any of customer information

II.6.4.3 Exceptions of use case EditCustomerInfo If the Customer doent exist the system should notify that



II.6.4.4 Extension of use case EditCustomerInfo Customer is not exist

II.6.5 Use case ModifyCustomer'sRentHistory

II.6.5.1 Card of use case ModifyCustomer'sRentHistoryName ModifyCustomer'sRentHistoryCode ModifyCustomer_sRentHistoryParent Package 'ManageCustomer'

II.6.5.2 Action steps of use case ModifyCustomer'sRentHistory User can add notice about any customer in each time the customer

rent a car,this is to keep track about customers behavior. here user should enter customerID,customer name,behavior good or not,reason,another note.

according to this history user can evaluate customer behavior.

II.6.5.3 Post-condition of use case ModifyCustomer'sRentHistory Customer behavior should enter to DB and DB should update

II.6.6 Use case NotifyCustomerExistance

II.6.6.1 Card of use case NotifyCustomerExistanceName NotifyCustomerExistanceCode NotifyCustomerExistenceParent Package 'ManageCustomer'

II.6.6.2 Action steps of use case NotifyCustomerExistance Notify the user that the customer already exist in DB

II.6.6.3 Exceptions of use case NotifyCustomerExistance Over Write the exist customer

II.6.6.4 Pre-condition of use case NotifyCustomerExistance User Entered Existing CustomerID In DB|

II.6.6.5 Post-condition of use case NotifyCustomerExistance Data base will be updated



II.6.7 Use case RemoveCustomerFromBL

II.6.7.1 Card of use case RemoveCustomerFromBLName RemoveCustomerFromBLCode RemoveCustomerFromBLParent Package 'ManageCustomer'

II.6.7.2 Action steps of use case RemoveCustomerFromBL If customer emended his work and user see that it is good to remove

this customer from blacklist he can do that but the user should enter good reason.

II.6.7.3 Post-condition of use case RemoveCustomerFromBL Update DB

II.6.8 Use case SendCustomerToBlackList

II.6.8.1 Card of use case SendCustomerToBlackListName SendCustomerToBlackListCode SendCustomerToBlackListParent Package 'ManageCustomer'

II.6.8.2 Action steps of use case SendCustomerToBlackList User requests to send customer to BlackList to prevent him from

letting new contract. CRP asks from user to enter CustomerID and The reason User enters CustomerID and the reson. CRP Asks from user to confirm User confirms request.

II.6.8.3 Pre-condition of use case SendCustomerToBlackList Customer Don't Keep to contract

II.6.8.4 Post-condition of use case SendCustomerToBlackList Update Database

II.7 Use case information for Package WorkshopII.7.1 List of use cases

Name Code ParentAddNewWorkshop AddNewWorkshop Package 'Workshop'



DeleteWorkShop DeleteWorkShop Package 'Workshop'EditWorshop EditWorshop Package 'Workshop'

II.7.2 Use case AddNewWorkshop

II.7.2.1 Card of use case AddNewWorkshopName AddNewWorkshopCode AddNewWorkshopParent Package 'Workshop'

II.7.2.2 Action steps of use case AddNewWorkshop User requset to add new workshop CRP open Dialogue user enter all info for this workshop

II.7.2.3 Post-condition of use case AddNewWorkshop Update DB

II.7.3 Use case DeleteWorkShop

II.7.3.1 Card of use case DeleteWorkShopName DeleteWorkShopCode DeleteWorkShopParent Package 'Workshop'

II.7.3.2 Action steps of use case DeleteWorkShop User request to delete workshop CRP open the dialogue User enter the workShopID and confirm deletion CRP Delete the workshop

II.7.3.3 Post-condition of use case DeleteWorkShop update DB

II.7.4 Use case EditWorshop

II.7.4.1 Card of use case EditWorshopName EditWorshop



Code EditWorshopParent Package 'Workshop'

II.7.4.2 Action steps of use case EditWorshop user request to modify the workshop info CRP open the info in dialogue user modify info and confirm the change CRP save change

II.7.4.3 Post-condition of use case EditWorshop Update DB

II.8 Model level use casesII.8.1 Use case DealwithDriver

II.8.1.1 Card of use case DealwithDriverName DealwithDriverCode DealwithDriverParent Object-Oriented Model 'UC_CarRental'

II.8.1.2 Action steps of use case DealwithDriver add new driver edit driver delete driver(these three function as same as customer functions)

II.8.2 Use case DealWithWorkShopMaintenance

II.8.2.1 Card of use case DealWithWorkShopMaintenanceName DealWithWorkShopMaintenanceCode DealWithWorkShopMaintenanceParent Object-Oriented Model 'UC_CarRental'

II.8.2.2 Action steps of use case DealWithWorkShopMaintenance add new workshop edit workshop information delete workshop



II.8.2.3 Pre-condition of use case DealWithWorkShopMaintenance Login as super user or customer

II.8.3 Use case LetContract

II.8.3.1 Card of use case LetContractName LetContractCode LetContractParent Object-Oriented Model 'UC_CarRental'

II.8.3.2 Action steps of use case LetContract let new contract, contract needs to Edit drop or delete.

II.8.4 Use case LogOut

II.8.4.1 Card of use case LogOutName LogOutCode LogOutParent Object-Oriented Model 'UC_CarRental'

II.8.4.2 Action steps of use case LogOut User requset to log out from CRP CRP notify the user that all windows will be closed when the user confirm all windows will be closed and the program return to main screen

II.8.5 Use case LongIn

II.8.5.1 Card of use case LongInName LongInCode LongInParent Object-Oriented Model 'UC_CarRental'

II.8.5.2 Action steps of use case LongIn User request to begin by enter user name and the password CRP check if the user allowed to enter the proram CRP check also the user type for privilege.



II.8.5.3 Extension of use case LongIn Notify the user to enter an other username or password

II.8.6 Use case MaintainCar

II.8.6.1 Card of use case MaintainCarName MaintainCarCode MaintainCarParent Object-Oriented Model 'UC_CarRental'

II.8.6.2 Action steps of use case MaintainCar send car to maintenance receive car from maintenance.

II.8.7 Use case ManageCarInfo

II.8.7.1 Card of use case ManageCarInfoName ManageCarInfoCode ManageCarInfoParent Object-Oriented Model 'UC_CarRental'

II.8.7.2 Action steps of use case ManageCarInfo UC AddNewCar UC EditCarInfo UC DeleteCar

II.8.7.3 Pre-condition of use case ManageCarInfo User should log in as superuser or admin(manager)

II.8.7.4 Post-condition of use case ManageCarInfo Execute the child UC correctly.

II.8.8 Use case ManageCustomerInfo

II.8.8.1 Card of use case ManageCustomerInfoName ManageCustomerInfoCode ManageCustomerInfoParent Object-Oriented Model 'UC_CarRental'



II.8.8.2 Action steps of use case ManageCustomerInfo Add new customer: EditCustomerInfo DeleteCustomer SendCustomerToBL RemoveCustomerFromBL ModifyCustomerRentHistory

II.8.9 Use case ManageUserAcount

II.8.9.1 Card of use case ManageUserAcountName ManageUserAcountCode ManageUserAcountParent Object-Oriented Model 'UC_CarRental'

II.8.9.2 Action steps of use case ManageUserAcountAdmin can:

add many user edit users informatio delete use set the privileges

II.8.9.3 Pre-condition of use case ManageUserAcount User Should log in as admin(manager)


Sybase PowerDesigner - Web viewSybase PowerDesigner. Object-Oriented Model Report. Model:...

Documents

Transcript of Sybase PowerDesigner - Web viewSybase PowerDesigner. Object-Oriented Model Report. Model:...