BACKEND SYSTEM DESIGN

SWDBS401
Design Backend System

Competence
RQF Level: 4 Learning Hours
80 Hours
Credits: 8

Sector: ICT and Multimedia

Trade: Software Development

Module Type: Specific

Curriculum: ICTSWD4002-TVET Certificate IV in Software Development

Copyright: © Rwanda TVET Board, 2023

1200 Issue Date: September, 2023

1|Page
Purpose statement This specific module describes the Knowledge, skills, Attitude and values
required to Design Backend System. Upon completion of this module. The
learner will be able to Analyze Backend System Requirements, develop
system structure and Build Backend System.
Learning assumed N/A
to be in place
Delivery modality Training delivery 100% Assessment Total 100%

Theoretical content 30% 30%

Practical work:

Group project and 30% Formative

50%
presentation 70% assessment 70%

Individual project 40%

/Work
Summative Assessment 50%

Elements of Competence and Performance Criteria

Elements of Performance criteria

competence
1.1 FURPS requirements are effectively gathered based on system
application requirements

1.2 Main objects are properly identified based on the system analysis
1. Analyze
methodology
System Backend
1.3 System interactions are clearly described based on identified objects

1.4 System Backend Requirements are appropriately reported in line with

software requirements document
2.1 System structure design tools are properly identified based on analysis

2|Page
 report and design methodology

2.2 The hardware & software technologies are properly identified based on
system requirements
2.Develop
System Structure 2.3 The system structure is neatly drawn based on the system requirements
and design methodology

3.1 The data flow of the system is appropriately developed based on the
system design Requirements

3. Build System 3.2 Physical Data Model is accurately designed based on the analysis report
Design and system structure
3.3 The documentation of system design is properly based on system
analysis and architecture

3|Page
 Intended Knowledge, Skills, and Attitude

Knowledge Skills Attitude

✓ Describe backend ✓ Document report of system ✓ Team work
development Technologies. requirements ✓ Be critical thinker
✓ Describe System ✓ Use System Analysis tools ✓ Being Innovative
development life cycle (SDLC) ✓ Use SSADM ✓ Be attentive.
✓ Identify system Analysis tools ✓ Identify of FURPS ✓ Being creative
✓ Identify FURPS Requirements Requirements ✓ Problem solving
✓ Identify main objects of ✓ Perform Object-Oriented ✓ Practical oriented
Backend System Analysis and Design ✓ Detail oriented
✓ Describe system Interaction ✓ Develop Data Flow diagram ✓ User-Centric Approach
✓ Identify system design tools ✓ Perform data Modeling ✓ Curiosity and Open-
✓ Identify hardware and ✓ Document system design Mindedness
software technology ✓ Attention to Detail

Course content

Learning outcomes At the end of the module the learner will be able to:

1. Analyze System Backend

2.Develop System Structure
3. Build System Design

Learning outcome 1: Analyze System Backend Learning hours: 17

Indicative content

• Gathering FURPS Requirements

✓ Definition of key terms

Backend

4|Page
 System

Server

Database

Operating System

System Development Life Cycle (SDLC)

API

JSON

Framework

UML

FURPS (Functionality, Usability, Reliability, Performance and Supportability)

✓ System development life cycle (SDLC)

Phases

Models (Agile, V shaped, Waterfall, Prototyping, etc.)

✓ Backend development Technologies

Python and its Frameworks

PHP and its Frameworks

JAVA and its Frameworks

JavaScript and its frameworks

Ruby and its Framework

✓ System Analysis tools

5|Page
 Grid chart

System Flowchart

Decision tree

Simulation

Decision table

✓ Data Gathering

✓ Identification of FURPS Requirements

Functionality requirements

Usability requirements

Reliability requirements

Performance requirements

Supportability

• Identification of Main objects of Backend System

✓ Define the Scope of Backend System

✓ Database

✓ APIs

✓ Servers

✓ Frameworks

• Description of System Interaction

✓ Purpose of System Interaction

6|Page
 ✓ Main components of System Interaction

Web server

Application Server

Database Server

External Services and API

Message queues or event Streams

• Report of the System Backend Requirements

