processes(e07 073)

CASE Islamabad

Group Members:

Sehar Shafqat E07-072

Zia-ul-Hassan E07-073

Qudsia Fatima E07-086

Javeria Ghani E07-129

Project Supervisor : Dr. Shoaib Ahmed Project Advisor : Dr. Asad Mehmood

OSSIE Running on GPP with DSP/FPGA on SDR Platform

Table of Contents

Introduction 3Project Management Process Group 4Initiating Process Group 51.1 – Project Charter 61.2 – Identify Stakeholder 10

Stakeholder Register 11Stakeholder Management Strategy 13

Planning Process Group 142.1 – Develop Project Management Plan 14

Project Management Plan 152.2 – Collect Requirements 22

Requirement documentation 22Requirement Management Plan 25Requirement Traceability Matrix 28

2.3 – Define Scope 30Project Scope Statement 31

2.4 – Create WBS 332.5 - Define Activities 332.6 – Sequence Activities 332.7 – Estimate Activity Resources 332.8 – Estimate Activity Durations 332.9 - Develop Schedule 332.10 – Estimate Costs 332.11- Determine Budget 34

Project Funding Requirement 352.12- Plan Quality 36

Quality Management Plan 36Quality Metrics 40Quality Checklists 40Process Improvement Plan 40

2.13 – Develop Human Resource Plan 41Human Resource Plan 42

2.14 - Plan Communications 44Communication Management Plan 45

2.15 – Plan Risk Management 46Risk Management Plan 47

2.16 – Identify Risks 49Risk Register 50

2.20 – Plan Pocurement 51Procurement Management Plan 52

INTRODUCTION TO SDR

Software Defined Radio (SDR) is a communication system in which components that have typically been implemented in hardware like mixers, filters, modulators/demodulators, detectors, etc. are implemented in software on a desktop environment or on a embedded system. By using this approach same piece of hardware may be used to implement different functions at different times.

Development of Software Defined Radio (SDR) technology is a revolution in radio design which promises to produce radios which can change their personality on fly, It’s a new paradigm in radio design which provides a framework by which radios can be reconfigured dynamically to satisfy user requirements. SDR employs reprogrammable signal processing elements maximally and analog portion is kept at minimum to provide flexible and reconfigurable device. This technology is evolving rapidly and wireless communication community has recognized its advantages. Due to which SDR’s have received considerable attention and it is one of the major research acitivities in wireless communication curriculum and industry.

After the initiation of JTRS program of the US Department of Defense , Software communication Architecture (SCA) has been developed and is a key enabler for SDR technology. SCA is developed to be able to port waveforms across the various radios in the JTRS family. This architecture assists in the development of SDR while capturing the benefits of recent technology advances. SCA greatly enhances interoperability of communication systems and reduces development and deployment costs. By using SCA, developers may use any combination of general puropose processor (GPP), digital signal processor (DSP) and field programmable gate array (FPGA) devices within which implementations of an SDR.

SDR technology offers several benefits to radio equipment manufacturers, service providers and end users like

Different radio products can be implemented using common hardware platform, allowing new products to be launched quickly.

Same software may be reused across different radio products which greatly reduces development cost.

New features may be added to existing infrastructure thus reducing capital expenditures to provide these features.

End users will be able to communicate with whomever they will need, whenever they will need and in whatever manner will be appropriate.

Project Management Process Groups

Initiating Process Group

1.1 Develop Project Charter

1.2 Identify Stakeholders

Planning Process Group

2.1 Develop Project Management Plan2.2 Collect Requirements2.3 Define Scope2.4 Create WBS2.5 Define Activities2.6 Sequence Activities2.7 Estimate Activity Resources2.8 Estimate Activity Durations2.9 Develop Schedule2.10 Estimate Costs2.11 Determine Budget2.12 Plan Quantity 2.13 Develop Human Resource Plan 2.14 Plan Communications2.15 Plan Risk Management2.16 Identify Risks2.17 Perform Qualitative Risk Analysis2.18 Perform Quantitative Risk Analysis2.19 Plan Risk Responses2.20 Plan procurements


1.1 - Develop Project Chater

Project Chater

Project Name: OSSIE running on GPP with DSP and FPGA on SDR platform.

Project Manger: Muhammad Zia ul Hassan.

Date: November 22, 2010 Point of Contact : 0334-5360590

1. PROJECT GOALS

To deploy the OSSIE software on the Davinci platform and writing proxies for GPP with DSP/FPGA. The main rationale of interfacing is to develop communication between two entirely different protocols. For example, Protocol ‘A’ is GPP dependent, while Protocol ‘B’ is DSP dependent. This way, we can communicate and manage both the technologies.

