SRS - Decision Systems Lab

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

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

94 εμφανίσεις


-

2
-




Intelligent Multi Agents System

Software Requirements Specification

For CSCI 321 Proj
ect





Version 1.0





Revision History

Date

Version

Description

Author

08/05/02

1.0

First implementation of SRS. Requirements may be
significantly changed as requested by the client.

Joe Cheung, Joe
Tsang, Lilian,
Fredrik, Angus
and Sammy

2/6/02

1.1

R
eformat the layout of SRS and add information. Review
version of SRS for SMP

Lilian, Joe
Cheung

2/9/02

1.2

Attach Appendixes

Lilian


2/10/02

1.3

Review and rewrite some parts of details.

Joe Cheung and
Lilian




-

3
-

Table of Content

Table of Content

-

3
-

Introduction

-

5
-

1.1

Purpose

-

5
-

1.2

Scope

-

5
-

1.3

Definition, Acronyms and Abbreviations

-

6
-

1.4

Reference

-

7
-

1.5 Overview

-

8
-

1.

Overall Description

-

9
-

2.1 Product prospective

-

9
-

2.2 Product function

-

9
-

2.3 User characteristics

-

9
-

2.4 Constraints

-

9
-

2.5 Assumptions

-

10
-

2.

Specific requirements

-

11
-

2.1

Functionality

-

11
-

2.2

Usability

-

11
-

3.2.1 Training time

-

11
-

3.2.2 Task time

-

11
-

3.2.3 Common usability standards

-

12
-

2.3

Reliability

-

12
-

2.3
.1

Availability

-

12
-

2.3.2

Mean Time Between Failures

-

12
-

3.3.3

Mean Time To Repair

-

12
-

3.3.4

Accuracy

-

12
-

2.4

Performance

-

12
-

2.4.1

Response time

-

12
-

2.4.2

Throughput

-

12
-

2.4.3

Capacity

-

12
-

2.5

Supportability

-

13
-

2.5.1

Coding standards

-

13
-

2.5.2

Class libraries

-

13
-

2.5.3

Maintenance access

-

13
-

2.6

Design Constraints

-

14
-

3.6.1 Software Languages

-

14

-

3.6.2 Software Proc
ess Requirements

-

14
-

3.6.3 Prescribed Use of Developmental Tools

-

14
-

3.6.4 Architectural

-

14
-

2.7

Help System Requirements

-

14
-

2.8

Software Components

-

15
-

2.8.1

Purchased Components

-

15
-

2.8.2

Free Components

-

15
-

2.9

Interface

-

15
-

3.9.1 User Interfac
e

-

15
-

3.9.2 Hardware Interface

-

15
-

3.9.3 Software Interface

-

16
-

3.9.4 Communication Interfaces

-

16
-

3.10 Licensing Requirements

-

16
-

3.11 Legal, Copyright, and Other Notices

-

17
-

3.12 Applicable Standards

-

17
-


-

4
-

3.

Supporting Information

-

17
-

4.1 Appendic
es

-

17
-

Appendix I: Use Case Modelling

-

18
-

Appendix II:
Use case model survey

-

19
-

Appendix III:

Web Site Flowchart

-

20
-


-

5
-

Introduction


The Infrastructure for Agent
-
based B2B Marketplace System is to provide a
container for autonomy Agent approach to assist Business user for B2B
comm
erce. In the present B2B auction place, user need to search among
available web site to find and select suitable product, autonomy agent are going
to find a best offer base on multiple auction and provider.



1.1

Purpose


The Intelligent Multi Agents System
(thereafter as “IMAS”) is a web based B2B
marketplace.

The use of autonomy agent is to provide an intelligent way for B2B commerce,
autonomy agent replace the present of human as an agent to search and select
among each offer.

Moreover, IMAS should be desi
gn to specific business model, agent need to
specific to those business properties.



1.2

Scope


The targets of Intelligent Multi Agents System are on enterprise user look for
large quantity and specific type of product. All kind of businesses users can
defin
e their agent in our marketplace. Members can use this any place anywhere
with an Internet connection.




-

6
-

1.3

Definition, Acronyms and Abbreviations


Intelligent Multi Agents System: The entire system that this document is defining

SRS: Software Requirement Sp
ecification

B2B: Business
-
to
-
Business

TCP/IP: Transmission Control Protocol/ Internet Protocol
-

Internet
communication protocol

TCP socket: communicate with another computer using IP address and port
number to connect a remote computer

HTTP


web document

transfer protocol

XML


extensible markup language, format the communicate document between
agents

SQL


Database transaction language

LAN


Local area network

HTML: hypertext markup Language, user interface formatting

Servlet


a Java CGI

JSP


Java Serv
er Page, dynamic web pages provide interactive web interface

