TA ASSIGNMENTS

SANJYOT GAMBARE
181071020 | TY CS | BTECH

problem question from TA1(q1 and

q4)
Nowadays, there is a shortage of teaching faculty in educational
institutions throughout the country. This is a major hurdle in
educating the youth of this nation. On the other hand, there are a
huge number of students across the country who wish to pursue
education from premier educational institutions such as IITs but are
unable to do so due to a variety of reasons ranging from financial
constraints, family responsibilities, limited available seats in
colleges, tough competition, etc.
E-Learning Tool - an initiative would help overcome these obstacles
and enable the aspiring students and teachers to realize their dreams
to be educated. E-learning tool which would enable the participating
actor, say a professor, to create his own synchronous interactive
learning material using multimedia resources. This when coupled
with database management is intended to serve as a repository of
lectures in video (along with audio) and text in various file types on
the website that would enable aspiring students from remote centers
all around the nation to acquire knowledge and pursue their
education just by a stroke on the keyboard.
1. Estimates for project management of E-Learning tool project
Calculate LOC, FP

 Calculating LOC through estimation

Functions Estimated
LOC
User interface and 2300
control facilities
Database 3300
Management
System
Computer Graphics 4900
display facilities
Peripheral control 2000
function
Design analysis 8400
modules
Estimated Lines of 20000 (20K)
Code

 Calculating FP

Complexity adjustment
values:
Question Value

Reliable backup and recovery? 5

Data communications? 5
Distributed Processing 5
functions?
Performance critical? 4
System runs in existing, heavily 4
utilized hardware?
On-line data entry required? 5
Input transaction on multiple 1
screens?
Master files updated online? 5
Complex input/output/inquiries 2
Internal processing complex? 2
Informa Count w T
tion ei o
Domain g t
Value h a
t l
Numbe 2 4 9
r of 4 2
input
Numbe 1 5 5
r of 6 5
output
Numbe 2 5 1
r of 2 2
inquiri 0
es
Numbe 4 1 4
r of 0 0
files
Numbe 2 7 1
r of 4
extern
al
interfa
ces
Count 3
Total 2
1
Reusable code? 5
Conversion and installation 3
included?
Designed for multiple 5
installations in multiple
organizations?

Designed to facilitate change and 5

ease of use by the user?
56

Therefore,
  FP = count total * [0.65 + 0.01 * Sum (Fi)]
= 321 * [0.65 + 0.01 * 56]
= 321 * 1.21
= 388.41

(ii) Calculate EFFORT using LOC and FP,

 Effort using FP:
 Here LOC = 20000 or KLOC = 20
 Model used: Boehm Simple Model
 Formula: E = 3.2 * (KLOC)1.05
 Effort in person-months = 74.34 pm

 Effort using FP:

 Here FP = 388.41
 Model used: Albrecht & Gaffney Model
 Model Formula: E = -91.4 + 0.355 FP
 Effort in person-months = 54.16 pm

iii) Estimate development effort and development time

using basic COCOMO Model for this Semi-detached
projects
Estimated size of project=20KLOC
i) Semi-detached Mode:
Effort(E)=a(KLOC)b
=3.0(20)1.12
= 85.95 PM(Person month)
Development Time(D)=C(E)d
=2.5(85.95)0.35
=11.88M ~ 12Months

-------------------------------------------------------------------
--------------
2. For Budget estimate, answer the following
 The spiral model has four phases: Planning, Design,
Construct and Evaluation. A software project repeatedly
passes through these phases in iterations (called Spirals in
this model).

2A. When & why to use Spiral Methodology?

 When project is large

 When creation of a prototype is applicable
 When risk and costs evaluation is important
 When releases are required to be frequent
 When requirements are unclear and complex
 When changes may require at any time
 When long term project commitment is not feasible due to
changes in economic priorities
 As this E-learning project is large and contains so many
functionality and features we need to use spiral model. E-
learning project requirenments may get changed which
added in next released.

2B. How to use Spiral model in E-learning?

 Identify Needs and Break Down The eLearning Budget.
 Create Communication Guidelines.
 Determine the Risks Involved and Create A Plan B.
 Set A Realistic Design and Development Schedule.
 Develop A Phased Prototype.
 Gather Client's Feedback at Each Stage.
 Theory question from TA2(q2
and q4)
3. Justify the following statements with reasons:
(a) “Software engineering methods strive to reduce the
magnitude of the spikes and the slope of the actual
Idealized and failure curves for software “ .

 Software is not susceptible to the environmental maladies that