By establishing the interface between GPP and FPGA/DSP, GPP’s load has been subdivided. Increase of efficiency and enhancement of signal processing can be achieved in this way. The task of signal processing is done purely by the DSP.

2. DELIVERABLES

1 – Running OSSIE on the GPP processor.2 – Running of OSSIE on the DSP processor3 - Integrating both DSP and GPP.4 – TMS320dm6446 DIVINCHI platform. 5 – SDR(Software Defined Radio) board.6 – Power board for the SDR.7 – OSSIE amended software.8 – USRP receiver board.9 – USRP transmitter board.10 – Handouts/Manuals in English only.

3. SCOPE DEFINITION

1 – To research about the previous work. 2 – Research about the interfacing techniques of GPP with DSP/FPGA.3 – Deploying of OSSIE on the GPP processor.4 – Developing a generic code for GPP and DSP.5 – Integrating the code as such that the code is burn in DSP and the functions are called in GPP.6 – Managing the communication between them by CORBA tools. 7 – Writing proxies for FPGA.

4. PROJECT MILESTONE

1- Completion of Planning.2- Deploying of OSSIE on GPP processor.3- Deploying of OSSIE on DSP proceesor.4- Interfacing of GPP with DSP and FPGA.

5. ASSUMPTIONS, CONSTRAINTS

The price of TMS320DM6446 might change because of inflation or shipping charges. To meet the requirement of the project we have to use the specific model of divinchi platform as specified by the customer. If for some reasons, it is unavailable in the market then we have to develop alternative , which may take more time

Constraints is that we have to use Divinchi platform model # TMS320DM6446 because of shared memory.

We have to use USRP board of frequency that is not already used.

6. RELATED DOCUMENTS

Related Documents are Manuals of whole project and training manuals that will guide the user, how to use the product. It also include RFP, Scope statement, project charter, BOQ and RTM etc.

7. PROJECT MANGER

Project Manger of the project is Muhammad Zia ul Hassan. He is responsible for managing and completion of the project in time. He controls the Human Resource and Cost issues as well. Four person are doing this project. And their skill and roles are given below.

Name Role

Muhammad Zia-ul –Hassan Project Manger

Sehar Shafqat Research

Qudsia Fatima Interfacing of DSP and GPP.

Javaria Ghani Interfacing of GPP and FPGA

8. PROJECT SCHEDULE

– Manufacturing of SDR Board. (4 Weeks)– Research about the interfacing techniques of GPP with DSP/FPGA. (2 Weeks)- Integrating both DSP and GPP (3 Weeks)– TMS320dm6446 DIVINCHI platform (3 Weeks)– SDR(Software Defined Radio) board test (2 Weeks)– Power board for the SDR. (1 Week)– OSSIE amended software (4 Weeks)– USRP receiver board. . (1 Week)– USRP transmitter board. . (1 Week)– Handouts/Manuals in English only. (2 Weeks)

9. BUDGET

The Overall budget required for the project is $25000. Summary of the budget is

To start the project $12500Mid of the project $7500After 2 weeks $2500Couple of weeks before the completion $2500

10. Approvals

Project Manger of the project is Muhammad Zia ul Hassan. He is responsible for managing and completion of the project in time. He controls the Human Resource and Cost issues as well. Four person are doing this project. And their skill and roles are given below.

Name Role

Dr.Shoaib Main Advisor

Dr Asad Surpervisor

Muhammad Zia-ul-Hassan Project Manger


1.2 - Identify Stakeholders

Stakeholder Register

Stakeholders

Dr. Shoaib Project Supervisor Dr. Asad Project Advisor Dr. Hammad Ahmed SDR Board providing authority Dr. Farrukh Kamran Working on SDR Saleh Usman Training Man on SDR Board Project Team CARE Customer Mr. Raheel Butta Coordinator Project Manager

Power / Interest High Medium Low

High Dr. Shoaib Mr. Hammad Ahmed

Medium Dr. Asad CARE/Mr. Raheel Dr. Farrukh Kamran

Low Project Manager Project Team Saleh Usman

Power / Interest Grid

Power / Influence High Medium Low

High Dr. Shoaib / Mr. Hammad

Medium Dr. Asad CARE Dr. Farrukh/Mr. Raheel

Low Saleh Usman Project Manager Project Team

Power / Influence Grid

Influence/Impact High Medium Low

High Dr. Shoaib/Dr. Asad Mr. Hammad

Medium Mr .Saleh/Project Manager CARE

Low Mr. Raheel Project Team Dr. Farrukh

Influence / Impact Grid

Stakeholder Register

Stakeholder name

Department (organization)

Communication Type

Type of Stakeholder

Role Expectation from project

Dr. Shoaib CEO Weekly Meetings Internal Provide Resources

Communication between the protocols

