Transcript Design/requirements [273.5 KiB]

1
CVS Reporting
Design and Requirements
2016-05-24
2
Web design
2016-05-24
3
Eclipse design
2016-05-24
4
Use case diagram
2016-05-24
5
Web Requirements Specification
Id
Priority
Description
r1
1
Definition: The user interface should be in the form of a
webpage.
Motivation: The application then becomes available to a majority
of internet users.
r2
1
Definition: The system shall have a good, user friendly interface.
Motivation: The user should not have to be a programmer to
retrieve reports.
r3
1
Definition: The user shall be able to create reports templates
easily, defining fonts and text styles as well as colors of text and
headline and the title of the report easily.
2016-05-24
6
Web Requirements Specification
Id
Priority
Description
r4
1
Definition: The user shall be able to construct SQL queries
without being familiar with SQL-language by using graphical
components such as drop-down boxes, checkboxes and
buttons.
Motivation: the same as requirement r2.
r5
1
Definition: The user shall be able to view reports of the CVS
database by clicking on a link on the front page and selecting
the format ( PDF or HTML) in which to display the report.
Motivation: Easy to use interface and easy to reuse old
templates without having to search for them.
2016-05-24
7
Web Requirements Specification
Id
Priority
Description
r6
2
Definition: The user should be able to construct SQL queries by
typing them in a text field.
Motivation: Allow users to fully control the creation of the query.
r7
2
Definition: The user should be able to edit reports templates he
or she has created.
Motivation: If a layout looks bad the user may wish to edit the
template instead of creating a new one.
r8
1
Definition: The user should be able to delete previous templates
that are no longer in use or for other reasons unwanted.
Motivation: Without this option the system may be cluttered by
old, never used templates resulting in that the user friendly
interface may suffer.
2016-05-24
8
Eclipse Requirements Specification
Id
Priority
Description
1
The user interface should conform to Eclipse guidelines for lookand-feel
1
Ability to edit report templates (define fonts, colours… of certain
elements of report)
r3
1
Ability to create SQL queries by typing them in a text box.
r4
2
Ability to construct SQL queries with a help of an Query Builder
r5
2
Management of report templates (add, move, delete template) in
a natural way
r1
r2
2016-05-24