ICT40115 Assignment 1: Software Development Case Study and Questions

This assignment, designed for a Certificate IV in Information Technology course, presents a comprehensive analysis of a software development case study. It encompasses multiple tasks, starting with identifying stakeholders within a dental practice scenario. The assignment then moves on to creating a Gantt chart for project planning, change negotiation based on provided issues, and evaluating quality objectives. Further tasks include variance reporting, requirements specification, and standards documentation. The student addresses quality objectives, reviews implementation standards, and defines acceptance criteria. The assessment also involves the application of software metrics, reporting on milestones, and answering multiple-choice and true/false questions related to system development methodologies, including the SDLC, project management, and software quality. The assignment demonstrates understanding of various software development concepts and their practical application.

Running head: ASSIGNMENT 1
Assignment 1: Case Study and Questioning
Name of the Student:
Name of the University:

1ASSIGNMENT 1
Table of Contents
Task 1: Identify stakeholders.....................................................................................................2
Task 2: Gantt chart.....................................................................................................................2
Task 3: Change negotiation........................................................................................................2
Task 4: Quality...........................................................................................................................3
Task 5: Variance reporting.........................................................................................................4
Task 6: Requirements specification...........................................................................................5
Task 7: Standards document......................................................................................................5
Task 8: Quality objectives..........................................................................................................5
Task 9: Reviewing and reporting on implementation standard.................................................6
Task 10: Acceptance criteria......................................................................................................6
Task 11: Software metrics..........................................................................................................6
Task 12: Report milestones and metrics to ensure written agreement.......................................7
Task 13: Multiple choice questions............................................................................................7
Task 14: True-false questions....................................................................................................8
References................................................................................................................................10

2ASSIGNMENT 1
Task 1: Identify stakeholders
Person Type of stakeholder
Peter Smith Supplier
Keith Dickson Staff
Mrs Mary O’Halloran Client
Brian Huang Staff
David Andrews Supplier
Pauline Santoro Staff
Task 2: Gantt chart
ID Task Name Duration Start Finish Predecessors Resource Names
1 Feasibility study 12 wks Mon 03-02-20Fri 24-04-20 Jill,John
2 Analysis requirement8 wks Mon 03-02-20Fri 27-03-20 Larry ,Louise
3 Design solution 5 wks Mon 27-04-20Fri 29-05-201,2 Mark
4 Develop system 10 wks Mon 01-06-20Fri 07-08-203 James,Jane,Jeff,Julie
5 Testing 10 wks Mon 01-06-20Fri 07-08-203 Bella,Brad,Brenda
6 Deployment 5 wks Mon 10-08-20Fri 11-09-204,5 Tony
7 Milestone:
Completion of
project plan
0 wks Fri
11-09-20
Fri
11-09-20
6
Jill,John
Larry ,Louise
Mark
James,Jane,Jeff,Julie
Bella,Brad,Brenda
Tony
11-09
F S S M T W T F S S M T W T F S S M
17 Nov '19 19 Jan '20 22 Mar '20 24 May '20 26 Jul '20 27 Sep '20 29 Nov '20 31 Jan '21 04 Apr '21
Figure 1: Gantt chart
(Source: Created by author using Ms Project)
Task 3: Change negotiation
Based on email send by Peta Young, following issues are identified as:
a. Issues regarding tracking of the open class cases for I-CUE project

3ASSIGNMENT 1
b. Improper cost estimation for the project as extra cost of beta testing is not included in
the cost estimation plan
Those two above issues ate to be handled by changing in the operational procedures
rather than implementing technical solutions to the issues. There should require to determine
the project cost by estimating all possible project expenses.
Based on email send by Bob Jenkison, following issues are identified as:
a. Issues regarding tracking of the open class cases for I-CUE project
b. Lack of follow-up of the customer services
There should require to handle those issues by taking follow-up from the case
worker’s supervisor. It should help to save thousands of dollars of the company and lead to
improve over the customer services.
Task 4: Quality
Based on Intuitive Contracts, Updates and Enhancements Project, the main quality
stakeholders identified are Peta Young and Bob Jenkison.