TOMCAT Servlet/JSP container


a container to server servlet and JSP request
from remote client

JDBC


JAVA database connection, provide connection between Java and
database

JAVA


multi
-
platform

programming language

JAVA multi
-
threading


provide multi
-
agent system



-

7
-

1.4

Reference




Stuart, J. R. & Peter, N.
Artificial Intelligence: A Modern Approach,
International Editions, Prentice
-
Hall, 1995



Turban, E. et al.
Electronic Commerce: A Managerial Persp
ective 2002
,
International Edition, Prentice
-
Hall, 2002



Kruchten, P.
The Rational Unified Process an Introduction
, 2nd Edition, MA,
Addison Wesley, 2001



Stephens & Pooley,
Using UML
, Updated edition, MA, Addison
-
Wesley
Longman, 2000.



http://
www.rational.com

-

Software Requirement Specification Template.



http://www.ecs.soton.ac.uk/~nrj/download
-
files/negotiation.pdf



http://www.cs.nccu.edu.tw/~jong/misce/online.html



http://haas.berkeley.edu/~citm/nego/nego
-
res.html



htt
p://pattie.www.media.mit.edu/people/pattie/ECOM/



http://www.ecs.soton.ac.uk/~nrj/neg
-
arg.html



http://agents.umbc.edu



http://www.ecst.csuchico.edu/~amk/foo/csci322/agents.html



http://www.iis.ee.ic.ac.uk/~frank/surp00/article1/ss498/



http://clio.mit.csu.edu.au/~mkavakli/seminars/css
s2000/sld034.htm



http://osiris.sunderland.ac.uk/cbowww/AI/TEXTS/AGENTS4/intro.htm



http://cis.paisle
y.ac.uk/research/journal/V7/N3/v7n3e.doc



http://www.cs.wisc.edu/~dyer/cs540/notes/agents.html



http://www.emory.edu/BUSINESS/et/i
agent/



http://www.cs.nps.navy.mil/people/faculty/rowe/andradethesis.htm



http://www.engr.uvic.ca/~seng450/negotiation/postnegotiation.htm



Schildt.H.
The Complete Reference Ja
va 2
, Fourth Edition. McGraw
-
Hill, 2001.




-

8
-

1.5 Overview


This specification included overall description of the Intelligent Multi Agents
System. The specific requirement of the Intelligent Multi Agents System has four
major sections:

Section 1

Introductio
n
-

provides an overview to the entire SRS document includes
purpose, scope, definitions, acronyms and abbreviations references and
overview.


Section 2

Overall description
-

describes the product that will be produced includes
production prospective, prod
uct function user characteristics, constraints
and assumptions


Section 3

Specific requirements
-

addresses the functionality, usability, reliability,
performance issue, supportability, design constrain, online user doc and
help system requirements, purcha
se components, interfaces, licensing
requirement, legal, copyright and other notices and applications standards.


Section 4

Supporting information


Appendix includes use case view, use case
report and sample of web page flowchart.



-

9
-

1.

Overall Description


2.1 Product prospective


The system is developed an infrastructure for agent
-
based B2B marketplace. It
aims to provide a medium for agents to make a better and quicker decision
through. It provides a greater efficiency for user.



2.2 Product function


Th
e IMAS supports the functions that agent can check status from database. The
agent will search suitable agent based on the user preference, provide three kind
of auctions, system will auto bid for product and support third party agent.



2.3 User character
istics


The users can be separated into three groups.



General users:

Intend to search their business partner and selling/buying large quantity of
raw material from them. User can come from wide and unexpected source.
It is assumed that users should have
a basic knowledge of their field in
order to perform negotiation.




Third party agent:

Design their own strategy agent to bid products or use bidding strategy
provided by our website.




Administrator and technical personnel:

Reply user enquiry, maintain me
mbership, update news and product
category.

Provide schedular backup and security check up.



2.4 Constraints


Solution constraints:

System must use Java 1.4 to implement.

Web server hosted on Tomcat 4.0

Database using mySQL 1.4


Hardware constraints:

Ba
sed on the limitation of computational power, we assume that the system
should be able to serve up to 100 users simultaneously.


-

10
-

2.5 Assumptions


This section provides a description of the technical feasibility and project related
assumptions necessary f
or the system described in the SRS.



The user has computer and internet connection



The user will be an occasional user without any training in this system.



The user can view the availability product from our website



The user can follow simple instructions t
o create buyer and seller agent



The user provides correct information to register



The user will need a password to login our website



The user choose appropriate auctions



The user set preference on their choice of price and time



The user cannot cancel the a
uction after it is started.



The user can view their posted information of selling product



The user can view their requested information of buying product



The user can view their bidding results on the website



The user may choose to be a third party agent



T
he IMAS provide third party agent communication interface language



