Course Retrospective Richard Anderson CSE 403 Lecture 27.

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Software Development Life-Cycle Models
Software Process Models
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
CEN nd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Process Models.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
CSE 470 : Software Engineering The Software Process.
Software Engineering 1. Software development – the grand view 2. Requirements engineering.
Informatics 43 – April 28, Fun with Models Fashion Student Model = Ideal.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
SYSTEMS ANALYSIS AND DESIGN INTRODUCTION 1. Systems Analysis and Design is the process people use to create (automated) information systems Systems Analysis.
SYSTEMS ANALYSIS AND DESIGN INTRODUCTION 1. Systems Analysis and Design is the process people use to create (automated) information systems Systems Analysis.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Software Process and Product Metrics
CHAPTER 19 Building Software.
Project Management and Scheduling
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 Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Chapter 2 The process Process, Methods, and Tools
Software Process and Models
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Installation and Maintenance of Health IT Systems
[ §3 : 1 ] 2. Life-Cycle Perspective Overview 2.1 Motivation 2.2 Waterfall Model 2.3 Requirements in Context.
111 Notion of a Project Notes from OOSE Slides – a different textbook used in the past Read/review carefully and understand.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
CSE 308 Software Engineering Software Engineering Strategies.
Improving engineering productivity APEGGA. Improving Productivity Mega Projects  History  What is needed  How will it be done  Division of Labour.
Jump to first page (c) 1999, A. Lakhotia 1 Software engineering? Arun Lakhotia University of Louisiana at Lafayette Po Box Lafayette, LA 70504, USA.
Software Processes n What is a process?  Sequence of steps required to develop or maintain software n Characteristics  prescribes major activities 
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Software Project Management By Deepika Chaudhary.
Prescriptive Process Models Jon Walker. Prescription? What does prescriptive mean?
Software Project Management Team 04 – K15T2. Content Summarizing your view on “Software development process”. Answer 3 question: ◦ What is Software Development.
1 SWE Introduction to Software Engineering Lecture 4.
Chapter 4 프로세스 모델 Process Models
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.
> whoami Yuriy Brun Office: CSE 340
Stand Up Comedy Project/Product Management
Software Engineering for Capstone Courses Richard Anderson CSE 481b Winter 2007.
Software Project Management Iterative Model & Spiral Model.
Principles of Software Engineering: Why Study Software Engineering? COSI 120b, Spring 2005.
18 Aug 2005CSE403, Summer'05, Lecture 17 Lecture 17: Course Retrospective and the Path to Lifelong Learning (Part I) Valentin Razmov.
Project Management Overview U08784Software Project Management Rosemary Phillimore.
Project Management Why do projects fail? Technical Reasons
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.
The Software Engineering Process Discussion Slides.
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.
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.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
1 SYS366 Week 2 - Lecture Visual Modeling and Process.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)
The Software Development Process. Contents  Product Components  Software project staff  Software development lifecycle models.
Advanced Software Engineering Dr. Cheng
Lecture 0 Software Engineering Course Introduction
Quality Assurance: Early Work Items
Software Life Cycle “What happens in the ‘life’ of software”
CSE 403 Software Engineering
System Development Life Cycle
Lecture 02: Software Lifecycle Models
Introduction To software engineering
CSE 403, Software Engineering Lecture 2
Software Processes Process should be
The Waterfall Model Also known as: classic life cycle, the waterfall model, the linear model Rarely projects are sequential (allows iteration indirectly)
Presentation transcript:

Course Retrospective Richard Anderson CSE 403 Lecture 27

Is software different? Methodology for building software very different Fewer reviews Fewer people involved in components Software is far more complicated Different change and update models

Scalability Working with large software systems is inherently different than small systems What does lines of code look like? Difficult to appreciate large scale issues working on a small scale

The bigger picture Building software is rarely the true objective Even for Microsoft! Answering to the customer Complex set of economic and technical constraints

Modeling the Software Process Software life cycles Waterfalls and Spirals Value of modeling Understand process Framework for work process Software construction only a portion of the process

Tradeoffs Engineering is about resource tradeoffs Constraints Money, Time, Resources, Personnel, Environment Where to cut back Quality, Features, Bug fixes, Process, Generality, Schedule,...

Risk Management Developing software is planning under uncertainty Source of risks Assessing and tolerating risks Risk Mitigation

People factors - Teams Increased workforce Diversity of Skills Economics Team organization Team dynamics

People factors - Motivation This single most important factor in determining team success / failure Ways to motivate Ways to demotivate

Requirements Understand what to build Many different formal approaches Functional and non-functional requirements

Design General understanding of design can help the design of software Basic design rules Provide a good conceptual model Make things visible Principle of Mapping Principle of Feedback

Quality assurance Independence of QA Many different aspects of quality Deliverable of QA is information Write it down

Testing Plan for testing from beginning of project Bug management process central in shipping a product

What else????