Software Architecture and Construction on Transit Control system

Transit control system

1

1. Background

This document provides a high level overview and of whole architecture of Process Specification Tool (PST), it explains how TCS insuring the goods reach to the rightful owner without any delay change in quality or in quantity, and free of dumping (Kesheba) if one of this fail to meet the system generate alert and notify in real time and relevant time. TCS system also incorporates different governmental bodies and private organization for the purpose establishing safe transit system. The document provides a high-level description of the goals of the architecture, the use cases support by the system and architectural styles and component. This framework then allows for the development of the design criteria and documents that define the technical and domain standards in detail.

.

Click t

o buy NOW!

PDF-XCHANGE

www.docu-track.com Clic

k to buy N

OW!PDF-XCHANGE

www.docu-track.com

http://www.docu-track.com/buy/



2

1.1 Purpose

The software architecture Document provides a comprehensive architectural over view of Transit Control System. It presents a number of different architectural views to depict different aspects of the system. It is intended to capture and convey the significant architectural decisions which have been made on the system.

In order to depict the software as accurately as possible, the structure of this document is based on the “4+1” model view of architecture.

The “4+1” View Model allows various stakeholders to find what they need in the software architecture.

1.2 Scope

This Software Architecture Document provides an architectural overview of the Transit Control System. The Transit Control System is being developed by HiLCO School of computer Science and Technology student to support and facilitate transit system across the country (Ethiopia). This Document has been generated directly from the Requirement Analysis & Design project.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




3

1.3 Document structure and reading suggestion

1.3.1 Document structure

Architectural activities Software Architecture Document

Step 1 - Background Section 1

Step 1 - purpose Section 1

Step 2 - Scope Section 1

Step 3 – Document structure and reading suggestions

Section 1

Step 4 – Design consideration and Decisions Section 2

Step 5 - Contextual Considerations Section 2

Step 6 – Data flow Diagram of TCS Section 2

Step 7 - Architectural Representation Section 2

Step 8 -TCS Qualities Section 2

Step 9- TCS Constraints Section 2

Step 10- Assumption and dependencies Section 2

Step 11- System Decomposition and Views Section 3

Step 12- Sub system of TCS Software Section 3

Step 13- Sub system interface Section 3

Step 14- Allocation View Section 4

Step 15- Deployment Section 4

Step 16- Implementation Section 4

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




4

1.3.2 Reading Suggestion

Document name Date Author

FLOSS SOLA Data Dictionary v1.0 26 July 2011 SOLA Development Team

FAO way of working Document v1.1 10 Feb 2011 Alexander Lokhaman and

Imed Hammoud

Technology option for Architectural

documentation

8 Feb 2011 A McDowell

Community portal Use Case August 2002 Valerie Smothers

Kruchten, IEEE software November1995

Architectural Blueprint-the “4+1” View

Model of Software Architecture,

April 2005 Philippe

http://www.government-fleet.com/article/story/2004/07/part-1-fleet-information-management-system-data-architecture.aspx

https://sites.google.com/site/softwarearchitectureinpractice/11-architecture-evaluation/c-the-atam/atam-phases

http://www.krawler.com/scmsuite/fleet-management-system-

http://www.mixtelematics.com/solutions/vehicle-tracking?gclid=CPnC_9Xwrb4CFbShtAodPxkA-Q

http://www.allbookez.com/functional-architecture-diagram-for-hospital-management-system/

http://worldlibrary.org/catalog/1/ebook-library-collections

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




5

2. Design Consideration and Decisions

This section documents the system terms of its purpose and the problem that it solve. It describe the:-

Context in which the system will be used and the problems that it solve

Functionality that the system provides at interface and the qualitative characteristics of the services.

The system purpose section provides a black box view of the Transit Control System to be designed. The Transit Control System satisfies the requirement as defined in any valid system requirement document. If for any reason there are requirements which are not met by the Transit Control System, then this must be explicitly recorded and we consider it as a constraint for Transit Control System. In the Design Consideration and Decision section we provide the summary of the specification concerning Contextual consideration, Quality attribute consideration and architecture and Assumption and dependencies documents.

