DECISION SUPPORT SYSTEM May-0210

1. DECISION SUPPORT SYSTEMMay-0210 Client: Dr. Gerald B. Shéblé Faculty advisors: Dr. Daniel Berleant Dr. Gerald B. Shéblé Team members: Hoang Van Pham Joseph Richard Archer Mei-Peng Cheong Mei-Teng Lee

2. Problem Statement Design Objectives End-Product Description Assumptions and Limitations Project Risks and Concerns Technical Approach Evaluation of Project Success Recommendations for Further Work Human and Financial Budgets Lessons Learned Closing Summary Program Demo Presentation Outline

3. Problem Statement • To create a text extraction software for business companies • Able to retrieve data (keywords) in text format using Microsoft Visual Basic - using Data Dictionary • Have the data stored Excel spreadsheets

4. Design Objectives Functionalities Needed • Retrieve data accurately (current assets, investing activities) • Validates collected data (no out-of-range values) • Has a simple graphical user interface • Has a tutorial for first-time users

5. Design Objectives (cont.) Operating Environment • Microsoft Windows-based computer • Business office environment

6. Design Objectives (cont.) Intended users and uses • Strategic management group - marketing personnel and engineers • View and update data • Easy analysis for decision-making • Provide current market information

7. Design Objectives (cont.) Design Constraints • Linear algorithm (O(n) time) • Handles data only from text files • Expansion of database • Flexible

8. End-Product Description • Gather and retrieve important data • Internal data • Market data • View and update data

9. Assumptions and Limitations • Assumptions • Data input will increase as the business grows • Microsoft Windows-based operating systems • Data input quarterly stored • Each quarter data in one text file • Validation • Maximum runtime is linear

10. Assumptions and Limitations (cont.) Limitations • Basic computer and software knowledge • Minimal knowledge of Microsoft Visual Basic • Minimal knowledge of engineering economics

11. Project Risks and Concerns • Project was not clearly defined • Completing the project on time • Knowledge of Visual Basic • Knowledge of economics

12. Technical Approach • Excel based interface • Using Excel as our database

13. Technical Approach (cont.) • Technical Approach Flowchart

14. Technical Approach (cont.) • Example data received from a company

15. Technical Approach (cont.) • Example data after the data has been validated

16. Technical Approach (cont.) • Example data after it has been stored in the database

17. Technical Approach (cont.) • Example of simple user interface

18. Technical Approach (cont.) • Example of data after using the software

19. Evaluationof Project Success Milestones • Define the functionalities • Understand the basic engineering economic terms • Data Dictionary • Extraction coding • Validation coding • Build database • Build simple user interface • Integration and testing

20. Evaluation of Project Success (cont.)

21. Recommendations for Future Work Continued/Additional Work • Design a better user-interface • Continue to look for better database programs • Add more decision functions Commercialization • Minimum cost • Potential market • small businesses and academic institutions

22. Human Budget Personnel effort budget (for 2 Semesters)

23. Financial Budget

24. Lessons Learned General • Always be prepared (Murphy’s Law) • Good communication is important • Time management – time conflicts • Clear definition of the project is needed • Must keep everyone on task Technical • Microsoft Visual Basic • Engineering Economic Terms

25. Closing Summary • Provides an organized representation of a company’s data • Allows the company to keep track of the current market situation • Assists in making decisions on business plan expansions

26. Questions ?