Docstoc

Sds For software project

Document Sample
Sds For software project Powered By Docstoc
					FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION

2009

E-fac SoftSynergy® fac

DEPARTMENT OF ELECTRICAL AND INFORMATION EIGINEERING

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7

Introduction........................................................................................... 05 CURRENT SYSTEMS ................................................................................... 05 PURPOSE .................................................................................................. 05 SCOPE ...................................................................................................... 05 OBJECTIVES .............................................................................................. 05 SYSTEMS OVERVIEW.................................................................................. 06 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ............................................ 07 REFERENCES ............................................................................................ 08

2.0 2.1 2.2 2.3

Related Diagram For The Application ................................................. 09 OVERALL ARCHITECTURE OF THE SYSTEMS ................................................ 09 NETWORK DIAGRAM OF THE SYSTEMS ...................................................... 10 PAGE FLOW DIAGRAM .......................................................................... ..…11 2.3.1 2.3.2 User Profile And Administrating Page Flow...................................11 Login And Registrating Page Flow………………………………..12

2.4

HOME PAGE UI SCREEN LAYOUT………………………………………….…..13

3.0 3.1 3.2

Maams Software Systems Main Module ……………………………..…14 USE CASE DIAGRAM FOR ALLMODULE………………………………………....15 DETAILED DESIGN FOR LOGIN MODULE………………………………………..16 3.2.1 3.2.2 User Profile ……………………………………………………………16 Ui Screen Design ………………………………………………….….17

3.2.2.1screen Layout ……………………………………………….……..17 3.1.4 Object Model/Data Flow Design …………………………….…….....18

3.1.4.1 use Case Diagram……………………………………..…….…....18 3.1.4.2 sequence Diagram For Login Module……..……………………20 3.1.4.3 Related Database Tables For Login Module...…………………21

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 2

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

4.0

DETAILED DESIGN FOR REGISTER MODULE …………………………………22 User Profile ……………………………………………………………22 Ui Screen Desigen ……………………………………………………22 Screen Layout………………………………………….…...…......22 Object Model/Data Flow Desigen ………………………………......23 Use Case Diagram……………………………………………......23 Sequence Diagram For Register Module………………………24 Related Database Tables For Register Module……………….25

4.1.1 4.1.3 4.1.3.1 4.1.4 4.1.4.1 4.1.4.2 4.1.4.3

5.0

DETAILED DESIGN FOR SEARCHING TRADE ITEMS MODULE ……………......26 5.1.1 5.1.2 5.1.3.1 5.1.4 5.1.4.1 5.1.4.2 5.1.4.3 User Profile……………………………………………...….…………26 Ui Screen Design………………………….………….………………26 Screen Layout ………………………………….…………….…..26 Object Model/Data Flow Design…………….….…………….…...27 Use Case Diagram…………………………….……………..…..27 Sequence Diagram Fo Module…………………………...…....28 Related Database Tables For Module………………………....29

6.0

DETAILED DESIGN FOR SUBMIT AN ADVERTESMENT MODULE……………31 User Profile…………………………….…………………..….……..31 Ui Screen Design…………………….………………........………...31 Screen Layout…………………….………………..…….…...…31 Object Model/Data Flow Design……..…………………………….32

6.1.1 6.1.3 6.1.3.1 6.1.4

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 3

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

6.1.4.1 6.1.4.2 6.1.4.3 6.1.4.4

Use Case Diagram.…………………………………………………32 Class Design……………………………………………………….33 Sequence Diagram For Module………………….………..………33 Related Database Tables For Module…………….……………. 34

7.0 8.0 9.0 9.1 9.2 10.0 10.1 10.2 10.3 10.4

Overall Class Design Of The Maams Systems ......................…………35 Packaging/Folder Structure And System Artifacts.. …………………38 Database Design………………………………………………………….….39 ENTITY RELATIONSHIP DIAGRAMS…………………………………………...….39 SYSTEM ARTIFACTS……………………………………………………….……..40 Core Technical Services Design …………………………………….…….41 PERSISTENCE……………………………………………………………..……...45 INTER-PROCESS COMMUNICATION ……………………………………………...46 AUTHENTICATION AND AUTHORIZATION …………………………………………47 ERROR HANDLING ……………………………………………………………......48

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 4

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

