My Motorola Experience August 8 th, 2013 Erich Kuerschner| 2013 Summer Intern Service Automation,...
-
Upload
andrew-ferguson -
Category
Documents
-
view
214 -
download
0
Transcript of My Motorola Experience August 8 th, 2013 Erich Kuerschner| 2013 Summer Intern Service Automation,...
My Motorola ExperienceAugust 8th, 2013
Erich Kuerschner| 2013 Summer InternService Automation, MOTOROLA SOLUTIONS
iProtect Classification as Appropriate
AGENDA
• Background Info
• Challenges
• New skills learned
• Projects: Development and Outcome
• What I will take away
• Q&A
About Myself
• Major: Computer Engineer
• Jr. at Iowa State University this Fall
• First professional work experience
• Interned with the Service Automation team this summer
Challenges
• Getting used to the new work environment
• Terminology
• New skills to learn
A Learning Experience
• New programming language- C#
• HTML
• ASP.NET
• Database management
• SQL
• Debugging techniques
My Projects
The Request Queue– Team Access– Submission Unlock / Delete– SA Portal Requests
System Launch Page (UO Launch Page)
Next Generation Tools (Checklist Tool)
Projects: Request Queue
• Web app designed to be a “one stop shop” for handling the various requests SA admins need to monitor from day to day.
• Would save time and improve upon the existing methods.
• Broken into three parts which spanned my entire time at Motorola.– Phase 1: Team Access Requests– Phase 2: RRR Unlock and Delete Requets– Phase 3: SA Portal Requests
A Step-By-Step Process:Phase 1 Mockup
Phase 2 Mockup
Request Queue: Outcome
• Overall success!• Published and currently
in use by David• Proud of the project’s
evolution and my increased independence as time went on
Lessons Learned:1) The importance of
mockups and pre-dev design.
2) How to test and debug web apps.
Projects: System Launch Page
• Iterated upon an existing web page in the SA web portal, adding some additional functionality.
• Create alternate form for UO to use when prepping for a big upgrade.
• Will promote a more organized way to manage the process in which other teams within Motorola contact SA for system launch needs.
Launch Page: Start up view
Launch Page: Outcome
• Published recently and ready for use.
• Developed independently
Lessons Learned:1) Strengthened web dev
skills.2) How to meet requirements3) Defect handling and
OnTime.
Projects: Checklist Tool
• Part of SA’s ‘Next Generation’ toolset.• The Checklist is a comprehensive tool which acts as
a visual aid and planner to CCSI engineers and PMs.• Will help keep engineers organized and on task.• Will ensure CCSI projects are on schedule – very
important!! • Small group project – exciting new environment to
work in.• Role: Backend code, class library, database queries
and main logic.
Checklist Tool: Outcome
• Currently still in development.
• Documenting code for easy hand-off to successor.
• Enjoyed the group brainstorming meetings and check-ups.
Lessons Learned:1) Teamwork.2) How to effectively
collaborate on large project using tfs.
3) Staying organized.
What I Will Take Away
• Always come prepared• Don’t be afraid to ask questions• Keep notes and records of daily progress• Picked the correct major• Practical applications
Thank You!
• John Coombes• Hussain Morbiwala• Service Automation• Craig Ibbotson• Motorola HR
Any Questions?
MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners. © 2010 Motorola, Inc. All rights reserved.
iProtect Classification as Appropriate