Dr. Asad Advisor Daily Meetings Internal Technical Support

Completion of Project

Mr. Hammad Head of Department

Nil Negative Negative

Dr. Farrukh Head of Electronics

Nil Negative Negative

Saleh Usman Teacher Assistant

Daily Meetings Internal Training Classes

Project Team Daily Meetings Internal Performing Project

Completion of Project

CARE Client Emails External Sponsor Completion in time

Mr. Raheel Butta

Coordinator Monthly Meetings External Keeping track of project

Completion in time

Project Manager

Daily Meetings Internal Organizing the project

Promotion

Initiating Process Group 1.2 – Identify Stakeholders

Stakeholder Management Strategy

Stakeholder Management Strategy

The stakeholder management strategy defines an approach to increase the support and minimize negative impacts of stakeholders throughout the entire project life cycle.

Name Strategy

Dr Shoaib As shown in the grid, Dr. Shoaib has power , interest and influence. So this person should be keep satisfied.

Dr Asad From grid , we know that Dr. Asad is main supervisor of the project. So, Dr. Asad should be keep informed during the whole project.

Mr. Hammad This person have negative influence towards the will of the project.So this person should be ignored.

Dr. Farrukh Dr. Farrukh has low interest and low influence on the project. So need to update him is not necessary.

Project Team Project Team includes all the members that perform the project. So, we need to satisfy them so that project will complete in time.

Project Manager Performing project as assigned and keeping the stakeholders informed about the results and problems

Saleh Usman Keep satisfying him until the training completed.

Mr. Raheel Provide deliverables to the required date.

CARE Provide the key deliverable to the required date.

Planning Process Group2.1 – Develop Project Management Plan

Project Management Plan

INTRODUCTION

SDR

Software Defined Radio (SDR) is a communication system in which components that have typically been implemented in hardware like mixers, filters, modulators/demodulators, detectors, etc. are implemented in software on a desktop environment or on a embedded system. By using this approach same piece of hardware may be used to implement different functions at different times.

Benefits of SDR

SDR technology offers several benefits to radio equipment manufacturers, service providers and end users like

Different radio products can be implemented using common hardware platform, allowing new products to be launched quickly.

Same software may be reused across different radio products which greatly reduces development cost.

New features may be added to existing infrastructure thus reducing capital expenditures to provide these features.

End users will be able to communicate with whomever they will need, whenever they will need and in whatever manner will be appropriate.

Project Purpose

By establishing the interface between GPP and FPGA/DSP, GPP’s load has been subdivided. Increase of efficiency and enhancement of signal processing can be achieved in this way. The task of signal processing is done purely by the DSP.

To deploy the OSSIE software on the Davinci platform and writing proxies for GPP with DSP/FPGA. The main rationale of interfacing is to develop communication between two entirely different protocols. For example, Protocol ‘A’ is GPP dependent, while Protocol ‘B’ is DSP dependent. This way, we can communicate and mange both the technologies.

PROJECT MANAGEMENT APPROACH

The Project Manager, Mr Muhammad Zia ul Hassan has the overall authority and responsibility for managing and executing this project according to this Project Plan and it Subsidiary Management Plans. The project team will consist of personnel from as designed by P.M.

PROJECT SCOPE

The scope of the project is to interface OSSIE running on GPP with DSP and FPGA, on an SDR platform. For this purpose, first we try to search out the specific models of gpp, dsp and fpga. And then we manufacture the SDR platform. After the manufacturing of the SDR platform, we will try to interface the GPP and DSP. Then we will cross compiled the source files of OSSIE software that are available at the open embedded site. First we cross compiled it for GPP only. Then we generate the binary file of the compiled file and transfer it to the memory of the GPP via NFS technique. After all this, we just simple try to write the protocol through which GPP and DSP will communicate with each other. After this we will pass the signal to GPP, GPP will transfer this signal to the DSP for digital signal processing . DSP will send back the processed signal back to the GPP. Here, GPP is controlling all the management process. By this, we can communicate between two entire different protocols. For example, Protocol ‘A’ is GPP dependent, while Protocol ‘B’ is DSP dependent. This way, we can communicate and mange both the technologies.

MILESTONE LIST

Milestones Deliverables

Completion of Planning Project Management plan. Scope baseline Schedule baseline Cost performance baseline Quality matrices

Deploying of OSSIE on GPP processor.

Running of the test waveform

Deploying of OSSIE on DSP processor.

Running of the Test waveform

Interfacing of GPP with DSP and FPGA.

Passing a signal to GPP and get the processed signal through DSP

SCHEDULE BASELINE AND WORK BREAKDOWN STRUCTURE

The schedule baseline and work breakdown structure (WBS) is created in Microsoft Project. Ms project file is attached with this file.

