PROCESS MODEL IN SOFTWARE SOFTWARE MYTHS

ENGINEERING
- Erroneous beliefs about software and
Adapting a Process Model the process that is used to build it

•Process should be agile and • Affect managers, customers and

adaptable to problem. practitioners
•The overall flow of activities, action,
and tasks interdependencies among • Are believable because they often have
them elements of truth, but
•Degree to which and tasks are • Invariably lead to bad decision, therefore
defined within each framework
activity •Insist on realty as you navigate your way
through software engineering
Prescriptive and Agile process models
Many people recognize the fallacy of the
Prescriptive process models stress detailed myths, regrettably, habitual attitudes and
definition identification and application of methods foster poor management and
process activities and task technical practices, even when reality dictates
Agile process models emphasize project a better approach.
“agility” How it all stats
George polya outline the essence of • SafeHome:
problem solving, suggest:
•every software project is precipitated by
1. Understand the problem some business need-
2. Plan a solution
3. Carry out the plan • The need to connect a defect in an existing
4. Examine the result for accuracy
application.
Hooker’s general principles for software
• The need to the need to adapt a “legacy
engineering practice: important
system” to a changing business environment;
underlying law
• The need to extend the functions and
1. The reason it all exist: provide values
to users features of an existing application, or
2. Kiss (Keep it simple, stupid! As simple
• The need to create a new product, service,
as possible)
3. Maintain the vision or system
4. What you produce, other will
consume CASE STUDIES
5. be open to the future
• A person insulin pump
6. Plan ahead for reuse
7. Think! Place clear complete thought  A mental health case patient
before action produces better result management system
 A wilderness weather station
Insulin pump control system
• Collect data from a blood sugar sensor
and calculates the amount of insulin
required to be injected
Insulin Pump Hardware Architecture
Activity Model Of The Insulin Pump
Essential high-level requirements
•The system shall be available to deliver
insulin when required.
•The system shall perform reliably and
deliver the correct amount of insulin to
counteract the current level of blood
sugar.
•The system must therefore be designed
and implemented to ensure that the
system always meets these requirements.
A Patient Information System For Mental
Health Care
•A patient information system to support
mental health care is a medical
information system that maintains
information about patients suffering from
mental health problems and the
treatments that they have received.
•Most mental health patients do not
require dedicated hospital treatment but
need to attend specialist clinics regularly
where they can meet a doctor who has
detailed knowledge of their problems.
•To make it easier for patients to attend,
these clinics are not just run in hospitals.
They may also be held in local medical
practices or community centres.
MHC-PMS
• MHC-PMS (Mental health care –patient,
management system) is an information
system that is
intended for use in clinics.
MHC-PMS GOALS
•To generate management information that
allows health service managers to assess
performance against local and
government targets.
THE ORGANIZATION OF THE MENTCARE
SYSTEM
MHC-PMS Key features areas of wilderness decides to deploy
several hundred weather stations in
Individual care management remote areas.
 Clinicians can create records for THE WEATHER STATION’S ENVIRONMENT
patients, edit the
information in the system, view
patient history, etc

Patient monitoring

 The system monitors the records of

patients that
are involved in treatment and issues
warnings if
possible problems are detected.

Administrative Reporting

 The system generates monthly WEATHER INFORMATION SYSTEM

management reports
showing the number of patients The weather station system
treated at each  This is responsible for collecting
clinic weather data, carrying
out some initial data processing and
transmitting it to the
MHC-PMS concern data management system.

•Privacy The data management and archiving

system
 It is essential that patient information
is confidential  This system collects the data from all
and is never disclosed to anyone apart of the wilderness
from weather stations, carries out data
authorized medical staff and the processing and analysis
patient themselves. and archives the data.

•Safety The station maintenance system

 Some mental illnesses cause patients  This system can communicate by

to become satellite with all
suicidal or a danger to other people. wilderness weather stations to
monitor the health of
WILDERNESS WEATHER STATION these systems and provide reports of
problems.
 The government of a country with
large
ADDITIONAL SOFTWARE FUNCTIONALITY - Software development provides
better and quality software product.
 Monitor the instruments, power and
communication hardware and report SOFTWARE ENGINEERING PROCESS
faults to the PARADIGMS
management system.
 Manage the system power, ensuring  Process model (or) software
that batteries engineering paradigm
are charged whenever the  Waterfall model
environmental  Prototyping model
conditions permit but also that  Rapid application development model
generators are
WATERFALL MODEL
shut down in potentially damaging
weather  Linear sequential model or classic life
conditions, such as high wind. cycle or waterfall
 Support dynamic reconfiguration  Requirements Analysis
where parts of
the software are replaced with new  Design
versions and
 Coding
where backup instruments are
switched into the  Testing
system in the event of system failure.
 Maintenance
NEED OF SOFTWARE ENGINEERING
Advantages:
Large software:

- It is easier to build a wall than to a

house or building, likewise, as the size
of software becomes large
engineering.

Scalability

- Easier to re-create new software

Cost

- Hardware, cost if software remains  Simple and easy to understand

high  Each phase has specific deliverables
and review process
Dynamic nature:
 Phases are processed and complete
- Adapting nature of software one at a time. Phases don’t overlap.
 Smaller projects.
Quality management:

Disadvantage:
 Once an application is in the testing
stage , it is very difficult to go back
and change
 Produced until the late during the life
cycle
 High amount of risk and uncertainty
 Not good for complex and object
oriented projects
 Poor model for long projects
 Not suitable for moderate to high risk
of changing.
The following phases:
PROTOTYPING MODEL
 requirements gathering
 developer and customer meet
 outline areas
 quick design
 May increase the complexity
 Incomplete application
RAPID APPLICATION DEVELOPMENT
(RAD) MODEL
 Increment software process
model that emphasize an
extremely short development
cycle
 High-speed adaptation
 It enables a development team to
create a fully functionality system
within very short time periods
 Business modeling
- information flow among business
function,
 Data modeling
- Data objects, relationship- between
objects.
 Process modeling
- Information flow, adding, modifying,
deleting and retrieving a data objects
 Application generation
- Generation programming languages.
 Testing and turnover
- Reduces overall testing time, reuses

EVOLUTION PROCESS MODELS

 Evolutionary models are iterative

models
Advantages:  Software engineers to develop
 User are actively involves increasingly more complete version
of the software
 Much earlier
 Incremental model
 Feedback is available
 Spiral model
 Easily identified
 Better understanding

Disadvantages:

 Repairing way of building system