Distributed Information Systems Lecture 7 - Practical Lecture1 Introduction, Lecture notes of Computers and Information technologies

Download Distributed Information Systems Lecture 7 - Practical Lecture1 Introduction and more Lecture notes Computers and Information technologies in PDF only on Docsity!

Distributed InformationDistributed Information

Systems Systems

Markus A. Wolf & Elena I. Teodorescu^ Markus A. Wolf & Elena I. Teodorescu

Practical Lecture 1

Introduction

Overview^ Overview

•^

Building a distributed information system withheterogeneous clients

-^

The system will be implemented using Microsoft.NET technology

-^

Clients will be implemented using .NET andJava technology to demonstrate cross-platforminteroperability in distributed systems

-^

The implementation is spread over 6 practicallectures

Pre^ Pre

requisite Knowledgerequisite Knowledge

•^

During the implementation of the system newconcepts related to the development ofdistributed system will be explained

-^

The practical sessions require a good priorknowledge of the following:^ – Database principles and SQL– Database design using entity relationship modelling– Microsoft Visual Studio– C# programming– Java programming– System analysis and design using UML (Unified

Modelling Language)

Tools^ Tools

• The following software tools will be used

during the implementation of the system:^ – Microsoft SQL Server 2005

• Including SQL Server Management Studio
  • Microsoft Visual Studio .NET 2005– NetBeans 5.

Introduction^ Introduction

• In this practical session we will introduce

the case-study:^ – The background– The requirements– What will be built (proposed system)

• We will explain the architecture and

behaviour of the proposed system

• You will build the database required for the

proposed system

Case^ Case

StudyStudy

• During the course of the six practical

lectures you will be incrementallyimplementing a system

• As each lecture builds on the work carried

out in the previous lectures, it is importantto do these in sequence

Out Of Bounds Ltd^ Out Of Bounds Ltd

Spain

India Sri Lanka

Slovakia

London Headquarter

Kent

Case^ Case

StudyStudy

Current SituationCurrent Situation

•^

Out Of Bounds Ltd is currently using Pert andGannt charts to plan the project and set uptasks, responsibilities, timeframes, etc.

-^

Instructions are then given to the team leadersinvolved

-^

Communication/progress tracking is donethrough face-to-face meetings with local teamsand through email/telephone/video conferencingwith the international teams

Case^ Case

StudyStudy

Requirements /2Requirements /

•^

Project Tracking System:^ – This system will allow a manager to register projects– Projects are divide into tasks– Rules regarding the order of tasks can be set– Different tasks can be assigned to different teams

(working for the company or outsourced to externalteams)

• The system will provide functionality for team leaders

to register task progress. Project progress can betracked by the project manager

• The customer who commissioned the project can get

summary information about the structure of theproject, distribution of work and progress

Users/Roles^ Users/Roles

• The system will be accessed by four

different types of users:^ – Administrator/project manager– Team leader (internal)– Team leader (external)– Customer

Users/Roles^ Users/Roles

Team LeaderTeam Leader

•^

A team leader is the person in charge of aparticular team. A team could be:^ – Internal team – employed by Out Of Bounds Ltd

• Local• International
  • External team – contracted by Out Of Bounds Ltd in

order to carry out tasks^ • Could be contracted because Out Of Bounds lacks resources

for a project or lacks the particular expertise

• Could be based anywhere (locally or abroad)

Users/Roles^ Users/Roles

Team Leader /2Team Leader /

• The responsibilities of a team leader

include:^ – break tasks down into subtasks– estimate completion dates for new tasks– assign subtasks to team members– record progress on a particular task– record completed tasks– report expected delays, justify them and

provide new estimated completion dates

Requirements Overview^ Requirements Overview

• One system – serving a number of

geographically dispersed users

• Different types of users which require

different functionality from the system

• Possibly different technologies/platforms

used by different users

CaseCase

StudyStudy

Proposed SystemProposed System

• Need to provide different interfaces – We have different types of users • Need for a

distributed

system

• Users are in different locations using the same

system

• Need for some kind of data layer – Information needs to be stored about projects,

teams, etc.