Enviar pesquisa
Carregar
Ch7
•
Transferir como PPT, PDF
•
2 gostaram
•
1,106 visualizações
P
phanleson
Seguir
Negócios
Turismo
Denunciar
Compartilhar
Denunciar
Compartilhar
1 de 52
Baixar agora
Recomendados
REQUIREMENT ENGINEERING: HOW TO MAKE IT COMPLETE AND CORRECT
REQUIREMENT ENGINEERING: HOW TO MAKE IT COMPLETE AND CORRECT
AM Publications,India
software engineering
software engineering
Snow Queenzz
Software engineering Unit-2
Software engineering Unit-2
Samura Daniel
Software Development Process - REQUIREMENTS ANALYSIS / ANALYSIS OF TECHNICAL...
Software Development Process - REQUIREMENTS ANALYSIS / ANALYSIS OF TECHNICAL...
Mark John Lado, MIT
Requirements Engineering (CS 5032 2012)
Requirements Engineering (CS 5032 2012)
Ian Sommerville
An overview of software requirements engineering
An overview of software requirements engineering
Ian Sommerville
Business analyst
Business analyst
Santosh Pattanshetty
Requirements Engineering for LSCITS
Requirements Engineering for LSCITS
Ian Sommerville
Recomendados
REQUIREMENT ENGINEERING: HOW TO MAKE IT COMPLETE AND CORRECT
REQUIREMENT ENGINEERING: HOW TO MAKE IT COMPLETE AND CORRECT
AM Publications,India
software engineering
software engineering
Snow Queenzz
Software engineering Unit-2
Software engineering Unit-2
Samura Daniel
Software Development Process - REQUIREMENTS ANALYSIS / ANALYSIS OF TECHNICAL...
Software Development Process - REQUIREMENTS ANALYSIS / ANALYSIS OF TECHNICAL...
Mark John Lado, MIT
Requirements Engineering (CS 5032 2012)
Requirements Engineering (CS 5032 2012)
Ian Sommerville
An overview of software requirements engineering
An overview of software requirements engineering
Ian Sommerville
Business analyst
Business analyst
Santosh Pattanshetty
Requirements Engineering for LSCITS
Requirements Engineering for LSCITS
Ian Sommerville
Requirements Engineering - Lecture 1.pdf
Requirements Engineering - Lecture 1.pdf
Flavia Tembo Kambale
Good Practices For Developing User Requirements
Good Practices For Developing User Requirements
nkaur
Requirement Analysis & Specification sharbani bhattacharya
Requirement Analysis & Specification sharbani bhattacharya
Sharbani Bhattacharya
Software requirements engineering problems and challenges erp implementation ...
Software requirements engineering problems and challenges erp implementation ...
Dr. Hamdan Al-Sabri
Reqdet
Reqdet
Fajar Baskoro
software requirement
software requirement
nimmik4u
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
IRJET Journal
4 sdlc and stlc
4 sdlc and stlc
Chandra Maddigapu
Requirements analysis
Requirements analysis
asimnawaz54
Business Analyst Overview
Business Analyst Overview
Salil Vaidya
Ch07-Moving into Design
Ch07-Moving into Design
Fajar Baskoro
Software requirements and analysis
Software requirements and analysis
Phanindra Cherukuri
System Requirements
System Requirements
Alaa Al Nouri
415 quiz1 answers
415 quiz1 answers
IIUM
Ch 2 types of reqirement
Ch 2 types of reqirement
Fish Abe
Requirements validation - requirements engineering
Requirements validation - requirements engineering
Ra'Fat Al-Msie'deen
Requirements engineering challenges
Requirements engineering challenges
sommerville-videos
Turizon Business Analysis Services
Turizon Business Analysis Services
Sanand Sule
Se lec-uosl-8
Se lec-uosl-8
Shahzad Zaman
Requirement analysis
Requirement analysis
Jaipal Dhobale
Mobile Security - Wireless hacking
Mobile Security - Wireless hacking
phanleson
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
phanleson
Mais conteúdo relacionado
Mais procurados
Requirements Engineering - Lecture 1.pdf
Requirements Engineering - Lecture 1.pdf
Flavia Tembo Kambale
Good Practices For Developing User Requirements
Good Practices For Developing User Requirements
nkaur
Requirement Analysis & Specification sharbani bhattacharya
Requirement Analysis & Specification sharbani bhattacharya
Sharbani Bhattacharya
Software requirements engineering problems and challenges erp implementation ...
Software requirements engineering problems and challenges erp implementation ...
Dr. Hamdan Al-Sabri
Reqdet
Reqdet
Fajar Baskoro
software requirement
software requirement
nimmik4u
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
IRJET Journal
4 sdlc and stlc
4 sdlc and stlc
Chandra Maddigapu
Requirements analysis
Requirements analysis
asimnawaz54
Business Analyst Overview
Business Analyst Overview
Salil Vaidya
Ch07-Moving into Design
Ch07-Moving into Design
Fajar Baskoro
Software requirements and analysis
Software requirements and analysis
Phanindra Cherukuri
System Requirements
System Requirements
Alaa Al Nouri
415 quiz1 answers
415 quiz1 answers
IIUM
Ch 2 types of reqirement
Ch 2 types of reqirement
Fish Abe
Requirements validation - requirements engineering
Requirements validation - requirements engineering
Ra'Fat Al-Msie'deen
Requirements engineering challenges
Requirements engineering challenges
sommerville-videos
Turizon Business Analysis Services
Turizon Business Analysis Services
Sanand Sule
Se lec-uosl-8
Se lec-uosl-8
Shahzad Zaman
Requirement analysis
Requirement analysis
Jaipal Dhobale
Mais procurados
(20)
Requirements Engineering - Lecture 1.pdf
Requirements Engineering - Lecture 1.pdf
Good Practices For Developing User Requirements
Good Practices For Developing User Requirements
Requirement Analysis & Specification sharbani bhattacharya
Requirement Analysis & Specification sharbani bhattacharya
Software requirements engineering problems and challenges erp implementation ...
Software requirements engineering problems and challenges erp implementation ...
Reqdet
Reqdet
software requirement
software requirement
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...
4 sdlc and stlc
4 sdlc and stlc
Requirements analysis
Requirements analysis
Business Analyst Overview
Business Analyst Overview
Ch07-Moving into Design
Ch07-Moving into Design
Software requirements and analysis
Software requirements and analysis
System Requirements
System Requirements
415 quiz1 answers
415 quiz1 answers
Ch 2 types of reqirement
Ch 2 types of reqirement
Requirements validation - requirements engineering
Requirements validation - requirements engineering
Requirements engineering challenges
Requirements engineering challenges
Turizon Business Analysis Services
Turizon Business Analysis Services
Se lec-uosl-8
Se lec-uosl-8
Requirement analysis
Requirement analysis
Destaque
Mobile Security - Wireless hacking
Mobile Security - Wireless hacking
phanleson
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
phanleson
Learning spark ch05 - Loading and Saving Your Data
Learning spark ch05 - Loading and Saving Your Data
phanleson
E-Commerce Security - Application attacks - Server Attacks
E-Commerce Security - Application attacks - Server Attacks
phanleson
Firewall - Network Defense in Depth Firewalls
Firewall - Network Defense in Depth Firewalls
phanleson
Authentication in wireless - Security in Wireless Protocols
Authentication in wireless - Security in Wireless Protocols
phanleson
Destaque
(6)
Mobile Security - Wireless hacking
Mobile Security - Wireless hacking
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch05 - Loading and Saving Your Data
Learning spark ch05 - Loading and Saving Your Data
E-Commerce Security - Application attacks - Server Attacks
E-Commerce Security - Application attacks - Server Attacks
Firewall - Network Defense in Depth Firewalls
Firewall - Network Defense in Depth Firewalls
Authentication in wireless - Security in Wireless Protocols
Authentication in wireless - Security in Wireless Protocols
Semelhante a Ch7
Software Engineering - Ch7
Software Engineering - Ch7
Siddharth Ayer
Lecture10.ppt
Lecture10.ppt
WasekaPropertyportal
Ch6
Ch6
phanleson
software recq.ppt
software recq.ppt
karinaabyys
Unit2 Software engineering UPTU
Unit2 Software engineering UPTU
Mohammad Faizan
Software Engineering - Ch6
Software Engineering - Ch6
Siddharth Ayer
Reqmt_Engn.ppt
Reqmt_Engn.ppt
DrCMeenakshiVISTAS
Wireless communication.ppt
Wireless communication.ppt
ssuser183d67
Lecture_three_Requirements_analysis.pptx
Lecture_three_Requirements_analysis.pptx
GracePeter10
SE - Lecture 5 - Requirements Engineering.pptx
SE - Lecture 5 - Requirements Engineering.pptx
TangZhiSiang
Requirement Engineering.pdf
Requirement Engineering.pdf
Muhammad Imran
SRE.pptx
SRE.pptx
KalsoomBajwa
5. SE RequirementEngineering task.ppt
5. SE RequirementEngineering task.ppt
HaiderAli252366
Software Requirements.pptx
Software Requirements.pptx
Prem Chandrakar
3. 1 req elicitation
3. 1 req elicitation
Ashenafi Workie
Requirementengg
Requirementengg
Prof.Dharmishtha R. Chaudhari
Lecture 8 & 9.pdf
Lecture 8 & 9.pdf
RaoShahid10
Requirements engineering
Requirements engineering
Sutha31
Unit 2
Unit 2
Jignesh Kariya
Software engg. pressman_ch-6 & 7
Software engg. pressman_ch-6 & 7
Dhairya Joshi
Semelhante a Ch7
(20)
Software Engineering - Ch7
Software Engineering - Ch7
Lecture10.ppt
Lecture10.ppt
Ch6
Ch6
software recq.ppt
software recq.ppt
Unit2 Software engineering UPTU
Unit2 Software engineering UPTU
Software Engineering - Ch6
Software Engineering - Ch6
Reqmt_Engn.ppt
Reqmt_Engn.ppt
Wireless communication.ppt
Wireless communication.ppt
Lecture_three_Requirements_analysis.pptx
Lecture_three_Requirements_analysis.pptx
SE - Lecture 5 - Requirements Engineering.pptx
SE - Lecture 5 - Requirements Engineering.pptx
Requirement Engineering.pdf
Requirement Engineering.pdf
SRE.pptx
SRE.pptx
5. SE RequirementEngineering task.ppt
5. SE RequirementEngineering task.ppt
Software Requirements.pptx
Software Requirements.pptx
3. 1 req elicitation
3. 1 req elicitation
Requirementengg
Requirementengg
Lecture 8 & 9.pdf
Lecture 8 & 9.pdf
Requirements engineering
Requirements engineering
Unit 2
Unit 2
Software engg. pressman_ch-6 & 7
Software engg. pressman_ch-6 & 7
Mais de phanleson
Hacking web applications
Hacking web applications
phanleson
HBase In Action - Chapter 04: HBase table design
HBase In Action - Chapter 04: HBase table design
phanleson
HBase In Action - Chapter 10 - Operations
HBase In Action - Chapter 10 - Operations
phanleson
Hbase in action - Chapter 09: Deploying HBase
Hbase in action - Chapter 09: Deploying HBase
phanleson
Learning spark ch11 - Machine Learning with MLlib
Learning spark ch11 - Machine Learning with MLlib
phanleson
Learning spark ch10 - Spark Streaming
Learning spark ch10 - Spark Streaming
phanleson
Learning spark ch09 - Spark SQL
Learning spark ch09 - Spark SQL
phanleson
Learning spark ch07 - Running on a Cluster
Learning spark ch07 - Running on a Cluster
phanleson
Learning spark ch06 - Advanced Spark Programming
Learning spark ch06 - Advanced Spark Programming
phanleson
Learning spark ch04 - Working with Key/Value Pairs
Learning spark ch04 - Working with Key/Value Pairs
phanleson
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
phanleson
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
phanleson
Lecture 1 - Getting to know XML
Lecture 1 - Getting to know XML
phanleson
Lecture 4 - Adding XTHML for the Web
Lecture 4 - Adding XTHML for the Web
phanleson
Lecture 2 - Using XML for Many Purposes
Lecture 2 - Using XML for Many Purposes
phanleson
SOA Course - SOA governance - Lecture 19
SOA Course - SOA governance - Lecture 19
phanleson
Lecture 18 - Model-Driven Service Development
Lecture 18 - Model-Driven Service Development
phanleson
Lecture 15 - Technical Details
Lecture 15 - Technical Details
phanleson
Lecture 10 - Message Exchange Patterns
Lecture 10 - Message Exchange Patterns
phanleson
Lecture 9 - SOA in Context
Lecture 9 - SOA in Context
phanleson
Mais de phanleson
(20)
Hacking web applications
Hacking web applications
HBase In Action - Chapter 04: HBase table design
HBase In Action - Chapter 04: HBase table design
HBase In Action - Chapter 10 - Operations
HBase In Action - Chapter 10 - Operations
Hbase in action - Chapter 09: Deploying HBase
Hbase in action - Chapter 09: Deploying HBase
Learning spark ch11 - Machine Learning with MLlib
Learning spark ch11 - Machine Learning with MLlib
Learning spark ch10 - Spark Streaming
Learning spark ch10 - Spark Streaming
Learning spark ch09 - Spark SQL
Learning spark ch09 - Spark SQL
Learning spark ch07 - Running on a Cluster
Learning spark ch07 - Running on a Cluster
Learning spark ch06 - Advanced Spark Programming
Learning spark ch06 - Advanced Spark Programming
Learning spark ch04 - Working with Key/Value Pairs
Learning spark ch04 - Working with Key/Value Pairs
Learning spark ch01 - Introduction to Data Analysis with Spark
Learning spark ch01 - Introduction to Data Analysis with Spark
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
Hướng Dẫn Đăng Ký LibertaGia - A guide and introduciton about Libertagia
Lecture 1 - Getting to know XML
Lecture 1 - Getting to know XML
Lecture 4 - Adding XTHML for the Web
Lecture 4 - Adding XTHML for the Web
Lecture 2 - Using XML for Many Purposes
Lecture 2 - Using XML for Many Purposes
SOA Course - SOA governance - Lecture 19
SOA Course - SOA governance - Lecture 19
Lecture 18 - Model-Driven Service Development
Lecture 18 - Model-Driven Service Development
Lecture 15 - Technical Details
Lecture 15 - Technical Details
Lecture 10 - Message Exchange Patterns
Lecture 10 - Message Exchange Patterns
Lecture 9 - SOA in Context
Lecture 9 - SOA in Context
Último
Independent Call Girls Andheri Nightlaila 9967584737
Independent Call Girls Andheri Nightlaila 9967584737
Riya Pathan
Global Scenario On Sustainable and Resilient Coconut Industry by Dr. Jelfina...
Global Scenario On Sustainable and Resilient Coconut Industry by Dr. Jelfina...
ictsugar
Pitch Deck Teardown: Geodesic.Life's $500k Pre-seed deck
Pitch Deck Teardown: Geodesic.Life's $500k Pre-seed deck
HajeJanKamps
Guide Complete Set of Residential Architectural Drawings PDF
Guide Complete Set of Residential Architectural Drawings PDF
Chandresh Chudasama
8447779800, Low rate Call girls in Uttam Nagar Delhi NCR
8447779800, Low rate Call girls in Uttam Nagar Delhi NCR
ashishs7044
Unlocking the Future: Explore Web 3.0 Workshop to Start Earning Today!
Unlocking the Future: Explore Web 3.0 Workshop to Start Earning Today!
Doge Mining Website
Fordham -How effective decision-making is within the IT department - Analysis...
Fordham -How effective decision-making is within the IT department - Analysis...
Peter Ward
FULL ENJOY Call girls in Paharganj Delhi | 8377087607
FULL ENJOY Call girls in Paharganj Delhi | 8377087607
dollysharma2066
Traction part 2 - EOS Model JAX Bridges.
Traction part 2 - EOS Model JAX Bridges.
Anamaria Contreras
8447779800, Low rate Call girls in Saket Delhi NCR
8447779800, Low rate Call girls in Saket Delhi NCR
ashishs7044
Investment in The Coconut Industry by Nancy Cheruiyot
Investment in The Coconut Industry by Nancy Cheruiyot
ictsugar
NewBase 19 April 2024 Energy News issue - 1717 by Khaled Al Awadi.pdf
NewBase 19 April 2024 Energy News issue - 1717 by Khaled Al Awadi.pdf
Khaled Al Awadi
The-Ethical-issues-ghhhhhhhhjof-Byjus.pptx
The-Ethical-issues-ghhhhhhhhjof-Byjus.pptx
mbikashkanyari
Call Us ➥9319373153▻Call Girls In North Goa
Call Us ➥9319373153▻Call Girls In North Goa
Call girls in Goa, +91 9319373153 Escort Service in North Goa
Church Building Grants To Assist With New Construction, Additions, And Restor...
Church Building Grants To Assist With New Construction, Additions, And Restor...
Americas Got Grants
Cybersecurity Awareness Training Presentation v2024.03
Cybersecurity Awareness Training Presentation v2024.03
DallasHaselhorst
International Business Environments and Operations 16th Global Edition test b...
International Business Environments and Operations 16th Global Edition test b...
ssuserf63bd7
Annual General Meeting Presentation Slides
Annual General Meeting Presentation Slides
KeppelCorporation
Financial-Statement-Analysis-of-Coca-cola-Company.pptx
Financial-Statement-Analysis-of-Coca-cola-Company.pptx
saniyaimamuddin
Cyber Security Training in Office Environment
Cyber Security Training in Office Environment
elijahj01012
Último
(20)
Independent Call Girls Andheri Nightlaila 9967584737
Independent Call Girls Andheri Nightlaila 9967584737
Global Scenario On Sustainable and Resilient Coconut Industry by Dr. Jelfina...
Global Scenario On Sustainable and Resilient Coconut Industry by Dr. Jelfina...
Pitch Deck Teardown: Geodesic.Life's $500k Pre-seed deck
Pitch Deck Teardown: Geodesic.Life's $500k Pre-seed deck
Guide Complete Set of Residential Architectural Drawings PDF
Guide Complete Set of Residential Architectural Drawings PDF
8447779800, Low rate Call girls in Uttam Nagar Delhi NCR
8447779800, Low rate Call girls in Uttam Nagar Delhi NCR
Unlocking the Future: Explore Web 3.0 Workshop to Start Earning Today!
Unlocking the Future: Explore Web 3.0 Workshop to Start Earning Today!
Fordham -How effective decision-making is within the IT department - Analysis...
Fordham -How effective decision-making is within the IT department - Analysis...
FULL ENJOY Call girls in Paharganj Delhi | 8377087607
FULL ENJOY Call girls in Paharganj Delhi | 8377087607
Traction part 2 - EOS Model JAX Bridges.
Traction part 2 - EOS Model JAX Bridges.
8447779800, Low rate Call girls in Saket Delhi NCR
8447779800, Low rate Call girls in Saket Delhi NCR
Investment in The Coconut Industry by Nancy Cheruiyot
Investment in The Coconut Industry by Nancy Cheruiyot
NewBase 19 April 2024 Energy News issue - 1717 by Khaled Al Awadi.pdf
NewBase 19 April 2024 Energy News issue - 1717 by Khaled Al Awadi.pdf
The-Ethical-issues-ghhhhhhhhjof-Byjus.pptx
The-Ethical-issues-ghhhhhhhhjof-Byjus.pptx
Call Us ➥9319373153▻Call Girls In North Goa
Call Us ➥9319373153▻Call Girls In North Goa
Church Building Grants To Assist With New Construction, Additions, And Restor...
Church Building Grants To Assist With New Construction, Additions, And Restor...
Cybersecurity Awareness Training Presentation v2024.03
Cybersecurity Awareness Training Presentation v2024.03
International Business Environments and Operations 16th Global Edition test b...
International Business Environments and Operations 16th Global Edition test b...
Annual General Meeting Presentation Slides
Annual General Meeting Presentation Slides
Financial-Statement-Analysis-of-Coca-cola-Company.pptx
Financial-Statement-Analysis-of-Coca-cola-Company.pptx
Cyber Security Training in Office Environment
Cyber Security Training in Office Environment
Ch7
1.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes
2.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 2 Objectives To describe the principal requirements engineering activities and their relationships To introduce techniques for requirements elicitation and analysis To describe requirements validation and the role of requirements reviews To discuss the role of requirements management in support of other requirements engineering processes
3.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 3 Topics covered Feasibility studies Requirements elicitation and analysis Requirements validation Requirements management
4.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 4 Requirements engineering processes The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements. However, there are a number of generic activities common to all processes • Requirements elicitation; • Requirements analysis; • Requirements validation; • Requirements management.
5.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 5 The requirements engineering process FeasibilistudyRequiremenelicitaanalysisRequiemespecRequemvalFeasibilireport SystemmodeUserrequRequemdo
6.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 6 Requirements engineering Requspeci RequvalidRequiremeelicitation System respecificamodelin Systemrequiremeelicitation User reqspecific Userrequiremelicitatio Businessspecific PrototFeasibilstudy ReviewSystem requdocume
7.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 7 Feasibility studies A feasibility study decides whether or not the proposed system is worthwhile. A short focused study that checks • If the system contributes to organisational objectives; • If the system can be engineered using current technology and within budget; • If the system can be integrated with other systems that are used.
8.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 8 Feasibility study implementation Based on information assessment (what is required), information collection and report writing. Questions for people in the organisation • What if the system wasn’t implemented? • What are current process problems? • How will the proposed system help? • What will be the integration problems? • Is new technology needed? What skills? • What facilities must be supported by the proposed system?
9.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 9 Elicitation and analysis Sometimes called requirements elicitation or requirements discovery. Involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system’s operational constraints. May involve end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called stakeholders.
10.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 10 Problems of requirements analysis Stakeholders don’t know what they really want. Stakeholders express requirements in their own terms. Different stakeholders may have conflicting requirements. Organisational and political factors may influence the system requirements. The requirements change during the analysis process. New stakeholders may emerge and the business environment change.
11.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 11 The requirements spiral RequiremclassificatorganisatiRequirprioritinegoti RequirdocumRequiremdiscovery
12.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 12 Process activities Requirements discovery • Interacting with stakeholders to discover their requirements. Domain requirements are also discovered at this stage. Requirements classification and organisation • Groups related requirements and organises them into coherent clusters. Prioritisation and negotiation • Prioritising requirements and resolving requirements conflicts. Requirements documentation • Requirements are documented and input into the next round of the spiral.
13.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 13 Requirements discovery The process of gathering information about the proposed and existing systems and distilling the user and system requirements from this information. Sources of information include documentation, system stakeholders and the specifications of similar systems.
14.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 14 ATM stakeholders Bank customers Representatives of other banks Bank managers Counter staff Database administrators Security managers Marketing department Hardware and software maintenance engineers Banking regulators
15.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 15 Viewpoints Viewpoints are a way of structuring the requirements to represent the perspectives of different stakeholders. Stakeholders may be classified under different viewpoints. This multi-perspective analysis is important as there is no single correct way to analyse system requirements.
16.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 16 Types of viewpoint Interactor viewpoints • People or other systems that interact directly with the system. In an ATM, the customer’s and the account database are interactor VPs. Indirect viewpoints • Stakeholders who do not use the system themselves but who influence the requirements. In an ATM, management and security staff are indirect viewpoints. Domain viewpoints • Domain characteristics and constraints that influence the requirements. In an ATM, an example would be standards for inter-bank communications.
17.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 17 Viewpoint identification Identify viewpoints using • Providers and receivers of system services; • Systems that interact directly with the system being specified; • Regulations and standards; • Sources of business and non-functional requirements. • Engineers who have to develop and maintain the system; • Marketing and other business viewpoints.
18.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 18 LIBSYS viewpoint hierarchy ArticleprovideFinanceLibrarymanagerLibrstaffUsersInteraIndirectAll V CsyUIstan Do ExternStaffStudentsCatSystemman
19.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 19 Interviewing In formal or informal interviewing, the RE team puts questions to stakeholders about the system that they use and the system to be developed. There are two types of interview • Closed interviews where a pre-defined set of questions are answered. • Open interviews where there is no pre-defined agenda and a range of issues are explored with stakeholders.
20.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 20 Interviews in practice Normally a mix of closed and open-ended interviewing. Interviews are good for getting an overall understanding of what stakeholders do and how they might interact with the system. Interviews are not good for understanding domain requirements • Requirements engineers cannot understand specific domain terminology; • Some domain knowledge is so familiar that people find it hard to articulate or think that it isn’t worth articulating.
21.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 21 Effective interviewers Interviewers should be open-minded, willing to listen to stakeholders and should not have pre-conceived ideas about the requirements. They should prompt the interviewee with a question or a proposal and should not simply expect them to respond to a question such as ‘what do you want’.
22.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 22 Scenarios Scenarios are real-life examples of how a system can be used. They should include • A description of the starting situation; • A description of the normal flow of events; • A description of what can go wrong; • Information about other concurrent activities; • A description of the state when the scenario finishes.
23.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 23 LIBSYS scenario (1) Initial assumption: The user has logged on to the LIBSYS system and has located the journal containing the copy of the article. Normal: The user selects the article to be copied. He or she is then prompted by the system to ei ther provide subscriber information for the journal or to indicate how they will pay for the article. Alternative payment methods are by credit card or by quoting an organisational account number. The user is then asked to fill in a copyright form that maintains details of the transaction and they then submit this to the LIBSYS system. The copyright form is checked and, if OK, the PDF version of the article is downloaded to the LIBSYS working area on the user’s computer and the user is informed that it is available. The user is asked to select a printer and a copy of the article is printed. If the article has been flagged as ‘print-only’ it is deleted from the user’s system once the user has confirmed that printing is complete.
24.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 24 LIBSYS scenario (2) What can go wrong: The user may fail to fill in the copyright form correctly. In this case, the form should be re-presented to the user for correction. If the resubmitted form is still incorrect then the user’s request for the article is rejected. The payment may be rejected by the system. The user’s request for the article is rejected. The article download may fail. Retry until successful or the user terminates the session. It may not be possible to print the article. If the article is not flagged as ‘print-only’ then it is held in the LIBSYS workspace. Otherwise, the article is deleted and the user’s account credited with the cost of the article. Other activities: Simultaneous downloads of other articles. System state on completion: User is logged on. The downloaded article has been deleted from LIBSYS workspace if it has been flagged as print-only.
25.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 25 Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself. A set of use cases should describe all possible interactions with the system. Sequence diagrams may be used to add detail to use-cases by showing the sequence of event processing in the system.
26.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 26 Article printing use-case Atic
27.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 27 LIBSYS use cases ArticleArticle UserSuppliCatal LibraryUserLibSta
28.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 28 Article printing Useritem:Articlecopyrighorm:Formrequestcomplete myWorkspaWorkspamyPrPrintrrequestreturncopyrighdeliverarticle OKprintsendconfirinformdelete
29.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 29 Print article sequence Useritem:Articlecopyrigorm:Formrequestcomple myWorkspWorkspmyPPrinrrequestreturncopyrigdeliverarticle Oprintsendconfinformdelete
30.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 30 Social and organisational factors Software systems are used in a social and organisational context. This can influence or even dominate the system requirements. Social and organisational factors are not a single viewpoint but are influences on all viewpoints. Good analysts must be sensitive to these factors but currently no systematic way to tackle their analysis.
31.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 31 Ethnography A social scientists spends a considerable time observing and analysing how people actually work. People do not have to explain or articulate their work. Social and organisational factors of importance may be observed. Ethnographic studies have shown that work is usually richer and more complex than suggested by simple system models.
32.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 32 Focused ethnography Developed in a project studying the air traffic control process Combines ethnography with prototyping Prototype development results in unanswered questions which focus the ethnographic analysis. The problem with ethnography is that it studies existing practices which may have some historical basis which is no longer relevant.
33.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 33 Ethnography and prototyping EthnographicanalysisDebriefmeetFocuethngraphyProtevaltiGenerdevelopmSystprotoypi
34.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 34 Scope of ethnography Requirements that are derived from the way that people actually work rather than the way I which process definitions suggest that they ought to work. Requirements that are derived from cooperation and awareness of other people’s activities.
35.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 35 Requirements validation Concerned with demonstrating that the requirements define the system that the customer really wants. Requirements error costs are high so validation is very important • Fixing a requirements error after delivery may cost up to 100 times the cost of fixing an implementation error.
36.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 36 Requirements checking Validity. Does the system provide the functions which best support the customer’s needs? Consistency. Are there any requirements conflicts? Completeness. Are all functions required by the customer included? Realism. Can the requirements be implemented given available budget and technology Verifiability. Can the requirements be checked?
37.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 37 Requirements validation techniques Requirements reviews • Systematic manual analysis of the requirements. Prototyping • Using an executable model of the system to check requirements. Covered in Chapter 17. Test-case generation • Developing tests for requirements to check testability.
38.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 38 Requirements reviews Regular reviews should be held while the requirements definition is being formulated. Both client and contractor staff should be involved in reviews. Reviews may be formal (with completed documents) or informal. Good communications between developers, customers and users can resolve problems at an early stage.
39.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 39 Review checks Verifiability. Is the requirement realistically testable? Comprehensibility. Is the requirement properly understood? Traceability. Is the origin of the requirement clearly stated? Adaptability. Can the requirement be changed without a large impact on other requirements?
40.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 40 Requirements management Requirements management is the process of managing changing requirements during the requirements engineering process and system development. Requirements are inevitably incomplete and inconsistent • New requirements emerge during the process as business needs change and a better understanding of the system is developed; • Different viewpoints have different requirements and these are often contradictory.
41.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 41 Requirements change The priority of requirements from different viewpoints changes during the development process. System customers may specify requirements from a business perspective that conflict with end-user requirements. The business and technical environment of the system changes during its development.
42.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 42 Requirements evolution Tim ChundofproblemInitiaunderofproblemChreqemInitiarequiremen
43.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 43 Enduring and volatile requirements Enduring requirements. Stable requirements derived from the core activity of the customer organisation. E.g. a hospital will always have doctors, nurses, etc. May be derived from domain models Volatile requirements. Requirements which change during development or when the system is in use. In a hospital, requirements derived from health-care policy
44.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 44 Requirements classification Requirement Type Description Mutable requirements Requirements that change because of changes to the environment in which the organisation is operating. For example, in hospital systems, the funding of patient care may change and thus require different treatment information to be collected. Emergent requirements Requirements that emerge as the customer's understanding of the system develops during the system development. The design process may reveal new emergent requirements. Consequential requirements Requirements that result from the introduction of the computer system. Introducing the computer system may change the organisations processes and open up new ways of working which generate new system requirements Compatibility requirements Requirements that depend on the particular systems or business processes within an organisation. As these change, the compatibility requirements on the commissioned or delivered system may also have to evolve.
45.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 45 Requirements management planning During the requirements engineering process, you have to plan: • Requirements identification • How requirements are individually identified; • A change management process • The process followed when analysing a requirements change; • Traceability policies • The amount of information about requirements relationships that is maintained; • CASE tool support • The tool support required to help manage requirements change;
46.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 46 Traceability Traceability is concerned with the relationships between requirements, their sources and the system design Source traceability • Links from requirements to stakeholders who proposed these requirements; Requirements traceability • Links between dependent requirements; Design traceability • Links from the requirements to the design;
47.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 47 A traceability matrix
48.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 48 CASE tool support Requirements storage • Requirements should be managed in a secure, managed data store. Change management • The process of change management is a workflow process whose stages can be defined and information flow between these stages partially automated. Traceability management • Automated retrieval of the links between requirements.
49.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 49 Requirements change management Should apply to all proposed changes to the requirements. Principal stages • Problem analysis. Discuss requirements problem and propose change; • Change analysis and costing. Assess effects of change on other requirements; • Change implementation. Modify requirements document and other documents to reflect change.
50.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 50 Change management ChaimpChangand cProblemchangeIdentifieproblemRereq
51.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 51 Key points The requirements engineering process includes a feasibility study, requirements elicitation and analysis, requirements specification and requirements management. Requirements elicitation and analysis is iterative involving domain understanding, requirements collection, classification, structuring, prioritisation and validation. Systems have multiple stakeholders with different requirements.
52.
©Ian Sommerville 2004
Software Engineering, 7th edition. Chapter 7 Slide 52 Key points Social and organisation factors influence system requirements. Requirements validation is concerned with checks for validity, consistency, completeness, realism and verifiability. Business changes inevitably lead to changing requirements. Requirements management includes planning and change management.
Baixar agora