software requirements specification e store - salyangoz · pdf filesoftware requirements...
TRANSCRIPT
Software Requirements
Specification
for
E-Store
Prepared by
Erkin Deveci
Ece Bitiren
25.05.2011
Software Requirements Specification for <E-Store>
Table of Contents
1 Introduction ..........................................................................................................................
1.1 .........................................................................................................................
Purpose.........................................................................................................................
1.2 .........................................................................................................................
Initial vision..................................................................................................................
2 Overall Description ..............................................................................................................
2.1 .........................................................................................................................
Product Scope...............................................................................................................
2.2 .........................................................................................................................
Constraints...................................................................................................................
2.3 .........................................................................................................................
Operating Environment..............................................................................................
2.4 .........................................................................................................................
Design and Implementation Constraints...................................................................
3 Requirements and Analysis .................................................................................................
3.1 .........................................................................................................................
Product Requirements.................................................................................................
3.1.1 .................................................................................................................
System Improvement Objectives.......................................................................
3.1.2 .................................................................................................................
What capabilities should the new system provide for its users?....................
3.1.3 .................................................................................................................
What data must be captured and stored?........................................................
3.1.4 .................................................................................................................
What are the priorities of the various requirements?.....................................
3.2 .........................................................................................................................
External Interface Requirements...............................................................................
3.3 .........................................................................................................................
Functional Requirements............................................................................................
Software Requirements Specification for <E-Store>
3.3.1 .................................................................................................................
Actors Glossary...................................................................................................
3.3.2 .................................................................................................................
Context Diagram.................................................................................................
3.3.3 .................................................................................................................
E-R........................................................................................................................
3.3.4 .................................................................................................................
Functional Requirements...................................................................................
3.3.5 .................................................................................................................
UML.....................................................................................................................
3.3.6 .................................................................................................................
Use Case Glossary...............................................................................................
3.3.7 .................................................................................................................
Use Case Diagrams.............................................................................................
3.3.8 .................................................................................................................
Use Case Scenarios..............................................................................................
3.3.9 .................................................................................................................
Activity Diagrams...............................................................................................
3.3.10 ...............................................................................................................
System Sequence Diagrams...............................................................................
3.3.11 ...............................................................................................................
Data Flow Diagrams..........................................................................................
3.4 .........................................................................................................................
Non-functional Requirements.....................................................................................
3.4.1 .................................................................................................................
Expectations Management Matrix....................................................................
3.4.2 .................................................................................................................
Task Estimation..................................................................................................
3.4.3 .................................................................................................................
Gantt Chart/ SW Development Plan.................................................................
3.4.4 .................................................................................................................
Pert Chart............................................................................................................
3.4.5 .................................................................................................................
COCOMO............................................................................................................
Software Requirements Specification for <E-Store>
Revision History
Name Date Reason For Changes Version
Erkin Deveci 20.03.2011 Activity and Sequences v.1.0
Ece Bitiren 20.04.2011 Data Flow Diagrams and General Revision v.2.0
Introduction
Purpose
In a web based project - specialized as E-Store - it is aimed to analyze the varying point of
views : customer, company, vendor etc. The structure of this project is being handled at this
document.
Initial Vision
Providing instant shipment shopping to customers without waiting days or hours. Minutes
can be enough for products to be handled. Also creating profiles, showing up clothes obtains
increased advertisement, having fun, creating own fashion, seeing who wear what. This e-
store project will be innovative looking to old e-store picture.
Overall Description
Product Scope
Using the great influence of the internet on human beings the product is prepared in order to
improve the shopping opportunities of the potential customers. This product will take a
bridging role between customers, companies and vendors, and make them bound on the
online platform.
Constraints
This system started analyze and design on 11.03.2011 and will be finish on 06.05.2011
through e-store system will be built in over 2 months.
Initially no profile creating only e-shopping and fast shipping later creating profiles and
showing up clothes to friends will be available
Sales reports couldn’t categorized separately , must be develop in maintenance time.
User can only order or purchase item only one vendor at the same time.
Operating Environment
Linux
Mac Os X
Windows
The other operating systems which can ;
have web browsers
support W3C standards
Design and Implementation Constraints
Use Case , Context Diagram , UML with Sybase Power Designer.
Activity , Sequence , DFD diagrams will be draw in Sybase.
Software Implementation with Microsoft Visual Studio .Net 2010 with C# and Asp.net.
Used DBMS Microsoft SQL Server 2008.
CSS, Jquery, HTML 5 standards.
Ajax, Silverlight technologies is going to use.
Requirements and Analysis
Product Requirements
3.1.1 System Improvement Objectives
◦ Secured customer information (Using SSL 128bit)
◦ Using cryptology to high up security
◦ Increased network speed
◦ 7/24 hours non-stop working servers
3.1.2 What capabilities should the new system provide for its users?
◦ Fast product service
◦ Personal profiles to show up clothes
◦ Low price shipment
◦ Brand based clothes
◦ New collection’s
◦ One click easy shopping
◦ Improved company sales
◦ Marketing through customers’ contacts
◦ No stock limitation and management
3.1.3 What data must be captured and stored?
◦ Company Based Data
▪ Company based stocks “company is responsible for stock limitation“
▪ Responsible for prices
◦ Customer Based Data
▪ Own profiles and collections which customers bought
▪ Product baskets
▪ Customer information (Address, Phone etc info)
▪ Shipping info
▪ Deliver info
▪ Purchase type
◦ Vendor Based Data
▪ Own collections or products added by vendors separately
▪ Vendor based shipment
▪ Sales info
◦ Well Organized Server Architecture
▪ Cloud computing
3.1.4 What are the priorities of the various requirements?
◦ Hardware Based
▪ Servers have high speed internet connections
▪ Continuous work cycle
◦ Web Application Based
▪ Need good programmers and architectures
▪ Vendor based interfaces or software packages need
External Interface Requirements
Functional Requirements
3.3.1 Actors Glossary
Term Description
IT Staff An employer responsible for all IT based activities :
software development, testing etc.
Sales Department Sales department mainly takes care of the financial calculations
by presenting possible advantages (e.g. modules) in order to
increase the profit.
Marketing Department Marketing department handles the marketing strategies to take
the attention of the potential customers and brands.
Maintenance Department This department makes system work as productive and
continuity by providing the customer support and passing the
needs of both the customers and brands on the system.
Data Warehouse A system that processes, stores data (e.g. customer data,
vendor brand's data, product data etc.).
Control Manager An employer controlling the product's information and the
information of the customers. He/She prevents the unwanted
information due to mistake or ethical policy.
Company’s Contact A contact person from the vendor brand, who is going to
decide to sell the products through the e-store system, and
who is going to get reports for their financial increase by using
this system.
Product Manager An employee of the brand, who is responsible for uploading
and updating the product details to the system.
Company’s Vendor The vendor has access to the products' information and has
authorization to upload their stock details according to the
products uploaded by the brand's employees.
Customer Someone who does shopping by using the e-store system.
3.3.2 Context Diagram
3.3.3 E-R
Functional Requirements
User
register
verify polymorphism
verify(Company) polymorphism
verify(Vendor) polymorphism
login(User,Pass)
Customer inheritance (USER)
update Profile
select Product
order
type Destination
select Payment Type
rate
comment
add Address
view Orders
select Address
select Order
rebate
update Address
Customer Address
get part
group Customers
Vendor inheritance (USER)
pick in stock product
feedback
get sales report
receive order
get rebate report
approve Vendor
Vendor In Stock Product
alert out of Stock
get Amount
set Amount
increase Amount
decrease Amount
Company inheritance (USER)
upload Product
update Product
get Report
get Rebate Report
Product
check in Sale
get Product
announce Sale Product
sale Product( amount, percentage )
City State Part
show City
show States
show Parts
Order
alert Rebate
check Rebate Time
add Order Product
approve Purchase
get Order Count by Company *variations can also includes payment reports
get Order Count by Vendor *variations can also includes payment reports
Payment
add To Commission
Commission
get Monthly Profit report
get Annual Profit report
get Profit
3.3.4 UML Class
See Appendix A-1.
3.3.5 Use Case Glossary
UC NAME UC DESCRIPTION PARTICIPATING ACTORS AND ROLES
Sales Report (Profit) The company's contact will get Company's Contact
the profit information of their
brand through the sales report
which he/she will see from
his/her system account.
Item Management The upload of the item details Product Manager, Company's
is handeled by the product Vendor
manager, and the company's
vendor will choose from these
item catalog according to their
stock information.
Improvement Report The improvements after using Company's Vendor
(Opt) the e-store system will be
presented to the company's
vendor, so that he/she will have
the opportunity to gain the profit
information in detail. This is an
optional module. The marketing
department gets also this
documentation but for the whole
systems usage.
Software consulting According to the feedback of the IT Staff,Maintenance
customers and company's Department
employees the -by the
maintenance department-
analyzed data's report is being
used by the IT staff for software
consulting.
Test and Detect By the development of the IT Staff
Errors system there could occur
some errors on the system,
they will be detected and
prevented by the tests done
by the IT staff.
Profile Actions The customer is able to create Customer
a profile by adding his/her
personal information after
registration. By signing in this
account he/she will be able to
see/buy/reserve items from the
system, and the items that he/she
will purchase will be shown on
his/her profile.
Register The system will ask for a Customer
registration from the customer
in order to let him/her to log on
to the system. The identity and
bank account informations are
required.
Reserve Item In case the vendor's stock runs Customer, Company's Vendor
out of the wnated item, the
customer will click on the reserve
button.
Purchase Item If the customer wants to buy an Customer
item, he/she will verify that
his/her bank account
informations are updated. After
the verification from the bank is
also done by the system, the item
will be sent to the customer, and
if he/she has a profile on the
system the purchased item will
be seen on his/her profile, too.
Prepare Special With the analysis of improvement Marketing Department
Campaigns report some special campaigns
will be provided by the marketing
department, in order to get
attention of a wide spreaded
audiance.
Analyze Customer According to the city regions Sales Department
Potential various customer potential will
be calculated and reported,
these reports are going to be
used by the sales and marketing
department.
Analyze Profit The profit will be analyzed by the Sales Department
sales department and this
analysis will be used in order to
improve the profit.
Analyze Feedback The taken feedback is analyzed Maintenance Department, IT
by the maintenance department Department
and this analysis is reported to
the IT department, they will do
software consulting according
to this report.
Get Feedback The feedback from customer's Maintenance Department,
and company's employees - as Company's Vendor, Customer,
company's vendor and Company's Contact
company's contact - will be
taken by the maintenance
department.
Make Report The control manager will make Control Manager
(Companies, report of the companies and
Vendors) vendors, it will be used for the
improvement of the system.
Check Information The information passed to the Control Manager, Customer,
Suitability system by both the customer Product Manager,
or product manager will be Data Warehouse
checked by the control
manager according to the
suitability conditions.
3.3.6 Use Case Diagrams
See Appendix A-2.
3.3.7 Use Case Scenarios
User UI System
Registration (Customer)
1. User clicks register button and system shows registration form
2. User fills the required fields (username,password,name,surname,email)
3. User adds address information
4. User accepts agreement
5. User clicks save button
6. System sends an email or text message for verification
7. Customer activates his/her account through this verification
8. System sends successful registration notification
9. Finalize registration
Registration (Vendor,Company)
1. User clicks register button and system shows registration form
2. User fills the required fields (username,password,name,surname,email etc)
3. User adds address information
4. User accepts agreement
5. User clicks save button
6. System sends text message for verification
7. Admin checks and verifies registration
8. Registration notification will be sent
9. Finalize registration
Login
1. User clicks login button and system redirects to login page
2. User enters username and password
3. if username and password is true than redirects to home page
4. System redirects user to home page
5. Finalize login
6. else system alerts user *wrong username or password
7. System redirects user to login page
8. else if number of tries > 5
9. Show random picture which guarantees that person is trying to login
10. System redirects user to login page
Customer UI System
Purchase Item
1. Customer selects and adds product to cart (n times)
2. Customer clicks checkout button to finalize order
3. System asks which address is the customer going to use
4. if customer needs new address
5. Customer adds new address
6. Customer selects address to ship items
7. Customer selects payment type and fills payment info
8. Approve order purchase
9. System shows order report to customer
10. System adds which order made from who and bought from which Company to the
database
11. System sends purchased item report to vendor
12. Finalize purchase
Rebate Item
1. Customer view orders and select one of the order
2. Customer clicks rebate button
3. if (Up to seven days it could be rebated is ) true
4. System informs successful rebate to customer
5. System rebates order
6. System alerts rebated product to company
7. else cancel request
8. Finalize rebate
Profile Actions
1. Customer can select 4 types of actions
a. Feedback
b. Update Profile Information
c. View Orders
d. Rate Orders
2. if feedback selected
3. Customer select type of feedback
a. for company
b. for system
4. Customer writes comments (detail information)
5. Clicks submit button
6. System report feedback to maintenance department
7. Finalize feedback
8. if update profile information selected
9. Customer can
a. update profile information
b. update address
c. add new address
10. Customer clicks save button
11. Finalize update information
12. if customer want to view orders
13. Click view orders button
14. System returns orders’ detailed information
15. if customer want to rate order
16. Customer select order and select rate number (between 1-10)
17. Customer clicks rate button
18. System saves rate information
19. Finalize rate
20. Finalize action
IT System
Software Consulting
1. Request help about software via email from company vendor
2. IT department analyzes the problem
3. IT department gives directives to the company vendor
4. Company vendor applies directives to solve the problem
5. Finalize consulting
Test and Detect Errors
1. IT Department test errors depending to the software measurement metrics
2. IT Department write reports about bugs and errors
3. Send reports to the developers via email
4. Developers fix errors depending on reports
5. Finalize error detection and testing
Information Management System
Check info Suitability (Profile and Product)
1. User uploads information (product info, profile info etc)
2. Control manager checks information uploaded by user
3. If information is suitable
a. Accept information and approve to publish
4. Else information is not suitable
a. Decline information and report to user
5. Finalize info suitability
Maintenance System
Get Feedback
1. Customer rates order between 1 and 10 depending on service quality
2. Customer can also write comments in his/her orders page.
3. Maintenance department gets feedback
4. Finalize get feedback
Analyze Feedback
1. Maintenance department gets feedback and analyzes it
2. Maintenance department creates report grouping by vendor and company depending
on customer feedback
3. Sends reports to Employee (IT Department, Sales and Marketing Department) and
Company Vendor
4. Finalize analyze feedback
Reporting System
Improvement Report
1. Marketing department queries orders and groups sales by vendor and company
(getProfit,getMonthlyProfitReport,getAnnualProfitReport)
2. Marketing department analyzes profit reports
3. Marketing department determines improvement reports
4. Prints and saves improvement report to computer
5. Finalize improvement report
Company Performance Report
1. Employee queries database to determine order counts groups by company
(getOrderCountBycompany)
2. Employee gets performance data
3. Employee sends report to company employee
4. Finalize performance report
Vendor Performance Report
1. Employee queries database to determine order counts group by
vendor(getOrderCountByVendor)
2. Employee gets performance data
3. Employee sends report to company vendor
4. Finalize performance report
Sales and Marketing System
Analyze Profit
1. Sales department queries data warehouse profit
(getProfit,getMonthlyProfitReport,getAnnualProfitReport)
2. Sales department analyzes profit
3. Sales department prints report
4. Finalize analyze profit
Analyze Customer Potential
1. Marketing department queries data warehouse orders made by
customers(getCustomers Order By maximum order count)
2. Marketing department analyzes customer potential region
3. Marketing department decides to make campaign on that regions
4. Marketing department prints potential customer region report
5. Finalize analyzing customer potential
Prepare Special Campaigns
1. Marketing department gets analyzed customer potential region report
2. Prepare special campaigns for the regions where the shopping is done at most by
the customers
3. Finalize preparing special campaigns
3.3.8 Activity Diagrams
See Appendix A-3.
3.3.9 System Sequence Diagrams
See Appendix A-3.
3.3.10 Data Flow Diagrams
See Appendix A-4.
Non-Functional Requirements
3.4.1 Expectations Management Matrix
3.4.2 Task Estimation
Tasks Identification and Estimation of Task Durations
Identification of tasks Task Duration(real-optimistic-pessimistic)
Hotel Chain Management R O P
1. Initiating 1 1 1
1.1 Select project manager
1.2 Form project team
1.3 Complete initiating
2. Scope Definition & Problem Analysis 1 1 2
2.1 Constraint
2.2 Statement of work
2.2.1 Define purpose and initial vision
2.2.2 Draw expectations management matrix
2.2.3 Define scope and constraints
2.2.4 Identify tasks and estimate task durations
2.2.4.1 Classic technique
2.2.5 Draw
2.2.5.1 PERT chart
2.3 Complete scope definition & problem analysis
3. Requirements Analysis 1 1 1
3.1 Business Requirements Statement
3.1.1 Define capability requirements
3.1.2 Define data/database requirements
3.1.3 Define performance level requirements
3.1.4 Define priorities of various requirements
3.2 Complete Requirements Analysis
4. Logical Design 7 4 9
4.1 Logical System Models and Specifications
4.1.1 Logical data models
4.1.2 Logical process models
4.1.3 Logical interface models
4.2 Complete Logical Design
5. Decision Analysis 2 2 4
5.1 Technical feasibility
5.2 Operational feasibility
5.3 Economic feasibility
5.4 Schedule feasibility
5.5 Risk feasibility
5.6 Complete Decision Analysis
6. Physical Design & Integration 12 10 14
6.1 Physical Design Models and Specifications
6.2 Design Prototypes
6.3 Redesigned Business Processes
6.4 Integrated Physical Design
6.5 Complete physical design & integration
7. Construction & Testing 19 17 21
7.1 Construction
7.1.1 Software
7.1.1.1 Purchased
7.1.1.2 Custom-built
7.1.2 Databases
7.1.2.1 Data Center
7.1.3 User and System interfaces
7.1.4 Networks
7.2 Testing
7.3 Implementation Ready Functional System
7.4 Complete Construction and Testing
8. Installation & Delivery 1 1 3
8.1 Deliver System into Production
8.2 Deliver User Training
8.3 Deliver Completed Documentation
8.4 Convert Existing Data
8.5 Working System
8.6 Complete Installation & delivery
9. System Operation & Maintenance - - -
9.1 System Support
Estimation of Task Durations according to Classic Technique:
Activities | Task Duration Estimation – Classical (et= (o+4r+p)/6 ...et: expected time) | Expected Time
1 (1+4*1+1)/6 = 1 1
2 (1+4*1+2)/6 =1,166 1,2
3 (1+4*1+1)/6 =1 1
4 (4+4*7+9)/6 =6,833 6,8
5 (2+4*2+4)/6 =2,333 2,3
6 (10+4*12+14)/6 = 12 12
7 (17+4*19+21)/6 = 19 19
8 (1+4*1+3)/6 = 1,333 1,3
9 - -
3.4.3 Gantt Chart / SW Development Plan
See Appendix B.
3.4.4 Pert Chart
3.4.5 COCOMO
Appendix A: Sybase Components
Context, UML, Use Case, Activity, System Sequence, Data Flow diagrams are constructed
with the Sybase Power Designer tool.
Appendices are categorized as :
A-1: E-Store UML Class
A-2: E-Store Use Cases
A-3: E-Store Activity and Sequences
A-4: E-Store DFDs
Appendix B: Software Development Plan
Software Development Plan is a kind of Gantt Chart of this project shown by using the
Microsoft Project 2010 tool.
Sybase PowerDesigner Object-Oriented Model Report
E-Store UML Class
Model: E-Store UML Class Report: UML Class
Author: Erkin Deveci | Ece Bitiren Version:
Date: 29.05.2011
Object-Oriented Model E-Store UML Class
PowerDesigner 29.05.2011 Page 2
I List of diagrams Name Code
Class Diagram ClassDiagram
II Diagram Class Diagram
1..1
1..*
1..1
0..*
1..1
1..1
1..1
1..1
1..1
0..*
0..*
1..1
0..1
0..*
1..1
1..1
1..1
1..*
1..1
1..*
1..1
1..*
1..1
1..*
1..1
1..*
1..1
1..1
1..1
1..1
1..1
0..*
1..1
1..*
1..1
0..*
Customer
-
-
-
-
-
-
CustomerID
Surname
Phone
Mobile
Birthdate
: int
: String
: String
: int
: int
: Date
+
+
+
+
+
+
+
+
+
+
+
+
+
updateProfile ()
selectProduct ()
order ()
typeDestination ()
selectPaymentType ()
rate ()
comment ()
addAddress ()
viewOrders ()
selectAddress ()
selectOrder ()
rebate ()
updateAddress ()
: void
: void
: void
: void
: void
: void
: void
: boolean
: void
: boolean
: void
: void
: voidVendor
-
-
-
-
-
-
VendorID
CompanyID
PartID
Owner
Address
IsApproved
: int
: int
: int
: String
: String
: boolean
+
+
+
+
+
+
pickInStockProduct ()
feedback ()
getReport ()
receiveOrder ()
getRebateReport ()
approveVendor ()
: void
: void
: Report
: void
: Report
: void
In Stock Product
-
-
-
-
InStockProductID
VendorID
ProductID
NumberInStock
: int
: int
: int
: int
+
+
+
+
+
alertOutOfStock ()
getAmount ()
setAmount ()
increaseAmount ()
decreaseAmount ()
: String
: float
: void
: void
: void
Company
-
-
-
-
-
-
-
-
CompanyID
Info
Address
Phone
PartID
ProductManager
CompanyManager
CommissionRate
: int
: String
: String
: int
: int
: String
: String
: float
+
+
+
+
uploadProduct ()
updateProduct ()
getReport ()
getRebateReport ()
: void
: void
: Report
: Report
EmployeeApplication
-
-
-
EmployeeID
ApplicationID
Date
: int
: int
: Date
+
+
saveApplicationHistory ()
createApplicationReport ()
: void
: Report
Employee
-
-
-
-
-
EmployeeID
Surname
Position
Phone
: int
: String
: String
: String
: int
+
+
+
updateItem ()
approveInfo ()
declineInfo ()
: Product
: void
: void
Product
-
-
-
-
-
-
-
-
ProductID
CompanyID
Photo
Name
Popularity
Price
IsDiscount
IsApproved
: int
: int
:
: String
: int
: float
: boolean
: boolean
+ checkInSale () : boolean
Product Category
-
-
-
PCategoryID
Name
Photo
: int
: String
:
+ getProduct () : void
Discount Product
-
-
-
-
DiscountProductID
ProductID
DiscountAmount
DiscountRate
: int
: int
: float
: float
+
+
announceSaleProduct ()
saleProduct ()
: String
: void
Subcategories
-
-
-
SubcategoryID
PCategoryID
Name
: int
: int
: String
+ getProduct () : void
Customer Address
-
-
-
-
-
-
AddressID
CustomerID
Type
PartID
Address
AddressDescription
: int
: int
: String
: int
: String
: String
+
+
getPart ()
groupCustomers ()
: Part
: Customer
Vendor Feedback
-
-
-
-
VendorFeedbackID
VendorID
Comment
Rate
: int
: int
: String
: int
Order
-
-
-
-
-
-
-
-
-
-
-
OrderID
CustomerID
AddressID
Destination
DestinationDescription
TotalAmount
PaymentID
OrderDate
OrderTime
Pleasure
IsRebated
: int
: int
: int
: String
: String
: float
: int
: Date
: Time
: int
: boolean
+
+
+
+
+
+
alertRebate ()
checkRebateTime ()
addOrderProduct ()
approvePurchase ()
getOrderCountByCompany ()
getOrderCountByVendor ()
: String
: boolean
: boolean
: boolean
: void
: void
Commission
-
-
-
-
-
ComissionID
PaymentID
Date
Time
Commission
: int
: int
: Date
: Time
: float
+
+
+
getMonthlyProfitReport ()
getAnnualProfitReport ()
getProfit ()
: Report
: Report
: Report
City
-
-
CityID
Name
: int
: String
+ showCity () : String
State
-
-
-
StateID
CityID
Name
: int
: int
: String
+ showStates () : String
Part
-
-
-
-
PartID
StateID
CityID
Name
: int
: int
: int
: String
+ showParts () : String
User
-
-
-
-
-
-
UserID
Username
Password
Authorization
Name
isVerified
: int
: String
: String
: String
: String
: boolean
+
+
+
+
+
register ()
verify ()
verify(Company) ()
verify(Vendor) ()
login(username,password) ()
: void
: boolean
: boolean
: boolean
: boolean
Application
-
-
-
ApplicationID
Name
Scope
: int
: String
: String
Payment
-
-
-
-
-
PaymentID
PaymentType
PaymentInfo
PaymentBank
Account
: int
: String
: String
: String
: char
+ addToCommission ()
OrderProduct
-
-
-
OrderID
ProductID
VendorID
: int
: int
: int
CustomerFeedback
-
-
-
-
CustomerFeedbackID
CustomerID
Comment
Rate
: int
: int
: String
: int
Object-Oriented Model E-Store UML Class
PowerDesigner 29.05.2011 Page 3
Sybase PowerDesigner Object-Oriented Model Report
E-Store Use Cases
Model: E-Store Use Cases Report: Use Cases
Author: Erkin Deveci | Ece Bitiren Version:
Date: 29.05.2011
Object-Oriented Model E-Store Use Cases
PowerDesigner 29.05.2011 Page 2
I List of diagrams Name Code
Customer UI System CustomerUISystem
Information Management System InformationManagementSystem
IT System ITSystem
Maintanance System MaintananceSystem
Report System ReportSystem
Sales and Marketing System SalesandMarketingSystem
User UI System UserUISystem
II Diagram Customer UI System
Customer UI System
Purchase Item
Customer
Profile Actions
Rebate Item
Data Warehouse
Object-Oriented Model E-Store Use Cases
PowerDesigner 29.05.2011 Page 3
III Diagram Information Management System
Information Management System
Check Info Suitability (Profile and Product)
Control Manager
User
IV Diagram IT System
IT System
( Developer )
Software Consulting
Test and Detect Errors
IT Department Company Vendor
Employee
Object-Oriented Model E-Store Use Cases
PowerDesigner 29.05.2011 Page 4
V Diagram Maintanance System
Maintanance System
Analyze Feedback
Get Feedback
Customer
Maintanance DepartmentCompany Vendor
Employee
Sales Department
Marketing Department
IT Department
Object-Oriented Model E-Store Use Cases
PowerDesigner 29.05.2011 Page 5
VI Diagram Report System
Reporting System
Data Warehouse
Improvement Report (Opt)
Company Perf Report
Vendor Perf Report
Marketing Department
Company Vendor
Company Employee
Employee
Object-Oriented Model E-Store Use Cases
PowerDesigner 29.05.2011 Page 6
VII Diagram Sales and Marketing System
Sales and Marketing System
Analyze Profit
Analyze Customer Potential
Sales Department
Prepare Special Campaigns
Marketing Department
Data Warehouse
Object-Oriented Model E-Store Use Cases
PowerDesigner 29.05.2011 Page 7
VIII Diagram User UI System
User UI System
Customer
IT Department
Sales Department
Employee
Login
Register
Data Warehouse
User
Company Employee
Object-Oriented Model E-Store Use Cases
PowerDesigner 29.05.2011 Page 8
Sybase PowerDesigner Business Process Model Report Activity and Sequence Diagrams
Author: Erkin Deveci | Ece Bitiren Version:
Date: 29.05.2011
Business Process Model Customer UI System
PowerDesigner 29.05.2011 Page 2
I List of diagrams Name Code
Profile Actions Profile Actions
Purchase Item Purchase Item
Rebate Item Rebate Item
II Diagram Profile Actions
Business Process Model Customer UI System
PowerDesigner 29.05.2011 Page 3
III Diagram Purchase Item
Business Process Model Customer UI System
PowerDesigner 29.05.2011 Page 4
IV Diagram Rebate Item
Business Process Model Information Management System
PowerDesigner 29.05.2011 Page 5
V List of diagrams Name Code
Check Info Suitability Check Info Suitability
VI Diagram Check Info Suitability
Business Process Model Maintanance System
PowerDesigner 29.05.2011 Page 6
VII List of diagrams Name Code
Software Consulting Software Consulting
Test and Detect Errors Test and Detect Errors
VIII Diagram Software Consulting
IX Diagram Test and Detect Errors
Business Process Model Maintanance System
PowerDesigner 29.05.2011 Page 7
X List of diagrams Name Code
Analyze feedback Analyze feedback
Get feedback Get feedback
XI Diagram Analyze feedback
XII Diagram Get feedback
Business Process Model Sales and Marketing System
PowerDesigner 29.05.2011 Page 8
XIII List of diagrams Name Code
Company Perf Report Company Perf Report
Improvement Report Improvement Report
Vendor Perf Report Vendor Perf Report
XIV Diagram Company Perf Report
Business Process Model Sales and Marketing System
PowerDesigner 29.05.2011 Page 9
XV Diagram Improvement Report
XVI Diagram Vendor Perf Report
Business Process Model Sales and Marketing System
PowerDesigner 29.05.2011 Page 10
XVII List of diagrams Name Code
Analyze Customer Potential Analyze Customer Potential
Analyze Profit Analyze Profit
Prepare Special Campaigns Prepare Special Campaigns
XVIII Diagram Analyze Customer Potential
Business Process Model Sales and Marketing System
PowerDesigner 29.05.2011 Page 11
XIX Diagram Analyze Profit
XX Diagram Prepare Special Campaigns
Business Process Model Sales and Marketing System
PowerDesigner 29.05.2011 Page 12
XXI List of diagrams Name Code
Login Login
Registration Customer Registration Customer
XXII Diagram Login
XXIII Diagram Registration Customer
Business Process Model Sales and Marketing System
PowerDesigner 29.05.2011 Page 13
Sybase PowerDesigner Business Process Model Report
E-Store Data Flow Diagrams
Author: Erkin Deveci | Ece Bitiren Version:
Date: 29.05.2011
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 2
I List of diagrams Name Code
Customer UI Context Customer UI Context
Customer UI Level 0 Customer UI Level 0
Customer UI Level 1 Customer UI Level 1
II Diagram Customer UI Context
receive Order info
rebate report info
Context Data Model
purchase item info
profile actions info rebate info
rebate state
rebate order report
action state
receive feedback information
get Rebate report
USER UI System
0
Customer UI
System
Customer
Company Employee
Company Vendor
Maintanance
Department
receive report info
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 3
III Diagram Customer UI Level 0
rebate Report info
Order info
receive order Report
receive Order info
purchase item info
profile actions info
rebate info
rebate state
rebate info
action state
receive feedback information
get Rebate report
Customer
Maintanance
Department
Company Vendor
Company Employee
1
Purchase Item
2
Rebate Order
3
Profile Action
1 Order
Level 0 Data Flow Diagram
receive
Order report
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 4
IV Diagram Customer UI Level 1
purchase item info
Company Employee
Company Vendor
Customer
Maintanance
Department
2 Customer
3 Customer Feedback
1.1
Select Product
(Purchase Item)
1.4
Select Payment
(Purchase Item)
1.3
Select Address
(Purchase Item)
1.5
Get Order report
(Purchase Item)
1.2
Add Product To Cart
(Purchase Item)
2.2
Determine rebate
(Rebate Order)
2.1
Select Order
(Rebate Order)
3.6
View Orders
(Profile Action)
3.2
Get Feedback
(Profile Action)
3.4
Get Updated Profile
(Profile Action)
3.5
Profile Actions
(Profile Action)
3.7
Rate Order
(Profile Action)
3.3
Update Profile
(Profile Action)
3.1
Feedback
(Profile Action)
1 Order : 1
1 Order : 2
product info reserved product info
order address and items info
order info receive order info
order information
receive order report
rebate info
receive order report
rebate report info
rebate time is rebate infoget rebate report
rebate state
1 Order : 3
feedback info feedback data receive feedback info
action state is feedback state saved
profile action info
action state
action state profile information
profile data
is updated data
action state
orders info
formatted order information
get order info
rate information
action state
Level 1 Data Flow Diagram
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 5
V List of diagrams Name Code
IM System Context IM System Context
IM System Level 0 IM System Level 0
VI Diagram IM System Context
control uploaded info
upload info
Control Manager User
Context Data Model
IM System
0
Information
Management
System
state of info approv ement
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 6
VII Diagram IM System Level 0
state of approv ement
Control ManagerUser
1
Check Info Suitabil ity
1 Product and Customer
control uploaded info
upload info
approv ed info
Level 0 Data Flow Diagram
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 7
VIII List of diagrams Name Code
IT System Context IT System Context
IT System Level 0 IT System Level 0
IX Diagram IT System Context
get software errors
IT System
0
IT System
Employee
IT Department
Company Vendor
fix bugs and errors
get software consulting request
get software errors
test and detect errors
request software consulting
get software consulting
Context Data Model
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 8
X Diagram IT System Level 0
get software errors
Employee
IT Department
Company Vendor
1
Software
Consulting
2
Test and Detect
Errorsfix bugs and errors
test and detect errors
get software consulting request
respond software consulting
request software consulting
get software consulting
Level 0 Data Flow Diagram
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 9
XI List of diagrams Name Code
Maintanance System Context Maintanance System Context
Maintanance System Level 0 Maintanance System Level 0
XII Diagram Maintanance System Context
get customer feedback
Maintanance
Department
Customer
Employee
Company Vendor
Maintanance System
0
Maintanance
System
analyze customer feedback
rate and comment
get customer feedback report
get customer feedback report
Context Data Model
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 10
XIII Diagram Maintanance System Level 0
Company Vendor
Customer
EmployeeMaintanance
Department
1
Get Feedback
2
Analyze Feedback
1 Customer Feedback
analyze customer feedback
formatted customer feedback
customer feedback
get customer feedback
rate and comment
get customer feedback report
get customer feedback report
Level 0 Data Flow Diagram
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 11
XIV List of diagrams Name Code
Reporting System Context Reporting System Context
Reporting System Level 0 Reporting System Level 0
XV Diagram Reporting System Context
query orders by group sales
Marketing
Department
Employee
Company Employee
Company Vendor
Reporting System
0
Reporting
System
profit reports
improv ement report
query order counts per company
query order counts per v endor
performance data (for v endor)
create and send performance report
(for v endor)
performance data (for company)
create and send performance
report (for company)
get performance report
get performance report
Context Data Model
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 12
XVI Diagram Reporting System Level 0
1
Improvement Report
2
Company Performance
Report
3
Vendor Performance
Report
Marketing
Department
1 Orders
query order and group sales
profit reports
improv ement report
orders and group sales
order counts per company
Employee
query query order counts per company
performance data (for company)
create and send performance report (for company )
Company Employee
get performance report
performance data (for v endor)
query order counts per v endor
create and send performance report (for v endor)
Company Vendor
get performance report
order counts per v endor
Level 0 Data Flow Diagram
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 13
XVII List of diagrams Name Code
SM Context SM Context
SM Level 0 SM Level 0
XVIII Diagram SM Context
Sales Department
Marketing
Department
Sales and Marketing System
0
Sales and
Marketing
System
query profit
get profit report
make campaigns
query orders made by customers
gets analyzed customer potential region report
Context Data Model
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 14
XIX Diagram SM Level 0
Marketing
Department
Sales Department
1
Analyze Profit
2
Analyze Customer
Potential
3
Prepare Special
Campaigns
1 Commission
2 Orders
query profit
get profit report
get commission to analyze profit
return commission info
get customers (order by max order count)
return formatted customer order info
query orders made by customers
get analyzed customer
make campaigns
Level 0 Data Flow Diagram
ü
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 15
XX List of diagrams Name Code
User UI Context User UI Context
User UI Level 0 User UI Level 0
User UI Level 1 User UI Level 1
XXI Diagram User UI Context
Context Data Model
USER UI System
0
User UI
System
registration info
login info
finalization of registration
login status info
User
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 16
XXII Diagram User UI Level 0
User
registration info
login info
finalization of registration
login status info
1
Register
2
Login
1 User
registration data
login data
status of matched data
Level 0 Data Flow Diagram
Business Process Model Customer UI System DFD
PowerDesigner 29.05.2011 Page 17
XXIII Diagram User UI Level 1
registration info
login info
finalization of registration
login status info
verification data
login data
status of matched data
Level 1 Data Flow Diagram
1 User
User
2.1
Check Login
(Login)
registration data
2.2
Determine Login
Status
(Login)
is verified data
1.1
Get Registration
(Register)
1.2
Verify Account
(Register)