1 The Software Engineering Education at CSULA Jiang Guo Jose M. Macias June 4, 2010.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software processes 2.
Advertisements

CS487 Software Engineering Omar Aldawud
CS3773 Software Engineering Lecture 01 Introduction.
Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems.
Chapter 2 The Software Process
Difference between project and other assignments  real customer  before programming: negotiations with client to clarify requirements  often.
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics
1 CS 691z/791z Topics on Software Engineering CS 691z/791z Topics on Software Engineering Software Processes Based on Chapter 4 of the book [SE-8] Ian.
Software Engineering General Project Management Software Requirements
CS565 Advanced Software Development (1 unit) Lecturer: Adrian O’Riordan Contact: is Office: prefab, behind.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Difference between project and other assignments real customer before programming: negotiations with client to clarify requirements often changes.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 1- Introduction Dr Richard Clayton &
Software Project Management By Assistant Prof. Samana Zehra
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
Introduction Course outline / Recommended books Course objectives Marks distribution / Schedule Basic concepts of SE and PM Project management framework.
Introduction. Classes: Tuesdays & Thursdays 8:30 – 10:00 am Groups: We will work in a group of 3 Sessions will be highly interactive! Prior learning is.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
Experience with Teaching Software Quality Assurance Dušanka Bošković Computing and Informatics Bachelor Programme Faculty of Electrical Engineering Sarajevo,
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
Issues in Teaching Software Engineering Virendra C. Bhavsar Professor and Director, Advanced Computational Research Laboratory Faculty of Computer Science.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Software Engineering Methodologies (Introduction)
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
GROUP PROJECTS IN SOFTWARE ENGINEERING EDUCATION Jiang Guo Department of Computer Science California State University Los Angeles April 3-4, 2009.
Software EngineeringIntroduction Slide 1 Software Engineering Mr. Ahmad Al-Ghoul.
CS 732 Software Engineering Semester 1/2545 Dr.Choonhapong Thaiupathump.
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
The Guide to the Software Engineering Body of Knowledge
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Introduction to Software Engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 3 Slide 1 Software Processes l Coherent sets of activities for specifying, designing,
Using a Project Model for Assessment of CDIO skills Tomas Svensson, Svante Gunnarsson Linköping University Sweden June
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,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Lecture 3 Software Engineering Models (Cont.)
1 / 18 CS 425/625 Software Engineering Requirements Engineering Processes Based on Chapter 6 of the textbook [Somm00] Ian Sommerville, Software Engineering,
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 1- Introduction Module homepage
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.
CMSC 345, Fall CMSC 345 Software Design and Development Fall 2003 Section 0101 Ms. Susan Mitchell Leave Your Ego at the Door!
Software Engineering. Introduction Objective To familiarize students to the fundamental concepts, techniques, processes, methods and tools of Software.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
UNIT-1 SOFTWARE PRODUCT AND PROCESS: Introduction – S/W Engineering paradigm – Verification – Validation – Life cycle models – System engineering –
© Monica Farrow & Andrew Ireland Software Design F28SD2 Future Horizons Monica Farrow & Andrew Ireland School of Mathematical & Computer Sciences Heriot-Watt.
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
1 Introduction to Software Engineering Wen-Yang Lin Dept. of Computer Science and Information Engineering National University of Kaohsiung February, 2007.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
Software Engineering, 8th edition. Chapter 4 1 Courtesy: ©Ian Sommerville 2006 FEB 13 th, 2009 Lecture # 5 Software Processes.
CS 4311 Software Design and Implementation Spring 2012.
CS 4311 Software Design and Implementation Spring 2013.
AIM : To provide an in-depth knowledge in software engineering paradigms, life cycles and Development processes.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
Chapter 24: Architecture Competence
Introduction to Software Engineering Course Outline
Lecture 0 Software Engineering Course Introduction
Project Management and Information Security
DT249/4 Information Systems Engineering Lecture 0
Practical Software Engineering
SNS College of Engineering Coimbatore
Software Engineering.
Presentation transcript:

1 The Software Engineering Education at CSULA Jiang Guo Jose M. Macias June 4, 2010

2 SE Education: CS337 and CS437 A sequential lab-oriented core courses: CS337 and CS437 Focus on engineering discipline and approaches plan and management design and development verification and validation

Text Books for CS337 and CS437 “Software Engineering A Practitioner’s Approach”, Roger Pressman “Software Engineering”, Ian Sommerville Open to other textbooks

4 SE Education: CS337 Estimation for Software Project Software Project Scheduling Software Process Requirement Engineering Analysis Modeling Design Engineering Architecture Design

5 SE Education: CS437 Architecture Design Component-level Design Component Implementation System Integration Software Testing Strategies Software Testing Techniques Software tools

6 Educational Skill Requirements: Plan and Management (I) Software Plan feasibility assessments prototyping Simulation

7 Educational Skill Requirements: Plan and Management (II) Software Project Management configuration management quality assurance system evolution risk assessment development processes improvement

8 Educational Skill Requirements: Design and Development (I) Design requirements engineering and specification system modeling and engineering models software architecture and its application automation of industry processes

9 Educational Skill Requirements: Design and Development (II) Software architecture and control multiprocessing distributed processing network-centric computing real-time control

10 Educational Skill Requirements: Design and Development (III) Integration system interoperability end-to-end system integration legacy system reengineering

11 Educational Skill Requirements: Verification and Validation Quality assurance verification techniques validation techniques risk assessment and trade-off diagnose and debug recover from software failures

12 Educational Skill Requirements: Software Technology Tools and techniques simulation and modeling of systems engineering automation assessment of software systems program generation computer aided software design IDE, UML and RSA

13 Project for CS337 and CS437 (I) 2-4 students per group CS337 Requirement Document Design Document Prototype CS437 More work on documents and system

14 Project for CS337 and CS437 (II) Group-based project from Requirement analysis to Design to Coding… Eliciting requirements by using use- cases Design by using UML diagrams Coding by utilizing new technologies and tools

15 Project for CS337 and CS437 (III) Documentation IEEE Standards used Software Requirement Specification Software Design Specification Software Coding Software Test Plan

16 Project Selection Challenges Meaningful Manageable Challenging Accomplishable

17 Project Ideas for CS437 Continuing previous projects Switch to other students’ projects

18 Lessons Learned for Group Projects The project success relies on leader’s dedication Good training from the previous CS337 is important A large amount of code is doable Continuous supervision and coordination are important Clearly defined project scope is important Communication must be open, flexible and routine

19 Skill Assessments Problem and Requirement Analysis – CS337 Development (Collaborative) – CS437 Oral Communication – CS337 & CS437 Written Communication – CS337 & CS437

20 Comments?