INDIVIDUAL ASSIGNMENT

TECHNOLOGY PARK MALASAYIA

CT071-3-3-DDAC
DESIGNING DEVELOPING APPLICATION ON CLOUD
NP3F1801IT
BINAYA SUBEDI (NP000026)

HAND OUT DATE: 26 JULY 2018

HAND IN DATE: 30 NOVEMBER 2018
WEIGHTAGE: 100%

INSTRUCTIONS TO CANDIDATES
1. Submit your assignment to the administration counter.
2. Students are advised to underpin their answers with the use of references
(sites using the Harvard Name System of Referencing)
3. Late submission 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 hardcopy 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.
 Acknowledgement
This project report is prepared for the partial fulfillment of the requirement for the
degree of BSc.IT in accordance to the rules and regulations prescribed by APU. So, I
would like to express my heartfelt gratitude to APU for providing me an opportunity to
apply my practical knowledge into the practical world enhances my knowledge.

My sincere gratitude goes to College for Professional Studies Lord Buddha Education
Foundation for providing me with learning environment and facilities without which
this project would have been impossible. I would especially like to thank all the faculty
members and program coordinators for their constant supervision and support.

I am also grateful to Mr. Sukant Kumar Sau, faculty member of DESIGNING

DEVELOPING APPLICATION ON CLOUD for his guidance and help to complete
this project.

Sincerely,

BINAYA SUBEDI (NP000026)

 Abstract
Container management system is developed for solving problems of Maersk Line
which have 374 offices in 116 countries. The main purpose of developing container
management system is to manage containers, reduces overall supply chain costs and
provide efficient way to manage logistics.

CMS was developed using C# language in visual studio 2017 following MVC (model,
view, container) pattern. SQL server 2014 was used as database management system.
Container management system have functionalities of search container and request for
shipping. Detailed functionalities are explained below. Before developing CMS
developer make some design and diagrams like, activity diagram, use case diagram,
class diagram, architecture diagram, sequence diagram, interface diagram and entity
relationship diagram. The detailed explanation are mention in this documentation.

Developer includes testing method, test cases and implementation of the system in this
documentation.
Table of Contents
1. Introduction ............................................................................................................ 1

1.1 Company Background ..................................................................................... 1

1.2 Problem context............................................................................................... 1

1.3 Requirement specification ............................................................................... 1

1.4 Aim .................................................................................................................. 2

1.5 Objectives ........................................................................................................ 2

1.6 Summary of functions of container management system ............................... 2

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

3. Design .................................................................................................................... 5

3.1 Architecture diagram ....................................................................................... 5

3.2 Use case diagram ............................................................................................. 6

3.3 Use case specification ..................................................................................... 8

3.4 Class diagram ................................................................................................ 11

3.5 Activity diagram ............................................................................................ 12

3.5.3 Activity Diagram of The System ........................................................... 12

3.6 Sequence diagram ......................................................................................... 13

3.6.1 Sequence diagram of the system ............................................................ 14

3.7 ER diagram .................................................................................................... 15

3.8 Data Dictionary ............................................................................................. 16

4. Implementation .................................................................................................... 19

4.1 Steps of publishing application to azure ....................................................... 19

4.2 Screenshot of the system ............................................................................... 21

5. Deployment .......................................................................................................... 24

5.1 Application Scaling with Justification .......................................................... 24

5.2 Performance Testing of Application ............................................................. 27

 5.3 Azure Platform as a Service (PaaS) .............................................................. 29

5.4 Database Management .................................................................................. 29

5.5 Testing on cloud application ......................................................................... 32

6. Testing..................................................................................................................... i

7. Conclusion .............................................................................................................. i

8. References ............................................................................................................... i

APPENDIX I: Marking Scheme ....................................................................................ii

List of Table
Table 1: Use case specification of login ........................................................................ 8
Table 2: use case specification of registration ............................................................... 8

Table 3: Use case specification for search ..................................................................... 9

