SEC4204 Fundamentals in Computer Programming: System Design Report

This report presents a comprehensive analysis of programming methodologies and system design principles, focusing on the development of a C++ application for the Light Up Electricity Corporation. The report details the usage of various programming methodologies, including procedural, ...Read More

Assignment Cover Sheet
Qualification Module Number and Title
HD in Computing/ Software Engineering SEC4204
Fundamentals in Computer Programming
Student Name & No. Assessor
M.G. Asanka Dinesh
Hand over date Submission Date
12.10.2020 Coursework 1 :
Coursework 2 :
Assessment type Duration/Length of
Assessment Type
Weighting of Assessment
Coursework 1 (design
Document)
Coursework 2
(Software project with
test document)
1,000 words equivalent
2,000 words equivalent
40%
60%
Learner declaration
I, ………………………………………….<name of the student and registration number>,
certify that the work submitted for this assignment is my own and research sources are fully
acknowledged.
Marks Awarded
First assessor
IV marks
Agreed grade
Signature of the assessor Date
FEEDBACK FORM
INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY
1

Module : SEC4204
Student :
Assessor : M.G. Asanka Dinesh
Assignment : FCP
Strong features of your work:
Areas for improvement:
Marks Awarded:
2

Scenario
Light Up Electricity Corporation deals with 100’s of customers monthly. At present the
Light Up maintains customer account details manually and they need a computerized
approach to maintain their billing information.
Every customer account is assigned an account number. New customers are registered by the
system and the system should take information such as account number, name, Address,
Telephone no, units burned, etc...
The program should do the following:
1. Proper authentication to the system (Login)
Use user name and password to login
2. Add new customer accounts
Customers Account number, Name, Address, Telephone no, etc.
3. Display account details
4. Calculate billing amount
Calculate amount according to the number of units burned
5. Print bill
Print account number, units burned and the billing amount, etc.
6. Help
System usage guidelines for new users
7. Exit from the system
(More functionality can be included)
You are required to use C++ programming language to construct this application. Create an
error free, effective console application by including appropriate messages, outputs and
menus. Make this as a menu driven program; show the user’s choice and allow the user to
make appropriate choice. Use an appropriate data storage mechanism and suitable
modularization techniques.
3

Course Work 1
This Component is worth 40% of the overall assessment for this module.
Learning outcomes covered
LO 1. Understand structured programming concepts
LO 2. Design a basic structured computer program
TASKS
Task 01 – Programming methodology (LO1) -Report
Describe the usage of basic programming methodology such as controlling structures
(selection, repetition) and modularization.
● Provide appropriate examples. (40 marks)
Task 02 - System Design (LO2) -Report
Identify the requirements of the system to be implemented. Design flow charts for the login
unit, calculate and print bill units according to the requirement given. Provide your system
hierarchy diagram to show modularization.● Use appropriate modularization to reduce the complexity of the design. (60 marks)
Submission Guidelines
▪ Submission format: Report (online: uploaded via SIS)
▪ Paper Size: A4
▪ Words: 3000 words
▪ Printing Margins: LHS; RHS: 1 Inch
▪ Header and Footer: 1 Inch
▪ Basic Font Size: 12
4

▪ Line Spacing: 1.5
▪ Font Style: Times New Roman
5

Assessment Criteria
Task 01 – Programming Concepts (LO1)
This submission will be assessed as follows
Criteria
Total marks
Allocated
Marks obtained
by the student for
the answer
provided
Out of 40
Excellent Understanding
● Outstanding/Excellent answer given with
strong discussion providing appropriate
examples
● Excellent knowledge in basic programming
methodology
● Evidence of Research and proper use of
referencing
28-40
Good Understanding
● Comprehensive answer given with very good
understanding providing appropriate
examples
● Good knowledge in basic programming
methodology
24-28
Satisfactory Understanding
● A satisfactory answer with a demonstration of
basic understanding of the programming
methodology
● Very basic answer with limited examples
16-24
Poor Understanding
● lack of understanding about basic programming
concepts
● Task is not attempted or attempted with an
insufficient, incomplete answer
0-16
6

Task 02 - System Design (LO2)
This submission will be assessed as follows
Criteria
Total marks
Allocated
Marks obtained by
the student for the
answer providedOut of 60
Excellent Design
● Excellent identification of requirements
● Highly detailed diagram
● Use of modularization concepts clearly visible
● Excellent use of symbols
● Clarity and Reduce complexity of the design
● Backed by relevant assumptions
42-60
Good Design
● Detail requirements including functional and
non-functional requirements, data and file
structure requirements
● Flow charts following standard notations in
flow charting.
● Accurate use of selection repetition structures
● Logical and continuous flow of instructions along
the design
36-42
Satisfactory Design
● Describe functional requirements
● Clear identification and application of symbols
in flow charts
● Average level design diagrams given
24-36
Poor Design
● Evidence of lack of understanding systems
requirements
● Poor use of design tools and symbols
0-24
7

