CSE 784 Software Studio Phil Pratt-Szeliga Fall 2010 Slides Derived From: Dr. Fawcett

Course Scope: Overview Software Development Process with emphasis on – Design – Implementation – Test Techniques used in large scale software development

Course Scope: Part I Analysis, Design, Implementation Specifying Software Systems – What, not how (Essential for testability) Attributes of a good design – Simplicity Attributes of a good implementation – Robustness Characteristics which weaken your designs and implementations

Course Scope: Part I Software Development Process Process models – Roles and activities for each phase of development – Using an agile process model in final project Version Control – Keeping track of changes – Using Mercurial Version Control System in final project

Course Scope: Part II Case Study (Final Project) One major project that the class develops together. Project Manager, Architect, Team Leaders, and Team Member roles are assigned (3 teams this year). Software Product is documented, developed and qualified with “the customer”.

Course Scope: Part II Case Study (Final Project) Teaming with Microsoft Open Source to develop parts of CoApp. – – CoApp is like apt-get on Ubuntu (and more)

Projects Individual – Project 1 (assigned in 2 parts) A. Requirements Specification Document (B-Spec) B. Code – Midterm Examination. Detailed analysis of aspects of your first project: Requirements Design Implementation Test Group – Final Project

Course Topics: Overview Requirements Analysis Design Implementation Test Qualification Maintenance

Course Topics: Requirements Analysis During Requirements Analysis we create the following three documents: A Specification Architecture B Specification

Course Topics: Design and Implementation Abstraction Modularity and Encapsulation Coupling and cohesion Object Oriented Design C Specification

Course Topics: Testing Phases – Construction, unit, integration, validation, qualification and regression testing Test Plan – Required Resources – Schedule – Test descriptions and procedures Unit and qualification test drivers

Course Topics: Qualification Demonstrate to the customer that the product works as specified Test Structure – Demonstration, Test, Analysis, Inspection

Course Topics: Maintenance We will talk about aspects of design and implementation that make software maintainable In your midterm you will analyze these aspects, among other things

Basis For Grades Individual Project – B Spec: 10% – Code: 10% Midterm – 15% – Demonstrates you know how to evaluate a software project – Documentation must be convincing Final Project – 65% – A peer review and attendance is part of this grade

Course Schedule - I will be lecturing the first four lectures - The remainder of the lectures are student presentations or group meetings regarding the final project

Student Presentations -Architectural Review -Software Architect Presents Architecture and Allocates Requirements to Teams -B Specification Review -One team asks questions about another teams B- Specification until all problems are fixed -B-Specifications must be distributed to me and the class no later than Thursday October 7th, Midnight

Student Presentations -Iteration Pre Presentation -Team Leaders Present the features their team will develop in the upcoming iteration -Team Members Present Test Procedures -Iteration Post Presentation -Team Leaders Present the status of the previous iteration (what went wrong and what went right) -Team Members Present Test Results

Student Presentations -Test Readiness Review -Project Manager Presents Status of Test Procedures -90% of Test Procedures need to be written and passing -Qualification Test -Project Manager and Customer test every requirement

Project 1 B-Spec Note -Start your B-Spec Early! -Management Positions are based on B-Spec grades -Students desiring management position must have B-Spec in by September 23th, Midnight.