Comprehensive Project Management Analysis: Willowbrook School System

This document presents a detailed project management analysis of an information system designed for Willowbrook School. It begins with a comprehensive overview of system requirements, including scalability issues and data validation processes. The analysis includes essential diagrams such as functional dependency diagrams, context diagrams, and 0-level DFDs, along with lists of data stores and data flows. A memo outlining the importance of leveling and balancing DFDs is also provided. The project further delves into the development phases, from analysis to implementation, detailing tasks, durations, and resource allocation. The document also includes a cost-benefit analysis, payback analysis, and break-even analysis, offering insights into the financial viability of the project. The project covers the use of different modules such as registration, content management, and inventory, for the school. The system aims to automate management processes and reduce errors. The document highlights the importance of data validation and the use of technologies like ASP.NET, C#, and Microsoft Access for the system's development. Finally, the project provides an overview of the proposed system's architecture, outlining its functionalities and features.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
Question Set 1................................................................................................................2
1. List of system requirement.....................................................................................2
2. Scalability issues....................................................................................................2
3. Validation of the information.................................................................................3
4. Functional Dependency Diagram...........................................................................3
5. Context diagram for the new system......................................................................4
6. 0 level DFD for the new system.............................................................................5
7. List of data store and data flows............................................................................5
8. Memo...................................................................................................................12
9. SRS Template.......................................................................................................13
10. RTM Template...................................................................................................13
11. Class Object.......................................................................................................13
12. Object relationship diagram...............................................................................14
14. Use case diagram................................................................................................15
Question Set 2..............................................................................................................16
Answer to Question 1:..............................................................................................16
Answer to Question 2:..............................................................................................21
Answer to Question 3:..............................................................................................28
Bibliography.................................................................................................................29

2
PROJECT MANAGEMENT

3
PROJECT MANAGEMENT
Question Set 1
1. List of system requirement
The system requirement identified for the development of the information system for
Willowbrook are as follows:
a. The records of the students should be handled and the current system should be
upgraded with the implementation of the information system.
b. The system should reduce the operation cost of the current business process and
should be fast and convenient to use
c. A workstation is required to be installed with intel core i3 and 2 Gb Ram and 500
HDD for installation of the application for the development of the information system.
d. Creation of new record for the creation of the new student
e. Deletion of the student record
f. Updating of the record
g. Displaying the data from the student record
h. Searching the record
2. Scalability issues
There are some scalability issues faced during the development of the information
system.
For the development of the information system the scalability and flexibility of the
system should be analyzed. The database should be created by aligning the business needs
and more storage space should be added with the requirement. The system should respond to
the changes occurred in the development of the information system.

4
PROJECT MANAGEMENT
3. Validation of the information
A survey should be performed on the data provided by the student during the
enrollment by checking the phone number and email address provided by the student. For
checking the details of the parents the account of the parents should be checked and the
details should be matched with the details provided by the student during registration.
The validation of the information reduces the errors in the system and helps the
organization to store genuine information and details about the students.
4. Functional Dependency Diagram

5
PROJECT MANAGEMENT
5. Context diagram for the new system

6
PROJECT MANAGEMENT
6. 0 level DFD for the new system
7. List of data store and data flows
The data flows are as follows:
APPOINTMENT DATA
APPOINTMENT LIST
APPOINTMENT REQUEST
APPT DATA
CALL LIST
CALL LIST DATA
CHARGES
STATUS SUMMARY

7
PROJECT MANAGEMENT
CPT CODES
CPT FEE SCHEDULE
FEE AND SERVICE DATA
FEE DATA
STUDENT CHANGE
STUDENT DATA
STUDENT UPDATE
MAILING LABEL DATA
MAILING LABELSMTD PAYMENTS
OFFICE STAFF REPORTS AND OUTPUTS
STUDENT INPUTS
STUDENT PAYMENT
STUDENT REPORTS AND OUTPUTS
PROVIDER APPOINTMENT DATA
PROVIDER CHANGE
PROVIDER CHARGES
PROVIDER DATA
PROVIDER INPUTS
PROVIDER REPORT
PROVIDER REPORT DATA