cause hardware to wear out. ln theory, therefore, the failure rate
curve for software should take the form of the “idealized curve”

fig. ldealized and actual failure curves for software

 Undiscovered defects will cause high failure rates early in the
life of a program.
 Thus, we encounter a spike in the actual curve.
 These defects can be prevented upto some extent by the
following measures:
1. Develop software product requirements that minimize
the likelihood of potential operational failures from
arising.
2. Evaluate the requirements obtained from stakeholders
 in the software performance and post–development
processes to ensure that those requirements do not
introduce complicated failure conditions or situations.

3. ldentify design characteristics that contribute to failure

detection and minimize failure propagation throughout a
data processing transaction.
4. Develop software test scenarios and procedures
designed to exercise the software behaviors associated
with failure detection, isolation, and recovery.
5. ldentify, track, and manage potential design risks to
ensure that product dependability is predictable and
substantiated via the software test effort.

(b)Software engineering is a layered technology

 Software engineering is a fully layered technology.
 To develop a software, we need to go from one layer to
another.
 Allthese layers are related to each other and each layer
demands the fulfillment of the previous layer.

The layered technology consists of:

1. Quality focus
The characteristics of good quality software are:
 Correctness of the functions required to be performed by
the software.
 Maintainability of the software
 lntegrity i.e. providing security so that the unauthorized
user cannot access information or data.
 Usability i.e. the efforts required to use or operate the
software.
 2. Process
 lt is the base layer or foundation layer for the software
engineering.
 The software process is the key to keep all levels together.
 lt defines a framework that includes different activities
and tasks.
 ln short, it covers all activities, actions and tasks required
to be carried out for software development.
3. Methods
 The method provides the answers of all 'how–to' that are
asked during the process.
 lt provides the technical way to implement the software.
 lt includes collection of tasks starting from communication,
requirement analysis, analysis and design modelling,
program construction, testing and support.
4. Tools
 The software engineering tool is an automated support
for the software development.
 The tools are integrated i.e the information created by
one tool can be used by the other tool.
 For example: The Microsoft publisher can be used as a
web designing tool.

(c)Software engineering is a discipline that integrates

process, methods, and tools for the development of
computer software.
 Software engineering is more than just programming. lt
includes computer science, project management, engineering
and other spheres.
 Process: A software development process is the process of
dividing software development work into distinct phases to
 improve design, product management, and project
management. lt is also known as a software development life
cycle (SDLC). The methodology may include the pre–
definition of specific deliverables and artifacts that are created
and completed by a project team to develop or maintain an
application.
 This process of developing a approach makes many decisions
and decides approach of S/W development based on various
methods such as :
 Effort, Schedule and Cost Estimation
 Risk Analysis
 Data Collection
 Project Tracking
 CM Management
 lterative/lncremental Development
 Agile Development
 White box / Black box testing.
 Monkey Testing
 No particular practice is the best, as requirements can
vary greatly from project to project,
 Along with human estimation, many software tools help
design an overall software's aspects. Tools include:
 lntegrated Development Environment (lDE)
 Database Management System (DBMS)
 Documentation Tools. For example, Doxygen,
DrExplain, Adobe RoboHelp for documentation.
 Project Management Tools. For example, Creative Pro
Office, Trac Project, Basecamp.
 Diagram tools. For example, Flow Chart Maker tool for
creating state–of–the–art flowcharts.rototyping tools.
For example, Serena prototype composer, Mockup
Builder.
 Quality Assurance Tools. For example, SoapTest,
AppsWatch, lMeter.
 Maintenance Tools. For example, Bugzilla for defect
tracking, HP Quality Center.
(d)Effective software project management focuses on the
four P’s: people, product, process, and project.
 The people:
 People of a project includes from manager to developer,
from client to finish user.
 Organizations that brought home the bacon high levels
of maturity within the people management space have a
better chance of implementing effective software
package engineering practices.
 The following categories of people are involved in the
software process.
 Senior Managers - Senior Managers define the business
issue
 Project Managers - Project Managers plan, motivate,
Organize and control the practitioners who do the
Software work.
 Practitioners - Practitioners deliver the technical skills
that are necessary to engineer a product or application.
 Customers - Customer specifies the requirements for the
