Introduction Background Information This assignment is based on Maersk Line who is t he global container division and the largest operating unit of the A.P Moller of Maersk Group which is Danish business conglomerate.
Problem Statement The Maersk Line is trying to focus more on business growth and company flexibility. Because of that, they wanted to cut down most of t he expenses in the IT sector and try tr y to make it more productive. One of the strategy, they wanted to implement is to transfer all their data servers in the whole world to one virtual cloud machine, which can cut down them from buying hosting server hardware expenses. Since Microsoft Azure provide one of the world best cloud storage service. They wanted to move all of their datas to there and centralize it.
Objectives
The objective of this project is to : 1. To deploy the system to Azure according to appropriate scales and business needs. 2. To provide a reliable and faster interactive inter active system for the company and customer to use. 3. To reduce as much of pass server data latency issues as much as possible. Scope
First, the developer will implement the main function which is the login and register part. And make sure everything works accordingly and perfectly. Secondly, the system will include the booking process which will let the agent to help the customer to book for available slot. And by using Azure cloud service, the developer will make sure it runs smoothly. Lastly, is the developer will deploy it to Az ure cloud and using traffic manager control cont rol to manage incoming and outgoing traffic.
Requirement Specification
Maintainability: The system will need to have constant update and upgrdate to ensure the system always run on the latest technology and system. Monitoring: The system must constantly get monitor to identify any problems or t roubleshoot problem that need to be change or update. update.
Main Function of the System Register Function
The system allows staff to register agent profiles and also let agents to register customer profile. Login Function
The system allows users to login l ogin to the system but giving their username and password. Edit Function
The system allows users to edit their details when they need to change it. Delete Function
The system allows users to delete the information they want to delete. Book Function
The system allows agents to book the time slot schedule for the customers.
2.0 Project Plan Project plan is one the most important i mportant element in the project to shows the overall progress that you had done in the project. At here the devel oper will show what is the task that had been done and when was executed and when when was finished.
Task Id
Task Names
Days
Start Date
End Date
2017
2017
Status
1.
Register
2
2-3-2017
3-3-2017
Complete
2.
Login
1
2-3-2017
2-3-2017
Complete
3.
Create Entity Framework Design
2
3-3-2017
4-3-2017
Complete
4.
Connect to the entity framework database.
3
4-3-2017
7-3-2017
Complete
5.
Create auto generate create, edit, delete and details controller MVC.
4
5-3-2017
9-3-2017
Complete
6.
Booking Process
1
9-3-2017
9-3-2017
Complete
7.
Deploy to Azure server
3
9-3-2017
12-3-2017
Complete
8.
Design Website Layout.
2
9-3-2017
11-3-2017
Complete
9.
3.0 The Architectural Diagram
The architecture diagram below shows how the Maersk Line web service works on the Azure cloud. First it will deploy on a local host server and then it will connect to the Azure cloud local resources web services to deploy to the cloud. And then, there will be a SQL database backend to connect to the database server and also a traffic manager to manage the outgoing traffic control.
Connect to Traffic Manager to manage traffic outgoing control.
Deploy to the web app service in Azure.
Connect to Database in Azure
Use Case Diagram
Figure 1 USE CASE DIAGRAM
Entity Relationship Diagram
Figure 2 Entity Relationship Diagram
4.0 Implementation Publishing the web app to Azure The first step is to t o register the application in the Azure Az ure by registering your application to it in the Azure Dashboard portal.
Figure 3 Main Resources Group Dashboard
This is where the resource group where you can see there are two different r esources group which are webappsoutheastasia and webappWesternEurope. These are the resources group that the developer is going to choose to develop the web app.
4.1.1 Web App
Figure 4 Select Web App
This image shows that the developer will choose t he web app features to deploy to the website.
Figure 5 Enter Web App Details
This image shows that after you input the app name which will be the website name that you are going to host. Then, you will need to choose the resource group which at the first image that had shows. After that, that you will need to choose the location which is the nearest which will be South East Asia.
Figure 6 Web App Service
After successfully created, you will see the app services will have the the web service name you created.
Connect To the SQL Database
Figure 7 Database
This part is where the developer type in the database name info to create the database.
Figure 8 Create Database Server
Then this part is where the developer need to create a server and then type in the server name and the admin and password login details to be use later in the connection string part to connect the app project to the Azure database.
Figure 9 Select Database Scaling Option
And also the user will also need to choose a pricing tier which is suitable for the database size.
Firewall Setting
Figure 10 Add Firewall Setting
In the firewall setting the user need to client IP address of the current IP address of the computer that is using it. So, that the SQL Server connection can access it.
Figure 11 Database Connection String
After that insert his ADO.NET string provided in the connection string in the web.config file in the visual studio project.
Application Scaling For this project application scaling had been done for both web app and SQL database. This is a necessary step to optimize the running speed time of the system.
Figure 12 Web App Scaling
This is the option page where you can see there are a Scale up and Scale out option for you to optimize the web app type. By scaling up, you will be able to make the web app much faster and optimize. By scale out, you will try to transfer out the data to some other server to help you to balance out the traffic. In later we will talk about the traffic manager control, which is the one that will optimize the traffic incoming and outgoing calls.
Traffic Manager
At here, the developer will key in the name for the traffic manager and then choose the routing method as performance to optimize the performance of the web app.
For the traffic manager, deploying two or more different locations will optimize the web app traffic. The explanation to this is that the server when connected to different locations in the world, when there are people from Europe countries trying to access it, they will able to
get pinpoint to the nearest server location which is Europe, when is SEA it will point to South East Asia.
This is the overall architecture of how the traffic manager works. It, will balance out the traffic by distribute the server to two different locations, which then will search for the nearest server to suite the user needs.
Container Management System
Figure 13 Home Page
Test Plan and Test Dicussion The web application was tested on their performance test in Azure. This enabled the user to see the load the application can handled at the time set. Container Management System as follows: User Load: 20 Duration: 1 minute
System Testing The following section will demonstrate the system testing process which will shows the validation of the specific features and shows the error message for specific features.
For the login page, the user should type in the correct username and password only able to login to the system. If wrong, it will shows up error message.
For registeration, it will check for the all the field is it enter. If not, the error message will prompt out and said all the field is require to fill up, before register.
Testing Plan Unit Testing S.N.O 1
Test ID TID 1
Test Function Login
Description
i.
Actual Result
Enter
Login
correct
successful
username and password.
Login Unsuccessful
ii.
Enter wrong username wrong
Login
password
unsuccessful
iii.
Enter correct username
Login unsuccessful
wrong password
2.
TID 2
Register
Enter wrong username or password 10 times. i. Enter Username,
Register Successful
password.
ii.
Enter password length too
Register
short or
Unsuccessful
long or not complex enough.
iii.
Enter username
Register
length too
Unsuccessful
long.
iv.
v.
vi.
Enter wrong email syntax.
Unsuccessful
Enter wrong phone number.
Register
Register
unsuccessful
Didn’t fill
up all information details.
Register unsuccessful
User Acceptance Testing
Question Poor 1. How would you rate the interface design of the page? 2. How would you rate the colour used by the app interface design? 3. How would you rate the emergency button design? Comments Remarks:
Ratings (1-4) Fair 2
Neutral
3
3
Very Good
