Some Closing Thoughts Software Engineering.

Slides:



Advertisements
Similar presentations
Continuous Assessment of Practice West Midlands Mental Health in H. E. Educators Conference Steve Wilding. Clinical Educator. Bernie Kitchen – Practice.
Advertisements

© 2012 Scott W. Ambler Agile Testing Survey 2012 November 2012 Scott W. Ambler
Using to encourage wider reading.. Two accounts for different courses.
ISNE101 Dr. Ken Cosh. Recap  We’ve been talking about Software…  Application vs System Software  Programming Languages  Vs Natural Languages  Syntax,
Copyright (c) 2003 Howard E. Dow1 Results from Inspecting Test Automation Scripts Howie Dow
1 Quality CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 25, 2004.
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
Team Skill 6 - Building The Right System Part 2: Traceability, Change and Quality (Chapters of the requirements text) CSSE 371 Software Requirements.
CSE 322: Software Reliability Engineering Topics covered: Course outline and schedule Introduction, Motivation and Basic Concepts.
7M701 1 Software Engineering Project Management Sommerville, Ian (2001) Software Engineering, 6 th edition Ch. 4
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
Best Practices In Design Outcomes Of A Survey P. H. King, PhD, PE Joan Walker, PhD Vanderbilt University.
Estimation Wrap-up CSE 403, Spring 2008, Alverson Spolsky.
Verification and Validation Yonsei University 2 nd Semester, 2014 Sanghyun Park.
IT Introduction to Website Development Welcome!
ABET’s coming to Rose! Your involvement Monday, Nov 5, 2012.
Software Engineering ‘The establishment and use of sound engineering principles (methods) in order to obtain economically software that is reliable and.
HFOOAD Chapter 2 Requirements. We create software for a reason. We create software fro people. We need to know what the people want in the software we.
Venue: M038 Date: Monday March 28,2011 Time: 10:00 AM JIC ABET WORKSHOP No.2 Guidelines on: IMapping of PEOs to Mission Statement IIMapping of SOs to PEOs.
Information literacy as a motivator for reading and research Vilve Seiler, Kärt Miil University of Tartu Library, Estonia CoBal , Trakai.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Traceability, Change and Quality – Chapters Requirements Text Steve Chenoweth & Chandan Rupakheti RHIT Question 1.
1 Release Grade – סיפורו של מדד Riki Tzadok – May 2008.
Software Engineering in the Academy Bertrand Meyer IEEE Computer, May 2001.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 24 Delivering the System.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Anton Krbaťa Ján Budáč  Verification: "Are we building the product right ?„  Validation: "Are we building the right product ?"
Guidelines: Prepare at most 20 slides Headwords, no sentences A title for every slide Contents Title Overview Background Approach Summary.
Chap 4. Project Management - Organising, planning and scheduling
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
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.
Project Management effects on software dependability Brendan Murphy Microsoft Research Cambridge, UK.
The Presentation of Self: Performance Distinction between LinkedIn & an E-portfolio Folayemi Akinbolaji Writing with New Media.
Some constructive thoughts on “Choosing the Work Order Management System” that is right for you and your organisation.
IT323 - Software Engineering 2 1 Tutorial 4.  List the main benefits of software reuse 2.
Stephen M. Thebaut Software Engineering Slide 1 Grade Info and Some Closing Thoughts CEN 5035 Software Engineering.
Course: Software Engineering – Design I IntroductionSlide Number 1 What is a specification Description of a (computer) system, which:  is precise;  defines.
Who are your Stakeholders Participants/Learners Facilitator/Trainer Other Service Suppliers Training Manager (and training team) Sponsor/Champion/Influencers.
1 TEAM BUILDING & MANAGEMENT. 2 CONTENTS Generalities The individual The individual in the group To manage the group The group manager The group facing.
Stakeholders in Global Requirements Engineering: Lessons Learned from Practice Written by Daniela Damian Presented by Misako Kobayashi.
Traceability, Change and Quality – Chapters Requirements Text Sriram Mohan/Steve Chenoweth.
BLACKBOARD WIKI TOOL From your Group…. There is a Group Tools menu and from there you select “Group Wiki”
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Primavera p6 Course in Bahrain
Software Reviews Ashima Wadhwa.
Applied Software Testing
Maintenance Issues in Software Engineering
Lecture 0 Software Engineering Course Introduction
Love Guardian Android App
Software Verification and Validation
CSC 480 Software Engineering
Chapter 18 Maintaining Information Systems
Assistant Professor of Computer Science Washington State University
Software Engineering in the Academy
Social and Cultural Issues in Requirements Engineering
Provide the Best Garmin Etrex Support Service Call
Welcome to Microsoft Support Number Welcome to Microsoft Support Number For More Visit on:
Software Engineering in the Academy
Frequently asked questions about software engineering
The audience is listening...
Learning goals and assessment (MBA)
Welcome W 1.2 Introduction to Engineering Design II
11/29/2018 Department of Software Engineering and IT Engineering
This is not safety-critical, but it is financial-critical.
The Project Reel’s five step approach for successful projects
PPT1: Basics of software engineering
ATutor LMS Programmer CustomSoft. Objectives  Atutor learning Management System (LMS) developed by CustomSoft for making learning easy.  Atutor LMS.
PFMEA Summary Process Steps
Presentation transcript:

Some Closing Thoughts Software Engineering

Summary of Important Themes Discipline Planning Development Post-delivery support Avoiding vs. Repairing Defects: Trial & error development (“maybe this will work…”) vs. disciplined design using appropriate tools/ methods (e.g., formal reviews/inspections)

Summary of Important Themes Criticality of RE and Continuous Validation: seeing stakeholders (e.g., end-users) as team members Anticipating and Planning for Change: During development After delivery

Summary of Important Themes Ethical, Professional Behaviour: Critical systems Recognizing limitations Not letting politics interfere Importance of Continuous Process Improvement: Measurement Analysis Change

Thanks for taking the course… Informal feedback/suggestions are welcome and much appreciated -- send me a note.