8
PROJECT MANAGEMENT
PROVIDER REPORTS AND OUTPUTS
PROVIDER UPDATE
REMINDER POSTCARD
REMINDER POSTCARD DATA
SCHEDULED APPT DATA
SCHEDULED SERVICE DATA
SERVICE CHARGE
SERVICE DATA
STATEMENT
STATEMENT DATA
YTD PAYMENTS
The data stores are as follows:
COMPLETED APPT DATA
COMPLETED SERVICE DATA
CPT FEE SCHEDULE
STUDENTS
INSURANCE CARRIERS
MTD CHARGES
MTD PAYMENTS
STUDENTS

9
PROJECT MANAGEMENT
PENDING INSURANCE CLAIMS
PROVIDERS
SCHEDULED APPOINTMENT DATA
SCHEDULED SERVICE DATA
The data elements for each data store are as follows:
COMPLETED APPT DATA (D27)
Data elements:
APPOINTMENT NUMBER
APPOINTMENT DATE
START TIME
END TIME
STUDENT NUMBER
PROVIDER NUMBER
COMPLETED SERVICE DATA (D28)
Data elements:
APPOINTMENT NUMBER
CPT CODE
FEE
CPT FEE SCHEDULE (D18)
Data elements:

10
PROJECT MANAGEMENT
CPT CODE
CPT FEE
PROCEDURE NAME
STUDENTS (D5)
Data elements:
STUDENT NUMBER
STUDENT FIRST NAME
STUDENT LAST NAME
STUDENT ADDRESS
STUDENT CITY
STUDENT STATE
STUDENT HOME PHONE
STUDENT WORK PHONE
INSURANCE CO. NUMBER
EMPLOYER GROUP NUMBER
YTD STUDENT CHARGES
YTD STUDENT PAYMENTS
YTD INSURANCE PAYMENTS
SCHEDULED SERVICE DATA (D26)
Data elements:

11
PROJECT MANAGEMENT
APPOINTMENT NUMBER
CPT CODE
FEE

12
PROJECT MANAGEMENT
Data Flow

13
PROJECT MANAGEMENT
8. Memo
Memo
To: Victoria Owens
From: IT consultant
Cc: File
Date: 09/12/2017
Re: Importance of leveling and balancing a set of DFDs
For the development of the low level diagram the levelling and the balancing techniques
varies. Levelling is applied for the adding details into the diagram until the benchmark is
reached. Balancing is applied in the lower level diagram for maintaining consistency in all
levels of diagram and it includes the inputs and outputs, data flow, data definition and the
description of each of the process involved for the development of the diagrams. The
information are displayed as a single process in case of levelling and more details are added
to each of the processes.

14
PROJECT MANAGEMENT
9. SRS Template
10. RTM Template
11. Class Object
srs-v1.doc
RTM.xls

15
PROJECT MANAGEMENT
12. Object relationship diagram
13. Answer to question 13
There are many classes in the Willowbrook School system that can be grouped into
subclasses such as the registration system of the students.
The data elements should be grouped into sub classes to create a functional module
and develop the modules in parallel and decrease the development time of the project.

16
PROJECT MANAGEMENT
14. Use case diagram

