Project Scenario

You are employed by Uptown IT’s Creative Department as a Web Developer. Your manager has given you a new project to design and develop. The client is The Mobile Hour. The company specialises in selling top brand mobile phones online. The Mobile Hour had a website developed by a friend a few years back but it needs to be replaced. The design is not appealing to today’s customers; it also lacks functionality and security. Your task is to design and develop a completely new website. Security and an attractive design are high on the client’s list of expectations.

Project requirements are as follows:

• Develop a responsive website (multiple devices)

• Integrate a database with the website

• Provide admin users access to manage the product by being able to:

• Securely log in to admin area

• Add new admin users (only manager can create new user)

• Modify user accounts

• Add new products

• Update products

• Delete products

• Keep track of stock on hand

• Keep track of changes made. A change log to identify the what, when and who made the changes.

In terms of display reports or outputs from the database, the Client has outlined the following:

• Display all mobile phones

• Display by brand

• Display by price

• Display stock on hand by product and by brand

• Display current users

• Display change log:

 by product

 by date and date range

 by user

A copy of the database structure in form of an entity relationship diagram (ERD) is presented below. You can add to, modify and improve the database structure as required to suit the project but you cannot remove data that is currently being stored.  

The product and the feature tables have a cardinality ration of one-to-one. Meaning that for each entry into the product table it will be a corresponding one in the feature table. 

ERD for the Mobile Hour

PART 1 - Analyse documentation provided and documenting project requirements

In this part you need to analyse the project documentation provided and extract and document the requirements for the website project. Seek clarification from your teacher/assessor as required.

Task 1 Conversation Log

1.1 Use the following conversation log to keep track all interactions with your manager and other stakeholders. Oral interactions are essential to this project as you need to maintain continuous contact with your manager, the user groups and other relevant personnel.

Task 2 Documenting web application requirements

Carefully read the case study or scenario provided and document the website project requirements. It is expected that you provide precise, formal, complete and technical information and descriptions in your answer. All sections must be completed. Write as much information as necessary inside each cell. It is not expected that you write in paragraphs in most sections but a precise and exhaustive listing is expected - it is presented as table for efficiency.

Project <<name>>

1.2 PROJECT DETAILS

Client details:

Developer details: Uptown IT - Web Development Department 42 Technology Avenue, Brisbane 4000

                                        Contact Person: Alan Turing, M. 0102 123 123 alan.turing@data.com 

Purpose/Goal:

Objectives:

Client expectations:

Legislative standards:

Project duration:

Other: Please list

1.3 REQUIREMENTS

Hardware

Hardware platform:

Software

OS:

Web server:

Frameworks (front/back end):

Languages:

APIs:

Database server:

DBMS:

Other: Please list

1.4 Functionality

Website functionality:

1.5 Database Integration

Connection to database server requirements:

Database functionality:

User data input requirements:

Data storage requirements:

Other: Please list

1.6 User interface

User characteristics:

User needs:

Design principles:

Navigation:

Accessibility features:

Devices supported:

Other: Please list

1.7 Security procedures

Authentication:

Injection:

Protocols:

Other: Please list

Task 3 Creating a requirements checklist

1.8 Before you proceed with the project, review the requirements you have documented and organise a conversation with your manage to go over any concerns or issues you may still have. Update Conversation Log.

1.9 Once the website requirements have been documented (Task 1, above), you can use the individual requirements in each section to create an Acceptance Requirements Checklist. This checklist will be used in (Part 4 – 4.1) at the completion of the project to test that all requirements specified have been implemented. You can use the template below to create the checklist. Make sure that you list all requirements.