Presentation is loading. Please wait.

Presentation is loading. Please wait.

Team Introduction Ovide Mercure Michael Ambroise Wai-Lam Chan Allen Lee Project Manager Time Keeper Project Historian Project Analyst.

Similar presentations


Presentation on theme: "Team Introduction Ovide Mercure Michael Ambroise Wai-Lam Chan Allen Lee Project Manager Time Keeper Project Historian Project Analyst."— Presentation transcript:

1 Team Introduction Ovide Mercure Michael Ambroise Wai-Lam Chan Allen Lee Project Manager Time Keeper Project Historian Project Analyst

2 Introduction to Study Feasibility Feasibility Determine the feasibility of developing SOGRS vs. Alternate Systems. (ACPEA and WebCT) Determine the feasibility of developing SOGRS vs. Alternate Systems. (ACPEA and WebCT) Project Plan Project Plan Outline administrative tasks for the development of SOGRS Outline administrative tasks for the development of SOGRS

3 Feasibility Problem Statement Inconveniences of current Excel and e-mail system Sensitive information cannot be sent via e-mail Cumbersome and Time Consuming Problems with WebCT Difficult to attend due to scheduling conflicts and existing workloads Alternatives Automated Cut Paste Email Application (ACPEA) Student Online Grade Report System (SOGRS) WebCT

4 Operational Feasibility Operational Feasibility Criteria for Operational Feasibility Criteria for Operational Feasibility Performance – throughput and response time Performance – throughput and response time Information – provides timely and pertinent info Information – provides timely and pertinent info Economy – cost effective services Economy – cost effective services Control – security and fraud protection Control – security and fraud protection Efficiency – maximum use of resources Efficiency – maximum use of resources Services – reliability, flexibility Services – reliability, flexibility

5 Feasibility CriteriaWt.Alternative 1Alternative 2Alternative 3 Operational Feasibility Performance Information Economy Control Efficiency Service User Friendliness 30% Performance  LOW 1.No control over the throughput of email server. Performance  HIGH 1.Fully Supports user required functionality. Performance  HIGH 1.Fully Supports user required functionality. Information  LOW 1.Sensitive information cannot be sent via email. 2.Only supports the distribution of grade reporting. Information  HIGH 1. Fully Supports user required functionality. Information  HIGH 1. Fully Supports user required functionality. Economy  MED 1.Economic to implement. Economy  MED 1.Economic to implement. Economy  HIGH 1.Very economic to implement. Control  LOW 1.Does not allow for sensitive information to be transmitted. Control  MED 1.Allows for sensitive materials. Control  HIGH 1.Allows for sensitive materials. Efficiency  MED Efficiency  MED Efficiency  HIGH Service  LOW Service  HIGH 1.Fully Supports user required functionality. Service  N/A 1.No control over this attribute. 2.Fully Supports user required functionality. User Friendliness: Yes Score: LOWScore: MED-HIGHScore: HIGH

6 Technical Feasibility Technical Feasibility Technology – maturity and availability Technology – maturity and availability Expertise – how much is needed? Expertise – how much is needed? Feasibility CriteriaWt.Alternative 1Alternative 2Alternative 3 Technical Feasibility Technology Expertise 30% Technology  When implemented in JAVA this application fulfills criteria. Expertise  JAVA and SMTP protocol knowledge. Score: MED Technology  The technology is available but most developers within the team are unfamiliar with the Tomcat server. All team members are familiar with JAVA programming but need to learn JSP and Servlets technology. Expertise  JAVA, JSP and Apache Tomcat server technology. Score: MED Technology  Currently Implemented Expertise  Currently Implemented Score: HIGH

7 Economic Feasibility  Cost Analysis of alternative. Feasibility CriteriaWt.Alternative 1Alternative 2Alternative 3 Economic Feasibility 10% Approximately $89,876.00 Score: MED Approximately $145,032.00 Score: LOW Approximately $0.00 Score: HIGH

8 Economic Cost analysis Cost analysis PM = Duration of Deliverable in Days * (8 hours / 1 Day) * (1 PM / 152 hours) PM = Duration of Deliverable in Days * (8 hours / 1 Day) * (1 PM / 152 hours) SC = Effort estimate (PM) * RELY * TIME * STOR * TOOL * LTEX * $15,000 SC = Effort estimate (PM) * RELY * TIME * STOR * TOOL * LTEX * $15,000 ACPEA ACPEA TPM = 6.16 PM TPM = 6.16 PM SC = $89,876.00 SC = $89,876.00 SOGRS SOGRS TPM = 9.93 PM TPM = 9.93 PM SC = $145,032.00 SC = $145,032.00 WebCT WebCT TPM = 0 PM TPM = 0 PM SC = $0 SC = $0 RELY – Required System Reliability TIME – Execution Time Constraints STOR – Memory Constraints TOOL – Use of Software Tools LTEX – Language and Tools Experience

