OBPSS Analysis

Online Beauty Products Shopping System –
Version:1.0.0.0
Analysis Report
Online Beauty Products Shopping System

(OBPSS)
Version:1.0.0.0
“3S1M” Team Members
Sanjeev [20071044]
Sonia [20091241]
Page 1 of 40
Created by "3S1M" Team
Version:1.0.0.0
Mandeep [20091501]
Sunita [20090351]
Table of Contents
SNO Content Page No
1 Project Initiation Document History 3

1.1 Document Location 3
1.2 Revision History 3
1.3 Approvals 3
1.4 Distribution 3
2 Introduction 4
3 System Description 4
4 Use cases 7
4.1 Use case Diagram 7
4.2 Use case Description 8
5 Activity Diagrams 20
6 Sequence Diagrams 23
7 Class Diagram 25
Appendix 1: Updated Risk Register 26

Appendix 2: Updated Gantt Chart 29
Appendix 3: Cost Report 30
Page 2 of 40
Version:1.0.0.0
1. Project Initiation Document History
1.1 Document Location

This document is only valid on the day it was printed.
The source of the document will be found on the project's PC in location
1.2 Revision History
Date Version Change Author Requested By

August 06 2009 Initial Draft Sanjeev John Paynter
August 22 2009 1.1 Requirement and cost Sanjeev John Paynter
analysis
1.3 Approvals
This document requires the following approvals.
Signed approval forms are filed in the Management section of the project files.
Name Signature Title Date of Issue Version
Mr. John Paynter Management Board 22 August 2009 1.1

Mr. Richard Client Representative 22 August 2009 1.1
Mr. Sanjeev Sanjeevgi Project Manager 22 August 2009 1.1
llalla
1.4 Distribution
This document has been distributed to:
Name Title Date of Issue Version
Mr. John Paynter Management Board 22 August 2009 1.1
Page 3 of 40
Version:1.0.0.0
2. Introduction:
An analysis report gives a detailed and descriptive outline of the business needs and
system requirements of the project, for the benefit of the client. It breaks down the
project into managable parts, and describes each individual component with diagrams. It
also provides alternative solutions to problems where such may be needed.
An analysis report also includes:
Use Case diagrams, which explain what a system should do to successfully fulfill the
user requirements
Activity diagrams, which show how the system will accomplish each goal.
Class diagrams, which provides a logical view of the system and all class relationships.
Sequence Diagrams, which show the sequence of interaction between the various
parts of the system.
A Risk Register, which lists the most likely pitfalls in the completion of the project,
along with recommendations to mitigate the severity of their impact (Updated for
Analysis Report).
A Gantt chart, which lays out the task hierarchy, resource allocation and timeline of
the project, and indicates the various milestones or deliverables (Updated for
Analysis Report).
A Cost Report, which lists the total expenditure of all available resources (Updated
for Analysis Report).
3. System Description
Zinaz Beauty Salon is a privately-owned company specializing in beauty services and

products sector. In particular they offer the latest services and products sourced from
Brazil. Despite enjoying adequate profitability in its niche, Zinaz understands that it
holds limited appeal in the broader market. It has accurately identified lack of brand
recognition and poor accessibility as its primary disadvantages, and aims to remedy that
with the proposed online store. With easy access over the web for customers
Page 4 of 40
Version:1.0.0.0
nationwide, Zinaz hopes to broaden its entrepreneurial scope while providing a

convenient service to its target demographic.
The Zinaz products website is being designed with an emphasis on user-friendliness and
ease of use. As such, a simple, easily navigable layout is the primary focus of the
project. The site greets the visitor with an introduction page that clearly indicates where
existing members can log in and where new members can sign up. Within the site
proper, the user will have access to browsing and shopping cart functions. For this, a
page for viewing available products in a sorted list is required, along with options to add
items to the shopping cart, change the number of selected items, etc. After reviewing
and finalizing the selection, users can proceed to the payment page, where they can
select from a variety of payment options. For payment by credit card, users are
redirected to a separate page where credit card details are entered and the account is
verified by the issuing bank. Lastly, a successful transaction record stored for further
process.
Page 5 of 40
Version:1.0.0.0
1. Use Cases
1.1. Use Case Diagram
OBPSS(ONLINE BEAUTY PRODUCTS SHOPPING SYSTEM )
«extends» Signup
-End2 -End43 «extends»

