Open Source Tools Module BSpec Gang Cheng Dipesh

  • Slides: 11
Download presentation
Open Source Tools Module B-Spec Gang Cheng Dipesh Khakhkhar Navaneeth Rajkumar

Open Source Tools Module B-Spec Gang Cheng Dipesh Khakhkhar Navaneeth Rajkumar

Architecture: Context Diagram

Architecture: Context Diagram

Architecture: Module Diagram

Architecture: Module Diagram

Reference Documents · Customer A-Specification – Web-Service based Project Center, A-Spec, Version 1. 1

Reference Documents · Customer A-Specification – Web-Service based Project Center, A-Spec, Version 1. 1 27 September, 2004 · Operational Concept Document – Project Center System, A-Level Specification, Version 1. 3 16 October, 2004 · Technical Presentation – – Project Center System, Architecture Review, 11 October, 2004 NAnt Build Tool, Dipesh Khakhkhar, 11 October, 2004 NUnit, Navaneeth Rajkumar, 11 October, 2004 Using Source Code Control Effectively, Gang Cheng, 11 October, 2004

Requirement: DFD

Requirement: DFD

Functional Requirements · Open Source Tools Manager Process – Shall communicate with the Communication

Functional Requirements · Open Source Tools Manager Process – Shall communicate with the Communication Service Module based on XML messages – Shall create and maintain the open source tools wrapper – Shall dispatch requests to corresponding open source tools wrapper – Shall retrieve results from wrapper and send them to the UI and Tracker Module through the Communication Services Module; – Shall collect error messages from wrapper and send them to the UI and Tracker Module through the Communication Services Module – Shall add time-date stamps and user information into the XML message by using the XML Message Handler Module

Functional Requirements · Source Code Control Process (CVS Wrapper) – The Source Code Control

Functional Requirements · Source Code Control Process (CVS Wrapper) – The Source Code Control Module shall accept commands, options and path from OSTM. – The Source Code Control Module shall run the CVS Client Tool without blocking the OSTM. – The Source Code Control Module shall run CVS Client for version control of code, build scripts and tests. – The Source Code Control Module shall support check in, check out and creation of new files by using CVS Client. – The Source Code Control Module shall record all changes made to the CVS code base and send it back to OSTM, so that OSTM can communicate it to the change log in a suitable XML format. – The Source Code Control Module shall retrieve the errors if any that occurred during the running of CVS Client and send them to the OSTM.

Functional Requirements · Build Process (NAnt Wrapper) – The Build process shall support building

Functional Requirements · Build Process (NAnt Wrapper) – The Build process shall support building of user specified source files incorporating libraries on which it depends using NAnt. – The Build process shall send the error message to OSTM which will send it to the UI process if source files are not supported by NAnt. – The Build process shall allow the user to define the options for a build and build the necessary script to run NAnt. The options for the build are captured in the information sent by the UI. – The Build process shall generate a XML message containing the results of the build after running NAnt and send it to the change log. – The process shall create a log file temporarily for the build result on user’s machine and use it to create message to send to the change log and to the UI. – The process shall delete the temporary log file after use. – The Build process shall display results of the build to the user. The process sends the result of the build to OSTM which will send it to the UI process and it will display the result to the user. – The Build process shall allow NAnt to be run without the changes being recorded into the bug tracker for testing purposes.

Functional Requirements · Test Process (NUnit Wrapper) – The Test Module shall accept the

Functional Requirements · Test Process (NUnit Wrapper) – The Test Module shall accept the path name of the dll or exe file to be tested and the NUnit testing options. – The Test Module shall run the NUnit Test Tool without blocking OSTM. – The Test Module shall run NUnit to test the specified file using the options specified by the user. – The Test Module shall retrieve the errors if any that occurred during the running of NUnit and send them to the OSTM. – The Test Module shall retrieve the path of the output XML file which is generated after the successful execution by the NUnit, read the file and send it to the OSTM.

Functional Requirements · XML Message Handler Process – The XML Message Handler Module shall

Functional Requirements · XML Message Handler Process – The XML Message Handler Module shall parse and create XML format message – The XML Message Handler Module shall create the proper objects by analyzing the XML Tag – The XML Message Handler Module shall create the proper XML message based on an input object

End of Presentation

End of Presentation