Name: LUKANGA FULGENCE reg.

No: 2018-M132-20028

Author Email: [email protected]

Q1. a) Differences between System Analysis and System Design

System Analysis is the study of a business problem domain to recommend improvements and
specify the business requirements for the solution while System Design is the specification or
construction of a technical, computer based solution for the business requirements identified in a
system analysis.
System analysis is a problem-solving technique that breaks down a system into its component
pieces for the purpose of the studying how well those component parts work and interact to
accomplish their purpose while Systems designs synthesizes system components together as
model, defining its architecture, components, modules, interfaces and data for a system to satisfy
a requirement.
System Analysis deals with understanding and specifying in detail what an information system
should do while System Design specifies in details how the parts of an information system
should be implemented.
System Analysis emphasizes an investigation of the problem and requirements, rather than a
solution while system design emphasizes a conceptual solution (in software and hardware) that
fulfills the requirements, rather than its implementation. For example, a description of a database
schema and software objects.
Similarities between System Analysis and System Design
Both phases (System Analysis and System design) are rigorous and mandatory when coming up
with any information systems.
Both phases require the expertise of a system analyst and the owner of the system to gather and
generate outputs.
Both phases require inputs such as business requirements and previous system.
Both phases are under System Development Life Cycle.

b) Indicators of a bad system

 Unreliability: A bad system doesn’t deliver services as specified – rate of occurrences of
failure is high.
 Difficult to maintain: How is easy is it to maintain it? It is usually hard to make changes
to a bad system after it has been put into operation.
 Low performance: When a bad system is put under “stress”, it will “break”. Bad system
usually don’t pass the rigorous testing phase.

Page 1 of 8
Name: LUKANGA FULGENCE reg. No: 2018-M132-20028

 Difficult to use: How easy is it to navigate, understand the system built? Can a novice
user understand it with a single training or can she/he teach himself? If neither of the
above, them it’s an indicator of a bad system.
 Insecure: A system should be able to protect itself against accidental or deliberate
intrusions. Security includes confidentiality, integrity and availability. It’s a bad indicator
if the system doesn’t offer any of these.
 Unsafe: If the system operates with catastrophic failure, then it’s an indicator of it being
bad.
c) Characteristics of a system.
A system is an orderly grouping of interdependent components linked together according to a
plan to achieve a specific objective.
Below are some of the characteristics of a system
1.  Components: A system is made up of components. A component is an irreducible part or
aggregation of that make up a system, also called subsystems. We can repair or upgrade the
system by changing individual components without having to make changes throughout the
entire system.
2. Boundaries: Every system has defined boundaries within which it operates. Beyond these
limits the system has to interact with the other systems. Example: Personnel system in an
organization has its work domain with defined procedures. If the financial details of an employee
are required, the system has to interact with the Accounting system to get the required details.
3. Interdependence: The components are interrelated. It means that parts of the organization or
computer system depend on one another. They are coordinated and linked together according to
a plan. One subsystem depends on the output of another subsystem for proper functioning
i.e, output of one subsystem is the required input for another subsystem.
4. Feed Back: A feedback may be defined as a check within a system in order to ensure that the 
objectives of the system are achieved. These checks are conducted in order to find out 
deviation. If any deviation is detected, then appropriate steps are taken to ensure 
that the error is rectified. Feedback may be positive or negative.
5. Interface: Interfaces are another important element through which the system interacts with
the outside world. System interacts with other systems through its interfaces. Users of the
systems also interact with it through interfaces.
6. Objective/Purpose: This is the overall goal or function of a system. A system must give
priority to the objectives of the organization as a whole as compared to the objectives of a
subsystem. For example: an organization would have an objective of earning maximum possible
revenues, for which each department and each individual has to work in coordination.
7. An Environment: This is everything external to a system that interacts with the system i.e.
everything outside the system’s boundary, usually the system interacts with its environment, 
exchanging, in the case of an information system, data and information.

Page 2 of 8
Name: LUKANGA FULGENCE reg. No: 2018-M132-20028

d) A systems analyst’s (or business analyst’s) role is to define (or specify) a new or modified
system (usually computer-based). The analyst’s end-product may be called an External System
Design (ESD), Functional Specifications, or Detailed User Requirements.
It must be:
 understood in complete detail and approved by responsible user representatives,
 understood and accepted by prospective developers (or software product purchasers).
