Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Help Needed in Doucumentation for GPS Antenna (I am using Patch Antenna)

Status
Not open for further replies.

chwf

Newbie level 5
Newbie level 5
Joined
Nov 23, 2009
Messages
9
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Location
Islamabad
Activity points
1,323
Actually my teacher has given me a assignment that I am a System Engineer and a customer comes to me and asks to design a GPS antenna which will be installed on a bicycle. I have to develop the USER REQUIREMENT DOCUMENT (URD) & SYSTEM REQUIREMENT DOCUMENT (SRD).

SRD will contain the actual antenna (i have selected Patch antenna) design with + all technical stuff. I am confused with URD. What things can I inculde in URD? I know stuff that will be included in SRD.
Can anyone help me with this matter?
 
Last edited by a moderator:

I would guess that the user requirements would consider issues such as :

1. accuracy of position (10m, 20m, 100m ?)
2. battery life of unit (before needing to be recharged)
3. size/bulk/aesthetic-design of the unit (to be able to fit on a bicycle)
...
 
  • Like
Reactions: chwf

    chwf

    Points: 2
    Helpful Answer Positive Rating
I am very grateful to you for help! :) But Sir in assignment the user has only asked me to supply him with just antenna design not the GPS module. Just antenna. The technical parameters will be included in SYSTEM REQUIREMENT DOCUMENT (SRD). I am still confused with the USER REQUIREMENT DOCUMENT (URD).
Can you help me more?
 
Last edited by a moderator:

It is expected that there is overlap with SRD and URD.

You say that you are given the role of a 'system engineer' and then say just focus on the antenna, so I am not clear on that.

URD is written from the perspective of the user of the system. Imagine you are the end user of the system, list what you expect to see in the system, the way you want it to behave, the options that it should have, etc... That forms the basis of your URD.

Do a Google search with the terms, you should find many results.
 
  • Like
Reactions: chwf

    chwf

    Points: 2
    Helpful Answer Positive Rating
Bundle of thanks Sir for your help. You are getting it right. :)
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top