MCOMD1APD Application Development

Requirement Specification:

Scenario

The University of Sarre Publishing Corporation (UK Ltd) publishes books authored by staff at the University. These are then sold to distributors to sell to the public. The current stock list of for five titles by three different authors. There are three different distributors. Each book has a title and a cost to the distributor.

The books and authors are as follows:

The distributors are as follows:

When a distributor requests an order, then this will update the total sale of books of each title to that distributor and a total price for THIS order will be presented in a Message Box. Sales cannot occur if there is no or insufficient stock of an item being ordered.

Three reports are required.

• After each sale the stock needs to be updated to reflect the new stock levels at the publisher (NB there is no way to add more stock in this version of the system).
• On demand, a list of total sales by distributor. For each distributor, giving the name of the distributor and the sales by each title. There are bonus marks for sorting this from highest total sales to lowest total sales, but the ordering of the books remaining the same for each distributor.
• On demand, a list of total sales per author, taking into account that some authors have written more than one book. For each author giving the name of the author and the total sales. This to be ordered from lowest sale to highest sales per author.

Task Description

Design, code, and test, a suitable software system implemented in C# to implement the system above.

You have been given the interface for the system in the C# project ‘SarrePublishing’. The interface must not to be modified in any way.

• Your main aim is to design and implement code, and test your solution. You MUST NOT use a database to store the sales, but should use a 2D array, if possible. Your system should be as generic as possible so that should the number of titles, authors or distributors be extended, then your code may largely remain the same and does not need major alteration. Your coding should help prevent errors by checking input values are valid.

Use the template of testing in Appendix B to

1. Complete the test cases in Appendix B
2. Create FIVE more tests of your own – which should be designed to test one small area of the system in as complete a fashion as possible. You must not test the Stock Update part of the system. Document these tests in the same manner as the given tests, ensuring you are accurate in your input specification. You are marked for quality of the tests and accuracy of recording results. Even if your program does not work, you can still score marks.

You should look at the Mark Scheme, and the Mark Breakdown (Appendix C) to see where to focus your efforts and how to maximise your marks.

SUBMISSION

1. You will need to put your testing document (completed) into the top level folder of your project folder.
2. Ensure that ALL the files needed to view and run your solution are in this folder and none are stored elsewhere on your drives.
3. Compress this entire folder into a zip format file using either 7zip or windows compression. Do not use any other compression algorithm than zip!
4. Submit this zipped folder of the entire project and associated testing to the Blackboard submission area.