● Design diagrams with invalid flows, incomplete
diagrams with logical errors
Total Marks 100
8

Course Work 2
This Component is worth 60% of the overall assessment for this module.
Learning outcomes covered
LO 3. Implement a modularized computer program for a prepared design
LO 4. Perform software testing and documentation
Task 03 – System Implementation (LO3) - Software submission
Implement a functional C++ program to meet the requirements given in the specification, by
following the design created earlier. (60 marks)
Task 04 - System Testing and Documentation (LO4) -Report
Produce proper testing documentation including test plan, test cases and test results. Conduct
user acceptance testing and provide feedback with sample questionnaires used.
● Proper standard documentationneeds to be followed throughout the report and
language need to be used accordingly. (40 marks)
Submission Guidelines
▪ Submission format: software source code and test documentation
▪ Submit at the end of the module.
9

Assessment Criteria
Task 03 – System Implementation (LO3)
This submission will be assessed as follows
Criteria
Total marks
Allocated
Marks obtained by
the student for the
answer providedOut of 60
Excellent implementation
● Excellent use of control structures with
improved coding efficiency
● Use file handling techniques for storage and
backup requirements
● Excellent Modularization with effective data
passing between developed modules.
● Appropriate arrays, structs(records) used
● Easy navigation between modules, accuracy,
creativity and completeness of the system
42-60
Good implementation
● Use of Comments to improve code readability
● good use of control structures with proper
understanding
● Modularize according to the given design.
● Use of input validations, onscreen help options
and User friendliness of the system
36-42
Satisfactory implementation
● Operational system according to the
requirements of the scenario
● Average use of data types and operators
● Average use of control structures (selection and
repetition)
24-36
Poor implementation
● Poor implementation with syntax errors
0-24
10

● Lack of knowledge of the language basics used
● Cannot fulfill basic system requirements
11

Task 04 - System Testing and Documentation (LO4)
This submission will be assessed as follows
Criteria
Total marks
Allocated
Marks obtained by
the student for the
answer providedOut of 40
Excellent Documentation
● Excellent Test documentation with detail test
plan and test cases
● Acceptance test with proper questionnaire
samples.Well analyzed user feedback which
supports recommendations.
● Testing conclusion with critical review and
future recommendations
● Appropriate use of language and Standard report
format followed
● Proper use of Referencing
28-40
Good Documentation
● Detailed Test Plan
● Appropriate Test Cases
● Acceptance test with User feedback and test
conclusion
● Good documentation
24-28
Satisfactory Documentation
● Basic Test Plan
● Average Test Cases
● Average documentation
16-24
Poor Documentation
● Lack of test plan, poor test cases
0-16
12

● No proper evidence of testing
● Poor report formatting
Total Marks 100
13

Acknowledgement
I am really thankful to all the people who helped me to make this report a reality. First of all,
my special thanks go to who helped me Mr. M.G Asanka Dinesh who provides me the
information and the guidance and also the center manager of ICBT Campus Kurunegala for
giving the access to the library and the other places to gain information. And my special
thanks to my batch mates who helping me to correct my mistakes and the providing me the
valuable information with examples. In the end, I am really gratefully to my parents for
helping me by giving their guidance and for paving the way to success.
14

Table of Contents
Acknowledgement....................................................................................................................10
Table of Figures.......................................................................................................................13
Table of Table..........................................................................................................................14
Executive Summary.................................................................................................................15
Introduction..............................................................................................................................16
Task 01 - Programming Methodologies...................................................................................17
1.1. Types of Programming Methodologies.........................................................................17
1.1.1. Procedural Programming.......................................................................................17
1.1.2. Object-oriented Programming................................................................................17
1.1.3. Functional Programming........................................................................................17
1.1.4. Logical Programming.............................................................................................17
1.2. Requirement Gathering.................................................................................................17
1.3. Problem Definition........................................................................................................18
1.4. Flowcharting.................................................................................................................18
1.5. Pseudocode....................................................................................................................18
1.6. Applying Modular Techniques.....................................................................................18
1.7. Control Structures.........................................................................................................19
1.7.1. Selection.................................................................................................................19
1.7.2. Repetition...............................................................................................................21
1.7.3. Sequence................................................................................................................22
1.8 Fundamental Data Types................................................................................................23
1.8.1. Character types.......................................................................................................23
1.8.2. Numerical integer types.........................................................................................23
1.8.3. Floating-point types...............................................................................................23
1.8.4. Void types..............................................................................................................23
15

