SDLC (Software Development Life Cycle) Role Play

Slides:



Advertisements
Similar presentations
Calyxinfo Walking through Calyx Info The Organisation.
Advertisements

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Object-Oriented Analysis and Design LECTURE 2: INCEPTION PHASE.
<<replace with Customer Logo>>
Stepan Potiyenko ISS Sr.SW Developer.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
Nov. 13, 2003CS WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003.
The Proposal. Project Proposals Genesis of Proposals: They can result for formal requests (e.g. Request For Proposal, RFP) They can be unsolicited (e.g.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Strategic Information Initiatives Week 4 Project Planning Frank Coker, MBA, CMC President Information Systems Management, Inc. (a consulting firm – since.
Project Management Methodology (PMM)
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
Planning. SDLC Planning Analysis Design Implementation.
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Project Management Design specifications
Introduction to Information System Development.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Enterprise Product Implementation Process. Components of a Successful Implementation  A detailed Scope Document for customer review and signoff  Creation.
Software Testing Life Cycle
LECTURE 1 What does a Business Analyst do? IFS 231 Business Analysis.
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
Independent User Acceptance Test Process (IUAT)
Boston University Project Management Association Website Development Group 3 Team3 CS632 Dr. Vijay Kanabar Team Members Mario Soto Emily Ziegler Kevin.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
PAGE 1 Company Proprietary and Confidential R&D Project Proposal Student Management Information System January 10, 2012.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Software Engineering Lecture # 1.
Business Project Plan Presenter Name | Company Name.
Systems Analysis & Design AUTHOR: PROFESSOR SUSAN FUSCHETTO 10/24/
IS2210: Systems Analysis and Systems Design and Change Twitter:
Team-Based Development ISYS321 Managing the Information Systems Project.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Software Testing-STLC
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
Project Execution Methodology
Chapter 11 Project Management.
MIS 120 Test Planning.
Software Verification and Validation
Presenter Name | Company Name
BA Continuum India Pvt Ltd
WORK BREAKDOWN STRUCTURE
Presenter Name | Company Name
Quality Management Perfectqaservices.
Presenter Name | Company Name
Software Development Life Cycle
Roles and Responsibilities (1/3)
How to Successfully Implement an Agile Project
Engineering Processes
Presenter Name | Company Name
IS&T Project Reviews September 9, 2004.
Presenter Name | Company Name
Presenter Name | Company Name
Insert name of who presenting to
Development Lifecycle
Presenter Name | Company Name
Engineering Processes
Software Testing Lifecycle Practice
Software Development In Agile
Presenter Name | Company Name
Software Development Life Cycle (SDLC)
Software Development In Agile
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

SDLC (Software Development Life Cycle) Role Play Week 09 SDLC (Software Development Life Cycle) Role Play

SDLC Role Play Class will be divided into several development teams. Each development team should consist of 4 to 6 students. (Max 8 students per team) From each development team, identify the following roles: Client (Owner of the product) – Your instructor (SRS) Project manager(s) Analyst(s) Developer(s) Tester(s)

Role Description – Project Manager Project Manager: is the person who manages a project. This includes leading the planning and the development of all project deliverables. The project manager is responsible for managing the budget and schedule and all project management procedures (scope management, issues management, risk management, etc.). Project manager(s) should submit the following documents for assignment #1: Project TimeLine Issue log

Role Description - Analyst Analyst: is responsible for capturing and documenting business requirements from the clients. For some cases, analyst is also responsible for creation of technical solution document, high level design document, and detail design document.  Analyst(s) should submit the following documents for assignment #1: High level design document Detail design document

Role Description - Developer Developer: is responsible for the actual building of the solution (coding the software), and performs unit testing too. Developer(s) should complete coding and unit testing of the software, and support tester during test phase.

Role Description - Tester Tester: is responsible for system testing, and ensures that the solution meets the business requirements and that it is free of errors and defects. Tester(s) should submit the following documents for assignment #1: Test plan Test cases Software defect log