Table 4: Use case specification for request for shipping ............................................... 9
Table 5: Use case specification of approve requested shipping .................................. 10
Table 6: Use case specification for notify.................................................................... 10
Table 7: Data dictionary of booking table: .................................................................. 16
Table 8: Data dictionary of containerinfo table ........................................................... 16
Table 9: Data dictionary of containerschedule table.................................................... 17
Table 10: Data dictionary of country table .................................................................. 17
Table 11: Data dictionary of registration table ............................................................ 18
Table 12: Data dictionary of tempbooking table ......................................................... 18

List of Figure
Figure 1: Architecture diagram of system ..................................................................... 6
Figure 2: Use case diagram ............................................................................................ 7
Figure 3 Class Diagram ............................................................................................... 11
Figure 4 Activity Diagram of the System .................................................................... 12
Figure 5 Sequence Diagram ......................................................................................... 14
Figure 6 ER Diagram of the system ............................................................................. 15
Figure 7 scaling up ....................................................................................................... 25
Figure 8 Scaling out ..................................................................................................... 26
Figure 9 Performance testing result ............................................................................. 27
Figure 10 Sql Created in Microsoft Azure ................................................................... 30
Figure 11 Deploy to SQL server .................................................................................. 30
Figure 12: Firewall Setting .......................................................................................... 31
1. Introduction
1.1 Company Background
Maersk Line is largest operating unit of Maersk Group, a Danish business conglomerate
and global container division. Company was established in 1928. Being world’s largest
container shipping company, it have 374 offices in 116 countries. It operates more than
600 vessels having capacity of 2.6 million TEU also gives employment approximately
7,000 sea farers and approximately 25,000 land-based people.

1.2 Problem context

Maersk Line already handling all the cargo it can manage by operating in 100 countries
and transporting goods around the globe. But when Maersk determined that the volume
of most of the goods it was shipping had grown to full capacity, the company decided
that cloud powered solutions would be a crucial part of rectifying the situation.

Maersk line decide to outsource every part of IT without impacting shipping. Since,
they increase organizational flexibility by consolidate all of its data centers and server
rooms operating worldwide onto a virtualized platform and Microsoft Azure was
already hosting some of Maersk’s IT environment. In March 2016 Maersk approached
Microsoft about expanding the scope of the relationship. But they cannot able to
manage the containers and reduces overall supply chain costs.

1.3 Requirement specification

 From import, export and transshipment processing to gate operations.

 To be able to scale the solution to meet the needs of demands during peak seasons.
 Improves profitability, cuts costs, increases productivity, eradicates errors and
optimizes resources to future-proof your cargo handling business for high
performance.
 Assurance & reliability through Failover Management.
 Manage your entire booking process from schedule search to booking confirmation.

1
1.4 Aim

Designing and developing a container management system (CMS) that can manage the
containers, reduces overall supply chain costs and provide efficient way to manage
logistics.

1.5 Objectives

The main objective of this assignment are:

 Develop web based application

 User can register, login, view container list, request for shipping, acknowledge of
approval of shipping request and view container status.
 Approval port manager can register, login, receive shipping information and update
arrives container status.
 Department manager can approve requested shipping, notify to arrival port and update
shipping container status

1.6 Summary of functions of container management system

Container management system is web based application having three actors and they
are: user, approval port manager, department manager. All actors need to login first.
After login, they are enter in their page according to role. User (customer) fill the form
for requesting for shipping. Departure port receive the shipping request, if request is
approve then notify to arrival port and user otherwise user need to resubmit the form.
After approving request, departure port update shipping container status and arrival port
will notify that. After arrived container arrival port update arrived status and notify to
departure port and customer.

2
 2. Project Plan
Project plan

WBS Task Name Duration Start Finish Status

1 Introduction 2 days 1st august 2nd august Complete

2018 2018

1.1 Background 3 hr. 1st august 2018 1st august 2018 Complete

1.2 Problem 3hr. 1st august 2018 1st august 2018 Complete
Context
5th 5th
1.3 Requirement 2 hr. august 2018 august 2018 Complete
specification
5th 5th
1.4 Aim 40 min august 2018 august 2018 Complete
5th 5th
1.5 Objective 3 hr. august 2018 august 2018 Complete
5th 5th
1.6 Summary of 30 min august 2018 august 2018 Complete
functions
7th 8th
2 Project Plan 3 days august 2018 august 2018 Complete

3 Design 30 days 9th august 2018 9th September Complete

2018
10th 12th
3.1 Architecture 3 days august august Complete
design 2018 2018
13th 19th
3.2 Use case 6 days august august Complete
diagram 2018 2018
20th 23th
3.3 Use case 3 days august august Complete
specification 2018 2018
24th
3.4 Class diagram 6days august 29thaugust Complete
2018 2018

3.5 Activity 4 days 30 august 2018 3rd sep 2018 Complete

diagram

3
 4th 11th
3.6 Sequence 7 days sep 2018 September Complete
diagram 2018
12th 15th
4 Implementation 5 days November November Complete
2018 2018
16th
5 Testing 5 days November 21st November Complete
2018 2018

6 Conclusion 1 day 22nd November 22nd November Complete

2018 2018

4
3. Design
3.1 Architecture diagram
Architectural diagram is a selective abstraction of a concept or an idea translated into
the form of drawing. Furthermore, it provides insight into the way of thinking in and
about architecture, thus creating a balance between the visual and the conceptual. The
subject of the research presented in this paper is diagrams as a specific form of
architectural representation and their implementation in the process of exploring and
designing a city.

Through the shown analysis of different diagramming practices among architects

(Kevin Lynch, Christopher Alexander, Bernard Tschumi, Rem Koolhaas, CHORA,
OMA), one can witness a wide variety of forms of diagrams, their functions and
applications. In the contemporary world of constantly shifting relationships, designer
needs a tool to understand these changes where it seems that nothing is fixed or
permanent. Hitherto, this paper indicates that diagrams can be of great use to urban
designers in clarifying the structure of a city, showing individual paths, complex
sections and collective shared maps. The choice of diagrammatic paradigm shapes and
filters the infinitive richness of a city, as a site for design intention and action. Each
diagram of a city is therefore a representational schema of the designer's own
conception of the world, a microcosm of their discipline.

From the aspect of city planning, diagram can serve both as an analytical tool and as a
generative expression of design ideas.

Analytical diagrams play an organizational role in the design, through the explanation
the genesis of a city or a place, by the depiction of its contemporary conditions or
relationships, and by projecting the intended future of the site through extrapolation of
the design intervention. Diagrams are also generative tools - agents of investigation and
revelation, forming the base on which the ideas may evolve.

(PDF) Architectural Diagram of a City.Talking about working mechanism of system,

main system have reference of all project i.e. business, common and repository,
business have reference of common and repository, Repository have reference of
common. In this way all of the projects were inter linked.

5
Suppose when user search for view container list, view pass the searched item to model,
controller receives that information through model and common receives from
controller. Now, controller call the function from business class, after checking
information availability in common, business pass those information to repository by
calling the function. Here, repository function executes the query from database that
checks the provided information is stored in database or not if stored then repository
passes to business, business to controller, controller to model and common then from
model information passes to browser and then user can able to view container list of
searched container. Otherwise got error message. (Dulić, 2016)

Figure 1: Architecture diagram of system

3.2 Use case diagram

The use case diagram models the user’s expectation for using the system. The people
and system that interact with the target system are called actors. The features of the
system that the actors use is called use cases. (Pender, 2003)

The main purpose of making use case diagram is to

 Identify client expectation toward the system

 Identify the features of system
 Identify shared behavior among the features of system
 Provide a simple & easiest way for client to understand their requirement.

6
Figure 2: Use case diagram

7
3.3 Use case specification

Table 1: Use case specification of login

Use Case Login

Brief Description All the three character can login into the system

Actors User, Arrival Port, Department Manager

Priority High

a. select sign in option

Main Flow b. Enter user name and password and
select role
c. Click on login button
Post Condition Show home page according to role

Table 2: use case specification of registration

Use Case Registration

Brief Description All people can register.

Actors User, Arrival Port, Department Manager

Priority High

a. Select registration option

Main Flow b. fill the form
b. Click on submit button

Post Condition Your information was registered successfully.

8
Table 3: Use case specification for search

Use Case Search

Brief Description User are able to search containers.

Actors User

Priority High

a. Enter container name

Main Flow b. Click on search button

Post Condition Show the list of related container

Table 4: Use case specification for request for shipping

Use Case Request for shipping

Brief Description Users request for shipping

Actors User

Priority High

a. Select shipping request

Main Flow b. Fill the form
c. Click confirm button

Post Condition Request was successfully sent

9
Table 5: Use case specification of approve requested shipping

Use Case Approve requested shipping

Brief Description Only departure port are allow to approve requested

shipping

Actors Departure port

Priority High

a. Select requested shipping

Main Flow b. Click on approve button

Post Condition Currently you approved the shipping request

Table 6: Use case specification for notify

Use Case Notify

Brief Description Only departure port are allow to notify (arrival port and
user) about approved request.

Actors Departure port

Priority High

a. Click on notify
Main Flow b. Write something on form
c. Click on send button

Post Condition Show home page according to role

10
3.4 Class diagram
AddLocationModel
DbResult AddLocationCommon 1..* LocationFrom_Name:string
-_errorCode:string LocationFromID:string
LocationFrom_Name:string
-_id:string LocationTo_Name:string
LocationFromID:string
-_msg:string LocationToID:string
LocationTo_Name:string
ErrorCode LocationToID:string
Extra
Extra2
Id 1..1
Message
+SetError(errorCode, msg, id)
AddLocationController
1..1 1..1
1..* +AddLocationList():ActionResult
+Delete(id):ActionResult
RepoDAO +DetailByID(id):ActionResult
AddLocationRepo +Edit(id):ActionResult
-_connection: sqlconnection +Index():ActionResult
-CloseConnection():void dao +save(model):ActionResult
+ExecuteDataRow(sql):DataRow
+AddLocationListRepo():list
+ExecuteDataSet(sql):DataSet 1..*
+DetailByID(id):common
+ExecuteDataTable(sql):DataTable
+Delete(id):DbResult 1..1
+FilterQuote(strVal):string
+Save(common):DbResult
+FilterString(strVal):string
-GetConnectionString():string 0..1
+GetSingleResult(sql):string AddLocationBiz
-Init():void
-OpenConnection():void 1..1 repo
+AddLocationList():list AddLocationView
+ParseDbResult(dt):DbResult
+ParseDbResult(sql):DbResult +Delete(id):DbResult
+DetailByID(id):common -memberName
+ParseDictionary(sql):string
+Save(common):DbResult -memberName
+RemoveDecimal(amt):string

Figure 3 Class Diagram

11
3.5 Activity diagram

Activity diagram model’s logic-any logic- from workflow to use cases to methods. The
main purpose of making use case diagram is to

 Represent the logic required to implement the system behavior.

 Represent logic at any level the design needs, from the system workflow to
individual method implementations.
 Are simple enough to learn quickly. (Pender, 2003)

3.5.3 Activity Diagram of The System

Login Registration

Fill the form

Enter username and
password Incorrect

Incorrect Validation check

Check if username
and password are
correct

Correct

Correct
Register successfully

Enter page as role

User Departure port Arrival Port

Request for View container Approve requested Notify Update shipping Receive approved Update arrived
Search container status shipping request
shipping status shipping container status

Figure 4 Activity Diagram of the System

12
Above mention figure is activity diagram of the system in this system user have the
option for the registration and have to fill up the all the mandatory field in the form.
Then it checks the form validation if there is incorrect information then again user have
to fill the form properly. If the information is correct then user will be successfully
registered. After the registration user have to login into the system during the login if
user have entered the wrong keyword then system will show the incorrect message. If
the username and password is correct user will be successfully login into the system.
After successfully login into the system there are different role in the system. In user
where user can able to request for shipping view status and view container status. Then
departure port can able to approved request shipping, notify and update shipping
container status. Other hand arrival port has the permission to received approved
shipping request and update arrival status.

3.6 Sequence diagram

Sequence diagram is a time-oriented view of the interaction between objects to

accomplish a behavioral goal of the system. An interaction may be modeled at any level
of abstraction within the system design, from sub-system interactions to instance-level
interaction for a single operation or activity. (Pender, 2003)

The focus of the diagram is on identifying interactions between objects over time. The
major benefit of the diagram is that it helps identify the message exchange between
objects. Exchanging message requires a sender & receiver. A receiver must have an
interface to receive message. Hence, if a message must be sent from object to another,
the receiver must define an interface that conforms to the message. (Pender, 2003)

13
3.6.1 Sequence diagram of the system

Admin :View :Model :Controller :Business Common :Repository DbResult

1. Fill fields in the form

1.2 Give information to
field name
1.5 check the field name
1.3 Pass data with information
1.4 Call the function

1.6 Available
1.7 call the function
1.8 Check the field name
alt with information

if errorcode=0
1.9 Available 1.10 Execute query

1.13 Pass Result 1.12 Pass Result 1.11 Result

1.14 Pass Successful message
1.16 Acknowledge admin
if errorcode !=0

1.15 Pass error message

Figure 5 Sequence Diagram

This is sequence diagram of manage location module. First, admin fill the required form
shown from Index page. Then, Index create the object of Model and send received data
to model. Model pass the information to controller, controller already created object for
model, business and common so that information pass to common at same time function
in business class activates and that function receives the information. Business creates
object of repository and function in repository class activates and get the information.

Repository function compare information with database (or check validation) and pass
result to business. Business pass message to controller, controller checks the result and
if error code is 0 then information is added/ updated/ deleted and successful message to
index then admin can acknowledge about his action and if error code is not 0 then admin
get error message through index page.

14
3.7ER diagram

Figure 6 ER Diagram of the system

15
3.8 Data Dictionary

Booking table

Table 7: Data dictionary of booking table:

SN Attribute Name Data type Allow Primary Foreign key

Null key

1 BookingID Int No Yes No

2 ContainerScheduleID Int Yes No Yes

3 RegistrationID Int Yes No Yes

4 Quantity Nvarchar(50) Yes No No

5 Weight Nvarchar(50) Yes No No

6 OrderDate Datetime Yes No No

7 Status Nvarchar(50) Yes No No

Container Information table

Table 8: Data dictionary of containerinfo table

SN Attribute Name Data type Allow Primary Foreign key

Null key

1 ContainerInfoID Int No yes No

2 ContainerCode Nvarchar(100) Yes No No

3 MaxWeight Nvarchar(50) yes No No

16
Container Schedule table

Table 9: Data dictionary of containerschedule table

SN Attribute Name Data type Allow Primary Foreign key

Null key

1 ContainerScheduleID Int No Yes No

2 ContainerInfoID Int Yes No Yes

3 Origin Int Yes No Yes

4 Destination Int Yes No Yes

5 ContainerNumber Nvarchar(50) Yes No No

6 DepartureDate Date Yes No No

7 Status Nvarchar(50) Yes No No

Country table

Table 10: Data dictionary of country table

SN Attribute Name Data type Allow Primary Foreign key

Null key

1 CountryID Int No Yes No

2 CountryName Nvarchar(50) Yes No No

17
Registration table

Table 11: Data dictionary of registration table

SN Attribute Name Data type Allow Primary Foreign key

Null key

1 RegistrationID Int No Yes No

2 Name Nvarchar(100) Yes No No

3 Address Nvarchar(100) Yes No No

4 Email Nvarchar(100) Yes No No

5 ContactNo Nvarchar(15) Yes No No

6 Password Nvarchar(50) Yes No No

7 Role Nvarchar(50) Yes No No

TempBooking table

Table 12: Data dictionary of tempbooking table

SN Attribute Name Data type Allow Primary Foreign key

Null key

1 TempBookingID Int No Yes No

2 BookingID Int Yes No Yes

3 Status Nvarchar(50) Yes No No

18
4. Implementation
4.1 Steps of publishing application to azure

1. Activate Azure account

2. Create or open an Azure cloud service project in Visual Studio.

19
3. Click on start button. Then the page displays & fill the information.

4. Click create button

20
4.2 Screenshot of the system

