Web Content Management System, Migration and Maintenance Services for ECDC Web Portal - Reference H

Web Content Management System, Migration and
Maintenance Services for ECDC Web Portal

Current System Description – Reference H
March 2015

Page | 1

Web Content Management System, Migration and Maintenance Services for ECDC Web Portal - Reference H

Table of Contents
1.

Introduction ...............................................................................................................4
1.1.
1.2.

2.

Purpose and Scope ...................................................................................................................... 4
How the SAD Is Organized ........................................................................................................... 5

Architecture Background .......................................................................................... 22
2.1. Problem Background ................................................................................................................. 22
2.1.1. System Overview ................................................................................................................ 22
2.1.2. Goals and Context .............................................................................................................. 23
2.1.3. Significant Driving Requirements ....................................................................................... 23
2.2. Solution Background .................................................................................................................. 24
2.2.1. Architectural Approaches ................................................................................................... 24
2.2.2. Analysis Results................................................................................................................... 25
2.2.3. Requirements Coverage ..................................................................................................... 25
2.2.4. Summary of Background Changes Reflected in Current Version ....................................... 28

3.

Views ....................................................................................................................... 28
3.1. Logical View ............................................................................................................................... 29
3.1.1. View Description................................................................................................................. 29
3.1.2. View Packet Overview ........................................................................................................ 29
3.1.3. Architecture Background .................................................................................................... 30
3.1.4. View Packet: Entity relations diagram ................................................................................ 30
3.1.5. View Packet: Sequence diagram......................................................................................... 30
3.2. Development / Implementation View ....................................................................................... 31
3.2.1. View Description................................................................................................................. 31
3.2.2. View Packet Overview ........................................................................................................ 31
3.2.3. Architecture Background .................................................................................................... 32
3.2.4. View Packet: Component diagram ..................................................................................... 34
3.2.5. View Packet: Package diagram ........................................................................................... 34
3.3. Process View .............................................................................................................................. 37
3.3.1. View Description................................................................................................................. 37
3.3.2. View Packet Overview ........................................................................................................ 37
3.3.3. Architecture Background .................................................................................................... 38
3.3.4. View Packet: Activity diagram ............................................................................................ 38
3.4. Physical / Deployment View ...................................................................................................... 38
3.4.1. View Description................................................................................................................. 38
3.4.2. View Packet Overview ........................................................................................................ 38
3.5. Scenarios / Use-cases View........................................................................................................ 39
3.5.1. View Description................................................................................................................. 39
3.5.2. View Packet Overview ........................................................................................................ 39
3.5.3. Architecture Background .................................................................................................... 39
3.5.4. View Packet: Use-case diagram .......................................................................................... 39

4.

Relations Among Views ............................................................................................ 54

5.

Referenced Materials ............................................................................................... 55

6.

Appendices............................................................................................................... 56
6.1.

Appendix: Glossary and Acronym List ....................................................................................... 56

Page | 2

Web Content Management System, Migration and Maintenance Services for ECDC Web Portal - Reference H