PROJECT CHANGE CONTROL PROCESS

If Project manager sees any variances in the project keeping in view the baselines i.e. Cost, Schedule, Scope baselines. PM will call a meeting and then those variances will be discussed and using the standard rules and procedures in OPA further action will be taken. Budget forecast and quality checks processes may be taken into account to minimize the effect of changes.

Cost Baseline

The cost performance baseline will be managed by presenting the finance department with weekly audit reports so that a check is applied over the cost of the project and possible variances. It will be decided by the project manager how much variance is acceptable for a certain task, if the variances are large the project manager will call an immediate meeting of the project team members and will try to find out the reason for such variances if he find the issue to be too complex to handle then a meeting involving the organization’s high ups will be arranged and all possible solutions including the increase in project funding will be discussed but only as a last resort.

Scope Baseline

It will be the responsibility of the project manager to look into the performance of the team members and assess their tasks assigned to verify their scope, in case of any variances the team will be directed to change their line of action, no such variances can be assigned because it is an issue of serious nature because scope variances directly affect the cost and schedule. As the project progresses, changing project scope can be fatal so avoiding the scope changes and changing the working method is recommended.

Schedule Baseline

The project manager will lead the team and it will be his responsibility to complete the tasks on time, for this purpose the project manager will call weekly meetings with the project team to assess their performance and will try to find out if the problems in the due completion of the tasks, the team leader is bound to send performance reports daily or after 2 days depending upon the nature of the task. Project manager will take care of the staff. Using interpersonal skills, P.M will do conflict management and will keep the team on board and unite. If some sort of problems are coming in the project the project manager will look into them and if they are out of his control then a meeting will be called and all possible solutions will be discussed including some extra time for the completion of a task. And after than the desired stakeholders will be taken into confidence. Using communication management plan keeping the desired stakeholders updated as asked and ordered. In case of continuous failures to meet the deadlines some sort of change in the current setup of the project team will be initiated which might include replacement of team members and the team leader as well but that would be in inevitable circumstances

PROJECT SCOPE MANAGEMENT PLAN

This project is carried out in order to convert SDR board into a complete SCA compliant platform by gradually making all of the hardware pieces SCA compliant. A logical step for this purpose will be to make digital signal processor (DSP) and FPGA available on SDR board, SCA compliant. There may be two ways to proceed in this direction; one is to add device proxies of DSP and FPGA by encapsulating drivers of DSP/FPGA in SCA device abstraction. In this approach, CORBA actually runs on GPP and all of the devices communicate through it.

Project Exclusions

When protocols would be executed simultaneously, the running of these protocols on the DIVINCHI platform is our main scope of the project but if we don’t run out of time then we will implement this on SDR and transmit the signals with the help of USRP

Project AssumptionsNo big changes in scope and time line are expected. Management and engineering staff will be readily available.

Project Constraints Project due in one year. Project cost is not to be higher than Rs. 20Million. We have to use Divinchi platform model # TMS320DM6446 because of shared memory.

Acceptance Criteria

The definitions of acceptance criteria can significantly increase or decrease project costs and quality costs. This project acceptance criteria includes:

Performance Requirements Documentation for obtaining the Project Acceptance Agreement is approved.

The project is aligned with the NextGen needs, goals and objectives.

The technical quality standard is adequate.

The schedule is adequate and consistent with cost, risk and mission goals.

Deliverables including budget are adequate and available.

Adequate integration plans and procedures are completed for the SDR system.

Developed component, subsystem, and system test results form a satisfactory basis for approval.

Objectives obtained within agreed tolerable risk level

The interfacing procedures and work flow have been clearly defined and documented.

Handouts/Manuals give appropriate understanding in the interfacing and safety procedures.

WBS

Work breakdown structure (WBS) is created in Microsoft Project. Ms project file is attached with this file.

Work Performance Measurement

The engineering staff and contractors will develop analytical models to predict the performance of the Execution of OSSIE_DEMO waveform on GPP of DM6446. Systems engineering will coordinate these efforts and to the extent possible will integrate these analyses to provide end-to-end modeling of the total system performance. These analyses will be repeated as the designs develop to provide improved performance predictions and to allow adjustments in error budgets, interfaces, and design requirements.

SCHEDULE MANAGEMENT PLAN

Project schedules will be created using MS Project 2007 starting with the deliverables identified in the project’s Work Breakdown Structure (WBS). Activity definition will identify the specific work packages which must be performed to complete each deliverable. Activity sequencing will be used to determine the order of work packages and assign relationships between project activities. Activity duration estimating will be used to calculate the number of work periods required to complete work packages. Resource estimating will be used to assign resources to work packages in order to complete schedule development.

