Software Engineering > Report > Software Development at Public Works and Procurement Coop Report 2016 (All)

Software Development at Public Works and Procurement Coop Report 2016

Document Content and Description Below

Software Development at Public Works and Procurement Coop Report 2016 Adetayo Odueke todue043@uottawa.ca 7834338 Software Engineering Public Works and Procurement2 Abstract The purpose of the... document is to describe my summer of 2016 coop placement at Public Works and Procurement Canada. While working at Public Works most of my work centered on the creation of an application. The development process I went through to set up this application, including the issues I had to address and the solutions to them, make up the majority of this report. Table of Contents Abstract 1 Table of Contents 2 Table of Figures 2 Introduction 3 Application Requirements 3 Database 4 Application Flow 4 Setting Up the Environment 8 SQLite Decisions and Problems 8 Java decisions and problems 9 Conclusion 10 Bibliography 11 Table of Figures Content Server Configurations Manager 5 Choose Panel 6 Push Panel 6 Push Configurations 7 Manage Server List 7 Add Server 73 Modify Server 8 Delete Server 8 Introduction I am a coop student working with the GCDOCS team at Public Work and Procurement Canada, formerly known as Public Works and Government Services (PWGSC). As a department, Public Works mostly focuses on helping other departments of the government do their job. GCDOCS is a software used to manage all of the documents for the government. It allows for documents to be stored, edited, and shared in a secure environment, similar to an intranet version of google drive. I was supposed to start working on May 2nd, but due to delays in processing my letter of offer the beginning of my employment was delayed by a week. This meant that I didn’t start until May 9th. In the beginning I spent most of my time getting organized and becoming acclimated to my work environment. I met many important people in the department, got my equipment, and learned the basics of GCDOCS. I learned about GCDOCS through meetings, discussions with my supervisors, and an information book. I also had to spend time getting various credentials and equipment. All of this took time, and in some cases never came through, such as my work phone which was never usable, and my login into the phoenix pay system which was never made available. Phoenix is a new system that handles the pay of the entire government in general the migration to it had many issues, causing payment issues across the board. These affected me personally both by delaying my pay for almost 2 months, and when I started to get paid it was not at the sufficient rate. Dealing with these pay issues warranted a lot of additional paperwork and dealing with both my HR representative and the pay center directly with a seemingly minimal effect. Outside of these issues my work environment was mostly pleasant [Show More]

Last updated: 2 years ago

Preview 1 out of 11 pages

Buy Now

Instant download

We Accept: