ΑΝΝΕΧ 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.

Slides:



Advertisements
Similar presentations
What is Test Director? Test Director is a test management tool
Advertisements

Lecture 9: Implementation Dr Valentina Plekhanova University of Sunderland, UK.
Enabling Access to Sound Archives through Integration, Enrichment and Retrieval WP1. Project Management.
UGDIE PROJECT MEETING Athens September WP6 – Assessment and Evaluation  Evaluation Results  Deliverable D 13 (first release issued and delivered.
CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
Figure 6-1: Transport Request Data Entities: CS: Customer OM: Order manager OPM: Operational manager FM: Fleet Manager MM: Maintenance manager OBT: On.
ΑΝΝΕΧ 6 by SCIRO. WP5 Testing and Verification Objectives To verify that the prototypes fulfil the functional specification set in WP2 To produce possible.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
ΑΝΝΕΧ 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.
Illinois Institute of Technology
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.
UGDIE KICK-OFF MEETING F-MAN 1 ΑΝΝΕΧ 1-A by UGDIE.
Kranjska Gora, Test plan - PI will test F-MAN tools on: - 2 types of wagons (Uacs, Himrrs) - 2 types of operation (timetable supervision.
1 SCIRO - Bled /09/02 WP2 Functional Requirements and Architecture External Functional Analysis (D4) & Internal Functional Analysis (contribution.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Systems Analysis and Design in a Changing World, 6th Edition
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
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.
Structure Commander Technical Presentation. Copyright (C) MCS 2013, All rights reserved. 2 STRUCTURE COMMANDER Introduction Product Overview.
Effective Methods for Software and Systems Integration
On-site construction employees’ occupational safety in Europe the enhancement and strengthening of their Health and Safety skills development by means.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Systems Analysis and Design
1 On Board Terminal  Technical characteristics  Functions  Messages  SIM requirements  Sensors for OBT  Installation.
Caminhos de Ferro Portugueses E.P. European Datacomm NV IVU Traffic Technologies AG National Technical University of Athens Prometni Institut Ljubljana.
Software System Engineering: A tutorial
SQA System Overview Chapter 4. Where we have been so far, Where we are going Where do software errors come from? What is quality? How can quality be measured?
Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin Clients Facilities Management Don Anderson Rick Klein.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Project Schedule PLAN IT!. Project Schedule Project Schedule is based on Work Breakdown Structure (WBS) Define the WBS correctly or the Project Schedule.
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
Course Conclusion. Agenda Summing up by Tom Handing over to Ellen Your presentations Typo3 // css stuff Information about exam.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Manufacturing Plant maintenance Materials management Quality management.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Purpose To develop and deploy a Metro Bus Tracking System (MBTS) Two main goals: – Provide the metro administration a tool to track and report on the status.
PROGRAM MANAGEMENT MODULE 2 Dr. Nicole Fitzhugh Professional School Counselor Berwyn Heights Elementary.
How the NCSX Project Does Business
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
InfoCentre May InfoCentre Overview InfoCentre used in over 90 million sq. ft. Web-based building management services for:  Workflow management.
LEONARDO DA VINCI PROGRAMME PL/04/B/F/PP – _________________________________________________________________________ European Curricula for Economic.
System Analysis and Design Copyright © Genetic Computer School 2007 SAD14-1 CHAPTER OVERVIEW  Overview Of System Maintenance  Tasks Performed During.
The Earth System Grid (ESG) A Fault Monitoring System for ESG Components DOE SciDAC ESG Project Review Argonne National Laboratory, Illinois May 8-9, 2003.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
Development Project Management Jim Kowalkowski. Outline Planning and managing software development – Definitions – Organizing schedule and work (overall.
ΑΝΝΕΧ 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.
Software Configuration Management
World Health Organization
Software Verification and Validation
Requirements Analysis Scenes
Chapter 18 Maintaining Information Systems
IEEE Std 1074: Standard for Software Lifecycle
V-Shaped SDLC Model Lecture-6.
Moving Students Between Sessions
Software Prototyping Animating and demonstrating system requirements.
Applied Software Implementation & Testing
SDLC Model A framework that describes the activities performed at each stage of a software development project.
Debrief Case Study Setting
Fundamentals of Human Computer Interaction (HCI)
Sample Test Questions Please identify the use cases of the system that cover all the behaviors described in the system specification. Please identify.
The development process
Moving Students Between Sessions
Human Computer Interaction Lecture 14 HCI in Software Process
Reflect the shapes in the mirror lines
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

ΑΝΝΕΧ 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 set in WP1: The functional analysis will be drawn using a top-down approach A suitable formal tool is provided by AFNOR X

The norms will be used to: Define the main functions of the overall system. Characterise the functions that will be the basis for the definition of the system and sub-systems architectures. Check the formal correctness of system requirements and their reflections on subsystems and components. Draw the verification plan The formal tool

Task 3.1 Tracking Module Development Objectives:  Fulfil the required updating rate of the position and wagon status data  Reply to non scheduled queries by the control centre  OBT power supply lifetime should be comparable with maintenance period of railcars

Task 3.1 Tracking Module Development

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2025 SlidePlayer.com. Inc. All rights reserved.