110 likes | 187 Views
PROCESS TOOL. What we have now:. SharePointUtil ProductStudioUtil Visio Parser. Visio Parser. Product Studio. Retrieve Process. ProcessTool. Scan/Create Bug. Scan/Upload Files. SharePoint. Your MailBox. SharePointUtil ( Call WebService Provided By SP ). CopyService
E N D
What we have now: • SharePointUtil • ProductStudioUtil • Visio Parser Visio Parser Product Studio Retrieve Process ProcessTool Scan/Create Bug Scan/Upload Files SharePoint Your MailBox
SharePointUtil(Call WebService Provided By SP) • CopyService • Copy(Upload) files to SharePoint • DWSService • Create Folders in SharePoint • ListsService • Get the entries in one List • Update the entries in Lists
ProductStudioUtil(Call API Provided By PS) • CreateBug • QueryBug • Generate The BugQuery • Load Bug From Bug Template
Visio Parser • Use the Visio API to Retrieve information of the process defined in Visio files. WorkItem Name:TestPlan WorkItem Name:TestPlanSignOff Depends: TestPlan Recursive Depends? No.
Current Functions • Notifier • Bug StatusDate • Project Status • Remind the user to close the bug resolved. (all through mail) • Filing Bug Machine • Documents(Template/BugQuery /DailyReport)
Why I use these techs • Eleminate • the costs of designing/developing new GUI • the costs of deploying/maintaining the DataBase • the costs of managing the documents
TODO: • Make The Visio Parser Work With Our Process Tool.
Then our tool will parse this file, then create the list according to this Visio File.
Once the user create one entry in this list. • Then the bugs according to this project will be filed then put it under the tracking of Process Tool.
That’s say: • If you want to define one new process, the only thing you need to do is create one new Visio file which describe your process. Then put one location our tool can fetch.