Software Engineering with Dr. Daniel P. Berger and Dr. Philip E. Vandermeer II.

Slides:



Advertisements
Similar presentations
PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Advertisements

Slide Set to accompany Web Engineering: A Practitioner’s Approach
Chapter 2 The Software Process
May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Release & Deployment ITIL Version 3
Software Engineering Introduction. Why are you here? …alternatively, why do we think you need to be here? Why a course on software engineering? How is.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
Effective Methods for Software and Systems Integration
Chapter : Software Process
Process: A Generic View
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
S/W Project Management
COMPGZ07 Project Management Presentations Graham Collins, UCL
Chapter 2 The process Process, Methods, and Tools
CLEANROOM SOFTWARE ENGINEERING.
Chapter 2 Process: A Generic View
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Chapter 2 Process: A Generic View
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Service Transition & Planning Service Validation & Testing
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
1 Chapter 3 Project Management. 2 Project Management Concerns staffing? cost estimation? project scheduling? project monitoring? other resources? customer.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
Software Engineering - I
Process: A Generic View
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter.
The Software Process Chapter – II. Topics S/w Engg – A layered Technology A Process Framework Process Patterns Process Assessment Product and Process.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 Chapter 2 A Generic View of Process Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
1 2.1 Software Engineering Software engineering is a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software;
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
Software Engineering (CSI 321) Software Process: A Generic View 1.
Software Engineering CE 501 Prepared by : Ashwin Raiyani.
Software Project Management
The Software Engineering Process Discussion Slides.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter 2.
How Software Projects Start SW projects start with a need. We need to keep better data on the students in the CSCE Dept. I heard that one of our competitors.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Software Configuration Management (SCM)
Chapter 2 Object-Oriented Paradigm Overview
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Chapter 2 Process: A Generic View
Software Requirements analysis & specifications
Chapter 3 Project Management
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
The Software Engineering Process
Presentation transcript:

Software Engineering with Dr. Daniel P. Berger and Dr. Philip E. Vandermeer II

Some Quotes “If you’re not serving the customer, you’d better be serving someone who is.” (Karl Albrecht, Ron Zembe) “Behold the turtle. He makes progress only when he sticks his neck out.” (James B. Conant) “Understanding customer needs doesn’t mean asking customers what those needs are. They’ll say only what they think they want.” (Michael Hammer, James Champy) “Good quality is never achieved by accident” (Katsuyoshi Ishihara) “Finding good players is easy. Getting them to play as a team is another story.” (Casey Stengel) “a stakeholder is a person holding a person holding a large and sharp stake…If you don’t look after your stakeholders, you know where the stake will end up.” (Rob Thomsett)

Software Process What is it? “a framework for the tasks that are required to build high-quality software” Different scenarios? COS 264, Final Projects Real-world examples WDD - Software development Other practicums

Generic Process Framework Communication – to determine the appropriate requirements for the project Planning – to create appropriate milestones and goals upon which both parties are agreeable Modeling (prototyping) – to formulate the necessary actions, interfaces, and procedures as it relates to development Construction – build it, test it Deployment – delivery to the customer for evaluation

Umbrella Activities Project Tracking and Control – monitor progress and maintain schedule Risk management – assess possible risks that influence the project’s success Quality Assurance – ensure the project acts as it is intended Formal technical reviews – ”beta testing” Measurement – quantitatively assessing the project’s status Configuration management – carefully manage external changes Reusability management – abstracting work-units (functions, components, modules, procedures) Preparation – detailed logging and documentation

Business Software Process Personal Software Process an individual’s guidelines and procedures for developing an assigned project an individual must record and self- analyze the types of errors they make in order to further their own process improvement Team Software Process comprised of delegated individuals usually operating within a team of similar-minded people using similar processes

Discussion Questions What is your method of process for projects? How would you prioritize the development process? Tools, Methods, Process, Quality Is a software process always necessary for a project? Is a software process always beneficial for a project?