Tuesday, 24 April 2012
Feasibility Analysis & Research on existing system
§
Economic Analysis
Budget
demand: little
§
Technical Analysis
§
Project size: small
Scale: storage and processing
§
Familiarity with the application area and
technologies: high
·
Developers can be those who are skillful at PHP & MYSQL
·
PHP is a well-known
programming language for web application, and so does MYSQL (database
management)
o
Degree of structure of the system
requirements: highly structured
A
well-defined technical problem
§ Good features we want to
adopt:
o
eBooks Help:
this feature to help customer can have a clear understanding about how to buy
an eBook. It gives a lot of detail information and useful instructions relates
to buying an eBook for customers who are
not clear
o
Reserve
Online & Collect Instore: the
ease of shopping online with the convenience of large network of stores. This
creates a simple way to shop and fast to receive the item.
o
Shipping: an
important feature to attract customer to the store
§ Bad features I want to avoid:
Corporate
account: this feature seems to quite unclear. In addition, this feature maybe
not useful and practical
§ Good features I want to adopt
o Book Points: “Earn Book Points every time you shop with the
Book People and you could soon be trading them in for another one of our
brilliant books”. This will increase the number of sales and store will have more regular
customers.
o
Book blog::
is where books and
people meet, check back for all the latest news and events related to books so
people can always update information.
§
Bad features
I want to avoid:
Points
Passport: In my opinion, this feature should not be included. It is nearly the
same as “Book point” feature thus not need to include this feature.
§ Good features I want to adopt:
o
Wishlist:
this list help customer add the items to their favorite list for later purpose
if they do not want to buy it immediately.
o
Search: This
is one of the most important features I want to adopt. It is to make easier in
finding items. Customer can find what they want in an easy way and take not
much time
§ Bad features I want to avoid:
o
Sell: this
function if not be managed carefully, it can be used for cheating purpose
o
International
trading: contain a lot of threats such as problem in shipping items, fake items
Work Breakdown Structure
Work
Breakdown Structure for Online Bookshop Website
Prepared by: Tran Anh Duc Date: 06/01/2012
1.0 Initiating
1.1
Select
project manager
1.2
Form
project plan
1.3 Develop project charter
2.0
Planning
2.1
Develop scope statement
2.2
Create WBS
2.3
Develop and refine other plan
3.0
Executing
3.1
Concept
3.1.1
Define requirements
3.1.1.1
Define user requirement
3.1.1.2
Define content requirements
3.1.1.3
Define system requirements
3.1.1.4
Define server requirements
3.1.2
Define specific functionality
3.1.3
Define risks and risk management
3.1.4
Develop project plan
3.1.5
Brief Web development team
3.2
Website Design
3.3
Website Development
3.4
Testing
4.0
Monitoring and controlling
5.0
Closing
5.1 Develop installation guide
5.2
Develop user guide
Scope Statement
Scope Statement
|
Project
Title: Online Bookshop Website
Date:
06/01/2012 Prepared
by: Nguyen Thi Tho
|
|
Project
Justification:
The project
will require purchasing a domain and a Linux server to support hosting the
bookshop website as well as Web, network, database, application functions.
PHP Yii framework will be used to provide fast performance and high response
rate for the website. If there are any changes to the server requirements, a
detailed description of the changes must be submitted to the project manager
for approval. The client must approve a detailed plan describing the server
requirements and their location at least 1 week before installation.
.
|
|
Product
Characteristics and Requirements:
1.
Website
must suffer from at least 2000 people request at the same time
2.
Website
must support ONE-MANY relationship between Book category and Book
3.
Website
must support shopping cart
4.
A
high-security authentication from the administration section is highly
required
5.
Frontend
design need to be as simple as possible
|
|
Summary of
Project Deliverables
Project
management-related deliverables: business
case, charter, team contract, scope statement, WBS, schedule, cost baseline,
status reports, final project presentation, final project report,
lessons-learned report, and any other documents required to manage the
project.
Product-related
deliverables: research reports, user guide,
software code, database file
|
|
Project
Success Criteria:
§
Construct the Online Bookshop website completely
with all planned functions by the end of May 2012
§
The website must meet all written specifications, and business rule, be thoroughly tested
§
Employee work disruptions will be minimal
§
Produce necessary deliverables
§
Manage project risks efficiently
§
Assigning tasks to suitable team members
§
Reviewing project regularly
|
Communication Channel
|
Stakeholders
|
Document Name
|
Document Format
|
Contact Person
|
Due
|
|
Project Manager
|
Monthly status report
|
Formal paper – based report
|
Tran Anh Duc
|
First of month
|
|
Team Lead
|
Weekly as
required report
|
Formal
paper – based report
|
Dang Van
Nghia
|
First of
month
|
|
Team Member
|
Weekly status report
|
Email
|
Nguyen Thi Tho
|
First of month
|
|
Team Member
|
Weekly
status report
|
Email
|
Le Manh
Tuong
|
First of
month
|
Subscribe to:
Posts (Atom)