List of Figures
FIGURE 1: WEB PORTAL 1.1. .................................................................................................................................... 23
FIGURE 2: ECDC VISUAL IDENTITY ............................................................................................................................ 26
FIGURE 3: LEFT HAND NAVIGATION ......................................................................................................................... 27
FIGURE 4: SOCIAL NETWORK LINKS ......................................................................................................................... 28
FIGURE 5: SEQUENCE DIAGRAM FOR THE CREATION AND PUBLICATION OF A NEW PAGE TO THE WEB PORTAL . 31
FIGURE 6: COMPONENT DIAGRAM .......................................................................................................................... 34
FIGURE 7: ADVISORY FORUM CRM DATA ACCESS ................................................................................................... 35
FIGURE 8: CRM COMPETENT BODIES DATA ACCESS ................................................................................................ 35
FIGURE 9: MANAGEMENT BOARD CRM DATA ACCESS ............................................................................................ 36
FIGURE 10: CONTENT TYPE HUB .............................................................................................................................. 37
FIGURE 11: ACTIVITY DIAGRAM FOR THE PAGE APPROVAL .................................................................................... 38
FIGURE 12: ADVISORY AND MANAGEMENT WEB PART USE CASE DIAGRAM ......................................................... 40
FIGURE 13: ECDC WEB CONTENT BOX WEB PART USE CASE DIAGRAM .................................................................. 41
FIGURE 14: COUNTRY INFORMATION SMALL MAP WEB PART USE CASE DIAGRAM .............................................. 42
FIGURE 15: CUSTOM FORM USE CASE DIAGRAM .................................................................................................... 43
FIGURE 16: ECDC CONTENT QUERY WEB PART USE CASE DIAGRAM ...................................................................... 44
FIGURE 17:ECDC TV WEB PART USE CASE DIAGRAM ............................................................................................... 45
FIGURE 18: EVENTS WEB PART USE CASE DIAGRAM ............................................................................................... 46
FIGURE 19: RELATED PAGES WEB PART USE CASE DIAGRAM.................................................................................. 47
FIGURE 20:FILTER PICTURE LIBRARY WEB PART USE CASE DIAGRAM ..................................................................... 48
FIGURE 21: HEALTH TOPICS WEB PART USE CASE DIAGRAM .................................................................................. 49
FIGURE 22: IMAGE ROTATOR WEB PART USE CASE DIAGRAM ................................................................................ 50
FIGURE 23: RELATED NEWS WEB PART USE CASE DIAGRAM .................................................................................. 51
FIGURE 24: OPEN DOCUMENT WEB PART USE CASE DIAGRAM .............................................................................. 52
FIGURE 25: PICTURE VIEWER WITH DROPDOWN WEB PART USE CASE DIAGRAM ................................................. 53
FIGURE 26: PHOTO GALLERY SMALL PICTURE WEB PART USE CASE DIAGRAM ...................................................... 54

Page | 3

Web Content Management System, Migration and Maintenance Services for ECDC Web Portal - Reference H

1.

Introduction

Sub-sections of Section 1 include the following.

Section 1.1 (“Purpose and Scope”) explains the purpose and scope of the SAD, and indicates what
information is and is not included. This tells you if the information you’re seeking is likely to be in this
document.

Section 1.2 (“How the SAD Is Organized”) explains the information that is found in each section of the
SAD. This tells you what section(s) in this SAD are most likely to contain the information you seek.

1.1. Purpose and Scope
This SAD specifies the software architecture for the Web Portal of ECDC. The Web Portal is built on
Microsoft SharePoint platform. Since SharePoint applications heavily depend on the underlying
SharePoint farm and its configuration, corresponding information will also be included where it is
relevant. All information regarding the software architecture may be found in this document, although
much information is incorporated by reference to other documents.
What is software architecture? The software architecture for a system* is the structure or structures of
that system, which comprise software elements, the externally-visible properties of those elements, and
the relationships among them [Bass 2003]. "Externally visible” properties refers to those assumptions
other elements can make of an element, such as its provided services, performance characteristics, fault
handling, shared resource usage, and so on. This definition provides the basic litmus test for what
information is included in this SAD, and what information is relegated to downstream documentation.
Elements and relationships. The software architecture first and foremost embodies information about
how the elements relate to each other. This means that architecture specifically omits certain
information about elements that does not pertain to their interaction. Thus, a software architecture is an
abstraction of a system that suppresses details of elements that do not affect how they use, are used by,
relate to, or interact with other elements. Elements interact with each other by means of interfaces that
partition details about an element into public and private parts. Software architecture is concerned with
the public side of this division, and that will be documented in this SAD accordingly. On the other
hand, private details of elements—details having to do solely with internal implementation—are not
architectural and will not be documented in a SAD.
Multiple structures. The definition of software architecture makes it clear that systems can and do
comprise more than one structure and that no one structure holds the irrefutable claim to being the
architecture. The neurologist, the orthopedist, the hematologist, and the dermatologist all take a different
perspective on the structure of a human body. Ophthalmologists, cardiologists, and podiatrists
concentrate on subsystems. And the kinesiologist and psychiatrist are concerned with different aspects
of the entire arrangement’s behavior. Although these perspectives are pictured differently and have very
different properties, all are inherently related; together they describe the architecture of the human body.
So it is with software. Modern systems are more than complex enough to make it difficult to grasp them
all at once. Instead, we restrict our attention at any one moment to one (or a small number) of the
software system’s structures. To communicate meaningfully about an architecture, we must make clear
which structure or structures we are discussing at the moment—which view we are taking of the
*

Here, a system may refer to a system of systems.
Page | 4

Web Content Management System, Migration and Maintenance Services for ECDC Web Portal - Reference H

