Predictive Modeling And Reporting Environment (PMRE)

1. Predictive Modeling And Reporting Environment (PMRE) CS 552 Senior Design Architecture Review • Presenting: • Steve Su • Ilya Chalyt • Yuriy Stelmakh (Architect)

2. Outline • MOV & Gantt Chart • Architecture • Sample Use Cases • QFD & ICED-T • Installation Procedure • Function Points • Questions?

3. MOV • PMRE will increase the efficiency and corresponding capacity of the USPS’s current parcel sorting infrastructure by 30% through predictive historical data analysis and strategic equipment placement while improving economic viability. • Engineering Management studies have shown that sorting machines run idle for approximately 30% of the day as employees search for bins by increasing the efficiency 30% (.30 x .70 = .21), to a new capacity of 91% leaving only 9% idle time. PMRE will minimize the amount of time these sorting machines remain idle.

4. Initial Gantt Chart

5. Current Gantt Chart

6. Architecture: Logical View • Logical view of the system is based mostly on the functional requirements. For PMRE the primary functional requirements are: • To predict future mail flow volume based on historical data • Manage facility equipment including machines and bins • Manage users and operating shifts

7. Architecture: Logical View

8. Architecture: Logical View • Equipment Management Class Category will consist of three classes: • Machine Management Class • Locations Management Class • Bin Management Class

9. Architecture: Logical View • Staff Management Class Category will consist of two classes: • User Management Class • Shift Management Class

10. Architecture: Logical View • Analysis and Predictions Class Category will consist of two classes: • Data Analysis Class • Predictions Class

11. Architecture: Process View • At highest level of abstraction PMRE will have 4 distinctive processes: • Data Storage and Collection Process • Analysis and Prediction Process • Notifications Process • RFID Tracking Process

12. Architecture: Process View

13. Architecture: Process View • Now let’s look at the Data Storage and Collection Process. It will consist of four main processes: • Login Process • Data Collection Process • Data Transfer Process • Logging process

14. Architecture: Physical View • PMRE server will be running Apache 2.0 with PHP 4.3 and MySQL 4.1 database • Client PC requirements are the following: • IE 5.0+ • Firefox 1.0+ • Netscape 7+ • OS capable of running any of the above

15. Architecture: Development View • PMRE has three distinct development layers as follows: • Database Layer • API Layer • UI Layer

16. Software Engineering Principles • WinWin Spiral Model • Ensures that all parties benefit and are considered in the goals of the application. • Change Freeze • Stabilizes requirements • Allows for progress to be made which may help to alleviate the requirements confusion. • Wideband Delphi Methodology • One or two experts create a specification which is then reviewed by a panel of members.

17. Complete Use Cases

18. User Logon and Main Menu

19. Equipment Management

20. Shifts Page

21. Statistics Page

22. Bin Types Page

23. User Administration Page

24. Data Input Page

25. Locations Page

26. QFD – House of Quality Matrix • The QFD matrix helps details the understanding of the customers needs and wants. • The House of Quality Matrix allows us to make a connection between system functionality and the technology implementation. • Based on customer requirements and technical solutions, a rating of the implementation solution is created. In our case, system administration and data availability are ranked as being the most important.

27. Implementation Ease vs. Feature Importance • The Implementation Ease vs. Feature Importance breakdown allows us to rank and determine which aspects of the project will require the most time and effort.

28. ICED-T Metrics

29. Installation Procedure Microsoft MSI Installer • Run the installer • Restart the Computer

30. Installation Procedure Advanced Installer – From Source • Install Apache using the standard Apache Runtimes • Install PHP 4.3+ using the standard PHP Runtimes • Install MySQL 4.1+ using the standard MySQL Runtimes • Copy the provided PMRE Source to the WWW Root / World Readable directory • Set the proper port forwarding as per your companies specific infrastructure • Populate the MySQL Database using the supplied INSTALL.sql file and the MySQL Batch loader • Restart the machine or respective services

31. Installation Procedure RFID Tracking Station Install • Install Microsoft .NET 1.1 and 2.0 using the standard .NET Runtimes • Install the RFID Tracker from the provided installer • Set the MySQL Server address, port, and login information • Restart the machine

32. Unadjusted Function Points By analyzing the structure of our application we can make critical staffing decisions and plan for complexity related issues that are now expected.

33. Technology Complexity Factor

34. Adjusted Functional Points and Effort Estimate • AFP=UFP(.65+.01*VAF) • AFP=38*(.65+.01*48)= 42.94 • PHP is most similar to PERL, for which Quantitative Software Management reports SLOC/FP of 60. • LOC = 43 * 60 = 2580 • Productivity: • 2580LOC -> 750 LOC per month • Effort: • 2580 / 750 = 3.44 Staff Months • Give a staff of 10 personnel for 10 month, working half time with a fifty percent reduction in productivity due to added communications costs yields a total of 10*10*(1/2)*(1/2) = 25 effective staff months, 7.26 times the necessary project staffing. This project is over staffed.

35. Thank You • Questions?