CT071 3 5 3 Ddac

e
INDIVIDUAL ASSIGNMENT
MAERSK LINE CONTAINER MANAGEMENT SYSTEM
CT071-3-5-3-DDAC
DESIGNING AND DEVELOPING APPLICATIONS ON THE CLOUD
NP3F1809IT
HAND OUT DATE: 25 May 2019
HAND IN DATE: 18 August 2019
WEIGHTAGE: 100%
_______________________________________________________________________
INSTRUCTIONS TO CANDIDATES:
1. Submit your assignment at the administrative counter.
2. Students are advised to underpin their answers with the use of references (Cited using
the Harvard Name System of referencing).
3. Late submissions will be awarded zero (0) unless extenuating Circumstances (EC) are
upheld.
4. Cases of plagiarism will be penalized.
5. The assignment should be bound in an appropriate style (comb bound or stapled)
6. Where the assignment should be submitted in both hard copy and softcopy, the
softcopy of the written assignment and source code (where appropriate) should be on
a CD in an envelope/ CD cover and attached to the hardcopy.
7. You must obtain 50% overall to pass this module.

MAERSK LINE CONTAINER MANAGEMENT SYSTEM
Presented By
Table of Contents
1. Introduction ........................................................................................................................ 1
1.1 Objective & Scope ...................................................................................................... 2
1.2 Requirement Specifications......................................................................................... 2
2. Project Plan ........................................................................................................................ 3
3. Design ................................................................................................................................ 4
3.1 Architectural Diagrams ............................................................................................... 4
3.2 Design considerations ................................................................................................. 4
3.3 Modelling .................................................................................................................... 5
3.3.1 Use Case Diagram................................................................................................ 5
3.3.2 Use Case Description ........................................................................................... 5
3.3.3 Class Diagram ...................................................................................................... 8
4. Implementation .................................................................................................................. 9
4.1 Develop Web application ............................................................................................ 9
4.2 Website Publishing In Azure..................................................................................... 10
4.3 Screenshot ................................................................................................................. 19
5 Test Plan & Testing Discussion (Functional & Performance)......................................... 22
5.1 Unit Testing ............................................................................................................... 22
5.1.1 Testing Admin ................................................................................................... 23
5.1.2 Testing Agent ..................................................................................................... 25
5.2 Performance Testing ................................................................................................. 28
6 Conclusion ....................................................................................................................... 29
7 References ........................................................................................................................ 30
Appendix: I .............................................................................................................................. 31
Marking Scheme .................................................................................................................. 31
Appendix: III............................................................................................................................ 34
Table of Figure:
Figure 1: Gantt chart .................................................................................................................. 3
Figure 2: The Cloud Architecture for Development Purpose .................................................... 4
Figure 3: Use Case Diagram ...................................................................................................... 5
Figure 4: Class Diagram ............................................................................................................ 8
Figure 5: Systems Files .............................................................................................................. 9
Figure 6: Create Resource Group ............................................................................................ 10
Figure 7: Successful to Create Resource Group ...................................................................... 11
Figure 8: Creating Web app ..................................................................................................... 12
Figure 9: Successful creating the Web App ............................................................................. 12
Figure 10: Creating SQL Database .......................................................................................... 13
Figure 11: New server .............................................................................................................. 14
Figure 12: Successful Creating SQL Database in Azure Cloud Server ................................... 15
Figure 13: Public ...................................................................................................................... 16
Figure 14: App Service ............................................................................................................ 17
Figure 15: Deploy Web Site .................................................................................................... 18
Figure 16: Home page .............................................................................................................. 19
Figure 17: Login Page .............................................................................................................. 20
Figure 18: Schedule of Shipping.............................................................................................. 20
Figure 19: New Agent Registration ......................................................................................... 21
Figure 20: Create new shipping Schedule ............................................................................... 22
Figure 21: Performance testing of the deployed system .......................................................... 28
CT071-3-5-3 –DDAC MAERSK LINE CMS
1. Introduction
Maersk Line is largest container shipping company. Maersk Group, a global container division
and the largest operating unit of the A.P. The company having customer 116 countries and
more than 374 offices. It is founded in 1928 it operates over 600 vessels and has a 2.6 million
TEU capacity. Company employs approximately 7,000 sea farers and it has 25,000 land based
people. (DJIA, 2019)
Danish shipping company it is the largest shipping company of the world. This company is
handling all the cargo so, company has large supply chain and it has difficult to handle all the
things. Company manager Soeren Lorenzen and Hewlett-Packard they decided find the
solution of shipping management. They think to make a system for overall business strategy
from the IT perspective.
For the manage all the supply chain Maersk Line company has develop their system from the
system they schedule all the things. They have large shipping management so they think the
hosting their system in Microsoft Azure because company had done this thing for the support
further business growth and increase organizational flexibility, Maersk decided to consolidate
all of its data centers and server rooms operating worldwide onto a virtualized platform.
1|Page
1.1 Objective & Scope

 Objective and scope of the system are as follow:
 Developing the system hosting in the cloud to manage the containers.
 System is deploying in cloud for expanding the business strategy of Maersk Line’s.
 It helps to manage booking process of Maersk Line.
 Able to deliver container in time and reduce the logistic cost.
 To scale the web application to accommodate the traffic of peak seasons.
 System will accessible both admin and agent for their easiness.