17
PROJECT MANAGEMENT
Question Set 2
Answer to Question 1:
Overview of the Proposed System: A new information system is required to be
development for meeting the requirement of Willowbrook School and automate the
management process for reducing the effort of the employees. The new information system
should include all the details of the students registered and for the development of the
information system the functionality are broken down into different module. The first module
is the registration of the students and the second module is developed for the management of
the contents. The inventory system is used for the management of the inventory such as the
management of the transport, fees, attendance of the students, information of the students,
and transfer of the student. In the developed information system different records regarding
the students are stored in details and the authorization of viewing the detailed information are
categorized according to the level of the employees. The teacher can view the marks and the
attendance of the student. The information system can be used for addition of the student
details by the student themselves and this would reduce the effort of the employees for filling
the excel sheet. The overheads can be minimized and the unnecessary information can be
eliminated for increasing the efficiency of the working procedure. The chances of errors are
also minimized and more information can be stored with the development of the information
system. The administrator have a search facility and improve the look and feel of the
interface and Microsoft visual studio 2012 is used for the development of the information
system. ASP.NET, C# and XML is used for the simplification of the Web based application
and statistical analysis system is used for identification of the sequence. Application
programming is used for the automation of the facilities. Microsoft Access is used for the
development of the database of the information system.

18
PROJECT MANAGEMENT
Task Name Duratio
n
Star
t
Finis
h
Predecesso
rs
Resource Names Cost
Development
of information
system for
Willowbrook
School
63 days Mo
n
30-
10-
17
Wed
24-
01-
18
$50,840.0
0
Analysis
phase of
development
28 days Mo
n
30-
10-
17
Wed
06-
12-
17
$18,560.0
0
Analyzing
system
requirements
22 days Mo
n
30-
10-
17
Tue
28-
11-
17
$11,240.0
0
Conducti
on of
interviews
4 days Mo
n
30-
10-
17
Thu
02-
11-
17
Project
Manager,System
Analyst
$1,760.00
Conducti
on of
7 days Fri
03-
Mon
13-
3 Project Manager $1,680.00

19
PROJECT MANAGEMENT
documentation 11-
17
11-
17
Conducti
ng reviews
8 days Fri
03-
11-
17
Tue
14-
11-
17
3 Designer $1,600.00
Conducti
ng surveys
9 days Tue
14-
11-
17
Fri
24-
11-
17
4 System Analyst $1,800.00
Conducti
ng research
10 days We
d
15-
11-
17
Tue
28-
11-
17
5 Development
Team,Database
Administrator
$4,400.00
Modelling
data and
processes
9 days We
d
15-
11-
17
Mon
27-
11-
17
5 Designer,Software
Engineer,Database
Administrator
$5,400.00
Building in
house of the
system
8 days Mo
n
27-
11-
Wed
06-
12-
6 Development Team $1,920.00

20
PROJECT MANAGEMENT
17 17
System
design phase
22 days We
d
29-
11-
17
Thu
28-
12-
17
$13,440.0
0
Developing
user interface
10 days We
d
29-
11-
17
Tue
12-
12-
17
7 Designer $2,000.00
Data design 14 days We
d
29-
11-
17
Mon
18-
12-
17
7 Database
Administrator
$2,800.00
Designing
new system
architecture
12 days Thu
07-
12-
17
Fri
22-
12-
17
9 Database
Administrator,Design
er
$4,800.00
Outsourcin
g the system to
cloud service
16 days Thu
07-
12-
Thu
28-
12-
9 Project Manager $3,840.00

21
PROJECT MANAGEMENT
17 17
Implementat
ion phase
27 days Tue
19-
12-
17
Wed
24-
01-
18
$18,840.0
0
Installation
of hardware
18 days Fri
29-
12-
17
Tue
23-
01-
18
10 Development Team $4,320.00
Software
installation
19 days Fri
29-
12-
17
Wed
24-
01-
18
10 Development Team $4,560.00
Training
the users
21 days Tue
19-
12-
17
Tue
16-
01-
18
12 Software Engineer $4,200.00
Go live 24 days Tue
19-
12-
17
Fri
19-
01-
18
12 Project Manager $5,760.00
Ongoing
support and
2 days Mo
n
Tue
26-
$0.00