Task 02 - SRS Document for Light Up Electricity Corporation..............................................24
2.1. System Requirement Specification of Light Up Electricity Corporation System.........24
2.1.1. Purpose...................................................................................................................24
2.1.2 Scope.......................................................................................................................24
2.1.3. Overview................................................................................................................24
2.1.4. Overall Description................................................................................................24
2.1.5. Product Perspective................................................................................................25
2.1.6. Product Functions...................................................................................................25
2.1.7. User Characteristics...............................................................................................25
2.1.8. Assumptions and Dependencies.............................................................................25
2.1.9. Requirements..........................................................................................................25
2.1.10. Functional Requirements.....................................................................................25
2.1.11. System Requirements...........................................................................................26
2.1.12. Non-functional requirements...............................................................................26
2.1.13. Schedule Representation......................................................................................26
2.2 Software Flowcharts.......................................................................................................27
2.3 Software Pseudocode.....................................................................................................30
2.4 Data Dictionary..............................................................................................................32
References................................................................................................................................33
16

Table of Figures
Figure 1-If Statement...............................................................................................................19
Figure 2-If else statement.........................................................................................................20
Figure 3-Switch Statement.......................................................................................................20
Figure 4-While Loop................................................................................................................21
Figure 5-For Loop...................................................................................................................22
Figure 6-Example for Sequence...............................................................................................22
Figure 7-Flow Chart 1.............................................................................................................27
17

Executive Summary
Light Up Electricity Corporation is a software application that helps to keep track of all
operations and day to day activities to handle their working process smoothly and effective
way. This program used two types of people. The system Administrator and the user who
came to use this system. Both of them have many functions to improve their service in this
program. This program works as a self-service and therefore the customer can submit the
application himself. The administrator can make changes to the services available to the user
and make all arrangements. An administrator can delete information to store and modify
information. This stored information can also be accessed separately by the user.
18

Introduction
Software Requirement Specification is used to describe the nature of the software. The SRS
includes purpose, scope, overview, overall description, product perspective, product
functions,
User characteristics and assumptions and dependencies. This report includes every
requirement
about Light Up Electricity Corporation.
C++, as we all know is an extension to C language and was developed by Bjarne sproutsup at
bell labs. C++ is an intermediate level language, as it comprises a confirmation of both high
level and low-level language features. C++ is a statically typed, free form, multiparadigm,
compiled general-purpose language.
C++ is an Object-Oriented Programming language but is not purely Object Oriented. Its
features like Friend and Virtual, violate some of the very important OOPS features, rendering
this language unworthy of being called completely Object Oriented. It’s a middle level
language.
In 1998 the ISO (International Organization for Standardization) approved a standard
for C++ (ISO/IEC 14882).
19

Task 01 - Programming Methodologies
1.1. Types of Programming Methodologies
1.1.1. Procedural Programming
Steps or blocks of code that carry out one function are the issue breakdown. The whole
program contains all the steps performed together. It can only be used in limited, low-
complicated programs
Example − Each of these operations can be developed as different procedures with a
calculator program that adds, subtracts, multiplies, divides square root and comparisons. The
method is initiated in the main program based on the choice of the user. (Tutorials Point,
2006)
1.1.2. Object-oriented Programming
The solution here focuses on entities or objects which constitute a problem. The solution
identifies how data concerning entities are stored, how entities are behavioral and how they
interact to offer a cohesive solution to each other.
Example − If a payroll management system is to be created, they shall have organizations
such as staff, wage scale, guidelines for the time of leave, etc. (Tutorials Point, 2006)
1.1.3. Functional Programming
Having regard to the problem, the desired solution is divided into functional units. Each unit
carries out its own task and is independent, and these units are combined into one solution.
Example − Payroll processing may include operational units such as the data maintenance of
workers, basic wage calculation, gross pay calculation, processing of leave, processing of
loans for repays, etc. (Tutorials Point, 2006)
1.1.4. Logical Programming
The problem here is separated into logical units instead of functional units.
Example: users have very defined roles in a school management system such as class
teachers,
instructors, laboratory assistants, coordinators of academics, etc. Therefore, according to user
roles, the program can be divided into units. The configuration, approval, etc. for each user.
20

