What I learned from the project with eGovernment

Since the project is coming to an end, I want to write something to make a conclusion and summarize what I have learned from that project.

Our project is to make a SLA between eGovernment and agencies since SLA could help them to solve their most pressuring problems.

Let's first have an overview about the business process and all the existing problems of eGovernment.

• They's main job is to receive and fulfill requests from different agencies they offer service. 
• The main requests from agencies are functional change requests and content change requests. 
• They need to evaluate the requests.
• After evaluation, some of the requests are passed to Squiz, which is a contracted company.
• Other requests are fulfilled by themselves. 
• They don't have a proper formal way for agencies to offer request. 
• They don't have an evaluation process to set the priority of change requests
• They don't have a clearly defined service level agree between agencies.

After have a brief overview of all their business and existing problems, we started to design the SLA for them. We divide the SLA into two parts. The first part is to design the service levels. The second part is to focus on change request evaluation, which is to design a priority matrix to prioritize different requests.

We designed the SLA referring to the eGovernment website, SLA draft and the SLA between Squiz and eGovernment. Also, we applied some EA methodologies.

I have learned a lot from that project. Not only better practiced what I have learned from the lectures, but also improved my communication, writing and analyzing skills.

Combine the lectures and the project, I now have a better view of EA. EA could provide a way for analysts to give a comprehensive analysis to the target organization.

For the eGovernment project, we successfully got the gaps and provided them a solution. We hope that could offer some help for them to build their own SLA.