Once a preliminary schedule has been developed, it will be reviewed by the project team and any resources tentatively assigned to project tasks. The project team and resources must agree to the proposed work package assignments, durations, and schedule. Once this is achieved the project sponsor will review and approve the schedule and it will then be base lined. MS project document file is attached to this file which contains all the scheduled activities.

COST MANAGEMENT PLAN

The Project Manager Mr. Muhammad Zia ul Hassan will be responsible for managing and reporting on the project’s cost throughout the duration of the project. During the monthly project status meeting, the Project Manager will meet with management to present and review the project’s cost performance for the preceding month. Performance will be measured using earned value. The Project Manager is responsible for accounting for cost deviations and presenting the Project Sponsor with options for getting the project back on budget. The Project Sponsor has the authority to make changes to the project to bring it back within budget.

Costs for this project will be managed in the Work Breakdown Structure (WBS). Control Accounts (CA) will be created at this level to track costs. Earned Value calculations for the CA’s will measure and manage the financial performance of the project. Although activity cost estimates are detailed in the work packages, the level of accuracy for cost management is at the fourth level of the WBS. Credit for work will be assigned at the work package level. Work started on work packages will grant that work package with 50% credit; whereas, the remaining 50% is credited upon completion of all work defined in that work package. Costs may be rounded to the nearest dollar and work hours rounded to the nearest whole hour.

Subsidiary Plans

Plans Reference No.

Requirement Management Plan 2.2

Quality Management Plan 2.12

Human Resources Management Plan 2.13

Communications Management Plan 2.14

Risk Management Plan 2.15

Procurement Management Plan 2.20

Process Improvement Plan 2.12

Planning Process Group2.2 – Collect Requirements

Requirement Documentation

Requirement Documentation

Stakeholder Requirement Influence Priority Acceptance Criteria

Dr Shoaib In time Completion and Product as demanded using resources efficently

Head of Organization

High Meeting the expectations of customer and best utilizing of the resources and keeping the cost as low as possible within quality constraints

Mr. Raheel Monitoring and checking the work and the deliverables according to quality standards and Customer needs, Expecting that procedures have been followed correctly.

Accepting a product. Has great influence on the project. If quality not met than Deliverables are useless.

High Monitoring the deliverables and sub processes , verifying the quality standards and its implementation.

M. Zia ul Hassan Implementation of the work to produce deliverable and Expecting to do in given time providing the budget as

Handling the project and dealing with situations

Medium In time Completion using lest cost and meeting customer satisfaction.

Saleh Usman Expert of his Department. Expecting to deal with a good cooperating team.

Technical work support and expert.

Medium Performing the tasks and producing technical output as demanded.

CARE Giving the opportunity of business and expecting quality standards being met as asked in producing deliverables

Awarding the Project with best ouput/Services and consuming less cost.

High Product which is Cheap, Not fragile, Power efficient and meeting the quality standards prevalent in market.

Team Members Completing the work as assigned

Doing the work as asked.

Low Doing work as demanded wholeheartedly

Planning Process Group2.2 – Collect Requirement

Requirement Management Plan

Purpose

We have undertaken this project to benefit people. If talking about the benefit of this project, the main benefit is that we would able to communicate between different protocols. For example, in board prospective, Protocol ‘A’ is GPP dependent and Protocol ‘B’ is DSP dependent and in this way, we can communicate and manage both the technologies i.e. GSM and CDMA. By doing this, limits of communications will come to an end and it will handle the signal’s traffic efficiently. Another benefit is that this system handles more users at a time. So it will reduce the call rates as well.

Objectives

The GPP’s load can be subdivided by establishing the interface between GPP and FGPA/DSP and by the establishment of this interface, efficiency and enhancement of signal processing can easily be achieved. DSP will be responsible for the task of signal processing.

To learn OSSIE software for deployment on Davinci platform. To learn ways of writing proxies (Device drivers) for DSP and FPGA Passing two numeric numbers / signals (as an argument) from GPP to DSP/FPGA and get the

result of any arithmetic operation performed on them.

Quality Requirements

PCB design of SDR Board Soldering Standard Quality of PCB used Serial Cable Quality High performance PC Long Ethernet Cable High Speed Internet


Project Constraints Project due in one year.

Project cost is not to be higher than Rs. 20Million. We have to use Divinchi platform model # TMS320DM6446 because of shared memory.

Acceptance Criteria











Handouts/Manuals give appropriate understanding in the interfacing and safety procedures

Training Requirement

Understanding of OSSIE software SDR Board understanding

Cross compilation of OSSIE

Understanding of NFS tools

Learning of LINUX

Memory Usuage of DM6446

Planning Process Group2.2 – Collect Requirements

Requirement Traceability Matrix