1.2 Requirement Specifications

 Developer has to develop a single tenant web solution that meets the following
criteria as below:
 Through the system all the import and export and transshipment processing should
be operate.
 System will able to scale the solution of company which should meet the needs of
demands during peak seasons.
 It should be improve the profitability, increases the productivity, reduce the cost
and optimizes resources and give the high performance for the company shipment.
 It has to be able to manage entire booking and manage schedule cargo shipment.
 The system should be able to assurance & reliability through Failover Management.
2|Page
2. Project Plan
Figure 1: Gantt chart
3|Page
3. Design
3.1 Architectural Diagrams
Figure 2: The Cloud Architecture for Development Purpose

This is the Microsoft Azure cloud architecture where company will deploying or hosting their
system. Main motive of hosting system in cloud while organization structure became complex
it means company wanted expand its business it has to difficult monitoring all the things. If the
system is in the cloud it is easy to manage all the things from anywhere. All the data are store
in cloud. It have so many definite like if any physical disaster occur in the company
organization data are safe in cloud. (Azure, 2019)
3.2 Design considerations

The design considerations are developed in order to draw the designers ' attention to applying
the principles and specifications of universal accessibility design to buildings and equipment.
In current structures, they can also be used to define obstacles.
The design factors are categorized into subgroups and displayed as reference facility bullet
points. (archsd, 2018)
4|Page
3.3 Modelling
3.3.1 Use Case Diagram
Login
Register Agent
View Schedule
Create Schedule
Admin
Agent
Add Item
Add Customer
View customer View Item
Figure 3: Use Case Diagram

3.3.2 Use Case Description
Use Case: Login
Summary: In the login page user have to input their valid username and password for the
access system.
Dependency: <<Include>> Credential Authentication
Actors: Admin and Guest
Precondition(s): This login page has connect to agent login page.
Main 1. User has provides their valid username and password then press login button.
Sequence: 2. System will check user’s input and verify the authentication from web server.
If the input value in invalid server will not allow to access the system.
Alternative Step 2: User input value id compare in the server database, if the input value is
Sequence: invalid system show the error message. After seen the error message user have to
input valid information for the access the system.
5|Page
Post With compare input information Web Server has identified the account type and
condition(s): redirected to the appropriate page with appropriate user access.
Use Case: Register as New Agent

Summary: Before direct login the login page Agent has to be register in the system
database, new user register is done by system admin.
Dependency: -
Actors: Admin
Precondition(s): Login by admin then connect to register page.
Main Sequence:1. While creating new account for agent there should give require information for
the new registration.
2. After providing required information press enter button for save the information
in data server.
3. Web server will store the entered information.
Alternative Step 2: If the input information is already exists account database, the system
Sequence: displays an error message to user and prompt user for next attempt.
Post After providing required information system show the success message.
condition(s):
Use Case: View Shipment Details

Summary: Agent view the details of a shipment record
Dependency: <<extends>> Manage Shipments
Actors: Agent
Precondition(s): For the viewing shipping detail User has logged first then click om view
shipment details navigation bar
Main Sequence:1. User have to click in view shipment details navigation bar.
2. The web server will redirect in view Shipment Details Page.
Alternative -
Sequence:
Post Page has redirect in next view shipment details page.
condition(s):
Use Case: View Schedule