Registration

As shown in the figure, it is a registration page where the client has to register before
logging in onto the system.

Login

As shown in the figure it is a login is system where client have to enter the email and
password from accessing the booking container system. If the client has access of login
the client have to register first.

21
User Home Page

The above figure shows the booking container page which the customer must catalogue
and after login the client will be inspecting this page. The user will book the container
by choosing the client obligatory country and its zone and click submit for the available
container for its zone. The client will select the ampule and choose the required
container / arrival date and book the container.

View Status Page

As appeared in the figure, it demonstrates the booking compartment status. In the wake
of booking the holder the customer will be divert the booking compartment status for
its required booking status check. After convey of compartment the customer will tap
the conveyed catch and tap the drop for cancelation before the on-travel status.

22
Admin home page

Status after approve

Status after receive

23
5. Deployment

5.1 Application Scaling with Justification

Scalability is a desirable property of s system which indicates its ability to either handle
growing amounts of work in a graceful manner, or to be readily enlarged as demands
increase. (Engates, 2008) it is also say that it is the process of monitoring the
performance of the web application and make a decision for additional and removal of
resources. In today’s data centric world, web applications have to be ready for any
sudden load of data and usage, and for that scalability apparently becomes a must need
for such new generation of web applications. Google.com is a scalable search engine.
It can handle any number of users and any amounts of content. It scales easily to more
content that is being added on the internet daily and to the large users that use it daily
while maintaining a fraction of second response times throughout the day. (Atlogys,
2018)

There are different type of Application

1. Scaling up
2. Scaling out

24
1. Scaling up
The obvious option in many cases is to address a scalability problem with better, faster,
more capable hardware. If we can’t load that giant spreadsheet model on a computer
with 512MB of RAM, we install 2GB and give it another try. If it is still too slow, we
can use a machine with a faster processor or faster hard disk. This approach can also be
applied to web servers, database servers, and other parts of your system. Got an
architecture problem? Get some better hardware. This approach is variously called
“scaling up” or “vertical scaling” – since we are addressing the problem by substituting
a more capable system (usually a single server), but one that is still logically equivalent.

Figure 7 scaling up

25
Scaling Out

A scale out operation is the equivalent of creating multiple copies of your web site and
adding a load balancer to distribute the demand between them. When you scale out a
web site in Windows Azure Web Sites there is no need to configure load balancing
separately since this is already provided by the platform. (Tardif, 2013)

Figure 8 Scaling out

Justification
Application scaling is important to enhance and maintain the performance of the web
application. A web app which is not scalable may also not support more development
and/or improvisations. Non scalable systems often need to be re-hauled and re-written
to support future development.

26
 5.2 Performance Testing of Application

The goal of performance testing is to appraise any user experience in realistic scenarios
on your target application. It will allow you to assess machine and infrastructure
capability. In the proposed system there were load of forty users for performance
testing. (Agileload, n.d.)

Figure 9 Performance testing result

27
After the performance testing which shows that the proposed web application has
50.03% success rate and 49.97%of failed requests.

28
5.3 Azure Platform as a Service (PaaS)

Platform as a service (PaaS) is a deployment and development environment within the

cloud that delivers simple cloud-based apps to complex, cloud-enabled applications.
PaaS is designed to support the complete web application lifecycle of building, testing,
deploying, managing, and updating.

PaaS includes a complete infrastructure of servers, storages, networking, and

middleware development tools like business intelligence services (BI), database
management systems, etc. A complete platform is offered in PaaS in which the client
can host their applications without the need to worry about the maintenance of the
servers and its operating systems. However, the user of the PaaS service should look
after the implementation of the developed application to decide whether to scale it up
or down depending on the traffic that the application receives.

5.4 Database Management

Configure SQL Server

29
Figure 10 Sql Created in Microsoft Azure

Deploy to Microsoft Azure

Figure 11 Deploy to SQL server

30
Firewall setting

Figure 12: Firewall Setting

31
5.5 Testing on cloud application

Test case for cloud testing:

Test scenario Test cases

 Failure due to one user action on cloud should not affect other