1.2. Requirement Gathering
In particular, customers or users cannot describe their issues or specifications clearly. You've
got a vague idea of what you want. The software engineers must gather client specifications
to
understand the problem or what needs to be resolved. Only through first understanding of the
business field for which the solution is created is possible a thorough understanding of the
problem.
1.3. Problem Definition
The problem statement needs to be stated explicitly after the criteria have been gathered and
evaluated. The definition of a problem should clearly specify which problems or problems
must
be resolved. To define project scope, maintain the team focused and keep the project on track,
a clear problem statement is necessary.
1.4. Flowcharting
Flowcharting is the method by which workflows and information flow by symbols and
diagrams be represented in a framework. It is a key tool to help the analyst find a solution to
the problem. This visually displays the system’s elements.
1.5. Pseudocode
After the program has been built it is passed for execution, i.e. coding, to the project
manager.
The actual program coding takes place in a programming language that can only be
interpreted
by developers who have been educated in this language. However, the coding of the program
is done in advance by means of a notation similar to the programming language to be used for
the basic operating principles, work flows, and data flows. A pseudo-code is a representation
of this kind.
21

1.6. Applying Modular Techniques
The technique of breaking down one large solution into smaller modules is called the
modular
technique of programming or software development for ease of creation, implementation,
modification and maintenance.
1.7. Control Structures
When programs are using to solve complex problems, they must be used controlling
structures for simplify the problem and to make it programmable. There are three main
control
structures,
1. Selection
2. Repetition
3. Sequence
1.7.1. Selection
Selection construct allows to write a program which is selectively executed. Which means if
the condition is satisfied one set of instruction will be executed otherwise another set of
instruction will be executed. C++ programming language has three types of selection
statements are,
i. If
ii. If else
iii. Switch(informIT, n.d.)
1.7.1.1. If Statement
The if selection statement either performs an action if a condition is true or skips the action if
a condition is false. In this case cannot be more than five attempts at logging in at this time.
The if selection is single selection statement. (informIT, n.d.)
22

Figure 1-If Statement
23

1.7.1.2. If else Statement
If condition is true performs an action and if a condition is false, then performs a different
action. That’s how if else statement works. If else statement can be used to check whether a
username/ password is right or wrong.(informIT, n.d.)
Figure 2-If else statement
1.7.1.3. Switch Statement
The switch selection statement performs one of many different actions, by using integer or a
char expression. Switch selection can be used to select one option among many different
options. Select one action through this group of actions in employee’ record such as save,
take, edit and delete can be used. (informIT, n.d.)
Figure 3-Switch Statement
24

1.7.2. Repetition
Repetitive expressions are called loops and are used to repeat the same code several times in
succession. Repetition is the idea of repeating the same words or phrases several times to
make
it clearer and more memorable. Several types of repetition are widely used in both prose and
poetry. The number of repetitions is based on the criteria defined in the loop structure,
usually
a true / false expression.
 Repetition allows the programmer to efficiently use variables
 Can structure programming statements to be repeated as long as specific conditions
are met
 There are three looping structures in C++: 1. while loop, 2. for loop, and 3. do...while
Loop
 Mnemonic: "ALL loops must have ITU"--Initialize, Test, Update
 For example: can input, add, and average multiple numbers using limited number of
variables (cs.fsu.edu, n.d.)
1.7.2.1.While Loop
A while loop is the most common type of loop. The main feature of the time loop is that it
repeats a set of instructions based on the condition. As long as the loop returns a Boolean
value
of truth, the code in it will repeat. We often use loops like this when we don't know exactly
how many times a code should run. (tutorialspoint, n.d.)
25

Figure 4-While Loop
26

1.7.2.2. For Loop
The method of the program used in this configuration statement is executed only once at the
beginning, and the expression test is evaluated. If the test expression is incorrect, the loop is
terminated. But if the test expression is correct, the symbols inside the loop text will be
executed and the refresh expression will be updated. (tutorialspoint, n.d.)
Figure 5-For Loop
1.7.3. Sequence
A sequential structure, action and event is directed to the next ordered action in a
predetermined
order. The sequence can contain any number of actions, but no actions can be omitted in the
sequence. When the program is running, each action must be performed without the ability to
skip or join another action.All logical problems in programming can be solved by developing
algorithms using only threelogical structures and combining them in an infinite number of
ways. The complexity of thestructure is more complex than the computing requirements.
In the following diagram, the c ++ program is encoded using the sequential structure.
27