Summary: Before booking any ship Agent has view the available shipping schedules
6|Page
Dependency: -
Actors: Agent
Precondition(s): After login agent has to click in view schedule navigation bar.
Main Sequence:1. User click on view schedule page. New Shipment link
2. The server will show the table of schedule in screen.
Alternative -
Sequence:
Post View schedule page will visible.
condition(s):
Use Case: Book New Shipment

Summary: Creates a new shipment record by agent.
Dependency: -
Actors: Agent
Precondition(s): After viewing shipment schedule agent has to book available time.
Main Sequence:1. User has to select available shipping schedule click on new shipping schedule.
2. User has to input required information.
Alternative Step 3: If Web server found invalid fields found, the web server will prompt an
Sequence: error message for next attempt.
Post System show new shipment record has been successfully
condition(s):
Use Case: Manage Shipping Schedule and creating new schedule.

Summary: Admin manage the shipping schedule records
Dependency: -
Actors: Admin
Precondition(s): User has logged in as Admin
Main Sequence:1. User click on Manage Shipping Schedule on Navigation Bar
2. The web server will redirect user to Manage Shipping Schedule Page.
Alternative -
Sequence:
Post System show the Manage Shipping Schedule successful.
condition(s):
7|Page
3.3.3 Class Diagram
Figure 4: Class Diagram
8|Page
4. Implementation
4.1 Develop Web application
For the develop Maersk Line’s Container Management System (CMS), Visual Studio 2017 is
used as the IDE. For develop front-end development HTML, JavaScript and CSS are used, for
the development of the application C# is used in the Back-end.
Figure 5: Systems Files
9|Page
The system is run in the locally and remotely because the system is hosting in the Microsoft
Azure. This system is hosing in the Azure cloud so it is possible to run remotely or globally.
For the database connected to the Microsoft SQL Server to store, update and retrieve data upon
requests.
All the development and implementation are first performed locally at the developer site to
ensure the efficient and effective delivery of the proposed system by allowing to perform
development, debugging, and testing at ease.
Developer has develop presentation layer of the company for the better visualization.
Developer should has to better understanding about the how to the pages are interlinked with
each other. Developer has to clarify creating the table, constraints, relationship and store
procedures. For that developer has to create sample database and test that database which is
working properly or not. After that developer has to start develop initial requirement of the
company also do the testing and debugging although the system is functioning properly or not.
After completing to develop the Maersk Line CMS before deploying the system there should
be done different type of testing like unit testing this type of testing has done by developer so
many time at the development. Integrating testing while completing the one task and also
completing another task at that time developer has done this type of testing. At last system
testing has done after completing the whole task, this testing is done by next person real tester.
4.2 Website Publishing In Azure

To deploying Website in Microsoft Azure by applying following steps:
Figure 6: Create Resource Group
10 | P a g e
First step in the Microsoft Azure cloud we should have to “Create Resource Group” at the time
of creating resource group we have to give the name of resource group and also select the our
nearest Microsoft Azure data server.
Figure 7: Successful to Create Resource Group
Here we are creating the successful resource group in Microsoft Azure cloud server.
11 | P a g e
Figure 8: Creating Web app

After creating the resource group we have to create “Web app” in the Azure Web service here
we can deploying our system or Web application.
Figure 9: Successful creating the Web App
12 | P a g e
Figure 10: Creating SQL Database

SQL Database is to create for the data store in cloud server. It is important things in cloud
without it application is not respond of client request. For the SQL connection we have to give
database name and server name.
13 | P a g e
Figure 11: New server

While creating the SQL database in cloud server we need to create “New server” this is for the
remote connection of system from cloud server.
14 | P a g e
Figure 12: Successful Creating SQL Database in Azure Cloud Server
15 | P a g e
Figure 13: Public

After creating all the condition in the Microsoft Azure developer is ready to deploy system in
cloud server. Developer will able to public in cloud server developer has to click in main page
of the system right click and next click on “Public Web App” and this page is visible in the
screen. Then click on “Profile” button select “Microsoft Azure App Service” and public it.
16 | P a g e
Figure 14: App Service

