Justification of Proposed Solution
The DPP Choice would be the most intelligent Decision. It is much easier to insert Pictures and to type in Text than a Word-Processor however a DPP interface is much more confusing than the Interface for a Word-Processing Program. Making the Publications by Hand is far too unprofessional and could be very poorly presented. This totally rules it out.
The DPP also allows the Publications have several Wizards making it so easy to understand and use the DPP. Word-Processing Programs tend to have more typing orientated Wizards e.g. to type a Letter.
The DPP also allows flexibility as to what can be done. You can make a Program using both sides of the Page just by telling the DPP that’s what you want. However with a Word-Processor it needs to be done manually i.e. take out the Paper and put it into the Printer reverse side up.
User Requirements
- The Program must include the Address and Opening Times of the Store.
- The Information Card must not be bigger than a standard Pocket Size.
- The Cards should be printed an A4 Sheet.
- The Program should not have Text smaller than 12pt.
- The Program should not have more than 80 words on each Page.
- The Ticket must have a Seat Number.
- The Banner must have Address, Opening Times and Ticket Price printed on.
- On the Information Card the Details have to be printed in no less than 10pt.
- The Publications must have the Logo on them in the same place.
- The Banner should not be longer than 6 Sheets long.
- The Ticket should feature a Thank-you Message to the Buyer.
Analyse
Appropriate Software and Hardware
Microsoft Publisher is probably the most popular Desktop Publishing Programme; however there are several different Desktop Publisher Packages and each of them have several different advantages that they can be used for.
Microsoft Publisher is works best when used with Microsoft Windows and other Windows Applications
Microsoft Windows XP will be the most extravagant Operating System we can find at a reasonable Price. Microsoft Windows XP includes Microsoft Publisher XP. Microsoft Publisher XP has a huge variety of Functions compared to other DPPs. Publisher XP is also the easiest to use as the Interface is very friendly. Another Program that could be used is Broderbund Print Shop Deluxe. This is also a DPP but this DPP is meant more for making Birthday Cards, Greeting Cards etc Microsoft Publisher XP is more formal than Print Shop Deluxe and would be the obvious in response to Steven’s needs.
Pictures will need to be manipulated to be put into the Publications and a Paint Package will be needed for this. There are several Paint Packages that could be used. All the Paint Packages available do the same thing so it won’t make a difference which Paint Package is chosen. Microsoft Paint comes free with Microsoft Windows XP. This makes this makes it very easy to get Microsoft Paint as once we have Microsoft Windows installed Microsoft Paint will be installed. Also Microsoft Paint interacts very easily with Microsoft Publisher and uses the same Picture File Types.
A Device will be needed to get Pictures of Goods within the Shop. A Scanner could be used or a Web Camera could be used to take Pictures of the Goods. A Scanner won’t be very useful in this Situation as to scan you need to already have a Picture. A Web Cam is very unsuitable as it doesn’t have enough pixels to allow a good, viewable Image to be seen. A Digital Camera would be the best Option as it has a huge range you can buy and even the cheapest Digital Camera would give you a good viewable Image.
A basic CPU will be needed and this CPU would have to be of a reasonable Speed. A Keyboard, Monitor and Mouse will be needed to construct the System. A Laser Printer will be needed to print out the Publication. The Laser Printer will produce a very good Picture and is also very fast. It is however expensive to purchase a LaserJet Printer and the Ink used is very expensive compared to other Ink Cartridges available.
Data required and its source
The Data required will be Graphics: Pictures of the Goods within the Store. This will be used for mainly to put on the Cards, Banners and the Programme. Graphics will bring in the Audience and will prove the deciding Factor to, potential Buyers of the Product.
The Graphics will be obtained from Pictures taken by the Digital Camera. The Pictures taken were of the Goods within the Store.
Text Data will also be required as it will provide the Information needed to find the Store, know its Opening Times, to know Ticketing Information etc. The Text Data will come from several Sources including Steven himself. The Text is the most important Data Type needed in the Publication. All the Data needed, will be taken from Steven.
Data manipulation
The Graphical Data will be manipulated in Microsoft Paint to fit the needs in the Publication. These will be Pictures of Goods within the Store which will be implemented into the intended Publications. The Pictures will be fitted into a Picture Frame which will be predefined before the Picture is obtained. A Logo for the Store will be scanned in and manipulated and copied unto each Publication creating a Uniform Look. The Logo will also be fitted into a Frame which will already be implemented into the Publication.
The Text Data that Steven will inform me to write into the Publication will be typed up and if necessary linked Text Boxes will be used. The Text will be typed up using different Fonts for each Piece of Writing.
Numerical Data will be used to define Dates, Times and Prices. The Font used will be very different in each Situation.
Flow of data
Most of the Data that will be needed will come from Steven. Steven will provide the Information which will be put into the Publications; however some of my own Judgement will be needed if there is a small Problem concerning the Publication or an Error by Steven which I can rectify. Using the Data Steven has provided I will make the Publications as close to his Specifications as possible. Then a Copy of the Publications will be sent back to Steven to evaluate. It will then be returned to me with any Corrections necessary being highlighted by Steven.
Output
All the Publications will be printed out using a Laser Printer; however each will have a different Format therefore require a different Printer Setting. All the Publications will be created using Microsoft Publisher. The Ticket will be printed on A6 Landscape Paper. The Paper used will be ordinary white Printing Paper. The Ticket will be colour printed and then colour printed as the Ticket has to be of a good Quality to reflect the riches of Steven. Colour printed Tickets will also look more attractive to the Buyers.
The Banner will be printed on more Quality Paper as less Copies will be made therefore it won’t be that expensive. The Quality will allow the colours to be more vibrant and will allow the Adverts to be more productive.
The Programme will be printed on normal A4 Paper and will be photo-copied in colour. These programs will be given to all the entrants and will have a lot of Information on them that’s why it will be A4 Size.
Backup/Security strategy
Every Week the System will be checked for Viruses to stop anything happening to the Publications on the Computer.
Design
I am going to design a Ticket for Entry to the Event. This Ticket will have be landscape on A6 size Paper but will also require a good Design to be printed on it. The Banner will be an A3 size and will be printed in colour. Glossy Paper will be used so it will appear more colourful than the Ticket or the Program. The Program will also be printed in colour. The Banner will be printed on glossy paper in colour and will include Pictures of goods gained by the Digital Camera. The Banner will also have Opening times and Party Information.
Breakdown of Solution into Subtasks
Make a detailed list of subtasks which will help you to complete the entire system to the exact specification you laid out in your user requirements.
Explain how you will meet each requirement you set out to fulfil.
Test Plan
A FULL and effective test plan should be drawn up which tests every detail of your system. You will have had several things go wrong in designing your system so write them down and include them as tests which you can later on, describe how you corrected them for extra marks.
Show what you will test, and give the test data that you will use to test it. Explain what your expected results should be.
Where you have used validation, verification or added default values, you should test this to its extreme.
Remember: The aim of testing is try your hardest to make your system go wrong!
Implementation
Changes to Final Design
Make a detailed note of any changes you made to your final designs when you developed the system.
Explain why these changes were necessary.
You are bound to have made some changes.
On the Business Card I added a Picture in the Top to make it more interesting before it was just empty Space. The Picture will be of a Bag and the Bag looks good printed in black and white
Evidence of Implementation
Print out a copy of everything that you have made. Include all slides, tables, forms, reports, queries, menu screens, formulae, worksheets, leaflets, posters depending on the projects you are doing.
Annotate the printouts to show the sequence of development, any errors you found and corrected, and any improvements you have already identified.
You could include some earlier drafts of whatever you are doing to show the sequence of development.
You will also need to explain any complicated or clever things that you have added. These may not be obvious just by looking at the printouts.
Test Results
Your test results should include a detailed comparison between the expected result and the actual result.
In addition to this you need to include a screenshot as evidence that the test was carried out. The screenshot can then be annotated to further explain anything.
Evidence of Testing
Publisher Only: Instead of showing screenshots, you can actually print out your publications and annotate these.
Error Correction
You WILL have some errors appear in your testing. It is very unlikely that any system will work perfectly first time.
You must show screenshot evidence of these errors occurring, an explanation of how you fixed them and more evidence of you re-testing to check that they work after correction.
Evaluation
Do not let yourself down by rushing this last section. It is worth 12½ % of your mark and could be the difference between 2 grades.
Evaluation of User Requirements
Refer to each objective that you wrote in your Identify section and critically evaluate each one separately in a new paragraph. A few lines for each is usually sufficient unless you have something of real discussion for that objective. You do not have to prove that you met all of your objectives or that you have produced the most perfect system but you do need to give a detailed evaluation of how well you met that requirements why you think so or not.
User Feedback
Your user’s feedback has to useful, critical comments with some of their suggestions for improvement. This could be in the form of a questionnaire that you compile a letter or some quotes from an interview which you conducted with them.
Suggestions for Further Improvement
You need to come up with some of you own suggestions for improvement and discuss how these would improve the current system if you actually had the opportunity to make them.
You also need to take the user’s comments for improvement into account as well and discuss how you would implement these if you had the chance.