22
PROJECT MANAGEMENT
maintenance
phase
25-
12-
17
12-
17
Stakeholder
sign off
2 days Mo
n
25-
12-
17
Tue
26-
12-
17
13 $0.00
Project
closure
2 days Mo
n
25-
12-
17
Tue
26-
12-
17
13 $0.00
Answer to Question 2:
A cost benefit analysis is done for the development of the information system and
identification of the return of investment of the project.
Cost benefit Analysis
Tangible Benefits
Category In $
Reduction of cost 5000.00
Reduction of Error 3500.00
Increase in flexibility 3000.00

23
PROJECT MANAGEMENT
Increase in activity speed 3500.00
Planning and control improvement 5000.00
Others 5000.00
Total Tangible Benefits 25000.00
Tangible One-Time Costs
Category In $
Total Development Cost 50840.00
New Hardware Cost 10000.00
New Software Cost 8000.00
Cost of Training 5000.00
Cost of preparation of site 5000.00
Others 3000.00
Total Substantial One-Time Costs 81840.00
Substantial Recurring Costs
Category In $
Cost of maintenance of the software 5000.00
Data storage incremental cost 3000.00
Cost of communication 2500.00
Implementation of new hardware /
Software
2500.00
Supply Cost 1000.00
Others 3000.00
Total Substantial Recurring Costs 17000.00
Payback Analysis

24
PROJECT MANAGEMENT
Payback Analysis (Willbrook School Information System)
Benefits of option Year 1 Year
2
Year
3
Year
4
Year 5
Savings from staffs $
9,000
$
9,000
$
9,000
$
9,000
$
9,000
Buying practice improvement $
20,000
$
20,000
$
15,000
$
15,000
$
10,000
Service improvement $
10,000
$
10,000
$
10,000
$
15,000
$
20,000
Total Benefits $
39,000
$
39,000
$
34,000
$
39,000
$
39,000
Costs of option Year 1 Year
2
Year
3
Year
4
Year 5
Cost of development $
50,840
$
-
$
-
$
-
$
-
Cost of implementation of additional
hardware
$
10,000
$
-
$
-
$
-
$
-
Cost of operation $
1,500
$
1,500
$
1,500
$
1,500
$
1,500
Time taken for the development of the
software
$ - $
-
$
-
$
-
$
-
Cost of maintenance $
1,000
$
1,000
$
1,000
$
1,000
$
1,000
Total Costs $
63,340
$
2,500
$
2,500
$
2,500
$
2,500

25
PROJECT MANAGEMENT
Net benefits/costs $
(24,340)
$
36,500
$
31,500
$
36,500
$
36,500
Cumulative benefits/costs $
(24,340)
$
12,160
$
43,660
$
80,160
$
116,66
0
Break Even Period 2.3132530
1
1 2 3 4 5
$(40,000)
$(20,000)
$-
$20,000
$40,000
$60,000
$80,000
$100,000
$120,000
Payback Analysis
Net benefits/costs
Cumulative
benefits/costs
Year

26
PROJECT MANAGEMENT
ROI
Break Even Analysis
Costs of Existing System Year 1 Year
2
Year
3
Year
4
Year 5
Total Cost of development $
-
$
-
$
-
$
-
$
-
Cost of implementation of additional
hardware
$
10,000
$
25,00
0
$
30,00
0
$
35,00
0
$
30,000
Cost of Operation $
10,000
$
10,00
0
$
12,00
0
$
8,000
$
10,000
Time taken for the development of the
software
$
-
$
-
$
-
$
-
$
-
Cost of maintenance $
10,000
$
15,00
0
$
20,00
0
$
30,00
0
$
30,000
Total Cost of the System $
30,000
$
50,00
0
$
62,00
0
$
73,00
0
$
70,000
Costs of Proposed System Year 1 Year
2
Year
3
Year
4
Year 5
Total cost of development $
50,840
$
-
$
-
$
-
$
-
Cot of implementation of the hardware $ $ $ $ $