Login
Change Password
-End20 * «extends» *
«extends»
* «extends»
-End1
Login for Admin &
-End5
-End3
-End21 Staff
* Send Feedback
* ** -End29
*-End37
-End31
-End49
** -End4 -End11
-End12
Update Products -End44
RICHARD/ZINIA View Products -End10
* «extends»
-End6 *
-End13 * *
-End14 -End9
«uses» «extends» *
Update Price
* View Prices Select Products *
* -End53
*
* «uses»
-End22 «extends»
CUSTOMER
Manage Staff A/C
*
View Product_Choice
-End19 Add to Shoppingcart
* -End28
-End27
-End23
Reply Feedback «extends»
-End30* «extends»
*-End35
*-End41
-End51 *
-End39
-End47 Make Payment
* ** «uses»
-End24
Provide Credit_Info «uses»
View Order_List
ZINIA/STAFF * Cancel Order
«uses»
Provide
Shipping_Info
-End25
-End26
Verify Credit_Info -End45
-End17 *
«uses» *
«uses» *
*
-End7
Print/Mail Invoice <<Banker System>>
* -End46
-End40 -End15 -End18
-End8
*
* -End16
-End56
-End38
* Place Order
-End36 * **
Access E-Mail «uses» * -End55 *
Marketing
Access
* -End42 Customer_Info
«uses» -End32 *
* -End52
* <<System>>
Send SMS -End33
Track
Delivery_Status -End34
*
-End50
* -End48
* * *
-End54
Logout
<<Courier_System>>
Page 6 of 40
Version:1.0.0.0
4.2 Use Case Descriptions
1. Use Case Name: Login to Website
Goal in Context: A user (Customer or Richard/Zinia or Other Authenticated Staff

Members) wishes to login to the system
Preconditions: The user has an existing account
Successful End Condition: The user logs in.
Failed End Condition: The user fails to login.
Primary Actors: Richard, Zinia, Other Authenticated Staff Members, and Customers.
Secondary Actors: Login info database.
Triggers: The user’s login details are entered into the system
MAIN FLOW:
Step Action:
 Log in details are entered by the user

 The system verifies the details
 The user logs in
 For other authenticated staff members, After first login they redirected to Change
password page
EXTENSIONS:
Step Branching Action:
 The database does not validate the log in information.
 The data remains invalidated.
2. Use Case Name: Signup New Members
Goal in Context: A new customer wishes to register on to the system
Preconditions: The user does not have an existing account
Successful End Condition: The user registers a new account
Failed End Condition: The user fails to register a new account
Primary Actors: New Customers
Triggers: The new user’s details are entered into the system
Page 7 of 40
Version:1.0.0.0
MAIN FLOW:
Step Action:
 Personal details are entered by the user

 The system logs in the details
 The user creates a new account
EXTENSIONS:
 The database does not log in the new user’s information.
 A new account is not created.
