Back to list
Views:   0
Replies:  0
Archived
,
Reply 1
$100/hr, or just buy a canned helpdesk app.

Mike
Michael Lopez, Aug 04, 2012
Reply 2
First of all Thanks for response.

We have request tracker (for help desk team) application andthat is running successfully for 4 client but we are facing support issues likeperformance, maintainability and versioning because we have different sourcecode for each client.

Current application has been designed before 5 year on DOTNET 2.0 and MS-SQL server 2005 without admin module, it only creates request,edit request and view request pages mainly.

Now we are planning to redesign RT (dot net 4.0) in such away that only one application will fulfill all requirements of any client thatmeans, it should have configurable admin module.

(1)   One client may have more than one customer andwe will setup all require objects for this customer like request status,request type etc (see the attached image).

(2)   There are most important roles like requestor, technician,manager and admin.

(3)   Each request has to follow request stateworkflow  like

“NEW”,”OPEN” ,“ASSIGN”,”ON HOLD”,”RESOLVED”,”CLOSE”and “RE OPEN”

We are in design phases that why I am trying to get perfect solutionof above issue.

I am looking positive response from your side……



Shujat Qureshi, Jul 22, 2012
Reply 3
Sorry, Question needs to be more clear (?)

If you have work flow kind of scenario , you could try  - Chain of Responsibility.
If you need to notify stakeholders involved, of any changes in status of a request - observer pattern.
Other than these two, more patterns get into picture, based on your requirements (if you can add detailed requriement, may be we can discuss further)

Thanks,
Tarriq Ferrose Khan
Tarriq Ferrose Khan, Jul 19, 2012
Stay Inspired!
Join other developers and designers who have already signed up for our mailing list.
Terms     Privacy     Licensing       EULA       Sitemap      
© Data & Object Factory, LLC.
Made with    in Austin, Texas