After publishing this page is visible in the screen developer have to login Microsoft Azure
login account for link to public after linking with Azure server it will get some required
resources from azure.
17 | P a g e
Figure 15: Deploy Web Site

After getting require resource from the Azure server system is ready to deploy in Microsoft
Azure cloud server. Above figure trying to show this page is ready to deploy system in cloud
server.
18 | P a g e
4.3 Screenshot
Figure 16: Home page

Above figure this the home page of the system where system user were able to login the
system by clicking in login navigation.
19 | P a g e
Figure 17: Login Page

Above figure is the login page after clicking the login navigation bar this login form will
public in the screen user have to enter require information for login like admin login
username “admin” and password “admin”.
Figure 18: Schedule of Shipping

After login the system user will able to see this page where guest or agent will able to see
shipping schedule by viewing the schedule agent can fixed the booking time.
20 | P a g e
Figure 19: New Agent Registration

From this page system will create or register new agent in the web server. After registering
the agent then agent will able to login in the system.
21 | P a g e
Figure 20: Create new shipping Schedule

Here in the page admin of the system will able to create new shipping schedule of new
shipment.
5 Test Plan & Testing Discussion (Functional & Performance)

For the testing propose of system the following testing are applying:
5.1 Unit Testing

In the unit testing, here will be tested a small part of the application like Admin login page or
agent login page or user login page this page are separately tested if these pages are separately
executable this unit testing part is successful. All these units must test done before integrated
into a component. (Software Testing Fundamental , 2018)
22 | P a g e
5.1.1 Testing Admin

Unit Test Case Steps Expected Result Actual Result
Login For the login Input Display the Display login
success of admin username success message success result
And password and redirect user then redirect
press login to Admin in the Admin
Button Interface. Interface.
For the validation Input the On the screen On the screen
random display Error display Error
username and Message. Message.
password then
click on login
Button
Create new Register new 1. Go to Display the Display the
Agent Agent in the register page, successful add successful add
system. Fill all the the new Agent in the new Agent
required the system. in the system.
information.
3. Click on
“Register
button”
Chick register 1. Fill only It will display It will display
validation. one field only error message on error message
Agent name the screen. on the screen.
2. Click on
Register
button
View on Chick View 1. click on Display the Display the
Schedule Schedule ‘View View Schedule. View
page. Schedule’ Schedule.
from
‘Schedule’
drop down
23 | P a g e
Create Create shipment 1. For the Display the Display the

shipping Schedule ‘Create successful successful
Schedule shipping creation and add creation and
Schedule’ schedule to add schedule
from database. to database.
‘Schedule’
select on
Schedule
navigation
bar.
2. Fill the
ship details
3. Click
Create on
button
Create Schedule 1. Fill in part Show Error Show Error
details not filled in of the details. Message. Message.
completely 2. Click
Create button
Viewing For Viewing Ship 1. click on Display the Display the
Ship Items Items ‘Schedule’ tab interface of ship. interface of
2. Click on ship.
‘View Item’
on specified
schedule.
No Item seen on 1. Click on Display ‘No Display ‘No
Ship ‘Schedule’ tab Item Assigned’ Item
2. Select message. Assigned’
‘View Item’ message.
on specified
schedule.
24 | P a g e
5.1.2 Testing Agent

Unit Test Case Steps Expected Result Actual Result
Login For the login Input username Display the success Display the
success of And password message and success
Agent press login redirect user to message and
Button Agent Interface. redirect user to
Agent
Interface..
For the Input the It will display error It will display
validation random message on the error message
username and screen. on the screen.
password then
click on login
Button
Register new 1. click on Display customer Display
Create new C in the ‘Register’ page registration success customer
Customer system. 2. Fill required and add customer registration
information of to database. success and add
Customer form. customer to
3. Click on database.
Register button
View View 1. Select Display Schedule. Display
Schedule Schedule ‘Schedule’ tab Schedule.
View 1. Select Show ‘No Schedule Show ‘No
Schedule ‘Schedule’ tab Exists’ message. Schedule
when no Exists’
schedule message.
exists
View for View for 1. Click on Show Customer. Show
Customer Customer ‘Customer’ Customer.
navigation bar.
25 | P a g e
View 1. Click Display ‘No are Display ‘No

