System Analysis and Design: Project Management and Strategy Report

This document presents a comprehensive system analysis and design project plan, focusing on the development of an IT project for Total Software Service Pvt Ltd. It includes a time management plan with a work breakdown structure and Gantt chart, a comparison of the 'TO BE' and 'AS IS' processes, and an entity-relationship diagram. The report further covers data normalization, system testing methodologies (black box and white box), staff training, and system changeover strategies. The importance of project management in ensuring client satisfaction and delivering value is highlighted, concluding with a report to management emphasizing the significance of the project management plan.

SYSTEM ANALYSIS AND DESIGN

Table of Contents
Introduction......................................................................................................................................3
Assignment 2...................................................................................................................................4
Task 1...............................................................................................................................................4
Time management Plan...................................................................................................................4
2.1. Work Breakdown Structure......................................................................................................4
2.2. Task-Sequencing Approaches..................................................................................................5
Gantt chart.......................................................................................................................................7
Task 2...............................................................................................................................................8
TO BE process.................................................................................................................................8
Task 3...............................................................................................................................................9
Comparing TO BE and AS IS process............................................................................................9
Task 4.............................................................................................................................................10
Entity relationship Diagram...........................................................................................................10
Task 5.............................................................................................................................................10
Data normalization.........................................................................................................................10
Task 6.............................................................................................................................................12
Testing...........................................................................................................................................12
Task 7.............................................................................................................................................13
Training..........................................................................................................................................13
Task 8.............................................................................................................................................13
System Changeover.......................................................................................................................13
Task 9.............................................................................................................................................14
Report to management...................................................................................................................14
Conclusion.....................................................................................................................................14
References......................................................................................................................................16
2

Introduction
System, analysis and project design is a vital activity for an IT based company in order to create
products according to client’s demand. In this study, the time management plan for software
development of an IT project has been mentioned. The study also includes the TO BE process
and its comparison to AS IS Process in respect to an IT company names Total Software service
Pvt ltd has been mentioned. The presentation of entity relationship diagram, grand chart of time
management plan has been also mentioned in the study. The study also produces report to the top
management mentioning the reason behind the preparation of project management plan in order
to get the clients satisfied with the IT services.
3

Assignment 2
Task 1
Time management Plan
2.1. Work Breakdown Structure
4

Figure 1: Work Breakdown structure
(Source: Created by author)
2.2. Task-Sequencing Approaches
ID Task Name Duration Start Finish Predecessors
5
EcommerceonTotalsoftwareservicesMarketingviamessageDesigningdetailedtemplateSMScontentwritingTrackingofcustomerbehaviourAssessingthecustomersMarketingofEmailEmailTemplateWritingdownEmailcontentDesigninganemailEmailSendingTrackingofcustomerbehaviourAssessingthecustomersWebinarDevelopingwebtutorialsDevelopinglabtutorialsArrangingwebinarTrackingofcustomerbehaviourAssessingcustomers

1 Ecommerce on CloudPlex 60 days Tue 5/22/18 Mon
8/13/18
2 SMS Marketing 16 days Tue 5/22/18 Wed 6/6/18
3 SMS Template Detailed Design 4 days Fri 6/8/18 Thu
6/14/18
4 Writing down SMS Content over
the Template
4 days Wed 5/23/18 Tue
5/29/18
20
5 SMS Sending to the customers 2 days Wed 5/30/18 Thu
5/31/18
4
6 Customers' behavior tracking 3 days Fri 6/1/18 Wed 6/6/18 5
7 Assessing the customers and
competitors
3 days Thu 6/7/18 Tue
6/12/18
6
8 Email Marketing 21 days Wed 6/13/18 Wed
6/20/18
7
9 Email Template Detailed Design 4 days Thu 6/21/18 Fri 6/29/18 8
10 Writing down Email content over
the template
4 days Mon 7/2/18 Tue 7/3/18 9
11 Designing an email campaign 3 days Wed 7/4/18 Fri 7/6/18 10
12 Email Sending to the customers 3 days Mon 7/9/18 Tue
7/10/18
11
13 Customers' behavior tracking 4 days Wed 7/11/18 Fri 7/13/18 12
14 Assessing the customers and the
competitors
3 days Mon 7/16/18 Wed
8/15/18
13
15 Webinar or Massive Open Online 23 days Thu 8/16/18 Thu 14
6

