Jason Smith completed work on three phases of a CREST API-based portal project for managing Microsoft product purchasing and licensing. When Microsoft ended support for important CREST functions, he implemented a fully functioning interface to another API. Jason also provided UI fixes for the Stratogator project when blocked and started addressing issues in Azure deployment code. He then created a fully functioning new portal using the CSP REST API, exceeding other providers' capabilities. Jason hardened the code against attacks in preparation for the portal's wide release. His manager notes that Jason exceeded expectations in delivering quality work quickly while facing challenges.

1. 1
Managed Solution/Stratogator
Software Development Team Review
Developer: Jason Smith
Review Period: January 18 – April 18 2016
Next Review: July 18, 2016
Assignment(s)/Accomplishments
Jason’saccomplishmentsheetisattached. The followingare mycommentsonhischallengesand
accomplishments.
Projects
Jasonhas actuallyhadone large challenge thatbreaksdowninto3 phases. I have detailedthembelow,
alongwithaccountingforwork onStratogator.
CREST API based portal
Thisis a way forusersto manage Microsofton-demandproductpurchasingandlicense management.
Jasonwas directedtouse PHPfor quickerdevelopment. Unfortunatelythere were noexamplesof PHP
usingthisinterface andthe C# examplesreliedonlibrariesthathidinformation usedinthe transaction.
Jasonlearnedhowtoread and understandthe APImanual pagesanddeterminehow totestforwhat
was leftout. The UI side wasacceptable butunfinishedwhenMicrosoftsuddenlyendedsupportfor
importantCREST functions. He implementedafullyfunctioninginterface tothe ManagedSolution
CreditCard reconciliationagent’sAPI.
Stratogator
Jasonprovidedseveral UIfixeswhenhe wasblockedbyMicrosoftonthe CREST-basedportal. He also
startedto addressshortcomingsinthe Azure deploymentcode.
Newly Released CSP REST based portal
This wasa seconditerationof the portal forusersto manage Microsofton-demandproductpurchasing
and license management. Buildingonworkdone byChrisBoyntonwhoprovidedPHPsupportingthe
newloginAPI, andhisownpreviouswork,Jasoncreatedafullyfunctioningportal thatbehavedasthe
Microsoftsite did. It exceedsthe capabilitiesof otherproviders. Hiswork allowedhimtoeasilyupdate
productimageswhenthe oneshe wasusingwere replaced. There issome technical debtonthe UI
renderingside butthe systemworks. The stakeholderswere veryimpresseswiththe finalproduct.
Prepare Portal for Wide Release
In preparationforwide release of the portal,Jasonrevisitedsecurityconcerns. UsingOWASPwarnings
and securityguidance fromthe web,he hardenedthe PHPcode againstattacks. He addedmailer
capabilitytothe error log,invoicing,andinitial sign-up. Once alargersystemisconfigured,hardened,
and givenDNSrecords,the Active Directoryentryforthe ACScallbackcan be changedand the system
can go live.(Thisisworkdone byChris.)

2. 2
Otheritemsof note
 Refreshedknowledgeof PHP
 LearnedPHP database interface
 LearnedCREST API
 Learned CSP REST API
Performance Appraisal
Jasonhas exceededexpectations. Whengivenalarge task withmanyunknownshe drove himself to
perform. Whenfacedwithlackof vendorsupport,he experimentedtofindthe informationhe needed.
In spite of unrealisticexpectationsonthe difficultyandscope of the projectfromuppermanagement,
he deliveredquicklyandwithquality.
Expectations/Goals for Developer
In the nextreviewperiod:
1. Continue supportof the CSPportal deployment
2. Addresstechnical debtonthe CSPportal
3. Beginconversionof CSPtoJava
4. Stratogatortasks, if time allows
Expectations/Goals from Developer
Jason’sgoalsare:
1. Earn the trustof CSP portal stakeholders
2. Meetmetricsfor hissigningchallenge
Suggestions/expectations for Lead
None
Issues
Comments About This Review

3. 3
_________________________________ ___________
Developer Date
_________________________________ ____________
Software Lead Date