Scribd
Upload
66 views12 pages

4.implementation Methodology - Design Build Test

This document outlines the implementation methodology, including the design, build, and test phases. In the build phase, it describes 8 criteria for considering development done and provides a timeline tracking progress across tasks. It also introduces the Robotic Enterprise Framework (ReFramework) which enables collaboration and includes repetitive implementation steps, proper exception handling, recovery abilities, effective logging, and other benefits. Finally, the test phase describes UiPath's three phase testing approach of unit testing, functional testing, and user acceptance testing to ensure no critical bugs reach production.

Uploaded by

jsoe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
66 views12 pages

4.implementation Methodology - Design Build Test

This document outlines the implementation methodology, including the design, build, and test phases. In the build phase, it describes 8 criteria for considering development done and provides a timeline tracking progress across tasks. It also introduces the Robotic Enterprise Framework (ReFramework) which enables collaboration and includes repetitive implementation steps, proper exception handling, recovery abilities, effective logging, and other benefits. Finally, the test phase describes UiPath's three phase testing approach of unit testing, functional testing, and user acceptance testing to ensure no critical bugs reach production.

Uploaded by

jsoe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Implementation Methodology

DESIGN
Please open the Process Design Document available in the
Course Documentation folder

Slide 2
Please open the Test Cases Template available in the
Course Documentation folder

Slide 3
Implementation Methodology

BUILD
Tracking the progress

Criteria for considering the development done for a process

1 Code produced (completed all ‘ToDo’ items in code)

2 Code commented according to best practices, checked and ran against current version in source control

3 Peer reviewed (or produced with pair programming) and meeting development standards

4 Passed unit tests

5 Deployed to system test environment

6 Passed System Integration tests and signed off as meeting requirements

7 SDD document filled in and approved

8 Relevant documentation/diagrams produced and/or updated

Slide 5
Tracking the progress

Scenario No. of days Timeline (End Date) Owner Status


Task 1 3
Task 1 Unit Testing 5
Task 2 2
Task 2 Unit Testing 1
Task 3 2
Task 3 Unit Testing 1
Reporting dashboards 1
Post code-review changes 2
SDD fill in 1
Migrate workflow to Test 1
System Integration Testing 3

Slide 6
Please open the Development Specification Document
available in the Course Documentation folder

Slide 7
Robotic Enterprise Framework - ReFramework
Enables collaboration between developers

Repetitive implementation
steps

o Initializing various applications


o Reading configuration parameters
o Capturing errors
o Closing all the applications
o Returning to a ground state once the
process finishes

Slide 8
Framework benefits

o Proper exceptions handling


o Recovery abilities
o Effective logging
o
o
Thank You!
Reporting functionalities
High maintainability
o Extensibility
o Reusability
o Ease of deployment
Implementation Methodology

TEST
Testing plan
UiPath has developed a three phase approach for the testing process, making sure
no critical bugs will reach the production environment. Paired with code review
sessions and approval board meetings, the methodology ensures quality in deliverables.

UT FT UAT

Unit Functional User Acceptance


Testing Testing Testing

Individually testing each End-to-end testing done End-to-end testing done


functionality of the by the development by the product owner,
automation made by team on the QA followed by the go-live
developer & discussing it environment, supervised meeting
in code review sessions by the Solution Architect

Slide 11
Thank You!

You might also like