If user is third party agent they can build their own strategy to bid products
in our website



Tomcat will provide interface for user interaction and input necessary data
for IMAS function



D
atabase will provide a medium to store and retrieve data for user, IMAS
and remote agent



IMAS will provide all decision making and connection for remote agents


-

11
-

2.

Specific requirements


This section contains all the software requirements to a level of detai
l sufficient to
enable designers to design a system and testers to test that the system that
satisfies those requirements.



2.1

Functionality


Data collection:

System stores all the information related to transactions such as user preference,
auction history

and user personal details.


Gathering suitable buyers and sellers:

The user specifies the range of the issues which are to be handled in the auction,
price, timing, amount of units etc. Then the agent would search suitable agent
based on the user prefer
ence.


Multiple Auctions:

Provide three types of auctions for user to choose. Those include English auction,
Japanese auction and Seal
-
bid (Vickery) auction.


Auto bid price:

The system will keep to bid and search suitable agent for products after user
cre
ated agent and set the price.


Remote agent:

Accept third party agents which are from other website to bid products in our
website.



2.2

Usability


3.2.1 Training time




The normal users are expected to spend 30 minutes approximately to
register and view all
information from our website.



The remote agents are expected to spend 1 hour approximately to
build their own agent from our website.


3.2.2 Task time




The users need to use 10 minutes approximately to create their seller
or buyer agent.



The users need to
use 1
-
3 minutes to view their bidding results.



-

12
-

3.2.3 Common usability standards




Sun’s standard



www.w3.org



TCP/IP standard



2.3

Reliability


2.3.1

Availability


The system is available online 24 hours a day and 7 days a week wi
th the
expectance of maintenance or system failures.


2.3.2

Mean Time Between Failures


The MTBF is around 4 weeks.


3.3.3

Mean Time To Repair


The system is allowed maximum two hours to repair after it has failed.


3.3.4

Accuracy


The time accuracy is

1/100 se
cond.



2.4

Performance


2.4.1

Response time




The average response time for web page request is less than 1 second.



The maximum response time for web page request is 3 second.


2.4.2

Throughput


The Tomcat handle about 100 web pages request per second.


2.4.3

Capacity


The sys
tem has the ability to provide service for at least 100 users.




-

13
-

2.5

Supportability


2.5.1

Coding standards


We expected to use the following standard codes to build our system:

JSP, Java, Servlet, html, JavaScript and XML


2.5.2

Class libraries


The following class lib
raries will be use to build for our system:



java.io.*



java.util.*



javax.servlet.*



javax.servlet.http.*



java.sql.*



java.text.*



java.lang.Object.*



java.sql.Date.*



java.net.*



javax.mail.*



javax.mail.internet.*


2.5.3

Maintenance access


We expected to employ a tech
nical person to be a Database Administrator to
maintain our system and keep checking the Database performance.



-

14
-

2.6

Design Constraints


The system has these following constraints when designed the web page:



Software languages



Software process requirements



Prescribed use of developmental tools



Architectural


3.6.1 Software Languages


The system must be written by JAVA, HTML, Servlet, JSP, Java script and SQL.


3.6.2 Software Process Requirements


The development process is firstly to design the agent neg
otiation logically class
function. Web page is used these agent negotiation logically class function and a
data from a database to provide the agent
-
to
-
agent negotiation web service.


3.6.3 Prescribed Use of Developmental Tools


Java SDK 1.4 is mainly us
ed to write the system. It provides the class library for
JAVA, Servlet and JSP. Any text editor can be used to write HTML web page and
SQL coding for the system.


3.6.4 Architectural


The system architectural is based on the Windows 2000 Professional and

Tomcat Apache Web Server to perform the web page. Tomcat performs the JSP
and Servlet function. JSP and Servlet function connect to mySQL database for
the system and user data.



2.7

Help System Requirements


Each function buttons are provided a help function

to explain the usage and
detail information of a function




-

15
-

2.8

Software Components


2.8.1

Purchased Components


Microsoft Windows 2000 Professional for windows licenses must be purchased
for the based on system. The system provides a web service on Internet (all

user
access to the Internet sites by anonymous users).


2.8.2

Free Components


Usage restrictions:

Tomcat Apache 4.0

Tomcat Apache is freely distributed software by Apache Foundation. It does not
restrict the use of itself for host web page and JSP.


MySQL:

It

supports SQL and Java. It is also supported by JDBC interface and stores an
unlimited data that depend on the size of hard drive.



2.9

Interface


Software provides an online marketplace interface for various B2B users. The
user interface must be easy to use

and navigate, it provide a way for user to
enable agent for negotiation.


3.9.1 User Interface


