Requirements Analysis Document



PAID Project




Informatik XII

WS 1998/1999

Technische Universität München

January 27, 1999



Preface:

This document addresses the requirements of the PAID system. The intended audience for this document are the designers and the clients of the project.

Target Audience:

Clients, Developers

PAID Members:

Project Management:

Bernd Brügge, Guenter Teubner

Team Coaches:

Ralph Acker, Stefan Riss, Ingo Schneider, Oliver Schnier, Anton Tichatschek, Marko Werner

Architecture Team:

Asa MacWilliams, Michael Luber

Authentication & Security Team:

Klaas Hermanns, Thomas Hertz, Guido Kraus, Gregor Schrägle, Tobias Weishäupl, Alexander Zeilner

Database Team:

Osman Durrani, John Feist, Florian Klaschka, Johannes Schmid, Florian Schönherr, Ender Tortop

Learning Team:

Burkhard Fischer, Jürgen Knauth, Andreas Löhr, Marcus Tönnis, Martin Uhl, Bernhard Zaun

Network & Event Service Team:

Henning Burdack, Jörg Dolak, Johannes Gramsch, Fabian Loschek, Dietmar Matzke, Christian Sandor

STAR NETWORK Integration & User Interface Team:

Daniel Stodden, Igor Chernyavskiy, Inaki Sainz de Murieta, Istvan Nagy, Stefan Krause, Stefan Oprea

Testbed Team:

Bekim Bajraktari, Bert van Heukelom, Florian Michahelles, Götz Bock, Michael Winter, Sameer Hafez











Revision History:


Table of Contents

1 General Goals
  1.1 Authentication and Security
  1.2 Database
  1.3 Learning and Adaption
  1.4 Network and Event Services
  1.5 User Interface and STAR NETWORK Integration
2 Current System
3 Proposed System
  3.1 Authentication and Security
    3.1.1 Overview
    3.1.2 Functional Requirements
    3.1.3 Nonfunctional Requirements
      3.1.3.1 User Interface and Human Factors
      3.1.3.2 Documentation
      3.1.3.3 Hardware Consideration
      3.1.3.4 Performance Characteristics
      3.1.3.5 Error Handling and Extreme Conditions
      3.1.3.6 System Interfacing
      3.1.3.7 Quality Issues
      3.1.3.8 System Modifications
      3.1.3.9 Physical Environment
      3.1.3.10 Security Issues
      3.1.3.11 Resource Issues
    3.1.4 Constraints
    3.1.5 System Model
      3.1.5.1 Scenarios
      3.1.5.2 Use Case Models
      3.1.5.3 Object Models
      3.1.5.4 Dynamic Models
      3.1.5.5 User Interface - Navigational Paths and Screen Mockups
  3.2 Database
    3.2.1 Overview
    3.2.2 Functional Requirements
      3.2.2.1 Main purpose
      3.2.2.2 Installation and replication
      3.2.2.3 Intelligent caching system
      3.2.2.4 Operability as a standalone system
      3.2.2.5 Data flow
    3.2.3 Nonfunctional Requirements
      3.2.3.1 User Interface and Human Factors
      3.2.3.2 Zero administration
      3.2.3.3 Documentation
      3.2.3.4 Hardware Consideration
      3.2.3.5 Performance Characteristics
      3.2.3.6 System Interfacing and location transparency
      3.2.3.7 System Modifications
      3.2.3.8 Physical Environment and resource Issues
      3.2.3.9 Security Issues
      3.2.3.10 Data management
      3.2.3.11 Error Handling and quality issues
    3.2.4 Constraints
    3.2.5 System Model
      3.2.5.1 Scenarios
      3.2.5.2 Use Case Models
      3.2.5.3 Object Models
      3.2.5.4 Dynamic Models
      3.2.5.5 User Interface - Navigational Paths and Screen Mockups
  3.3 Learning and Adaption
    3.3.1 Overview
    3.3.2 Functional Requirements
    3.3.3 Nonfunctional Requirements
      3.3.3.1 User Interface and Human Factors
      3.3.3.2 Documentation
      3.3.3.3 Hardware Consideration
      3.3.3.4 Performance Characteristics
      3.3.3.5 Error Handling and Extreme Conditions
      3.3.3.6 System Interfacing
      3.3.3.7 Quality Issues
      3.3.3.8 System Modifications
      3.3.3.9 Physical Environment
      3.3.3.10 Security Issues
      3.3.3.11 Resource Issues
    3.3.4 Constraints
    3.3.5 System Model
      3.3.5.1 Scenarios
      3.3.5.2 Use Case Models
      3.3.5.3 Object Models
      3.3.5.4 Dynamic Models
      3.3.5.5 User Interface - Navigational Paths and Screen Mockups
  3.4 Network and Event Services
    3.4.1 Overview
    3.4.2 Functional Requirements
    3.4.3 Nonfunctional Requirements
      3.4.3.1 User Interface and Human Factors
      3.4.3.2 Documentation
      3.4.3.3 Hardware Consideration
      3.4.3.4 Performance Characteristics
      3.4.3.5 Error Handling and Extreme Conditions
      3.4.3.6 System Interfacing
      3.4.3.7 Quality Issues
      3.4.3.8 System Modifications
      3.4.3.9 Physical Environment
      3.4.3.10 Security Issues
      3.4.3.11 Resource Issues
    3.4.4 Constraints
    3.4.5 SystemModel
      3.4.5.1 Scenarios
      3.4.5.2 UseCase Models
      3.4.5.3 Object Model
    3.4.6 DynamicModels
      3.4.6.1 User Interface - Navigational Paths and Screen Mockups
  3.5 User Interface and STAR NETWORK Integration
    3.5.1 Overview
    3.5.2 Functional Requirements
    3.5.3 Nonfunctional Requirements
      3.5.3.1 User Interface and Human Factors
      3.5.3.2 Documentation
      3.5.3.3 Hardware Consideration
      3.5.3.4 Performance Characteristics
      3.5.3.5 Error Handling and Extreme Conditions
      3.5.3.6 System Interfacing
      3.5.3.7 Quality Issues
    3.5.4 System Modifications
      3.5.4.1 Physical Environment
      3.5.4.2 Security Issues
      3.5.4.3 Resource Issues
    3.5.5 Constraints
    3.5.6 System Model
      3.5.6.1 Scenarios
      3.5.6.2 Use Case Models
      3.5.6.3 Object Models
      3.5.6.4 User Interface - Navigational Pathsand Screen Mockups

This page is hosted by the Chair for Applied Software Engineering of the Technische Universität München.
Imprint (Impressum)