SWE © Solomon Seifu 2010 1 CS425 Software Engineering Solomon Seifu Department of Computer Science Maharishi University of Management, Fairfield, IA.

Slides:



Advertisements
Similar presentations
Object-Oriented Software Development CS 3331 Fall 2009.
Advertisements

Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
Object-Oriented Analysis and Design
Mastering Object-Oriented Analysis and Design with UML Module 4: Analysis and Design Overview.
IS6112 Application Modelling and Design Introduction.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
Rational Worldwide Software Symposium
NJIT 1 On to Object Design Chapter 14 Applying UML and Patterns.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Objectives Explain the purpose and objectives of object- oriented design Develop design class diagrams Develop interaction diagrams based on the principles.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
An Agile View of Process
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
OOSD Using Java Lecture 1 Introduction. 8/19/04introduction2 Introduction  IST 350 – Tools & CSC 485 – OOD?  Software Development vs. Programming 
The Design Discipline.
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
1 Introduction Chapter 1. 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.
UML - Development Process 1 Software Development Process Using UML (2)
An Introduction to Models & The UML The Unified Modeling Language Copyright © 2007 Patrick McDermott College of Alameda Not really.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Chapter 1 The Systems Development Environment
A Development Process Lecture Oo13 Objectory based method.
Chapter 1: Introduction to Systems Analysis and Design
Systems Analysis and Design in a Changing World, 6th Edition
Unified Modeling Language, Version 2.0
Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.
Systems Analysis and Design in a Changing World, 6th Edition 1 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH Chapter 11 SATZINGER.
Course Guide IS325 Systems Analysis & Design II Ms Fatima Khan Prince Sultan University, College for Women.
Course Overview & Topics CSc 335: Object-Oriented Programming and Design © Rick Mercer 1.
Information System Development Courses Figure: ISD Course Structure.
Systems Analysis and Design in a Changing World, 3rd Edition
1-1 C Sc 335 Course Overview Object-Oriented Programming and Design Rick Mercer.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object-Oriented Analysis and Design Ruonan Rao.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
CS-2852 Data Structures LECTURE 3B Andrew J. Wozniewicz Image copyright © 2010 andyjphoto.com.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Course Introduction CEN 5016 Software Engineering Dr. David A. Workman School of EE and Computer Science January 9, 2007.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
The principles of an object oriented software development process Week 04 1.
A Well Designed Web Application The Benefits of Object Oriented Analysis and Design Simone Becker
The Systems Development Environment Systems Analysis and Design II.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Object Oriented Analysis and Design 1 CREATED BY RUONAN RAO Object-Oriented Analysis and Design.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.
Basic Characteristics of Object-Oriented Systems
SWE 214 (071) Introduction to UML Slide 1 Introduction to UML.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
1 An Overview of UML. 2 The Unified Modeling Language UML is a graphical language used by software engineers to model software systems during development.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Process 4 Hours.
INTERNATIONAL BURCH UNIVERSITY
Chapter 7: Software Engineering
Systems Analysis and Design With UML 2
Introduction to Software Engineering
Object Oriented Analysis and Design
Rational Worldwide Software Symposium
Basic SDLC Models SDLC  System Development Life Cycle.
Rational Worldwide Software Symposium
Rational Worldwide Software Symposium
Logical Architecture & UML Package Diagrams
Presentation transcript:

SWE © Solomon Seifu CS425 Software Engineering Solomon Seifu Department of Computer Science Maharishi University of Management, Fairfield, IA

SWE © Solomon Seifu SWE - Agenda Administrative Issues Course Goal Course Objectives Lessons  Lesson 1 Introduction to Software Engineering & Best Practices Project

SWE © Solomon Seifu SWE - Agenda (Cont.)  Lesson 2 Projects & Tools  Modeling Tools  Versioning Tools  JUnit  Lesson 2-1  Rapid Prototyping, GUI Design & Stubs  Lesson 3 Fundamentals of OO & UML Lesson 3-1  Class Diagram Lesson 3-2  Sequence, Interaction Overview, Communication,  Interaction, State, Package, Deployment, Timing Diagrams

SWE © Solomon Seifu SWE - Agenda (Cont.) Inception  Lesson 4 - Requirement Analysis Elaboration  Lesson 5 – Use Case Modeling  Lesson 6 – Architecture Analysis  Lesson 7 – Use Case Analysis  Lesson 8 – Project Management, Planning & Software Lifecycle Models  Lesson 9 – Architecture Design  Lesson 10 – Use Case Design  Lesson 11 – Subsystem Design

