Declarative development is fun and powerful, but sometimes implementing business processes requires Apex, and it becomes your job to define the requirements and create a functional specification to pass on to the developers. Good developers will build to your requirements so you’d better make sure they are clear, accurate and comprehensive.
Without a well thought out functional specification, you can quickly find yourself in an endless series of QA iterations as those ‘oh, I didn’t think of that’ items crop up, costing you down-time, development time and money.
In this session we’ll walk you through the common scenarios you need to consider when defining functional requirements. You’ll learn how to build in extensibility, and how to write a functional requirements document that developers can use to code and write unit tests against, so that you will get the functionality you need the first time.
Roan Bear Consulting
Roan Bear’s oldest dev org is dated 2005, and she’s been hooked on the platform ever since. She’s been involved as a consultant, and as co-founder and part of the team that designed a fully native product at Full Circle Insights. She's a 2x Dreamforce speaker, and expects to be a Trailhead Ranger by the Sunnyvale Global Gathering on November 13th (or she’ll eat her hat).
Roan Bear implemented her first web-2-lead form in 2003, and was astounded that marketing metrics could be measured! She got her first developer org on June 10, 2005, and yes, she keeps it with that year’s UI because she’s that type of geek. She liked the Salesforce platform so much she became an authorized partner (that test was hard), then a certified consultant. She then co-founded Full Circle Insights, a marketing analytics company and Salesforce ISV, and was part of the team that designed its first fully native product. She's a 2x Dreamforce speaker and 1x Forcelandia speaker. She’s currently on semi-sabbatical, chillin’, travelin’ and dabblin’.