JAAA Jxta Aplication Adapter and Architecture


from


Sven Hohlfeld



Software requirements specification



JAAA reactor



Version 0.1


Version

Author

QS

Date

Status

Comments

0.1

Sven Hohlfeld (sourceforge alias: wunderkind)


13.11.02

Init

Egg or hen?


Sven Hohlfeld

EMail wunderkind@users.sourceforge.net


Referring documents

JAAA Architecture SRS

JAAA reactor SRS

  1. Purpose

What is the purpose of the future software system? What aims can be mentioned?

  1. Product perspective

In which kind of domain shuold the software system be installed. Describe the domain in detail to explain the kernel of the software system and its environment. For whom? List the user roles.


  1. Product overview

Integrate the use case diagram. There should be at least 6-10 use cases in your domain.


Figure. F-1: Use case diagram project name


  1. Product functions

/PF10/ Use case: use case name: From ... until ...

Actor:

Description: One or two short sentences that decribe the use case.

/PF20/ Use case:

Actor:

Description:

/PF30/ Use case:

Actor:

Description:

/PF40/ use case:

Actor:

Description:

/PF50/ Use case:

Actor:

Description:

/PF60/ Use case:

Actor:

Description:

/PF70/ Use case:

Actor:

Description:

/PF80/ Use case:

Actor:

Description:

/PF90/ Use case:

Actor:

Description:

/PF100/ Use case:

Actor:

Description:


  1. Product data:


/PD10/ data that should be permanently be stored (max. number)

/PD20/

/PD30/

/PD40/

  1. Constraints, assumptions and dependencies

/C1/ The constraints that are given in the domain should be mentioned here.

/C2/


/A1/ The assumptions you make should be stated here.

/A2/


/D1/ The dependencies to other software systems should be stated here.

/D2/

  1. Product performance


/PP10/ Any performance characteristices that are necessary to run the system should be stated here.


  1. Quality requirements

For each row decide which quality is necessary. Make an X in the cell to indicate your decision.


Product quality

very well

well

normal

not relevant

Functionality





Reliability





Usability





Efficency





Changeability





Portability






  1. Additional

Any additional comments should be listed here.


/AD1/