Customer ‘Customer’ exists’ are exists’
when no navigation bar
customer
exists
Create new Create new 1. Click Display success Display success
Item Item ‘Customer’ message in screen. message in
navigation bar screen.
2. Click on
‘Add Item’
specified
customer.
3. Fill all
information in
item details.
4. Click Add
button.
Details will 1. Fill single of Error Message will Error Message
not enter Item Details show. will show.
completely 2. Click on
Add button
Assigning Assigning the 1. Click on Item will Item will
the Item Item ‘Schedule’ tab successfully added successfully
2. Choose in the schedule. added in the
‘Assign Item’ Schedule is updated schedule.
on specified with on total Schedule is
schedule amount on the ship. updated with on
4. Click the total amount on
‘Assign’ to add the ship.
item to
schedule.
26 | P a g e
No Item 1. Select Show ‘No Item Show ‘No Item

exists ‘Schedule’ tab Exists’ Message. Exists’
2. Select Message.
‘Assign Item’
on specified
schedule
Ship are not 1. Click on Display the Display the

Available ‘Schedule’ message ‘Ship is message ‘Ship
navigation bar Not Available’ is Not
2. Choose Available’
‘Assign Item’
on specified
schedule
View Item View Item of 1. Click Display the item of Display the
of Ship Ship ‘Schedule’ ship. item of ship.
navigation bar
2. Click on
‘View Item’
specified
schedule.
No Item 1. Click on Display message. Display
shown in ‘Schedule’ ‘No Item are message. ‘No
Ship navigation bar assigned’. Item are
2. Choose the assigned’.
‘View Item’
specified
schedule.
27 | P a g e
5.2 Performance Testing

Performance testing is the testing of software application features and functionality. The
efficiency of the software application, such as its response time, reliability, use of resources
and scalability. Performance Testing's objective is not to discover bugs, but to eliminate
bottlenecks in performance. (Guru99, 2019)
Figure 21: Performance testing of the deployed system
28 | P a g e
6 Conclusion
While developing this Maersk Line Container Management System developer will get the
opportunity to gain a lot of knowledge about real time Microsoft Azure cloud hosting.
Developer has get the knowledge of about to deploying project in Microsoft Azure.
Furthermore, the developer will learned the configuration of the Microsoft Azure cloud
environment. This Maersk Line CMS system also hosting in Microsoft Azure cloud by
developer this is the real time experience of the developer.
This CMS is able to handle the booking process from searching shipping schedule to
confirming the bookings. This system has achieved all the requirements of the Maersk Line
Company. In the system database is managed by cloud to reduce latency for each region. Before
deploying in the cloud server developer has done so many test of the system.
Developing the system and deploying that project on the cloud was challenging. While
deploying in the cloud VM server it will helpful for future real organizational level.
29 | P a g e
7 References
archsd, 2018. Universal Accessibility – Best Practices and Guidelines. [Online]
Available at: https://www.archsd.gov.hk/archsd/html/ua/05-Chapter5.pdf
[Accessed 21 06 2019].
Azure, 2019. Azure Architecture Center. [Online]

Available at: https://docs.microsoft.com/en-us/azure/architecture/
[Accessed 19 6 2019].
DJIA, 2019. The Will Street Journal. [Online]

Available at: https://www.wsj.com/articles/maersk-line-buys-german-container-shipper-
hamburg-sud-1480590315
[Accessed 7 06 2019].
Guru99, 2019. Performance Testing Tutorial: What is, Types, Metrics & Example. [Online]
Available at: https://www.guru99.com/performance-testing.html
[Accessed 29 08 2019].
Software Testing Fundamental , 2018. Software Testing Fundamental. [Online]

Available at: In the unit testing, here will be tested a small part of the application like Admin
login page or vendor login page or user login page this page are separately tested if these
pages are separately executable this unit testing part is successful. All these
[Accessed 28 08 2019].
30 | P a g e
Appendix: I
Marking Scheme
Marking
Band Description
Band
Exceptional problem solving with supporting analysis and application

