Find this profile here: http://www.guru.com/freelancers/Software-Developer-Web-Programmer-Database-Consultant-Smart-Phone-Technology-Expert/Washington/Spokane/302376
|
Guru.com Profile - IanPhillips Find this profile here: http://www.guru.com/freelancers/Software-Developer-Web-Programmer-Database-Consultant-Smart-Phone-Technology-Expert/Washington/Spokane/302376 |
| Screen name: | IanPhillips |
| Profile ID: | 302376 |
| Tagline: | Design, Develop, Implement, and Test |
| Screen icon: |
|
| Membership: | Basic Member |
| Photograph: | No images have been uploaded. |
| Country: | United States |
| GMT: | Pacific Standard Time |
| Category rank: | 61860 in Programming & Databases |
| Quality score: | 0.00 |
| Feedback: | None |
| Money (year): | $0.00 |
| Money (all time): | $0.00 |
| Min. rate/hour: | $50.00 |
| Min. project budget: | Not specified |
| Member since: | 16 Nov 2001 |
| Last sign In: | 11 Apr 2009 1:29 AM ET |
| Quotes submitted: | 0 in last 30 days |
| Work onsite: | Yes |
| Experience: | 11 years |
| Highest degree: | Associate's Degree |
| Software skills: | Languages: • C#* • SQL* • Transact-SQL* • VB.Net* • ASP.Net* • Visual Basic* Other: • Software Architecture/Design • Automated Software Testing • Systems Analysis and Design • User Interface Design and Testing • Object-Oriented Programming (OOP) • Service-Oriented Architecture (SOA) • Component-Based Architecture • Unified Modeling Language (UML) • Rational Unified Process (RUP) • ClickOnce Deployment |
| Additional skills: | Professional: • Communication • Problem Resolution • Customer Crisis Intervention • Staff Management • Customer Service • Co-worker Support • System Analysis and Optimization Technical: • User Support • Database Normalization • Database design • Technology Research • Multi-threading • Robotics • Crystal Reports • Win32 API • Handheld Computer Programming (Windows Mobile) |
| Subcategories: | Programming Web Programming Database Design Smart Phone Applications Other - Technology Projects |
| Industries: | Health Care Industrial & Defense Technology & Internet Non-Profits & Charities Utilities |
| Highlights: | Position: Programmer Project: SiteWizard Insurance Enrollment Software Client: PennCorp Financial Services Manager: Paul Webb Duration: 1 Year Description: I was brought in to implement a graphical user interface that had already been designed by a graphics designer. The software was based on the COM architecture and was implemented as a shell application that was responsible for the presentation of the graphics and the hosting of the ActiveX controls for each insurance package. I implemented the shell in a way that allowed the application to be reconfigured without editing the code. I used private profiles and a fixed directory structure to facilitate the dynamic loading of graphics and controls. I finished the shell application before the rest of the components could be completed. I was then moved into the team that was working on the ActiveX controls for the insurance packages. Each control was developed as a separate project and I was involved in the full life cycles of three of those controls. Outcome: The software was rolled out and succeeded in the field. Position: Software Engineer (Telecommuting) Project: ADEPT Data Entry Framework Client: Analytical Sciences, Inc. Manager: Mike Apadula Duration: 1 Year Description: I was brought in to ASI to develop the replacement for an old console-based data entry system. ASI was a government contractor responsible for the collection and analysis of data from many of the National Center for Health Statistics surveys. They had been granted another series of surveys to process from the Center for Disease Control, but the federal government required that each of the cases of forms, and the individual forms, be tracked through the entire system. They wanted to be able to identify, at any time, the status of every form in the system. What's more, the software would have to restrict access to the data, so there would have to be user management and full auditing capabilities. When a piece of data was added or edited, the system would have to store the old value, the new value, and the person who made the change. The old system did not suffice. I architected the system as a framework that would allow developers to add surveys to the system without editing the actual system code. It was a distributed system with full data tracking and audit capabilities. The architecture did not end up supporting the end requirements of the system (the requirements changed), so I had to refactor much of the system half way through. Ironically, the architectural changes were a reversion to my preferred architecture. My initial architectural design was rejected because it would take too long to implement. I had estimated ten months to design, develop, test, and roll out the architecture, but the project manager and primary domain expert required me to change the design so that the project would be done in six months or less. After the stripped down architecture failed and the older architecture was factored in, the project was completed in twelve months. Even though I was constantly requesting assistance on the project, I was denied assistance until the last three months of the project when I was granted the assistance of a very junior programmer (he had never worked on professional code). Outcome: The software was rolled out and succeeded in the field. Since I was telecommuting, they hired a local developer to support the system. Position: Software Engineer / Tech Lead (Contractor) Project: ePoss Retail Store Management System Client: Magnetic North, Inc. Manager: Subrata Ghosh Duration: 6 months Description: I led a team of developers who were working on a project that was inherited by Magnetic North. The ePoss project had been in development for over a year and a half. Initially, the owner of the project contracted it out to a company that did the initial database design and architecture. The owner had many falling outs with the initial design company and withheld payments to the company. As a result, the designs and initial architecture were only halfheartedly done. The contract went to another company to finish up but, by that time, the database was a mess (undocumented, barely 1NF, and without any referential integrity), the architectural documentation was lost and all comments had been removed from the code. The new contractor was destined to fail. After they gave up, the contract came to Magnetic North. My first introduction to the system was seeing the database schema plastered across the wall of the development room. Within ten seconds, I stated that the database would have to be redone. I was told that that was not in the contract and that the client had put a freeze on changes in the database. I started to get a sinking feeling. When I asked to see the architectural documentation and was told that it doesn't exits, I was having alarms going off. A look at the code reassured me that the project was not supportable. The client told me that they believed that the software was 75 percent done, and they just wanted us to wrap it up. Even though I told the project manager that there was no way to actually finish the job, I was told to do my best. After the six months of my involvement in the project, the project manager believed that the software was ready for release to the client. It was well known that the software was buggy. I estimated it as 90 percent done. At this point, though, I was laid off and moved on to other projects. Outcome: Magnetic North is still trying to get this software stable. Three months after I left, the new Tech Lead estimated that the software was still approximately 90 stable. I am glad that I was able to work on this project. It gave me invaluable insight into the anatomy of a failed project. I can now better identify project risks and I am willing to turn down projects that are not able to be completed. Position: User Interface Architect (contractor) Project: eCorp Retail Chain Management System Client: Magnetic North, Inc. Manager: William MacHugh Duration: 2 Weeks Description: I collected user interface requirements and created a look-and-feel prototype for the entire eCorp system. I used the prototype to collect further requirements and responded with updated prototypes. The domain experts and management representatives were so pleased with the interface that they, without seeing the final system, requested the interface to be retrofitted onto existing products. Outcome: The client accepted the prototype and the project was started. Position: Software Engineer (contractor) Project: eCorp Retail Chain Management System Client: Magnetic North, Inc. Manager: William MacHugh Duration: 6 Weeks Description: I architected to specification a COM component that manages Crystal Reports. The software was designed to be self-contained so that it could be reused in other applications. It was implemented as an ActiveX control and had the ability to be pointed at any OLEDB database. Much work was focussed on developing an affective API for the component so as to minimize later development efforts. Outcome: The project was completed, tested, and integrated into the eCorp system. Magnetic North has at least one request for the component to be integrated into another system. Position: User Interface Architect (contractor) Project: TL-Pro Power Grid Design System Client: LineSoft Manager: Subrata Ghosh Duration: 6 Weeks Description: LineSoft had a problem. They had many tools that were all sold under different wrappers and each had a different interface. They had made a suite of tools that were sold to companies as a single package, but the grouping was loose. There was one start-up screen that would allow you to launch the other programs. Their software was complex. It has more features exposed to the user than any one user could ever use without extensive training. Even though their software was, arguably, the best available, LineSoft wanted its next release to solidify its lead in the market for the years to come. I was brought in to manage the complexity of the user interface. I interacted with graphics designers to produce a look-and-feel prototype for the main system. LineSoft wanted to set aside any standards that are currently accepted that stood in the way of having the best software package. They agreed that the user interface would be skinable and support many high-end user interface techniques such as forced windows order, roll-up windows, docking pallets, and transparent error messages that froze up single processes instead of the entire application. I produced a prototype that was greeted with much enthusiasm. The client then put me to work on managing the complexities of the lower-level components. I worked with domain experts to learn their jobs so that I could design a user experience that would be intuitive and highly productive. During this phase, the requirements were being changed rapidly, so LineSoft opted to discontinue my services until they had a clearer picture of the software they wanted me to produce. Outcome: The user interface prototypes and requirements were well received. Position: Software Engineer (Contractor) Project: ePoss Retail Store Management System Client: Magnetic North, Inc. Manager: William MacHugh Duration: 2 weeks Description: I was called in to work on the ePoss system's register module for an NCR register. They called me because the communications modules for that register was written in COBOL and Magnetic North didn't have any engineers with experience in COBOL. I cleaned up and documented the existing COBOL code and added the code needed to implement NSF-checks tracking. I mentored junior level programmers on staff in how to support the existing and new code and I left my contact information in case there was a problem with my implementation. Outcome: I finished the COBOL code that I was contracted to complete. During the work, I identified that there was some C++ code that needed to be done to communicate with the COBOL. I could have done the C++ work, but there was a contractor who had direct experience with the code and the COBOL-to-C++ communication process. I contacted that programmer who confirmed his availability. I gave the information to the head of Magnetic North and the contract was fulfilled. Position: User Interface Architect (contractor) Project: TL-Pro Power Grid Design System Client: LineSoft Manager: Subrata Ghosh Duration: 3 Days Description: LineSoft had proceeded in the development on some of the components for the TL-Pro system after I had been laid off. These components were implemented in standard executables. The suite was to be presented at an IEEE convention in less than a week when they called me in. The programs were almost ready to be shown, but the system had been marketed as an integrated power grid design suite. They were only short on the "integrated" part. I was called in to take the existing software executables and make them look as if they were all running as a single program. Further, they wanted the application skinned and some other user-interface elements implemented. I did everything that was requested in the course of three days. Outcome: The software was completed with two days to spare and it was sent to the convention. At the convention, the integrated suite consistently drew one of the best crowds and the presenters returned with offers to but the software package as soon as it could be finished. The presentation went better than any of the presenters had expected. |
| Work terms: | The professional has not written profile Work Terms. |