Unit 6 - Software Design & Development - AS2 (P6, M2, D2)

GOOD DESIGN!
Unit 6: Software Design & Development – AS3




Cobzariu, Daniel 4/30/21 BTEC LEVEL 3 IN IT

,Contents
1. A. Requirement Specification.............................................................................................................2
1. Brief description of the project......................................................................................................2
2. User requirements.........................................................................................................................2
3. Inputs and Outputs........................................................................................................................2
4. Functions (from the user’s perspective)........................................................................................3
5. User Interface................................................................................................................................3
6. Data validation...............................................................................................................................4
7. Constraints.....................................................................................................................................4
1 B. Design documentation....................................................................................................................5
1. User Interface Design.....................................................................................................................5
2. Output Design (receipts – delivery/collection)..............................................................................8
3. Entity Relationship Diagram.........................................................................................................10
4. Level 0 (context) DFD...................................................................................................................10
5. Level 1 DFD..................................................................................................................................11
6. IPO Chart......................................................................................................................................11
7. Data dictionary.............................................................................................................................12
2. Justification of Design Solution........................................................................................................13
1. Data types....................................................................................................................................13
2. Software structures......................................................................................................................14
Sub-procedures and modular code..............................................................................................14
Selection......................................................................................................................................14
Iteration.......................................................................................................................................14
T3. Developing algorithms to represent a design solution..................................................................16
1. Annotated flowchart....................................................................................................................16
2. Pseudocode with annotations.....................................................................................................18

, 1. A. Requirement Specification

1. Brief description of the project

A local fast-food restaurant needs a new ordering and billing system
that can be used to take orders quickly. The application must enable
users to take orders and calculate the total price for their customers.
An option indicating whether delivery is required or not should be
implemented as well. If the order has to be delivered, further customer
details such as the address and name must be collected. Before
preparation, the order summary will be displayed so it can be checked
with the customer.
2. User requirements

 The program must enable the user to take orders from their
customers
 It should also calculate the total price for the order
 The user must select whether the order will be delivered or
collected
 Produce a summary of the order that can be printed afterwards
(receipt)
Other relevant suggestions:
 There should be a menu containing all the food available
 The application should work on touchscreen devices
3. Inputs and Outputs

Inputs
 The food requested by the client must be inserted through button
clicks
 Users will have a selection of three options
(delivery/collection/eating in)
 If the order has to be delivered, customer details should be
inserted

Outputs
 The total price needs to be displayed on the screen
 The summary of the order should be shown on the screen
The program should show whether the order must be delivered,
collected or if the customer is eating in, based on the feedback