80-100 development skills with extraordinary originality and adoption of new
% tools, platforms, methods & technologies. Work may be considered for
further expansion.
75-79 % Outstanding problem solving and application development skills.

Characteristics of Student Achievement by Marking Band
Excellent knowledge base that supports analysis, evaluation, problem-

70-74 % solving and application development of discipline with considerable
originality
Good knowledge base that supports analysis, evaluation, problem-

65-69 %
solving and application development.
Satisfactory knowledge base that supports some analysis, evaluation and

60-64 %
problem-solving and application development.
Basic knowledge base with some omissions at the level of technology.

55-59 %
Restricted ability to discuss and/or or solve problems.
Limited knowledge base. Limited understanding of discipline. Difficulty

50-54 %
with problem solving and application development.
Little evidence of knowledge base. Little evidence of understanding of

40-49 % discipline. Significant difficulty with problem solving and application
development.
Inadequate knowledge base. Inadequate understanding of discipline.

30-39 %
Major difficulty with problem solving and application development.
31 | P a g e
No evidence of knowledge base; no evidence of understanding of

20-29 % discipline. Total inability of problem solving and application
development.
Awarded for: (i) non-submission; (ii) dishonesty; (iii) in situations where

0-19 % the student fails to address the assignment brief (e.g.: answers the wrong
question) and/or related learning outcomes
32 | P a g e
33 | P a g e
Appendix: III
Source Code
Web Source code: https://website1120190819112933.azurewebsites.net
34 | P a g e

CT071 3 5 3 Ddac

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CT071 3 5 3 Ddac

Încărcat de

Drepturi de autor:

Formate disponibile

e

HAND OUT DATE: 25 May 2019

HAND IN DATE: 18 August 2019

1. Submit your assignment at the administrative counter.

4. Cases of plagiarism will be penalized.

5. The assignment should be bound in an appropriate style (comb bound or stapled)

7. You must obtain 50% overall to pass this module.

1.1 Objective & Scope ...................................................................................................... 2

1.2 Requirement Specifications......................................................................................... 2

2. Project Plan ........................................................................................................................ 3

3.1 Architectural Diagrams ............................................................................................... 4

3.2 Design considerations ................................................................................................. 4

3.3 Modelling .................................................................................................................... 5

3.3.1 Use Case Diagram................................................................................................ 5

3.3.2 Use Case Description ........................................................................................... 5

3.3.3 Class Diagram ...................................................................................................... 8

4.1 Develop Web application ............................................................................................ 9

4.2 Website Publishing In Azure..................................................................................... 10

4.3 Screenshot ................................................................................................................. 19

5 Test Plan & Testing Discussion (Functional & Performance)......................................... 22

5.1 Unit Testing ............................................................................................................... 22

5.1.1 Testing Admin ................................................................................................... 23

5.1.2 Testing Agent ..................................................................................................... 25

5.2 Performance Testing ................................................................................................. 28

Marking Scheme .................................................................................................................. 31

1.1 Objective & Scope

1.2 Requirement Specifications

Figure 1: Gantt chart

Figure 2: The Cloud Architecture for Development Purpose

3.2 Design considerations

View customer View Item

Figure 3: Use Case Diagram

Use Case: Register as New Agent

Use Case: View Shipment Details

Use Case: View Schedule

Use Case: Book New Shipment

Use Case: Manage Shipping Schedule and creating new schedule.

3.3.3 Class Diagram

Figure 4: Class Diagram

Figure 5: Systems Files

4.2 Website Publishing In Azure

Figure 6: Create Resource Group

Figure 7: Successful to Create Resource Group

Figure 8: Creating Web app

Figure 9: Successful creating the Web App

Figure 10: Creating SQL Database

Figure 11: New server

Figure 12: Successful Creating SQL Database in Azure Cloud Server

Figure 13: Public

Figure 14: App Service

Figure 15: Deploy Web Site

Figure 16: Home page

Figure 17: Login Page

Figure 18: Schedule of Shipping

Figure 19: New Agent Registration

Figure 20: Create new shipping Schedule

5 Test Plan & Testing Discussion (Functional & Performance)

5.1 Unit Testing

5.1.1 Testing Admin

Create Create shipment 1. For the Display the Display the

5.1.2 Testing Agent

View 1. Click Display ‘No are Display ‘No