Requirements engineering – seminar with a real case study Zoran Budimac.

Slides:



Advertisements
Similar presentations
VCE IT Theory Slideshows By Mark Kelly Vceit.com Problem Solving Methodology Analysis Activities Revised version: 2013.
Advertisements

Johnson Logistics Solutions Office of Systems and Information Technology.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
On the concept of the course on software project management Mirjana Ivanović (Zoran Budimac) Faculty of Science, Department of Mathematics and Informatics.
An industrial software project as a software engineering module at HU Kay Schützler.
Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.
Discovering Computers Fundamentals, 2011 Edition Living in a Digital World.
Team Name Critical Design Review Team Members Date Fall 2011 Rev A
Lecture 2: Software Production & Processes Dr Valentina Plekhanova University of Sunderland, UK
1 Chapter 7 IT Infrastructures Business-Driven Technology
Cooperation, Learning, and Project Management SLP 10: Follow up Learning Profiles, P2 Process Analysis, and Presentations Frances Jørgensen.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
©© 2013 SAP AG. All rights reserved. Scenario/Processes Make-to-Stock Scenario Overview Planning Supply Initiating Production Executing Production Processing.
S R S S ystem R equirements S pecification Specifying the Specifications.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
1 CMPT 275 Software Engineering Requirements Analysis Phase Overview of Requirements Analysis Activity System Context Diagrams.
ERP Raghunath M D BSNL Mobile Services, Ernakulam, Ph:
John Hardy Business Services Going the Distance for you.
Introduction to Business
1 Software Engineering CEN5035 copyright © 1996, 2001 R.S. Pressman & Associates, Inc.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
ITEC 370 Lecture 8 Requirements. Review Requirements –What are some of the characteristics of a good requirement? –What are use cases?
 Over 25 years experience  Contingent Labor Specialists  Branch offices Nationwide  Dedicated account managers  National recruiting teams  Financially.
Implementing Update Management
Course Introduction CSCI Software Engineering II Fall 2014 Bill Pine.
Feasibility and Business Planning
Software Requirements Engineering CSE 305 Lecture-2.
Lecture 1Software Engineering1 (Trimester I Session 2002/2003) Lecturer / Tutor Name : Mr. R. Logeswaran
7-1 Chapter 7 IT Infrastructures Business-Driven Technology.
Software Engineering EKT 420 MOHAMED ELSHAIKH KKF 8A – room 4.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
7-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 7 IT Infrastructures.
Click here to advance to the next slide.. Chapter 5 Entrepreneurship Section 5.2 The Business Plan.
The Main Idea Once an entrepreneur discovers a good business opportunity, the next step is to do market research. Market research helps to determine.
Lecture 7: Requirements Engineering
COMP 208/214/215/216 – Lecture 8 Demonstrations and Portfolios.
CS/SWE 421 Project Overview Dan Fleck. Project Overview Team Formation Team Formation - just to get an idea of who you are and what you want to do Detailed.
VCE IT Theory Slideshows By Mark Kelly Vceit.com Problem Solving Methodology 3 Development.
CONTENTS OF THE SRS REPORT. Software Requirements Specification (SRS) template The SRS document describes recommended approaches for the specification.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Systems Development Life Cycle
CS 345 – Software Engineering Nancy Harris ISAT/CS 217
Software Engineering Lecture # 1.
An Overview of Software Testing By Kay E. Duchesne.
1Lecture 8 Introduction to Systems Analysis l Objectives –Explain how systems analysis relates to business needs, problems, and opportunities –List and.
CompSci 702 Security for Smart Devices
Software Requirements Specification Document (SRS)
Chapter 3: The Requirements Workflow [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada, Reno Department of Computer.
Activity 1 5 minutes to discuss and feedback on the following:
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
PRESENTER: MS. CRYSTAL WATSON DATE: OCTOBER 4, 2014 Preparing for a Successful Job Interview.
© 2015 IBM Corporation IBM and IBM Business Partner Use Only Business Partner Technical Vitality Overview January, 2015 Send an to
After class… Reach out to your GP1 group Setup time to meet Get started on GP1 asap!
SAP MDG(MASTER DATA GOVERNANCE) ONLINE TRAINING UK Contact Us :
Session 2.  Recap of Services We Provide  Refund Policy  Selling Tools Demo(s)  CRM Demo  Commission/Bonus Recap  Teen to show how to configure.
For more course tutorials visit
What is CRM ? Customer Relationship Management (CRM) is an information industry term for methodologies, software, and usually Internet capabilities that.
Discovering Computers 2010: Living in a Digital World Chapter 14
Enterprise Architecture Guide Project at MIT CSG Presentation 9/23/04 Jerry Grochow MIT’s ITAG team sponsored a six week initiative to document the.
Classical Waterfall Model
Lifecycle Services for Advanced Wireless LAN (LCSAWLAN) practice-questions.html.
Software Requirements analysis & specifications
NTC 406 Competitive Success/snaptutorial.com
#1 Explain the Work ➢ For technical work, you will be needing remote employees for Long- Term Roles and Assignments. ➢ The job description should clearly.
INF 220 Week 2 Assignment Source of Competitive Advantage FOR MORE CLASSES VISIT INF 220 Week 2 Assignment Source of Competitive Advantage.
NTC 406 Education for Service/snaptutorial.com
INF 220 RANK Education for Service-- inf220rank.com.
EMPLOYCODER The Dedicated Offshore Development Center In India.
Theories of the Interview
Presentation transcript:

Requirements engineering – seminar with a real case study Zoran Budimac

Requirements engineering Elective seminar offered this year – 12 students  Three teams + 1 individual to cover validation IV and III year  Budimac and Ivanović Combination of theory and practice Theory  Elicitation  SRS + example, another example of RS (JCSE), overviewed notations (UC, automaton, activity diagrams…)  Validation

Practice - 1 Analysis  exercise with sampled interviews for virtual company (12 pages): general manager, IT manager, security officer, financial manager (on site!).  Sampled interviews are for stating the requirements for hardware and software infra-structure for the company  The task was to order the gathered information according to importance

Practice 1 - analisys General manager  Two paragraphs saying that they are distributed among 8 centers in 8 countries, having 650 employees, and will grow by 10% every year. Thae wanted a stable solution that will be valid at least 10 years IT manager  9 pages stating in 12 points specific tasks such are what shall be accessible from Internet, what should not, what should be accessible from wireless, how access should be maintained from within a building and from distributed centers… Security officer  1 page stating security issues Financial manager  2 paragraphs stating that the most important application is ERP that has to report in real-time and that money is not the issue Can you guess in one minute?

Practice 2 – from interview to specification Subset of a real case study Software for a company selling dishes in a ‘door-to-door’ manner, to be run in three countries  Customers and their status  Contracts With their lifetime (remainders, annulations, invoices, …)  Associates with their hierarchy  Provision (commission) calculation  … Not all phases could be performed properly (e.g., reviews done only by me)

Practice 2 (contd.) I was acting in different roles: customer, lecturer, reviewer – we were trying to make a clear difference of my roles.  Face to face, , Skype This task was done by teams over the semester and should end with a RS according to IEEE SRS recommendation.

Practice 3 - automaton Done on the site. To create automaton that describes the lifetime of the contract.

Results Final mark based on the final document and solutions to practical aassignments One team got 10, other two got 8  Every team needed 3 itearations until mark could be offered  Two persons are doing additional tasks for better marks Final document