End Users Interface is web based html web page. All users need a compatible
browser (Internet Explorer 4.1+ or Netscape 6.0+) and Internet connection
(TCP/IP

and HTTP protocol) in their computers. The software virtually works on
any Operation System.


3.9.2 Hardware Interface


User parameters are submitted by HTTP protocol through browser to web server,
web server translate these parameters into agent recogni
ze language. Later on,
agents will start the negotiation process throw selected negotiation technology.
The result will store in database. User receives the result/process status by
request query database through web server. The result will present on html

format to user.



-

16
-

3.9.3 Software Interface


Servlet and JSP


dynamic web page generator and workplace of negotiation
algorithm.

mySQL Database


all data storage e.g. user login, membership, temporary
process data, result.

Browser


software interface

present in html format.


3.9.4 Communication Interfaces


56K dial up network or LAN


use for Internet access

HTTP


web page download protocol to user

HTML


the markup language of interface

XML


extensible markup language

TCP/IP


Internet communicat
ion protocol

TCP socket


connection between remote computers

JAVA


Agent communicate using java objects

SQL


SQL statement


3.10 Licensing Requirements


Opening System:

Our system will base on the opening System Windows 2000 Professional. We
will need

to have a license for the Windows 2000 Professional.



Database software:

MySQL will be our database server. It does not have to purchase license to using
it.


Web Server:

Tomcat Apache will be out web server. It does not have to purchase license to
usin
g it.



-

17
-

3.11 Legal, Copyright, and Other Notices


Microsoft Window 2000:

Our system will use Microsoft Window 2000 as an operating system.


Sun Microsystems:

Our system will use Sun Microsystems Product: JSP, Servlet, JAVA, JDBC and
Java threading.


Jakart
a:

We will also use the Jakarta product: Tomcat.


Other:

For the web programming, we will use HTML standard. About the data transfer,
we will use XML standard.



3.12 Applicable Standards



HTML 4.01

XML 1.0

JDK 1.4

JSP 1.1

Servlet 2.2

Tomcat 4.0.10

W
indows 2000 Professional

mySQL



3.

Supporting Information


4.1 Appendices




Use
-
case modelling



Use
-
case model survey



Sample of web page flowchart





-

18
-

login
Register
check status
bid product
save result
Agent
start bid
return result
IMAS
User
choose negotiation technique
provide inf ormation
set constraints
view result
choose seller
/
buyer
Client
check available product
check match agent
check result
Remote agent
bid product
Appendix I:
Use Case Modelling



-

19
-

Appendix II:
Use case model survey


Software Interface

Interface Descriptio
n


Login

Register login to our web page

Create buyer/seller
agent

Client who want to buy/sell their product then they need to
post their details to create buyer/seller agent


Choose negotiations
technique

Client can choose three kinds of auction techniq
ue.

English, Japanese and Seal
-
bid (Vickery) auction

Provide information

Client provide the information of their products, such as
category, unit name, quantity etc.

Set constraints

Client set their preferences, such as price, start bid time,
end bid tim
e, bid frequent etc.

View result


Client can view their bidding result from web page

Check status

Client can check the bidding status.

Bid product

An action that agent or remote agent bid the products

Save result

Agent will save the final bidding resul
t


Start bidding


IMAS will involved to bid after the agent created

Return result

IMAS will return to result to agent

Check result


The remote agent can keep checking their bidding result

Check available
product

The remote agent can check what product
is available to
sell or buy

Check match agent

The IMAS will check what agent is match to remote agent
preference.



-

20
-

Home
[index.jsp]
Member home
[member.jsp]
Company
Background
[company.jsp]
Product Available
[category.jsp]
Contact Us
[feedback.jsp]
Change Member
Info
[change_member.j
sp]
Check Buying Info
[buying_informatio
n.jsp]
Check Selling Info
[selling_informatio
n.jsp]
Create New Buyer
Agent
[auction_type.jsp]
Create New Seller
Agent
[auction_type_s.js
p]
Logout
[logout.jsp]
Forgot Password
[message.jsp]
Wrong
password
Join Member
[join_member.jsp]
OK
[message.jsp]
Miss/incorrect information
OK
[message.jsp]
Miss/incorrect information
Seller Auction
Status/Result
[selling_history.ht
ml]
Buyer Auction
Status/Result
[buying_history.ht
ml]
New window
New window
English Seller
[english_auction_s
.jsp]
Japanese Seller
[japanese_auction
_s.jsp]
Seal Seller
[seal_auction_s.js
p]
English Buyer
[english_auction.js
p]
Japanese Buyer
[japanese_auction.
jsp]
Seal Buyer
[seal_auction.jsp]
OK
[message.jsp]
Miss/incorrect information
OK
[message.jsp]
Miss/incorrect information
Web Flow Structure
[20 Oct 2002]
Appendix III:

Web Site Flowchart