Requirement Traceability Matrix

Clause RFP Reference

Proposal Reference

Contract Reference

Planning Reference

Related Clauses

Start date 1 2

Completion date

1

Budget 7 7 5 1.1 2.11

Acceptance Criteria

5 2.3 2.4,2.12

Scope 3 4 3 2.3 2.4,2.12

Termination 9

Assumptions 2.3 2.4,2.12

Constraints 2.3 2.4,2.12

Planning Process Group2.3 – Define Scope

Project Scope Statement

Project Scope

To interface OSSIE running on GPP with DSP and FPGA, on an SDR platform.The scope of the project is to interface OSSIE running on GPP with DSP and FPGA, on an SDR platform. For this purpose, first we try to search out the specific models of gpp, dsp and fpga. And then we manufacture the SDR platform. After the manufacturing of the SDR platform, we will try to interface the GPP and DSP. Then we will cross compiled the source files of OSSIE software that are available at the open embedded site. First we cross compiled it for GPP only. Then we generate the binary file of the compiled file and transfer it to the memory of the GPP via NFS technique. After all this, we just simple try to write the protocol through which GPP and DSP will communicate with each other. After this we will pass the signal to GPP, GPP will transfer this signal to the DSP for digital signal processing . DSP will send back the processed signal back to the GPP. Here, GPP is controlling all the management process. By this, we can communicate between two entire different protocols. For example, Protocol ‘A’ is GPP dependent, while Protocol ‘B’ is DSP dependent. This way, we can communicate and mange both the technologies.

Project Exclusions

When protocols would be executed simultaneously, the running of these protocols on the DIVINCHI platform is our main scope of the project but if we don’t run out of time then we will implement this on SDR and transmit the signals with the help of USRP


Project Constraints Project due in one year.

Project cost is not to be higher than Rs. 20Million. We have to use Divinchi platform model # TMS320DM6446 because of shared memory.

Acceptance Criteria













2.4 – Create WBSMS project file is attached.

2.5 – Define ActivitiesMS project file is attached.

2.6 – Sequence ActivitiesMS project file is attached.

2.7 – Estimate Activity Resources

MS project file is attached.

2.8 – Estimate Activity DurationsMS project file is attached.

2.9 – Develop ScheduleMs project file is attached.

2.10 – Estimate CostsMs project file is attached.

Planning Process Group2.11 – Determine Budget

Project funding Requirements

Project Funding Requirements

The Overall budget required for the project is $25000. Summary of the budget is

To start the project $12500Mid of the project $7500After 2 weeks $2500Couple of weeks before the completion $2500

2.12 – Plan Quality Quality Management Plan

Project Scope

The GPP’s load can be subdivided by establishing the interface between GPP and FGPA/DSP and by the establishment of this interface, efficiency and enhancement of signal processing can easily be achieved. DSP will be responsible for the task of signal processing.

To learn OSSIE software for deployment on Davinci platform. To learn ways of writing proxies (Device drivers) for DSP and FPGA Passing two numeric numbers / signals (as an argument) from GPP to DSP/FPGA and get the

result of any arithmetic operation performed on them.

Purpose

The purpose of this Quality Management Plan is to ensure that the project will satisfy the needs for which it was undertaken.

This Quality Management Plan includes “all activities of the overall management function that determine the quality policy, quality standards, and responsibilities and implements them by means such as quality planning, quality control, quality assurance and quality improvement.

Acceptance Criteria












Quality Requirement

PCB design of SDR Board Soldering Standard Quality of PCB used Serial Cable Quality High performance PC Long Ethernet Cable High Speed Internet

Quality Assurance Quality Assurance is to ensure manufactured and purchased parts meet specified requirements. The subjects covered in the quality assurance will include:

configuration control procedures for building waveforms, loading kernel, and project documents used for the fabrication of parts or subassemblies

procedures for incoming inspection of purchased parts to ensure they meet specifications

procedures for identification and control of parts in inventory requirements to be imposed on contractors who are manufacturing parts or subassemblies for the

project

Quality standardsQuality standards helps us determing the quality of our product and process. . Most of the times quality standards are by the customer. Identifying customer about the quality client needs will be the standards of the organization for that particular project.

The major deliverables of the project that will be tested for satisfactory quality level. The quality standards and the correctness and completeness criteria established for the project

deliverable. Included are any organizational standards that need to be followed. The quality control activities that will be executed to monitor the quality of the deliverables. How often or when the quality control activity will be performed.

Roles and Responsibilities

Quality manager will monitor it throughout the entire project according to the requirement and schedule. He will be responsible for assuring that all the activities carried out under the Project are within the quality standards. The Quality Manager will equally be supported by the Project Manager.

To explain the requirements of clients to the sales and marketing department and identify the ways in which the organization can meet them.