✓ Executive summary

✓ Detailed analysis of the Current State

✓ Findings on Gaps and issues

✓ Recommendations

Resources required for the learning outcome

Equipment ▪ Computer

Materials ▪ Internet

Tools ▪ Microsoft Office

▪ Visual paradigm

▪ E- Draw

▪ Browser

Facilitation ▪ Group discussion

7|Page
techniques
▪ Brainstorming

▪ Individual Work

▪ Demonstration and simulation

Formative ▪ Oral presentation

assessment methods
▪ Written Assessment
/(CAT)

▪ Performance Assessment

8|Page
Learning outcome 2: Develop System Structure Learning hours: 31

Indicative content

• Identification of system design tools

✓ UML (Unified Modeling Language)

✓ Algorithm

✓ Flowchart

✓ Data flow Diagram (DFD)

✓ Entity Relation diagram (ERD)

✓ Context diagram

✓ Decision table

✓ Use case diagram

✓ Class Diagram

✓ Decision tree

• Identification of Hardware and software technology

✓ Computer Hardware

✓ System software

✓ Application Software

Microsoft Office

visual paradigm

E-Draw max

browser

9|Page
 • Application of SSADM (Structured System Analysis and Design Methods)

✓ Objective of SSADM

✓ SSADM Techniques

Logical Data modeling

Data flow Modeling

Entity Behavior modeling

✓ Implementation of stages for drawing SSADM

• Application of Object-Oriented Analysis and Design

✓ Introduction

✓ Advantage and disadvantages

✓ Phases in Object-Oriented Software development

Analysis

Design

Implementation

Resources required for the indicative content

Equipment ▪ Computer

Materials ▪ Internet

Tools ▪ Microsoft office

▪ Visual paradigm
▪ Draw
▪ Browser
Facilitation ▪ Group discussion
techniques ▪ Brainstorming
▪ Jig Saw

10 | P a g e
Formative ▪ Oral presentation
assessment methods ▪ Written Assessment
/(CAT) ▪ Performance Assessment

11 | P a g e
Learning outcome 3: Build System Design Learning hours: 32

Indicative content

• Development of Data Flow

✓ Data flow Diagram (DFD)

Elements of DFD

Rules of Drawing a DFD

Level 0 (Context)

Level 1

Level 2 (Function decomposition)

✓ Software tools

Microsoft office

visual paradigm

E-draw

✓ Develop Data flow diagram of system

• Application of Physical Data Model

✓ Identify the database Objects

✓ Design Database

Tables

Relationships

• Documentation of system design

✓ Types of documentation of system design

12 | P a g e
 System Design document(SDD)

Functional Specification Document(FSD)

Technical Specification Document(TSD)

Database design Document

Use case Document

✓ System documentation

✓ User documentation

Resources required for the indicative content

Equipment ▪ Computer

Materials ▪ Internet

Tools ▪ Microsoft office

▪ Visual paradigm

▪ E- Draw max

▪ Browser

Facilitation ▪ Group discussion

techniques ▪ Brainstorming
▪ Jig Saw
Formative ▪ Oral presentation
assessment methods ▪ Written Assessment
/(CAT) ▪ Performance Assessment

13 | P a g e
 Integrated/Summative assessment

Integrated situation
UX Pharmacy is located in Kigali City, Kicukiro District and has two branches one in Remera and
another in Kacyiru. The main branch manager purchases medicines and keeps in the pharmacy stock
for sell. The Pharmacy supplies medicines to its branches depending on branch sales through stock
manager at each branch.

Even though the branches Managers are skilled in using computer, they record and report sales using
Microsoft office excel and hard copies. However, this filing system is not reliable as it can cause some
problems like loss of data in case documents are misplaced or lost, in addition these paper records
occupy large space at the branches and sharing files requires branch managers to travel to the main
branch. Moreover, it is very hard to produce daily/weekly/monthly and annual reports about stock
and sales status.

As a Backend System designer you are hired to design the system structure and make a
documentation that will help the developers to build a backend system for UX Pharmacy.

Instruction:

1. The designed Backend system structure should include

• A visual presentation of data flows within the system.

• A graphical representation of how the system objects are related to each other

