NATIONAL UNIVERSITY OF LESOTHO

FACULTY OF SCIENCE AND TECHNOLOGY

MINI PROJECT
CS3430
SYSTEMS ANALYSIS AND LOGICAL DESIGN

Lecturer: Likeleli Qhomane-Letsie (PhD)

[email protected]

Instructions:
This assessment requires a group of not more than five (5) students per group.
All outcomes should be completed and submitted within the stipulated time-
frames.
Where submission is late, supporting documentation indicating why the
submission is late should be given to the lecturer.

CS3430 Year 2022/23 Page 1 of 7

 1. Introduction
This mini-project focuses on the process of development of an Information
System (IS) that can benefit the business operations of an organisation. The
purpose of this exercise is to assist students in gaining practical skills (soft skills)
and hone the core skills (technical skills).
The project is a team effort during which each member has the opportunity to get
first-hand experience in not only applying what they have learned to a project that
can support a real life organisation but also gaining valuable knowledge in terms
of group dynamics and business communication.

2. Submission
Submissions will be aligned with the following schedule;
Outcome Description Submission Dates
1 Team and client information as well as project 11 April 2023
proposal. (20 Marks)
2 Product Models (40 Marks) 23 April 2023
3 Design and Testing Specifications (30 Marks) 30 April 2023
4 Prototype (40 Marks) 12 May 2023

3. Outcome Requirements
Outcome 1 – Team and client information
In order to complete Outcome 1 successfully, the following information is
required:
a) Team name and background.
b) Team members’ details (name, surname, student number, e-mail address,
phone number).
c) Who is the client (you have to make an assumption that you have a real
client)
d) Client contact details and background including when the client came into
existence, the business’s objectives, the organizational structure and the
business functions.
e) Proposed System Project scope.
The project scope is clear, explicit and realistic for the purpose of this module.
At a minimum the project scope statement should convey the following

CS3430 Year 2022/23 Page 2 of 7

information:
o The project name.
o The project goals and objectives in terms of the proposed system.
o The project requirements. Divide the requirements into a set of functional
and non-functional requirements.
o The project deliverables (the outcomes).
f) Feasibility study.
The feasibility study should have at least the following sections:
o An economic feasibility section.
o A technical feasibility section.
o An operational feasibility section.
o A schedule feasibility section.
The feasibility study should be concluded by stating whether the project is
feasible considering the various factors associated with each type of feasibility
study.
g) Risk analysis and action plan.
The risk analysis and action plan must be complete, realistic and in the correct
format. Consolidate as many risks as you can e.g. if your team has identified
risks such as scope creep or not finishing the project within time; these risks
can be consolidated into a risk called poor project management. Keep your
risks clear, concise and to the point. Use the following format for your risk
analysis and action plan:

h) Project plan (Gantt/ PERT/ CPM)

The project plan should be presented as a Gantt chart. The Gantt chart should
include all tasks that you will complete to complete the project. The chart should
also indicate who is assigned to which activities. Use MS Project to set up this
Gantt chart, as this will give you the capability of tracking your progress
throughout the project.

CS3430 Year 2022/23 Page 3 of 7

Outcome 2 – Product Model
This outcome requires that the various product models be created and all the
reports required by the client be identified. The students are given the choice
between the object-oriented approach and the traditional or structured approach.
Below is a list of models which needs to be created, depending on the approach
chosen.
Traditional Approach Object-Oriented approach
Context diagram Use Case diagram
Decomposition diagram Activity diagram
DFD Sequence diagram
ERD ERD

The diagrams need to be complete and technically correct.

Reports Identification

Students have to list all reports to be generated by the system. There should be
at least 6 different reports on the list. These reports should be useful and not just
simple lists of tables in your databases. There should be reports that use at least
two or more tables from your database. Use the following example to guide you:
Report Name Report The person the Time
Description report is
intended for
Weekly Sales This report will Manager The report will be
Report provide a generated each
comprehensive Monday on a
list of all the weekly basis
products sold on
each day of the
week

Outcome 3 – Design and Testing Specifications

This unit requires the students to create a design specification for the database
and application as well as provide information regarding help file planning. The
students also have to create testing specifications for the application.

Design specification
a) Design specifications for the database
o Specify the business rules for the business/organisation’s situation
o Full specifications should be provided entities/tables, views for the

CS3430 Year 2022/23 Page 4 of 7

 system and the data dictionary
o Specify the DBMS software to be used and the space it will require on
the client’s hard drive
o Insert normalization
o Insert an updated Entity-Relationship Diagram of the database.

b) Design specifications for the application

o System Processes
Take each process specified in foregoing deliverables and state how it will be
implemented technically. Specifications of each screen which makes up a
process should be provided (i.e. a screenshot and descriptions of every data
item displayed, the sizes of the fonts to be used, and the size of the screens).

o Reporting interface
Provide the specifications of each report to be created by providing
screenshots of each report and specify for each report: the fonts used, the
graphics, the font sizes and font weights, the report size, the tables it reads
from, the dates or logos and positioning thereof etc.

c) Testing specification for application

The test plan for the application should state which features will be tested and
how these features will be tested.
Test type Component Person Test Description
Responsible
Unit test Sales calculator Process analyst Use test data to calculate various
sales transactions and verify the
amounts by calculating total with
another calculator.
Repeat this at least 10 times. The
formula used: sales total = sum
(product cost * quantity) +14%VAT

d) Help file planning

The section on help file planning should contain the following information:
o What technology will be used to create the help file?
o How the help file will function (i.e. type of search functionality, how it will

CS3430 Year 2022/23 Page 5 of 7

 be accessed).
o What will the help file look like?
o What will the help file cover in terms of content? (Functionalities, error
messages, validation etc.)

Outcome 4 – Prototype
a) Database/Application Prototype
o The tables in the database should support the scope of the system
completely.
o Normalization is complete and correct.
o Adequate records are kept
o There is data integrity
b) Add, Edit and Delete
Add: A record can be added. Once the record has been added, a confirmation
message should be displayed. It should be possible to verify that the record has
been added to the database.
Edit: A record can be modified and it can be verified that the record has been
modified in the database. There should be a message confirming the modification
made.
Delete: A record can be deleted from the database. Before deletion, a message
should confirm with the user whether the record should be deleted. A message
should confirm deletion once the operation has been completed. It should be
possible to verify that the record has been deleted from the database.

c) Reports
o It should be easy for the intended user to access and use reports
o The prototype should be able to produce at least 4 relevant reports
o Information contained in the report can be seen and is not truncated
o Correct notation is used to indicate relationships.
o Is there referential integrity?
o Is there entity integrity?

d) Single queries/search
o There should be adequate search facilities to locate specific, single

CS3430 Year 2022/23 Page 6 of 7

 record.
o It should be easy to use the search facilities.
o The result of the query should be displayed in a usable format.

The evaluation of this outcome will be in a form of presentation of the prototype.

Arrangements will be made and communicated in due course with regards to
presentation venue and preparation for this outcome presentation.

CS3430 Year 2022/23 Page 7 of 7