I intend to give you a better understanding of what a robust and efficient development process should look like: from gathering the requirements of the team, up to coding the solution, including going through the deploy until publication.

4. WHY SHOULD I CREATE AN ADD-IN?

5. Automatio
n
Added
value
Interoperabilit
y

6. WHAT DO I NEED TO CREATE AN
ADD-IN?

8. DESIG
N
ANALYSI
S
PLANNIN
G
DEVELOPMEN
T
PUBLICATIO
N
FEEDBAC
K

10. Developme
nt
Analysis
Planning
Design
Publication
Feedback

11. HOW TO CREATE AN ADD-
IN?

12. 0
1
ANALYSI
S

19. RO
I

21. • Goals
• Problem
Statement
• Proposed
Solution
• How is expected to
work
• Exclusions
• Storytelling
• Features

22. 0
2
DESIG
N

28. SINGLETON
PATTERN

31. Autodesk Icon
Guidelines 25X25 px
120X120
px
120X120
px

33. KISS +
UX
AESTETHIC
S

36. 0
3
PLANNIN
G

42. • Brief
description
• Dependencies
• Versions
• Installation
• How to
contribute
• About

45. 0
4
DEVELOPMEN
T

47. • Naming conventions
• Comments
• Properties vs
Variables
• One action per
class
• One statement per
line
• Etc, etc

48. PROJECT 01
PROJECT 01
PROJECT 01
PROJECT 01
PROJECT 01
PROJECT 01

50. • Sanity Checks
• User Case tests
• Exploratory Testing
• Quality level

52. 0
5
PUBLICATION

54. WEBSIT
E
AUTODESK

56. 0
6
FEEDBAC
K

62. Don’t miss our updates!
LinkedIn: ENGworksUS
Website: www.engworks.com
Twitter: @ENGw_Innovation

63. Thank you!