Scribd
Upload
54 views

Notes

An insulin pump is an embedded system that mimics the pancreas to control blood glucose levels for diabetics. The software process involves specification, design, implementation, and testing activities. Requirements engineering produces an agreed requirements document specifying the system. It involves feasibility studies, requirements elicitation and analysis, specification, and validation. Software design converts specifications into an executable system through architectural design, interface design, component design, and algorithm design. The Rational Unified Process (RUP) is an iterative software development process with phases for inception, elaboration, construction, and transition.

Uploaded by

MUNEEBA GUL
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
54 views

Notes

An insulin pump is an embedded system that mimics the pancreas to control blood glucose levels for diabetics. The software process involves specification, design, implementation, and testing activities. Requirements engineering produces an agreed requirements document specifying the system. It involves feasibility studies, requirements elicitation and analysis, specification, and validation. Software design converts specifications into an executable system through architectural design, interface design, component design, and algorithm design. The Rational Unified Process (RUP) is an iterative software development process with phases for inception, elaboration, construction, and transition.

Uploaded by

MUNEEBA GUL
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

A personal insulin pump:

An embedded system in an insulin pump


used by diabetics to mimic the function of the pancreas and hence control
the level of glucose (sugar) in their blood.

Insulin pump control system:

The software process"


A software process is the set of activities and associated outcome that
produce a software product. Software engineers mostly carry out these
activities. These are four key process activities, which are common to
all software processes.
 A structured set of activities required to develop a software system.

1. Software specification
Software specification or requirements engineering is the
process of understanding and defining what services are required from the
system and identifying the constraints on the system’s operation and
development.

The requirements engineering process (Figure 2.4) aims to produce an agreed


requirements document that specifies a system satisfying stakeholder
requirements.
There are four main activities in the requirements engineering process:

Feasibility study

An estimate is made of whether the identified user


needs may be satisfied using current software and hardware
technologies. The study considers whether the proposed system
will be cost-effective from a business point of view and if it can be
developed within existing budgetary constraints. A feasibility
study should be relatively cheap and quick. The result should
inform the decision of whether or not to go ahead with a more
detailed analysis.
2. Requirements elicitation and analysis

This is the process of deriving the


system requirements through observation of existing systems, discussions
with potential users and procurers, task analysis, and so on. This may
involve the development of one or more system models and prototypes.
These help you understand the system to be specified.

3. Requirements specification

Requirements specification is the


activity of translating the information gathered during the analysis activity
into a document that defines a set of requirements. Two types of
requirements may be included in this document. User requirements are
abstract statements of the system requirements for the customer and end-
user of the system; system requirements are a more detailed description of
the functionality to be provided.

4. Requirements validation

 It is determined whether the


requirements defined are complete. This activity also checks the requirements
for consistency.

Software design and implementation

The implementation phase of software development is the process of


converting a system specification into an executable system through the
design of system. A software design is a description of the architecture
of the software to be implemented, the data which is part of the system,
the interfaces between system components and, sometimes, the
algorithms used. The design process activities are the followings:
1. Architectural design. The sub-systems of system and their
relationships are identified based on the main functional
requirements of software.
2. Abstract specification. For each sub-system, an abstract
specification of its services and the constraints under which it must
operate is defined.
3. Interface design. Interfaces allow the sub-system’ services to be
used by other sub-systems. The representation of interface should
be hidden. In this activity the interface is designed and documented
for each sub-system. The specification of interface must be
unambiguous.
4. Component design. Services are allocated to components and the
interfaces of these components are designed.
5. Data structure design. The data structures used in the system
implementation are designed in detail and specified.
6. Algorithm design. In this activity the algorithms used to provide
services are designed in detail and specified.

This general model of the design process may be adapted in different


ways in the practical uses.

RUP and its Phases


 Difficulty Level : Basic

Rational Unified Process (RUP)


 is a software development
process for object-oriented models. It is also known as the Unified
Process Model. It is created by Rational corporation a division of IBM .

Some characteristics of RUP include use-case driven, Iterative


(repetition of the process), and Incremental (increase in value) by nature,
delivered online using web technology, can be customized or tailored in
modular and electronic form, etc. RUP reduces unexpected development
costs and prevents wastage of resources.
Phases of RUP :
There are total five phases of life cycle of RUP:

1. Inception –
 Communication and planning are main.
 Identifies Scope of the project using use-case model
allowing managers to estimate costs and time required.
 Customers requirements are identified and then it becomes
easy to make a plan of the project.
 Project plan, Project goal, risks, use-case model, Project
description, are made.
 Project is checked against the milestone criteria and if it
couldn’t pass these criteria then project can be either
cancelled or redesigned.

2. Elaboration –
 Planning and modeling are main.
 The project's architecture and required resources are further evaluated.
 Detailed evaluation, development plan is carried out and
diminish the risks.
 Revise or redefine use-case model (approx. 80%), business
case, risks.
 Again, checked against milestone criteria and if it couldn’t
pass these criteria then again project can be cancelled or
redesigned.
 Executable architecture baseline.

3. Construction –
 Project is developed and completed.
 System or source code is created and then testing is done.
 Coding takes place.

4. Transition –
 Final project is released to public.
 Transit the project from development into production.
 Update project documentation.
 Beta testing is conducted.
 Defects are removed from project based on feedback from
public.

You might also like