software to be developed.
 End Users - End Users interact with the software once it
is released.

 The Product:
 Product is any package that needs to be developed.
 To develop with success, product objectives and scope
ought to be established, various solutions ought to be
thought of, and technical and management constraints
ought to be known. while not this data, it's not possible to
outline cheap and correct estimates of the price, a good
assessment of risk, a sensible breakdown of project tasks
or a manageable project schedule that gives a meaning
indication of progress.
 Before a software project is planned, the product
objectives and scope should be established, technical and
management constraints should be identified.
 Without this information it is impossible to define a
reasonable cost,amount of risk involved,the project
 schedule etc.
 A software project scope must be unambiguous and
understandable at the management and technical
levels. To develop a reasonable project plan we have to
functionally decompose the problem to be solved.

 The Process:
 A package method provides the framework from that a
comprehensive arrange for package development is
established. variety of various tasks sets— tasks,
milestones, work merchandise, and quality assurance
points—enable the framework activities to be custom–
made to the characteristics of the package project and
therefore the necessities of the project group.
 Finally, umbrella activities becomes more prominent
method model. Umbrella activities are freelance of
anybody framework activity and occur throughout the
method.
 Here the important thing is to select an appropriate
process model to develop the software.
 Some examples are Water fall model,lterative water
fall model,Prototyping model,Evolutionary
model,RAD(Rapid Application Development) model,
Spiral model.
 The Project:
 Here, the manager needs to perform some job.
 The project contains all and everything of the entire
development method and to avoid project failure the
manager needs to take some steps, needs to fret
concerning some common warnings etc.
 ln order to manage a successful software project,we
must understand what can go wrong (so that problems
can be Avoided)and how to do it right.
 A project is a series of steps where we need to make
accurate decision so as to make a successful project.
 (e)Boehm’s W5HH principle is applicable regardless of the
size or complexity of a software project.
 Boehm’s W5HH principle is applicable regardless of the size or
complexity of a software project. The questions noted provide
an excellent planning outline for the project manager and the
software team
 Boehm suggests an approach that addresses project objectives,
milestones and schedules, responsibilities, management and technical
approaches, and required resources. He calls it the WWWWWHH
principle, after a series of questions that lead to a definition of key
project characteristics and the resultant project plan:
 Why is the system being developed? The answer to this question
enables all parties to assess the validity of business reasons for the
software work. Stated in another way, does the business purpose
justify the expenditure of people, time, and money?
 What will be done, by when? The answers to these questions help
the team to establish a project schedule by identifying key project
tasks and the milestones that are required by the customer.
 Who is responsible for a function? The answer to this question
helps accomplish this.
 Where are they organizationally located? Not all roles and
responsibilities assigned within the software team itself. The
customer, users, and other stakeholders also have
responsibilities.
 How will the job be done technically and managerially? Once
product scope is established, a management and technical strategy
for the project must be defined.
 How much of each resource is needed? The answer to this question
is derived by developing estimates based on answers to earlier
questions.

(f)Software project management is an umbrella activity

within software engineering
The phases and related steps of the generic view of software
engineering are complemented by a number of umbrella activities.
Typical activities in this category include:
 Software project tracking and control: When plan,
tasks, models all have been done then a network of software
engineering tasks that will enable to get the job done on
time will have to be created.
 Formal technical reviews: This includes reviewing
the techniques that has been used in the project.
 Software quality assurance: This is very important
to ensure the quality measurement of each part to ensure
them.
 Software configuration management: Software
configuration management (SCM) is a set of activities
designed to control change by identifying the work products
that are likely to change, establishing relationships among
them, defining mechanisms for managing different
versions of these work products.
 Document preparation and production: All the
project planning and other activities should be hardly copied
and the production get started here.
 Re–usability management: This includes the backing
up of each part of the software project they can be corrected or
any kind of support can be given to them later to update or
upgrade the software at user/time demand.
 Measurement & Metrics: This will include all the
measurement of every aspects of the software project.
 Risk management: Risk management is a series of steps
