Software Development Life Cycle (SDLC) Tata Consultancy Services ltd. 12 October
|
|
- Theresa Spencer
- 6 years ago
- Views:
Transcription
1 Software Development Life Cycle (SDLC) Tata Consultancy Services ltd. 12 October
2 Objectives (1/2) At the end of the presentation, participants should be able to: Realise the need for a systematic approach to software development Comprehend and get a feel of Software Development Life Cycle 2
3 Objectives (2/2) Get a clear idea of all the phases of SDLC Objective Input Activities Output Role 3
4 Why SDLC? Objective To systematically develop high quality software in timely and cost effective manner Approach Systematic and engineering like approach is inevitable for developing large and complex software Involves use of techniques like system analysis, estimation, designing, development, testing, etc 4
5 SDLC Overview & Phases (1/4) A software life cycle is the series of identifiable stages that a software product undergoes during its lifetime Phases of SDLC Feasibility (pre-development) Establishes a high-level view of the intended project and determines its goals 5
6 SDLC Overview & Phases (2/4) Requirements Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs. Addresses on What System should do 6
7 SDLC Overview & Phases (3/4) Design Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation. Coding and Unit testing The real code is written here 7
8 SDLC Overview & Phases (4/4) Testing Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. Maintenance (post-development) Incorporation of changes, corrections, additions. 8
9 Objective Pre-development Phase: Feasibility Study (1/4) Determine whether developing the software is FINANCIALLY and TECHNICALLY feasible Input Inquiry from customer (Request for Proposal) 9
10 Feasibility Study (2/4) Activities Involves high level understanding of scope: Inputs to the system Processing to be carried out Outputs from the system Constraints to be adhered to 10
11 Feasibility Study (3/4) Analyzing the data to arrive at: Abstract definition of the problem Formulation of different solution strategies Examination of alternative solutions strategies i.e. benefits, resources input, cost, time, development related issues 11
12 Feasibility Study (4/4) Performing cost/benefit analysis to determine best solution under current circumstances Output Feasibility Analysis Report Role Business Analyst Note: May lead to a decision of NOT pursuing the project further 12
13 Requirements Phase (1/6) Objective: To establish user requirements Input Contract Agreement Feasibility Analysis Report 13
14 Activities: Requirements Phase (2/6) Requirements Gathering Collects all the possible information from customer Data collection techniques include: Interviews Discussions Questionnaires Understanding the Existing system, if any 14
15 Requirements Phase (3/6) Requirements analysis Analyze the gathered information by resolving Anomalies Conflicts Incompleteness 15
16 Requirements Phase (4/6) Requirements specification Properly documents the requirements Addresses What System should do Includes Functional and Non Functional Requirements Serves as a contract between the customer and the developer 16
17 Requirements Phase (5/6) Guidelines of Requirement Document: Written in a language that user can understand Thoroughly understood by both the customer and developer Reviewed Unambiguous; Consistent; Complete; Concise Well structured and easily modifiable 17
18 Outputs : Requirements Phase (6/6) Requirement Specification Document (Signed Off) Requirements Traceability Matrix (initiation) Test Case Document System Test Plan Role: Business Analyst 18
19 Design (1/6) Objective: To transform requirements specified in SRS document into a design that will be implemented using a programming language Inputs: Requirement Specification Document Requirement Traceability Matrix Test Case Document 19
20 Design (2/6) Activities: High level design Identification of Different modules Control relationships amongst modules Interfaces amongst the modules 20
21 Design (3/6) Low level design Data structures for individual modules Algorithms required for individual modules 21
22 Design (4/6) Design Guidelines Good modular design is achieved by using the rule divide and conquer i.e. Functionally independent modules Functionally independent modules have minimum interaction with each other Reduces error propagation across modules Increases reuse of modules Reduces design complexity 22
23 Design (5/6) Measures of functional independence: COHESION of a module is a measure of functional strength of a module COUPLING of a module (with other module) is a measure of degree of functional interdependence between the two modules 23
24 Design (6/6) Outputs High level Design Document Low level Design Document Updated Requirement Traceability Matrix Test Specification Document Role System Analyst, Sr. Developer 24
25 Coding and Unit Testing (1/5) Objective: Convert system design into code and Testing of each Unit independently Input: High Level and Low Level Design documents Requirement Traceability Matrix 25
26 Coding and Unit Testing (2/5) Activities: Individual modules are coded as per specifications by following CODING GUIDELINES After coding, the modules are subjected to walkthroughs Reduces the errors before testing starts After walkthroughs, the modules are individually unit tested 26
27 Coding and Unit Testing (3/5) Coding guidelines: Keep coding style simple Do not use same identifier for different purposes e.g. looping variables Use meaningful variable names Well document the code e.g. suggested ratio of code/comments is 3:1 27
28 Coding and Unit Testing (4/5) Keep function size as small as possible Minimize use of GOTO statement Use proper error handling mechanism Follow best practices which leads to Improved performance, easy maintenance, reusability 28
29 Coding and Unit Testing (5/5) Output Unit Tested Modules Responsibility Developers 29
30 Verification Verification & Validation Ensures that software correctly implements a specific function (Are we building the product right?) Validation Ensures that the built software is traceable to customer requirements (Are we building the right product?) 30
31 Testing (1/6) Objective : To identify all the defects existing in the integrated S/W product Input: Individually Tested Modules Test Specifications Document 31
32 Testing (2/6) 32
33 Testing (3/6) Activities Integration testing: Modules are integrated in planned manner During each integration step, partially integrated system is tested When ALL modules are integrated (and tested), the system is ready for system testing 33
34 Testing (4/6) System testing: Objective: To confirm that the developed system meets the requirements (as specified in SRS document) Carried out according to the system test plan Note: system test plan is prepared during requirements phase (include test cases and expected results) 34
35 Testing (5/6) Additional types of system testing: Alpha testing and Beta testing (for product) Acceptance testing (by customer) 35
36 Testing (6/6) Output Tested System Test Report Responsibility Tester 36
37 Testing Techniques Black Box testing White Box testing Security Testing Stress Testing Performance Testing Smoke Testing Regression Testing 37
38 Post-development Phase: Maintenance Phase Objective : Maintaining the delivered system Incorporation of changes, corrections, additions Inputs : Client approved deployed System 38
39 Maintenance Phase Activities: 1) Corrective maintenance: Fixing errors not detected during the development phase 2) Adaptive maintenance: Improving implemented system (performance) Enhancing functionalities (new requirements) Porting software to new environment 39
40 Software Maintenance Output: Enhanced System Roles: System Analyst, Developer 40
41 Thank You 41
Software Development Life Cycle:
Software Development Life Cycle: The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software
More informationObjectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationSDLC AND MODEL SELECTION: A STUDY
SDLC AND MODEL SELECTION: A STUDY V. Therese Clara Asst professor of Computer Science, Madurai Kamaraj University College, Madurai, India ABSTRACT In the software industry, the frequency of failure of
More informationSoftware Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationLectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1
Lectures 2 & 3 Software Processes Software Engineering, COMP201 Slide 1 What is a Process? When we provide a service or create a product we always follow a sequence of steps to accomplish a set of tasks
More informationSoftware Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationTopics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationKINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK
KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK Subject Code & Subject Name: IT1251 Software Engineering and Quality Assurance Year / Sem : II / IV UNIT I SOFTWARE PRODUCT
More informationThe software process
Software Processes The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. A software process model is an abstract representation
More informationDigital Industries Apprenticeship: Occupational Brief. Software Tester. March 2016
Digital Industries Apprenticeship: Occupational Brief Software Tester March 2016 1 Digital Industries Apprenticeships: Occupational Brief Level 4 Software Tester Apprenticeship Minimum Standards and Grading
More informationVolume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at
Volume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info A Study of Software Development Life Cycle Process Models
More informationProduct Requirements. Requirements. Get it Right ASAP. Why Requirements are Difficult. Levels of S/W Requirements. Types of S/W Requirements
Requirements Overview importance of getting right difficulty of getting right types and levels of characteristics of good the Requirements Development Process inception gathering, classification actors
More information[Name] [ ID] [Contact Number]
[Name] [Email ID] [Contact Number] THIS IS ONLY MODEL RESUME - DO NOT COPY AND PASTE INTO YOUR RESUME. PROFILE SUMMARY 15+ years of IT experience in Consulting and worked with the Major clients for the
More informationBased on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems
Software Processes Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems Slide 1 Objectives To introduce software
More informationIntroduction to Systems Analysis and Design
Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.
More informationRequirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2014/2015 Dr. Sebastian Adam Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects
More informationThis tutorial also elaborates on other related methodologies like Agile, RAD and Prototyping.
i About the Tutorial SDLC stands for Software Development Life Cycle. SDLC is a process that consists of a series of planned activities to develop or alter the Software Products. This tutorial will give
More informationCHAPTER 2 LITERATURE SURVEY
10 CHAPTER 2 LITERATURE SURVEY This chapter provides the related work that has been done about the software performance requirements which includes the sub sections like requirements engineering, functional
More informationCMPT 275 Software Engineering
CMPT 275 Software Engineering Software life cycle 1 Software Life Cycle Sequence of processes completed as a software project moves from inception to retirement At beginning of project development, choose
More informationProduct Requirements. Requirements. Get it Right ASAP. Why Requirements are Difficult. Types of S/W Requirements. Levels of S/W Requirements
Requirements Overview importance of getting right difficulty of getting right types and levels of characteristics of good the Requirements Development Process inception gathering, classification evaluation
More informationGENERAL PRINCIPLES OF SOFTWARE VALIDATION
GUIDANCE FOR INDUSTRY GENERAL PRINCIPLES OF SOFTWARE VALIDATION DRAFT GUIDANCE Version 1.1 This guidance is being distributed for comment purposes only. Draft released for comment on: June 9, 1997 Comments
More informationProject Report Template (Sem 1)
1. Introduction & Problem Statement Project Report Template (Sem 1)
More informationIntroduction to software testing and quality process
Introduction to software testing and quality process Automated testing and verification J.P. Galeotti - Alessandra Gorla Engineering processes Engineering disciplines pair construction activities activities
More informationRequirements Engineering
Requirements Engineering Professor Ray Welland Department of Computing Science University of Glasgow E-mail: ray@dcs.gla.ac.uk The Importance of Requirements Identifying (some) requirements is the starting
More informationPertemuan 2. Software Engineering: The Process
Pertemuan 2 Software Engineering: The Process Collect Your Project Topic What is Software Engineering? Software engineering is the establishment and sound engineering principles in order to obtain economically
More informationService Description for Storage Implementation. Issue 1.0. Date
Service Description for Storage Implementation Issue 1.0 Date 2012-11-01 Contents 1 Service Overview... 3 1.1 Service Product Definition... 3 1.2 Service Architecture... 3 2 Service Description... 4 2.1
More informationISTQB Sample Question Paper Dump #11
ISTQB Sample Question Paper Dump #11 1. Which of the following is true a. Testing is the same as quality assurance b. Testing is a part of quality assurance c. Testing is not a part of quality assurance
More informationSoftware Testing Life Cycle
Software Testing Life Cycle STLC (Software Testing Life Cycle) is an integral component of SDLC (Software Development Life Cycle). Testing has become a distinct phenomenon during and after the development
More informationRequirements Engineering and Software Architecture Project Description
Requirements Engineering and Software Architecture Project Description Requirements Engineering Project Description This project is student-driven. There will be external sponsors, users, and others that
More informationREQUIREMENT DRIVEN TESTING. Test Strategy for. Project name. Prepared by <author name> [Pick the date]
REQUIREMENT DRIVEN TESTING Test Strategy for Project name Prepared by [Pick the date] [Type the abstract of the document here. The abstract is typically a short summary of the contents of
More informationRisk Based Testing. -Why we need RBT? -Types of risks -Managing risks -Methods of evaluation & risk analysis -Costs and benefits
Risk Based Testing -Why we need RBT? -Types of risks -Managing risks -Methods of evaluation & risk analysis -Costs and benefits Ladislau Szilagyi www.euroqst.ro Definitions (ISTQB glossary) Risk = a factor
More informationIntroduction to Software Engineering
Introduction to Software Engineering 2. Requirements Collection Mircea F. Lungu Based on a lecture by Oscar Nierstrasz. Roadmap > The Requirements Engineering Process > Functional and non-functional requirements
More informationSE420 Software Quality Assurance
SE420 Software Quality Assurance Lecture 2 Software Specification Part-1 January 16, 2017 Sam Siewert SQA LO s (Learning Objectives) Theory and Principles 1. Coverage of Current SQA Theory and Practice
More information7. What is planning? It is an act of formulating a program for a definite course of action. Planning is to decide what is to be done.
UNIT I FUNDAMENTALS 2 MARKS QUESTIONS & ANSWERS 1. What is software project management? Software project management is the art and science of planning and leading software projects. It is sub discipline
More informationObject-Oriented and Classical Software Engineering
Slide 3.1 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 3 Slide 3.2 THE SOFTWARE PROCESS Overview Slide 3.3
More informationIntegration and Testing
Integration and Testing 1 Today Software Quality Assurance Integration Test planning Types of testing Test metrics Test tools 2 Deliverables by Phase Possible Deliverables by Phase Concept Document Statement
More informationManual Testing Material. Address: #104,Nandini Residency, Addagutta Society, Beside KPHB Police station lane JNTU X-Roads, HYD
Material Address: #104,Nandini Residency, Addagutta Society, Beside KPHB Police station lane JNTU X-Roads, HYD 1. Introduction to Software Testing Manual Testing 1.1 What is Software Testing Software testing
More informationChapter 3 Software Process Model
Usman Akram COMSATS Institute of information Technology lahore musmanakram@ciitlahore.edu.pk March 8, 2015 About software process model Outline 1 About software process model Build and Fix Model Why Models
More informationBSV Better SuperVision Ltd. #904, Street Edmonton, AB T5K 2J1. Phone: (780) Fax: (780)
BSV Better SuperVision Ltd. #904, 10050-112 Street Edmonton, AB T5K 2J1 Email: bsv@clra.org Phone: (780)702-5835 Fax: (780)451-5447 1 BSV Better SuperVision Ltd. ON-THE-JOB COACHING TOOL PART ONE - INTRODUCTION
More informationIntroduction to Software Engineering
UNIT I SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, objects oriented) -system engineering computer
More informationChapter 8. Systems Development. Ralph M. Stair George W. Reynolds
Ralph M. Stair George W. Reynolds Chapter 8 Systems Development An Overview of Systems Development Managers and employees in all functional areas work together and use business information systems Corporations
More informationRequirements Engineering Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 7 Slide 1
Requirements Engineering Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 7 Slide 1 Objectives To describe the principal requirements engineering activities and their relationships
More informationRequirements Gathering using Object- Oriented Models
Requirements Gathering using Object- Oriented Models Software Quality Assurance What is software? According to the IEEE (Institute of Electrical and Electronics Engineers) A software is: Programs, procedures,
More informationQuestion 2: Requirements Engineering. Part a. Answer: Requirements Engineering Process
Question 2: Requirements Engineering Part a. Answer: Requirements Engineering Process The requirements engineering process varies from domain to domain. But the general activities involved are: Elicitation
More informationNumber: DI-IPSC-81427B Approval Date:
DATA ITEM DESCRIPTION Title: Software Development Plan (SDP) Number: DI-IPSC-81427B Approval Date: 20170313 AMSC Number: N9775 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity:
More informationTest Management Test Planning - Test Plan is a document that is the point of reference based on which testing is carried out within the QA team.
Test Management Test Planning - Test Plan is a document that is the point of reference based on which testing is carried out within the QA team. - It is also a document we share with the Business Analysts,
More informationCase Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model
Case Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model Agile Waterfall Hybrid Model The Waterfall Model has been the ideal choice for software development.
More informationSOFTWARE MAINTENANCE PROCESS MODEL AFTER DELIVERY WITH QUALIFIED OUTPUT
SOFTWARE MAINTENANCE PROCESS MODEL AFTER DELIVERY WITH QUALIFIED OUTPUT SALEEM AL-ZOUBI Faculty of Information Technology, Irbid National University E-mail: it@inu.edu.jo Abstract-Software maintenance
More informationInstallation and Maintenance of Health IT Systems
Installation and Maintenance of Health IT Systems Software Development Life Cycle (SDLC) Model Software Development Life Cycle Learning Objectives 1. Define the steps of the Software Development Life Cycle
More informationRecommended Configuration Management Practices for Freelance Software Developers
Recommended Configuration Management Practices for Freelance Software Developers Chaudry Bilal Ahmad Khan Department of Electrical Engineering Institute of Space Technology Islamabad, Pakistan chaudrykhan@gmail.com
More information6/29/ Professor Lili Saghafi
6/29/2014 1 Professor Lili Saghafi MANAGING INFORMATION TECHNOLOGY Lecture 9 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT By : Prof. Lili Saghafi 1-2 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT Large
More informationChapter 6: Software Evolution and Reengineering
Chapter 6: Software Evolution and Reengineering Harald Gall Software Engineering Group www.ifi.unizh.ch/swe/ Universität Zürich Institut für Informatik Ian Sommerville 2004 Software Engineering, 7th edition.
More informationIt will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect.
Functional Specification / Requirement Document (FSD / FRD) The Functional Specification Document (FSD) in software development is a formal document that describes the functions of the software/system
More informationBASICS OF SOFTWARE TESTING AND QUALITY ASSURANCE. Yvonne Enselman, CTAL
BASICS OF SOFTWARE TESTING AND QUALITY ASSURANCE Yvonne Enselman, CTAL Information alines with ISTQB Sylabus and Glossary THE TEST PYRAMID Why Testing is necessary What is Testing Seven Testing principles
More informationCMMI for Technical Staff
CMMI for Technical Staff SES CMMI Training Series April 7, 2009 Audio Conference #: Dial - 1-877-760-2042 Pass code - 147272 SM SEI and CMM Integration are service marks of Carnegie Mellon University CMM
More informationSystem Development Life Cycle Fall Introduction to Information and Communication Technologies CSD 102
System Development Life Cycle Fall 2016 Introduction to Information and Communication Technologies CSD 102 Outline Software Engineering SDLC Mehwish Fatima - CIIT Lahore 06/11/2016 2 What is the System
More informationIntroduction to Software Engineering
Introduction to Software Engineering 11. Software Quality Mircea F. Lungu Based on materials by Oscar Nierstrasz. What you will know > Can a correctly functioning piece of software still have poor quality?"
More informationThe Sector Skills Council for the Financial Services Industry. National Occupational Standards. Risk Management for the Financial Sector
The Sector Skills Council for the Financial Services Industry National Occupational Standards Risk Management for the Financial Sector Final version approved April 2009 IMPORTANT NOTES These National Occupational
More informationAgile Test Plan How to Construct an Agile Test Plan
Agile Test Plan How to Construct an Agile Test Plan XBOSoft White Paper How to Construct an Agile Test Plan www.xbosoft.com 2 Agile is changing not only the way we develop software but the way we work
More informationVALLIAMMAI ENGINEERING COLLEGE SRM Nagar, Kattankulathur
VALLIAMMAI ENGINEERING COLLEGE SRM Nagar, Kattankulathur 603 203 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING QUESTION BANK IV SEMESTER CS6403 SOFTWARE ENGINEERING Regulation 2013 Academic Year 2017
More informationConfident Software Development Process Model
Confident Software Development Process Model S.Thulasi Krishna M.E., (Ph.D), Research scholar Rayalaseema University Kurnool (dist.,) Andhra Pradesh Dr. S.Sreekanth, Ph.D Professor, Dept of CSE SITAMS,Chittoor(dt),
More informationWORK PLAN AND IV&V METHODOLOGY Information Technology - Independent Verification and Validation RFP No IVV-B
1. Work Plan & IV&V Methodology 1.1 Compass Solutions IV&V Approach The Compass Solutions Independent Verification and Validation approach is based on the Enterprise Performance Life Cycle (EPLC) framework
More informationSystems Analysis and Design Methods Chapter 3: Information Systems Development
Systems Analysis and Design Methods Chapter 3: Information Systems Development Multiple Choice Questions 1. The act of drawing one or more graphical representations of a system is called. A. modeling B.
More informationCost of Changing the Activities in SDLC. Minimum of Cost at this level. code debuging unit test integration. Activity
Software Development Life Cycle (SDLC) This is a work flow for creating a new software/application. Usually, any company that is in the software business follows the same route and structure. In this document
More informationSoftware Auditor Skills Training Course Offered by The Westfall Team
Software Auditor Skills Training Course Software Auditor Skills is a 2-day course that is a subset of the Software Auditing course. This course is designed to provide a knowledge base and practical skills
More informationAUTOMOTIVE SPICE v3.1 POCKET GUIDE
EXTENDED VDA SCOPE ASPICE v3.1 AUTOMOTIVE SPICE v3.1 POCKET GUIDE 4 5 6 7 8-9 10 11-13 14-15 16-19 20-43 44-49 50-51 52-69 70-93 94-103 104-105 106 Automotive SPICE at a glance Automotive SPICE application
More informationMajor attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system development projects Major attributes of the Lifecycle The project Moves systematically
More informationarxiv: v1 [cs.se] 4 Apr 2017
Checklists to Support Test Charter Design in Exploratory Testing Ahmad Nauman Ghazi, Ratna Pranathi Garigapati, and Kai Petersen arxiv:1704.00988v1 [cs.se] 4 Apr 2017 Blekinge Institute of Technology,
More informationBidirectional Requirements Traceability By Linda Westfall.
Bidirectional s Traceability By Linda Westfall www.westfallteam.com Traceability is one of the essential activities of good requirements management. Traceability is used to ensure that the right products
More informationJOB PROFILE JOB STORE # 220 TITLE: POLICY ANALYST (DEVELOPMENTAL) CLASSIFICATION: ADMINISTRATIVE OFFICER 18, 21 OR 24 PROGRAM
JOB PROFILE JOB STORE # 220 TITLE: POLICY ANALYST (DEVELOPMENTAL) CLASSIFICATION: ADMINISTRATIVE OFFICER 18, 21 OR 24 PROGRAM The Health Services Division sets the foundation for the delivery of high quality
More informationA Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 2.0 Skillport
A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 2.0 by The International Institute of Business Analysis (IIBA) International Institute of Business Analysis. (c) 2009. Copying
More informationPMI-PBA IN ACTION. Saturday PDU Program PMI Metrolina Chapter. Gary Schmitz, PMP, PMI-PBA.
PMI-PBA IN ACTION Saturday PDU Program PMI Metrolina Chapter Gary Schmitz, PMP, PMI-PBA www.totalsystemseduca5on.com 2016 Total Systems Educa5on, LTD. Business Analysis WHAT IS BUSINESS ANALYSIS? The application
More informationRisk-Based Testing: Analysis and Strategy. Presented at Quality Assurance Institute QUEST Conference Chicago, Ill., 2009
Risk-Based Testing: Analysis and Strategy Presented at Quality Assurance Institute QUEST Conference Chicago, Ill., 2009 Clyneice Chaney, CMQ/OE, PMP April 21, 2009 Workshop Outline Part I Risk Management
More informationChallenges of Managing a Testing Project: (A White Paper)
Challenges of Managing a Testing Project: () Page 1 of 20 Vinod Kumar Suvarna Introduction Testing is expected to consume 30 50 % of the Project Effort, Still properly managing testing project is not considered
More informationObject-Oriented and Classical Software Engineering THE SOFTWARE PROCESS 9/17/2017. CHAPTER 3 Slide 3.2. Stephen R. Schach. Overview Slide 3.
Slide 3.1 CHAPTER 3 Slide 3.2 Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS Eighth Edition, WCB/McGraw-Hill, 2011 Stephen R. Schach Overview Slide 3.3 Overview (contd) Slide 3.4
More informationDeliverable: 1.4 Software Version Control and System Configuration Management Plan
Deliverable: 1.4 Software Version Control and System Configuration VoteCal Statewide Voter Registration System Project State of California, Secretary of State (SOS) Authors This document was prepared
More informationThe Role of ISO in Strategic Asset Lifecycle Information Management
The Role of ISO 15926 in Strategic Asset Lifecycle Information Management Summary Utilizing IS0 15926 enables organizations to meet their asset information requirements while reducing the costs associated
More informationMINGGU Ke 1 Analisa dan Perancangan Sistem Informasi
MINGGU Ke 1 Analisa dan Perancangan Sistem Informasi Pokok Bahasan: A Framework for Systems Analysis and Design Tujuan Instruksional Khusus: Learn step by step building system analysis and design Referensi:
More informationCHAPTER 2 PROBLEM STATEMENT
CHAPTER 2 PROBLEM STATEMENT Software metrics based heuristics support software quality engineering through improved scheduling and project control. It can be a key step towards steering the software testing
More informationEffective Test Automation of SAP Implementations
Effective Test Automation of SAP Implementations Vipin Kumar Managing Director & Software Engineering Evangelist Astra Infotech Pvt Ltd vk@astrainfotech.com QM15 2009 IBM Corporation Agenda Introduction
More informationIIBA Global Business Analysis Core Standard. A Companion to A Guide to the Business Analysis Body of Knowledge (BABOK Guide) Version 3
IIBA Global Business Analysis Core Standard A Companion to A Guide to the Business Analysis Body of Knowledge (BABOK Guide) Version 3 International Institute of Business Analysis, Toronto, Ontario, Canada.
More informationSUSE Unified Delivery Process
Guide www.suse.com SUSE Unified Delivery Process What Is the SUSE Unified Delivery Process? The SUSE Unified Delivery Process is a solution delivery process based on the IBM* Rational Unified Process*
More informationQUESTIONS NUMBER ONE (Total marks 20) NUMBER TWO (Total marks 20) NUMBER THREE
NUMBER ONE QUESTIONS The growth of telecommunications has made information a key organisational resource, which requires careful management. a. Give your definition of an Information System. (5 b. The
More informationSoftware Quality. A Definition of Quality. Definition of Software Quality. Definition of Implicit Requirements
Definition of Software Quality Software Quality The Ultimate Goal of Software Engineering Software must conformance to explicit and implicit requirements if it is to be considered to be of good quality.
More informationvramanujam Page 1 5/22/2014 TESTING MANUAL VARUN RAMANUJAM
vramanujam Page 1 5/22/2014 TESTING MANUAL BY VARUN RAMANUJAM vramanujam Page 2 5/22/2014 TOPICS SDLC (different phases) Types of SDLC models Role of Testing in SDLC Key differences between QA, QC and
More informationSignificance of Quality Metrics during Software Development Process
Significance of Quality Metrics during Software Development Process 1 Poornima. U. S., 2 Suma. V 1 Program Manager, MCA Department, Acharya Institute of Management and Sciences 1,2 Research and Industry
More informationCreating Your Own Software Development Life Cycle (SDLC)
Documentation Consultants Creating Your Own Software Development Life Cycle (SDLC) www.sdlcforms.com Revision History Date Version Author Change 02-23-17 1.0 Ken Fass Initial release. COPYRIGHT NOTICE
More informationSurviving the Top Ten Challenges of Software Testing
Surviving the Top Ten Challenges of Software Testing: A Closer Look at Understanding Software Testing Randy Rice, CQA, CSTE Rice Consulting Services, Inc. 405-692-7331 http://www.riceconsulting.com rcs@telepath.com
More informationCOMP 474 Software Engineering
COMP 474 Software Engineering Professor W. L. Honig The Process at a Glance (TSPi) Launch Strategy Plan Requirements Repeat A controlled, data driven, step-by-step process for software life cycle Design
More informationVC SOFTWARE PROJECT MANAGEMENT PLAN
VC SOFTWARE PROJECT MANAGEMENT PLAN Supporting Process Plan This part will contain plans for the supporting processes that span the duration of the software project. Team #4 Members: Yazeed Al-Swailem
More informationSession-2: Deep Drive into Non Functional Requirements (NFRs)
Session-2: Deep Drive into Non Functional Requirements (NFRs) Important Points to Note All Participating colleges are requested to mute your telephone lines during the webinar session. Participants are
More informationObject-Oriented & Classical Soft Engineering
Object-Oriented & Classical Soft Engineering Seventh Edition Stephen R. Schach Vanderbilt University Higher Education Boston Burr Ridge, IL Dubuque, IA New York San Francisco St. Louis Bangkok Bogota Caracas
More informationIntroduction. Fundamental concepts in testing
INF 3121 Software Testing - Lecture 01 Introduction. Fundamental concepts in testing 1. Why is testing necessary?? 4. Fundamental test process 5. The psychology of testing 1 1. Why is testing necessary?
More informationSistemi ICT per il Business Networking
Corso di Laurea Specialistica Ingegneria Gestionale Sistemi ICT per il Business Networking Requirements Engineering Docente: Vito Morreale (vito.morreale@eng.it) 17 October 2006 1 UP Phases 1. Inception
More informationSOFTWARE ENGINEERING
Page 1 MCA302 SOFTWARE ENGINEERING UNIT I - SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, object oriented)
More informationRequirements Validation Techniques: An Empirical Study
Requirements Validation Techniques: An Empirical Study Hafiz Anas Bilal Dept. of Computer Science COMSATS Institute of Information Technology, Islamabad, Pakistan Muhammad Ilyas Dept. of Computer Science
More informationCMMI and FPA. the link and benefit of using FPA when rolling out CMMI. Christine Green IFPUG - Certified Function Point Specialist EDS
CMMI and FPA the link and benefit of using FPA when rolling out CMMI Christine Green IFPUG - Certified Function Point Specialist EDS and the EDS logo are registered trademarks of Electronic Data Systems
More informationSOFTWARE TESTING REVEALED
SOFTWARE TESTING REVEALED TRAINING BOOK SECOND EDITION BY INTERNATIONAL SOFTWARE TEST INSTITUTE www.test-institute.org COPYRIGHT INTERNATIONAL SOFTWARE TEST INSTITUTE Dedication To all of the International
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More information