A system analyst is a person who uses analysis and design techniques to solve business problems
using information technology (Wikipedia). He identifies the organizational improvements
needed, design systems to implement those changes, and train and motivate others to use the
systems.
System Analyst skills are as follows
Analytical Skills: At the beginning of the project, a system analyst has to understand the
requirements of the client and study the various ways in which the requirements can be met.
He/she should be in position to analyze and understand the problem. If one of the solutions fail to
solve the problem, he/she should be in position to identify alternative solutions and decide a
course of action.
Efficient Planning and Execution Skills: A system analyst is expected to have an eye on detail
and has to plan the various stages in which the project has to be executed. He has to plan by
drawing a skeleton of how the product would look like and noting down possible deliverables.
After defining the plan, he has to make sure the all the details in the plan are adhered to and the
different stages are executed.
Technical knowledge: Since the system analyst is going to work closely with the technical team,
he must poses ample technical skills, from operating systems, programming to hardware
platforms. He will help in coding and debugging when need be.
Interpersonal Skills: system analyst has to have great interpersonal skills and the ability to
manage people. He has to coordinate with the different technical teams and get the product done
as per requirement within the time agreed on.
Ethical Skills: Confidential is crucial when dealing with sensitive information. System analyst
has to keep a non-disclosure agreement of the information for the project he signed up for failure
to do this renders him unethical.
Management Skills: A good systems analyst should be able to evaluate the results, in which
case if the problem is not solved, to return to the drawing board for further system analysis in
which case he has to make a quick decision.

Page 3 of 8
Name: LUKANGA FULGENCE reg. No: 2018-M132-20028

Q2. KASANJE PRISON SYSTEM: Keeping prisoners convicted of only one offense or of
white collar crimes, processing in/out prisoners on a daily basis.
Functional Requirements
i. The system shall record prisoner changes in the prison control center office
ii. The system shall receive the new prisoners’ information
iii. The system shall enable the control officer to generate reports on the new prisoners
iv. The system shall keep a record on physical examination on each prisoner
v. The system shall assign prisoners to living quarters.
vi. The system shall allow the officer to review each prisoner behavior record
vii. The system shall send move information (in form of report) to the control officer
viii. The system shall allow the control officer to be updated on prisoners’ movements.
ix. The system shall have a database to store prisoners’ information.
x. The system shall also generate a set of prisoner to be released
xi. The system shall enable the control officer to generate reports on the prisoners to be
released
xii. The system shall enable The parole board shall to able to review prisoner record
Non-Functional Requirements
i. The system shall generate reports
ii. The system shall have users at different levels, supervisors, control officer
iii. The system shall authenticate users
iv. The system shall notify the officer on the prisoner movement weekly

Q3. FOOD ORDERING SYSTEM

Functional Requirements
i. The system shall allow a Customer to place an Order.
ii. The system shall receive, process and forwards the Order to the Kitchen.
iii. The system shall enable storage of processed orders.
iv. The system shall store updated inventory details.
v. The system shall enable the processes to deliver a Bill to the Customer.
vi. The system shall allow the order inventory process to forward the Inventory order to the
Supplier.
vii. The Manager shall be able to initiate the Order Inventory process.
viii. The Manager shall receive reports from the Inventory details and Order data store
respectively.

Non-Functional Requirements

i. Manager will need to be authorized before they can use the admin interface to
manage the system

Page 4 of 8
Name: LUKANGA FULGENCE reg. No: 2018-M132-20028

ii. The system shall require Manager to login before allowing access to administrator’s
page.

Q4. VIDEO RENTAL SYSTEM

Functional Requirements
i. The system shall receive Video info from the Video Library data store.
ii. The system shall store the Video info into Video library data and store Rental info
into the Rental data store.
iii. The system shall allow the Return Video process to receive Video & Rental
information.
iv. The system shall produce a Bill to the Customer.
v. The system shall generate a Return receipt to the Customer who returns the video.
vi. The Customer shall be able to make a Video request through the Rent Video process
vii. The customer shall provide the Video & Rental Info on returning the video.
viii. The Manager shall receive Rental report using the Generate Rental Report process
from the information involved is provided by the Rental data store.

Q5. SUPERMARKET SYSTEM

Functional Requirements
i. The system shall be able to send hot promotional news to customers.
ii. The system shall allow a Customer to build Shopping List.
iii. The system shall store customers’ shopping list in the shopping-cart.
iv. The system shall be able to retrieve items details from the shopping-cart database.
v. The system shall store item details in the warehouse database.
vi. The system shall enable a customer to search for items.
vii. The system shall enable a Customer to receive Supermarkets' physical location details
by performing Check Locations from the company database.
viii. The system shall enable a Customer to receive Supermarkets' physical location details
by performing Check Locations from the company database.
ix. The system shall enable a customer to view shopping list.

