Theatrical Lighting Design and Inventory Management System Architecture Presentation Presenters: Ed Morrison, Harikrishna Patel, Joshua Zawislak

+ 1 Business Logical Process PhysicalDevelopment 4+1 Model

Logical View

Process View

Process View (continued) Diagram shows user operation dependencies Diagram shows user operation dependencies All user operations extend from creating a house object All user operations extend from creating a house object User operations can be repeated User operations can be repeated

Development View

Module architecture analyzed with Spiral Development Module architecture analyzed with Spiral Development Modules based around centralization Modules based around centralization Inheritance used to minimize coupling functions between modules Inheritance used to minimize coupling functions between modules Module version controlled by a CVS server Module version controlled by a CVS server

Physical View Any computer that Any computer that supports Java Runtime supports Java Runtime For use of printing feature a For use of printing feature a the computer needs to have a properly configured printer

Business View Light Design  Program  Electrician Use of program will save $ in Lighting Designer wages $ in Lighting Designer wages $ in Electrician wages $ in Electrician wages

Gantt Chart Changes XML Parser moved to First Release XML Parser moved to First Release

“ICED T” Metrics Scale: 1-Worst I’ve Ever Seen. 2-Worse than average. 3-About the same as other applications I’ve used. 4-Better than average. 5-The best I’ve ever seen. IntuitiveConsistentEfficientDurableThoughtful Change Log v Drawing of some theatre objects. XML Storage partially implemented. First Release Interactive Drawing Utility, Back End Second Release Wiring Plot/Design Diagrams, Print Functions Third Release Inventory Management System, Export Functions

QFD Scale: 1 - Weak 2 - Moderate 3 -Strong XML/Java Backend Interactive Drawing Utility Inventory Mgmt. System Wiring Plot Export Utility Print Functions Totals: User Friendly Stability Portability Flexibility Reliability Scalability Totals:

Function Point Reduction Function Points Function Points Before Refactoring: 63 Function Points Before Refactoring: 63 Function Points After Refactoring: 52 Function Points After Refactoring: 52 Function Points Refactored Components Refactored Components Print Functions Print Functions XML Parser XML Parser Function Points = UFP x TCF Function Points = UFP x TCF UFP = 4I + 5O + 4E + 10L + 7F UFP = 4I + 5O + 4E + 10L + 7F TCF =.96 TCF =.96 Inputs (I) Outputs (O) Inquiries (E) Logical Internal Files (L) Interfaces (F) UFPFP Before After

Coupling Number of 1 way links :38 Number of 1 way links :38 Number of Modules:21 Number of Modules:21 Total Coupling:1.8

Complexity Problem Domain: 2 Problem Domain: 2 Architecture Complexity: 4 Architecture Complexity: 4 Logic Design - Data:3 Logic Design - Data:3 Logic Design - Code:3 Logic Design - Code:3 Type Factor: 9 Total Complexity6

Testability Assumptions: Inheritance for similar modules Inheritance for similar modules Centralized design for module interaction Centralized design for module interaction Limited interface states with known options Limited interface states with known options Test cases and test plan designed around assumption

Test Plan Evolutionary Prototyping Evolutionary Prototyping Regression Testing Regression Testing Use-Case Testing Use-Case Testing Test cases derived from requirements document Test cases derived from requirements document Test cases derived from possibly interface states Test cases derived from possibly interface states Bug Log Bug Log

Maintainability Minimal coupling between modules Minimal coupling between modules CVS used for version control and branching CVS used for version control and branching

Reliability All data given bound limits All data given bound limits Data stored in xml same structure as data stored in program Data stored in xml same structure as data stored in program Interaction states limit possible actions in each state Interaction states limit possible actions in each state

Simplification User Interface: Point and Click Interface Point and Click Interface Specializing windows for minimal tasks Specializing windows for minimal tasksDevelopment: Open source code used for xml parser and print routine Open source code used for xml parser and print routine IDE environment with WYSIWYG UI tools and built in CVS client IDE environment with WYSIWYG UI tools and built in CVS client

Performance Budgeting 128 MB RAM 128 MB RAM 500MB hard drive space 500MB hard drive space 750 MHz processor 750 MHz processor Java installed on computer Java installed on computer

Critical Components Java Runtime to run program Java Runtime to run program File access to save files File access to save files Printer to create hardcopy of data Printer to create hardcopy of data

Screen Shot

Questions/Comments?