Presentation is loading. Please wait.

Presentation is loading. Please wait.

Faculty Coach: Professor Martinez  Justin Mahar  Chris Baum  Greg Schmitz  Adam Abdelhamed.

Similar presentations


Presentation on theme: "Faculty Coach: Professor Martinez  Justin Mahar  Chris Baum  Greg Schmitz  Adam Abdelhamed."— Presentation transcript:

1 Faculty Coach: Professor Martinez  Justin Mahar  Chris Baum  Greg Schmitz  Adam Abdelhamed

2  Project Summary  Process  SEEM  Current Reflections  Website  CVS  Product Progress  Research  Prototype  Future Plans  Questions

3

4  A self contained computer system that allows input from multimedia devices and uses a touch screen monitor to receive input from the user.  Customers use this device to print Kodak quality images from their digital media.  They can edit images, create collages, and photobooks.

5  A collage is a collection of images placed on a single page.  The images are assorted in a pleasing manner.  The collage may also contain text.  A photobook is a collection of collages bound together into a book.

6  An improved collage layout component.  New features  Improved collage output  Windows demo application.  Demonstrates improvements  Proof-of-concept using Web Forms

7  Performance  The new algorithm must run in equal or better time than the current one.  The new algorithm must produce a better collage than the current one.  Platform/Language  C# code to be run on a Windows XP embeddded system.  Web Forms (ASP.NET)

8 Process  Software Engineering Effectiveness Model (SEEM)  Created by former RIT Software Engineering professor Tom Bullinger  Built on best practices of eXtreme Programming and the Rational Unified Process  Waterfall-like model

9 SEEM Overview

10 1. Determine Scope

11 2. Problem Analysis

12 3. Solution Design

13 4. Implement Solution

14 5. Deploy Product

15  Immaturity in SEEM Process  Separation of our product from Kodak’s  Team Development  Performing  Communication with Coach

16  Task Time  Estimation vs. Actual  Where is time being spent?  Bugs  Bugs per line  Time to fix bugs

17 The Photorganizers Website  Dreamweaver for design

18 The Photorganizers Website  Housed in CVS repository  Updated regularly from CVS  Latest deliverables readily available to sponsors  RSS Feed, PHP, Meeting Agenda, Dynamic Linking, and Password Protection

19

20  Simulated Annealing Algorithm provided by Kodak  Collage Layout Properties  Kodak’s current Kiosk workflow  ASP.NET for application implementation

21  Solid understanding of existing algorithm  Identified areas where improvements can be made  Identified some implementation risks

22  Layout properties are used to determine the quality associated with the collage  Examples: White Space, Alignment, Separation, Balance etc.  The more properties used in calculations, the better the calculation of the collage’s quality

23  Used as a basis for the workflow in our application  Allows for easy migration to Kiosk  Small changes must be made to better suit our application  Ex. More transitioning between states

24  Allows our application to run on the kiosk as well as web-based platforms  Algorithm updates can easily be made  Allows our application to run on a local client as well as remote clients

25 Prototype

26 Why Prototype? Assumptions are bad  Complex Algorithm ▪ Performance ▪ Layout Output Quality

27  Simulated Annealing – low risk at a high level  Team has identified two classes of high risk components  Random layout generation algorithms  Energy (quality) factor analysis algorithms

28 Value to the project – Provides the ability to quickly “test drive” prototyped implementations of risky components Algorithm Tracing Visual Feedback Tabular Feedback – Configuration Capture – Performance Data – Layout Quality – Minimizes uncertainty and risk – Helps team determine which components make it into production – Demonstrates progress to sponsor/coach

29

30

31

32

33

34

35  Solution Design in the next two weeks  Based on our Problem Analysis  Includes Interface Prototypes and Interface Specification  Continue prototype development on the Algorithm  Used as proof-of-concept  Possible use in final implementation

36  Implement Solution Phase (Starts 2/29/2008)  Includes User Documentation and Acceptance Tests  Deploy Product (Ends 4/25/2008)  Metrics Report  Acceptance Test Results  Project Reflection  Stretch goals (if time allows)

37


Download ppt "Faculty Coach: Professor Martinez  Justin Mahar  Chris Baum  Greg Schmitz  Adam Abdelhamed."

Similar presentations


Ads by Google