SBM4201 System Analysis and Design: High-Quality Institute Report 2018

This report presents a comprehensive system analysis and design for the High-Quality Institute (HQI) project, focusing on the development of Undergraduate Learning System (ULS) and Postgraduate Learning System (PLS). It covers the System Development Life Cycle (SDLC) using the waterfall model, detailing phases from analysis and feasibility to maintenance. The report includes a Work Breakdown Structure (WBS) with task descriptions and durations, a PERT/CPM chart for project scheduling, an Entity-Relationship (ER) diagram for database design, and a cost-benefit analysis demonstrating a payback period of approximately 2.3 years. The analysis provides a complete overview of the software development process, budget, and schedule for the organization.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student:
Name of the University:
Author Note

2
SYSTEM ANALYSIS AND DESIGN
Introduction
The system development procedure is very important for any type of organization.
The report henceforth is concerned with the case study of the high quality institute. The
organization is looking to develop a system that would be helpful in their organization
procedures. The organization is looking to incorporate two systems within the development
which are the Undergraduate Learning System (ULS) and Postgraduate Learning System
(PLS).
The detailed description of both the system which are to be developed in
incorporation are provided in this report. The software developer staff at the IT department
assigned the task of developing both learning systems from scratch.
The report consists of the information about the system development lifecycle of the
software and also the work Breakdown structure of the development of the project,
Additionally the ER Diagram associated with the development and the cost calculation is also
provided in this report.
The System Development Life Cycle
The system development life cycle is very important for any type of development of
the software is very important. For the current project the waterfall model is selected and the
processes that are involved in the model for the development of the system are; Analysis and
feasibility phase, the planning and requirement phase, design phase, the testing phase, the
deployment phase and the maintenance phase.
For the analysis phase the work should be strong about the deficiency that would be
existing in the current structure for deciding the goals of the new approach. The feasibility
study would also determine if the project goals and other aspects are viable for the

3
SYSTEM ANALYSIS AND DESIGN
organization and the society on a whole or not. In addition to this, the technical personnel of
the organization would also perform the feasibility study on the project so that the technically
the project works for the advancement of the organization. In addition to this, the overall
project scope and the aims and objectives of the project are also defined in this phase of the
development of the software. The economic, external factors and the human resources are
also important which are to be processed during this phase and the schedule is also developed
during this phase.
In the planning and the requirement phase the adaptations for the new system and the
development of the completely new system is developed in this phase. The users’
requirement, hardware and software requirements and the overall capacities of the project are
developed in the planning phase of the development.
In the designing phase the costs of the system and the requirements of the users are
identified and are worked up on. The designing of the front end part and the database
concepts such as the ER diagram and the data model are developed in this phase. After the
planning phase the system development and the implementation of the system starts. The
developers perform the coding and the designing of the system. The back coding and the
integration of the system is done during the implementation phase of the project.
Additionally, the physical configurations and the access control features are also performed
in the implementation phase.
After the implementation phase the testing phase of the project is started. As the
project that is being discussed in this report is a IT oriented project hence, the testing phase
would involve the procedures of the usability testing, the responsive design testing and the UI
testing. After conducting the testing, the users would be providing valuable insights for the

4
SYSTEM ANALYSIS AND DESIGN
further development of the project and this would help the developers to improve the final
product to great extent.
After the implementation phase the project sign off stage would be processed by the
developer and during the sign off phase the documentation about the project and system
manual would be submitted to the owners. The project team would also be dissolved during
this phase.
Work Breakdown Structure (WBS)
The work breakdown structure for the project that is to be completed within the
budget is provided below:
WBS Task Name Duration Start Finish Predecessors
0 Teaching and Learning 95 days
Thu 18-10-
18
Wed 27-02-
19
1 Project Initiation 4 days
Thu 18-10-
18
Tue 23-10-
18
1.1
Meeting with the
college authority
1 day
Thu 18-10-
18
Thu 18-10-
18
1.2
Meeting for budget
allocation
1 day Fri 19-10-18 Fri 19-10-18 2
1.3
Project team
compilation
2 days
Mon 22-10-
18
Tue 23-10-
18
3
2 Analysis of the system 3 days Wed 24-10- Fri 26-10-18

5
SYSTEM ANALYSIS AND DESIGN
18
2.1 Feasibility Study 1 day
Wed 24-10-
18
Wed 24-10-
18
4
2.2
Decide on the aims
and objectives of the
project
1 day
Thu 25-10-
18
Thu 25-10-
18
6
2.3
Allocation of budget
for the project
1 day Fri 26-10-18 Fri 26-10-18 7,2
3
Planning of the system
development
4 days
Mon 29-10-
18
Thu 01-11-
18
3.1
Development of
project Schedule
1 day
Mon 29-10-
18
Mon 29-10-
18
8
3.2
identification of
Hardware and Software
1 day
Tue 30-10-
18
Tue 30-10-
18
10,7
3.3
Procurement of
Hardware and Software
2 days
Wed 31-10-
18
Thu 01-11-
18
11
4 System Design 8 days Fri 02-11-18
Tue 13-11-
18
4.1
Planning the design of
the Undergraduate
Program
2 days Fri 02-11-18
Mon 05-11-
18
12
4.2 Planning the design of 2 days Tue 06-11- Wed 07-11- 14,11

