Eye Tracking

EYE TRACKING SYSTEM

Overview Eye tracking system

 This system is used to provide safety to drivers and passengers while driving it helps in tracking individual through eye retina and location GPS  To develop an application of eye tracking with android and IOS for the automobile sector.  To avoid accident when the driver is not alert on the road while driving so it can track their eyes to avoid accident by alarming through the cell phone.

Aims and objective 1 2 3 4

Provide safety to automobile customers

Prevent vehicles from accidents

Track them properly through eye system

Alerts and notifications to end user

SCOPE

1

Admin can track the location and route of employee

3

Eye tracking system is to provide customer safety so that sectors will track their customers either th ey are on right track

2 4

System will prevent the employee from car accident by using eye tracking system.

Alert and notification

Milestone/Deliverables

Detailed Scope will be provided

Signed off by the client before 27/12/19

Create database each customer

30/12/19-10/01/19

Mobile App design

13/01/20 - 17/01/20

Mobile App build

20/01/20- 24/02/20

Mobile App unit testing

25/02/20- 02/03/20

deliverables tracking

03/03/20- 09/03/20

System UAT

10/03/20-16/03/20

Server Deployment or connecting app with eye track system

17/03/20- Tue 31/03/20

Project organization chart PROJECT OWNER

PROJECT MANAGER

Head of Development

Team Lead

Developers

Head of Infrastructure

Business Analyst

SQA Lead

Tester

Associate Business Counsultant

Network engineer

Design and innovation

Infrastructure Engineer

UI/UX Designer

Web designer

WBS 1 Eye tracking system

1.1 Project Management 1.1.1 Initiation

1.4.1 deliverables tracking

1.2.1 technical Planning 1.3.1 Mobile App Design

1.1.2 Planning 1.1.3 Scope Management Project Office 1.1.4 Administration

1.2.2 Technical Supervision

1.2.3

1.2.4

Business requirement definition System requirement definition

Mobile App requirement 1.3.1.1 specification 1.3.1.2 Mobile app work package 1.3.1.3 Mobile app prototyping

1.1.5 Project Communication 1.3.1.4 1.1.6 HR Management

1.4 deliverables Management

1.3 Software development

1.2 System Engineering

Mobile app unit detil design

1.3.2 Mobile app build 1.3.2.1 Mobileapp unit coding

1.3.2.2

mobile app unit debugging

1.3.3 Mobile app unit testing Mobile app unit test 1.3.3.1 planning 1.3.3.2 Mobile unit test cases

1.4.2

deliverables production & packaging

1.5 system test

1.5.1

1.5.2

module & sub system test system integration testing

1.5.3 acceptance testing

1.6 deployement 1.6.1 Client Support document Deoplyement 1.6.2 Management & Coordination 1.6.3 Smoke test Deployement 1.6.4 performance & monitoring

Resource management plan Role

Responsibilities

Project Owner

Sign off on important document and work wit h manager

Project manager

Co-ordinate project team, manage deadlines and communicate between all stakeholders

Design /marketing

Oversees build-out of applications

Head of Development

Planning and execution of applications

Head of IT infrastructure

Overseeing building, installing and testing of technology

Resource management plan

COST MANAGEMENT PLAN  parametric estimating technique will be used  Budget will be determined using cost aggregation

GANTT CHART

GANTT CHART

Procurement management plan Explanation

Sr. No 1.

Designation Project Manger

Procurement Role He/ She are Responsible for overall procurement

activities. 2.

Procurement Manager

Assist the procurement manager and make it sure that required product is procured.

3.

Procurement Manager’s Team

Check and balance of all the activities of procurem

ent. Ensure that right product and required quantit y of product is acquired.

Risk Management Plan ID

RISK description

Severity of risk

1

Project purpose and need not well defined

High

2

Project design & architecture not cleared

High

3

Project schedule not cleared

Medium

4

Estimating or Scheduling Error

High

5

Technical Risks

High

Mitigating Plan

Complete a business case if n ot already provided and ensur e purpose is well defined on P roject Charter.

Define the scope in detail via meetings from experts

Contingency plan

Escalate to the Project Board with an assessment of the risk of runaway costs/never-ending project.

Risk Owner

Project Sponsor

Documents made on assumptio ns and associated risks

Project sponsor

Holding timely meetings with a Share the plan and go through ll project members so to under upcoming tasks on every weekl stand the plan and risk of miss y meeting. ed tasks would be minimized.

Project Manager

Forward this matter to project s ponsor and project board. Rais e change request for change in budget or schedule If technical risks are causing del Experts should be hired to avo ays matter should be forwarded id any technical risk and back to project sponsor for request of up plan should be available change schedule Break this risk into Cost estim ating and Scheduling error

Project Manager

Project Manager

Quality Management plan Quality objectives

Item

Metric

Measurement Method

Project schedule

Time

Schedule Performance index (SPI)= Earned Value / planned

Value Budget

Cost

Cost Performance Index (CPI)=Earned Value /Actual Cost

Quality Management

Quality

No of defects fixed per user acceptance test

Roles

Responsibilities

Project manager

PM will use sprints as a requirement of clients in order to maintain desired quality of short-t erm scope.

Project team

PT will use user story given by PM as per breakdown of sprints to avoid any scope creep a nd as develop deliverables with defined process.

Agile Release Plan

Project closeout Project will be closed after client’s satisfaction by comparing

required vs. actual in this process Prototype which was passed by client earlier will be compare d with final one along with user manual. Final performance r eport will be documented and lessons learned will be updated in register for future projects. Project Closing Process



Confirm that work is done as per requirement



Complete final performance reporting



Closing Documents

At the time of closing these are the requirement of project 

Handing over Technical documents.



User manuals.



Singing off Documents.

Thank you