CSE784 – Software Studio Jim Fawcett Fall 2002.

Slides:



Advertisements
Similar presentations
DWebSpec Why dWebSpec? It could be asked,with all the web application alternatives.
Advertisements

Design Concepts and Principles
Chapter 13 Design Concepts and Principles
1 Marvel Electronics and Home Entertainment e-Commerce System Final Status Report April 12, 2005 (Tuesday)
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Design Creative Process of transferring the problem into a solution
Software Requirements Specification Quality Measures Derived from Dr. Fawcett’s slides Phil Pratt-Szeliga Fall 2009.
CSE 784 Software Studio Phil Pratt-Szeliga Fall 2010 Slides Derived From: Dr. Fawcett.
Software Architecture and Specification Derived from Dr. Fawcett’s slides Phil Pratt-Szeliga Fall 2010.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
1 Object Oriented Programming Computer Systems Engineering (D2) and Programming (P)
Lesson 7 Guide for Software Design Description (SDD)
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Chapter 6 Software Implementation Process Group
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
SOFTWARE DESIGN.
Chapter 9 Moving to Design
Large Scale Software Systems Derived from Dr. Fawcett’s Notes Phil Pratt-Szeliga Fall 2010.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Request for Proposal (RFP)
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
UNIT 2 TESTING TECHNIQUES Testing begins with a proposal for software/system application development/maintenance and end with the system is formally accepted.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Software Architecture and Specification 2 Derived from Dr. Fawcett’s slides Phil Pratt-Szeliga Fall 2009.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Phase 3 The Software Requirements Specification. After review of the customer’s System Spec. After educated analysis Preliminary design A technical, software.
Conceptual design Tells the customer what the system will do Tells the customer what the system will do Answers: Answers: Where will the data come from?
© 2010 John Wiley & Sons Ltd. Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
CHAPTER 3 MODELING COMPONENT-LEVEL DESIGN.
310414IMPLEMENTATION1 IMPLEMENTATIONIMPLEMENTATION SOFTWARE ENGINEERING SOFTWARE ENGINEERING.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Engineering Lecture 10: System Engineering.
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
Design CS 470 – Software Engineering I Sheldon X. Liang, PH.D.
SYSTEM ANALYSIS AND DESIGN SAFAA S.Y. DALLOUL. DESIGN THE PROGRAM.
Software Design Derived from Dr. Fawcett’s slides CSE784 – Software Studio Fall 2009.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
CS 4311 Software Design and Implementation Spring 2013.
Basic Characteristics of Object-Oriented Systems
1 Software Development Life cycle (SDLC). Phases of SDLC 2 Requirement Analysis (Defining Requirement) Designing (Design) Coding (Implementation) Software.
Software Design. Introduction Designing engineering encompasses the set of principles concepts and practices that lead to the development of a high quality.
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.
Final Exam Study Guide COP 4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of EE and Computer Science University of.
Appendix 1 - Packages Jim Fawcett copyright (c)
CSC 480 Software Engineering
Software Design.
Test-Driven Development
The Movement To Objects
CSE687 – Object Oriented Design
Chapter ? Quality Assessment
Architecture Concept Documents
Configuration Management Why do we need it? What does it do?
Object-Oriented Techniques
which satisfies software requirements
Lecture 9- Design Concepts and Principles
CSE784 – Software Studio Jim Fawcett Fall 2006.
Software Development Life cycle
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Lecture 9- Design Concepts and Principles
Systems development life cycle (SDLC)
Project Prototype Demo 1 Grading Rubric
Requirements Engineering
Chapter 3 Software Architecture and Specification
Executable Specifications
Software Architecture
Presented by KARRI GOVINDA RAO ,
Chapter 10 – Component-Level Design
Presentation transcript:

CSE784 – Software Studio Jim Fawcett Fall 2002

Course Scope Software Development process with emphasis on principles of good design and implementation. Techniques needed for large scale software development.

Part I Analysis, Design, implementation Specifying software systems what, not how Attributes of a good design simplicity Attributes of a good implementation robustness Characteristics which weaken your designs and implementations

Part II Software Development Process Process models and products Roles and activities for each phase of development

Part III - Case Study One major project that the class develops together. SW Project Manager, Architect, Team Leader, and Team Member roles are assigned (usually 5-6 teams). SW product is documented, developed, and qualified with the customer.

One Individual Project Requirements Document Design Document Code Revised Requirements Document

Midterm Examination Take-home examination Detailed Analysis of your first project Requirments Design Implementation Test

Topics Requirements Analysis Design Implementation Test Qualification Maintenance

Requirements Analysis A Specification Architecture Partitioning Organizing principles Critical Issues B Specification (Software Requirements Spec) define top-level modules define abstraction Data Flow Diagrams Pspecs (HIPO format) Data Dictionary Requirments Traceability Matrix

Design abstraction modularity and encapsulation coupling and cohesion object oriented design C Specification (Product Spec, Design Document) elaborate architecture define structure and processing of each module Mspecs class hierarchy charts event trace diagrams structure charts state transition diagrams data dictionary

Implementation Abstraction modularity and encapsulation manual and maintenance pages modularity and encapsulation modules, classes, and functions coupling and cohesion HIPOs object implementation building self-sufficient servers

Testing Phases test plan unit and qualification test drivers construction, unit, integration, validation, qualification, and regression testing test plan test structure required resources Schedule procedures unit and qualification test drivers

Qualification test structure legal aspects demonstration, test, analysis, inspection legal aspects

Basis for Grades Individual Project – 30% Midterm – 30% B-Spec, C-Spec, and code count equally Midterm – 30% Demonstrates you know how to evaluate a software project. Documentation must be convincing. Final Project – 40%