• A graphical representation of user and Backend system interaction

2. The designed Backend System structure should have User documentation

3. The designed Backend System structure should have system documentation

Task is needed in 8 Hours

Resources
Tools ▪ Microsoft office E-Draw max
Equipment ▪ Computer

14 | P a g e
 ▪ Papers
▪ Pens
Materials/ Consumables ▪ Pencils
▪ Electricity
▪ Rubber

Assessable Assessment criteria (Based Observation Marks

Indicator
outcomes on performance criteria) Yes No allocation

Learning 1.1 FURPS requirements are Ind1. FURPS 5

outcome 1: effectively gathered based Requirements are
Analyze System on system application Reported
Backend (30%) requirements
1.2 Main objects are properly Ind2. Main 4
identified based on the objects are
system analysis selected
methodology
1.3 System Backend Ind3. System 6
Requirements are Backend
appropriately reported in line Requirements are
with software requirements Reported
document
Learning 2.1.System structure design Ind1. design tools 5
outcome 2: tools are properly identified are used
Develop System based on analysis report and
Structure (40%) design methodology
2.2. The hardware & software Ind1. computer’s 2
technologies are properly Hardware are
identified based on system prepared
requirements Ind2. Software 3
Technology is
selected

15 | P a g e
 2.3The system structure is Ind1. SSADM or 10
neatly drawn based on the OOAD is used
system requirements and
design methodology
Learning 3.1. The data flow of the Ind1. DFD 2
outcome 3: system is appropriately software tools
Build System developed based on the are used
Design (30%) system design Requirements Ind2. DFD Rules 2
are applied
Ind2. DFD is 2
developed
Ind1. Database 2
3.2 Physical Data Model is
Objects are
accurately designed based on
designed
the analysis report and
Ind2. ERD is 2
system structure
designed
3.3. The documentation of Ind1. User 2
system design is properly documentation is
based on system analysis and reported
architecture Ind2. System 3
documentation is
reported
Total marks 50
Percentage Weightage 100%
Minimum Passing line % (Aggregate): 70%

16 | P a g e
References
1. (n.d.). Retrieved from Cyblance: https://www.cyblance.com/system-analysis/tools-
used-system-analysis-details/

2. (n.d.). Retrieved from tutorialspoint:

https://www.tutorialspoint.com/object_oriented_analysis_design/ooad_quick_guid
e.htm

3. (n.d.). Retrieved from java T point: https://www.javatpoint.com/software-

engineering-data-flow-diagrams

4. (n.d.). Retrieved from Project Practical: https://www.projectpractical.com/9-steps-

to-write-a-system-design-document-free-template/

5. (2020, March 17). Retrieved from tutsmaster: https://tutsmaster.org/what-is-

system-design-tool-explain-the-different-types/

6. (2021, 03 08). Retrieved from IBM:

https://www.ibm.com/docs/en/ida/9.1.1?topic=modeling-physical-data-models

7. (2023, March 21). Retrieved from InterviewBit:

https://www.interviewbit.com/blog/backend-technologies/

8. Aletexsoft. (2021, jul 23). home. Retrieved from home:

https://www.altexsoft.com/blog/business/functional-and-non-functional-
requirements-specification-and-
types/#:~:text=Functional%20requirements%20are%20product%20features,system
%20behavior%20under%20specific%20conditions

9. Bandakkanavar, R. (2021, june 10). Retrieved from KrazyTech:

https://krazytech.com/projects/sample-software-requirements-specificationsrs-
report-airline-database

10. Laube, A. (2022, 02 15). home. Retrieved from Neomind: 2.

https://www.neomind.com.br/en/blog/importance-software-

17 | P a g e
 usability/#:~:text=For%20a%20system%20to%20have,errors%2C%20and%20be%20s
ubjectively%20satisfying

11. Lutkevich, B. (n.d.). Retrieved from TechTarget: https://tutsmaster.org/what-is-

system-design-tool-explain-the-different-types/

12. Vissers, C. A. (2016, september 24). Retrieved from Springer link:

https://link.springer.com/chapter/10.1007/978-3-319-43298-4_7

18 | P a g e