F122028 – VIVAN Kourosh. Authors Universidad de Murcia Ambrosio TOVAL, Reader in Software Engineering in the Department of Computing Joaquin NICOLAS Begona.

Slides:



Advertisements
Similar presentations
Julián Valero Torrijos
Advertisements

GpiI-2C Identifying software project stages, tasks and deliverables
Pedigreed Attribute eLicitation Method (PALM) Onno Dijkstra.
NEES Project Management Workshop June 16 June 18 1 Segment 2.
Requirements engineering – seminar with a real case study Zoran Budimac.
Chapter 7 CASE Tools and Joint and Rapid Application Development.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Computer ScienceSoftware Engineering Slide 1 Team l Team Leads: Put your list of questions for Galaxy Sleuth on your web page and send me the URL l Everyone:
WKES 3202 SOFTWARE REQUIREMENTS ENGINEERING SEMESTER 1 SESSION 2004/2005.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Visual Analysis of a Moodle-based Software Engineering Course Francisco J. García Miguel Á. Conde
©2011 Rolls-Royce plc The information in this document is the property of Rolls-Royce plc and may not be copied or communicated to a third party, or used.
Identifying needs and establishing requirements Chapter 7b.
Requirement engineering for an online bookstore system
UNITED NATIONS COMMISION ON INTERNATIONAL TRADE LAW (UNCITRAL) Current issues on electronic contracting José Angelo Estrella Faria Legal Officer UNCITRAL.
Requirements Management
January 28, 2014CS410 – Software Engineering Lecture #1: Introduction 1 Welcome to CS 410 – Introduction to Software Engineering Spring 2014 Instructor:
Welcome ISO9001:2000 Foundation Workshop.
Effectively Integrating Information Technology (IT) Security into the Acquisition Process Section 5: Security Controls.
QUPER Paper Outline Yuri Sprockel. Update Unfortunate CCV date pick Cost view elaboration New QUPER PDD almost finished.
BTS330: Business Requirements Analysis using OO Lecture 5 Requirements Development: Practices and Skills.
CC20O7N - Software Engineering 1 CC2007N Software Engineering 1 Requirements Engineering Practices with Techniques.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Software Requirements Engineering CSE 305 Lecture-2.
Project Management Practices Vesa Tenhunen University of Eastern Finland LUMA Centre
Introduction To Software Component Reuse
Good Practices of Requirements Eng. Copyright, 2000 © Jerzy R. Nawrocki Requirements.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Status Report for Critical Infrastructure Protection Advisory Group
Software Safety Risk Evaluation Process Yorick Bouma, , Group III.
10/20/ The ISMS Compliance in 2009 GRC-ISMS Module for ISO Certification.
Lecture 7: Requirements Engineering
Requirements Engineering Csaba Veres. Outline What is requirements engineering? Why is it important? How can you do it (properly)?
CEN 4010 First Lecture January 9, 2006 CEN 4010 Introduction to Software Engineering Spring 2006 Instructor: Masoud Sadjadi
ENGINEERING LESSONS LEARNED AND SYSTEMS ENGINEERING APPLICATIONS Paul S. Gill and Danny Garcia, NASA Technical Standards Program Office William W. Vaughan,
Requirements Elicitation and Validation with Real World Scenes Peter Haumer, Klaus Pohl and Klaus Weidenhaupt Rens van Erk
ISO 9001 – an overview Tor Stålhane IDI / NTNU. ISO 9001 and software development ISO 9001 is a general standard – equally applicable to software development.
RUNA SEWRADJ GROUP A EXTRACTING AND MODELING PRODUCT LINE FUNCTIONAL REQUIREMENTS.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
CRAC++ Risk-Based Confidentiality Requirements Specification for Outsourced IT Systems.
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Systems Development Life Cycle
Method Engineering Fiona Gelink Group 3.  The method  Advantages of the method  Related literature  PDD  Steps of the method  References.
Requirements Engineering Requirements Elicitation Overview of Requirements Analysis.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
A Personal Data Audit Method through Requirements Engineering Thomas van Eerden.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Chapter 3: The Requirements Workflow [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada, Reno Department of Computer.
How Can the Federal Electronics Challenge (FEC) Help You? Federal Environmental Symposium June 5, 2007 Cate Berard U.S. Environmental Protection Agency.
Introduction to Software Requirement Engineering Nisa’ul Hafidhoh Teknik Informatika
DEVRY CIS 321 Week 2 Milestone 2 Check this A+ tutorial guideline at For more classes.
The prevention of fraud in land registration systems
Software Requirements
CASE Tools and Joint and Rapid Application Development
Requirement Management
Software Engineering Mujahid Rafiq.
CS 790M Project preparation (I)
Chapter 3: The Requirements Workflow
Goal, Question, and Metrics
Frequently asked questions about software engineering
Introduction to Requirements Management
IREB Foundation Level Agenda: About Me About CodeSpace About IREB
Requirements Engineering Lecture 6
CS 426 CS 791z Topics on Software Engineering
CS 426 CS 791z Topics on Software Engineering
Presentation transcript:

F – VIVAN Kourosh

Authors Universidad de Murcia Ambrosio TOVAL, Reader in Software Engineering in the Department of Computing Joaquin NICOLAS Begona MOROS, lecturer. She has a background in prototyping environment, software development and requirement engineering (RE)  Universidad Politécnica de Valencia Fernando GARCIS VIVAN Kourosh - ME 20132

Origins  CARMMA project: develop a risk analysis using MAGERIT in the Regional Information Systems and Telecommunications Office One year/ 5 analysts/ 50 stakeholders  Results Countermeasures costs could be lower if assets would be developed taking into security issue from the beginning. But MAGERIT countermeasures are linked to thread not assets. VIVAN Kourosh - ME 20133

Purpose  Method took place during elicitation and specification  Use a reused repository that contains Requirements from MAGERIT  Method focus on security of information system  Method result are: Specification documents and testing documents VIVAN Kourosh - ME 20134

Main phases 1. Requirements selection 2. Analysis and negociation 3. Documentation 4. Repository improvement 5. Validation VIVAN Kourosh - ME 20135

Create reused repository VIVAN Kourosh - ME 20136

Reused repository  Classified by domains and profiles Domains: finance, shop... Profiles: personal data law privacy, information system security…  Requirement can be parameterized or not VIVAN Kourosh - ME 20137

Requirements selection VIVAN Kourosh - ME 20138

Analysis and negotiation VIVAN Kourosh - ME 20139

Documentation VIVAN Kourosh - ME

Repository improvement & Validation VIVAN Kourosh - ME

Related litteratures  Toval, A., Nicolás, J., Moros, B., & García, F. (2002). Requirements reuse for improving information systems security: a practitioner’s approach.Requirements Engineering, 6(4),  Sindre, G., Firesmith, D. G., & Opdahl, A. L. (2003, June). A reuse- based approach to determining security requirements. In Proceedings of the 9th international workshop on requirements engineering: foundation for software quality (REFSQ’03), Klagenfurt, Austria.  Gutiérrez, C., Moros, B., Toval, A., Fernández-Medina, E., & Piattini, M. (2005, August). Security requirements for web services based on SIREN. In Symposium on Requirements Engineering for Information Security, Paris, France.  Tsang, V. W. S. Towards Analysis of Templates for Security Requirements(Doctoral dissertation, University of Auckland). VIVAN Kourosh - ME

PDD VIVAN Kourosh - ME

Deliverables VIVAN Kourosh - ME

Exemple  SyRS S42. The maintainability contract of the electronic equipment shall include a clause enforcing the supplier to make a commitment to solve any failure in less than [time in minutes]. SyRS: System Requirement Specification document 3.5.2: Section number 3.5 System attributes S42 : Security requirement 42 IEEE 1233 standard VIVAN Kourosh - ME

VIVAN Kourosh - ME