dddd

Figure 1: Design Consideration and Decisions

2.1 Contextual Considerations

In this section we briefly describe the context of the system and the problem that it solves. The intention of this section is to allow us to provide an introduction to the system that is accessible to non-domain experts. The problem description should specify the key entities involved with the system, and the roles of these entities, not the system it self. In order to describe the problem solved by the system we define the boundary between the Transit Control System and its environment. The Context diagram can be represented or illustrated by different forms, such as an object or class diagram, High-level use case diagram and data flow diagram. From those methods we prefer to use data flow diagram that will make TCS easily understandable

Contextual consideration

Quality attributes consideration and architecture

Assumption and dependencies documents

Design Consideration and Decisions

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




6

Figure 2: Data flow Diagram of TCS

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




7

2 .2 Architectural Representation

As we describe in the introduction this document detail architecture presented using 4+1” model view. The Views used to document The TCS are:-

Logical view

Audience: Designers.

Area: Functional Requirements: describes the design's object model. Also describes the most important use-case realizations.

Related Artifacts: Design model

Process view

Audience: Integrators.

Area: Non-functional requirements: describes the design's concurrency and synchronization aspects.

Related Artifacts:- no specific artifact

Implementation view

Audience: Programmers.

Area: Software components: describes the layers and subsystems of the application.

Related Artifacts:- Implementation model, components

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




8

Deployment view

Audience: Deployment managers.

Area: Topology: describes the mapping of the software onto the hardware and shows the system's distributed aspects.

Related Artifacts: - deployment model.

Use Case view

Audience: all the stakeholders of the system (ERCA, Minstar of Transport, Insurances Company, Transistor, Truck owners and Development team)

Area: describes the set of scenarios and/or use cases that represent some significant, central functionality of the system.

Related Artifacts: - Use-Case Model, Use-Case documents

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




9

2.3 Quality Attribute Considerations and architectural decisions

This section documents a summary of those requirements that address aspects of the system besides functionality and that are relevant for the system architecture.

2.3.1 TCS Qualities:-

I. Availability of TCS

TCS Provides real time and relevant time communication between the cargo or fuel truck and the system.

There will be a highly distributed system in ERCA branch offices; in case failure is occurred quick response shall be necessary to manage the faults.

Communication has a possibility of being lost (because of noisy or overloaded communication lines), a reliable transmission protocol can be used to recover.

We will have active server in ERCA main branch which responds events and informs the other distributed standbys servers and update the state they must make.

A standby spare computing platform shall configure to replace many different failed components.

Once a fault in a process has been detected, a monitoring process can delete the nonperforming process and create a new instance of it, initialized to some appropriate state as in the spare.

Transactions shall use to prevent any data from being affected if one step in a process fails and also to prevent collisions among several simultaneous threads accessing the same data.

In the case of network failure the system remain operational in relevant time which allow to record up to 50 events.

II. Modifiability of TCS

We shall organize modifiability in sets according to TCS goals. TCS shall integrate with the legacy system without any effect. Because of users need and technology change, TCS shall adapt and make change without

affecting the user interface. Localizing modifications is one set of reducing the number of modules that are directly

affected by a change. We shall use ripple effect to limit modifications to localized modules. We shall use defer binding time to control deployment time and cost.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




10

III. Performance of TCS

The TCS shall be fast and perceived as more efficient than the current systems. TCS shall safe and secure for the intended users this might decrease the performance because we give much attention for security rather performance. There will be contention of resource because the system enables to serve 10,000 trucks across the country. Therefore, we shall use arbitration mechanism this will standardized how the contention is arbitrated and how individual requests are treated.

