Scenario
A system is required that allows Aston students to maintain an account for purchasing books from an Aston book store. The account can be topped up by cash payment to stores. Books are identified by their ISBN and categorised by its type (e.g. Computing, Business, Multimedia, Electronic, Electrical, Mathematic, Languages, etc). The books in the store are associated with the book category. One book can appear in more than one category (for example, a book can be in both Computing and Business category). Each book has its price and quantity in stock. Students can access a web-based catalogue of these items, and add any book to their shopping basket. When an item is added to the basket, the quantity of that item in stock should be reduced accordingly. When they wish to complete the purchased they must visit stores where they may collect these items - provided there is sufficient money in the student's account. The store staff who manage this system also use a web-based interface. They can add a book in the system and associate it to appropriate categories. When students visit the store, they can view the orders in the students' shopping basket and completes the purchase.
Requirements (S1, S3 T2 and T4)
Below is a list of functionalities of the system. You are required to implement FOUR of the requirements: S1, S3, T2 and T4.
Students using this system can:
S1. View all books in the catalogue, including the amount in stock.
S3. Add an item to their shopping basket.
S4. Remove an item from their shopping basket.
S5. View their basket and account balance.
Store staff in stores can:
T2. View a student's basket and account balance.
T4. Complete a purchase by providing a given student with the items in their shopping basket and the system will deduct the total from their account.
To reduce the need for repetitive coding, you are required to implement FOUR of these requirements: S1, S3, T2 and T4, though you can implement more if you wish as part of the Stretcher. You need to design the database used for this system. You should populate the tables (manually or automatically) fill these tables with a dozen or so entries for testing purposes.
Your implementation must be in PHP, HTML and MySQL. You are free to choose whether to use object-oriented programming or other relevant techniques. If you choose to develop your system on your own computer, make sure your software is compatible with that on our remote webserver. Your web server should be www..eas-cs2410-1415.aston.ac.uk (please check the email ISA sent to you), and allow at least 24 hours to transfer it across. If you want to download the software, you are suggested to download wampserver or xampp which includes Apache, PHP, MySQL etc in one package.
You need include a suitable interface; for example an opening page which contains a link to a student page and a link to the staff's page, etc. Note that the user interface must be easy to use.
Your short report includes the following:
oA summary of the architecture of your system (not longer than 2 pages). The report should summarise the structure of your implementation, and in particular which source code files I must read to find where ?you have made use of sessions and multi-table select or join query.
oAny assumption of using the system should also be described.
oA HTTP link which links to the entry page of your website, normally index.html
oDetails of at least two type users which can be used to assess your system including one student user and one staff user. If password is needed to login in the system, this should be provided clearly in your report.
oDo not include screen-shots, UML diagrams, nor any other graphical material. ?Your submission must be your own effort. Copying and sharing work is forbidden. If you are found to have copied or shared part or all of your submission your mark may be reduced or set to zero (or worse).
Attachment:- Archive.zip