SPM Experiment 9: Activity Network Diagram

SPM Experiment 9
Activity Network Diagram

Project – Exploring Disease Prediction Using Voice Analysis
B. Tech Information Technology – 4th Year
Ajay Dabas
Roll - A-209
SAP -7011118012
1. Develop an Activity Task network required for the project.
2. List the events to be carried out in the project
The execution involves the following milestones/goals that need to be

completed incrementally to ensure a minimum viable product:
1. Creating and completing an acceptable dataset with sufficient

records and essential metrics.
2. To clean the dataset using various libraries available to avoid

overfitting and generalization.
3. To identify and extract features which sway the decision making

of the model/engine i.e., the dominant/deciding factor(s).
4. To engineer and identify the most suitable algorithm for the

model which will give acceptable accuracy with unseen data too.
5. To implement the model and test the model for robustness,
expected accuracy, stakeholder acceptance and concluding the project
with a minimum viable product in accordance with the defined
timeline.
3. Prepare a checklist based on sequence of events

4. Identify the major objectives and their interdependencies
The problem of inaccessible healthcare and diagnosis infrastructure in developing and

under-developed nations is a very real problem in the 21st century. In times as advanced
as today, we expect that all people have access to right diagnosis and adequate healthcare
despite their location. To address this, we have come up with a solution that intends to
create a machine learning engine/model which can be integrated with other sub-systems
to enable inexpensive and reliable diagnosis.
To create a machine learning based project. It analyses voice samples along with other
metrics like the heartrate, blood pressure, gender of a patient to generate unique patient
reports highlighting any ailments (comparing with the data from healthy individuals to aid
in classification) thereby, acting as a diagnostic system enabling remote healthcare
diagnosis in underdeveloped regions.
5. Draw an outline based on start and finish time
The product discussed in the document presents itself as an independent product as of now with
potential to become a component to other larger applications in the future provided the model is
successful/adequate in its function. Presently, the product is a standoff product that will not inherit
anything from existing products. This product in turn will become the key component to be used as
an engine essentially, for future products like a smartphone application or a web-based application.
The product will comprise of a software capable of taking user voice input through a microphone
(preferably in an environment devoid of background noise) and performing a diagnosis to detect
potential diseases with a report print out at the end, highlighting the findings in a report format for
the patient. These will be the functional deliverables which will comprise the MVP. Any GUI
(graphical user interface) can be added to the final product to render it more accessible for the
masses and enter a commercial competitive market of remote medical dignosis which is grossly
untapped and unmeasured. A fast, efficient, reliable, tested, competitive and robust software will be
provided to the clients.
6. Evaluate and observe the critical tasks identified
Interface
1. Database Creation
2. Database needs to be consistent
3. Ensuring Security Of the Database using security protocols
4. Real Time Connection
Database
1. Create UI/UX
2. Connect database with user input
3. Feed data into model
4. Retrieve data from model
The Model
1. Feed/Receive from interface

2. Apply applicable algorithm
3. Check Accuracy
4. Send Results
7. Create a table and calculate values of all parameters
Effort = a*(KLOC)^b
3.6*(7) ^1.20
3.6*10.3304
37.18944 Person-Months
Time = c*(Effort)^d
2.5*(37.1899) ^0.32
2.5*3.1807
7.9519 Months
Person Required = Effort/Time

37.1894/7.9519
4.7 ~ 5 people
Intermediate Model Calculations

Cost Drivers Coefficients
Product Attributes
Required Software Reliability 1.40

Size of Application Database 1.08
Complexity of The Product 1.30
Hardware
Runtime Performance Constraints 1.11

Memory Constraints 1.21
Volatility of the virtual machine environment 1.00
Required turnabout time 1.07
Personnel attributes
Analyst capability 0.71

Applications experience 1.00
Software engineer capability 0.86
Virtual machine experience 0.90
Programming language experience 0.95
Project Attributes
Application of software engineering methods 0.91

Use of software tools 0.83
Required development schedule 1.00
Effort Adjustment Factor (EAF) - 1.1138
Effort – (a(KLOC) ^b) * EAF

28.925*1.1138
32.216 person-months
Development Time – c(E) ^d

0.25 (32.216) ^0.32
7.59 months
8. Classify the scenarios (best, normal, worst) along with the expected duration
Best Scenario:
Achieve better than expected accuracy in the first trial of the model thereby significantly
reducing development time and efforts. Also, database does not overfit and cause
generalization of data result in skewed Analysis.
Leads to at least 2 months of decrease in the development time.
Normal Scenario:
Defined in the table above, expecting heavy development time for the model and perfecting
the database to acceptable levels.
Worst Scenario:
This is when we do not have a model ready due to un-acceptable accuracy and the database
designed overfits all observations resulting in a skewed analysis.
Leads to at least 3 months of addition to the normal scenario defined in the table above.
9. Draw the final diagram and evaluate its effectiveness based on realistic project management
goals
Every goal will be reached as per any of the timelines (Best, Normal, Worst). The planning for each
task has been done and effectiveness will be highest if done in best timeline, normal if done in the
normal timeline and the worst or minimum effectiveness will be seen when we perform task in
worst timeline.

SPM Experiment 9: Activity Network Diagram

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

SPM Experiment 9: Activity Network Diagram

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPM Experiment 9: Activity Network Diagram

Uploaded by

Copyright:

Available Formats

SPM Experiment 9

Activity Network Diagram

B. Tech Information Technology – 4th Year

2. List the events to be carried out in the project

The execution involves the following milestones/goals that need to be

1. Creating and completing an acceptable dataset with sufficient

2. To clean the dataset using various libraries available to avoid

3. To identify and extract features which sway the decision making

4. To engineer and identify the most suitable algorithm for the

3. Prepare a checklist based on sequence of events

The problem of inaccessible healthcare and diagnosis infrastructure in developing and

6. Evaluate and observe the critical tasks identified

1. Feed/Receive from interface

Person Required = Effort/Time

Intermediate Model Calculations

Required Software Reliability 1.40

Runtime Performance Constraints 1.11

Analyst capability 0.71

Application of software engineering methods 0.91

Effort Adjustment Factor (EAF) - 1.1138

Effort – (a(KLOC) ^b) * EAF

Development Time – c(E) ^d

Leads to at least 2 months of decrease in the development time.

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.