Figure 6-Example for Sequence
1.8 Fundamental Data Types
Variable values are stored somewhere in an undefined location in the computer's memory
such
as zeros and others. It can save numerical numbers, letters, words, etc., as well as a C ++
program that is able to store history in a .txt file and a .dat file. There are many species in
their
classification.
1.8.1. Character types
They can be a single character. Like a ‘A’, ‘@’, etc. The basic type is char mostly one-byte.
That’s basic character type in used the C++ Char, char16_t, char32_t, varchar
1.8.2. Numerical integer types
They can store a total number value, such as 6 or 999. They are in different types of sizes,
and
each of them can be signed or unsigned, depending on the negative values that are not
supported
or not.These variables can be defined as short int, int, long int, long int, etc.
1.8.3. Floating-point types
It can represent actual values, such as 10.25 or 0.025, not the same resolution levels,
depending
on the floating-point types used. More than the variable can be defined as floating-point types
such as float, double, double, long, etc.
1.8.4. Void types
Encrypted program code in the blank, they can at any time call the function and any place in
the main function code is called the program easily. Therefore, the entire program code can
be
collected separately
28

Task 02 - SRS Document for Light Up
Electricity Corporation
2.1. System Requirement Specification of Light Up Electricity
Corporation System
2.1.1. Purpose
The target of this undertaking is to create autonomous software for Light Up Electricity
Corporation Management System.There is a logging interface for overseeing leading group of
the employee and customer. Customer can pick the for which they have the sorts of Print
bill.
The proprietor of Light Up Electricity Corporation has the office of enlisting employee, and
the obligation of employee inside the day and a record of the salary got during the day.
2.1.2 Scope
Right now, segment centres on how the framework favours individuals who profit by this
framework and what offices and offices they have to get to the framework.This spotlights on
finishing all the prerequisites, consequently making the capacity to handilyserve patients. The
proprietor will focus on make the important necessities as simple as could be expected under
the circumstances. The framework makes a current arrangement of Increment in income,
Permitting the proprietor to win more salary. It is likewise feasible for purchasers to utilize
their own innovation to address their own issue sand this offers them the chance to
accomplish their own needs. The proprietor of the venture has the chance to utilize his own
innovation with present day innovation.
2.1.3. Overview
The initial segment of this note portrays the capacities performed by this task and afterward
how to arrive at it and how it will be executed in the last stage.
2.1.4. Overall Description
It gives a short depiction of the product that was made as a response to an issue routed to this
business foundation. This product can be utilized by the entrepreneur and purchasers.
29

customer can pick the employees for their applicable bill. They can make instalments without
utilizing money notes.
2.1.5. Product Perspective
This software is basically specialized for Light Up Electricity system. This software can be
developed by software developers in a proper way. Software developers can add the details.
2.1.6. Product Functions
We can use this software for getting know about consultants and registration of customer by
giving details. As a result of these things we can develop the relationship between customers
and employees as well as board of management of Light Up Electricity Corporation.
2.1.7. User Characteristics
Administrator can separate and supervise direct on customer and employee. customer can
instruct the bumbles in regards to the bill & units and framework errors or experts' direct. So,
administrator can change the framework, authority and fix the units & bills.
2.1.8. Assumptions and Dependencies
This software is specialized Light Up Electricity Corporationsystem. customers can connect
with Light Up Electricity Corporationsystem by giving details to the management system. On
the other hand, we can get a feedback of customers to develop the process of Light Up
Electricity Corporationsystem.
2.1.9. Requirements
There are functional and non-functional requirements identified to the Light Up Electricity
Corporation systemapplication. According to the overall system, users and admins the
functional requirementshave listed below and according to the safety, security, interface,
operation, maintenance andperformance is listed below after the functional requirements.
2.1.10. Functional Requirements
This section presents the functional requirements identified for the company. Standard
specifications were initially made for the entire system. The further requirements were
limited,
30

where possible, based on their relevance to the system users.
2.1.11. System Requirements
Below is an example of minimum versus recommended system requirements for a Windows
application.
1. OS: Windows XP with SP1; Recommended: Windows 10
2. CPU: Intel or AMD processor with support; Recommended: 2.8 GHz or faster
processor
3. Disk Storage: 4 GB of free disk space
4. Monitor Resolution: 1280x800; Recommended: 1920x1080
2.1.12. Non-functional requirements
Non-functional requirement (NFR) is a requirement that defines rather than specifies
behaviors, parameters that can be used to test process operations. These are in addition with
specific conditions that describe individual actions or functions.
1. Usability
2. Reliability
3. Performance
4. Supportability
5. Maintainability
6. Availability
7. Security
8. Legal
2.1.13. Schedule Representation
Scheduling the project tasks is an important project planning activity. It involves deciding
which tasks would be taken up when. In order to schedule the project activities, a software
project manager needs to do the following this rule.
31