To analyze various business statistics. To determine the areas of improvement and document them.

Planning Process Group2.12 - Plan Quality

Quality Metrics, Checklists

And

Process Improvement Plan

Quality Metrics

BPSK signal checking Memory usage Calculations Communication Between GPP and DSP Number of successful run Latency and delay Calculations

Quality Checklists

Process Good/Bad Quality

Quality of PCB Good

Components used for signals Avg

BPSK signal Checking Good

QPSK signal Checking Bad

Memory Overhead Bad

Process Improvement Plan

Process Improvement plan is required when customer wants some more advancement in the product , service or result. If the client wants to improve the quality of product. We may follow these steps:

Improve the communication protocol so that we can efficiently use the device. Improve the memory capacity of the device. Improve the speed of the processing processors. Attach more accessories to increase the features. Develop the advanced software to use it efficiently.

Planning Process Group2.13 – Develop Human Resource Plan

Human Resource Plan

Roles, Responsibilities, and Authority

Role Authority Responsibility

Mr. M. Zia ul Hassan

(Project Manager)

Has the authority to make change in project management plan and the methods of doing the project.

Looking after the project’s management processes, reviewing the team’s performance and improving the processes to increase project performance efficiency.

Javaria Ghani Has to authority to change the protocol writing methods between the GPP and DSP communication.

Lead the Team about the communication methods and other issues related to memory handling.

Sehar shafqat Has the authority regarding project’s research related issues as the task assigned is to do research about the specific issues. Otherwise has limited or no authority regarding project’s management affairs.

Whenever issue is raised , she should study about the issue.

Qudsia Fatima Has the authority regarding the communication related issues between GPP and FPGA.

She has to write the communication method between GPP and FPGA. It is her responsibility to handle issue related to them.

Saleh Usman Has the authority to train on different workshops regarding learning of SDR Board, linux and cross compiling of software’s for SDR Board. Has no authority regarding project management plan .

He has responsibility to conduct training as scheduled.

Staffing Management Plan

Staff Acquisition

The team will be selected based upon the needs of the project. In this project, there is a need of electrical engineers with specialization in power electronics and have strong programming background. Since the organization has such workforce so there is no need for outsourcing.

Staff Release

After completion of the project the team members will be sent back into their respective departments. It is mandatory on them to write a project experience report and mention the changes if needed in the organization’s project conducting procedure and other engineering related processes. Bonus will be given to each team member.

Training Needs

Training courses will be initiated to train the team and equip them with the basic knowledge so that they can use the software being used in the project.

Rewards and Recognition

Other than the regular pay the project team members will be paid additionally and also travel expenditures will be paid, because during the project they might have to travel extensively meeting the project stakeholders, conducting procurements etc. At the completion of the project each team member will be given a reward in the form of bonus and during the project, fortnightly project team performance will be assessed and performance appraisal will be conducted based upon each member’s performance. The team member’s will be free to express their perception towards project manager.

Regulations, Standards, and Policy Compliance

The team members will report to team leader and can report the project manager if they feel team leader’s performance is not satisfactory in other words only in extreme situations otherwise they will interact with team leader only, but they will not report the CEO directly. To communicate with CEO and other functional managers only project manager is authorized. The team leader will report the project manager only as according to organization’s policies.

Planning Process Group2.14 - Plan CommunicationsCommunications Management Plan

Communication Management Plan

Message Audience Method Frequency Sender

Status reports, performance reports, project

Dr. Shoaib Presentations, meetings.

Weekly Meetings Project Manager

updates.

Status reports, performance reports, project updates, individual team member’s performance.

Mr. Raheel Butta Presentations, Performance Reports

Monthly Project Manager

Status reports, performance reports, project updates.

Dr. Asad Meetings Daily meetings Any Member

Key success Deliverables

Client Monthly Performance Reports

Monthly CEO

Cost and Budget Issues

Client and CEO Cost performance reports

Occasionally Project Manager

Issue log Project Manager Phone talk Depends upon the occurrence of issue

Team Member

Change Requests CEO Meetings Weekly Project Manager

Communication Constraints or Assumptions

The Project Manager will communicate with all the relevant stakeholders including the CEO and the customer and will present them with project performance reports. The Project Manager will bring in notice the cost and schedule performance to the CEO. The customer will not be briefed about the cost and schedule performance of the project at all. Team members will communicate to the CEO or other stake holders through the project manager.

Planning Process Group 2.15 – Plan Risk Management

Risk Management Plan

RISK MANAGEMENT APPROACH

The approach we have taken to manage risks for this project included a methodical process by which the project team identified, scored, and ranked the various risks. The most likely and highest impact risks were added to the project schedule to ensure that the assigned risk managers take the necessary steps to implement the mitigation response at the appropriate time during the schedule. Risk managers will