4ASSIGNMENT 1
Task 5: Variance reporting
Task Name Plan Actual Variance
Developing total $19,99,532.00 $29,51,052.00 -$9,51,520.00
Update risk assessment $492.00 $492.00 $0.00
Equipment for development/proof of concept arrives $0.00 $0.00 $0.00
Set up development environment/lab $4,800.00 $4,800.00 $0.00
Initial release #1 $4,22,560.00 $4,22,560.00 $0.00
Develop target components $4,800.00 $4,800.00 $0.00
Test individual components $0.00 $0.00 $0.00
Test integrated application $0.00 $0.00 $0.00
Develop performance enhancement materials $4,480.00 $4,480.00 $0.00
Test and review materials $5,000.00 $5,000.00 $0.00
Develop distribution procedures $4,480.00 $4,480.00 $0.00
Create distribution product $0.00 $4,480.00 -$4,480.00
Distribute to appropriate parties $0.00 $4,480.00 -$4,480.00
Buffer $49,200.00 $49,200.00 $0.00
Internal release #1 complete $0.00 $0.00 $0.00
Review results from internal release $0.00 $0.00 $0.00
Perform post-release review $0.00 $0.00 $0.00
Initial release 2 $4,24,960.00 $4,24,960.00 $0.00
Develop target components $4,800.00 $4,800.00 $0.00
Test individual components $0.00 $0.00 $0.00
Test integrated application $0.00 $0.00 $0.00
Develop performance enhancement materials $4,480.00 $4,480.00 $0.00
Test and review materials $5,000.00 $5,000.00 $0.00
Develop distribution procedures $4,480.00 $4,480.00 $0.00
Create distribution product $0.00 $4,480.00 -$4,480.00
Buffer $49,200.00 $49,200.00 $0.00
Distribute to appropriate parties $4,480.00 $4,480.00 $0.00
Internal release 2 complete $15,680.00 $15,680.00 $0.00
Initial release 3 $0.00 $5,78,560.00 -$5,78,560.00
Develop target components $4,800.00 $4,800.00 $0.00
Test individual components $0.00 $0.00 $0.00
Test integrated application $0.00 $0.00 $0.00
Develop performance enhancement materials $4,480.00 $4,480.00 $0.00
Test and review materials $5,000.00 $5,000.00 $0.00
Develop distribution procedures $4,480.00 $4,480.00 $0.00
Create distribution product $0.00 $4,480.00 -$4,480.00
Buffer $49,200.00 $49,200.00 $0.00
Distribute to appropriate parties $0.00 $4,480.00 -$4,480.00
Internal release 3 complete $0.00 $15,680.00 -$15,680.00
Review results from internal release $32,800.00 $15,680.00 $17,120.00
Functional specification freeze $0.00 $0.00 $0.00
Final feature development $1,04,000.00 $1,04,000.00 $0.00
Final logistics development $15,840.00 $15,840.00 $0.00
Final performance support development $7,600.00 $7,600.00 $0.00
Feature complete $0.00 $0.00 $0.00
Update Plans and Schedules $95,520.00 $95,520.00 $0.00
Update development plan $0.00 $0.00 $0.00
Update testing plan $0.00 $0.00 $0.00
Update logistics plan $0.00 $0.00 $0.00
Update program management plan $0.00 $0.00 $0.00
Update product management plan $0.00 $0.00 $0.00
Update user education plan $0.00 $0.00 $0.00
Buffer $49,200.00 $49,200.00 $0.00
Perform milestone review $32,800.00 $32,800.00 $0.00
Scope complete $15,680.00 $15,680.00 $0.00

5ASSIGNMENT 1
Task 6: Requirements specification
The main functional requirements of program or software are its reliability,
availability, capability and serviceability. The other performance related requirements are its
response time, utilization as well as throughput.
Task 7: Standards document
In the highlighted section such as 3.0 Coding, it includes identification of language as
well as protocols should be used for development of the new application for Sharp Solutions.
Code standards also include details of how codes are required to be documented in addition
to structured (Burhandenny, Aman and Kawahara 2018).
Task 8: Quality objectives
ISO 9000 standard should require to follow for maintaining quality of the software
developed. It documents quality system elements required to maintain quality system (Lewis
2017). It helps the company to meet with client’s requirements, satisfy the customers,
meeting with regulatory needs as well as achieve continual improvements. It deals with how
products are to be delivered and its reliability plus accuracy are also determined (Hoyle
2017). The characteristics of this quality standard are as follows:
i. Understanding requirements of existing customers
ii. Meeting with the client’s requirements and measuring their satisfaction
iii. Evidence based decision making process (Guzman et al. 2017).
iv. Maintaining supplier relations
v. Analysing percentage of products free from quality defects
i.

6ASSIGNMENT 1
Task 9: Reviewing and reporting on implementation standard
Based on the Gantt chart, the project status report 1 indicated how the project work is
performing. It helps to determine the project status and its current progress in relation to the
planned schedule. The status report also provides information on what changes are required
in the Gantt chart, what activities are more important to complete work on scheduled
timeframe (Chandra et al. 2018). Before starting new status report, this report provides with
the end date of the plan.
Task 10: Acceptance criteria
The acceptance criteria for the software development project based on business,
functional and technical requirements are as follows:
 Communicate with the technical service provider to determine technical solutions
required for meeting with customer’s demands and requirements
 Gain agreement with the project stakeholders (Hoda and Murugesan 2016).
 Providing an input for the next phase of the software development project work
 Describing if the software solution meet with the customer’s needs or not
 Pre-established standards and requirements of the project should require to meet
(Alahyari, Svensson and Gorschek 2017).
 Providing guidelines for the user centered viewpoints