SWE © Solomon Seifu SWE - Agenda (Cont.) Elaboration  Lesson 12 – Class Design Lesson 12-1 – Reusability & Portability Lesson 12-2 – Design Patterns Lesson 12-3 – Cohesion Lesson 12-4 – Coupling Lesson 12-5 – Good OO Design

SWE © Solomon Seifu SWE - Agenda (Cont.) Construction  Lesson 13 – Implementation Lesson 13-1 – Exception, Logging & Assertion Lesson 13-2 – Testing Transition  Lesson 14 – Maintenance & Refactoring

SWE © Solomon Seifu Administrative Issues

SWE © Solomon Seifu SWE - First Thing First All students need to be in class by 10:00am Professional etiquette, attitude and behavior in the class will be given consideration We’ll have meditation everyday, starting at 12:20 & ending at 12:30 before we’re dismissed. Everyone is expected to be silent during meditation

SWE © Solomon Seifu SWE - Professional Etiquette Policy Since you are in here on a Masters degree and a Professional program, the Computer Science department requires higher standards of dress than the rest of the University Men should be clean shaven (beard is OK, but if no beard then clean shaven), dress pants and a shirt with a sleeves and a collar Jeans are not acceptable for class!

SWE © Solomon Seifu SWE - Professional Etiquette Policy (Cont.) Ladies may wear dress pants with a nice top, or skirt or a dress, but again, no jeans! YOU MAY BE ASKED TO LEAVE CLASS IF YOU ARE NOT APPROPRIATELY DRESSED ACCORDING TO THESE STANDARDS

SWE © Solomon Seifu SWE - Professional Etiquette Policy (Grading) Proper etiquette is essential to our personal and professional success, and the college years are an ideal time to cultivate these values To give attention and importance to this, several fundamental values of etiquette are built into the grading system in every course

SWE © Solomon Seifu Course Goals & Objectives

SWE © Solomon Seifu SWE - Goals Understand the principles and best practices of software “engineering” Learn to plan and execute an entire software engineering project from inception to delivery and maintenance, including analysis, design, implementation and testing

SWE © Solomon Seifu SWE - Objectives Know the principles of object-oriented software development and gain hands-on experience with industry standard analysis and design tools and techniques, such as the Unified Modeling Language (UML) and Unified Software Development Process using use case driven, incremental, iterative, architecture-centric approach

SWE © Solomon Seifu SWE - Objectives (Cont.) Compare the Unified Process with emerging eXtreme Programming, Agile & other development processes Know the basic organization of a modern integrated development environment (IDE) such as Eclipse, including a versioning tool

SWE © Solomon Seifu SWE - Objectives (Cont.) Apply modern software architecture such as the 3-tier architecture in software development Use technologies such as Java Swing for the interface development and Java Database Connectivity (JDBC) for the bridge to the database layer such as MS Access

SWE © Solomon Seifu SWE - Objectives (Cont.) Skillfully assign responsibilities to software objects, which is a critical ability in OO development Design and implement a software system which is reusable, modular, cohesive and loosely coupled Use architecture and design patterns to solve common software engineering problems

SWE © Solomon Seifu SWE - Objectives (Cont.) Foster mutual support, individual accountability and a can-do attitude among one’s teammates to accomplish a given objective

SWE © Solomon Seifu Course Text, Materials & Resources

SWE © Solomon Seifu SWE - Course Website

SWE © Solomon Seifu SWE - Text & Materials UML Distilled, Third Edition: A Brief Guide to the Standard Object Modeling Language by Martin Fowler, (2003) Addison-Wesley Pub Co; ISBN: Rational Unified Process. Copyright 1987 – 2003 Rational Software Corp

SWE © Solomon Seifu SWE - Resources SWE Template Documents (CVS Documents)  Architecture Analysis  Architecture Design  Class Responsibility Collaboration (CRC)  Glossary  Iteration Plan  Software Architecture

SWE © Solomon Seifu SWE - Resources (Cont.)  Subsystem Design  Supplementary Specification  Test Plan  Use Case Analysis  Use Case Design  Use Case Model  Use Case Specification  Vision

SWE © Solomon Seifu 2010 SWE - Resources (Cont.)