From: Patrizio Boschi <patrizio.boschi@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Help on effort estimation
Date: Sat, 14 Mar 2009 17:17:19 +0100 [thread overview]
Message-ID: <68bb87b70903140917m7395453fwabda4ff1a5ed3b5a@mail.gmail.com> (raw)
Hi, I'm doing some academical research about the development of device
emulators. So far I managed to create an emulator of a simple PCI
device (Intel i6300ESB watchdog timer) just to get an idea of the
development process in QEMU, and studied some of the other emulators
in qemu/hw. I was also looking for some basic metrics (e.g. sloc,
emulator sloc/driver sloc, function points) and models (e.g. cocomo
II) to do some effort estimation (e.g. how many person-month to
emulate a particular device model?).
At this point, a little help from you would really benefit my studies
and research. So... the questions are very simple :)
- does someone have old or future development schedules for some of
the qemu modules to share?
- could someone (roughly) estimate the work-days needed to develop the
emulator of a very simplce device (e.g. an hardware timer), an hard
one (e.g. a VMEbus bridge with poor documentation), a mid one (e.g. an
ethernet card), given an experienced programmer?
- could someone (roughly) estimate which are the prerequisites to
successfully develop a particular device emulator? (e.g. datasheet,
real hardware, driver source code, vendor help, luck, girls, ...)
- that's all but you can give hints if you want :)
I'll obviously share all of my work once is finished.
Thank you in advance,
Patrizio
next reply other threads:[~2009-03-14 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 16:17 Patrizio Boschi [this message]
2009-03-15 14:20 ` [Qemu-devel] Help on effort estimation Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68bb87b70903140917m7395453fwabda4ff1a5ed3b5a@mail.gmail.com \
--to=patrizio.boschi@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).