Software Engineering 3156 3-Dec-01 #24: Review Phil Gross.

Slides:



Advertisements
Similar presentations
Software Life Cycle and Models
Advertisements

Slide 3.1 © The McGraw-Hill Companies, 2002 Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach
Software Development Life-Cycle Models
CHAPTER 3 SOFTWARE LIFE-CYCLE MODELS.
10 Software Engineering Foundations of Computer Science ã Cengage Learning.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 methodologies 1.
Introduction to Software Engineering Lecture 3 André van der Hoek.
IS6112 Application Modelling and Design Introduction.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Software Engineering.
CMSC 132: Object-Oriented Programming II
Computer ScienceSoftware Engineering Slide 1 Review l The need for software engineering l Processes Waterfall Iterative waterfall Evolutionary Formal systems.
Introduction to Software Engineering Dr. Basem Alkazemi
Object-oriented Analysis and Design
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.
Software Engineering 3156 Fall 2001 Section 1 24-Sep-01 #5: Project, OOA, UML Phil Gross.
Midterm 1 Overview Fawzi Emad Chau-Wen Tseng Department of Computer Science University of Maryland, College Park.
Soft. Eng. I, Spring 07Dr Driss Kettani1 CSC-3324: Chapter II The Software life cycle & Software engineering process models Reading: I. Sommerville, Edition.
Incremental Model Requirements phase Verify Specification phase Verify
COMS W3156: Software Engineering, Fall 2001 Lecture #24: The End…? Janak J Parekh
CS252: Systems Programming Ninghui Li Final Exam Review.
CS 5150 Software Engineering Lecture 15 Program Design 2.
CIS 321—IS Analysis & Design
Slide 12.1 © The McGraw-Hill Companies, CS 4310: Software Engineering Lecture 7 Systems Analysis Object-Oriented Design.
Design Patterns OOD. Course topics Design Principles UML –Class Diagrams –Sequence Diagrams Design Patterns C#,.NET (all the course examples) Design Principles.
COMP 523 DIANE POZEFSKY 20 August AGENDA Introductions Logistics Software Engineering Overview Selecting a project Working with a client.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Introduction to Software Development 1. Outline The code-compile-debug process for writing a program The software development process 2.
CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
L1-S1Introduction 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Introduction To System Analysis and Design
CSE 308 Software Engineering Software Engineering Strategies.
Information System Development Courses Figure: ISD Course Structure.
10/20/2015 ©2007 Scott Miller, University of Victoria. 1 SENG130 Engineering Software Systems Introduction Rev. 2.1.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Chapter 10: Software Engineering
Software Engineering Summary James Gain
Software Engineering II Lecture 3 Fakhar Lodhi. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification.
SOFTWARE LIFE-CYCLE MODELS
Slide 3.1 © The McGraw-Hill Companies, 2002 Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach
Intro. to Software Engineering 1CSCI 3333 Data Structures.
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Slide 13.1 © The McGraw-Hill Companies, 2002 Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach.
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
1. What do you understand by software engineering? Discuss the role of engineering software development. 2. What do you understand by software requirement.
Software Engineering At Glance. Why We Need Software Engineering? The aim of software engineering is to solve the software crisis Software is delivered.
COMP2110 Software Design in 2003 ● a(nother) framework for Software Engineering ● the Software Engineering ideas and concepts in comp2110 ● Organisation.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
DE?!GN software. COMP2110 Software Design in 2004 Chris Johnson 1.Software Requirements and Software Design in a framework for Software Engineering 2.The.
Systems Development Life Cycle
1 slc5 TTYP – C++ revisited 1 Which of the following statements are reasonable after the following statement: char* fred = new char[5]; a. fred = bill;
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
Why is Design so Difficult? Analysis: Focuses on the application domain Design: Focuses on the solution domain –The solution domain is changing very rapidly.
4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)
Chapter 7: Software Engineering
Chapter 7: Software Engineering
Review for Final, Fall 2010 Close book, Close notes
CS 5150 Software Engineering
Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach
Practical Software Engineering
Review CSE116 2/21/2019 B.Ramamurthy.
Chapter 10: Software Engineering
Presentation transcript:

Software Engineering Dec-01 #24: Review Phil Gross

2 Administrivia Proto2 is up This is probably the wrong time to mention, but you should all fill out course evaluations HWs 2 & 3 here HW4 up soon – No readme on HW4 = zero points – all future classes in CS: readme.txt required

3 Demos Either of the two scheduled final dates – Mon 17 th 1:10-4:00pm – Thu 20 th 4:10-7:00pm We’ll have signup forms available soon If whole team can’t make either of the two final dates (or if you have little to demo) you can schedule for reading week instead Reasonably complete reference servers and clients will be available then

4 Demo Bonuses Up to 10 extra points for added functionality over final submission Integration bonus: – Use another team’s component to demo with instead of ours and (tentatively) +3 points to you +1 point to them (accumulates over all demos)

5 Review MMM Chapters 16, 17, 18 Note chapter 18

6 Waterfall Model Requirements Specification Design Implementation Integration Maintenance

7 Teams Democratic Chief Programmer Extreme Microsoft Typical modern

8 Processes and Lifecycles CMM Build-and-fix Rapid prototyping – *cough* Waterfall Incremental Extreme

9 More Lifecycles Synchronize and Stabilize Spiral Object-Oriented / Fountain

10 OOD Cohesion and Coupling Architectural vs. Detailed Noun extraction

11 Testing Black Box vs. White/Glass Box Testing to specification Boundary/Functional testing Path coverage Walkthroughs

12 SoftE Concepts Reuse Planning and estimation Coding & documentation standards Complexity metrics Security/Cryptography Design Patterns

13 UML Class diagrams Sequence diagrams

14 Concurrent/Distributed Programming Event models RPCs Threads Synchronization CORBA/COM/EJB Service discovery Serialization

15 Tools Rose CVS Regular Expressions Basic SQL & RDBMS

16 XML Syntax Schemas APIs Pros and Cons

17 LDAP Concepts APIs

18 Networking Concepts – IP – TCP – DNS – Addresses and ports – Sockets APIs – Working with server and client sockets

19 Java Reflection AWT/Swing

20 C Differences from Java Compilation/Execution Syntax Pointers System call

21 See You Wednesday Final Closed book Good luck