users performance
 Manual or automatic scaling should not cause any disruption
 On all types of devices the performance of the application
should remain same

Performance  Overbooking at supplier end should not hamper the

Testing application performance (Anon., n.d.)

 Only authorized customer should get access to data

 Data must be encrypted well
 Data must be deleted completely if it is not in use by client
 Data should be accessible with insufficient encryption
Security Testing  Administration on suppliers end should not access the
customers data
 Check for various security settings like firewall, VPN, Anti-
virus etc. (Anon., n.d.)

 Test protocol responsible for cloud connectivity

 Check for data integrity while transferring data
Network Testing
 Check for proper network connectivity
 Check if packets are being dropped by firewall. (Anon., n.d.)

 Valid input should give the expected results

 Service should integrate properly with other applications
 System should display customer account type when
successfully login to the cloud

Functional testing  When customer chose to switch to other service the running
service should close automatically. (Anon., n.d.)

32
6. Testing
Testing is done not only for checking if system runs properly or not and it shows any
errors, also to check if the output is matched with expectations or not. Test driven
development is a programming practice that instruct developer to write new code only
if executed code have some error & cannot meet with expectations. The main purpose
of TDD is to make code clearer, simple and bug-free.

For developing this system developer first add the test case (which portion need to be
test), after that execute the test if test case gives expected result then add another test
case. But if test case cannot give expected result then developer make changes on code
and again execute this process continues until developer get expected result.

33
7. Conclusion
In the conclusion researcher gets the opportunity to learn about how to publish a Web
application on Microsoft Azure. During the development of the system it was hard to
learn and develop the system and publish on Microsoft Azure. But at last researcher
come up with the system after many research through online and book.

Limitation

 It is only web based application

 Status can be changed by admin
 User cannot able to tracking container

Future Enhancement

 Will be android application

 Status can be changed automatically
 Implement the function i.e. tracking container

34
8. References
Agileload, n.d. Agileload. [Online]
Available at: http://www.agileload.com/performance-testing/application-performance-
testing
Anon., n.d. cloud testing tutorial. [Online]
Available at: https://www.guru99.com/cloud-testing-tutorial-with-saas-testing-
primer.html
[Accessed 10 october 2018].
Atlogys, 2018. Atlogys. [Online]
Available at: http://www.atlogys.com/scaling-web-applications
Dulić, O., 2016. Researchgate.net. [Online]
Available at:
https://www.researchgate.net/publication/301342950_Architectural_Diagram_of_a_C
ity
Engates, J., 2008. Seven stages of scaling web apps, San fransisco: s.n.
Microsoft, 2018. Publish a Web app to Azure App Service using Visual Studio.
[Online]
Available at: https://docs.microsoft.com/en-us/visualstudio/deployment/quickstart-
deploy-to-azure?view=vs-2017
[Accessed 10 october 2018].
Pender, T., 2003. Activity diagram. In: uml 2. new delhi: wiley publishing, pp. 60-62.
Pender, T., 2003. sequence diagram. In: UML 2. new delhi: wiley publishing, pp. 275-
295.
Pender, T., 2003. Sequence diagram. In: uml 2. new delhi: wiley publishing, pp. 61-
62.
Pender, T., 2003. Use case diagram. In: UML 2. new delhi: wiley publishing, pp. 58-
65.
Tardif, B., 2013. Microsoft. [Online]
Available at: https://azure.microsoft.com/en-us/blog/scaling-up-and-scaling-out-in-
windows-azure-web-sites/

i
APPENDIX I: Marking Scheme
Mark Allocated Score
No Criteria

Documentation Binaya Subedi

(NP000026)

1. Introduction 15

2. Project Plan 15

3. Design & Solution Architecture 60

4. Conclusion 10

Total (Documentation) 100

Implementation

5. Publishing an Application to Azure 10

6. Application Scaling with Justification 20

7. Testing Cloud Applications 25

8. Investigate & Analyze Application 20

(Plan, collect, and interpret diagnostics
and instrumentation data)

9. Implementation & Discussion of 25

Managed Databases (PaaS)

Total (Implementation) 100

ii