Non Functional requirements

i. The system shall store news in the company database.

Page 5 of 8
Name: LUKANGA FULGENCE reg. No: 2018-M132-20028

Q6. ONLINE AUCTION DATABASE SYSTEM: Members (buyers and sellers) participate in
the sale of items.

Functional Requirements
i. The system shall identify members by a unique member Id
ii. The system shall describe members by an email address, their name, a password, their
home address, and a phone number.
iii. The system shall be able to identify a buyer and a seller.
iv. A member who is a buyer shall possess a shipping address recorded in the database
v. A member who is a seller shall possess a ban, account number and routing number
recorded in the database.
vi. The system shall assign a unique item number to items placed by seller.
vii. The system shall enable seller to place item for sale.
viii. The system shall describe items placed by the seller by an item title, an item
description, a starting bid price, bidding increment, the start date of the auction, and
the end date of the auction.
ix. The system shall allow the buyer to make bids for items they are interested in.
x. The system shall record a bidding price and time of bid placement.
xi. The system shall declare a winner with the highest bid price at the end of the auction.
xii. The system shall allow transaction between the buyer and the seller to proceed soon
after the winner is declared.
xiii. Items shall be categorized based on a fixed classification hierarchy for example a
modem may be classified as COMPUTER/ HARDWARE/ MODEM.

Non Functional Requirements

i. The system shall enable the buyers and sellers to place feedback ratings on the
purchase or sale of an item.
ii. The system shall allow feedback rating between 1 and 10 and a comment on
completed transactions only.
iii. System shall have a database to receive information about members.
iv. The system shall enable authentication of members.
v. The system shall evaluate bids.

Q7. BASEBALL ORGANIZATION DATABASE SYSTEM: The personnel involved in the

league include players, coaches, managers, and umpires.

Functional Requirements
i. The system shall identify a member by a unique personnel ID.
ii. The system shall have a database to store information on Personnel such as players,
coaches, managers, umpires.
iii. The system shall describe each personnel by their first and last names along with the
date and place of birth.
iv. The system shall describe players by other attributes such as their batting orientation
(left, right, or switch) and have a lifetime batting average (BA).

Page 6 of 8
Name: LUKANGA FULGENCE reg. No: 2018-M132-20028

v. The system shall associate pitchers (among the players) with a life time ERA (earned
run average).
vi. The system shall uniquely identify teams by their names.
vii. The system shall describe teams by the city in which they are located and the division
and league in which they play (such as Central division of the American league).
viii. The system shall assign games to be played between two teams with one designated
as the home team and the other the visiting team on a particular date.
ix. The score (runs, hits, and errors) shall be recorded for each team.
x. The systems shall declare the team with more number of runs the winner of the game.
xi. The system shall record number of hits (singles, doubles, triples, and home runs)
obtained by each player after each finished game.
xii. The system shall record a winning pitcher and a losing pitcher after each finished
game.

Non Functional Requirements

i. Teams shall have one manager, a number of coaches, and a number of players.
ii. In case there is a save awarded, the system shall record the save pitcher.

Q8. SMALL PRIVATE AIRPORT DATABASE SYSTEM: To keep track of airplanes, their
owners, airport employees, and pilots
Functional Requirements
i. The system shall identify each airplane by a registration number
ii. The system shall record plane-type.
iii. The system shall describe each plane-type by a model number, a capacity, and a
weight.
iv. The system shall enable each plane-type to be stored in a particular hangar.
v. The system shall describe each hangar by a number, a capacity, and a location.
vi. The systems shall keep track of the owners of each plane and the employees who
have maintained the plane.
vii. The system shall be able to identify a relationship between an airplane to an owner
and includes the purchase date.
viii. The system shall describe a service-record by attributes such as the date of
maintenance, the number of hours spent on the work, and the type of work done
ix. The system shall identify both pilots and employees as subclasses of person.
x. The system shall describe each pilot by specific attributes license number and
restrictions
xi. The system shall describe each employee by specific attributes salary and shift.
xii. All person entities in the database shall have their data kept on their social security
number, name, address, and telephone number.
xiii. The system shall capture data about corporation entities which will include name,
address, and telephone number.
xiv. The system shall record the service record to employee.
xv. The system shall keep track of the types of planes each pilot is authorized to fly and
the types of planes each employee can do maintenance work on

Page 7 of 8
Name: LUKANGA FULGENCE reg. No: 2018-M132-20028

Non Functional Requirements

i. The system shall authenticate user such as plane owners, airport employees, and
pilots

Page 8 of 8