Software Requirements Specification

coldwaterphewΔιακομιστές

17 Νοε 2013 (πριν από 3 χρόνια και 6 μήνες)

83 εμφανίσεις


Software Requirements
Specification

for

SOAized SHIELD

Version 1.0 approved

Prepared by Shaun Netherby

Team Pic Portal

2
/5/08

Software

Requirements Specification for
SOAized SHIELD

Page
ii


Table of Contents

Table of Contents

................................
................................
................................
..........................

ii

Revision History

................................
................................
................................
............................

ii

1.

Introduction

................................
................................
................................
..............................
1

1.1

Purpose

................................
................................
................................
................................
............

1

1.2

Document Conventions

................................
................................
................................
....................

1

1.3

Intended Audience and Reading Suggestions

................................
................................
..................

1

1.4

Project
Scope

................................
................................
................................
................................
...

1

1.5

References

................................
................................
................................
................................
........

1

2.

Overall Description

................................
................................
................................
..................
1

2.1

Product Perspective

................................
................................
................................
.........................

1

2.2

Product Features

................................
................................
................................
..............................

1

2.3

User Classes and Characteristics

................................
................................
................................
.....

1

2.4

Operating Environment

................................
................................
................................
....................

2

2.5

Design and Implementation Constraints

................................
................................
..........................

2

2.6

Documentation

................................
................................
................................
................................
.

2

2.7

Assumptions and Dependencies

................................
................................
................................
......

2

3.

System Features

................................
................................
................................
........................
2

4.

External Interface Requirements

................................
................................
...........................
3

4.1

User Interfaces

................................
................................
................................
................................
.

3

4.2

Hardware Interface
s

................................
................................
................................
.........................

3

4.3

Software Interfaces

................................
................................
................................
..........................

3

4.4

Communications Interfaces

................................
................................
................................
.............

3

5.

Other Nonfunctional Requirements

................................
................................
.......................
3

5.1

Performance Requirements

................................
................................
................................
..............

3

5.2

Reliability
Requirements

................................
................................
................................
.................

3

5.3

Security Requirements

................................
................................
................................
.....................

3

5.4

Supportability

Requirements

................................
................................
................................
...........

3

6.

Other Requirements

................................
................................
................................
................
3

Appendix

A: Glossary
................................
................................
................................
....................
3

Appendix B: Analysis Models

................................
................................
................................
.......
3

Appendix C: Issues List

................................
................................
................................
.................
3



Revision History

Name

Date

Reason For Changes

Version











Software

Requirements Specification for
SOAized SHIELD

Page
1


1.

Introduction

1.1

Purpose


The purpose of this document is to capture the attributes of this system such as design con
straints,
reliability, performance, supportability, and general security requirements.

1.2

Document Conventions

1.3

Intended Audience and Reading Suggestions


This
document is intended for the product sponsor and for the professor overseeing the project.

1.4

Project
Scope


Please
refer to the vision document for the project scope.

1.5

References


Vision document


Title: Vision, Author: Karan Shah, Version 1.0, 2
-
5
-
08

Glossary document


Title: Glossary, Author: Shaun Netherby, Version 1.0, 2
-
6
-
08

2.

Overall Description

2.1

Prod
uct Perspective


This product is a restructuring of an existing LM tool. The restructuring includes converting
SHIELD into a thin client and a server side application that communicate to each other. The server
side contains the large SAR image files and
processes them, while the client side provides a GUI for
the user.

2.2

Product Features


The product features are implemented by SHIELD already, and will remain in SOA
-
SHIELD.

2.3

User Classes and Characteristics


Due
to the nature of this product, user classes ar
e unknown to us. Similarly, because we are not
redesigning the GUI, the classes are not relevant to us.

Software

Requirements Specification for
SOAized SHIELD

Page
2


2.4

Operating Environment


The server side application will reside on a Sun T2000 Unix box. The thin client will be able to
operate on any machine running

JVM 1.6.

2.5

Design and Implementation Constraints


The implementation will be restricted to using Java 1.6, Java Web Services 2.0, and either the
Tomcat or GlassFish server.

2.6

Documentation


Two sets of documentation will be provided to the client:




Instructio
ns for installing the product on the server and client side



A tutorial for SOAizing homegrown tools using Java Web Services, along with a listing of
difficulties we faced during the process.

2.7

Assumptions and Dependencies


Please refer to the Vision document
.

3.

System Features


The system features are already implemented by SHIELD and will not be lost during the
transformation to SOA
-
SHIELD.

4.

External Interface Requirements

4.1

User Interfaces

The thin client will be using the already existing SHIELD user interface.

The server side
application user will not have a special interface; the user will navigate and alter files by their own
software.

4.2

Hardware Interfaces

4.3

Software Interfaces


The software interfaces will include either the Apache Tomcat or GlassFish server.

The SAR image
files will also constant an interface.

Software

Requirements Specification for
SOAized SHIELD

Page
3


4.4

Communications Interfaces

The thin client and server side application will communicate via the Internet and Java Web Services.

Specifically, the method of transportation will be XML, and the protocols
will be SOAP and HTTP.

5.

Other Nonfunctional Requirements

5.1

Performance Requirements



SOA
-
SHIELD’s performance will primarily be dependent on network speed and server
performance. However, the client is not concerned with performance.

5.2

Reliability

Requirement
s

The server and thin client will be available to users 24/7, with the exception of maintenance periods.

5.3

Security Requirements

Security issues will be assumed by LM.

5.4

Supportability

Requirements

The system will be built so that functionality can be easily a
dded, such as the functionality that has
been classified from our team. Due to the requirements of Web Service communication, naming
conventions will be congruent to those of the current application.

6.

Other Requirements

There are no other requirements.

App
endix A: Glossary

Please refer to the Glossary document.

Appendix B: Analysis Models

Currently we have no analysis models.

Appendix C: Issues List

Currently there is debate whether to use the Apache Tomcat server or GlassFish application server
to implemen
t Web Services.