SE351 Roadmap. SE351a: Software Project & Process Management. W3.2: Software Development Lifecycles
|
|
- Morris Cross
- 5 years ago
- Views:
Transcription
1 SE351a: Software Project & Process Management W3.2: Software Development Lifecycles 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa SE351 Roadmap Introduction to Software Project Management Project Management Software Development Life Cycles Requirements Engineering Software Process & Project Metrics Software Project Planning Project Monitoring & Control Risk Management Software Quality Assurance 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 2
2 Outlines Software Lifecycles/Software Development Lifecycles Main Phases of SLC Major SLC Models ISO/IEC Software Lifecycle Process 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 3 The Objective is High quality Product Successful Development Process 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 4
3 Software Project Management Machine Process SDLC PMLC 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 5 PMLC Scope the Project State the problem or opportunity Establish the project goal Define the project objectives Identify the success criteria List assumptions, risks and obstacles Launch the Plan Recruit and organize project team Establish team operating rules Level project resources Schedule work packages Document work packages Project Close-Out Obtain client acceptance Install project deliverables Complete project documentation Complete post-implementation audit Issue final project report Develop Detailed Plans Identify project activities Estimate activity duration Determine resource requirements Construct & analyze project network Prepare the project proposal Monitor & Control Progress Establish progress reporting system Install change control process Define problem escalation process Monitor progress versus plan Revise project plan 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 6
4 Software Lifecycle: Main Phases 1. Requirements Analysis 2. Design 3. Implementation 4. Testing 5. Delivery/Deployment 6. Maintenance SDLC SLC 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 7 PMLC vs. SDLC Scope the Project Scope the Project Develop Detailed Plans Develop Detailed Plans Request Initiation Business Requirements Success Criteria Develop Requirements Establish Phase Review Schedule Launch the Plan Launch the Plan Identify the Development Team Build the System Monitor & Control Progress Monitor & Control Progress Monitor Progress Conduct Subsystem Test Conduct Acceptance Test Project Close-Out Project Close-Out Evaluate System Performance Conduct Post-Project Review 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 8
5 Cost vs. Phases 15% 6% 15% 18% 15% 21% 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 9 Software Development Lifecycle: Major Models Build It & Fix It Waterfall Rapid Prototyping Incremental Spiral Agile 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 10
6 Waterfall Model Requirements/ Specifications Verify Software Requirements Specification Design Verify Design Document Implementation Test Software System Integration Test Operations Manual Operations 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 11 Waterfall Model: Strengths Emphasis on early planning, client input, and design Emphasis on testing as an integral part of the lifecycle Document driven: per phase Emphasis on completion of one phase before moving on!! Weaknesses Sequential flow is not practical Depends on capturing and freezing requirements early in the lifecycle High blocking states No working version of the system until the end of the cycle Technical documents usually are not appropriate for communication 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 12
7 Rapid Prototyping Model Requirements/ Specifications Verify Develop Prototype Software Requirements Specification Design Verify Design Document Implementation Test Software System Integration Test Operations Manual Operations 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 13 Rapid Prototyping Strengths Avoids building systems to bad requirements Enable requirements and design to be communicated more clearly between Participants More requirements and design faults are caught early Weaknesses Lengthy requirements phase Need to throw away Temptation to release product early o the prototype may become the production system 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 14
8 The Incremental Model Breakdown design into builds Modules that can stand alone increment 1 analysis design code test delivery of 1st increment increment 2 analysis analysis design code code test delivery test of 2nd increment increment 3 analysis design code test delivery of 3rd increment 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 15 Spiral Model: Risk Management Determine risks involved in developing product Deal with risks in turn (resolve, minimize) Assessment Pushing limits of technology Assessing costs frequently 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 16
9 Spiral Model: A Simplified Version Planning Risk Analysis Evaluation Engineering 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 17 Spiral Model(Cont.) (Cont.) Strengths Emphasis on risk reduction techniques, o such as prototypes, COTS vs. In-house Assess cost-benefit Provides checkpoints for considering project cancellation Weaknesses Appropriate for large projects Full scale risk analysis requires training, skill, and considerable expense Internal (in-house) software 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 18
10 Agile Software Development Processes Are based on three key assumptions It is difficult to predict in advance o which requirements or customer priorities will change In many types of software o design and construction activities are interleaved (construction is used to prove the design) Analysis, design, and testing are not as predictable from a planning perspective as one might like them to be 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 19 Agile Software Development Processes Agile processes must be adapted incrementally to manage unpredictability It requires customer feedback o based on evaluation of delivered software increments (executable prototypes) over short time periods 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 20
11 Agile Software Development Encourages customer involvement and satisfaction incremental software delivery o o Stresses small project teams (software engineers & stakeholders) minimal software engineering work products continuous communication and collaboration (among developers and customers) on-time delivery of an operational software increment over analysis and design If applied effectively, it can deliver successful systems quickly 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 21 Extreme Programming (XP) Relies on object-oriented approach Key activities Planning o Design o Coding o Testing o o user stories created and ordered by customer value simple designs preferred, CRC cards and design prototypes are only work products, encourages use of re-factoring emphasizes on use of pairs programming to create story code, continuous integration and smoke testing is utilized unit tests created before coding are implemented using an automated testing framework to encourage use of regression testing, integration and validation testing done on daily basis, o acceptance tests focus on system features and functions viewable by the customer 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 22
12 XP-SDLC 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 23 Other Process Models Component assembly model reuse is a development objective Formal methods mathematical specification is to be developed Cleanroom software engineering emphasizes error detection before testing 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 24
13 ISO/IEC SLC Standard 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 25 ISO/IEC PURPOSE Establish a common framework for software lifecycle 1. To acquire, supply, develop, operate, and maintain software 2. To manage, control, and improve the framework 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 26
14 ISO12207 :Background International Organization for Standardization ISO ESTABLISHED: 1987 International Electrotechnical Commission IEC JTC1 Joint Technical Committee OBJECT: TO CARRY ON STANDARDIZATION WORK IN INFORMATION TECHNOLOGY SC1 - Vocabulary SC2 - Character sets & information coding SC6 - Telecommunications & information exchange between systems SC7 - Software engineering SC11 - Flexible magnetic media for digital data interchange SC14 - Representation of data elements SC15 - Labelling and file structure SC17 - Identification cards & related devices SC18 - Document processing and related communication SC21 - Information retrieval, transfer & management for OSI SC22 - Programming languages, their environments & systems software interfaces SC23 - Optical disk cartridges for information interchange SC24 - Computer graphics and image processing SC25 - Interconnection of information technology equipment SC26 - Microprocessor systems SC27 - IT security techniques SC28 - Office equipment SC29 - Coded representation of picture, audio and multimedia/hypermedia information 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 27 Background (Cont.) History: Proposed in June Working Drafts; 2 Committee Drafts Over 6 years and 17,000 person-hours Published 1 August 1995 Participants: Countries: Australia, Canada, Denmark, Finland, France, Germany, Ireland, Italy, Japan, Korea, Netherlands, Spain, Sweden, UK, USA 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 28
15 Relationship to System Areas SYSTEM ENGINEERING INFORMATION TECHNOLOGY CONVENTIONAL ENGINEERING ENGINEERING [12207] 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 29 Establishes Link With System Engineering Software treated as a part of the system System engineering activities are the foundation of software engineering Necessary system context provided Software activities placed under the context Software extracted from and integrated into the system Software engineering participates in system engineering 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 30
16 The Engineering View of ISO/IEC Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 31 DEVELOPMENT PROCESS SYSTEM ORGANIZATION SYSTEM HI X SI X MO SC SC SU SU SU SU HI- Hardware Item; SI- Software Item; MO- Manual Operations; SC- Software Component; SU- Software Unit; X- Other 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 32
17 A Management Complement ISO not a substitute for systematic, disciplined management Rather, ISO complements the management practices It provides a powerful and complete but flexible set of building blocks of a software lifecycle for a project and an organization to use as appropriate and effective 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 33 ISO12207 Concepts ISO describes 17 processes Each process is divided into "activities," and o the activities into "tasks," while placing requirements upon their execution 5 primary processes For major functions and primary parties 1. acquisition 2. supply 3. development 4. operation 5. maintenance 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 34
18 Primary Processes OPERATION 0 ACQUISITION SUPPLY DEVELOPMENT MAINTENANCE 0 DEVELOPMENT PLAN, DO, CHECK & ACT 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 35 ISO12207 Concepts(Cont.) (Cont.) 8 supporting processes For supporting other processes with a purpose 1. Documentation 2. Configuration Management 3. Quality Assurance 4. Verification 5. Validation 6. Joint Review 7. Audit 8. Problem Resolution 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 36
19 ISO Concepts(Cont.) 4 organizational processes For corporate level management and improvement 1. Management 2. Infrastructure 3. Improvement 4. Training Tailoring Processes To formalize tailoring of the standard o The intention for organizations is to tailor these 17 processes to fit the scope of their particular projects by deleting all inapplicable activities; and it defines compliance as the performance of those processes, activities, and tasks selected by tailoring 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 37 ISO Concepts Process Tree ACQUISITION SUPPLY DEVELOPMENT OPERATION MAINTENANCE PRIMARY Lifecycle SUPPORTING DOCUMENTATION CONFIGURATION MANAGEMENT QUALITY ASSURANCE VERIFICATION VALIDATION JOINT REVIEW AUDIT PROBLEM RESOLUTION ORGANIZATIONAL MANAGEMENT INFRASTRUCTURE IMPROVEMENT TRAINING TAILORING
20 Development Process FOR THE DEVELOPER (MODIFIER) OF PRODUCTS -May Perform or Support some System Engineering - Activities not necessarily in time order ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS Development Process FOR THE DEVELOPER (MODIFIER) OF PRODUCTS -May Perform or Support some System Engineering - Activities not necessarily in time order ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS 1. PROCESS IMPLEMENTATION 2. SYS. REQ. ANALYSIS 3. SYS. ARCH. DESIGN DOCUMENTATION C.M. PROBLEM RESOLUTION EVALUATIONS EVALUATIONS DEVELOPMENT PLANS & MODELS SYSTEM REQUIREMENTS SYS. ARCHITECTURE - HW, SW, MO 4. SOF. REQ. ANALYSIS EVALUATIONS ISO/IEC 9126 JT. REVIEWS REQUIREMENTS 5. SOF. ARCH. DESIGN EVALUATIONS JT. REVIEWS ARCHITECTURE 6. SOF. DET. DESIGN EVALUATIONS JT. REVIEWS DET. DESIGN 7. SOF. CODE/TEST EVALUATIONS CODE/DATABASE 8. SOF. INTEGRATION EVALUATIONS JT. REVIEWS INTEGRATED (SCIs) 9. SOF. QUALIF. TEST EVALUATIONS AUDITS DESIGN & CODE 10. SYS. INTEGRATION EVALUATIONS INTEGRATED 11. SYS. QUALIF. TEST EVALUATIONS AUDITS DESIGN & CODE 12. SOF. INSTALLATION 13. SOF. ACCPT. SUPPORT EVALUATIONS INSTALLATION PLAN INSTALLED SOFT. DELIVERABLE
21 Development Process FOR THE DEVELOPER (MODIFIER) OF PRODUCTS - May Perform or Support some System Engineering - Activities not necessarily in time order ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS 4. SOF. REQ. ANALYSIS EVALUATIONS ISO/IEC 9126 JT. REVIEWS 5. SOF. ARCH. DESIGN EVALUATIONS JT. REVIEWS 6. SOF. DET. DESIGN EVALUATIONS JT. REVIEWS 7. SOF. CODE/TEST EVALUATIONS 8. SOF. INTEGRATION EVALUATIONS JT. REVIEWS REQUIREMENTS ARCHITECTURE DET. DESIGN CODE/DATABASE INTEGRATED 9. SOF. QUALIF. TEST EVALUATIONS AUDITS DESIGN & CODE 12. SOF. INSTALLATION EVALUATIONS 13. SOF. ACCPT. SUPPORT INSTALLATION PLAN INSTALLED SOFT. DELIVERABLE DEVELOPMENT PROCESS ACTIVITIES & TASKS 1. Process Implementation 3. System Architectural Design Define/Select lifecycle Model(s) Employ Regularly Doc, CM, & Prob. Res. Processes Select/Tailor internal Methods/Tools/ Develop, Doc., Execute plans May use non-deliverables - Avoid dependency of future operations & maintenance 2,3,10,11 System Activities Perform or support 4-9, 12,13 Software Activities Produce an Architecture of the system Identify HW, SW, & Manual Operations 5. Sfotware Architectural Design Produce an architecture of the SW system Identify components of the SW system 8. Software Integration 10. System Integration Integration in aggregates partition & Integration Paths may be different Perform
22 Operation Process For the Operator of a system contains software QUALITY LINES ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS PROCESS IMPLEMENTATION PROBLEM RESOLUTION MAINTENANCE - OPERATION PLAN - OPERATION PROCEDURES OPERATIONAL TESTING INTERNAL TESTING & ENSURANCE RELEASED OPERATIONAL SYSTEM OPERATION FUNCTIONS PERFORMED USER SUPPORT - USER REQUESTS - PROBLEM RESOLUTIONS 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 43 OPERATION PROCESS ACTIVITIES & TASKS 1. PROCESS IMPLEMENTATION Develop Operational Plan Set Operational Standards Document & execute plan Establish procedures for/with problem resolutions Establish procedures for operational testing Establish procedures for interfacing with maintenance process Establish procedures for releasing products for operational use 2. OPERATIONAL TESTING Perform Operational testing for each release Release after criteria met Ensure code/database perform as planned 3. SYSTEM OPERATION Operate in environment 4. USER SUPPORT Proved assistance to users Forward user requests to maintenance as needed For temporary fixes, provide option to use it
23 Maintenance Process For the Maintainer of Software Product QUALITY FIXING HD ACTIVITIES INTERNAL USE INVOKED PROCESSES OUTPUTS PROCESS IMPLMENT. PROBLEM RESOLUTN. CM -MAINTENANCE PLANS/PROCS. PROB/MOD. ANALYSIS - PROB./MOD. ANAL/SOLN. MOD. IMPLEMENT. DEVELOPMENT MODIFIED MAINT. REVIEW/ ACCEPT. INTERNAL REVIEWS REVIEW RESULTS MIGRATION INTERNAL REVIEWS -MIGRATION PLANS/REPORTS - MIGRATED SYS. RETIREMENT - RETIREMENT PLANS - ARCHIVES 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 45 Maintenance Process Activities & Tasks 1. PROCESS IMPLEMENTATION 3. MODIFICATION IMPLEMENTATION 5. MIGRATION Develop, document and execute plan Establish procedures for problem reports and modifications requests Manage modifications Determine targets of modifications Use Development Process for mods. Supplement with testing to ensure modified and unmodified parts are correctly done Develop/document/ execute plan Notify users, etc. Do parallel operations Do post-operations for impact 2. PROBLEM/MODIFICATION ANALYSIS Analyze modifications for impacts Replicate/vefify problems Implement modifications Document and get approval 4. MAINTENANCE REVIEW/ACCEPTANCE Review with authorizing organization 6. RETIREMENT Develop/document/ execute plan Notify users, etc. Do parallel operations Provide for access to retired data/products
24 Organizational Process For an organization to manage and improve its process at corporate level 1 MANAGEMENT PROCESS PRIMARY PROCESS SUPPORTING PROCESS INFRASTRUCTURE PROCESS IMPROVEMENT PROCESS TRAINING PROCESS 1: Manage following management process 2: Establish infrastructure following infrastructure process 3: Improve following improvement process 4: Train personnel following training process NOTE: Management process is instantiated in primary & supporting processes, because they are managed differently 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 47 Indicators & Metrics PROCESS INDICATOR/METRIC ACQUISITION PROCESS MONITORING - Cost, Schedule, Technical SUPPLIER SELECTION - Capability, Past performance,... PROPOSAL EVALUATION - Technical, Cost, Schedule, Personnel,... AGREEMENT CHANGES - No., Rate, Impact,... ACCEPTANCE PROGRESS - Acceptance criteria, Conformance, Releasability,... JOINT ACTION ITEMS STATUS SUPPLY BID DECISION PROCESS MONITORING - Cost, Schedule, Technical PROBLEM STATUS - By Activity/Task/Source, Trend,... ACCEPTANCE PROGRESS - Acceptance criteria, Conformance, Releasability,... JOINT ACTION ITEMS STATUS
25 Indicators & Metrics(Cont.) (Cont.) Process DEVELOPMENT Indicator/Metric CHANGE STATUS: By Activity/Task, Source, Trend,... PROBLEM STATUS: BY Activity/Task, Source, Trend,... JOINT ACTION ITEMS STATUS TRACEABILITY: - Sys Reqs to Acquisition Needs - Sys Arch Design to Sys Reqs - Soft Reqs to Sys Reqs & Design - Soft Arch Design to Soft Reqs - Soft Det Design to Soft Reqs - Soft Unit to Soft Reqs & Design - Soft Design & Unit to Sys Reqs QUALITY CHARACTERISTICS [ISO/IEC 9126] - Functionality, Reliability, Usability, Efficiency, Maintainability, Portability - Plus their sub-characteristics REQs TESTABILITY STATUS TEST COVERAGE CONSISTENCY: INTERNAL & EXTERNAL CONFORMANCE TO EXPECTED RESULTS FEASIBILITY OF NEXT ACTIVITY FEASIBILITY OF OPERATIONS FEASIBILITY OF MAINTENANCE Indicators & Metrics(Cont.) (Cont.) Process Indicator/Metric OPERATION OPERATIONAL CHARACTERISTICS - Run time, Throughput, Availability, Responsiveness,... OPERATIONAL TESTING - Coverage, Releasability,... USER SUPPORT - Status of requests, support, releases,... MAINTENANCE STATUS: PROBLEM REPORTS & MODIFICATION REQUESTS - Measure of classification, size, criticality, closure,... - Impact on operations & maintenance TEST COVERAGE OF - Modified parts - Unmodified parts IMPACT ON UNMODIFIED PARTS MIGRATION PORTABILITY USER SUPPORT DURING MIGRATION POST-OPERATION IMPACT OF MIGRATION USER SUPPORT DURING RETIREMENT
26 ROLE? Primary Roles ACQUISITION ROLE SUPPLY ROLE OPERATING ROLE ACQUIRER SUPPLIER OPERATOR USER employ ACQUISITION PROCESS contract SUPPLY PROCESS employ employ OPERATION PROCESS employ employ employ S U P P O R T I N G ENGINEERING ROLE SUPPORTING ROLE DEVELOPER MAINTAINER EMPLOYER OF SUPPORTING PROCESSES use MAINTENANCE PROCESS use Documentation Configuration management Quality assurance Verification DEVELOPMENT PROCESS employ Validation Joint review Audit Problem resolution P R O C E S S E S ORGANIZATIONAL ROLE MANAGER ORGANIZATIONAL PROCESSES Management Infrastructure Improvement Training 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 51 Prototyping in Not listed as an activity of the Development Process - Treated as a method/technique for: - Performing studies, requirements analysis, design, etc. 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 52
27 Relationships to Quality Areas QUALITY MATURITY ISO 9002 QUALITY SYSTEM REQUIREMENTS SPICE/CMM QUALITY SYSTEM REQUIREMENTS Lifecycle PROCESSES REQUIREMENTS ISO/IEC Lifecycle Lifecycle PRACTICES 06 Oct, 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa 53
Chapter 1. Software Engineering Supporting Processes
Chapter 1 Software Engineering Supporting Processes 1. Introduction to IEEE/EIA Standard 12207.0-1996 IEEE/EIA Standard 12207.0-1996 establishes a common framework for software life cycle processes. The
More information1 Introduction to Software Engineering Standards
1 Introduction to Software Engineering Standards Francois Coallier ISO/IEC JTC1/SC7 Secretary, Bell Canada, Canada* Prof. Motoei Azuma ISO/IEC JTC1/SC7/WG6 Convenor, Waseda University, Japan The SPICE
More informationSoftware Engineering
Software Engineering (CS550) Software Development Process Jongmoon Baik Software Development Processes (Lifecycle Models) 2 What is a S/W Life Cycle? The series of stages in form and functional activity
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Building Skills is a 3-day course that is a subset of our course. The course is designed to provide a fundamental knowledge base and practical skills for anyone interested in implementing or improving
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Courses is a 2-day course that is a subset of our course. The course is designed to provide an overview of techniques and practices. This course starts with an overview of software quality engineering
More informationPART THREE: Work Plan and IV&V Methodology (RFP 5.3.3)
PART THREE: Work Plan and IV&V Methodology (RFP 5.3.3) 3.1 IV&V Methodology and Work Plan 3.1.1 NTT DATA IV&V Framework We believe that successful IV&V is more than just verification that the processes
More informationMeasuring and Assessing Software Quality
Measuring and Assessing Software Quality Issues, Challenges and Practical Approaches Kostas Kontogiannis Associate Professor, NTUA kkontog@softlab.ntua.gr The Software Life Cycle Maintenance Requirements
More informationLecture 2: Software Quality Factors, Models and Standards. Software Quality Assurance (INSE 6260/4-UU) Winter 2016
Lecture 2: Software Quality Factors, Models and Standards Software Quality Assurance (INSE 6260/4-UU) Winter 2016 INSE 6260/4-UU Software Quality Assurance Software Quality Quality Assurance Factors and
More informationISO/IEC JTC1/SC7 N2182
ISO/IEC JTC1/SC7 Software Engineering Secretariat: CANADA (SCC) ISO/IEC JTC1/SC7 N2182 1999/07/19 Document Type Title Source Proposed Draft Amendment 12207/PDAM 1 - Software Engineering - Life Cycle Processes.
More informationChapter 6. Software Quality Management & Estimation
Chapter 6 Software Quality Management & Estimation What is Quality Management Also called software quality assurance (SQA) s/w quality:- It is defined as the degree to which a system, components, or process
More informationCMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide
processlabs CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide CMMI-DEV V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAR - Causal Analysis and Resolution...
More informationTopics. Background Approach Status
16 th September 2014 Topics Background Approach Status Background e-governance in India National e-governance Plan 2006 31 Mission Mode Projects Quality Assurance in e-governance Quality Assessment of
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2 Friday 30 th September 2016 - Morning Answer any THREE questions
More informationNATO Integrated Quality Requirements for Software throughout the Life Cycle
NATO Integrated Quality Requirements for Software throughout the Life Cycle Edition 1 (July 2001) -i- -ii- NORTH ATLANTIC TREATY ORGANIZATION MILITARY AGENCY FOR STANDARDIZATION (MAS) NATO LETTER OF PROMULGATION
More informationCONTENTS. Introduction to Software Engineering. Software Process and Life Cycle Models. Software Life-Cycle Model-2. Chapter 1. Chapter 2.
Contents (v) CONTENTS Preface About the Author (xv) (xvii) Chapter 1 Introduction to Software Engineering 1.1 Introduction 1 1.2 Basics of Software Engineering 2 1.3 Principles of Software Engineering
More informationContents. List of Acronyms Preface
Contents List of Acronyms Preface xi xv PART I Introduction 1 1 Introduction 3 1.1 The evolution of medical purpose software 3 1.2 Product quality and software quality 4 1.3 On the need for quality in
More informationThis is a preview - click here to buy the full publication INTERNATIONAL STANDARD
This is a preview - click here to buy the full publication INTERNATIONAL STANDARD ISO/IEC 12207 First edition 1995-08-01 Information technology - Software life cycle processes Technologies de / information
More informationCMMI Version 1.2. Model Changes
Pittsburgh, PA 15213-3890 CMMI Version 1.2 Model Changes SM CMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University. Capability Maturity Model, Capability Maturity Modeling,
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 informationQUALITY ASSURANCE PLAN OKLAHOMA DEPARTMENT OF HUMAN SERVICES ENTERPRISE SYSTEM (MOSAIC PROJECT)
QUALITY ASSURANCE PLAN OKLAHOMA DEPARTMENT OF HUMAN SERVICES ENTERPRISE SYSTEM (MOSAIC PROJECT) MOSAIC Quality Assurance Plan v04.02 Prepared by: Approved by: QUALITY ASSURANCE PLAN APPROVALS QA/QC Program
More informationThe Systems Development Lifecycle
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system developments projects The project Major attributes of the Lifecycle Moves systematically
More informationCMSC 435: Software Engineering Section Back to Software. Important: Team Work. More Resources
CMSC 435: Software Engineering Section 0101! Atif M. Memon (atif@cs.umd.edu)! 4115 A.V.Williams building! Phone: 301-405-3071! Office hours!.tu.th. (10:45am-12:00pm)! Don t wait, don t hesitate, do communicate!!!
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 informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More informationSummary of TL 9000 R4.0 Requirements Beyond ISO 9001:2000
This summary identifies the additional TL 9000 Release 4.0 requirements beyond those stated in ISO 9001:2000. See the TL 9000 R4.0 Handbook for the actual TL 9000 R4.0 requirements. ISO 9001:2000 section
More informationR214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION PROGRAM
A2LA R214 Specific Requirements: Information Technology Testing Laboratory Accreditation Document Revised: 3/5/18 Page 1 of 34 R214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION
More informationThis resource is associated with the following paper: Assessing the maturity of software testing services using CMMI-SVC: an industrial case study
RESOURCE: MATURITY LEVELS OF THE CUSTOMIZED CMMI-SVC FOR TESTING SERVICES AND THEIR PROCESS AREAS This resource is associated with the following paper: Assessing the maturity of software testing services
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationCMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide
processlabs CMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide CMMI-SVC V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAM - Capacity and Availability Management...
More informationIntroduction to Software Project Management. CITS3220 Software Requirements & Project Management
Introduction to Software Project Management CITS3220 Software Requirements & Project Management "A project gets a year late one day at a time." "Anything that can be changed will be changed until there
More informationCSE 435 Software Engineering. Sept 14, 2015
CSE 435 Software Engineering Sept 14, 2015 What is Software Engineering Where Does the Software Engineer Fit In? Computer science: focusing on computer hardware, compilers, operating systems, and programming
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 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 informationTest Workflow. Michael Fourman Cs2 Software Engineering
Test Workflow Michael Fourman Introduction Verify the result from implementation by testing each build Plan the tests in each iteration Integration tests for every build within the iteration System tests
More informationSystems and software engineering Software life cycle processes
INTERNATIONAL STANDARD ISO/IEC/ IEEE 12207 First edition 2017-11 Systems and software engineering Software life cycle processes Ingénierie des systèmes et du logiciel Processus du cycle de vie du logiciel
More informationSoftware Engineering
Software Engineering Part I. Aspects and Models of Software Development Process Gunadarma University 1 Software Engineering Outline 1 Introduction 2 Aspects of Software Engineering Software Engineering
More informationECSS. Space engineering
-E-40B Draft 1 EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space engineering Software This document is a draft standard circulated for review and comments. It is therefore subject to change and may
More informationWork Plan and IV&V Methodology
Work Plan and IV&V Methodology Technology initiatives and programs should engage with an IV&V process at the project planning phase in order to receive an unbiased, impartial view into the project planning,
More informationSOFTWARE DEVELOPMENT STANDARD
SFTWARE DEVELPMENT STANDARD Mar. 23, 2016 Japan Aerospace Exploration Agency The official version of this standard is written in Japanese. This English version is issued for convenience of English speakers.
More informationIndependent Verification and Validation (IV&V)
Independent Verification and Validation (IV&V) 12 th Annual NDIA CMMI Conference November 2012 - Denver, CO The MITRE Corporation The author s affiliation with The MITRE Corporation is provided for identification
More informationThis document is a preview generated by EVS
INTERNATIONAL STANDARD ISO/IEC/ IEEE 12207 First edition 2017-11 Systems and software engineering Software life cycle processes Ingénierie des systèmes et du logiciel Processus du cycle de vie du logiciel
More informationCMMI V2.0 MODEL AT-A-GLANCE. Including the following views: Development Services Supplier Management. CMMI V2.0 outline BOOKLET FOR print.
CMMI V.0 MODEL AT-A-GLANCE Including the following views: Development Services Supplier Management CMMI V.0 outline BOOKLET FOR print.indd CMMI V.0 An Integrated Product Suite Designed to meet the challenges
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 informationQuality management systems
L E C T U R E 9 Quality management systems LECTURE 9 - OVERVIEW Quality management system based on ISO 9000 WHAT IS QMS (QUALITY MANAGEMENT SYSTEM) Goal: Meet customer needs Quality management system includes
More informationSoftware Quality Engineering where to find it in Software Engineering Body of Knowledge (SWEBOK)
Software Quality Engineering where to find it in Software Engineering Body of Knowledge (SWEBOK) Witold Suryn 1, Anabel Stambollian 2, Jean-Charles Dormeux 3, Luc Bégnoche 4 1 Software and Information
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 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 informationGAMP Guideline & Validation Documentation
GAMP Guideline & Validation Documentation Danilo Maruccia Milano, 21 Marzo 2006 GAMP Guideline & Validation Documentation GAMP Guideline Planning documents Specification Documents Testing Documents Acceptance
More informationCLASS/YEAR: II MCA SUB.CODE&NAME: MC7303, SOFTWARE ENGINEERING. 1. Define Software Engineering. Software Engineering: 2. What is a process Framework? Process Framework: UNIT-I 2MARKS QUESTIONS AND ANSWERS
More informationRational Software White Paper TP 174
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP 174 Table of Contents Abstract... 1 Introduction... 1 Level 2, Repeatable... 2 Requirements Management...
More informationHow the Rational Unified Process Supports ISO 12207
How the Rational Unified Process Supports ISO 12207 by Philippe Kruchten Director of Process Development Rational Software Canada "My organization must comply with the ISO Standard 12207; can the RUP help
More informationISTQB-Level1 ASTQB. American Software Testing Qualifications Board Level 1
ASTQB ISTQB-Level1 American Software Testing Qualifications Board Level 1 Download Full Version : https://killexams.com/pass4sure/exam-detail/istqb-level1 QUESTION: 46 Comparing TMMi and TPI, which is
More informationThis document describes the overall software development process of microcontroller software during all phases of the Company Name product life cycle.
Maturity Process Owner Check Release Description Valid Name / Department Name / Department Name / Department Detailed procedure for software development Title: Software Development Procedure Purpose: This
More informationISO/IEC INTERNATIONAL STANDARD. Software and systems engineering Tools and methods for product line technical management
INTERNATIONAL STANDARD ISO/IEC 26555 First edition 2013-03-01 Software and systems engineering Tools and methods for product line technical management Ingénierie du logiciel et des systèmes Outils et méthodes
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 informationNATO STANDARD AQAP-2210
NATO STANDARD AQAP-2210 NATO SUPPLEMENTARY SOFTWARE QUALITY ASSURANCE REQUIREMENTS TO AQAP-2110 OR AQAP-2310 Edition A Version 2 September 2015 NORTH ATLANTIC TREATY ORGANIZATION ALLIED QUALITY ASSURANCE
More information7. Model based software architecture
UNIT - III Model based software architectures: A Management perspective and technical perspective. Work Flows of the process: Software process workflows, Iteration workflows. Check Points of The process
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 informationThe software process
The software process Process product Process properties Cost Effort Hours worked Punctuality Outline Activities Production (requirements, design, implementation), verification, management Phases Development,
More informationISO /TS 29001:2010 SYSTEMKARAN ADVISER & INFORMATION CENTER SYSTEM KARAN ADVISER & INFORMATION CENTER
SYSTEM KARAN ADVISER & INFORMATION CENTER PETROLEUM, PETROCHEMICAL AND NATURAL GAS INDUSTRIES -- SECTOR-SPECIFIC QUALITY MANAGEMENT SYSTEMS -- REQUIREMENTS FOR PRODUCT AND SERVICE SUPPLY ORGANIZATIONS
More informationDarshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1
Failure Rate Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1 SOFTWARE (What is Software? Explain characteristics of Software. OR How the software product is differing than
More informationISO/IEC JTC1/SC7 N2683
ISO/IEC JTC1/SC7 Software & System Engineering Secretariat: CANADA (SCC) ISO/IEC JTC1/SC7 N2683 2002-07-25 Document Type PDTR Ballot Title PDTR 19760 Systems Engineering Guide for ISO/IEC 15288 (System
More informationCS350 Lecture 2 Software Dev. Life Cycle. Doo-Hwan Bae
CS350 Lecture 2 Software Dev. Life Cycle Doo-Hwan Bae bae@se.kaist.ac.kr Whose Drawings? Watts Humphrey, SE is Religion and Philosophy. Just Follow me! CS350 Software Engineering, SoC, KAIST 2 What is
More informationII. Software Life Cycle. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini
II. Software Life Cycle Laurea Triennale in Informatica Corso di Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process
More informationReflection on Software Process Improvement
Reflection on Software Process Improvement Keynote for SEPG Conference in Japan - 2005 John D. Vu, Ph. D Technical Fellow The Boeing Company BOEING is a trademark of Boeing Management Company. John Vu
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 informationBuilding High Assurance Systems with SAFe 4.0
Building High Assurance Systems with SAFe 4.0 Agile 2016 By Dean Leffingwell 2016 Scaled Agile, Inc. All Rights Reserved. 2016 Scaled Agile, Inc. All Rights Reserved. V4.0.0 1 What is a high assurance
More informationApplying Software Engineering Standards in Small settings
Applying Software Engineering Standards in Small settings Recent historical perspective and Initial Achievements Claude Y Laporte École de technologie supérieure Editor SC 7/Working Group 24 Content Introduction
More informationSystems Engineers provide a Key Contribution and Role in System Integration and Test
s Engineers provide a Key Contribution and Role in Integration and Test National Defense Industrial Association (NDIA) 9 th Annual s Engineering Conference October 23-26/2006 Test & Evaluation Track, Tuesday
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 informationCapability Maturity Model for Software (SW-CMM )
PHASE-IV: SYSTEMS IMPLEMENTATION Software Quality Assurance Application Development Installation and Support Software Quality Assurance Capability Maturity Model for Software (SW-CMM ) The Capability Maturity
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 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 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 informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers UNIT 1 1. What are software myths Answer: Management myths: We already have a book
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 informationversion NDIA CMMI Conf 3.5 SE Tutorial RE - 1
Requirements Engineering SE Tutorial RE - 1 What Are Requirements? Customer s needs, expectations, and measures of effectiveness Items that are necessary, needed, or demanded Implicit or explicit criteria
More informationABHELSINKI UNIVERSITY OF TECHNOLOGY
T 76.3601 Introduction to Software Engineering Software Life-Cycle Models http://www.soberit.hut.fi/t-76.3601/ Casper.Lassenius@tkk.fi Software Engineering? 1. The application of a systematic, disciplined,
More informationMapping of Fusion Process Model onto ISO/IEC 12207:2008
Mapping of Fusion Model onto ISO/IEC 12207:2008 Rupinder Kaur; Jyotsna Sengupta Department of Computer Science; Punjabi University Patiala, India rupadeo@gmail.com Abstract Fusion Model is a component
More informationSoftware configuration management
Software configuration management Bởi: Hung Vo Introduction A system can be defined as a collection of components organized to accomplish a specific function or set of functions. The configuration of a
More informationProgram Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
More informationCHAPTER 2. Slide 2.1 THE SOFTWARE PROCESS
CHAPTER 2 Slide 2.1 THE SOFTWARE PROCESS Overview Slide 2.2 Client, Developer, and User Requirements Phase Specification Phase Design Phase Implementation Phase Integration Phase Maintenance Phase Retirement
More informationSoftware Engineering Part 2
CS 0901341 Software Engineering Part 2 In this part, we look at 2.1 Software Process 2.2 Software Process Models 2.3 Tools and Techniques for Processing Modelling As we saw in the previous part, the concept
More informationT Software Testing and Quality Assurance Test Planning
T-76.5613 Software Testing and Quality Assurance 10.10.2007 Test Planning Juha Itkonen Outline Test planning, purpose and usage of a test plan Topics of test planning Exercise References: IEEE Std 829-1998,
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 informationISO9001:2008 SYSTEM KARAN ADVISER & INFORMATION CENTER QUALITY MANAGEMENT SYSTEM SYSTEM KARAN ADVISER & INFORMATION CENTER
SYSTEM KARAN ADVISER & INFORMATION CENTER QUALITY MANAGEMENT SYSTEM WWW.SYSTEMKARAN.COM 1 www.systemkaran.org Foreword... 5 Introduction... 6 0.1 General... 6 0.2 Process approach... 6 0.3 Relationship
More informationEUROCONTROL Guidance Material for Approach Path Monitor Appendix B-2: Generic Safety Plan for APM Implementation
EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION EUROCONTROL EUROCONTROL Guidance Material for Approach Path Monitor Appendix B-2: Generic Safety Plan for APM Implementation Edition Number : 1.0
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 informationA Continuous Improvement Approach for Medical Device Software Development Companies. Dr. Özden Özcan-Top - Dr. Fergal Mc Caffery
A Continuous Improvement Approach for Medical Device Software Development Companies Dr. Özden Özcan-Top - Dr. Fergal Mc Caffery 12/07/2017 Lero 2015 1 Dr. Özden Özcan - Top Dr. Fergal Mc Caffery Dundalk
More informationNext Generation Design and Verification Today Requirements-driven Verification Methodology (for Standards Compliance)
Next Generation Design and Verification Today Requirements-driven Verification Methodology (for Standards Compliance) Mike Bartley, TVS Agenda Motivation - Why Requirements Driven Verification? Introduction
More informationQuEST Forum. TL 9000 Quality Management System. Requirements Handbook
QuEST Forum TL 9000 Quality Management System Requirements Handbook Point Release 6.1 The ICT Quality Management System Performance Excellence through Global ICT Quality Copyright Copyright 2017 Quality
More informationExplore Comparative Analysis Software Development Life Cycle Models
Explore Comparative Analysis Software Development Life Cycle Models Anshu Mishra Assistant Professor, Department of Information Science and Engineering Jyothy Institute of Technology, Bangalore Abstract-The
More informationThe Top Thrill Dragster
EEC 421/521: Software Engineering The Software Process Prescriptive Process Models 1/22/08 EEC 421/521: Software Engineering 1 The Top Thrill Dragster 420 ft tall Max speed over 120 mph World s second
More informationNumber: DI-IPSC-81427B Approval Date:
DATA ITEM DESCRIPTION Title: Software Development Plan (SDP) Number: Approval Date: 20170313 AMSC Number: N9775 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: EC Project Number:
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 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 informationEvolutionary Differences Between CMM for Software and the CMMI
Evolutionary Differences Between CMM for Software and the CMMI Welcome WelKom Huan Yín Bienvenue Bienvenido Wilkommen????S???S??? Bienvenuto Tervetuloa Välkommen Witamy - 2 Adapting an An Integrated Approach
More information9/24/2011 Sof o tw t a w re e P roc o e c s e s s s Mo M d o e d l e s l 1 Wh W a h t t i s i s a Pr P oc o ess s 2 1
Software Process Models 1 What is a Process 2 1 What is a Process? Given input, transforms it into output Consist of a set of activities Ordering among the activities (a partial order) Software Process
More information