provide status updates on their assigned risks in the bi-weekly project team meetings, but only when the meetings include their risk’s planned timeframe. Upon the completion of the project, during the closing process, the project manager will analyze each risk as well as the risk management process. Based on this analysis, the project manager will identify any improvements that can be made to the risk management process for future projects. These improvements will be captured as part of the lessons learned knowledge base.

RISK IDENTIFICATION

The Process of Risk identification is simple to ease the identification of risk. Any team member can identify the Risk. For this purpose, the organization environment must be friendly to tackle the risk. On the identification, project manager must call the urgent meeting and call the team to brain storm about the risk and its impact. Calculate the cost and time effect of the risk etc.

Roles and Responsibilities

Project Manager chairs the risk assessment meetings. Project team participates in risk assessment meetings and members serve as meeting recorder and

timekeeper. Key stakeholders participate in risk assessment meetings. Sometimes key stakeholder “Customer”

isnot included when risk is internal and not external. Project Sponsor may participate in risk assessment meetings.

Baseline Thresholds

Thresholds means that we set the minimum and maximum limit to minimize the risk. For example for the cost and time are shown in table given.

Risks Max Min Normal

Time 140 days 170 days 154 days

Cost $20000 $30000 $25000

Risks

Hardware issues of SDR Board Availability of Training Man Cost issues Natural Disaster

Fever Problems Time line of Project Research Issues Inflation Client Dissatisfaction Market Conditions Electricity Problems Shipment Issues

Risk Monitoring

All the process of Risk monitoring is done by calculating the Probability and impact of the specified Risk. Priorities are assigned accordingly to all the risks. And then handled accordingly. The process of risk monitoring is done by the using Risk Register, which is given below in this document. Project Manger usually use risk register to monitor the risk. Qualitative and Quantitative methods are used to find the impact and occurrence probability of the risk . In the case of identification of new risk, Risk Register is updated accordingly. Risk monitoring will be a continuous process throughout the life of this project. As risks approach on the project schedule the project manager will ensure that the appropriate risk manager provides the necessary status updates which include the risk status, identification of trigger conditions, and the documentation of the results of the risk response.

Planning Process Group2.16 – Identify Risks

Risk Register

Risk Register

Statement Of Risk

Priority Probability Possible Causes Impact Response

Hardware issues of SDR Board

High 60% Hardware failure or wiring issues

Cost and time schedule

Improve the hardware implementation techniques.

Availability of Training Man

High 90% Less Pay Time and cost even result in failure of project

Satisfy by paying extra money or arrange someone new.

Cost issues Medium 25% Inflation Cost Variance Extra Budget must be improved.

Natural Disaster

Low 2% Floods, earth quakes etc

Time line of project

Ignore that risk

Fever Problems

Low 1% Viral Attack due to season

Schedule baseline Ignore that risk

Over Budgeting

High 10% Inflation, poor handling of budget etc

Client dissatisfaction, loss in project profit

Extra Budget must be improved.

Inflation High 20% Increase value of Dollar in a local region

Cost Variance Extra Budget must be improved or report client about this.

Shipment Issues

High 50% Crisis in region Project Start will be delayed.

Early orders of shipment

Electricity Problems

High 50% Low production of a country.

Cost, quality and time line of project.

Use generators.

Planning Process Group2.20 – Plan ProcurementsProcurement Management Plan

Procure Management Plan

Procurement Authority

The procurement authority is assigned to the project manager and he can procure the required material for the project.

Role of Project Manager

He will prepare procurement requirement document with the consultation of project team leader. He will look after the needs of the project and the things needed to be procured. It will be the responsibility of project manager to procurements should be timely The project manager will prepare audit report of the procurements made. Any constraints and assumptions that could affect planned procurements.

Procurement Department

The procurement department has laid down rules for procurements. It is the responsibility of procurement department to made the things available on time. The procurement department will ask the authorized suppliers about the availability of the

components, devices and equipment available or not. Managing multiple suppliers.

Standard Procurement Documents

1. Request For Proposal.2. Request For Quotation.3. Tender Notice.4. Invitation For Seller’s Initial Response.

Selection Criteria

The selection criteria is depends upon the low cost and rapid production of required PCB’s of SDR board. The technical capability of organization must be strong. Experience will count. The organization must know precisely the need of the quality of the client organization.

List

Tmsdm6446 processors High Quality PCB mounted the required design Connecting hardware cables PC having capability to run linux. Work stations

Procurement Assumptions and Constraints

The procurements will be on time but as the funds are limited so the procurements should be limited and we have to complete the tasks and responsibilities with the available devices, equipments and supplies.