9 Schedule Feasibility  As assessment of how long the solution will take to design and implement Feasibility CriteriaWt.Alternative 1Alternative 2Alternative 3 Schedule Feasibility Time required to design and implement. 30% 2 Months Score: MED 3 Months Score: LOW Done Score: HIGH

10 Recommendations Top Recommendation Top Recommendation Based on our matrix result Based on our matrix result WebCT WebCT Second Recommendation Second Recommendation If inconvenience is the top factor If inconvenience is the top factor If cost is not a factor If cost is not a factor SOGRS SOGRS

11 Project Plan Introduction Hardware and Software Hardware and Software SOGRS Cost Analysis SOGRS Cost Analysis Project Schedule Project Schedule

12 H/W & S/W Requirements Server Computer Server Computer Java 1.4.2 Java 1.4.2 Tomcat 5.0 Tomcat 5.0 Ethernet Connection Ethernet Connection Client Computer Client Computer Web Browser with JVM (students and professor) Web Browser with JVM (students and professor) Excel (professor only) Excel (professor only) Development Development Rational Rose Rational Rose JCreator JCreator Microsoft Project, Word, and EXCEL Microsoft Project, Word, and EXCEL

13 SOGRS Cost Analysis Deliverable 1: Feasibility Study and Project Plan Deliverable 1: Feasibility Study and Project Plan PM = 20 * 8 / 152 = 1.1 PM PM = 20 * 8 / 152 = 1.1 PM SC = 1.1 *.91 * 1.07 * 15,000 = $16,066.00 SC = 1.1 *.91 * 1.07 * 15,000 = $16,066.00 Deliverable 2: Software Requirements Document Deliverable 2: Software Requirements Document PM = 38 * 8 / 152 = 2 PM PM = 38 * 8 / 152 = 2 PM SC = 2 *.91 * 1.07 * 15,000 = $29,211.00 SC = 2 *.91 * 1.07 * 15,000 = $29,211.00 Deliverable 3: Design Document Deliverable 3: Design Document PM = 85 * 8 / 152 = 4.4 PM PM = 85 * 8 / 152 = 4.4 PM SC = 4.4 *.91 * 1.07 * 15,000 = $64,264.00 SC = 4.4 *.91 * 1.07 * 15,000 = $64,264.00 Deliverable 4: Test Document Deliverable 4: Test Document PM = 36 * 8 / 152 = 1.9 PM PM = 36 * 8 / 152 = 1.9 PM SC = 1.9 *.91 * 1.07 * 15,000 = $27,750.00 SC = 1.9 *.91 * 1.07 * 15,000 = $27,750.00 Deliverable 5: Software Document Deliverable 5: Software Document PM = 10 * 8 / 152 =.53 PM PM = 10 * 8 / 152 =.53 PM SC =.53 *.91 * 1.07 * 15,000 = $7,741.00 SC =.53 *.91 * 1.07 * 15,000 = $7,741.00 TPM = 9.93 PM TPM = 9.93 PM SC = $145,032.00 SC = $145,032.00

14 Work Breakdown 1 – Document Study 1 – Document Study 2 – Prototype User Interfaces 2 – Prototype User Interfaces 3 – Research Software Tools 3 – Research Software Tools 4 – Feasibility Study and Project Plan Deliverable 4 – Feasibility Study and Project Plan Deliverable 5 – Presentation of Project Plan and Feasibility Study 5 – Presentation of Project Plan and Feasibility Study 6 – M1 6 – M1 7 – Document Project (SRD) 7 – Document Project (SRD) 8 – Develop Use Cases 8 – Develop Use Cases 9 – Expertise with Software Tools 9 – Expertise with Software Tools 10 – M2 (Use Case Completion) 10 – M2 (Use Case Completion) 11 – Software Requirement Documents (SRD) 11 – Software Requirement Documents (SRD) 12 – Presentation of SRD 12 – Presentation of SRD 13 – M3 13 – M3 14 – Document Project (DD) 14 – Document Project (DD) 15 – Develop Object Sequence Structure 15 – Develop Object Sequence Structure 16 – Develop Class Structure 16 – Develop Class Structure 17 – M4 (Object and Class Structure Done) 17 – M4 (Object and Class Structure Done) 18 – Design Document 18 – Design Document 19 – Presentation of Design Document 19 – Presentation of Design Document 20 – Develop Implementation 20 – Develop Implementation 21 – M5 21 – M5 22 – Test Document Project 22 – Test Document Project 23 – Develop Test Cases 23 – Develop Test Cases 24 – Testing 24 – Testing 25 – Test Document (TD) 25 – Test Document (TD) 26 – Presentation of TD 26 – Presentation of TD 27 – M6 27 – M6 28 – Document Project (SD) 28 – Document Project (SD) 29 – Software Document (D5) 29 – Software Document (D5) 30 – Presentation of SD 30 – Presentation of SD 31 – M7 31 – M7

15 Project Schedule

16 Questions ? ? ?


Download ppt "Team Introduction Ovide Mercure Michael Ambroise Wai-Lam Chan Allen Lee Project Manager Time Keeper Project Historian Project Analyst."

Similar presentations


Ads by Google