Proposal document Project Name Version: Date: Mentor: Msc, Nguyen Thi Thanh Tam Document create by: International School – Duy Tan University Project Information Project Title Start Date – End Date Lead Institution Project Mentor Project Manager Contact detail Partner Organization Team member Document name Document Title Reporting period Author Role Filename Revision History Name Date Comments Version Document Approvals: The following signatures are required for approval of this document. Msc Tam Nguyen Thi Thanh Mentor Date Leader Date Table of Contents 1. INTRODUCTION 5 1.1 Purpose: 5 1.2 Scope: 5 1.3 References: 6 2. PROJECT OVERVIEW 7 2.1. Project definition 7 2.2. Business Needs 7 2.3. Business Values 7 2.4. Prior Art 7 2.5. Proposed Solution 7 2.5.1. Vision of the Solution 7 2.5.1.1. Vision Statement 7 2.5.1.2. Major Features 7 2.5.1.3. Assumptions and Dependencies 7 2.5.2. System overview 7 2.5.2.1. System context 7 2.5.2.2. System context description 7 2.5.3. Scope and Limitations. 7 2.5.4. Business Context 7 3. EXPECTED OUTCOME 8 4. METHOD APPROACH 9 4.1 Process overview 9 4.2 Tool and technical 11 4.3. Costs Estimate 11 4.3.1. Cost personhours 11 5.3.1 Master Schedule 11 4.3.2. Total cost estimate 12 1. INTRODUCTION The document describe overview of our job website for Vietnamese developer and student who is senior student or just graduated and have not experience, our expectations of website and the characteristics of the proposed solution for biding jobs website. The intended audience of the Proposal: • The customer, • Project managers (PMs), • Project team, • And any other stakeholders involved in carrying out the project. 1.1 Purpose: The document provides an overview of the project includes the purpose and scope of project. In addition, identify business needs, problems or situation related to the initialization and construction projects. Provide solution for business needs Provide overview about resources, schedule, risk, solution and budget for the project. 1.2 Scope: This document provides an overview of project will be developed. It includes overview of the product, overview of the process and overview of the project team. This document provides a plan for each phase of software development process based on waterfall process include: requirement, design, implementation, verification and maintenance. This is the general plan and will be updated with detail of the software development process in the next version of document. Proposal includes the introduction of solutions, determine the best way to develop software that we make, the total estimated costs, payback period, breakeven volume for the project. 1.3 References: No. Description Location 1 Waterfall process http:en.wikipedia.orgwikiWaterfall(software_development) 2 Business case http:www.freelance.com http:www.upwork.com 2. PROJECT OVERVIEW 2.1. Project definition < Background> 2.2. Business Needs < Customer or Market Needs>< Business Objectives> 2.3. Business Values 2.4. Prior Art 2.5. Proposed Solution 2.5.1. Vision of the Solution 2.5.1.1. Vision Statement 2.5.1.2. Major Features 2.5.1.3. Assumptions and Dependencies 2.5.2. System overview 2.5.2.1. System context 2.5.2.2. System context description 2.5.3. Scope and Limitations. 2.5.4. Business Context 2.5.4.1. Stakeholder Profiles 2.5.4.2. Operating Environment 3. EXPECTED OUTCOME 4. METHOD APPROACH In this project, we use Waterfall process to develop the application. 4.1 Process overview The waterfall model is a sequential (noniterative) design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, productionimplementation and maintenance. The waterfall development model originates in the manufacturing and construction industries: highly structured physical environments in which afterthefact changes are prohibitively costly, if not impossible. Because no formal software development methodologies existed at the time, this hardwareoriented model was simply adapted for software development The following list details the steps for using the waterfall model: 1. System requirements—Establishes the components for building the system, including the hardware requirements, software tools, and other necessary components. Examples include decisions on hardware, such as plugin boards (number of channels, acquisition speed, and so on), and decisions on external pieces of software, such as databases or libraries. 2. Software requirements—Establishes the expectations for software functionality and identifies which system requirements the software affects. Requirements analysis includes determining interaction needed with other applications and databases, performance requirements, user interface requirements, and so on. 3. Architectural design—Determines the software framework of a system to meet the specified requirements. The design defines the major components and the interaction of those components, but the design does not define the structure of each component. You also determine the external interfaces and tools to use in the project. 4. Detailed design—Examines the software components defined in the architectural design stage and produces a specification for how each component is implemented. 5. Coding—Implements the detailed design specification. 6. Testing—Determines whether the software meets the specified requirements and finds any errors present in the code. 7. Maintenance—Addresses problems and enhancement requests after the software releases. In some organizations, a change control board maintains the quality of the product by reviewing each change made in the maintenance stage. Consider applying the full waterfall development cycle model when correcting problems or implementing these enhancement requests. Advantage: 1. Easy to assign work, distribution costs, monitoring of work 2. System architecture stability Disadvantages: 1. The relationship between the stages are not shown. 2. Must end at each stage so difficult to implement full requirements of customers because in this model is very difficult to change the implementation phase. 3. The only contact with the customer in the required phase should take the software does not meet all the requirements of customers. 4. Development costs are relatively large. 5. High possibility of failure. 4.2 Tool and technical Programing: PHP, Laravel 5.xx framework. Web server: LinuxDebian. Operating system: Window 7 or higher, mobile. Develop tools: PHP storm, mysql workbench. Database: MySQL. Internet Connection. 4.3. Costs Estimate 4.3.1. Cost personhours Full Name Role Salary Rate (USDhour) Khang Dao Sy Team Leader 1 Phuc Tran Le Nhat Team Member 1 Tuan Huynh Viet Team Member 1 Khiem Nguyen Binh Team Member 1 5.3.1 Master Schedule Cycle Phase Start End Duration 01 Requirements Specifications 1 System analysis Design 1 Coding and Unit Test 1 Test 1 Deployment and Maintenance 1 01082016 20092016 51 days 02 Requirements Specifications 2 System analysis Design 2 Coding and Unit Test 2 Test 2 Deployment and Maintenance 2 20092016 01112016 31 days Review Final Release 01112016 04112016 3 days 4.3.2. Total cost estimate No Criteria Price Amount Total 1 Working hours 1 1000 1000 2 Gas cost support 15 15 225 3 Lunch cost support 0,5 460 230 4 PC’s depreciation 15 5 75 Total 1530
Proposal document Project Name Version: Date: Mentor: Msc, Nguyen Thi Thanh Tam Document create by: International School – Duy Tan University Project Information Project Title Start Date – End Date Lead Institution Project Mentor Project Manager & Contact detail Partner Organization Team member Document name Document Title Reporting period Author Role Filename Revision History Name Date Comments Version Document Approvals: The following signatures are required for approval of this document Msc Tam Nguyen Thi Thanh Mentor Date Leader Date Table of Contents INTRODUCTION The document describe overview of our job website for Vietnamese developer and student who is senior student or just graduated and have not experience, our expectations of website and the characteristics of the proposed solution for biding jobs website The intended audience of the Proposal: • The customer, • Project managers (PMs), • Project team, • And any other stakeholders involved in carrying out the project 1.1 Purpose: - The document provides an overview of the project includes the purpose and scope of project - In addition, identify business needs, problems or situation related to the initialization and construction projects - Provide solution for business needs - Provide overview about resources, schedule, risk, solution and budget for the project 1.2 Scope: - This document provides an overview of project will be developed It includes overview of the product, overview of the process and overview of the project team - This document provides a plan for each phase of software development process based on waterfall process include: requirement, design, implementation, verification and maintenance This is the general plan and will be updated with detail of the software development process in the next version of document - Proposal includes the introduction of solutions, determine the best way to develop software that we make, the total estimated costs, payback period, breakeven volume for the project 1.3 No References: Description Waterfall process Business case Location http://en.wikipedia.org/wiki/Waterfall(software_developme nt) http://www.freelance.com http://www.upwork.com 2.1 PROJECT OVERVIEW Project definition < Background> 2.2 Business Needs < Customer or Market Needs>< Business Objectives> 2.3 Business Values 2.4 Prior Art 2.5 Proposed Solution 2.5.1 Vision of the Solution 2.5.1.1 Vision Statement 2.5.1.2 Major Features 2.5.1.3 Assumptions and Dependencies 2.5.2 System overview 2.5.2.1 System context 2.5.2.2 System context description 2.5.3 Scope and Limitations 2.5.4 Business Context 2.5.4.1 Stakeholder Profiles 2.5.4.2 Operating Environment EXPECTED OUTCOME METHOD/ APPROACH - 4.1 In this project, we use Waterfall process to develop the application Process overview - The waterfall model is a sequential (non-iterative) design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, production/implementation and maintenance - - The waterfall development model originates in the manufacturing and construction industries: highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible Because no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development The following list details the steps for using the waterfall model: System requirements—Establishes the components for building the system, including the hardware requirements, software tools, and other necessary components Examples include decisions on hardware, such as plug-in boards (number of channels, acquisition 10 speed, and so on), and decisions on external pieces of software, such as databases or libraries Software requirements—Establishes the expectations for software functionality and identifies which system requirements the software affects Requirements analysis includes determining interaction needed with other applications and databases, performance requirements, user interface requirements, and so on Architectural design—Determines the software framework of a system to meet the specified requirements The design defines the major components and the interaction of those components, but the design does not define the structure of each component You also determine the external interfaces and tools to use in the project Detailed design—Examines the software components defined in the architectural design stage and produces a specification for how each component is implemented Coding—Implements the detailed design specification Testing—Determines whether the software meets the specified requirements and finds any errors present in the code Maintenance—Addresses problems and enhancement requests after the software releases In some organizations, a change control board maintains the quality of the product by reviewing each change made in the maintenance stage Consider applying the full waterfall development cycle model when correcting problems or implementing these enhancement requests - - Advantage: Easy to assign work, distribution costs, monitoring of work System architecture stability Disadvantages: The relationship between the stages are not shown 11 4.2 Must end at each stage so difficult to implement full requirements of customers because in this model is very difficult to change the implementation phase The only contact with the customer in the required phase should take the software does not meet all the requirements of customers Development costs are relatively large High possibility of failure Tool and technical - Programing: PHP, Laravel 5.xx framework - Web server: Linux/Debian - Operating system: Window or higher, mobile - Develop tools: PHP storm, mysql workbench - Database: MySQL - Internet Connection 4.3 Costs Estimate 4.3.1 Cost person/hours Full Name Role Salary Rate Khang Dao Sy Team Leader (USD/hour) Phuc Tran Le Nhat Team Member Tuan Huynh Viet Team Member Khiem Nguyen Binh Team Member 5.3.1 Master Schedule 12 Cycle Phase 01 Requirements & Specifications System analysis & Design Coding and Unit Test Test Deployment and Maintenance Requirements & Specifications System analysis & Design Coding and Unit Test Test Deployment and Maintenance 02 Review & Final Release Start End Duration 01/08/2016 20/09/2016 51 days 20/09/2016 01/11/2016 31 days 01/11/2016 04/11/2016 4.3.2 Total cost estimate No Criteria Price Working hours Gas cost support Lunch cost support PC’s depreciation 15 0,5 15 13 Amount 1000 15 460 Total Total 1000 225 230 75 1530 days 14 ... Document name Document Title Reporting period Author Role Filename Revision History Name Date Comments Version Document Approvals: The following signatures are required for approval of this document. .. intended audience of the Proposal: • The customer, • Project managers (PMs), • Project team, • And any other stakeholders involved in carrying out the project 1.1 Purpose: - The document provides an... project 1.2 Scope: - This document provides an overview of project will be developed It includes overview of the product, overview of the process and overview of the project team - This document