Unavailability may be caused by the resource being offline or by failure of the component or for some other reason. Therefore, we shall intended to provide update (real time and relevant time) information about the status of the cargo and the fuel in convenient, secure, and advanced way We shall introduce concurrency because if requests can be processed in parallel, the blocked time can be reduced. We shall maintain multiple copies of either data or computations. The purpose of replicas is to reduce the contention that would occur if all computations took place on a main server.

We shall increase availability of resources. Faster processors, additional processors, additional memory, and faster networks all have the potential for reducing latency. This will assure the performance as well as security of the TCS.

IV. Security of TCS

TCS shall detect attack and those concerning with recovering from attacks. We shall authenticate users through password. By thin-client. There will be authorized users who have the right to access and modify either data or services.

We shall maintain confidentiality by applying some form of encryption to data and to communication links.

We shall maintain integrity by delivering message to the intended user only. We shall limit exposure by designing the allocation of services to users so that limited services are available on each interface.

We shall maintain an audit trial. This can be used to trace the actions of an attacker, support no repudiation (it provides evidence that a particular request was made), and support system recovery.

We shall maintain audit trial in trusted fashion to manage it.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




11

V. Testability of TCS

Since testing consumes a high percentage of system development cost, anything we can do to reduce this cost will yield a significant benefit.

One of the well-known testing mechanisms is separating the interface from the implementation which allows substitution of implementations for various testing purposes.

Recording the information also allows us to test input for one of the components to be generated and test output for later comparison to be saved.

We shall use refactoring mechanisms.

VI. Usability of TCS

Any subsequent stages of development should be based on this document to ensure consistency and achieve better usability of the TCS.

Separate the user interface from the rest of the application. Since the user interface is expected to change frequently both during the development and after deployment, maintaining the user interface code separately will localize changes to it.

TCS shall need less keyboard input from user. The user interface in TCS shall be consistent. Users expect consistency and will

make errors where inconsistencies occur. TCS shall provide enough help for users to accomplish their task. Terminologies also needed to represent some tasks.

2.3.2 TCS Constraints

Constraints are conditions and limitation on TCS from its environment.

The system has to run on window The TCS must ensure complete protection of data from unauthorized access of

all client bank statement. All access are subject to user identification and password control

The bank system must be integrated with TCS The policy of the government should govern the implementation of TCS Insurance company should have access to a particular customer declaration.

Insurance company cover the damaged or lost goods based on the client declaration to the bank

Internet services depend on service provided by ETCC. Internet service provider provides 3G SIM card for each GPRS modem installed in the truck.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




12

2.4 Assumption and dependencies

Assumption of TCS Dependency

There should be robust internet services The system depend on the service provided by ETCC and Djibouti telecom service provider

The Government imposes suitable rule and regulation that has a positive impact on the success of the project.

The system depend on the rule imposed by the government

