1 SCIRO - Bled - 19-20/09/02 WP2 Functional Requirements and Architecture External Functional Analysis (D4) & Internal Functional Analysis (contribution.

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

AAA Architecture Use of a AAA Server Application Specification to Support Generic AAA Applications Across a Mesh of Interconnected AAA Servers With Policy.
Diameter Credit Control Application Tutorial - IETF67
UML an overview.
1 SOLVAY The Sarralbe Experience Sarralbe is the name of a town in France, close to the border between France and Germany. In this town Solvay has a Production.
Use Case & Use Case Diagram
UGDIE PROJECT MEETING Athens September WP6 – Assessment and Evaluation  Evaluation Results  Deliverable D 13 (first release issued and delivered.
The University of Anytown School of Business Computing.
WP3- Development: Milestone M3 Lisbon 30 January 2004 National Technical University of Athens.
Introduction to Database ISYS 363. File Concepts File consists of a group of records. Each record contains a group of fields. Example: Student file –SIDSnameMajorSexGPA.
Figure 6-1: Transport Request Data Entities: CS: Customer OM: Order manager OPM: Operational manager FM: Fleet Manager MM: Maintenance manager OBT: On.
Robustness Analysis Dr. Neal CIS 480. Outline What is robustness analysis? Key roles in robustness analysis Object types found in discovery Diagramming.
Lecture 13 Revision IMS Systems Analysis and Design.
Introduction to Database ISYS 363. File Concepts File consists of a group of records. Each record contains a group of fields. Example: Student file –SIDSnameMajorSexGPA.
Application architectures
ΑΝΝΕΧ 11-A by SCIRO. WP7 Dissemination and Implementation The objectives are the following: to build consensus around F-MAN To set-up the basis for further.
Crete Meeting April 10 th – 11 st, 2003 WP3 Sciro Presentation.
UGDIE PROJECT MEETING Bled September WP6 – Assessment and Evaluation Evaluation Planning  Draft Evaluation plan.
ΑΝΝΕΧ 3 by SCIRO. Task 2.1 – Functional requirements definition Task 2.1 aims at drawing the functional analysis of F-MAN, starting from the users’ needs.
Overview of Software Requirements
Kranjska Gora, Test plan - PI will test F-MAN tools on: - 2 types of wagons (Uacs, Himrrs) - 2 types of operation (timetable supervision.
WP4- Integration Kranjka Gora - Slovenia April 2004 National Technical University of Athens.
Octopus F-MAN FM OPM OM Standards and Norms Environment MM Wagons F2 F1 F3 Contractual data Wagons owner F4 F5 F6 F9 F7 F8 F10 F11 F12.
Caminhos de Ferro Portugueses E.P. European Datacomm NV IVU Traffic Technologies AG National Technical University of Athens Prometni Institut Ljubljana.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
EMBEDDED SOFTWARE Team victorious Team Victorious.
Application architectures
Clear Lake Country Club Membership Database Data Flow Diagrams Project Team: Trisha Drumm & Michael Phillips.
MODULE IV SWITCHED WAN.
Information storage: Introduction of database 10/7/2004 Xiangming Mu.
1 On Board Terminal  Technical characteristics  Functions  Messages  SIM requirements  Sensors for OBT  Installation.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
ANALYSIS REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Databases ? 2014, Fall Pusan National University Ki-Joune Li.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Caminhos de Ferro Portugueses E.P. European Datacomm NV IVU Traffic Technologies AG National Technical University of Athens Prometni Institut Ljubljana.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Old Town Library Group Members Tatiana Ruiz Judith Webb Paul Salvo Phase two.
Introduction Object oriented design is a method where developers think in terms of objects instead of procedures or functions. SA/SD approach is based.
BY: ANN BIJI ABRAHAM MEGHA V. K NEHA FATHIMA. DATA BASE MANAGEMENT SYSTEM IS A SOFTWARE TO MANAGE DATA BASE. It basically involves 4 operations: DEFINING.
Analysis following the update of the GSE Investment Database February 2010.
UML - Development Process 1 Software Development Process Using UML.
SAP Controlling Functionality and Implementation
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
WORKSHOP ON ACCREDITATION OF BODIES CERTIFYING MEDICAL DEVICES INT MARKET TOPIC 9 CH 8 ISO MEASUREMENT, ANALYSIS AND IMPROVEMENT INTERNAL AUDITS.
Making Sense of Service Broker Inside the Black Box.
ΑΝΝΕΧ 10 by EK. Rail Operators‘ Group (1) 1.Background F-Man Cargo operators: FS, CP, SZ. Their responsibilities: - to define their needs for a F-Man.
Powerpoint Templates Data Communication Muhammad Waseem Iqbal Lecture # 07 Spring-2016.
DEVRY CIS 339 iLab 4 Sequence, Communication, and State Diagrams Check this A+ tutorial guideline at
Database Development (8 May 2017).
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Object-oriented and Structured System Models
Software Process Activities.
Management Information System
Management Information System
Management Information System
Management Information System
Management Information System
Management Information System
A Tutorial on the Zachman Framework for Enterprise Architecture
2018, Fall Pusan National University Ki-Joune Li
Chapter 2. Protocols and Architecture
Sample Test Questions Please identify the use cases of the system that cover all the behaviors described in the system specification. Please identify.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Chapter 6: Architectural Design
"Step by Step" Guide to implement TAF TSI
Presentation transcript:

1 SCIRO - Bled /09/02 WP2 Functional Requirements and Architecture External Functional Analysis (D4) & Internal Functional Analysis (contribution to D5)

SCIRO - Bled /09/02 2 External Functional Analysis (D4) zA set of sequence diagrams has been reported in order to well understand: ythe processes where the F-Man system is supposed to be involved in, ythe roles of the external entities, ythe data exchanged. zThe following phases have been implemented: ydetermination of the external medium that constitute the environment where F-MAN is supposed to work, once it is implemented, ydetermination of the principal functions (17), ydetermination of the constraints (9), yvalidation of functions and constraints, ydetermination of the main characteristics of functions and constraints.

SCIRO - Bled /09/02 3 Internal Functional Analysis (contribution to D5) zSciro and Sigma/SNCF have performed two independent Internal Functional Analysis, starting from the same F-Man structure and from the result of D4

SCIRO - Bled /09/02 4 Internal Functional Analysis Main differences F8, F12, F13, F14 SciroSigma/SNCF zThe DPM performs delays/damages detection, each time it receives an event messages from the wagon or the OPM zThe DPM actualizes the database of future wagons location and availability zOnly in case of delay/damage, the DPM warns the AMM zThe AMM checks if the delay/damage is related to an empty/loaded or booked wagon zThe AMM informs the FM, the MM or the OM zThe DPM actualizes the database about wagon location and status taking into account information coming from the GS and the OPM zF8: The AMM analyses the database and warns about the difference of the current location and the foreseen one. In case of delay he informs the FM

SCIRO - Bled /09/02 5 Internal Functional Analysis F8 To update wagons allocation on the basis of real time data provided by the OPM and Wagons and of foreseen path and timetable (by the OPM), and to inform the FM in case of delay detection related to empty booked wagons F12 To inform the FM, the OM and the MM about damage on wagons F13 To inform the FM and the MM that wagons are arrived in workshop, taking into account event messages sent by the OPM and real time events sent by wagons F14 To update wagons allocation on the basis of the MM data about delay during maintenance in workshop and to inform the FM in case of delay detection related to booked wagons