1.0

INTRODUCTION

1.1 Current system
In today’s world there are some online applications by using which the customers can online visit and see the details and information like market prices of the goods they want to buy. But they have to spend huge amount of money on paying the data provide application holders through credit cards etc. so for the users it is not free to upload their data or contacting a man with what I’m satisfied to buy.

1.2 Purpose
As Sri Lankans we are mainly focused on such dealings through the newspaper advertisements. Here the Idea behind this Multi Access Automated Marketing Solution is a customer and vender based automated marketing agent online for public as a community oriented project. This is specially targeted to fulfill the needs of Sri Lankan customers and venders free of charge. That means this solution is expected to help the Sri Lankan community for accessing their marketing partners faster and easier than ever through multi channel pathways with optimum use of existing technology.

1.3 Scope of the application
We have planned to design our application within the specific requirements through the features as mentioned above. When a free user is just logged in he will be able to browse for all related entries and then choose the preferred ones. Here, a multi-access login will be made available to the free users which will help them to have an easy access to the application.

1.4 Objectives
We as designers are not going to be a third party as in existing applications here. We are just making the link between the buyer and the seller; by making the people with solutions meet the ones those

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 5

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

have the problems in selling and buying goods. Therefore those who visit us online with the view to selling or buying are guaranteed to be impressed with the service provided and its effectiveness.

1.5 System Overview
The Multi Access Automated Marketing Solution is mainly based on the seller and buyer information and their online linkages. Seller can himself decide what to be manifested so we don’t take any responsibility about the data posted. So in our application we have the following respective features.     A user profile system. Seller advertisement uploading. Buyer-seller communication system. Web based dealing system with multiple accesses.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 6

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

1.6 Definitions, Acronyms and Abbreviations
MAAMS SRS AJAX UI GUI ODBC DBMC ID MSSQL HTTP TCP/IP XML LAN IIS Multi Access Automated Marketing Solution Software Requirement Specification Asynchronous JavaScript and XML User Interface Graphical User Interface Open Database Connectivity Database Management Class Identification Microsoft SQL Server Hyper Text Transfer Protocol Transmission Control Protocol/Internet Protocol Extensively Mark-Up Language Local Area Network Internet Information Service

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 7

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

