SWE5206- System Analysis and Design
Module Number and Name: SWE5206- System Analysis and Design
Assessment Number, Type (and weighting): 1, Coursework (70%)
Assignment Title: Investigate and Analyse a Bakery Management System.
Assessment Description: Case Study
Assessment Author: Ms. Ibtisam Mogul & Ms. Renuka Nyayadhish
Submission Deadline: 12/12/22
Learning Outcomes
LO1: Apply a structured method to the analysis and design of an information system
LO2: Investigate, document and understand an information system
LO3: Analyse an information system defining requirements, problems and solutions
LO4: Apply analysis and design methods to varied scenarios
LO5: Appraise the underpinning principles of structured methods
Assignment Brief
The attached case study relates to BlueBerry Bakery Ltd who are currently operating computer
systems to support the operation of the company's bakery business in Bolton. There are some
difficulties with the operation of the order processing system and the information that it provides for
management control.
In this assignment you will play the role of a computer Solutions Company contracted to carry out an
investigation into the order processing function at the bakery.
Objectives
1. To investigate the existing order processing system and its interfaces to the bakeries and the
existing computerised accounting system.
2. To define the existing order processing system, the associated problems and new information
requirements.
Students will work in teams during the investigation, but each team member will be responsible for a
detailed analysis of a specific area of the system.
Page 1 of 9
SWE5206- System Analysis and Design
BlueBerry Bakery Ltd – Case study
Overview
BlueBerry Bakery Ltd. is a quality bakery that produces a variety of cakes and bread as well as
speciality and celebration cakes. It is a family firm that has been in existence for 75 years. The Head
Office is located in Maude Street, Bolton, and consists of two floors; an upstairs bakery is used for the
production of cakes and a downstairs bakery for the production of bread. Creaming and packaging of
cakes takes place in the upstairs bakery and the goods are counted and prepared for delivery in an
adjoining room to the downstairs bakery.
The company owns many shops and 60% of production is retail. The main source of competition on
the retail side is from the main supermarkets, particularly those with an in-store bakery, and from the
Hampsons, Greggs and Greenhalgh shops. The remaining 40% of production is wholesale. Both the
shops and wholesale customers are situated in and around Bolton, covering a large area of about 30
miles radius.
BlueBerry’s employs 49 staff full-time and 67 part-time staff. Last year's turnover was £1.8m and it is
expected that sales will continue to increase in all the shops.
Use of Computers
For the past three years, the company has been using a software package called Cakebake for order
processing, invoicing and production lists. The package runs on a Windows based operating system
with a printer which is situated in the Front Sales Office. The package is rudimentary and slow in use.
It does not provide all the information that is needed and cannot handle more than one order per day
per customer.
About two years ago the managing director installed a PC and printer with packaged software for
business and financial accounting and company payroll. The computer is situated in the managing
director's office where it is operated by the accounts clerk. The accounting software is not being fully
utilised because so much information about the company's operations is currently unobtainable.
The PC is under the personal control of the managing director. Routine transactions are entered by
the accounts clerk, but the managing director operates the computer to obtain the company financial
information. Through dealings with the suppliers of computer systems and by use of the PC, the
managing director has become quite knowledgeable about computing. The staff in the front sales
office at BlueBerry’s are competent in using the PC. None of the other staff at BlueBerry’s currently
have any need to use the computers.
Order Processing
The bakery is a production environment with a 24-hour cycle. Orders are initiated by the front sales
office staff, who telephone the wholesale customers and BlueBerry’s shops during the morning asking
for their orders, which are entered into the computer. By early afternoon, invoices, delivery notes and
the production lists are output by the computer and the front sales’ office staff distribute them. Once
the production lists are received in the bakeries, cake and bread production commences. Starting
early next morning, the orders are packed onto the vans by route, and deliveries made to wholesale
customers and shops before 9.00 a.m.
During the afternoon, the front sales office staff receive late orders or additions and changes to
Page 2 of 9
SWE5206- System Analysis and Design
existing orders. As the computer system can only process one order per customer per day, these
orders cause difficulties which result in underproduction and overproduction of bakery products,
shortfalls on deliveries, disruption of the front sales office and incorrect information being input to the
accounting system.
Company Structure
J H Barden
Managing Director
│
┌──────────────────┬─────┴─────────┬───────────────
┐
│ │ │ │
C Nightingale F Hasty S Packer A Birdsong
Front Sales Office Chief Baker Despatch Accounts
Supervisor │ Controller Clerk
│ │ │
│ │ ┌──────┴──────┐
│ │ │ │
Agnes McAdam │ Annabelle Smith Delivery Van
Sales Assistant │ Diane Rigby Drivers
│ Packers
│ Order Assembly
┌───────┴───────┐
│ │
Mrs Prince Alastair Todd
Senior Baker Senior Baker
Cake Production Bread Production
In addition, up to 30 part-time and seasonal staff may be employed to cope with demand as needed.
Business Functions of the Bakery
Function 1. Prepare daily orders for production and despatch.
Own shops and wholesale customers are telephoned for daily orders. These are entered into the
Cakebake system which is then used to produce production lists, invoices and delivery notes. Order
amendments are dealt with manually.
Function 2. Prepare daily reports for accounts.
Using the confirmation of delivery in the form of the yellow invoices and delivery note copies, the shop
delivery valuation and day book listing are prepared for the accounts section.
Function 3. Prepare routes and assemble orders.
Page 3 of 9
SWE5206- System Analysis and Design
The invoices for wholesale customers and the delivery notes for own shops are assembled into route
sets together with a route chit giving details of the delivery route.
Orders are assembled by route set in the despatch room. Trays are labelled and placed in the
despatch area ready for loading into vans. Invoice and delivery note copies returned by van drivers
are passed to the Front Sales Office. Cash collected is passed to the accounts section.
Function 5. Maintain Cakebake files.
New customers and products and amendment to existing customers and products are applied to the
Cakebake system. The amended files are printed. A copy of each is retained within Front Sales
Office. Copies are distributed to Front Sales Office, Despatch and own shops and wholesale
customers as appropriate.
------------------------------------------------------------ Case Study Ends here---------------------------------------------
Resources
The following staff at BlueBerry are available as required to assist with the investigation.
1. C Nightingale, Front Sales Office Supervisor, will explain the details of the order processing
activities and the operational difficulties encountered.
2. S Packer, Despatch Controller, is available to discuss the day-to-day operations in his areas
of work.
Sam Packer will be available to see single analysts from 9.00 am to 11.00 am on Wednesday the 19 th
of October. The following week on Wednesday the 26 th and Thursday the 27th from 9.00 to 11.00 am
Colin Nightingale will be available to see single analysts. The following week, both will be available to
be interviewed by groups of analysts as required on both the Wednesday and the Thursday.
Reporting
Regular progress meetings will be held by analysts currently working on the project. The definition of
the existing system, its problems and new requirements will be prepared and reported back in a
standardised report format.
Students can utilize choice of tool to create plan, design, questionnaire for their Portfolio.
Deliverables
Each Student should submit a Report, a presentation and a portfolio as a zipped folder.
Submission Instructions
Student should submit deliverables on Moodle on or before deadline in the Moodle Assignment/
Turnitin submission links as described below.
1. Individual Report should be submitted via TurnItIn.
2. The presentation should be submitted via TurnItIn, one per group.
Page 4 of 9
SWE5206- System Analysis and Design
3. The learners must submit the portfolio as a zipped folder with StudentId_Name as the
folder name. It should have evidence of planning, interview questions and answers and
survey questions and answers.
Report:
The deliverable is a single project file (in electronic format), one should submit individual work.
Remember that this is an academic piece of work and should be produced to a professional
standard. All citations must be in Harvard notation.
The file should contain the following SSADM products submitted by the group
1. Issues Identified about the system
2. Proposed system
3. Context Data Flow Diagram
4. Level 1 DFD
5. External Entity Descriptions and Entity Relationship Diagram.
6. Requirements Catalogue
7. User Catalogue
8. Minutes of meetings held by the group
Each team member should then investigate further at least one process from the Level 1 DFD.
Relating to this investigation, for each team member the following should be submitted
1. Level 2 DFD
2. Elementary Process Descriptions
3. Interview plan and write-ups
4. Presentation
Each student is required to perform at least one fact finding interview alone. Each student’s first
interview will be assessed. Teams or individuals may request additional/follow-up interviews.
Minimum Secondary Research Source Requirements
Level HE5 - It is expected that the Reference List will contain between ten and fifteen sources. As a
MINIMUM the Reference List should include two refereed academic journals and four academic
books
Presentation
Final Presentation should be for 20 minutes. The presentation details include Issues Identified
about the system, DFDs, ERDs and the proposed system design. All team members should
participate in the presentation.
Page 5 of 9
SWE5206- System Analysis and Design
Late submission of assessments
On or before deadline, actual marks.
Late work will be subject to the penalties:
o Up to 7 calendar days late = 10 marks subtracted but if the assignment would
normally gain a pass mark, then the final mark to be no lower than the pass mark for
the assignment.
o More than 7 calendar days late = This will be counted as non-submission and no
marks will be recorded.
Specific Assessment Criteria:
First class (70% and above):
Students will provide an in-depth appraisal of the Analysis, Elicitation Techniques and Design,
demonstrating excellent critical reasoning skills. Focused and justified recommendations will be
made as to how problems/weaknesses identified in the plan may be overcome, and sustainability
improved. Extensive research demonstrating use of a wide range of current secondary research
sources will be evident. Academic style and referencing will be excellent.
Second class (50-69%):
Students will provide a comprehensive appraisal of the Analysis, Elicitation Techniques and
Design, demonstrating critical reasoning skills. Justified recommendations will be made as to how
problems/weaknesses identified in the plan may be overcome, and sustainability improved.
Research demonstrating use of a wide range of current secondary research sources will be
evident. Academic style and referencing will be good.
Third class (40-49%):
Students will provide a satisfactory appraisal of the Analysis, Elicitation Techniques and Design,
demonstrating critical reasoning skills. Considered recommendations will be made as to how
problems/weaknesses identified in the plan may be overcome, and sustainability improved.
Research demonstrating use of a range of current secondary research sources will be evident.
Academic style and referencing will be fair.
Fail (39% and below): Students who do not meet the requirements of a third-class grade will not
successfully complete the assessment activity.
Page 6 of 9
SWE5206- System Analysis and Design
Assessment Criteria and Marks
No. Criteria Marks
I Individual Assessment 50
1 Contribution to SSADM products and project file-Level 2 Data Flow 15
Diagram
2 Elementary Process Descriptions 10
3 Interview - plan, conduct and write-up 15
4 Presentation of the completed project file. 10
II Team Assessment 40
1 Issues Identified about the system 5
2 Proposed system 6
3 Entity Relationship Diagram and explanation 6
4 Context Level Data Flow Diagram 6
5 Requirements Catalogue 6
6 User Catalogue 6
7 Minutes of meetings held by the group 5
III Report Presentation Skills 10
1 Report Structure (like Headings, Sections, Justified text) 2
2 Spelling, Punctuation, Sentence Framing and Grammar 2
3 References
a Number of references 3
b Harvard Referencing (In-text/image, Reference Listing) 3
Total 100
There should be a critical reflection by each individual student on the process of system
analysis and design.
The project report should be structured and referenced appropriately.
Guidelines for the Preparation and Submission of Written Assessments
Page 7 of 9
SWE5206- System Analysis and Design
1. Written assessments should be word-processed in Arial or Calibri Light font size 12. There
should be double-spacing and each page should be numbered.
2. There should be a title page identifying the programme name, module title, assessment
title, your student number, your marking tutor and the date of submission.
3. You should include a word-count at the end of the assessment (excluding references,
figures, tables and appendices).
Where a word limit is specified, the following penalty systems applies:
Up to 10% over the specified word length = no penalty
10 – 20% over the specified indicative word length = 5 marks subtracted (but if the
assessment would normally gain a pass mark, then the final mark to be no lower
than the pass mark for the assessment).
More than 20% over the indicative word length = if the assessment would normally
gain a pass mark or more, then the final mark will capped at the pass mark for the
assessment.
4. All written work should be referenced using the standard University of Bolton Harvard
referencing style– see: https://libguides.bolton.ac.uk/resources/referencing/
5. Unless otherwise notified by your Module Tutor, electronic copies of assignments should be
saved as word documents and uploaded into Turnitin via the Moodle class area. If you
experience problems in uploading your work, then you must send an electronic copy of your
assessment to your Module Tutor via email BEFORE the due date/time.
6. Please note that when you submit your work to Moodle, it will automatically be checked for
matches against other electronic information. The individual percentage text matches may
be used as evidence in an academic misconduct investigation (see Section 13).
7. Late work
Late work will be subject to the following penalties:
Up to 7 calendar days late = 10 marks subtracted but if the assignment would
normally gain a pass mark, then the final mark to be no lower than the pass mark for
the assignment.
More than 7 calendar days late = This will be counted as non-submission and no
marks will be recorded.
Page 8 of 9
SWE5206- System Analysis and Design
8. Student must demonstrate competent analytical and problem-solving skills which should be
evidenced by the appropriate reasoned argument and activities. The reports should be
presented carefully, with accurate spelling, punctuation and word processed and referenced
using the Harvard System.
Academic Misconduct
Academic misconduct may be defined as any attempt by a student to gain an unfair advantage in
any assessment. This includes plagiarism, collusion, commissioning (contract cheating) amongst
other offences. In order to avoid these types of academic misconduct, you should ensure that all
your work is your own and that sources are attributed using the correct referencing techniques.
You can also check originality through Turnitin.
Please note that penalties apply if academic misconduct is proven. See the following link for further
details: https://www.bolton.ac.uk/student-policy-zone/student-policy-zone-2022-23/academic-
misconduct-regulations-and-procedures-2022-23
Page 9 of 9