Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Gift Registry Portal End User Login Project Charter _____________________________________________________________________________ Table of Contents Project Objectives ……………………………………………………………………… Project Scope …………………………………………………………………………… Assumptions ……………………………………………………………………………. Dependencies and Constraints ………………………………………………………… Risk Analysis ………………………………………………………………………… Completeness Criteria ………………………………………………………………… Quality Assurance Requirements ……………………………………………………… Procurement Requirements ………………………………………………………………. Proposed team, roles and responsibility ………………………………………………….. Deliverables …………………………….………………………………………………… Major Milestones …………………………………………………………………………. Estimated Operational and Capital Charges ……………………………………………… Implementation Strategy …………………………………………………………………... Project Management ………………………………………………………………………. Related Documents ……………………………………………………………………… . _____________________________________________________________________________ Project Objective End User Login project goal is to provide the provide end users with the login to the system functionality. All kinds of end users are supported – Recipient, Customer, Retailer and GRP Owner. Project Scope In scope First time login - creating user’s credentials (ID and Password) All succeeded logins with existing ID and Password Credentials checking Change existing password Documentation Out of scope Other than ID+Password based user’s identification and authentication Error handling User’s event log creating Online help Connectivity Objects (ODBC, JDBC) design Relational database support Stored Procedures and Triggers development Source code writing Assumptions Relational database design completed in DES715 course is sufficient Dependencies and Constraints The project must be completed within 14 weeks Risk Analysis Risk Description Computer System Components availability is not sufficient Completeness Criteria Ways of Mitigation Switch to other possible tools including writing by hands _____________________________________________________________________________ The project design is completed with Rational Rose Tools The software is written in pseudo code All the deliverables are completed Project Management Documentation is completed Technical documents are completed Application design implements Model-View-Controller pattern Quality Assurance Requirements Design and development results are sufficient Documentation is sufficient Procurement Requirements N/A Proposed Team, Roles and Responsibility Role Name/TBD Project Manager Product Manager Technical Leader Tatiana Responsibility Organize the team work, Write the project management documents, Insure the project be completed in time and within the budget , Insure the project results meet the QA requirements, Insure the resources are on place, Escalate the project issues to the top management Convey Business Requirements to the development team, Insure the business requirements are met, Analysis of the project scope change requests, Insure the QA requirements are met, Sign Off the project launching Provide the alternatives of technical solutions and criteria of consideration, Make the proposal what the alternative is better and why Write the project technical documents, Write detailed technical requirements and specifications, Determine the programming standards, Convey the requirements and specifications to the developers, Develop the Testing Plan, Skills required *) OO design and programming, MVC concept, Rational Rose Tools, Experience in eCommerce application development _____________________________________________________________________________ Supervise Units Testing, Escalate the issues to the Project Manager Developer Objects design and development on the base of specifications Unit Testing Participate in Testing Plan development Participate in technical documents writing Escalate the issues to the Technical Leader OO design and programming, MVC concept Deliverables Stages and Activities Project Initiating and Planning: - Requirements Deliverables Project Charter Project Plan Project Executing (Design and Development): - Detailed Design - Development - Testing - Deployment Functional and Non-functional Requirements Use Case Diagram Activity Diagram State Diagram Sequences Diagram Class Diagram Source code (pseudo code) Testing Plan Project closing Major Milestones Milestone End Date Project Charter Week 2 Use Case Diagram Week 3 Activity and State Diagram Week 4 Sequences Diagram Week 6 Class Diagram Week 9 _____________________________________________________________________________ Source Code (Pseudo Code) Week 10 Testing Plan Week 12 Project Closing Week 13 Estimated Operating and Capital Charges (mandatory) N/A Implementation Strategy Convert the data model from the relational database design Follow UML methodology to design the software Project Management Communication Management Communication Plan Audience Content Medium for Delivery Frequency/ Timing Communication Deliverables Who is responsible Mini-Project Teams Project Management Methodology Lectures Team meetings As scheduled Project Management Documentation T.O. Mini-Project Teams Technical Solutions Lectures As scheduled Technical Documentation T.O. Issues Management Issues must be escalated at the project team meeting and recorded into Issue Log. Major decisions are to be recorded into Decision Log Related Documents 1. Gift Registry Portal. Project Charter 2. PRJ845 Weekly Schedule