Project #39186 - Requirements Document

Recently I bought a low-end digital camera (< $75) and there was software bundled with the product. The software allows the user to organize their digital photos on their PC. When I installed the software on my PC I realized that the software was awful and did not work as intended. So, I had the brilliant idea that I should have this software developed so that I can bundle my software with these low-end digital cameras. *** Let's assume that I have the connections to get this done. Also, using built-in software on PC/MAC is not an option -- the software must be custom developed.



The
Requirements
Document
should
address
the
system
requirements
and
should
not
include
design
issues.
At
a
minimum
your
requirements
document
must
contain:
• Document
Title
• Date
• Introduction
• Glossary
• User
Requirements
Definition
o Functional
Requirements
o Fully-­â€elaborated
Use
Cases
and
Scenarios
o Non-­â€functional
Requirements
• Requirements
prototyping
o Screen
Layout/Screenshots
• Risk
Analysis
Note:
Use-­â€cases
are
a
great
way
to
address
requirements.
The
use-­â€case
diagram
(stick-­â€
men
and
bubbles)
is
only
the
starting
point
for
your
UML
diagrams.
Fully
elaborated
use-­â€cases
are
a
very
powerful
way
to
analyze
requirements.
For
example,
suppose
we
have
a
use-­â€case
called
"Add
photo
to
album".
What
is
the
purpose
of
this
use-­â€
case?
What
are
the
pre-­â€conditions?
Must
the
album
already
be
selected
or
is
this
part
of
the
use-­â€case?
What
happens
during
the
use-­â€case?
What
are
the
post-­â€
conditions?
Is
their
exception
flow
in
addition
to
normal
flow?
Requirement
prototyping
can
help
refine
and
further
elaborate
your
requirements.
Creating
screenshots
of
the
use
cases
or
requirements
can
help
user
visualize
the
system
and
helps
identify
underlying
requirements.
You
can
include
screenshots
within
the
body
of
the
use
case
or
you
can
place
all
screenshots
in
an
appendix
and
refer
to
them
from
the
use-­â€cases.
You
will
normally
have
at
least
one
use
case
for
each
functional
requirement
-­â€-­â€
this
is
just
a
general
notion
-­â€-­â€
but
it's
a
good
place
to
start.
There
are
many
Requirements
Document
Templates
available
online.
If
you
already
have
a
template
that
you
have
used
in
the
past,
please
feel
free
to
use
it
in
this
course
as
long
as
it
covers
the
areas
listed
above.

 

The request for a new piece of software has been made on the top paragraph. The requirements for the document are listed below it.

Subject Computer
Due By (Pacific Time) 09/30/2014 12:00 am
Report DMCA
TutorRating
pallavi

Chat Now!

out of 1971 reviews
More..
amosmm

Chat Now!

out of 766 reviews
More..
PhyzKyd

Chat Now!

out of 1164 reviews
More..
rajdeep77

Chat Now!

out of 721 reviews
More..
sctys

Chat Now!

out of 1600 reviews
More..
sharadgreen

Chat Now!

out of 770 reviews
More..
topnotcher

Chat Now!

out of 766 reviews
More..
XXXIAO

Chat Now!

out of 680 reviews
More..
All Rights Reserved. Copyright by AceMyHW.com - Copyright Policy