architecture. Thus, this SAD follows the principle that documenting a software architecture is a matter
of documenting the relevant views and then documenting information that applies to more than one
view.
None of these structures alone is the architecture, although they all convey architectural information.
The architecture consists of these structures as well as many others. This example shows that since
architecture can comprise more than one kind of structure, there is more than one kind of element (e.g.,
implementation unit and processes), more than one kind of interaction among elements (e.g.,
subdivision and synchronization), and even more than one context (e.g., development time versus
runtime). By intention, the definition does not specify what the architectural elements and relationships
are. Is a software element an object? A process? A library? A database? A commercial product? It can be
any of these things and more.
These structures will be represented in the views of the software architecture that are provided in
Section 3.
Behavior. Although software architecture tends to focus on structural information, behavior of each
element is part of the software architecture insofar as that behavior can be observed or discerned from
the point of view of another element. This behavior is what allows elements to interact with each other,
which is clearly part of the software architecture and will be documented in the SAD as such. Behavior
is documented in the element catalog of each view.

1.2. How the SAD Is Organized
This SAD is organized into the following sections:

Section 1 (“Introduction”) provides information about this document and its intended
audience. It provides the roadmap and document overview. Every reader who wishes to find
information relevant to the software architecture described in this document should begin by
reading Section 1, which describes how the document is organized, which stakeholder viewpoints
are represented, how stakeholders are expected to use it, and where information may be found.
Section 1 also provides information about the views that are used by this SAD to communicate the
software architecture.

Section 2 (“Error! Not a valid bookmark self-reference.”) explains why the architecture is
what it is. It provides a system overview, establishing the context and goals for the development.
It describes the background and rationale for the software architecture. It explains the constraints
and influences that led to the current architecture, and it describes the major architectural
approaches that have been utilized in the architecture. It includes information about evaluation or
validation performed on the architecture to provide assurance it meets its goals.

