Software engineering Module 1 -Introduction to software process Teaching unit 1 - Requirements engineering Ernesto Damiani Free University of Bozen-Bolzano.

Slides:



Advertisements
Similar presentations
© 2005 Prentice Hall13-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Advertisements

The System Development Life Cycle
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 3 – Building.
Software engineering Module 1 -Introduction to software process Teaching unit 1 – Requirements engineering Ernesto Damiani Fee University of Bozen-Bolzano.
CMPT 370 Course Project Library Information System Analysis and Design.
DEVELOPMENT OF SOFTWARE FOR SUPPORTING THE LEARNING PROCESS ACCORDING TO BOLOGNA AGREEMENTS - LESSONS LEARNED 9 th Workshop "Software Engineering Education.
Software project management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.
SWE Introduction to Software Engineering
Distributed systems Module 2 -Distributed algorithms Teaching unit 1 – basic techniques Ernesto Damiani University of Bozen Lesson 1 – Introduction.
Systems of Distributed Systems Module 2 -Distributed algorithms Teaching unit 3 – Advanced algorithms Ernesto Damiani University of Bozen Lesson 6 – Two.
Distributed systems Module 1 -Basic networking Teaching unit 1 – LAN standards Ernesto Damiani University of Bozen-Bolzano Lesson 5 – Collision management.
Software engineering Module 1 -Introduction to software process Teaching unit 1 - Requirements engineering Ernesto Damiani Free University of Bozen-Bolzano.
1 Module 1 INTRODUCTION TO DECISION ANALYSIS. 2 Introduction To Decision Analysis Learning Objectives Reasons for studying decision analysis Basic sources.
Software process management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.
Identifying needs and establishing requirements Chapter 7a.
Analysis Concepts and Principles
Fundamentals of Information Systems, Second Edition
Software project management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.
Distributed systems Module 1 -Basic networking Teaching unit 1 – LAN standards Ernesto Damiani University of Bozen-Bolzano Lesson 4 – Ethernet frame.
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen-Bolzano Lesson 1 – Component-Based.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Lesson-15 Systems Analysis What are information systems, and who are the stakeholders in the information systems game? Define systems analysis and relate.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Towards an activity-oriented and context-aware collaborative working environments Presented by: Ince T Wangsa Supervised by:
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Problem Identification
Chapter 14 Information System Development
Human Computer Interaction
VCU Information Systems Institute Advanced Delivery Methodology Courtesy of Data Management That Works.
Workflow Treatment with Coloured Petri Nets Alexandru Cicortaş Diana
Chapter 11 Analysis Concepts and Principles
Software Engineering Saeed Akhtar The University of Lahore Lecture 7 Originally shared for: mashhoood.webs.com.
Maria Grazia Pia, INFN Genova 1 User Requirements: Maria Grazia Pia Genova, 31 May 2000 their definition and application in the project Geant4-DNA.
Lecture 7: Requirements Engineering
Requirements Gathering How do we find out what we are supposed to be building?
IS2210: Systems Analysis and Systems Design and Change Twitter:
Modeling Preferences of a Group Member Farrokh Alemi, Ph.D.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2013 Lecture.
IFS310: Module 3 1/25/2007 Fact Finding Techniques.
Presentation by: Joe Casabona.  Web Apps depend on end users  Time to Market (TTM) very important in web development  Trade-off Analysis helps decide.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
(1) Introduction to Requirements and Design Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of.
Alain Thomas Overview workshop Background to the Principles Definitions The National Principles for Public Engagement What.
Teaching material for a course in Software Project Management & Software Engineering – part V.
Software Engineering Lecture # 1.
Fundamentals of Information Systems, Fifth Edition Chapter 8 Systems Development.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Requirement Engineering
Module 11: Planning and Implementing an Active Directory Infrastructure.
Requirements Gathering
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
Stakeholders in Global Requirements Engineering: Lessons Learned from Practice Written by Daniela Damian Presented by Misako Kobayashi.
PROCESS ASSESSMENT AND IMPROVEMENT. Process Assessment  A formal assessment did not seem financially feasible at the onset of the company’s process improvement.
1 Requirements Analysis Lecture # Recap of Requirements Elicitation - 1 Requirements elicitation deals with discovering requirements for a software.
The System Development Life Cycle
Systems Development Life Cycle
Requirements Engineering
Lecture on Systems Analysis
Survey Results Q
The System Development Life Cycle
Introduction To System Analysis and Design PART 2
Members: Keshava Shiva Sanjeeve Kareena
Systems Development Life Cycle
Public Management Information Systems System Analysis Thursday, August 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
Consultation with stakeholders & User participation
DiGiTech Classes offers Digital Marketing Training Center
Presentation transcript:

Software engineering Module 1 -Introduction to software process Teaching unit 1 - Requirements engineering Ernesto Damiani Free University of Bozen-Bolzano Lesson 3 – User involvement

User involvement (1) The most important stakeholders are users Users know the domain and what the system must do, but they have some problems to express them – No single user has all answers – Sometimes users have reasons not to express completely – Some difficulties may be in talks with owners – Users often do not know the technology

User involvement (2) There are some social and cultural aspects There are various technologies to manage user involvement Different levels of involvement are expected – Consultative Design – Representative Design – Consensus Design

Consultative Design Developers Power Users = information sources Tools – Interviews – Formal meetings – Election of “User liaison”

Representative Design (RD) User representatives are involved into all project decisions Classic RD techniques – Joint Application Design (JAD) – Quality Functional Deployment (QFD)

Consensus Design (CD) User Power The usage is an important part of all project decisions Classic CD techniques – Participatory Design (PD)

Management When requirements are gathered, they always must be upgraded Upgrading become RFC (Request For Change) that must be showed at the beginning of each iteration Requirements management take care of changes en route during the development FINE