Project Management of DAD Project

The project is a comprehensive DAD (Disciplined Agile Delivery) project that aims to design and implement a software system within a specific timeframe and budget. The project involves several milestones, including project initiation, requirement analysis, procurement analysis, design, implementation, testing, and closure. The project has several resources, including hardware, software, and personnel with different skill sets and rates. The project also requires the creation of various diagrams, such as Gantt charts, work breakdown structures, process maps, data flow diagrams, and relational database structures.

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

1
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Gantt chart.......................................................................................................................................2
Narrative table.................................................................................................................................4
Process Maps...................................................................................................................................5
Sales Order...................................................................................................................................5
Cash Receipts...............................................................................................................................5
Data flow diagrams..........................................................................................................................6
Context data flow diagram...........................................................................................................6
Physical data flow diagram..........................................................................................................6
Level 0 - logical data flow diagram.............................................................................................7
Systems flowcharts..........................................................................................................................8
REA Entity-Relationship Diagram..................................................................................................9
Relational database structure...........................................................................................................9
Self and Peer Assessment of Contribution to the Team Project......................................................9
Overall company professionalism...................................................................................................9
Bibliography..................................................................................................................................10

2
SYSTEM ANALYSIS AND DESIGN
Gantt chart
Project Timeline
WBS Task Name Duratio
n Start Finish Predecessor
s Resource Names
0 DAD Project 129
days?
Mon
8/31/15
Thu
2/25/16
1 Project Initiation 2 days Mon
8/31/15
Tue
9/1/15
1.1 Project proposal 1 day Mon
8/31/15
Mon
8/31/15 Abby, Emma
1.2 Project approval 1 day Tue
9/1/15
Tue
9/1/15 2
2 Project Requirement analysis 5 days Wed
9/2/15
Tue
9/8/15
2.1
Identification of the
functional and non-functional
requirements
4 days Wed
9/2/15
Mon
9/7/15 3 System analyst
2.2 Analysis of the proposed
system 1 day Tue
9/8/15
Tue
9/8/15 5 System analyst
3 Project procurement analysis 8 days Wed
9/9/15
Fri
9/18/15
3.1 Procurement of the
required equipments 3 days Wed
9/9/15
Fri
9/11/15 6 Hardware[1]
3.2 Analysis of the procured
items 5 days Mon
9/14/15
Fri
9/18/15 8 Software[1],System
analyst
4 Project Design 42 days Mon
9/21/15
Tue
11/17/15
4.1 Front End Design for the
Project 9 days Mon
9/21/15
Thu
10/1/15 9 frontend designer
4.2 Database Design for the
Project 12 days Fri
10/2/15
Mon
10/19/15 11 database designer
4.3 Backend Design for the
Project 21 days Tue
10/20/15
Tue
11/17/15 12 backend designer
5 Project Implemenation 64 days Wed
11/18/15
Mon
2/15/16
5.1 Front end implementation 30 days Wed
11/18/15
Tue
12/29/15 13 frontend designer
5.2 Database implementation 14 days Wed
12/30/15
Mon
1/18/16 15 database designer
5.3 Backend implementation 20 days Tue
1/19/16
Mon
2/15/16 16 backend designer
6 Project Testing 4 days? Tue
2/16/16
Fri
2/19/16
6.1 Testing System 1 day? Tue
2/16/16
Tue
2/16/16 17 System analyst
6.2 Implementing minor fixes 3 days Wed
2/17/16
Fri
2/19/16 19
backend designer,
database designer,
Employee, frontend
designer,
Software[1],System
analyst
7 Project Closure 4 days Mon
2/22/16
Thu
2/25/16
7.1 delivering the project 1 day Mon
2/22/16
Mon
2/22/16 20 Abby,Emma,System
analyst
7.2 Documentation of the 3 days Tue Thu 22 System analyst