6
SYSTEM ANALYSIS AND DESIGN
the Postgraduate Program 18 18
4.3
Designing for system
integration
4 days
Thu 08-11-
18
Tue 13-11-
18
15
5
Project
Implementation
52 days
Wed 14-11-
18
Thu 24-01-
19
5.1
System Interface
design
5 days
Wed 14-11-
18
Tue 20-11-
18
16
5.2
Designing Interface
for the undergraduate
program
7 days
Wed 21-11-
18
Thu 29-11-
18
18
5.3
Designing Interface
for the undergraduate
program
7 days Fri 30-11-18
Mon 10-12-
18
19,15
5.4
procurement of the
Student details of the
university
2 days
Tue 11-12-
18
Wed 12-12-
18
20
5.5
Designing the
database for the system
5 days
Thu 13-12-
18
Wed 19-12-
18
21
5.6
Inserting the data into
the database
6 days
Thu 20-12-
18
Thu 27-12-
18
22
5.7 Implementing 3 days Fri 28-12-18 Tue 01-01- 23

7
SYSTEM ANALYSIS AND DESIGN
functions in the database 19
5.8
System back end
development
10 days
Wed 02-01-
19
Tue 15-01-
19
24
5.9 System integration 7 days
Wed 16-01-
19
Thu 24-01-
19
25,20
6 System Testing 8 days Fri 25-01-19
Tue 05-02-
19
6.1 GUI Testing 2 days Fri 25-01-19
Mon 28-01-
19
26
6.2 Usability Testing 1 day
Tue 29-01-
19
Tue 29-01-
19
28
6.3 Compatibility Testing 2 days
Wed 30-01-
19
Thu 31-01-
19
29
6.4
System performance
Testing
2 days Fri 01-02-19
Mon 04-02-
19
30
6.5
Fetch System testing
report
1 day
Tue 05-02-
19
Tue 05-02-
19
31,26
7 System Rebuild 7 days
Wed 06-02-
19
Thu 14-02-
19
7.1
Receive the feedback
of the user
1 day
Wed 06-02-
19
Wed 06-02-
19
32

8
SYSTEM ANALYSIS AND DESIGN
7.2
Analysis of the user
reviews
1 day
Thu 07-02-
19
Thu 07-02-
19
34
7.3
Deployment of minor
fixes in the system
5 days Fri 08-02-19
Thu 14-02-
19
35,31
8 System Deployment 2 days Fri 15-02-19
Mon 18-02-
19
8.1
Upload the system on
the server
1 day Fri 15-02-19 Fri 15-02-19 36
8.2
Hand over the
Administration
credentials
1 day
Mon 18-02-
19
Mon 18-02-
19
38
9 Project Maintain ace 5 days
Tue 19-02-
19
Mon 25-02-
19
9.1
Schedule the project
maintenance
2 days
Tue 19-02-
19
Wed 20-02-
19
39
9.2
Allocate resource for
maintenance
2 days
Thu 21-02-
19
Fri 22-02-19 41
9.3
creating the system
manual
1 day
Mon 25-02-
19
Mon 25-02-
19
42
10 project Sign-Off 2 days
Tue 26-02-
19
Wed 27-02-
19
10.1 Handing over the 1 day Tue 26-02- Tue 26-02- 43

9
SYSTEM ANALYSIS AND DESIGN
system manual and
project documentation
19 19
10.2
Dissolve the project
team
1 day
Wed 27-02-
19
Wed 27-02-
19
45,36
PERT/CPM chart
The Pert chart is generally used for the identification of the early start, late start, early
finish and late finish of the project. The pert chart for the project is provided below:

10
SYSTEM ANALYSIS AND DESIGN
ER Diagram
The ER Diagram for the data that is to be stored in the system is provided below:
Cost Calculation
The calculations for the budget and cost for the implementation of the system is
provided below:
Cost benefit analysis
Year 0 Year 1 Year 2 Year 3 Year 4 Year 5
Value of benefits $0 $7,000 $7,000 $7,000 $7,000 $7,000
Development cost ($20,000) $750 $800 $770 $750 $730
Annual Expenses $0 ($2,000) ($2,000) ($2,000) ($2,000) ($2,000)

11
SYSTEM ANALYSIS AND DESIGN
Net benefit/costs $10,000 $0 $0 $0 $0 $0
Net cash flow ($10,000) $5,750 $5,800 $5,770 $5,750 $5,730
Discount factors
Discount rate 6%
Year Index 0 1 2 3 4 5
Discount factor 1 0.94 0.89 0.84 0.79 0.75
Discounted flows
Cost ($20,000) ($1,887) ($1,780) ($1,679) ($1,584) ($1,495)
Benefit $10,000 $6,604 $6,230 $5,877 $5,545 $5,231
Net ($10,000) $4,717 $4,450 $4,198 $3,960 $3,736
Cumulative ($10,000) ($5,283) ($833) $3,365 $7,326 $11,062
Net present value $11,062
ROI 33%
Payback Analysis
Years Months
1 14

12
SYSTEM ANALYSIS AND DESIGN
Payback Period in Years 2.30
Conclusion
For conclusion it can be said the project development would be done using the
waterfall model and the budgeting and the schedule of the project is done according to the
waterfall model. The schedule of the project indicates that the project can be completed in the
95 days and the payback period is calculated to be 2.3 years approximately. Hence, the report
provides the entire details of the development of the software by the organization.