Task 11: Software metrics
The metrics which used to measure performance of the software development project
are as follows:

7ASSIGNMENT 1
Lead time: It determines time require to deliver the software idea. In order to become
responsive to the customers, it is required to reduce lead time by lessening of wait time
(Fontdevila, Genero and Oliveros 2017).
Cycle time: It determines time required to make possible changes in the software
system as well as deliver changes in production (Alakus, Das and Turkoglu 2019). By means
of using continuous delivery, the cycle time is to be measured in minutes or seconds.
Team velocity: It determines units of software the team can complete in one sprint.
The number is used for planning iterations (Tonelli et al. 2018). Making proper velocity in
goal determines value of estimation in addition to project planning.
Open and close rates: It determines number of production issues being reported as
well as closed in particular period of time (Behutiye et al. 2019).
Task 12: Report milestones and metrics to ensure written agreement
The possible actions which are taken for testing situation are using crash rate for the
application. It helps to determine crash rate by dividing number of application failed by total
number of times used. Open and close rate is used to determine the production issues reported
and closed (Meredith, Mantel Jr and Shafer 2017). Finally, lead time metrics should use to
determine time require to deliver the software idea.
Task 13: Multiple choice questions
1) Answer – c) System development life cycle
2) Answer – c) IT Manager
3) Answer – d) Analysis phase
4) Answer – a) Rapid application development (RAD)
5) Answer – a) Rapid application development (RAD)

8ASSIGNMENT 1
6) Answer – e) both b and d
7) Answer – a) A reasonable approach when requirements are well defined.
8) Answer – a) A reasonable approach when requirements are well defined.
9) Answer – c) Includes project risks evaluation during each iteration
10) Answer – c) Removes need to consider performance issues
11) Answer – e) a, b, and c
12) Answer – e) both a and d
13) Answer – e) a, b and d
14) Answer – e) both a and b
15) Answer – d) uncover errors in software work products
16) Answer – e) both a and d
17) Answer – c) what was reviewed, who reviewed it, what were the findings
18) Answer – b) to evaluate them
19) Answer – c) to make strategic changes to the software process
20) Answer – a) LOC is easily computed.
Task 14: True-false questions
1) True
2) False
3) True
4) False
5) True
6) True
7) False
8) True
9) True

9ASSIGNMENT 1
10) False
11) True
12) True
13) True
14) False
15) False

10ASSIGNMENT 1
References
Alahyari, H., Svensson, R.B. and Gorschek, T., 2017. A study of value in agile software
development organizations. Journal of Systems and Software, 125, pp.271-288.
Alakus, T.B., Das, R. and Turkoglu, I., 2019, September. An Overview of Quality Metrics
Used in Estimating Software Faults. In 2019 International Artificial Intelligence and Data
Processing Symposium (IDAP) (pp. 1-6). IEEE.
Behutiye, W., Karhapää, P., Lopez, L., Burgués, X., Martínez-Fernández, S., Vollmer, A.M.,
Rodríguez, P., Franch, X. and Oivo, M., 2019. Management of quality requirements in agile
and rapid software development: a systematic mapping study. Information and Software
Technology, p.106225.
Burhandenny, A.E., Aman, H. and Kawahara, M., 2018, July. Empirical Analysis of Coding
Standard Violation Focusing on Its Coverage and Importance. In 2018 IEEE 42nd Annual
Computer Software and Applications Conference (COMPSAC) (Vol. 1, pp. 837-838). IEEE.
Chandra, S., Erlina, E., Maksum, A. and Supriana, T., 2018. Effect of corporate governance
on cost of equity before and after international financial reporting standard implementation.
Fontdevila, D., Genero, M. and Oliveros, A., 2017, November. Towards a usability model for
software development process and practice. In International Conference on Product-Focused
Software Process Improvement (pp. 137-145). Springer, Cham.
Guzman, L., Oriol, M., Rodríguez, P., Franch, X., Jedlitschka, A. and Oivo, M., 2017,
February. How can quality awareness support rapid software development?–a research
preview. In International Working Conference on Requirements Engineering: Foundation for
Software Quality (pp. 167-173). Springer, Cham.

11ASSIGNMENT 1
Hoda, R. and Murugesan, L.K., 2016. Multi-level agile project management challenges: A
self-organizing team perspective. Journal of Systems and Software, 117, pp.245-257.
Hoyle, D., 2017. ISO 9000 Quality Systems Handbook-updated for the ISO 9001: 2015
standard: Increasing the Quality of an Organization’s Outputs. Routledge.
Lewis, W.E., 2017. Software testing and continuous quality improvement. Auerbach
publications.
Meredith, J.R., Mantel Jr, S.J. and Shafer, S.M., 2017. Project management: a managerial
approach. John Wiley & Sons.
Tonelli, R., Destefanis, G., Marchesi, M. and Ortu, M., 2018. Smart contracts software
metrics: a first study. arXiv preprint arXiv:1802.01517.