As the need increase and relase 1.0 aplicaple there will be a copany that capable of providing hardware component like AVL (Automatic vhice Locator), GPRS modem,CR (copact reader),LFT (Low Frequency terminal) and MHHT (Mastor Hand Heald Terminal

There should be a company licensed and registered to supply RFID enabled and embedded hardware

Coperation among differet goverment organization wiil be acheved

TCS must be integrated with ASYCUDA

The Dajibuti tele service providert allowtele rooming service for the TCS GPRS modem

The service depend on the service Provided by Djibouti telecom service

The TCS will inspire a number of hardware supplier which in near future reduce the cost of the hardware

The number of hardware suppler increase it can deduce the cost of the hardware

When TCS release 1.0 lounche the transit system minmize the work effort required and increase the trust of government and non governmetal organization on the bases of relable ,tangable and confedential data exchange

The system depend on the impact of release 1.0

Non Governmental Banks trust the security of the system and they will request to integrate there system, some feature with TCS

The system depend on the mutual interest and trust between an organization.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




13

3. System Decomposition and Views

The purpose of this section is to describe the static structure of the architecture in terms of its logical components and their interconnections.

Figure 3: System Decomposition and Views

System Decomposition and Views

Sub systems

Sub System interface

Allocation view

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




14

Figure 3: TCS architectural diagram

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




15

Figure 4: Sub System Decompositions

CC Sub System

Station ESP

ESP Server

ERCA Control Center Application

Work Station Application

CR (Compact Reader)

LFT Microreader

Station Sub system

Minster of Transport Sub system

Location Fuel sensor

Speed

Lock (Wireless data seal)

AVL

Sub System

Client ESP

MHHT

Transport Company

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




16

3.1 Sub systems

This section describes each component in the architecture. This section contains references to the component design documentation and to the implementation.TCS sub system is complex system that should be broken down in to sub system.

Key points

Responsibilities

Describe the purpose or job description of the component in terms of

1. Component responsibility 2. The interfaces that it provides

Collaborators

List of other component in TCS from which the component request service in order to achieve its purpose.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




17

3.1.1 Sub system of TCS Software

Sub system ESP server Responsibilities

Provide web based application to the user of TCS

Collaborations

Interface :CC Manifest Sub system MHHT (Comand Center) Sub system LFT

Sub system ERCA control center Application Responsibility Create ,Edit and Delete Route

Create, Edit and Delete Account Record Alert history, Login information and notify the operator when alert generated.

Collaboration Interface : Alert Severity Status Interface :Authentication Interface :Route Sub System :ESP Server Sub System :Station Server

Sub system Work Station Application Responsibility Maintain information about the transit when

the trip start and send to ESP server At the destination notify the operator about the status of the transit.

Collaboration Interface :Work Station ESP Interface :Work Station Alert Sub System :MHHT Sub System : Compact Reader Sub System : Micro Reader

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




18

3.1.2 Sub system of TCS Hardware owned by ERCA

Sub system MHHT (Master Handheld Terminal) Responsibility Write and read manifest information about the

transit Collaboration Interface : Work Station ESP

Interface : Work Station Alert Sub system :Work Station Application

Sub system Micro Reader Responsibility Notify the operator the effect of the changes

while transit goods suspected for dumping Collaboration Sub system : Work Station Application Sub system Compact Reader Responsibility Read status of the transit in relevant time Collaboration Sub system :AVL Sub system LFT (Low Frequency Terminal) Responsibility Write the transit information on the Seal Collaboration Interface :Work station manifest

Sub system : Work Station Application

3.1.3 Sub system of TCS owned by Client

Sub system Locks/Wireless Data Seal Responsibility Provide information about the status of the

goods in transit, Information provided in real time for the central server and in relevant time for the AVL modem

Collaboration Sub system : AVL Sub system AVL (Automatic Vehicle Locator) Responsibility Facilitate the synchronization between the

Lock and the central server Collaboration Sub system : Locks/Wireless Data Seal

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




19

3.2 Sub system interface

Interface Work station Manifest Description Allow access the transit goods in progress Operations Operation :access to the Transit goods in progress

Description : list of truck in the specified route Operation :Trip start Description: Transit number created, Route selected, Destination site selected, Truck plate number inserted and Truck armed. Operation :Trip finalized Description : Access work station manifest, inserting Transit number and returned the corresponding rout, truck plate number and Trip start date

Interface Work station alert Description Allow trip starting site and destination site to access alert for the trip

initiate in their particular route. Operation Operation :browse alert

Description: Select the particular transit number in their route and select alert. The system return Alert with corresponding severity level Operation :Delete alert Description: Select the particular transit number in their route and select alert. The system return Alert with corresponding severity level, then operator insert authentication number and delete the alert

Interface CC Manifest (Command Control Mangiest) Description Allow to register truck and delete truck from the system Operation Operation :Register Truck

Description: Truck plate number and Transport company registered to the system. New truck Displayed Operation :Delete truck Description: Removal of target plate number truck Operation :Create route Description: Select route from trip start site to destination. new route created Operation :Remove route Description: Remove target route

Interface Authentication Description Provide access to create and delete password or change authentication

level Operation Operation :Create password

Description: New password with corresponding authentication level created Operation :Delete password Description: Removal of target pass word Operation :Change Authentication Level Description: Authentication level changed. System return new Authentication level

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




20

4. Allocation views

TCS software interacts with its environment in various ways so that different groups of people with different tools can develop, store, and execute the software, both the software architecture and environmental structures influence each other.

We will start out by considering the TCS allocation view type in its most 3 general styles

The TCS Deployment style describes the implication of the hardware on which the software executes

The TCS Implementation style describes the mapping of modules on a configuration management scheme and helps the TCS files that implement the modules

The TCS Work Assignment style describes the aggregation of modules according to the people, groups, or teams which are tasked with the actual development of the implementations of the modules.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




21

4.1 Deployment Diagram

The TCS deployment diagram describes the relationship of components with that of

Hardware, it gives a high-level view of each component deployment.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




22

4.2 Implementation Style

Implementation of the TCS is the programming tools, and development environment.

1 Programming Tool

The web-based application is becoming a turning point of solution for the industry

World when a distributed application becomes an issue. It is a multitier application by its nature, where functionalities are divided into tiers. This nature of the application enables the task division easy and increases flexibility. The web-based application requirements of technology are categorized into two; these categorizes are the client technology and the server technology. The client technology is referred as browser technology. The browser technology is left to the client Internet explorer, Fire fox or any. The server technology requirements are basically seen from three technology corners; these are the web server, the web pages and database. The development of the web pages can be made possible using the different technology of preference; the java technology is one of them, which is the technology choice of development tool. The java technology has three technology components in supporting the web-based applications. These are the servlets java server pages and applets. From these technology components the first two along with that of the web server will be discussed in the following paragraphs.

1.1. Servlet

This technology component extends the web servers functionality by allowing the server to generate dynamic contents. The dynamic contents enables in achieving security and easy interaction with that of a database. It uses the HTTP request response model of communication between the client tier and the server tier.

1.2. Java Server Page (JSP)

It is an extension of the servlets technology. JSP unlike that of servlets, it separates the presentation from the contents. JSP has four parts; these are directive, actions, scripting element and tag libraries. The processing on JSP enabled server is: - As the server receives the request the JSP container translates the JSP into servlet that handles the current request.

1.3. Web Server

The web server is the one that handles the request from the browser. The choice of such servers depends on many factors. For TCS capacities of handling concurrent requests and freedom of choice in the platform they run are considered. It is the apache web server which is selected, the apache web server is free open source software and it has the capability of running on different platforms.

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




23

Appendix A: Glossary

Terms Description

Rout The specific direction which the transit expect to follow until it reach to clearing house

Importer The person or company engaged in importing activity which has the financial clime of the goods.

Exporter The person or company engaged in Exporting activity which has the financial clime of the goods.

Dumping /Kesheba Removal/Additional of goods or part of the goods which is not included in the declaration

Real time The communication between device at a time t

Relevant time The seal hold the data to be transfer and send the data when it get the network

Roaming service Allow other country mobile network to operate

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com




24

Appendix B: Abbreviations

API Application Programming Interface DBMS Database Management System OS Operating System TCS Transit control system ETCC Ethiopia Tele Communication Corporation HTML Hypertext Markup Language OTCS Online Transit control system SMS Small Message Service SRS Software Requirements Specification ERCA Ethiopia Revenue and Custom Authority AVL Automatic Vehicle Locator CR Compact Reader LFT Low frequency Terminal GPRS General Packet Radio Service GPS Global Positioning System MMHT Master Hand Held Terminal IP Internet protocol

LF Low frequency

PST Process Specification Tool

TCS Transit Control System

Click t

o buy NOW!

PDF-XCHANGE


k to buy N

OW!PDF-XCHANGE

www.docu-track.com



Software Architecture and Construction on Transit Control system

Documents

Transcript of Software Architecture and Construction on Transit Control system