1.7References
      Video Tutorials(Web Development applications, SQL Server, C#) MSDN help Microsoft TechNet www.codeproject.com www.wikipedia.org www.asp.net/ajax

BOOKS Microsoft C# Professional Projects –Microsoft Developer Team –NIIT ISBN-81-203-2030-1 Publisher-Prentice Hall of India Microsoft ASP.NET-Professional Projects ISBN-81-203-2020-4 Publisher-Prentice Hall of India Microsoft ASP.NET CODING STRATERGIES WITH THE MICROSOFT ASP.NET TEAM ISBN-0-07-058489-3 Tata McGraw-Hill Publishing Company LTD Software Project Management ISBN 0-07-058672-1 TATA McGraw-HILL EDITION Bob Hughes and Mike Cotter ell

ASP.net Ajax in Action Author: Alessandro Gallo Publisher: Manning Publications ISBN: 1933988142
FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA Page 8

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

2.0 RELATED DIAGRAM FOR THE APPLICATION 2.1 Overall Architecture of the systems
Database MSSQL

N-Hibernate

Application Firewall

Web server IIS, Silver Light video Streamer App Server .NET Engine / Silver light Framework Languages ASPX/C#/Ajax

ASPX Resources

Web Client

Silver Light Video Encoder

Third Party Libraries

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 9

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

2.2 Network Diagram Of The Systems

` Web Browser FireWall
Co mm .-lin k

Database Administrator

User/Client

Internet
Wireless Access Point
k m-lin Com

Mobile Client

Router

nk -li m m Co

Web server IIS7 FireWall

Database Server MSSQL

Database
Web Browser User/Client

Administrator

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 10

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

2.3 Page Flow Diagram 2.3.1User profile and administrating page flow
UserLoginPage Homepage

logout.aspx

userProfile.aspx
Search/show fields

User Homepage

searchItems.aspx

Administrating.asp x

Show.aspx
Change Password/user profile

changeProf.aspx

doProfile.aspx

View User

Hide/ show user

Submit a trade item

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 11

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

2.3.2 Login and Register process flow

Invalid login

Home Page

Login.aspx

doLogin.aspx

User.aspx

Invalid register information

register.asp x

Register_confirm.aspx

UserHomePage.aspx

doRegister.aspx

Register successfully

Thanks.aspx

doMember.aspx

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 12

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

2.4 Home page UI screen layout
Home Page:

When the user browsing our web site to fulfill their requirements this is the page he or she see first time. It include several functions those are traditional and new, and also those people can see recently uploaded advertisement with their brief description as below

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 13

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

3.0. MAAMS SOFTWARE SYSTEMS MAIN MODULE
Basically we have four basic modules as mentioned above and can be simply described as shown below 1) 2) 3) 4) Login Register Searching trade items Submitting an advertisement

Module Login Login

Sub module

Description User logs into the system

Login Page Login

Uploads the login page and fills in the User Profile drop-down list Checks the user input and redirect based on result A session is build to a user

Register Init Session Logout Session

Initialize session Check that session is still valid and pass it forward

Searching

User can enter advertisement name according to the category or user prefer Show Item Show the result according to the date. If there is no item show the error message Check user logging or not if valid user allow to go get information page. Upload advertisement with necessary required field

Submit and advertisement

Submit ad

upload

display message with the link to the advertisement

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 14

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

System main modules can be figure out as bellows. The first figure illustrates the top level view of all use cases.

3.1use case diagram for all modules
ud Use Case View Remov e/Edit/Dissable trade items in the DataBase to keep the quality, serv ice and security of the proj ect Monitor users and get crusial decisions for the safety of other users and serv ice of the proj ect

Remov e/Edit/Dissable trade Items

«i nvokes»

Change/Delete general user

«i nvokes»

Guest Register «i nvokes»

Guests can register in the site and start using full fuctionality of the site

Searching for Trade items in the site

«i nvokes»

Users can v iew information on the trade items adv ertised by others,so they can select a suitable product for them. Guests and registered users can log in to the site.

DB Admin

Loggin «trace»

Submit an Adv ertisement

«trace»

user can adv ertise about any product they hav e to inform public for selling.Adv ertises hav e to first logged in to the site. The user w ho adv ertised an item may need to edit/change some data ihe entered early.

Customer(Adv ertising)

Edit sales items details

«trace»

Request an Item «trace»

When a user needs more infomation on a selected item, they can contact more information from the adv ertise by using e-mail or leav ing a message to Registered users can change their profile informations.

Customer(Buying) Edit User Profile «trace»

See contact details of the Adv ertiser

«trace»

registed users can see granted informations of the adv ertises for selected trade items.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 15

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

3.2 detailed design for Login module
3.2.1 User Profile All registered users can login to their accounts through their own username & password.

 In order to perform submit an advertisement processes of the system the users should log to the system.

 If the user has entered an invalid login name &/or password, for that location or even for the whole system, the status field will display a message telling the user that he or she does not have access to that location, or the login name and password is not recognized in the database.

 The staff has entered a valid login name and password at their specific location. This will not enable any data manipulations (only view), but this will state that the specific staff has been accepted at that location and then the screen for that location will come up.

 The user has entered a valid login name and password and the user is an administrator this will enable all data manipulation that they will have access to, and then enable any function as they wish.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 16

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

3.2.2 UI Screen Layout

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 17

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

3.1.4.1 Use case diagram for all module

cd Use Case M odel-Loggin

DB Admin

«i ncl ude»

Loggin «i ncl ude» Customer(Adv ertising)

Validation «trace»

«i ncl ude»

Customer(Buying)

Actor Description Pre-conditions Post-Conditions

DB-Admin Administrator and the Super user of the System Login to the system using admin password and username Login to the Admin-Home Page granted. Can control the registration of users, controlling the advertisements and

privileges

validating there activations. Also capable of all the controlling and management roles of the databases.

Notes

If access fails it will re-direct to the admin login page.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 18

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

Actor Description Pre-conditions Post-Conditions privileges Notes

Customer(Advertising) A registered user under the admin user. Play a major in the site. Registered at the Registration page and grant access by the BD-Admin user. Access to the Advertising page is granted. View public results of latest exam and past exams, view individual results, edit student profile. If access fails it will stay/re-directed to the Homepage.

Actor Description Pre-conditions Post-Conditions privileges

Customer(Buying) A registered user under the admin user. Play a major in the site. Registered at the Registration page and grant access by the BD-Admin user. Accesses to advertiser’s information’s pages are granted. View public results of latest exam and past exams, view individual results, edit student profile.

Notes

If access fails it will stay/re-directed to the Homepage.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 19

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

3.1.4.2 Sequence Diagram of Login Module
sd Login SecureLoginEv enthandler:SecureLogin SecureLoginHandler:Secure Authentication:LoginAuthentication LoginAuthentication:DataAccess UI Login User db Serv er

/* Enter Username & Password */

Login_click(); /* Send data */

/* Send Query */

Retrieve

GetReload()

VerifyAuthentication(); /* Re Enter data If login failed */

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 20

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

3.1.4.3 Related Database Table
User User _ID userType Role_ID User_Name Password int String int String String <encrypted> <encrypted> Not Null Primary Key Unique identifier for the each user Identification the user type Identifier for the role of users Username of the user Password of the user

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 21

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

4.0 Detailed Design for register module
Any guest user visiting this website willing to get the use of web site has to be registered first.

4.1.1. UI Screen Layout

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 22

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

4.1.4.1 Use case Diagram of Register Module
ud Register

«include» Users

Register

«extend»

User validation through email

Detail description of Register Module use case Diagram

Use case Description Pre-conditions Post-Conditions Exception

Register When users need extensive entrance to the site they want to enter required information and register in the site, so they can login later. Interest in using the site. Validate registration through e-mail. Must supply all required information.

Notes

Registration is free.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 23

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

4.1.4.2 Sequence diagram for Register Module

sd Registering User Input Data; User Check Input Data Types With Capture String(); IF Verification No Errors.

Click SignUP(); /* Fill Relevant Forms & Submit */

Verification(); Direct T o Welcome Page.

Sign Out();

/*Verification Of One Or Morefields Failed*/

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 24

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

4.1.4.3 Related Database Table for Register Module
User User _ID
userFirstName userPassword userSecurityQuestion

int int int String

Not Null Primary Key

Unique identifier for the each user Identification for the employee Identifier for the role of employee Security question for password recovery Security answer for password recovery User’s contact email address User’s contact telephone address User’s contact mail address User’s contact mail address

userSecurityAnswer

String

userEmail userTelNo userAddressLine1 userAddressLine2

String String

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 25

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

5.0 DETAILED DESIGN FOR SEARCHING TRADE ITEMS MODULE
5.1 User Profile It will give a search-term that will search through a database of compatible Multi access websites that are added by the development team. The results of this search will be displayed as web links in a tab on the program’s main window. This is one of the main features of the software and therefore has a high priority for development. Administrator & registered or unregistered user are free to search for trade items within the web site. 5.1.2 UI Screen Layout of Search page:

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 26

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

5.1.4.1 Use Case diagram of Searching Items Module
od Use Case M odel-Searching for Trade items in the site

Guests required to Register and Loggin Validation DB Admin

«incl ude»

«i nvokes»«i nvokes»

Identify User State Loggin «i ncl ude» Customer(Adv ertising) Detailed View and More information «precedes» «extend» Adv ertiser's «extend» contact infomation

«trace»

«trace»

«include» Registered Users required to Loggdin

Customer(Buying)

Use case Description Pre-conditions Post-Conditions Exception Notes

Search for trade items All general users are given the opportunity to use different searching criteria to search for the best trade information. None When user needs contact information about the Advertisers, they need to be logged in. Back to Home Page None

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 27

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

5.1.4.2 Sequence Diagram for Searching Trade items
sd Searching DropDownListHandler(); User Process Data that User Selected Get User Inputs To Query. Db Serv er

/*UserSelectFromDropDownList*/

*/Click Search*/

/* Send Data */

Send Query

Data Retrieve

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 28

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

5.1.4.3 Related Database Tables For Module
User
transactionID

int

Not Null Primary Key

Unique identifier for the each entity of a advertise Unique identifier for the each entity of a trade item Identification for the prize for which the user is looking for User’s selection category type to search on

tradeItemID

int

itemPrize

double

tradeItemcar tradeItemLand tradeItemMobile description

TradeItemCar TradeItemLand TradeItemMobile

String

User specified search string for searching purpose

brand

String

Specify the type of the vehicle brand, user is looking for Specify the province of the vehicle used at Specify the whether the vehicle is registered or not Specify the whether the vehicle is for rent or sale

provience

String

registered

bool

rent

bool

area

double

Specify the area of the land ,user is looking for Specify the province the land is located at

provience

String

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 29

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

withHouse

bool

Specify whether the land contain a house or not Specify the whether the land is for rent or sale

rent

bool

brand

String

Specify the type of the mobile brand Specify the type of the mobile model

model

String

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 30

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

6 .0 DETAILED DESIGN FOR SUBMIT AN ADVERTISEMENT MODULE.
6.1 User Profile This function can only be handled by the registered user acting customer as an advertiser. In that window customer is expected to upload all the attributes with a photo of the trade item. 1. check if the user has logged in 2. display form 3. get form information 4. validate form information 5. store uploaded information and photo file as /<username>/filename 6. store photo information into database 7. display message with the link to the advertisement

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 31

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

6.1.4.1 Use Case Diagram of Submit an Advertisement
cd Use Case Model-Submit an Adv ertisement

«i ncl ude» Guest

Register and Loggin

«invokes» Logged User

Customer(Adv ertising)

«real i ze»

Submit an Adv ertisement

«i nvokes»

setting profile details for Adv ertised item

Customer(Buying)

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 32

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

6.1.4.3 Sequence Diagram of Submit an Advertisement
sd Submitting An Adv ertisement. Check w hether User Loggged in or not. Validate Registered User Input Data For The Add. Execute Sequence Registering Or Login Modules. Db Serv er

User

*/ Click Submit An Advertisement */

Verify Whether User Logged In. /*If Yes Direct To Submit Add */

Verification(); /* Send Query*/

/* If Not User Redirect For Home Page */

Back To Submit Add.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 33

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

6.1.4.4 Related Database table
User
brand

String

Specify the type of the vehicle brand, user is looking for Specify the province of the vehicle used at Specify the whether the vehicle is registered or not Specify the whether the vehicle is for rent or sale User specified search string for searching purpose

provience

String

registered

bool

rent

bool

description

String

area

double

Specify the area of the land ,user is looking for Specify the province the land is located at Specify whether the land contain a house or not Specify the whether the land is for rent or sale User specified search string for searching purpose

provience

String

withHouse

bool

rent

bool

description

String

brand

String

Specify the type of the mobile brand Specify the type of the mobile model

model

String

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 34

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

7.0 OVERALL CLASS DIAGRAM OF THE MAAMS SYSTEMS
cd Users Users + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + userID: i nt userUserName: string userPassword: stri ng userSecuri tyQuesti on: stri ng userSecuri tyAnswer: stri ng userFi rstNam e: stri ng userEmai l : string userT el No: stri ng userCountry: string userStateorProvi nce: stri ng userAddressLi ne1: stri ng userAddressLi ne2: stri ng userT own: string GetuserID() : i nt SetuserID() : i nt GetUserName() : string SetUserNam e() : stri ng GetPassword() : stri ng SetPassword() : string GetSecuri tyQuesti on() : stri ng SetSecuri tyQuesti on() : stri ng GetSecuri tyAnswer() : stri ng SetSecuri tyAnswer() : string GetFi rstNam e() : stri ng SetFirstName() : string GetEmai l () : string SetEm ai l () : stri ng GetT el no() : i nt SetT el no() : i nt GetCountry() : string SetCountry() : stri ng GetStateorProvi nce() : stri ng SetStateorProvi nce() : stri ng GetAddressLi ne1() : stri ng SetAddressLi ne1() : string GetAddressLi ne2() : stri ng SetAddressLi ne2() : string GetT own() : string SetT own() : stri ng

«i nterface» usersDAO

Com pose usersDAOImpl + + + + AddusersDAOIm pl : i nt Edi tusersDAOIm pl : i nt Del eteusersDAOIm pl : i nt Vi ewDAOImpl : i nt

Com pose

«i nterface» AdminDAO

«i nterface» RegisteredUserDAO

Im pl em ent

Im pl em ent

Admin

RegisteredUser

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 35

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

cd TradeItem # # # # # # # # transactionNumber: int itemPrize: double itemPicture: string itemDescription: char getTransactionNumber() : int getItemPrize() : double getItemDescription() : void getItemPicture() : void setTransactionNumber() : int «extend» setItemPrize() : double setItemPicture() : void setItemDescription() : void # # # # # #

«extend» Car # # # # # # # # carID: int carBrand: char carColor: char carUsagePeriodYears: char carWheels Operated: int getCarId() : int getCarBrand() : void getCarColor() : void getCarUsagePeriod() : double setCarID() : int setCarBrand() : void setCarColor() : void setCarUsagePeriod() : double # # # # # # # # #

MobilePhones mobileId: int mobileModel: string mobleBrand: string getMobileId() : int getMobileModel() : void getMobileUsagePeriodYears() : double setMobileId() : void setMobileModel() : void setMobileUsagePeriodYears() : void

«extend» Land landId: int landArea: double landProvince: string LandWithhouseOrWithout: string landRentOrSale: string getLandId() : int getLandProvince() : void getLandArea() : double getLandWithhouseOrWithout() : void getLandRentOrSale() : void setLandId() : int setLandProvince() : void setLandWithhouseOrWithout() : void setLandRentOrSale() : void

cd TransactionRecords TransactionRecords + + + + # # # # transacti onId: int itemAdvertisedDate: Date itemIpAddress: string itemLastUpdatedDate: Date getT ransactionId() : int getItemAdvertisedDate() : Date getItemIpAddress() : string getItemLastUpdatedDate() : Date

Overall Class Diagram

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 36

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

TradeItem Abstract Class

TradeItemCar
Class TradeItem

TradeItemLand
Class TradeItem

TradeItemMobile
Class TradeItem

TradeItemCarDAOImpl
Class

TradeItemCarDAO
Interface TradeItemCar

Members brand Brand carId CarId provience Provience rent Rent withHouse WithHouse

Members area Area landID LandID provience Provience rent Rent withHouse WithHouse

Members brand Brand mobileId MobileId model Model
TradeItemLand

TradeItemMobile

Members addTradeItem deleteTradeItem editTradeItem viewTradeItem

TradeItemCarD…

Members
addTradeItem deleteTradeItem editTradeItem viewTradeItem

TradeItemCarDAO

TradeItemLandDAO Transaction
Class Interface

TradeItemLandDAOImpl
Class

UsersDAOImpl
Class

Members lastUpdatedDate UsersDAO
Interface

TradeI…

Members
addTradeItem deleteTradeItem editTradeItem viewTradeItem

Tr Members addTradeItem deleteTradeItem editTradeItem viewTradeItem

Members addTradeItem addUser deleteTradeItem deleteUser editTradeItem editUser viewTradeItem viewUser UsersDAO

LastUpdatedDate tradeItem UsersDAO TradeItem transactionDate TransactionDate transactionID TransactionID transactionIpAddress TransactionIpAddress users Users
Transaction

Members
addUser deleteUser editUser viewUser

TradeItemMobileDAO TradeItemMobileDAO
Interface

Members
addTradeItem deleteTradeItem editTradeItem viewTradeItem

Users

Users
Class

TransactionDAO
Interface

TradeItemMobileDAO

Members userAddressLine1 UserAddressLine1 userAddressLine2 UserAddressLine2 userCountry UserCountry userEmail UserEmail userFirstName UserFirstName userID UserID userPassword UserPassword userSecurityAnswer UserSecurityAnswer userSecurityQuestion UserSecurityQuestion userStateorProvince UserStateorProvince userTelNo UserTelNo userTown UserTown userUserName UserUserName

Members
addTransaction deleteTransaction editTransaction viewTransaction

TradeItemMobileDAOImpl
Class

TransactionDAO

Members addTradeItem deleteTradeItem editTradeItem viewTradeItem

TransactionDAOImpl
Class

Members addTransaction deleteTransaction editTransaction viewTransaction

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 37

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

8.0 Packaging/Folder Structure and System Artifacts

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 38

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

9.0 Database Table

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 39

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 40

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

10.0 CORE TECHNICAL SERVICES DESIGN
We have used .NET Framework, ADO.NET silver light and Ajax script for developing our project. .NET Framework This is our main Application Framework. We used the ASP.Net web application Framework to build the web application. This consists of three basic features. 1. CLR (Common language runtime) and JIT (Just in time) 2. Class libraries 3. ASP.NET

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 41

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

Silver light and .NET Framework 3.5
Silver light enables development of the next generation of Microsoft .NET-based media experiences based and rich interactive applications (RIAs) for the Web. Silver light is delivered as a cross cross-platform and cross-browser plug-in that exposes a programming framework and features that are a subset of the in .NET Framework and Windows Presentation Foundation (WPF).  Support for the .NET Framework.  Support for .NET-compliant programming languages such as C#, Visual Basic, Python, and compliant Ruby.  Support for database operations and language language-integrated query (LINQ).

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 42

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

Silver Light Architecture
Unlike ASP.NET, the bulk of silver light processing occurs on the client machine thus decreasing server resource utilization and improving the Web experience on the client. The figure below shows the difference between ASP.NET processing and silver light processing: When a client initially attempts to run a Silverlight application, if the Silverlight plug-in has not been installed on the client machine, it will be downloaded and installed. Upon subsequent requests to run the application, the application will instantiate on the client machine and make requests for resources from the server only when necessary. The Silverlight plug-in can be thought of as a scaleddown version of the full .NET Framework. It only contains those classes and functionality that are applicable to a Silverlight Web client and those were streamlined and optimized for use on the Web client machine.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 43

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

ASP.NET Ajax
ASP.NET AJAX was developed to improve performance in the browser by making post backs and calls between the browser and server asynchronously. ASP.NET AJAX uses new built-in types and controls and JavaScript. Both ASP.NET and ASP.NET AJAX are heavily dependent upon the ASP.NET page event life cycle, are tightly coupled to the server, and have a tough time competing with advanced, media-rich plug-in solutions such as Adobe Flash. Additionally, it is difficult to create Web applications that offer a consistent experience across all supported browsers and platforms by using ASP.NET and AJAX. In 2006, Microsoft began developing a solution to extend into the browser and offer media experiences more robust than competing plug-in solutions.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 44

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

10.1 Persistence
This requirement is evident from a database point of view. Persistence is the ability of the programmer to have data survives the execution of a process, in order to eventually reuse it in another process. Basically we use ADO.net which is a part of the base class library included in the .NET Framework, in order to access dataset without a direct connection with the database server. So when queries are executed the relevant datasets are copied and connection with the server is disconnected. This is more reliable. At the same time those retrieved data can be used for other application executions. Therefore information can continue to exist without the paternal support of the server, or repeated server queries Persistence allows Microsoft Internet Explorer 6 and later to retain Web page information. For example, a collapsible list of links within a table of contents can remain expanded to the user's choice upon leaving and later returning to the page. Also History persists, it means that information stored within the current session’s memory. Also persistence creates new opportunities to the user. Without support from the server or with the help of cookies the navigation speed is increased. As an example once an user logged on to the system the system asked whether the user wants to remind his username and password by the system.(Normally those are stored in temporary internet files, in cookies). If the user says “Yes”, then he can just type part of his or her username and navigate to other pages very quickly. There’s a base class library for C# in the .NET framework. It provides simple file access and many other features which is a facility for our development.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 45

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

10.2 Inter-process Communication (IPC)
Inter process communication concerns how processes affect which entities are involved in other processes. This happens in two ways.  Inbound-Entities coming from other processes  Outbound-Entities go to other processes Typically, applications can use IPC categorized as clients or servers. A client is an application or a process that requests a service from some other application or process. A server is an application or a process that responds to a client request. Many applications act as both a client and a server, depending on the situation. For example, a word processing application might act as a client in requesting a summary table of manufacturing costs from a spreadsheet application acting as a server. The spreadsheet application, in turn, might act as a client in requesting the latest inventory levels from an automated inventory control application.

For our system we use protocols and ports for inter-process communication.  Protocols This is a kind of way that controls the way that data is sent between computers. Here we use http (Hyper text transfer protocol) as our protocol. The site can be accessed through this protocol. Data packets are sent in and out with the help this http protocol.

 Ports The entities and other messages are sent in and out by or to ports on the sender and the receiver. And also when run in the local host we execute our system through ports of the computer.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 46

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

10.3 Authentication and Authorization
When considering authentication we use the database (SQL Server 2000) to validate user login information, setting some session and allow login based on the validity results. Here we use our own coding to implement the authentication logic based on the roles of employees. According to the logic and database validity the logger is authenticated. The user’s credentials are stored in a cookie for use during the session.

Authorization given to the employees based on their roles (designation). Manager has full authority. Except data entry operator all the other staff has lower level authority. Roles are used to partition the application's user base into sets of users that share the same security privileges within the application as mentioned before staff has same security privilege.

Also there’s a special type of authorization for the customer, on the other hand once a customer is being registered with a reservation he becomes an authorized customer.

So we can conclude that in our project each user (except general customer) is authorized to perform some limited operations according to their authorization levels.

Above mentioned authorization providing can be categorized as below.  .NET and  SQL Server User Defined Database

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 47

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

10.4 Error Handling
All applications should have error handling. This we all know. We can't always be notified of an unhandled error (and usually aren't) when one occurs on a client's machine. The advantage we have on the Web is that we can always be notified when an unhandled error occurs. With the advent of ASP.NET, there are some great new ways to handle errors. There are some differences in .NET in not only how to handle the error, but how the information is provided to us. For example, classic ASP uses Server.GetLastError to return an ASP Error object. We can and should still use Server.GetLastError in .NET, but this now returns a type System.exception. I must give Microsoft credit for making almost everything consistent in .NET, which is quite a welcome change. Errors will occur in our applications. We try to trap for most errors using try-catch blocks (or the only possibility in traditional ASP 'on error resume next'); however, we usually don't cover every possible exception. What happens when an unhandled error occurs? Usually the user is brought to IIS's default error pages (usually located in c:\winnt\help\iishelp\common). The downsides are we have no idea when this occurs and the page doesn't have our site's look and feel. Errors are a development fact, but we strive to eliminate or handle them gracefully. With this in mind, we need to know: 1) When an error occurs 2) Where it occurred 3) What the error is The Solution For such a list of problems, the solution is actually pretty simple. There are three places in ASP.NET to define what happens to these unhandled errors. 1. In the web.config file's customErrors section. 2. In the global.asax file's Application_Error sub. 3. On the aspx or associated codebehind page in the Page_Error sub.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 48

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

The actual order of error handling events is as follows: 1. On the Page itself, in the Page_Error sub (this is default, you can name it anything because it specified Handles MyBase.Error) 2. The global.asax Application_Error sub 3. The web.config file When an exception occurs in your application, it should be an object inherited from type System.Exception, and as such will have the following public members: HelpLink Gets or sets a link to the help file associated with this exception.

InnerException Gets the Exception instance that caused the current exception. Message Source StackTrace TargetSite Gets a message that describes the current exception. Gets or sets the name of the application or the object that causes the error. Gets a string representation of the frames on the call stack at the time the current exception was thrown. Gets the method that throws the current exception.

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 49

SOFTWARE PROJECT
MULTI ACCESS AUTOMATED MARKETING SOLUTION
SOFTWARE DEVELOPMENT SPECIFICATION

FACULTY OF ENGINEERING UNIVERSITY OF RUHUNA

Page 50


				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:156
posted:5/29/2009
language:English
pages:50
Description: Faculty of Engineering University of Ruhuna This is our software project SDS