3. Use Case Name: Change Password
Goal in Context: If user (Customer, Richard, Zinia, wishes to change his password
Preconditions: The user has an existing account
Successful End Condition: The user password to be updated.
Failed End Condition: The user fails to change password (If entered old password
wrong).
Primary Actors: Customer, Richard, Zinia, Other Authenticated Staff member.
Triggers: The user’s login (Changed Password) details are entered into the system
MAIN FLOW:
Step Action:
 Login details (Old Password, New password) are entered by the user
 The user changed his password
EXTENSIONS:
 The database does not validate the login information.
 The data remains invalidated.
4. Use Case Name: View Products
Goal in Context: A user wishes to view available products
Page 8 of 40
Version:1.0.0.0
Preconditions: The user has accessed the product information is available.
Successful End Condition: The user view the products
Failed End Condition: The user fails to view the products
Primary Actors: Customers
Secondary Actors: Product database.
Triggers: The user enters the product gallery
MAIN FLOW:
Step Action:
 The user clicks on the “Product gallery” Tab/Link

 The system redirects the user to the “view products” page
 The user browses the products
EXTENSIONS:
 The user cannot access the product catalogue.
5. Use Case Name: View Product Price
Goal in Context: A user wishes to view the price of a product
Preconditions: The user has accessed the products and their prices, are entered
Successful End Condition: The user views the product price
Failed End Condition: The user fails view the product price
Triggers: The user clicks on the product’s “price” link
MAIN FLOW:
Step Action:
 The user clicks on the “Price” Link

 The system redirects the user to the Price page
 The user views various rates on different versions of the item
Page 9 of 40
Version:1.0.0.0
EXTENSIONS:
 The system does not redirect the user to the prices page.
6. Use Case Name: Select Products
Goal in Context: A user wishes to select a particular product to add to the shopping cart
Preconditions: The product is available.
Successful End Condition: The user selects the desired product
Failed End Condition: The user fails to select the product
Triggers: The user clicks on the “add to shopping cart” link
MAIN FLOW:
Step Action:
 The user clicks on the “add to shopping cart” link

 The system logs his selection into a system array
 The user successfully selects the product for purchase
7. Use Case Name: Add Products
Goal in Context: Richard/Zinia needs to add new product information to catalogue.
Preconditions: The user has an administrative right to access the system.
Successful End Condition: The user adds the new product information to catalogue.
Failed End Condition: The user fails to add the new product information to catalogue.
Primary Actors: Richard/Zinia
Secondary Actors: Staff database; Product database;
Triggers: The Richard/Zinia adds the new product information on the product database.
MAIN FLOW:
Step Action:
Page 10 of 40
Version:1.0.0.0
 Richard/Zinia logs in using User ID

 Richard/Zinia proceeds to add new product information.
EXTENSIONS:
 The system rejects the updates.
 The changes are not saved.
8. Use Case Name: Update Products
Goal in Context: Richard/Zinia needs to update the product Information.
Successful End Condition: The user updates the product information.
Failed End Condition: The user fails to update the product information.
Secondary Actors: Staff database; Product database; Product_History database;
Triggers: The Richard/Zinia enters updated information on the product status.
MAIN FLOW:
Step Action:

 Richard/Zinia proceeds to make the required updates
EXTENSIONS:
9. Use Case Name: Update Prices
Goal in Context: Richard/Zinia needs to update prices of a product.
Successful End Condition: The user updates the price of a product.
Failed End Condition: The user fails to update the price of a product.
Page 11 of 40
Version:1.0.0.0
Secondary Actors: Login info database; Product database; Product_History database;
Triggers: The Richard/Zinia enters updated prices on the product status.
MAIN FLOW:
Step Action:
 Richard/Zinia proceeds to update the product price.
EXTENSIONS:
10. Use Case Name: Manage Staff Accounts
Goal in Context: Richard wishes to create supporting staff accounts to handle reply
feedback, email marketing and SMS marketing by accessing customer information.
Preconditions: Richard need support staff to handle the business operations.
Successful End Condition: Richard able to create and manage a staff account.
Failed End Condition: Richard fails to create and manage a staff account.
Primary Actors: Richard
Secondary Actors: Staff Database;
Triggers: Richard enters a query into the database to create and change the
authorization role of a support staff.
MAIN FLOW:
Step Action:
 Richard logs in with his User ID and Password.

 The system verifies his details.
 Richard creates and set the authorization limits for a staff.
EXTENSIONS:
 The database does not recognize the query
 The query is discarded.
Page 12 of 40
Version:1.0.0.0
11. Use Case Name: Send Feedback
Goal in Context: A customer wishes to send feedback on purchased products, if any
Preconditions: The customer has an existing account.
Successful End Condition: The user sends feedback.
Failed End Condition: The user fails to send feedback.
Secondary Actors: Login database, Feedback database.
Triggers: The customer clicks on the “Send Feedback” tab
MAIN FLOW:
Step Action:
 The user clicks on the “Send Feedback” tab

 The system verifies customer authentication and authorization
 The customer sends the feedback.
EXTENSIONS:
 The system does not recognize the customer authentication.
 The query is ignored.
12. Use Case Name: Make Payment
Goal in Context: A customer is given an option to pay for the transaction by credit card.
Preconditions: A transaction is made, i.e., products have been selected for purchase
Successful End Condition: The customer makes payment
Failed End Condition: The customer fails to make payment
Secondary Actors: Product and order database.
Triggers: The user selects the option to complete the transaction
MAIN FLOW:
Page 13 of 40
Version:1.0.0.0
Step Action:
 The user selects the option to make payment

 The system displays all current options
 The customer provides credit card information.
EXTENSIONS:
 The system does not provide any selections.
 The transaction is left incomplete.
13. Use Case Name: Cancel Order
Goal in Context: A customer wishes to cancel his order
Preconditions: There is an order placed or in process
Successful End Condition: The customer cancels his order
Failed End Condition: The customer fails to cancel his order
Triggers: The user clicks on the option to cancel his order
MAIN FLOW:
Step Action:
 The user clicks on the “Cancel Order” option

 The system asks for confirmation
 Upon the user’s confirmation, the order is cancelled
EXTENSIONS:
 The system does not allow the cancellation.
14. Use Case Name: Print/Mail Invoice
Page 14 of 40
Version:1.0.0.0
Goal in Context: An invoice is required for proof of purchase
Preconditions: A transaction has been completed
Successful End Condition: The invoice is printed / mailed.
Failed End Condition: The invoice is not printed / mailed.
Secondary Actors: Transaction processing system.
Triggers: The user completes a transaction
MAIN FLOW:
Step Action:
 The user finalizes a purchase

 The system processes the transaction
 The invoice is generated
EXTENSIONS:
 The system does not recognize the transaction as complete.
 The invoice is not printed.
15. Use Case Name: Place Order
Goal in Context: After generating an order invoice that info need to be kept into an
order database.
Successful End Condition: The order information stored in order database.
Failed End Condition: The order is not placed in order database.
Primary Actors: System
Secondary Actors: Transaction processing system; order database;
Triggers: The user completes a transaction
MAIN FLOW:
Step Action:
 The user finalizes a purchase
Page 15 of 40
Version:1.0.0.0
 The system processes the transaction

 The invoice is generated
 The order information stored in an order database.
EXTENSIONS:
 The system does not recognize the transaction as complete.
 The order is not placed.
16. Use Case Name: View Order_Info
Goal in Context: Richard/Zinia can able to access the order information
Successful End Condition: The order information accessed by Richard/Zinia.
Failed End Condition: Richard/Zinia is unable to access order information from order
database.
Primary Actors: Richard/Zinia, System
Secondary Actors: Transaction processing system; Order database;
Triggers: Richard / Zinia send a query to view orders information.
MAIN FLOW:
Step Action:
 Richard/Zinia logs in to the system with their user id and password.

 Check for order information (By clicking on view order_info).
 The order information displayed from an order database.
EXTENSIONS:
 The system does not recognize the requested transaction.
 The order information not displayed.
Page 16 of 40
Version:1.0.0.0
Use cases explained:
1. Log in to Website: This allows customers to log in to their personal accounts on

the website. They will interact with the front-end of the interface.
2. Log in by Employees: This allows employees to log in to their individual

accounts, according to their rank and access level. They will be able to operate
all features of the site, i.e., both the front and back ends.
3. Sign Up New Members: New members can sign up for an account with the site,
which, besides allowing on-site’s shopping functions, brings with it certain limited
access privileges.
4. Change Password: If customer wants to change his password and also

authenticated staff first login, system redirect them to change password form.
5. View Product Choice: This displays a list of the product or products selected.
6. View Products: Users can browse through the range of available products.
7. View Price of Products: Users can view the prices of the respective products.
8. Select Products: Users select the desired products from the available stock.
Page 17 of 40
Version:1.0.0.0
9. Update Products and Prices: A back-end feature that allows staff to update the
product stock levels, descriptions, etc, as well as the prices.
10. View shopping cart: Displays the final selection of the customer.
11. Make Payment: Let the customer make payment by providing credit card
information.
12. Enter Credit Card Details: A form to enter the details of the card selected.
13. Validate Card: A verification of the authenticity of the account by connecting with
the issuing bank’s server.
14. Cancel Order: Rescind an order already made.
15. Print/Mail Invoice: Print/mail out a hard copy of an invoice of the transaction.
16. Website Logout: Allows users to log out of the site, ending the current session.
17. Manage Staff Accounts: Allow Richard to create and manage staff accounts.
18. Send Feedback: Allow authenticated customer send feedback on purchased

products.
19. Reply Feedback: Allow authenticated and authorized staff member to give reply
for customer feedback.
20. Place Order: Allow the system to store the purchase details on order database.
21. Access Order Information: Allow Richard/ Zinia or authorized staff member to
track the orders details.
22. Access customer Information: Allow Richard/ Zinia or authorized staff member
to access the customer details for further operations.
23. Email Marketing: Allow authorized staff member to send product promotional
and offer news letters to existed customers.
24. SMS Marketing: Allow authorized staff member to send product promotional and
offer news letters to existed customers.
25. Track the Delivery status: Allow Richard/ Zinia or authorized staff member to
access the delivery status reports from courier service system (external).
26. Portal Logout: Allow all users of system to logout from portal.
Page 18 of 40
Version:1.0.0.0
2. Activity Diagrams
OBPSS – Customer Activity Diagram:
Page 19 of 40
Version:1.0.0.0
“3S1M” Team
Activity Diagram Online Beauty Products Shopping System (OBPSS)
Customer
Change Password
Website Login
Send Feedback
View Products
Select Products
View Prices
Like
Not Like
Access Shopping Cart
Make Payment Cancel Order
Provide Credit Info
Valid Invalid
Print/mail Invoice
Logoff
OBPSS – Richard/Zinia Activity Diagram:
Page 20 of 40
Version:1.0.0.0
“3S1M” Team
Richard/Zinia
Manage Staff Accounts

Website Login
Change Password
Add New_Product
Stock Information about Products
Update Product View Products
Update Price View Prices
Track Order Reports Track Delivery Information
Generate Oreder List Generate Delivery Report
Print Report
Logoff
Page 21 of 40
Version:1.0.0.0
“3S1M” Team
Zinia / Staff
Website Login
Change Password
Stock Information about Products
View Products
Reply to Feedback
View Prices
Access User Info Track Order Reports Track Delivery Information
Generate Oreder List

Generate Delivery Report
Send Promotionals
Print Report
No
Yes
Email / SMS
Logoff
Page 22 of 40
Version:1.0.0.0
3. Sequence Diagrams
“3S1M” Team Online Beauty Products Shopping System (OBPSS)
Sequence Diagram
Website Login Page View Products Page Access Order List Page Delivery Track Page
View()
View Products by category
View Prices
Update Products& Prices

Access of Orders List
Generate Order List Report

Track Delivery Status
Access of Order List()
Generate Delivery Status Reports
Track Delivery Status()
Page 23 of 40
Version:1.0.0.0
“3S1M” Team Online Beauty Products Shopping System (OBPSS)
Sequence Diagram
Access Shopping Cart Invoice Page

Website Login Page View Products Page
Page
View()
View Products by category
View Prices
Select Products
Selected Products()
Modify Selected Products List
Make Payment()
Generate Invoice Report
Page 24 of 40
Version:1.0.0.0
4. Class Diagram
Page 25 of 40
Version:1.0.0.0
OBPSS (ONLINE BEAUTY PRODUCTS SHOPPING SYSTEM

)
“3S1M” Team
ADDRESS CUSTOMER
-Add_ID : int -Cust_NO : int 1
-Street : string -Fname : string CreditInfo
-Suburb : string -Lname : string -Card_NO : long
-City : string -Password : char -Card_Type : string
-PostCode : string -Add_ID : int -Card_Name : string
-Phone : long -Card_NO : long -Exp_Date : string
-Email : string +Login() +SelectCardType()
+addAddress() +ChangePassword() +EnterCardInfo()
+DeliveryAdd() +Makepayment() +ValidateCard()
+Display() +display()
+AddnewCustomer()
+Get()
+Set()
1...*
CustomerOrder 1...* OrderItem

1...* -Order_NO : int -Order_NO : int
-Cust_NO : int -Prod_NO : int
-Add_ID(ShippingAdd) : int -Qty : int
-OrderPrice : float +AddItem()
STAFF -ShippingAmt : int 1 +getPrice()
-SalesTax : float +Display()
-Staff_ID : int
-Meth_Payment : string
-Name : string
-Password : char +addOrderRecord() DeliveryStatus
1 1...* 1
-Staff_Type : char 0...1 +ShippingAdd() -Delivery_NO : int
-Add_ID : int +CalculateOrderAmt( ) -ServiceProvider : string
+CalculateTaxAmt( ) -DeliveryType : string
+Login()
+CalculateSalesValue() -Delivery_Price : float
+ChangePassword()
+getOrderItem.Prod_NO() -DeliveryStatus : string
+AddStaff()
+UpdateStaff( ) -Order_NO : int
0...1 +DeleteStaff() +addDeliveryInfo()
+Display() +UpdateDeliveryStatus()
+Display()
0...1 PRODUCT ProductHistory
1
-Prod_NO : int -Prod_NO : int
-Prod_Name : string -EffectingDate : string
-Prod_Desc : string 0...* -Prod_Desc : string
0...* 1
-Unit_Price : float -Prod_Price : float
0...*
+AddProduct( ) +UpdatePrice()
+UpdateProductDesc() +Display()
FeedBack +DeleteProduct( ) +Process()
-FeedBack_NO : int +Display() +Get()
-FeedBack_Date : string +ViewProduct() +Set()
-Cust_NO : int +ViewPrice()
-Message : string
-Staff_NO : int 1
-ReplyMsg : string
0...* -ReplyMsg_Date : string
0...*
+InsertFeedBack()
+getDate() PromotionDelivery
+getCust_NO() PROMOTION
+UpdateReplyMsg() -Promotion_NO : int
-Promotion_NO -Delivery_Date : string
+UpdateStaff_NO() -Prod_NO
0...* -Delivery_Type : string
+Display() -Description 1 -Cust_NO : int
-PromotionType 0...*
+ForwardPromotions()
-PromotionDate
+getDate()
+addPromotion() +getCust_Email()
+UpdatePromotion() +getCust_PhoneNo()
+Process() +Process()
+Display() +display()
Page 26 of 40
Version:1.0.0.0
Appendix1: Updated Risk Register

Risk
Rank Risk Potential Response Likelihood Impact
Owner
1. Backup system at
regular intervals
2. Create multiple
backups, including
60%
periodic hard copy of
Loss of crucial Coder
1 all code High
data (Sunita)
Moderate
3. Use data recovery
safeguards like
Spinrite and
HandyRecovery
1. Salvage data
storage devices from
defective hardware
2. Keep inexpensive
replacements handy 55%
where possible. For
Hardware
example, in case of PM
3 defects or High
network hardware (Sanjeev)
malfunctions Moderate
failure, the team
should have a spare
56kbps modem to
maintain connectivity
until the problem is
rectified.
4 Analysis phase 1. Develop plan to PM High

may reveal that secure alternatives to (Sanjeev) 55%
securing core standard resources.
resources may For example, if AMD-
be difficult based ATI video-cards Moderate
(generally considered
the most stable and
powerful on the
market) are not
available, Nvidia might
be a viable alternative.
2. If alternatives are
not readily available,
scale down the parts
Page 27 of 40
Version:1.0.0.0
of the site that depend

on the missing
resource. For
example, a simpler
interface built through
C# might be necessary
if Microsoft Expression
Suite is not available.
1. Install spike-guards
or surge protectors to
protect data integrity
and power-sensitive
hardware such as 15%
Power outages
video-cards. PM
5 (Short-term to High
2. Wherever possible, (Sanjeev)
long-term)
have alternative power Low
solutions (like portable
generators) handy for
longer power outages.
1. Ensure members
are familiar with each
other’s duties
Unexpected 75%
2. Maintain copies of
leave or PM
6 work done on Moderate
indisposition of (Sanjeev)
members’ personal
team members High
computers, allowing
them to work from
home in an emergency
7 Limited technical 1. Seek guidance from Coder 90% Moderate

know-how may class instructors in (Sunita)
hamper the their areas of expertise
scope of the High
project 2. Make extensive use
of training manuals
and programming
guides, like Deitel’s,
O’Reilly’s and Jesse
Liberty’s
3. Consult online
resources like the
MSDN Library and
popular forums like C#
Corner and
CodeProject
Page 28 of 40
Version:1.0.0.0
1. Stay up-to-date with

the latest
documentation on
Software
official patches
updates and
100%
patches may
2. Visit Microsoft.com Coder
8 introduce Moderate
and ZDNet for news (Sunita)
features
on major upcoming Low
unfamiliar to
changes in the .NET
team
framework, Visual
Studios, etc.
1. Develop standard
database in SQL
Studios 2005; avoiding
2008 may be prudent 25%
Database
due to known DB
incompatibility or
9 compatibility issues. Analyst Moderate
inefficiency with
2. Develop backup (Sonia) Low
certain programs
OleDB database
model in Microsoft
Access.
1. Have an alternate
location with updated
system backups ready.
10%
Venue of
2. Follow standard
operations might PM
10 backup procedures Moderate
change or be (Sanjeev)
(asmentioned above) Low
inaccessible
so that no one location
alone has crucial
irreplaceable data.
1. Members assume
multiple roles; for
example, one member
may double as an
Scarcity of skilled analyst and a 85%
members may designer. PM
11 Low
affect quality of (Sanjeev)
project 2. Where multiple roles High
are not feasible, each
member may take on
part of the duties
12 Scheduling 1. Project schedule PM Low
Page 29 of 40
Version:1.0.0.0
must be laid out early

to spot and iron out
possible conflicts
2. Periods of
unavoidable (but
foreseeable) absence
can be compensated 50%
conflicts due to for by redistributing the
external workload for that (Sanjeev)
commitments period between the Moderate
remaining members.
Resources and work
hours so allotted in the
initial phases should
reduce, if not
completely eliminate,
the impact of such
schedule conflicts.
1. Ensure tasks have
50%
Milestones or adequate lag to avoid
deliverables may such contingencies. PM
13 Low
be missed or 2. Allow greater free (Sanjeev)
Moderate
delayed slack for tasks likely to
be delayed.
1. Regularly scheduled
meetings to acclimate
each member with
Lack of
their role 60%
coordination Analyst
2. In the initial phases,
14 within various (Mandeep Low
allow member tasks to
parts of the )
overlap to familiarize Moderate
project team
them with the other
members
Page 30 of 40
Version:1.0.0.0
Appendix 2: Updated Gantt Chart
Page 31 of 40
Version:1.0.0.0
Appendix 3: Cost Report
Page 32 of 40
Version:1.0.0.0
Page 33 of 40
Version:1.0.0.0
Page 34 of 40
Version:1.0.0.0
Group Contribution Form
The purpose of this form is to indicate to the lecturer the contribution each student has made to
the report. It is completed individually by all group members. This completion of this page will
influence the final marks that all members get on this report therefore not all members are
guaranteed the same mark rather a based on their overall effort. This section is for your benefit
and will help
Contribution Student Percentage Tasks worked on

ID contribution
to project
Student
Names
 Final draft
 Formatting and
Sanjeev 20071044 43.33% proofreading
 Risk Register
 Cost report
 Gantt chart
20090351 23.33%  Risk Register

Sunita
 Class Diagram
 Use Case Diagram
20091501 22.33%  Activity Diagram

Mandeep
 Sequence Diagram
Sonia 20091241 11.00%  Class Diagram
 Use Case Diagram
Total 100
Page 35 of 40
Version:1.0.0.0
Analysis Report Marking Sheet

Introduction
Mark
Introduction 0 ½ 1
Not included Limited or does not Includes a report on
discuss the report the company as well
and project fully as gives the overall
picture of the
analysis report
Background 0 ½ 1 2
Not included Limited does not Shows a good An excellent
give a good understanding of understanding of
understanding of the who the company is who the company is,
company and why they need a show understanding
website of business
requirements
Goal 0 ½ 1 2
Not included Limited or with major Shows a good goal An excellent goal
errors but not quite fully outlines the full
outlining the full scale of the project
scale project
Objectives 0 ½ 1 2
Not included Limited does not Shows good Lists the full range of
outline the full extent understanding of objectives related to
of the project objectives of the the project
project
Description of 0 ½ 1 2
Project Not included Very little is A good explanation An excellent
discussed about the of the project description of the
website only project giving insight
highlights discussed to the use case
diagrams and
processes of the
website
Mark: /9
Use Case Diagram

Mark
Use Case 0 ½ 1
Standard Not drawn Use cases have Use cases are
as per minor problems correctly draw
standard and are not as based on standard
specified as
standard
Important Actors 0 ½ 1
Not Only minor actors Includes
included included in design generalisation or
0 reflects the wide
range of possible
DOES NOT users
Important MEET 1 2 3 4
Functionality MINIMUM Limited Only minor Includes a wide An excellent use
AMOUNT functionalit functionality range of possible case diagram with
OF y identified identified functionality all functionality
ACTIVITIES described without
errors
Extend or include 0 ½ 1 2
relationships Not Correctly identified Includes a wide An excellent range
included extend or include range of possible of include and
relationships functionality extend
relationships
showing a good
understanding of
UML
Mark: /8
Page 36 of 40
Version:1.0.0.0
Use Case Descriptions

Mark
Use Cases ½ 1 2
Described All major use All uses cases An excellent range
cases are are fully of descriptions that
described described give detailed and
good understanding
of use cases
Pre and Post 0 ½ 1
Conditions Not included Pre and post Pre and post
conditions are conditions correctly
described with described
some errors
Basic Flow 0 ½ 1 2
0 Not included The flow of the The flow of the use An excellent and
use case is case is described detailed description
DOES NOT described with and appropriate of the flow of the
MEET some error use case with
MINIMUM enough information
AMOUNT to assist in the
OF drawing of the
ACTIVITIES activity diagram
Alternate Flow 0 ½ 1
Not included Some The alternate flow
appropriate of the use case is
alternate flows included where
missing or relevant and is
have some correct and
errors appropriate
Trigger 0 ½ 1
Not included Triggers are Triggers are
described with correctly described
some errors or and relevant
some missing
Mark: /7
Activity Diagram
Mark
Activity drawn to 0 0 ½ 1
standard DOES NOT Not drawn Activity Activity diagrams
MEET as per diagrams have are correctly draw
MINIMUM standard minor problems based on standard
AMOUNT and are not as
OF specified as
ACTIVITIES standard
Different activity 0 ½
diagrams Activity Activity
diagrams diagrams are
are not significantly
significantly different to
different each other
Effective and 0 1 2
useful diagrams Activity Activity Activity diagrams
diagrams diagrams are are detailed and
are incorrect correct and show a good insight
show a wide to the methods of
range of the activities
options
Understandable 0 ½
Activity Activity
diagrams diagrams are
are well laid out
Page 37 of 40
Version:1.0.0.0
incorrectly and easy to
drawn or understand
hard to read
Decision points 0 ½
Conditions Conditions
guards are guards are
not included correct and
or are not understandable
self
explanatory
Mark: /4.5
Sequence
Mark
Sequence drawn 0 ½ 1
to standard Not drawn diagrams have diagrams are
as per minor problems correctly draw
standard and are not as based on standard
specified as
standard
Different 0 ½
Sequence Sequence Sequence
diagrams diagrams diagrams are
are not significantly
significantly different to
different each other (if
applicable)
Effective and 0 1 2 3
useful diagrams Sequence Sequence Sequence diagrams Excellent
0
diagrams diagrams are are detailed and sequence
DOES NOT
are incorrect correct and show a good insight diagrams with no
MEET
show a wide to the sequence of errors, and shows
MINIMUM
range of activities an excellent
AMOUNT OF
options understanding the
SEQUENCES
sequence of
activities
Understandable 0 ½
Sequence Sequence
diagrams diagrams well
are laid out and
incorrectly easy to
drawn or understand
hard to read
Messages 0 ½ 1 2
Not included The messages The messages stem The messages are
are missing or from the class relevant, clear and
incorrectly diagram and are understandable
assigned correctly linked to and make sense
the correct object
Mark: /7
Class Diagram
Mark
Diagram Standard 0 ½ 1 2
Not drawn as per The Class Diagram The Class Diagram An excellently laid
standard have minor is correctly draw put class diagram
problems and are based on standard with all necessary
not as specified as elements
standard
Properties 0 ½ 1 2
Not included Incorrect or missing Properties are A full range of
properties related to correct and fully properties are shown
class define each class and are correct and
with just a few cover all items that
mistakes will be in the
database
Classes 0 1 2 3
Page 38 of 40
Version:1.0.0.0
Not included Incorrect or missing Classes are correct A detailed list of
classes and fully define the classes showing
major classes for the insight to all possible
project entities in the project
Methods 0 ½ 1 2
Not included Incorrect or missing Methods are correct An excellent range
methods related to and fully define each of methods that are
class class with just a few fully covered and
mistakes correctly assigned
and understandable
Multiplicity and 0 ½ 1 2
link Not included Incorrect or missing The Multiplicity of Multiplicity is correct
multiplicity related to classes is correct and shows direction
class and fully define the and are named to
links to each class aid in readability
Mark: /11
Updated Risk Register

Mark
Risk Register ½ 1 2
Risk are listed but Risks are An excellent range
not all relate to related to of risks are shown
the project or the project overall relating to the
analysis phase but not related project and analysis
to the analysis
phase
½ 1
Risks listed are Risks are
- 7 marks not relevant or no relevant and
Is the longer an issue current
same as ½ 1 2
PDD Risks are not Risks are fully Risks are
described in full understandable understandable and
and realistic reflect the rank of
the risk
½ 1 2
Responses are Responses are An excellent range
limited or do not correct and of responses are
fully relate to the relate to the given that are
risk risk practical and
understandable
Mark: /7
Updated Gantt Chart
Mark
Gantt Chart - 5 marks 0 1 1
Is the same as PDD Gantt chart does not give Tasks are limited A full range of
sufficient list of tasks tasks are shown
0 ½ 1
Milestones not included at Some problems Milestones are
end of phases with milestones are correct and
shown applicable
0 ½
Milestones do not reflect Milestones reflect
correct date of submission correct date of
submission
0 ½
Project start date does not Correct start date is
reflect the correct start shown
date of last semester
0 ½ 1
Resources are not Resources have Resources are
assigned or are incorrect some errors correct and fully
outline all
Page 39 of 40
Version:1.0.0.0
possible
resources
0 ½ 1
Not all tasks are linked Tasks are linked Links are
but only Finish to appropriate and
start relationships wide ranging
added
Mark: /5
Updated Cost Report

Mark Comment
Cost Report 0 ½
Not included Cost Report is
included
Mark: /0.5
Professional Report
Mark Comment
Professional 0 1 3
document The report is not The report is not The report is
professionally professionally professionally
written with many written with minor written with no
spelling and spelling and spelling and
grammar errors grammar errors grammar errors
Mark: 3/3
Total out of 62:
Page 40 of 40

OBPSS Analysis

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OBPSS Analysis

Uploaded by

Copyright:

Available Formats

Online Beauty Products Shopping System –

Online Beauty Products Shopping System

“3S1M” Team Members

SNO Content Page No

1 Project Initiation Document History 3

Appendix 1: Updated Risk Register 26

1. Project Initiation Document History

1.1 Document Location

1.2 Revision History

Date Version Change Author Requested By

Name Signature Title Date of Issue Version

Mr. John Paynter Management Board 22 August 2009 1.1

Name Title Date of Issue Version

Mr. John Paynter Management Board 22 August 2009 1.1

Zinaz Beauty Salon is a privately-owned company specializing in beauty services and

nationwide, Zinaz hopes to broaden its entrepreneurial scope while providing a

1.1. Use Case Diagram

OBPSS(ONLINE BEAUTY PRODUCTS SHOPPING SYSTEM )

-End2 -End43 «extends»

4.2 Use Case Descriptions

1. Use Case Name: Login to Website

Goal in Context: A user (Customer or Richard/Zinia or Other Authenticated Staff

Preconditions: The user has an existing account

Successful End Condition: The user logs in.

Failed End Condition: The user fails to login.

Secondary Actors: Login info database.

 Log in details are entered by the user

2. Use Case Name: Signup New Members

Goal in Context: A new customer wishes to register on to the system

Preconditions: The user does not have an existing account

Successful End Condition: The user registers a new account

Failed End Condition: The user fails to register a new account

Primary Actors: New Customers

Secondary Actors: Login info database.

 Personal details are entered by the user

3. Use Case Name: Change Password

Preconditions: The user has an existing account

Successful End Condition: The user password to be updated.

Primary Actors: Customer, Richard, Zinia, Other Authenticated Staff member.

Secondary Actors: Login info database.

4. Use Case Name: View Products

Goal in Context: A user wishes to view available products

Preconditions: The user has accessed the product information is available.

Successful End Condition: The user view the products

Failed End Condition: The user fails to view the products

Primary Actors: Customers

Secondary Actors: Product database.

Triggers: The user enters the product gallery

 The user clicks on the “Product gallery” Tab/Link

5. Use Case Name: View Product Price

Goal in Context: A user wishes to view the price of a product

Successful End Condition: The user views the product price

Primary Actors: Customers

Secondary Actors: Product database.

Triggers: The user clicks on the product’s “price” link

 The user clicks on the “Price” Link

6. Use Case Name: Select Products

Preconditions: The product is available.

Successful End Condition: The user selects the desired product

Failed End Condition: The user fails to select the product

Primary Actors: Customers

Secondary Actors: Product database.

Triggers: The user clicks on the “add to shopping cart” link