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

Slides:



Advertisements
Similar presentations
1 Eurostat Unit B1 – IT Systems for Statistical Production IT outsourcing in Eurostat – our experience Georges Pongas, Adam Wroński Meeting on the Management.
Advertisements

Systems Analysis and Design in a Changing World
Chapter 8: Evaluating Alternatives for Requirements, Environment, and Implementation.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Team 7 / May 24, 2006 Web Based Automation & Security Client Capstone Design Advisor Prof. David Bourner Team Members Lloyd Emokpae (team Lead) Vikash.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Project Risks and Feasibility Assessment Advanced Systems Analysis and Design.
Project 2002 A Proposal Application Project 2002 Actions.
Lesson-24 Feasibility Analysis and the System Proposal(2)  Write suitable system proposal reports for different audiences.  Plan for a formal presentation.
OCT1 Principles From Chapter One of “Distributed Systems Concepts and Design”
Title 1 Software Linked Interactive Competitive Environment Software Plan September 23 rd, 2011.
The Architecture of Transaction Processing Systems
8 Systems Analysis and Design in a Changing World, Fifth Edition.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Initiating and Planning Systems Development projects
IT Project Management Cheng Li, Ph.D. August 2003.
INFO425: Systems Design INFORMATION X Finalizing Scope (functions/level of automation)  Finalizing scope in terms of functions and level of.
Web Platform Performance Analysis for AOL Team #4 ECE 498A Spring 2004.
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
System Development Process Prof. Sujata Rao. 2Overview Systems development life cycle (SDLC) – Provides overall framework for managing system development.
Next Doc Project Team: xxxxx Spring TitlePage Scope Statement Mission Statement3 Business Need4 Project Description5-6 Project Lifecycle Approach7.
Matrix Mapping Tool Sam Gross Internship at Virtual Technology Corporation.
Feasibility Study.
CS480 Computer Science Seminar Introduction to Microsoft Solutions Framework (MSF)
Feasibility Analysis What is feasibility and when should feasibility checkpoints occur? What are the four types of feasibility and what is the description.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Project Overview Graduate Selection Process Project Goal Automate the Selection Process.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Student Curriculum Planning System MSE Project Presentation I Kevin Sung.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
Insurance Industry is information intensive 8,000 Companies 3 Million People Employed State Farm has over 5,000 IS employees.
Information Systems System Analysis 421 Class Three Initiating and Planning Systems Development Projects.
1 CS6320 – SW Engineering of Web- Based Systems L. Grewe.
Self-assembling Agent System Presentation 1 Donald Lee.
Ashley Montebello – CprE Katie Githens – SE Wayne Rowcliffe – SE Advisor/Client: Akhilesh Tyagi.
Expert System Job Offer Evaluation Software May Abstract The project’s focus is to decide what criteria should be used to determine which job offer.
Abstract Introduction End Product & Deliverables Resources Project Requirements Team Members: Faculty Advisors: Client: Team Members: Faculty Advisors:
T Project Review eGo PP Iteration
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Software Engineering Lecture # 1.
The Planning Phase Recognize the problem MIS steering committee 7. ManagerSystems analyst Define the problem Set system objectives Identify system constraints.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
1 Statements of Work – Getting Them Right!!. 2 Today’s Agenda A.The Basics B. Sources of Information C. Scenario #1: Procurement is in the loop D. Scenario.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 11 Project Management.
Statements of Work – Getting Them Right!!
Chapter 8 Environments, Alternatives, and Decisions.
Managing the Information Systems Project
Systems Analysis & Design N106
Systems Analysis – ITEC 3155 Evaluating Alternatives for Requirements, Environment, and Implementation.
SKILL ASSESSMENT OF SOFTWARE TESTERS Case Study
Chapter 3 Managing the Information Systems Project
The Impact of Cloud Computing to Technology-Based Companies
Scheduler 1.0 By Vipul Sabhaya Udam Dewaraja.
End-Product Description
Globey's World Abstract Design Requirements Introduction
Proposal Presentation
API DOCUMENTATION Swetha Mohandas Microsoft Connect 2016
Power Market Game.
Joint Application Development (JAD)
Chapter 2 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Presentation transcript:

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

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

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

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

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 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 . 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

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

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

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, SC = $89, SOGRS SOGRS TPM = 9.93 PM TPM = 9.93 PM SC = $145, SC = $145, 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

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

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

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

H/W & S/W Requirements Server Computer Server Computer Java Java 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

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, SC = 1.1 *.91 * 1.07 * 15,000 = $16, 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, SC = 2 *.91 * 1.07 * 15,000 = $29, 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, SC = 4.4 *.91 * 1.07 * 15,000 = $64, 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, SC = 1.9 *.91 * 1.07 * 15,000 = $27, 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, SC =.53 *.91 * 1.07 * 15,000 = $7, TPM = 9.93 PM TPM = 9.93 PM SC = $145, SC = $145,032.00

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

Project Schedule

Questions ? ? ?