CHEVROLET ADVANCE-DESIGN

SERIES PAINT VISUALIZER

REQUIREMENT SPECIFICATIONSYOUR DREAM, OUR

SOLUTION

1

Y OS

AgendaIntroductionProblem Restate

Project ProgressionUse Case Narratives

UML Use Case DiagramData Flow Diagrams

Functional RequirementsPrototype Screens

What’s Next?

2

TEAM INTRODUCTION

TROY VALLE – TEAM LEADER

FRANK SCHROEDER – PROJECT MANAGER

KERRIE DALEY – TECHNICAL PROCESSOR

GRADY MCBRIDE – DATABASE MANAGER

MATT MAINELLO – WEBMASTER

3

AgendaIntroduction

Problem RestateProject ProgressionUse Case Narratives

UML Use Case DiagramData Flow Diagrams

Functional RequirementsPrototype Screens

What’s Next?

4

PROBLEM RESTATE

DR. TIMOTH LEDERMAN IS A GENERAL MOTORS TRUCK

ENTHUSIAST. SEVERAL YEARS AGO, HE FOUND A WEB

APPLICATION ON THE INTERNET THAT ALLOWED HIM TO CUSTOM

DESIGN TRUCKS. UNFORTUNATELY, THE WEBSITE IS NO LONGER

IN EXISTENCE. DR. LEDERMAN HAS EXPRESSED HIS WANT FOR

A NEW WEB APPLICATION THAT WILL ALLOW USERS TO CUSTOM

DESIGN 1947-1955 CHEVROLET TRUCKS. THIS PROJECT WILL BE

CALLED CHEVROLET ADVANCE-DESIGN SERIES PAINT

VISUALIZER (CADS PAINT VISUALIZER).

5

AgendaIntroduction

Problem Restate

Project ProgressionUse Case Narratives

UML Use Case DiagramData Flow Diagrams

Functional RequirementsPrototype Screens

What’s Next?

6

PROJECT PROGRESSION

“DEVELOP A THOROUGH UNDERSTANDING OF THE

FEATURES AND FUNCTIONALITY REQUIRED OF THE

SOFTWARE SYSTEM THAT WILL BE DEVELOPED. “

7

AgendaIntroduction

Problem RestateProject Progression

Use Case NarrativesUML Use Case Diagram

Data Flow DiagramsFunctional Requirements

Prototype ScreensWhat’s Next?

8

TWO DIFFERENT USERS

• CUSTOMIZER

• RESTORER

9

GENERAL USE OF CADS PAINT VISUALIZER

• SELECT MODEL BY YEAR

• CHANGE COLOR

• CHANGE VIEW

• SAVE TRUCK

10

WHAT’S THE DIFFERENCE?

11

AgendaIntroduction

Problem RestateProject ProgressionUse Case Narratives

UML Use Case DiagramData Flow Diagrams

Functional RequirementsPrototype Screens

What’s Next?

12

Actor: An entity that interacts with thesystem externally. This can be either a

human or non-human user.

Use Case: A component within the systemthat actors may interact with.

System Boundary: A boundary betweeninternal and external components.

A

Actor A interacts with all of the systemsUse Cases

A B

A

A B

A B

BActor A interacts with Use Case B

Actor B interacts with all Use Cases thatActor A is able to interact with.

Use Case A includes Use Case B

Use Case B is a more specific type of Use Case A

UML USE CASE LEGEND 13

14

User

MySQLDBMS

Change Color

Select Makeand Model

Save TruckChange View

UpperBody

LowerBody Rims

Bumper

Pinstripeon Body

Pinstripeon Wheels

GrillFender

Input UniqueNameSide View Front View

Year

Body Style WindowStyle

Cab Style

<<includes>>

<<includes>>

ApacheWebserver

Webhosting PadRestorer Customizer

<<extends>>

<<extends>>

<<extends>>

<<extends>> <<extends>>

<<extends>>

<<extends>>

<<extends>>

<<extends>><<extends>>

<<includes>>

<<extends>>

<<extends>>

CADS UML USE CASE DIAGRAM

AgendaIntroduction

Problem RestateProject ProgressionUse Case Narratives

UML Use Case Diagram

Data Flow DiagramsFunctional Requirements

Prototype ScreensWhat’s Next?

15

CONTEXT DIAGRAM 16GMC Truck Customizer

CADS

GMC Truck Restorer

CADS MySQL Database

GM TruckCustomizer/Restorer

4. SwitchView

2. SelectTruck andBody Style

5. Save Truck

3. ChangeColor

1. Load TruckLibrary

CADS MySQL Database

TruckRequest

TruckData

TruckInformation

Type ofTruck

Truck Data

View Type

Available Views

Factory Colors

Selected Color

TruckInformation

LibraryRequest

New View

Truck withnew color.

TruckImage

Save Response

LibraryResponse

Color Request

View Request

Truck DataRequest

SaveResponse

LEVEL 0 DIAGRAM 17

CADS MySQL Database

User

1.1 View Library

View LibraryRequest

1.2Get Library

View LibraryRequest

View LibraryRequest

TruckLibrary

TruckLibrary

TruckLibrary

LEVEL 1 LOAD LIBRARY 18

CADS MySQL Database

User

2.3 EnterTruck

Information

2.1 DisplayTruck

2.2 GetTruck

TruckInformation

TruckInformation

TruckInformation

TruckImage

TruckImage

TruckImage

LEVEL 1 SELECT TRUCK 19

User

3.2 SelectColor andSection

3.3 DisplayNewTruck

Color/SectionRequest

Color/SectionRequest

NewTruck

CADS MySQL Database

3.1 Get FactoryColors

RequestColors

RequestColors

FactoryColors

FactoryColors

LEVEL 1 CHANGE COLOR 20

User

4.1. Select View 4.2 ChangeView

RequestView

NewView

New ViewImage

LEVEL 1 CHANGE VIEW 21

CADS MySQL Database

User

5.1 View Library

View LibraryRequest

5.2 Get Library

View LibraryRequest

View LibraryRequest

TruckLibrary

TruckLibrary

TruckLibrary

22LEVEL 1 SAVE TRUCK

AgendaIntroduction

Problem RestateProject ProgressionUse Case Narratives

UML Use Case DiagramData Flow Diagrams

Functional RequirementsPrototype Screens

What’s Next?

23

The two types of users are restorers and customizers.

Restorer• Will be able to choose from the original factory colors of the selected truck that will be stored in a database created by YDOS.  Customizer• Will be able to choose any color that the user wants using a color wheel.

FUNCTIONAL REQUIREMENTS 24

AgendaIntroduction

Problem RestateProject ProgressionUse Case Narratives

UML Use Case DiagramData Flow Diagrams

Functional Requirements

Prototype ScreensWhat’s Next?

25

PROTOTYPE SCREEN 26

AgendaIntroduction

Problem RestateProject ProgressionUse Case Narratives

UML Use Case DiagramData Flow Diagrams

Functional RequirementsPrototype Screens

What’s Next?

27

• PRELIMINARY DESIGN – DECEMBER 2, 2013

• DETAILED DESIGN – SPRING 2014

• ACCEPTANCE TEST – SPRING 2014

WHAT IS NEXT? 28

QUESTIONS?

29