that help a software team to understand and manage
uncertainty. lt’s a really good idea to identify it, assess its
probability of occurrence, estimate its impact, and establish a
contingency plan that— `should the problem actually
occur’.
 g. Boundary time calculations by PERT Chart can be
very useful in software project scheduling.
 PERT is an acronym that stands for Program Evaluation and
Review Technique.
 lt’s a statistical method that can be very useful when working on
a project, as it analyzes and represents the project’s tasks.
 A PERT chart is a graphic representation of the data you
generate from that method, laid out as a timeline.
 lt’s a critical tool project managers can use when putting
together a project schedule, as it allows them to break down
each of the project’s tasks for analysis.
 The purpose of the PERT chart is to find out how much time will
be required to finish each task in the project.
 This leads to figuring out the minimum time needed to
complete the whole project.
 What’s unique about a PERT chart is that you don’t have to start
your plan with a beginning and an end. Since it’s focused on
events, you can create one without knowing every detail.
 A PERT chart also gives you the raw data that can be imported
into project scheduling software, which helps you manage the
whole project, link your schedule to your plan, monitor
progress and keep stakeholders in the loop with report
 -----------------------------------------------------------------------
--------------
You have been appointed a project manager for a small software products
company. Your job is to build a breakthrough product that combines virtual
reality hardware with state-of-the-art software. Because competition for the
home entertainment market is intense, there is significant pressure to get the
job done. What team structure would you choose and why? What software
process model(s) would you choose and why?
What team structure to prefer & why?
 Random paradigm
The random paradigm structures a team loosely and depends on individual
initiative of the team members.

 This paradigm is similar to a Democratic decentralized (DD) team.

  This team does not deal with the work what is similar to past efforts.

 When innovation or technological breakthrough is required, teams

following the random paradigm will excel.
 Such team may struggle when “orderly performance” is required
Why?
 These types of teams will be successful when innovation or a
technological advance is required (for example, developing software
for a new machine).
 Informal
 Freewheeling
 Independent initiative
 Autonomous
 Less stable
 Creatively inventive
 Individualistic

Roles played by Team members:

1. Project Manager

 The project manager plays a primary role in the project, and is responsible
for its successful completion.
 The manager’s job is to ensure that the project proceeds within the specified
time frame and under the established budget, while achieving its objectives.
 Project managers make sure that projects are given sufficient resources,
while managing relationships with contributors and stakeholders.

2. System Administrator:
 A system administrator, or sysadmin, is a person who is responsible for the
upkeep, configuration, and reliable operation of computer systems;
especially multi-user computers, such as servers.
 The system administrator seeks to ensure that the uptime, performance,
resources, and security of the computers they manage meet the needs of the
users, without exceeding a set budget when doing so.
3. Project Leader
 Large projects may include a team leader, who reports directly to the project
manager.
 In small projects, the project manager wears both hats.
 The team leader cannot act like the boss and still obtain the benefits of team-
based work. Instead, he must adopt the following important roles:
● Initiator.
● Model.
● Negotiator.
● Listener.
● Coach.
● Working member.

4. Business Decision Makers - Finance Manager

 Finance project managers oversee projects that relate directly to an
organization’s revenue and expenses, cash flow, long-term investments, and
reporting.
 This requires them to conduct financial due diligence and apply accounting
procedures while also gathering and analyzing data from many sources at
once.

5. Domain expert:
 A domain expert is a person with special knowledge or skills in a particular
area of endeavour.
 Roles:
● Provides knowledge and/or skills of a particular domain critical to the
management, development and/or completion of the project.
● Collaborates, Communicates & Assists project team members project status
and issues to the Service Owner and Project Manager

 Skills: Virtual reality expert, artificial intelligence expert, Knowledge of iot

devices.

6. QA:
  QA or tester is responsible for the Quality Assurance and makes sure the
product is ready to use.

7. Software Engineer:
 Software engineer is a highly-skilled software developer that has to think
through all the aspects of the project and is responsible for making high level
design choices, as well as select technical standards.They apply their
knowledge of engineering and programming languages in software
development.
 Task:
 analyse user requirements
 write and test code, refining and rewriting it as necessary and communicate
with any programmers involved in the project research, design and write
new software programs (e.g. business applications or computer games) and
computer operating systems
 evaluate the software and systems that make computers and hardware work
 Skills:
 Virtual Reality Modelling Language (VRML), Web3D consortium for web-
based 3D graphics, WebVR , an experimental JavaScript application
programming interface (API) that provides support for various virtual
reality devices, such as the HTC Vive, Oculus Rift, Google Cardboard or
OSVR, in a web browser.

8. Hardware Engineer :
Hardware Engineers are mainly responsible for system configurations and
updates.
Task:

 They plan and design the layout of systems and check on what modifications
or changes have to be made.
 Analyze user and client requirements
 Gain continuous knowledge of how the system can be made better, efficient
and faster, producing higher and better results.
 Skills: Knowledge of gyroscopes and motion sensors, HD screens, VR
cameras, input devices such as 3D mouse, the wired glove, motion
controllers, and optical tracking sensors.

9. Marketing Manager:
 A Marketing Project Manager is a Project Manager who specializes in
planning, managing, and executing projects related to marketing
campaigns.
 Task:
o Collaborating with the graphics department on advertising artwork
o Conducting in-depth market research on a product or service as
well as competitor analyses
o Understanding the company, its products, and customer base in
order to create effective marketing campaigns
o Ensuring all marketing assets are on-brand and aligned with the
global business strategy

10. Systems Integration Manager:

 The systems engineer working on a project will plan, monitor, confront risk,
and deliver the technical aspects of the project, while the project manager is
concerned with the same kinds of activities for the overall project.
 Consult with customer to determine needs and implement proposals.
 Synthesize with internal program management, engineering and third party
vendors.
 Schedule incoming work, select staff and estimate time.
 Perform several tasks with manager.
 Assess new technologies and define new infrastructure requirements.
 Develop and establish efficient customer relationships.
 Assess current procedures to accomplish department goals.
 Develop and execute improved practices.
 Evaluate ongoing project and offer feedback to team.
 Manage department plans, budgets and policies.

What project model to use and why?

ANS
 Evolutionary models are suitable for given project.
 Therefore, we use one of the popular evolutionary models
 SPIRAL MODEL:-
o Reasons for using SPIRAL MODEL as process model:
 o The project is large
o The releases are required to be frequent as users might need new
updated features
o In order to confirm when the creation of a prototype is applicable
o Here in this project the risk and costs evaluation are very much
important as it will directly affect the company’s image in market
o This project is high-risk project because if it is accepted by
customers company’s repo will increase but if rejected it will fall
drastically as there is huge competition in market
o Here the requirements are unclear and complex so it will need
updates and fixes in time to time releases
o As mentioned in above point if we want to put it in simple words,
above point means, changes may require at any time
o Its long-term project, so commitment is not feasible due to
changes in economic priorities
o Since it includes high amount of risk analysis hence risk
avoidance is greatly enhanced

(problem question from TA2)

5. Today, there is a shortage of teaching faculty in educational institutions
throughout the country. This is a major hurdle in educating the youth of this
nation. On the other hand, there are a huge number of students across the
country who wish to pursue education from premier educational institutions
such as IITs but are unable to do so due to a variety of reasons ranging from
financial constraints, family responsibilities, limited available seats in
colleges, tough competition, etc. E-Learning Tool - an initiative would help
overcome these obstacles and enable the aspiring students and teachers to
realize their dreams to be educated. E-learning tool which would enable the
participating actor, say a professor to create his own synchronous interactive
learning material using multimedia resources. This when coupled with
database management is intended to serve as a repository of lectures in video
(along with audio) and text in various file types on the website that would
enable aspiring students from remote centers all around the nation to
 acquire knowledge and pursue their education just by a stroke on the
keyboard.
a. Develop a risk monitoring strategy and specific risk monitoring activities
for this case study. Be sure to identify the factors that you’ll be monitoring to
determine whether the risk is becoming more or less likely
Risk Management:
E-learning tools
Risk classification according to Charette
 Known risks:
 Confidentiality violation of content.
 Lack of cyber security
 Teachers may not be friendly with new technologies
 Feasibility of E-learning tool

 Predictable risks:
 Server may slow down due to multiple requests
 Poor Internet connection
 Unavailability of range in Remote areas

 Unpredictable risks: Can be anything that we can’t predict!

 Technology Risks:

1. Server and individual pc or smartphone may be affected by internet virus.

At the time of lecture streaming, or sending receiving study related
emails as that software runs on different browsers by different student.
2. If server is unable to handle multiple requests simultaneously, that
software may lag or can hang so we need to increase capacity of server.
3. If internet speed is not that high, student won’t be able to learn from the
video lectures and cannot upload his/her assessment on the portal.
4. If proper login system is not there, unauthorized party can access the
content and can disturb the system’s functioning via hacking
(Confidentiality violation)
 5. If that portal is completely new, there can be problem for some people to
adopt new technology
 People Risk:
1. Faculties may not be comfortable with new online technologies. We are
not sure about they have enough knowledge or not.
2. There can be case that any major occur to student during test and faculty
is not available to contact.
3. Faculties cannot monitor every student’s performance as students can
cheat during exams or can simply copy the assignments.
4. Due to distant learning, very less interaction will happen so it very
difficult to understand students’ need and to teach according to their
expectations.
5. There can be situation where faculty or student is not well aware of the
platform so he/she cannot utilize the portal fully using all features.

Customers Risks:
1. If the portal is not user friendly and affordable, customer won’t choose
that as there are many such portals available in market.
2. Portal should be based on customer’s requirements and their
expectations at lowest possible price.
3. In remote areas, students don’t have range for many days. So that is very
serious issue as student won’t be able to access the portal on the time.
4. Many students have Wi-fi but if electricity went off due to some issue or
heavy rainfall, they can lose the connection and won’t be able to join the
class.

Risks due to product size:

1. If there are many and frequent updates, there can be case those updates
are not supported by user’s device.
2. If content is getting added to portal every day, there should be cloud
system to handle that amount of data.
3. If product size is too large, it is very tough to manage everything as sole
administrator.
 Market and selling Risk:
1. If Our E-learning software is costly, then even if it has excellent features,
there can be price factor which comes in between.
2. If there is no advertisement and marketing of portal then maximum
people won’t get to know about the service.
3. If Our portal should be compatible with other portals in markets and
people won’t choose us. we should use innovative ideas, offers to attract
more customers as well as to keep existing customers as it is.

b. Develop a time line chart for it.

Time line chart

Week 1 Week 2 Week 3 Week 4 Week 5

Identify need and
benefit
Meet with customers

Establish product
statement
Define desired
output/control/input
Defining scope
Milestone1:
Document OCI
Revise OCI with
customer as required
OCI definition
complete
Define functionality

Define keyboard
input
User registration part
Milestone 2:
voice functions
Revise with client as
required
Isolate software
elements
Research availability
of existing softwares
Reusable
components
identified
Define technical
feasibility
Evaluate voice/
grammar checking
Make quick estimate
of size
Milestone3:
Create a scope
definition
Revise as required

c. Apply earned value analysis on this project

Analysis Report :
Activity Predecessor Duration(week) Cost/Week Total
Cost
Identify need and - 1 200 200
benefit
Meet with customers - 1 200 200

Establish product - 1 250 250

statement
Define desired - 1 250 250
output/control/input
Defining scope Define desired 1 300 300
output/control/input
Milestone1: - 2 200 400
Document OCI
Revise OCI with Define desired 1 200 200
customer as required output/control/input
OCI definition - 2 100 200
complete
Define functionality OCI definition 1 300 300
complete
Define keyboard OCI definition 1 200 200
input complete
User registration part OCI definition 1 400 400
complete
Milestone 2: OCI definition 1 200 200
voice functions complete
Revise with client as OCI definition 1 150 150
required complete
Isolate software OCI definition 2 400 800
elements complete
Research availability OCI definition 2 300 600
of existing softwares complete
Reusable OCI definition 2 200 400
components complete
identified
Define technical Revise with client as 1 200 200
feasibility required
Evaluate voice/ Revise with client as 1 300 300
grammar checking required
Make quick estimate Revise with client as 2 300 600
of size required
Milestone3: Revise with client as 2 300 600
Create a scope required
definition
Revise as required Evaluate voice/ 1 200 200
grammar checking

Field reported at the end of week 3

Activity Actual % Complete Incurred Cost
Identify need and benefit 100 200

Meet with customers 100 250

Establish product 100 250
statement
Define desired 100 250
output/control/input
Defining scope 100 400
Milestone1: Document OCI 100 350
Revise OCI with customer 100 300
as required
OCI definition complete 100 200
Define functionality 100 300

Define keyboard input 100 200

User registration part 100 350
Milestone 2: 100 300
voice functions
Revise with client as 100 100
required
Isolate software elements 0 0
Research availability of 0 0
existing softwares
Reusable components 0 0
identified
Define technical feasibility 0 0
Evaluate voice/ grammar 0 0
checking
 Make quick estimate of size 0 0
Milestone3: 0 0
Create a scope definition
Revise as required 0 0

Activity ACWP BCWP BCWS CPI CV SPI SV

Identify need and 200 200 200 1 0 1 0
benefit
Meet with customers 250 200 200 0.8 -50 1 0

Establish product 250 250 250 1 0 1 0

statement
Define desired 250 250 250 1 0 1 0
output/control/input
Defining scope 400 300 300 0.75 - 1 0
100
Milestone1: 350 400 400 1.14 50 1 0
Document OCI
Revise OCI with 300 200 200 0.66 - 1 0
customer as required 100
OCI definition 200 200 200 1 0 1 0
complete
Define functionality 300 300 300 1 0 1 0

Define keyboard 200 200 200 1 0 1 0

input
User registration part 350 400 400 1.14 50 1 0
Milestone 2: 300 200 200 0.66 - 1 0
voice functions 100
Revise with client as 100 150 150 1.5 50 1 0
required
Isolate software 0 0 400 0 0 0 -
elements 400
Research availability 0 0 300 0 0 0 -
of existing softwares 300
Reusable 0 0 200 0 0 0 -
components 200
identified
Define technical 0 0 0 0 0 0 0
feasibility
Evaluate voice/ 0 0 0 0 0 0 0
grammar checking
Make quick estimate 0 0 0 0 0 0 0
of size
Milestone3: 0 0 0 0 0 0 0
Create a scope
definition
Revise as required 0 0 0 0 0 0 0
Total to DATE 3450 3250 4150 0.94 - 0.78 -
200 900

CPI=BCWP/ACWP
CV=BCWP-ACWP
SPI=BCWP/BCWS
SV=BCWP-BCWS
Here the value of CPI is 0.94 which is less than 1 which shows that the project
is over budget.
The value of SPI is 0.78 which is less that 1 which shows that the project is
behind schedule.

-----------------------------------------------------------------------------------------
 Problem Question from TA3
5. Design the GUI Of EVM Machine for control unit, ballot unit
and VVPAT voterslip Report

Fig. GUI for BALLOT UNIT Fig. GUI for CONTROL UNIT

Name

Sr.no. Symbol

Fig. GUI for VVPAT UNIT

 6. Illustrate the following concept wrt given case study
7.1 Draw an ER diagram to represent the data requirements as
following:

(I)Identify the main entity types.

Strong Entities Weak Entities:-
Patients Nurse
Ward
Room
Doctor
Medicine
Bill
Receptionist
Employee
 Record

(II) Identify the main relationship types between the entity types.
 Patients assigned with Doctors, Ward, Test
 Receptionist maintain Record, Employee, Doctor
 Medicine, Bill assigned to Test
 Nurse assigned to Room

(III)Identify attributes and associate them with entity or relationship types.

 Patients – P_id, name, sex, age, address, mobile_no, details, MRN
 Ward – R_no, floor, Ward_type - ICU, Oncology, Radiology
 Room – R_no, floor
 Doctor – name, D_id
 Nurse – Name, N_id
 Medicine – name
 Test – T_id, T-type, N_test, P_id
 Employee – name, emp_id
 Record – p_id, p_name, description, appointment

(IV)Determine candidate and primary key attributes for each (strong) entity
type.
 Patient – id (Primary Key)
 Employee – id(Candidate Key)
 Test – T_id(primary key) T_type(candidate key)
 Ward – Ward_type(candidate key)
 Receptionist – P_id, P_name(candidate key)
(V)Determine the multiplicity constraints for each relationship.
State any assumptions necessary to support your design.
 Relationship between Doctor (N) & Patient (M) is many to many
 Relationship between Patient (N) & Ward (1) is many to one
 Relationship between Ward (N) & Room (1) is many to one
 Relationship between Patients (1) & Test (N) is one to many
 Relationship between Test (1) & Medicine (N) is one to many
 Relationship between Test (1) & Bill (1) is one to one
 Relationship between Medicine (1) & Bill (1) is one to one
 Relationship between Nurse (1) & Room (N) is one to many
 Relationship between Receptionist (1) & Record (N) is one to many

Q 7.2 Map the EER Diagram to Database schema design

Database Schema
7.3 Create two tables using oracle having pk and fk and other
constraints.

7.4 Creating Employee Table having emp_id as primary key

 Creating Branch Table branch_id as primary key
 Adding foreign key constraint
 Adding foreign key constraint
 Calling Describe command to check if constraint imposed on employee
table or not
 Calling Describe command to check if constraint imposed on branch
table or not