Course (MOOC) 8/23/18
16 Developing web tutorials and
deploy
5 days Fri 8/24/18 Thu
8/30/18
15
17 Developing lab tutorials sessions
for customers
6 days Fri 8/31/18 Tue 9/4/18 16
18 Arranging webinar 5 days Wed 9/5/18 Fri 9/7/18 17
19 Customers' tracking on the
website
4 days Mon 9/10/18 Wed
9/12/18
18
20 Assessing customers and the
competitors
3 days Tue 5/22/18 Tue
5/22/18
21 Project Closure 1 day Tue 5/22/18 Tue
5/22/18
Table 1: Task-Sequencing Approaches
(Source: Created by author)
Gantt chart
7

Figure 2: Gantt chart
(Source: Created by author)
Task 2
TO BE process
Figure 3: TO BE Process by BPMN
(Source: Created by author)
TO BE process can be defined as the state of business process in future in an organisation like
Total Service pvt ltd. Basically the analysis of the TO BE process is to put the future state of the
business into work to know how the organisation can work in future at the same point of time in
future when the changes are made. Under the Total Software Service pvt ltd these changes can
be technological change or the change of business process. Since this process of TO BE is
complete part of a project it always needs a lead team of stakeholders who knows the entire
business analysis process (Rittinghouse and Ransome, 2016, p.21). In an organisation like Total
Software Service pvt ltd the stakeholders with their team can start the project by analyzing the
8

objective of the project and with its documentation. When these processes are applicable to the
organisation it seems very overwhelming but after the work done a small improvement can be
seen. After few weeks or months when there is a large scale process several improvements take
place through which the technical process of the organisation like Total Software Service pvt ltd
change. Under this TO BE process all the section of work are typically analyzed.
Task 3
Comparing TO BE and AS IS process
Piraghaj et al. (2016, p.410) stated that basically the process of AS IS based on the combination
of system where people, process, technology and data that are currently performing in the task
and function of system under the study. The system AS IS is may or not used in the computers.
On the other hand, TO BE system is the process where the system where analysis is made in the
current process of the orgsanisation to know the changes is to be made in the future process. In
the TO BE system is combination of people, process data and technology that can be performed
in the required task and function of system in the study.
According to Sheikhi et al. (2015, p.1007), basically the TO BE process analyze the future state
of the organisation, in other word it can also be explained that the organisation’s process, culture
and capabilities in the future. Whereas the AS IS system only describes the present condition of
the process, culture and capabilities. The main objective of the AS IS system is to improve the
need and the changes to be made in the starting point. On the hand the main objective of TO BE
process is to analyze and solve the problem to get better outcome in the future.
9

Task 4
Entity relationship Diagram
Figure 3: Entity relationship Diagram
(Source: Created by author)
Task 5
Data normalization
Project topic Methods Final actions
SMS marketing SMS Template
Detailed Design
Writing down SMS
Content over the
Customers' behavior
tracking
Assessing the
customers and
10

Template
SMS Sending to the
customers
competitors
Email Marketing
Email Template
Detailed Design
Writing down Email
content over the
template
Designing an email
campaign
Email Sending to the
customers
Customers' behavior
tracking
Assessing the
customers and the
competitors
Table 2: ERP
(Source: Created by author)
Data normalization is a typical process of refinement after the exercise of work is done initially
to identify the data object that is a relational database. The main objective of this process is to
identify and analyze the relationship in a table form with defining it in a column within each
table. In a particular organisation like Total Software Service pvt ltd the database can hold
several number of information. This information can be count in millions or billions. Therefore
data normalization helps in reducing its size and also prevents from the data duplication. It
process ensures each piece of data in stored safe and securely (Zhang et al. 2014, p.167).
Application developers in an organisation like Total Software Service pvt ltd that have to create
the application process they find this process of normalization easier to deal with the database. In
this process the of data normalization it can be accessed more logically. This process is often
similar to the process of in which real world objects are basically designed in an organisation.
Under the process of data normalization it reduces the data redundancy which is an important
application for the developers because it is difficult to store the object in relational database
which maintain the same information in several places.
11

Task 6
Testing
Figure 4: White box and black box testing
(Source: Kumar et al. 2014, p.111)
According to Kumar et al. (2014, p.111), system testing is a method of examining the efficiency
of a newly created IT based system that helps in delivering required service to customers. The
system test is methodical phenomenon to get the outcome of a newly launched system for its
clients. The system developer follows black box and white box system testing in order to identify
the internal functionality of the system. Black box testing is considered to be a method of system
testing that examines the functionality of an application without peering into its structures. In this
test, implementation details, knowledge of internal paths of the software and the internal code
structure gets tested in an application.
White box testing is another type of testing that is more important and it includes the transparent
testing so as to get an idea about the outcome of the application of software. As stated by
Moreno-Vozmediano et al. (2017, p.46), it is also important to mention that the testing can help
in getting about the internal functionality of the new developed software. The functionality of the
software is also important for the client so that it can efficiently increase the efficiency of the
application for better performance.
12