Section 3 (Views”) and Section 0 (“The utilization of the web parts is one of the most important
and used in Web Portal. Below are the use cases for a selection of web parts:

Page | 5

Web Content Management System.Reference H Figure 12: Advisory and Management web part use case diagram Page | 6 . Migration and Maintenance Services for ECDC Web Portal .

Reference H Figure 13: ECDC Web Content Box web part use case diagram Page | 7 .Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .

Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 14: Country Information small map web part use case diagram Page | 8 .

Reference H Figure 15: Custom Form use case diagram Page | 9 . Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.

Reference H Figure 16: ECDC Content Query web part use case diagram Page | 10 . Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.

Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 17:ECDC TV web part use case diagram Page | 11 .Web Content Management System.

Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 18: Events web part use case diagram Page | 12 .

Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 19: Related pages web part use case diagram Page | 13 .Web Content Management System.

Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 20:Filter Picture Library web part use case diagram Page | 14 .Web Content Management System.

Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 21: Health Topics web part use case diagram Page | 15 .Web Content Management System.

Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 22: Image Rotator web part use case diagram Page | 16 .Web Content Management System.

Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.Reference H Figure 23: Related News web part use case diagram Page | 17 .

Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 24: Open Document web part use case diagram Page | 18 .

Reference H Figure 25: Picture Viewer with Dropdown web part use case diagram Page | 19 .Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .

Views specify elements of software and the relationships between them.Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 26: Photo Gallery Small picture web part use case diagram  Relations Among Views”) specify the software architecture.1). A view corresponds to a viewpoint. and is a representation of one or more structures present in the software (see Section 1.  Sections 0 (“[Kruchten 1995] Page | 20 .

Page | 21 . Section 5 provides look-up information for documents that are cited elsewhere in this SAD. which is an index of architectural elements and relations telling where each one is defined and used in this SAD. The section also includes a glossary and acronym list.Web Content Management System.Reference H  Referenced Materials”) and Appendix (“Appendix: Glossary and Acronym List”) provide reference information for the reader. Section 6.1 is a directory. Migration and Maintenance Services for ECDC Web Portal .

Web Content Management System. The current version 1.1.1. Page | 22 . System Overview The Web portal is the public ECDC web site used to emit information regarding ECDC work and programmes. The Web Portal 1.1 was out on the 13th of September of 2013 and is powered by SharePoint 2010. Architecture Background 2.Reference H 2.0 was powered by SharePoint 2007 and went live at September 2009.1. Migration and Maintenance Services for ECDC Web Portal . Problem Background 2.

Significant Driving Requirements The most Significant Driving Requirements for the Web Portal are: Page | 23 . Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 1: Web Portal 1.1. 2. 2.Web Content Management System.2. various health topics.1. Goals and Context The general goal/objective of the Web Portal it to provide an overview of the mission and activities of ECDC.3.1. More specifically it offers detailed information about the organization. its activities. list of its publications and related media.

1/Specific ations/BasicNavigation_Portal1. making this a natural choice also for the Web Portal. Timer Jobs: They are periodically executed tasks inside SharePoint Server. Timely notification of users: Social bookmarking. Content types can be defined for any item type. Pdf documents. CSS Styles: Web Portal common branding comes in the form of CSS stylesheets.  (Web server) Internet Information Services (IIS).  (Development environment) Visual Studio 2010 Team System. All ECDC related material has some specific color and style guidelines.  (Email server) Microsoft Exchange.  (Server operating system) Windows Server technologies. list items.europa. Architectural Approaches ECDC as an organization is using Microsoft technologies. and folders. 2. media files. More specifically Microsoft SharePoint is the application platform that Web Portal is built on.Reference H 1. text files. Document libraries: They are used for storing various types of files like Word documents.0. In light of this the system is based on / using:  (Development platform) The . Solution Background 2. Left hand navigation in all content pages (http://ecdcintranet. Content editors should be able to modify content and add functionality to pages 2. Various features of SharePoint are utilized inside the web portal. Page | 24 . ESCAIDE. Migration and Maintenance Services for ECDC Web Portal .2. 5.  (Deployment): SharePoint solution packages and Windows PowerShell scripts MS SharePoint version 2010 is the version that currently powers the big majority of content 1.  (Database software) MS SQL Server technologies utilized by SharePoint Farm.ecdcnet.1_v1. They provide a task execution environment. Content types: A content type is a group of reusable settings that describe the shared attributes and behaviors for a specific kind of content.xlsx). EAAD migration.5 and the C# programming language.1. More specifically: Managed metadata service: This is a SharePoint feature that facilitates the publishing and subscription of managed terms or words in order to govern companywide taxonomy.1 version of the Web Portal except the following sub sites: EPIET. including documents.NET framework v3. Improved usability 4.2. Excel spreadsheets.eu/OrgAndMe/workspaces/wss/WebPortalspace/1. SharePoint supports the custom branding of the different websites.Web Content Management System. Compliance with ECDC branding. 3.

2002).2. No formal analysis has been performed to evaluate the architecture. They are reusable. Analysis Results The architecture is based on the principles exposed in the book “Patterns of Enterprise Application Architecture” (Martin Fowler. More specifically: Page | 25 . public pages) while page layouts arrange the structure of different pages inside different sections (health topics. In addition to special SharePoint features. Masterpages and layouts: Different master pages form the basic structure of the various pages of the portal (admin. Web Parts: This is a component on a web page. The web portal can present data from CRM by the aid of this. The complete source site collection can be deployed. The web portal is utilizing handlers to redirect old urls (before the migration) to new urls and for serving RSS feeds. 2. Requirements Coverage The Web Portal 1. home.Web Content Management System.NET features: Http handlers: An ASP.1. custom ones are utilized by the portal Content Type Hub: it allows the centralization and sharing of content types through the Metadata Service Application. the web portal utilizes some special ASP. web part page etc) Resource files: They are used for making the application content easily available to multiple languages RSS feeds: Really Simple Syndication (RSS) is a widely used technology for transmitting information across the Internet and intranets.NET Web application (like SharePoint). Content deployment: it deploys content from a source site collection to a destination site collection. 2.2. search. In addition to the out of the box web parts. Migration and Maintenance Services for ECDC Web Portal .NET HTTP handler is the process (frequently referred to as the "endpoint") that runs in response to a request made to an ASP. which is considered as a reference in the field of enterprise application development.2. SharePoint offers support for syndicating content from the various lists.Reference H Javascript: Custom javascript is utilized by SharePoint in order to enhance the client side experience of the user.3. some code/functionality packaged in the form of Web Part.1 covers the general requirements as stated in the 2. Business Data Catalog: A SharePoint feature for integrate business data from back-end server applications. or a subset of sites can be deployed.3 section.

Figure 2: ECDC visual identity Page | 26 .Reference H 1. Migration and Maintenance Services for ECDC Web Portal .Web Content Management System. It adopts the ECDC design guidelines with a strong ECDC identity.

Reference H 2. less words per line are placed.Web Content Management System. Figure 3: Left hand navigation 3. In order to improve usability larger font size is used. Migration and Maintenance Services for ECDC Web Portal . and bullets are used to make lists clearer Page | 27 . Left hand navigation in all content pages.

2.2.4. and interfaces. classes. configure or remove web parts on various pages in order to add functionality. Timely notification of users: Social bookmarking.Web Content Management System. The elements are packages. Figure 4: Social network links 5. Summary of Background Changes Reflected in Current Version 3.Reference H 4. Migration and Maintenance Services for ECDC Web Portal . Views The views presented in this SAD are the following: Name of view Logical Rationale Describes how the system is structured in terms of units of implementation. The relationship between Module view? Yes Componentandconnector view? Allocation view? Yes Page | 28 . Content editors can add.

taken (mostly) from the problem domain. and its principal users. Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.1. They exploit the principles of abstraction. Sequence Diagram Development / Describes how development artifacts are Implementation organized in the file system.1. Logical View 3. The elements are files and directories (any configuration items).2. Class Diagram. 3. Yes Example diagrams: Component Diagram. This includes development artifacts and deployment artifacts. encapsulation. Yes Example diagram: Activity Diagram Physical / Deployment Describe how the system is mapped to the hardware. Example diagram: Use Case Diagrams 3. View Packet Overview Page | 29 .1.1. its external interfaces. Yes Yes Example diagram: Deployment Diagram Scenarios / Use-cases Describes functionality of the system. This decomposition is not only for the sake of functional analysis. but also serves to identify common mechanisms and design elements across the various parts of the system. Example diagrams: Entity Relations Diagram. interface realizations. in the form of objects or object classes. View Description The logical architecture primarily supports the functional requirements—what the system should provide in terms of services to its users. and inheritance. and so forth. The system is decomposed into a set of key abstractions. Package Diagram Process Describes how the run-time system is structured as a set of elements that have run-time behavior and interactions.Reference H elements shows dependencies. part-whole relationships.

1 is developed in SharePoint 2010.1.Reference H This view has been divided into the following view packets for convenience of presentation:  Entity relations diagram: Shows the entities at play and their internal relationship between each other. Also indicates the lifespans of objects relative to those messages. This was a natural choice since the previous Web Portal was running on SharePoint 2007 and the migration would be easier. and the relationships among the classes. Instead. SharePoint is quite suitable for the creation of web sites or intranets. View Packet: Sequence diagram Web editor team members do not access directly the production Web Portal environment.1. their attributes. Below is the sequence diagram that describes the procedure: Page | 30 . with definition of different roles.Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .1. Architecture Background The Web portal 1. View Packet: Entity relations diagram Not applicable.  Class diagram: Describes the structure of a system by showing the system's classes. 3.4.  Sequence diagram: Shows how objects communicate with each other in terms of a sequence of messages. they are making any updates to the staging environment.5. SharePoint environment takes over: the Content Deployment feature is utilized for transferring the updated content to the production environment. 3. 3.3. Additionally the content editing and the web part usage empower the content editors to add by themselves information and functionality to the pages. As soon as they select to publish a page. It offers comprehensive security model.

It is. The development view serves as the basis for requirement allocation. For the most part. the development architecture takes into account internal requirements related to the ease of development. software management. possible to list the rules that govern the development architecture: partitioning. for reasoning about software reuse. View Packet Overview This view has been divided into the following view packets for convenience of presentation:  Component diagram: Describes how a software system is split up into components and shows the dependencies among these components.2. Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.2.2. for monitoring the progress of the project. visibility. or the programming language.Reference H Portal environment. and to the constraints imposed by the toolset. It is the basis for establishing a line-of-product. portability and security. or subsystems— that can be developed by one or a small number of developers. grouping. each layer providing a narrow and well-defined interface to the layers above it. The development architecture of the system is represented by module and subsystem diagrams. however. Figure 5: Sequence diagram for the creation and publication of a new page to the web portal 3.2. showing the ‘export’ and ‘import’ relationships. The software is packaged in small chunks—program libraries. Page | 31 . The complete development architecture can only be described when all the elements of the software have been identified. for allocation of work to teams (or even for team organization). for cost evaluation and planning. 3. Development / Implementation View 3. View Description The development architecture focuses on the actual software module organization on the software development environment. The subsystems are organized in a hierarchy of layers.1. reuse or commonality.

7.2. 3.9. HttpHandlers It contains the http handlers that were developed for .3. BDC It contains the Business Data Catalog implementations for present data from CRM as SharePoint lists. Tools Contains various small console applications and tools.2. Applications It contains the solution for the custom version of RSS feed.2. Metadata Contains the definition for the content types stored in the content type hub.8.3.6. Templates Contains custom forms used for News.Reference H  Package diagram: Describes how a system is split up into logical groupings by showing the dependencies among these groupings.2. Migration and Maintenance Services for ECDC Web Portal .TV. UserInterface Contains all the artifacts that support the user interface of the portal.config.2. It consists of multiple sub solutions that are organized in the following subfolders: 3.2. and an event receiver that performs UI configuration.5. There is a specific list that contains the old and news Url mapping 3.redirecting from some old links to the new location of them after the migration. 3. Events.2. Call for Tenders.3. used to aid the migration. Architecture Background The source code of the application is developed and stored in the form of MS Visual Studio 2010 solution. Publications. 3.2.Player: used for playing videos Page | 32 .4. master pages.ECDC. 3. 3. or perform other supporting development tasks.3. address issues and bugs.redirecting the SharePoint RSS feeds to the custom implementation of Web Portal RSS feeds. 3.Web Content Management System. WebParts This is a quite important subfolder since it contains the work done for the various web parts. Publications.2. stylesheets. .3.3. Scientific Advice. More specifically it contains javascript files.3. WebConfig Contains features that add entries in the web.3.1.3.2.3. form layouts.2. page layouts. 3. More specifically it contains: . Call for Grants.3. 3.

ECDC.WP.FilterPictLibrary: A custom image display control that uses a dropdown list .WP.ECDC.SP.WP.WP.ECDC.WP.ECDC.SP.WP.WP.WP.ECDC. Migration and Maintenance Services for ECDC Web Portal .SP.ContentDisplay: This is a custom content box .WP.ECDC.CompetentBody: used at the Competent body page .WP.ECDC.SP.ImageRotator: used for displaying images from a custom list . Page | 33 .WP.Web Content Management System.TessyRedirection: used for redirecting requests for old urls to the new ones for the TESSy related pages.WP. .ECDC.WP.OpenDocument: Presents the documents of a list as entries inside a dropdown control.SP. .SP.WP.SP.SP.SP.PhotoGallery: Used for displaying images as a photo gallery.SP.Organization: Displays information from a list containing organizational information items.WP.WP.WP.Reference H .ECDC.WP.SP.WP.ECDC.WebParts.SP.ECDC.AFMB: used for diplaying the Advisory and Management board members .WP.WP. . .PhotoViewerDropDownList: It is a photo viewer web part .Members: used for displaying information from a list containing ECDC contacts.WP.WP. .CustomForm: It enables the building of custom form by using xml definitions.ECDC.WP.TessyReports: Used for displaying TESSy reports as they are retrieved from Reporting Server .ECDC.WP.

The Content Type Hub.Management Board . CRM integration CRM provides information to the Web Portal in order to populate three lists: .Web Content Management System.2. View Packet: Package diagram 3. View Packet: Component diagram Figure 6: Component diagram Above the high level component diagram of the application can be found.4. CRM and Tessy contribute data that is displayed by the various pages of the Web Portal.1.5.Advisory Forum .2. Managed Metadata Service.2.5.Reference H 3.Coordinating Competent Bodies Page | 34 . Migration and Maintenance Services for ECDC Web Portal . 3.

Reference H Figure 7: Advisory Forum CRM data access Figure 8: CRM Competent Bodies data access Page | 35 . Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.

Web Content Management System. The related CRM fields for the contacts are mapped to columns of SharePoint lists in order to encapsulate the external CRM data to a SharePoint list form.2. 3.Reference H Figure 9: Management Board CRM data access This is done by using Business Connectivity Services of SharePoint.5.2. Migration and Maintenance Services for ECDC Web Portal . Content Type Hub Page | 36 .

and shut down).2.Reference H The Content Type Hub is a central location where content types can be defined and published. It addresses issues of concurrency and distribution. or for improved availability. In this manner there is a central repository of reusable content types.3. Some base content types are defined at the hub. View Packet Overview This view has been divided into the following view packets for convenience of presentation: Page | 37 . A process is a grouping of tasks that form an executable unit. Process View 3. processes can be replicated for increased distribution of the processing load. such as performance and availability. started.Web Content Management System. Migration and Maintenance Services for ECDC Web Portal . Figure 10: Content Type Hub 3. of fault-tolerance. View Description The process architecture takes into account some non-functional requirements. recovered.e.. The software is partitioned into a set of independent tasks. Such content type hub is utilized by the web portal. Even updates are reflected to the subscribed web applications.3. In addition. and how the main abstractions from the logical view fit within the process architecture—on which thread of control is an operation for an object actually executed. The imported ones are used again in order to produce new derived custom content types that are specifically tailored to the Web Portal needs.3. of system’s integrity. The following diagram depicts the base types that are provided by the ECDC content type hub. Processes represent the level at which the process architecture can be tactically controlled (i. reconfigured. These type are imported in Portal. 3.1. A task is a separate thread of control that can be scheduled individually on one processing node.

1. Migration and Maintenance Services for ECDC Web Portal . performance (throughput). View Packet: Activity diagram In specific pages an approval workflow is attached.4. and objects—need to be mapped onto the various nodes.4.3. 3.3.2.Reference H  Activity Diagram: Describes the business and operational step-by-step workflows of components in a system. Physical / Deployment View 3. reliability (fault-tolerance). The mapping of the software to the nodes therefore needs to be highly flexible and have a minimal impact on the source code itself. View Packet Overview This view has been divided into the following view packets for convenience of presentation: Page | 38 . We expect that several different physical configurations will be used: some for development and testing.4. others for the deployment of the system for various sites or for different customers. View Description The physical architecture takes into account primarily the non-functional requirements of the system such as availability. An example is the “World Health Day 2014” page: Figure 11: Activity diagram for the page approval 3. An activity diagram shows the overall flow of control. tasks. or processing nodes (or just nodes for short).Web Content Management System. The software executes on a network of computers. The various elements identified—networks.4. and scalability. 3. processes.3. Architecture Background 3.

upload images and files.5. View Description The elements in the four views are shown to work together seamlessly by the use of a small set of important scenarios —instances of more general use cases—for which we describe the corresponding scripts (sequences of interactions between objects. their goals represented as use cases.3.5. 3. add and configure web parts. Architecture Background Web portal audience is divided into three categories: - Public anonymous end users. but it serves two main purposes:  as a driver to discover the architectural elements during the architecture design as we will describe later  as a validation and illustration role after this architecture design is complete. and between processes). both on paper and as the starting point for the tests of an architectural prototype. and any dependencies among those use cases. 3. Below are the use cases for a selection of web parts: Page | 39 .5.4. View Packet: Use-case diagram The utilization of the web parts is one of the most important and used in Web Portal.5. 3.1. Scenarios / Use-cases View 3.Web Content Management System. These are the ECDC users that add content to pages.5. This view is redundant with the other ones (hence the “+1”). Migration and Maintenance Services for ECDC Web Portal . 3.2. View Packet Overview This view has been divided into the following view packets for convenience of presentation:  Use-case diagram: Describes the functionality provided by a system in terms of actors. These are the end users that consume the information presented by the various pages of the web portal. The scenarios are in some sense an abstraction of the most important requirements.Reference H  Deployment diagram: Describes the hardware used in system implementations and the execution environments and artifacts deployed on the hardware. - Web Editor Team members. They do not authenticate but access it in an anonymously.

Reference H Figure 12: Advisory and Management web part use case diagram Page | 40 .Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .

Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 13: ECDC Web Content Box web part use case diagram Page | 41 .Web Content Management System.

Web Content Management System.Reference H Figure 14: Country Information small map web part use case diagram Page | 42 . Migration and Maintenance Services for ECDC Web Portal .

Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 15: Custom Form use case diagram Page | 43 .

Reference H Figure 16: ECDC Content Query web part use case diagram Page | 44 .Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .

Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.Reference H Figure 17:ECDC TV web part use case diagram Page | 45 .

Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.Reference H Figure 18: Events web part use case diagram Page | 46 .

Reference H Figure 19: Related pages web part use case diagram Page | 47 .Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .

Reference H Figure 20:Filter Picture Library web part use case diagram Page | 48 .Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .

Web Content Management System.Reference H Figure 21: Health Topics web part use case diagram Page | 49 . Migration and Maintenance Services for ECDC Web Portal .

Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.Reference H Figure 22: Image Rotator web part use case diagram Page | 50 .

Reference H Figure 23: Related News web part use case diagram Page | 51 .Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .

Web Content Management System. Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 24: Open Document web part use case diagram Page | 52 .

Migration and Maintenance Services for ECDC Web Portal .Reference H Figure 25: Picture Viewer with Dropdown web part use case diagram Page | 53 .Web Content Management System.

Some aspects of a system are relevant to the Developers.Reference H Figure 26: Photo Gallery Small picture web part use case diagram 4. Kruchten thought it made sense to decompose architecture into distinct views so stakeholders could get what they wanted. Why? Because different stakeholders always have different interest in a software system. hardware and network configurations and don't care about classes. Relations Among Views This document and the views included are based on the 4+1 view model: In November 1995. while working as Lead software architect at Hughes Aircraft Of Canada Philippe Kruchten published a paper entitled: "Architectural Blueprints—The “4+1” View Model of Software Architecture".Web Content Management System. The Developers want to know about things like classes. others are relevant to System administrators. In total there were 5 views in his approach but he decided to call it 4 + 1. Project Managers and Customers. Similar points can be made for Testers. [Kruchten 1995] Page | 54 . System administrators want to know about deployment. The intent was to come up with a mechanism to separate the different aspects of a software system into different views of the system. Migration and Maintenance Services for ECDC Web Portal .

Kazman. 2001. Documenting Software Architectures: Views and Beyond. Clements. IEEE Recommended Practice for Architectural Description of Software-Intensive Systems. Kruchten 1995 Philippe Kruchten.1 – Guidelines (v 4.1) Olivia Carstocea (from 2010 to 2013) Use Cases for Web Portal Web Parts (15 web parts) Page | 55 . Ivers. Clements 2002 Clements. Kazman. second edition.Reference H 5. IEEE Software 12 (6). Clements 2001 Clements. Stafford. Addison Wesley Longman. Architectural Blueprints—The “4+1” View Model of Software Architecture. Software Architecture in Practice. 1995 Olivia Carstocea 15 May 2013 Web Portal 1. 21 September 2000. 2003. Referenced Materials Bass 2003 Bass. Addison Wesley Longman. IEEE 1471 ANSI/IEEE-1471-2000. Bass. Migration and Maintenance Services for ECDC Web Portal . Garlan. Addison Wesley Longman. 2002.Web Content Management System. Nord. Little. Klein. Evaluating Software Architectures: Methods and Case Studies. Bachmann.

performance characteristics. "Externally visible” properties refer to those assumptions other elements can make of an element. evaluation techniques.Reference H 6. Appendix: Glossary and Acronym List Term Definition software architecture The structure or structures of that system. Appendices 6. and identifies the modeling techniques. The documentation of a view is composed of one or more view packets. used by any conforming view. and the relations among them. a pattern or template from which to develop individual views by establishing the purposes and audience for a view. Migration and Maintenance Services for ECDC Web Portal . and the relationships among them [Bass 2003]. Acronym Definition API Application Programming Interface. fault handling. which comprise software elements. etc. A representation of a particular type of software architectural elements that occur in a system. view A representation of a whole system from the perspective of a related set of concerns [IEEE 1471].Web Content Management System. the externally visible properties of those elements. their properties. Application Program Interface. consistency checking techniques. and the techniques for its creation and analysis [IEEE 1471]. Identifies the set of concerns to be addressed.. shared resource usage. view packet The smallest package of architectural documentation that could usefully be given to a stakeholder. viewpoint A specification of the conventions for constructing and using a view. such as its provided services. and so on.1. A view conforms to a defining viewpoint. Application Programmer Interface ATAM Architecture Tradeoff Analysis Method CMM Capability Maturity Model CMMI Capability Maturity Model Integration CORBA Common object request broker architecture COTS Commercial-Off-The-Shelf EPIC Evolutionary Process for Integrating COTS-Based Systems IEEE Institute of Electrical and Electronics Engineers KPA Key Process Area OO Object Oriented ORB Object Request Broker OS Operating System QAW Quality Attribute Workshop Page | 56 .

includes Software Engineering UML Unified Modeling Language Page | 57 .Reference H RUP Rational Unified Process SAD Software Architecture Document SDE Software Development Environment SEE Software Engineering Environment SEI Software Engineering Institute Systems Engineering & Integration Software End Item SEPG Software Engineering Process Group SLOC Source Lines of Code SW-CMM Capability Maturity Model for Software CMMI-SW Capability Maturity Model Integrated . Migration and Maintenance Services for ECDC Web Portal .Web Content Management System.