3
SYSTEM ANALYSIS AND DESIGN
System 2/23/16 2/25/16
Project Milestones
Task Name Duration Start Finish
DAD Project 129
days? Mon 8/31/15 Thu 2/25/16
Project Initiation 2 days Mon 8/31/15 Tue 9/1/15
Project Requirement analysis 5 days Wed 9/2/15 Tue 9/8/15
Project procurement analysis 8 days Wed 9/9/15 Fri 9/18/15
Project Design 42 days Mon 9/21/15 Tue 11/17/15
Project Implemenation 64 days Wed
11/18/15 Mon 2/15/16
Project Testing 4 days? Tue 2/16/16 Fri 2/19/16
Project Closure 4 days Mon 2/22/16 Thu 2/25/16
Project Resources
Resource Name Type Material
Label Initials Group Max.
Units Std. Rate
Hardware Material H $10,000.00
Software Material S $2,000.00
System analyst Work S 100% $1,000.00/hr
frontend designer Work f 100% $800.00/hr
backend designer Work b 100% $700.00/hr
database designer Work d 100% $800.00/hr
Abby Work A 100% $0.00/hr
Emma Work E 100% $0.00/hr
Employee Work E 100% $100.00/hr
Gantt chart and Work Break down Structure for the Project
ID Task Mode WBS Task Name Duration Start Finish Predecessors
0 0 DAD Project 129 days?Mon 8/31/15 Thu 2/25/16
1 1 Project Initiation 2 days Mon 8/31/15 Tue 9/1/15
2 1.1 Project proposal 1 day Mon 8/31/15 Mon 8/31/15
3 1.2 Project approval 1 day Tue 9/1/15 Tue 9/1/15 2
4 2 Project Requirement analysis 5 days Wed 9/2/15 Tue 9/8/15
5 2.1 Identification of the functional and non-functional requirements 4 days Wed 9/2/15 Mon 9/7/15 3
6 2.2 Analysis of the proposed system 1 day Tue 9/8/15 Tue 9/8/15 5
7 3 Project procurement analysis 8 days Wed 9/9/15 Fri 9/18/15
8 3.1 Procurement of the required equipments 3 days Wed 9/9/15 Fri 9/11/15 6
9 3.2 Analysis of the procured items 5 days Mon 9/14/15 Fri 9/18/15 8
10 4 Project Design 42 days Mon 9/21/15 Tue 11/17/15
11 4.1 Front End Design for the Project 9 days Mon 9/21/15 Thu 10/1/15 9
12 4.2 Database Design for the Project 12 days Fri 10/2/15 Mon 10/19/1511
13 4.3 Backend Design for the Project 21 days Tue 10/20/15 Tue 11/17/15 12
14 5 Project Implemenation 64 days Wed 11/18/15Mon 2/15/16
15 5.1 Front end implementation 30 days Wed 11/18/15Tue 12/29/15 13
16 5.2 Database implemenation 14 days Wed 12/30/15Mon 1/18/16 15
17 5.3 Backend implmenetation 20 days Tue 1/19/16 Mon 2/15/16 16
18 6 Project Testing 4 days? Tue 2/16/16 Fri 2/19/16
19 6.1 Testing System 1 day? Tue 2/16/16 Tue 2/16/16 17
20 6.2 Implementing minor fixes 3 days Wed 2/17/16 Fri 2/19/16 19
21 7 Project Closure 4 days Mon 2/22/16 Thu 2/25/16
22 7.1 delivering the project 1 day Mon 2/22/16 Mon 2/22/16 20
23 7.2 Documenation of the System 3 days Tue 2/23/16 Thu 2/25/16 22
Abby,Emma
System analyst
System analyst
Hardware[1]
Software[1],System analyst
frontend designer
database designer
backend designer
frontend designer
database designer
backend designer
System analyst
backend designer,database designer,Employee,fron
Abby,Emma,System analyst
System analyst
W T F S S M T W T F S S M T W T F S S M T W T F
Aug 16, '15 Sep 6, '15 Sep 27, '15 Oct 18, '15 Nov 8, '15 Nov 29, '15 Dec 20, '15 Jan 10, '16 Jan 31, '16 Feb 21, '16

4
SYSTEM ANALYSIS AND DESIGN

5
SYSTEM ANALYSIS AND DESIGN
Narrative table
Sale order
No
.
Entity Employee
Name
Input - Process Activity Output - (sends)
1 Customer Orders products
and quotes
member number
(orally).
2 Sales Dept.
Sales Clerk
Emma Receives
order and
member
number
Checks customer
credit and enters
customer and order
details into machine
Customer and
order details
keyed data.
3 Customer member signs the first
copy of the
sales order
4 Sales Dept.
Sales Clerk
Emma repairs a report of
the total sales
5 Computer The first copy
of Sales order
is sent to the
production
function.
The second copy of
Sales order is sent
to shipping.
The last copy of
sales order is
sent to the billing
department.
6 The
operator
Processes
Order
Stock Release Sends Stock
Release
Cash recipients
No
.
Entity Employee
Name
Input - Process Activity Output - (sends)
1 Mail Clerk Abby Receives
Cheque and
remittance
advice
Reconcile
Documents
Sent Two
copies
2 The
computer
System
Create
Statement
Deliver System
3 Billing
department
Sends Out
Statements
Collects payment
4 Mail Clerk Abby Receives
payment
5 Mail Clerk Remittance Copy Remittance
Advices

6
SYSTEM ANALYSIS AND DESIGN
No
.
Entity Employee
Name
Input - Process Activity Output - (sends)
6 Treasury
Clerk
Receives
Advice
Uses the remittance
Copy
Prepares slip for
deposit
Process Maps
Sales Order

7
SYSTEM ANALYSIS AND DESIGN
Cash Receipts
Data flow diagrams
Context data flow diagram

8
SYSTEM ANALYSIS AND DESIGN
Physical data flow diagram
Level 0 - logical data flow diagram

9
SYSTEM ANALYSIS AND DESIGN
Systems flowcharts

10
SYSTEM ANALYSIS AND DESIGN
REA Entity-Relationship Diagram
Relational database structure
Self and Peer Assessment of Contribution to the Team Project
I played the role of System Analyst for the project. The project was to be designed in
such a way so that the system can be implemented within the required time and also the project
could be completed within the allocated budget. It was also kept in mind during the designing of
the project that the project can generate ample revenue so that the project would be feasible
enough.
Overall company professionalism
The company is a start up and is looking to establish its business. However in process of
establishment the company does not want to adopt any false methods and abide by the rules.
Hence the company wants to maintain a strict professionalism in their business that would be
increasing the accountability of the businesses for the company.

11
SYSTEM ANALYSIS AND DESIGN
Bibliography
Majchrzak, A., Beath, C.M., Lim, R. and Chin, W., 2014. Managing client dialogues during
information systems design to facilitate client learning.
Peppard, J. and Ward, J., 2016. The strategic management of information systems: Building a
digital strategy. John Wiley & Sons.
Galliers, R.D. and Leidner, D.E. eds., 2014. Strategic information management: challenges and
strategies in managing information systems. Routledge.
Stair, R. and Reynolds, G., 2013. Principles of information systems. Cengage Learning.
Pearlson, K.E., Saunders, C.S. and Galletta, D.F., 2016. Managing and Using Information
Systems, Binder Ready Version: A Strategic Approach. John Wiley & Sons.
Venkatesh, V., Brown, S.A. and Bala, H., 2013. Bridging the qualitative-quantitative divide:
Guidelines for conducting mixed methods research in information systems. MIS quarterly, 37(1).