3 Tier Architecture

3 Tier Architecture

View more presentations from guestd0cc01.

System Base Service Registration

Due to the last discussion in later session we should change our diagram to system base service registration.
In the customer base Service registration we encounter some problem which one of them will occur when the related customer is removed from the department .
Because of there are services that should be completed in any condition ,
we need to register our services based on related system.

Modify Of Person, Admin, Tech, Supervisor and Customer's class diagram

Incomplete form of diagarm A with some correction

For precise comparison between Diagram A and B I place UML form of diagram A .certainly this is not perfect one and need to be discussed in detail.

I removed the relation between customer and system classes and associated new relations from case and device classes and to customer class.

How to identify service process?

Let suppose that we identify each requested service based on related customer(the owner of the service)
one exception is that, if a customer was removed from the list , what happen to services which requested by this customer(employee) .
we can handle this exception in two different way :
1.we can remove requested service(s) created by this customer from the list of services.
2.flag these services as completed and close them.
but one problem exists :
there are services that should be completed unrelated of which one has requested them-the unconditional services- which should be completed under any situation.(should be discussed).

The question is:

how can we determine the customer independent services ?

Type Of Service

آیا نوع سرویس دهی بر اساس سیستم باشد یا مشتری؟

Problem, Troubleshooting & Report's class diagrams

corrective form of person's class diagram

REVISED OBJECT DESIGN DOCUMENT FOR CRM

this post is included a file document for crm project
You can download this document here .

System base Or Customer base

Person, Admin, Tech, Supervisor and Customer's class diagram sended by P.aghdashi

Person, Admin, Tech, Supervisor and Customer's class diagram

Person , Customer.Admin,Supervisor,Tech

Person :
Attributes :
Name
Family
OfficeAddress :
city
street
alley
no
postalCode
HomeAddress :
city
street
alley
no
postalCode
HomeTel
OfficeTel
Mobile
Email
Fax
Website
EducationLevel
EducationFeild
Faviorates
Username
Password
Sex
Birthdate
year
month
day
MarrialStatus
AboutMe
Job
IncomeRange
MessengerId
NationalId

Operations :
Add(all parameters)
Edit(all parameters)
Delete(all parameters)
Search(all parameters)

Service Class

In the later session the project team discussed about class attribute and operation .
here you can see the attribute and operation definition for the Service Class which is gathered and agreed by all members of the team.


service class :
The operations of the service class should be discussed in detail.
Below I explain parameter definition for each method of this class:

AddService(dateAdded, dueDate, relatedCustomer, priority, relatedSystem, serviceType, description, additionalcmment, importantData) //this method has clean definition and all parameters are clear to understand
EditService(all) // the word , all means that this method is overloaded and will be called by diffrenet types of parameter , it is called when the service info has to be edited
DeleteService(serviceId) //for delete a service from the list of services
Search(all) // we need different type of search among service list
ChangePriority(serviceId,newPriority) //Admin call this method to changing the priority of the services
ChangeProgress(serviceId,newProgress) // in each step tech must be updated the service progress by calling this method
ChangeNote(serviceId,newnote) //for editing the entered supervisor notes
ChangeAdminQuality(serviceId,newQuality) // each service has a quality stated by admin for changing its value this method must be called
AssignTech(serviceId,techList) //each service must be assigned to a tech
UpdateAssignTech(serviceID,newTechList) //for changing thech(s) assingned to a service
UpdateStatus(serviceId,newStatus) // for changing the status of the service ,each service may be at one of these status : active ,stopped or finished
ChangeTechDiagnosis(serviceId,newThechDiagnosis) //tech might be enforced to change his or her diagnosis this operation is responsible for tech diagnosis
ChangeDueDate(serviceId,newDate) // for changing the due date

Our Glossary

Here is a list of our common used terms and phrases to be unified to the whole project and all developers: 

1. ثبت = Add
2. نمايش = Show
3. تغيير = Modify
4. تاييد = Confirm
5. تعريف كردن = Define
6. تعريف = Definition
7. مشخصات = Specifications = Spec
8. پيغام = Message
9. ويرايش = Edit
10. Employee -> Customer
11. User -> Technician = Tech
12. مدير كل سيستم = Administrator -> Admin
13. مدير ناظر / عامل سيستم = Supervisor