SERP’06 A Multi-Role Collaborative Method and Platform for Developing Software Requirements Chin-Yi Tsai and Chua-Huang Huang Dept. of Information Engineering.

Slides:



Advertisements
Similar presentations
Rational Unified Process®
Advertisements

Computer Science Department
Systems Development Environment
CSC 480 Software Engineering
Approaches to Systems Development
Requirements Specification
1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,
Fatima Al-Abdulla Managing Analysis. Outline:  Introduction  Why managing Analysis? 1-Documenting Analysis 2-Assigning Responsibilities 3-Communicating.
2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.
An Efficient and Scalable Pattern Matching Scheme for Network Security Applications Department of Computer Science and Information Engineering National.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Requirement engineering for an online bookstore system
An Agile View of Process
Software Product Lines Krishna Anusha, Eturi. Introduction: A software product line is a set of software systems developed by a company that share a common.
Classical vs. Agile Requirements Development Svetlin Nakov Telerik Software Academy academy.telerik.com Senior Technical Trainer
Roles and Responsibilities Jahangheer Shaik. Service Specification Specification requires development of three inter-related documents CIM, PIM and PSM.
Software Engineering Tutorial. Tutorial objectives  Direct application for the SW engineering activities.  Discuss real software development case studies.
Process: A Generic View
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
CompSci 230 Software Design and Construction
Method comparison: for Situational Method Engineering Mohssen Ali.
LECTURE 1 What does a Business Analyst do? IFS 231 Business Analysis.
UNIVERSITI TENAGA NASIONAL “Generates Professionals” CHAPTER 4 : Part 1 INTRODUCTION TO SOFTWARE DEVELOPMENT: SYSTEM ANALYSIS & DESIGN.
The Architecture Business Cycle. Software Architecture Definition The software architecture of a program or computing system is the structure or structures.
Introduction to Software Development 1. Outline The code-compile-debug process for writing a program The software development process 2.
CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University.
Lecture 7: Requirements Engineering
Approaches to Systems Development
ICS 2006 A Supervised Learning System for Software Project Management Chien-Kuo Bien, Chin-Yi Tsai, and Chua-Huang Huang Dept. of Information Engineering.
TCSE2007 A Multi-Role Collaborative Cooperation for Software Project Monitoring and Control Chin-Yi Tsai and Chua-Huang Huang Dept. of Information Engineering.
Capturing Web Application Requirements through Goal-Oriented Analysis Presented by Chin-Yi Tsai
Latifa AlAbdlkarim King Saud University October,2009.
Software Engineering Saeed Akhtar The University of Lahore Lecture 5 Originally shared for: mashhoood.webs.com.
Supporting Scenario-Based Requirements Engineering IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER, 1998 A. G. Sutcliffe, N. A. M.
Requirements Validation with Enactable Models of State-based Use Cases Chin-Yi Tsai.
Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 1 Requirements  Elicitation  Analysis  Specification.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Intro. to Software Engineering 1CSCI 3333 Data Structures.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Roles in a project team and software life cycles Authors: Hubert Czerczer s3688 Maciej Basista s3524.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
The principles of an object oriented software development process Week 04 1.
IEEE IT (Information Technology) Strategy – 2005 Unapproved.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Using UML, Patterns, and Java Object-Oriented Software Engineering 15. Software Life Cycle (Waterfall)
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
Inferring Declarative Requirements Specification from Operational Scenarios IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER, 1998.
Adding Hypermedia Requirement to Goal-Driven Analysis Presented by Chin-Yi Tsai.
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group January 2011.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Method engineering [infome] paper presentation Rodi heijbom
CS 160 and CMPE/SE 131 Software Engineering February 18 Class Meeting Department of Computer Science Department of Computer Engineering San José State.
Documenting Software Architectures. Outline  Introduction  Uses of Architectural Documentation  Views  Choosing the Relevant Views  Documenting a.
Think Scrum, act Scrum Scrum Practitioner like a boss Thibault Clavier.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Plan-Driven Processes Emerson Murphy-Hill. The Planning Spectrum 2 Source: Barry Boehm “Get Ready For Agile Methods, With Care,” IEEE Computer, Jan 2002.
Agile/XP Introduction
Chapter 7: Software Engineering
Chapter 7: Software Engineering
Unified Process Source & Courtesy: Jing Zou.
Introduction to Software Engineering
Documentation in Continuous Delivery Model and DevOps
Lecture 2 Revision of Models of a Software Process
Chapt 2 Iterative Evolutionary Agile.
Basic SDLC Models SDLC  System Development Life Cycle.
Presentation transcript:

SERP’06 A Multi-Role Collaborative Method and Platform for Developing Software Requirements Chin-Yi Tsai and Chua-Huang Huang Dept. of Information Engineering and Computer Science Feng Chia University Taichung, Taiwan, R.O.C.

SERP’06 2 Outline Introduction Roles and Role Relationship Collaborative Mechanism Collaborative Software Requirements Generation Collaborative Software Requirements Development Process Conclusion

SERP’06 3 Introduction Software development  Requirement analysis  System analysis  System design  Implementation  Testing Software development method  Waterfall  Spiral  Iterative and incremental  RUP  XP

SERP’06 4 Introduction (Cont’d) Requirements engineering  Goal-oriented  KAOS  i*  NFR framework  … Requirements Document

SERP’06 5 Introduction (Cont’d) Communication Collaborative method and platform  Multi roles  Distributed area

SERP’06 6 Roles and Role Relationship Roles  Client representative  Stakeholder  Client manager  Development representative  Analyst  Development manager Customer sideDeveloper side

SERP’06 7 Roles and Role Relationship (Cont’d) Role relationship  Representative-Representative Negotiation Role Relationship  Stakeholder-Analyst Collaborative Role Relationship Client representative Development representative StakeholderAnalyst

SERP’06 8 Roles and Role Relationship (Cont’d) Role relationship  (Client Manager/Stakeholder)-Development Manager Role Relationship  Client Manager-(Development Manager/Analyst) Role Relationship Client manager Development manager Stakeholder Client manager Development manager Analyst

SERP’06 9 Roles and Role Relationship (Cont’d) Role relationship  (Client Manager/Stakeholder)-(Development Manager/Analyst) Role Relationship  Client Manager-Development Manager Role Relationship Client manager Development manager StakeholderAnalyst Client manager Development manager

SERP’06 10 Collaborative Mechanism Collaborative Services  Collaborative Authoring Service  Supporting Work Service  Integrated Specification Generation Service  Collaborative Validation Service

SERP’06 11 Collaborative Mechanism (Cont’d) Collaborative Patterns  Single Peer Interaction  Multi Peer Interaction

SERP’06 12 Collaborative Mechanism (Cont’d) Collaborative Patterns  Single Central Collaboration  Multi Central Collaboration

SERP’06 13 Collaborative Software Requirements Generation IEEE std 830  IEEE recommended practice for software requirements specification The pruned SRS template  Introduction  Functional requirements  Non-functional requirements  Glossary 1. Introduction 2. Function requirements 3. Non-functional requirements 4. Glossary

SERP’06 14 Collaborative Software Requirements Development Process Role assignment validation Stakeholder authoring Analyst commenting SRS Generation Initial requirements or Refined requirements Comments Final SRS specification

SERP’06 15 Conclusion Communication Two kinds of roles  Customer side  Developer side Collaborative method and platform for  Project management and monitoring

SERP’06 16 Thank You