karthik chb0911015

8/3/2019 karthik chb0911015

1/34

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

i

ASSIGNMENT

EMBEDDED COMMUNICATION

SYSTEM

Module Code ESD 525

Module Name Real Time Software Engineering

Course M.Sc in Real-Time Embedded Systems

Department Computer Engineering

Name of the Student Karthik.K

Reg. No CHB0911015

Batch Full-time 2011

Module Leader Mr. Deepak V

POSTGRADUATEE

NGINEERING

ANDM

ANAGEMENTPROGRAMME(PEMP)

M.S.Ramaiah School of Advanced Studies

Postgraduate Engineering and Management Programmes(PEMP)

#470-P Peenya Industrial Area, 4th Phase, Peenya, Bengaluru-560 058

Tel; 080 4906 5555, website: www.msrsas.org

8/3/2019 karthik chb0911015

2/34

ii

Declaration SheetStudent Name Karthik k

Reg. No CHB0911015

Course Real Time Embedded System Batch FULL-Time 2011

Batch FT-11Module Code ESD525

Module Title Real Time Software Engineering

Module Date 08-11-2011 to 03-12-2011

Module Leader Mr. Deepak V

Extension requests:Extensions can only be granted by the Head of the Department in consultation with the module leader.Extensions granted by any other person will not be accepted and hence the assignment will incur a penalty.Extensions MUST be requested by using the Extension Request Form, which is available with the ARO.A copy of the extension approval must be attached to the assignment submitted.

Penalty for late submissionUnless you have submitted proof of mitigating circumstances or have been granted an extension, thepenalties for a late submission of an assignment shall be as follows:

Up to one week late: Penalty of 5 marks

One-Two weeks late: Penalty of 10 marks

More than Two weeks late: Fail - 0% recorded (F)All late assignments: must be submitted to Academic Records Office (ARO). It is your responsibility toensure that the receipt of a late assignment is recorded in the ARO. If an extension was agreed, theauthorization should be submitted to ARO during the submission of assignment.

To ensure assignment reports are written concisely, the length should be restricted to a limit

indicated in the assignment problem statement. Assignment reports greater than this length may

incur a penalty of one grade (5 marks). Each delegate is required to retain a copy of the

assignment report.

DeclarationThe assignment submitted herewith is a result of my own investigations and that I have conformed to theguidelines against plagiarism as laid out in the PEMP Student Handbook. All sections of the text andresults, which have been obtained from other sources, are fully referenced. I understand that cheating andplagiarism constitute a breach of University regulations and will be dealt with accordingly.

Signature of the student Karthik k Date 03-11-2011

Submission date stamp(by ARO)

Signature of the Module Leader and date Signature of Head of the Department and date

8/3/2019 karthik chb0911015

3/34


iii

Abstract

____________________________________________________________________________

Now-a-days Real-time software engineering systems have become most important and

indispensible part of our modern day life. Real-time systems are growing rapidly in current

markets. Real time software engineering is an engineering providing certain methods and tools

for the development of quality product with a limited budget and a given deadline, in the

context of constant requirements change. Hence it is very important that the real-time systems

are highly efficient, reliable and robust. To develop such real time embedded systems, various

approaches are used.

Here, the software which I am going to develop is Digital Video Recording system. It is

a real time system; there are two approaches which I am using for developing the system. They

are structured approach and object oriented approach which is using UML standard. Here, I am

making everything automated by writing code in C, C++ using RRRT tool. By this the whole

system is controlled by the software, this reduces man power and will be more efficient. In the

next session I have discussed the issues and future development of the two approaches.

By following these methods, I developed a system which gives a better quality to end

user. The system is reliable and easy to maintain. The structural and object oriented approach

gives a confidence of Digital Video Recording (DVR) system development with good

document which can used to maintain it.

8/3/2019 karthik chb0911015

4/34


iv

Contents

____________________________________________________________________________

Declaration Sheet .......................................................................................................................... iiAbstract ........................................................................................................................................ iiiContents ....................................................................................................................................... ivList of Tables ............................................................................................................................... viList of Figures ............................................................................................................................. viiList of Symbols .......................................................................................................................... viiiPART-A ........................................................................................................................................ 1CHAPTER 1 ................................................................................................................................. 1

1.1 Introduction ......................................................................................................................... 11.2 Literature survey on characteristics of ISO&CMM ........................................................... 1

1.2.1 Characteristics of CMM .............................................................................................. 11.2.2 Characteristics of ISO .................................................................................................. 2

1.3 Comparisons of the Models ................................................................................................ 21.4 Conclusion .......................................................................................................................... 3

PART-B ........................................................................................................................................ 4CHAPTER 2 ................................................................................................................................. 4

2.1 Introduction ......................................................................................................................... 42.2 Functional Requirements .................................................................................................... 42.4 Entity Relationship Model .................................................................................................. 52.5 DATA FLOW MODEL ...................................................................................................... 5

2.5.1 CONTEXT LEVEL DIAGRAM ................................................................................. 52.5.2 Level 1 DFD .................................................................................................................... 7

2.5.3 Level 2 DFD ................................................................................................................ 82.6 DATA DICTIONARY ....................................................................................................... 82.7 CFD (Control Flow Diagram) ............................................................................................ 92.8 Test cases .......................................................................................................................... 10

8/3/2019 karthik chb0911015

5/34


v

PART-C ...................................................................................................................................... 13CHAPTER 3 ............................................................................................................................... 13

3.1 Introduction ....................................................................................................................... 133.2 Use cases ........................................................................................................................... 13

3.2.1 Data card .................................................................................................................... 133.2.2 Sd card slot ................................................................................................................ 133.2.3 Copy to DVD ............................................................................................................. 133.2.4 Play or pause .............................................................................................................. 133.2.5 Rewind & forward ..................................................................................................... 133.2.6 Replay or stop ............................................................................................................ 14

3.3 Actors in use case diagram ............................................................................................... 143.4 Use case specifications ..................................................................................................... 143.5 Use Case Diagram ............................................................................................................ 163.6 Capsule in DVR ................................................................................................................ 17

3.6.1 Class Diagram ............................................................................................................ 173.6.2 Capsule Structure Diagram ........................................................................................ 18

3.7 Results Discussion ............................................................................................................ 193.8 conclusion ......................................................................................................................... 213.9 Comments on Learning Outcome ..................................................................................... 22References............................................................................................................................... 23APPENDIX A ......................................................................................................................... 24

8/3/2019 karthik chb0911015

6/34

vi

List of Tables

____________________________________________________________________________

Table1. 1 Difference for ISO & CMM ......................................................................................... 3

Table 2. 1 Data dictionary ............................................................................................................ 9Table 2. 2 Test cases ................................................................................................................... 12

8/3/2019 karthik chb0911015

7/34


vii

List of Figures

____________________________________________________________________________

Fig1. 1 Maturity levels .................................................................................................................. 1

Fig2. 1 E-R DIAGRAM ................................................................................................................ 5Fig2. 2 ZERO LEVEL .................................................................................................................. 6Fig2. 3 level 1 ................................................................................................................................ 7Fig2. 4 level 2 ................................................................................................................................ 8

Fig 3. 1Use Case Diagram .......................................................................................................... 16Fig 3. 2 State Diagram ................................................................................................................ 18Fig 3. 3 Capsule Structure Diagram ............................................................................................ 18Fig 3. 4 Test Execution 1 ............................................................................................................ 19Fig 3. 5 Testing Case2 ................................................................................................................. 20Fig 3. 6 Testing Case3 ................................................................................................................. 21

8/3/2019 karthik chb0911015

8/34


Real Time Software Engineering viii

List of Symbols

___________________________________________________________________________

Acronyms

RTES Real Time Embedded Systems

UML Unified Model Language

DFD Data Flow Diagram

OOA Object Oriented Analysis

RRT Rational Rose Real Time

FR Functional Requirement NFR Non- Functional Requirement

PSPEC Process Specifications

CSPEC Control Specifications

8/3/2019 karthik chb0911015

9/34

1.1 Introduction

The day today software

developers, modern software dev

quality management, the iso was

growing number of is developers

companies are eager to obtain a c

the use of standard in control of

Europe and Japan [1], it is com

standards followed in USA[2][3][4

1.2 Literature survey on ch

1.2.1 Characteristics of CMM

These levels are described i

A Key Process Area is a gr

functioning at the appropri

Many organizations may

Levels 2 and 3 posing a ma

evelopers can no longer afford to deliver poo

elopment organization are paying a great de

specifically for designed for system devel

use standard as control of implementing quali

rtificate because of market pressure. In this se

uality of software. Iso model which is most p

ared with capability maturity model(cmm),

].

racteristics of ISO&CMM

Fig1. 1 Maturity levelsn terms of Key Process Areas.

oup of related activities considered important f

te process maturity level.

find themselves operating at Level 1,with m

jor challenge.

PART-A

HAPTER 1

quality software

l of attention to

opment. Today a

y systems. Many

ssion, we discuss

pular standard in

hich is common

r an organization

ovement towards

8/3/2019 karthik chb0911015

10/34


Real Time Software Engineering 2

1.2.2 Characteristics of ISO

The ISO software provides 6 main characteristics[5]

Functionality

Functionality is the essential purpose of any product or service. For certain items this isrelatively easy to define, for example a ship's anchor has the function of holding a ship at a given

location. The more functions a product has, e.g. an ATM machine, then the more complicated it

becomes to define it's functionality

Reliability

Once a software system is functioning, as specified, and delivered the reliability

characteristic defines the capability of the system to maintain its service provision under defined

conditions for defined periods of time.

Usability

Usability only exists with regard to functionality and refers to the ease of use for a given

function. For example a function of an ATM machine is to dispense cash as requested. Placing

common amounts on the screen for selection, i.e. $20.00, $40.00, $100.00 etc, does not impact the

function of the ATM but addresses the Usability of the function.

Efficiency

This characteristic is concerned with the system resources used when providing the required

functionality. The amount of disk space, memory, network etc. provides a good indication of this

characteristic.

Maintainability

The ability to identify and fix a fault within a software component is what the

maintainability characteristic addresses. In other software quality models this characteristic is

referenced as supportability. Maintainability is impacted by code readability or complexity as well

as modularization.

Portability

This characteristic refers to how well the software can adopt to changes in its environment

or with its requirements. The sub characteristics of this characteristic include adaptability. Object

oriented design and implementation practices can contribute to the extent to which this

characteristic is present in a given system.

1.3 Comparisons of the Models

Both the Capability and Maturity Model and the ISO 9001 standards were designed to

improve organizational processes. While ISO was not designed specially with software

8/3/2019 karthik chb0911015

11/34



development in mind it has widely been accepted on an international basis as a successful model

with consider to quality promise in the software industry.

Table1. 1 Difference for ISO & CMMISO CMM

Minimum Requirements to become certified

With indirect continuous improvement

Five-Levels of Certification with explicit

Continuous improvement

Designed to implement in all industry

Development

Designed particularly for the software

Purpose

Focused outwards in different views Focused inwards in different views

Re-certification must be done within one

year

No need of any certification further

Certification will be done by 3rd party not by

the main organization

Certification will be done by SIE(developers

of CMM)

1.4 Conclusion

At present there is a conflict between the desire for better quality systems resulting in

measurable improvements of the systems development process and the way in which this is

implemented by means of standards. Quality certificates can give a wrong impression of the realcapabilities of an organization, but this should not lead to the abolition of standards.

The majority of organizations can improve their systems by making (sensible) use of the

standards. In the short term, the quality of systems development can be improved by an approach

that is specially constructed for assessing systems development environments, that support

measurable improvement in the development process, and that support the choice and

implementation of actions.

In the longer term, standards and certificates will have to take into account the diversity that

exists in the real world. We think this process will take some time and that, therefore, organizations

will have to carefully assess the value of quality certificates in different situations.

8/3/2019 karthik chb0911015

12/34



PART-B

CHAPTER 2

________________________________________________________________________________

2.1 Introduction

Nowadays everyone is busy with their jobs, carers, schedules etc. so many people are

missing their favourite programs, celebrity interviews and lot more valuable programs for this

problem dth providers found out new idea to control this problem i.e. DVR(digital video recorder)

which can record live programs & future programs so who are missing the live telecast can record

those telecast and watch those in leisure times even we can record future TV programs in hd quality

this is main motive of the DVR in set up box

Even we can copy those contents into dvd or memory card, for this purpose DVD writer&memory card slot is provided. more than 550 hours of streaming can recorded un interruptedly, it

can increased in future with advanced technology

2.2 Functional Requirements

1. User must insert data card to get interact. [Tag: FR_1]

2. Select particular channel for recording. [Tag: FR_2]

3. Entering into recording zone to record. [Tag: FR_3]

4. He must mention record starting time. [Tag: FR_4]

5. He must mention stopping time for recording. [Tag: FR_5]

6. For advanced recording he must mention date. [Tag: FR_6]

7. Date must not exceed 6 days from present date. [Tag: FR_7]

8. User can pause live steaming & watch later. [Tag: FR_8]

9. User can access database for storing purpose. [Tag: FR_9]

10. User can forward or rewind data in database. [Tag: FR_10]

2.3 Nonfunctional Requirements

Safety: Only user should be able to data in his database. [NFR_1]

Courteousness: DVR must exhibit human-friendly behavior so as to increase

chances of successful human interaction. [NFR_2]

Reliable: Quality of recorded content must be same as streamed one. [NFR_3]

8/3/2019 karthik chb0911015

13/34



2.4 Entity Relationship Model

Fig2. 1 E-R DIAGRAM

The Entity-Relationship (ER) Model defines the relationship between the entities present in

the system, in this the relation will be given between dvr & set-up box. The Figure 1 illustrates the

E R Diagram for the DVR. The Entities present in the digital video recorder are as follows

USER

DVR

SET-UP BOX

2.5 DATA FLOW MODEL

2.5.1 CONTEXT LEVEL DIAGRAM

In this context level diagram we are implementing 3 levels of representations they are

8/3/2019 karthik chb0911015

14/34



Level 0

Level 1

Level 2

Fig2. 2 ZERO LEVEL

User interacts with dvr option in setup box

Data stores in database

Setup box interacts with dvr to record

Data recorders record data in dvr

8/3/2019 karthik chb0911015

15/34



2.5.2 Level 1 DFD

Fig2. 3 level 1

User interacts with sd card slot to copy data from data base

Recorder records from live streaming

8/3/2019 karthik chb0911015

16/34



2.5.3 Level 2 DFD

Fig2. 4 level 2

2d recorder records other than 3d contents

3d recorder records 3d movies & content

Play& pause option lets u pause live contents

User can forward or rewind data stored in database

2.6 DATA DICTIONARY

Name Aliases Where/How

Used

Description Format

Set-up box Hardware Hardware for

Dth services

User can interact Signal

transmission

Records Used for

recording

Records the data

requested by the

Signal

transmission

DATA

RECODER

USER

DATA BASE

SET-UP BOX

RECORDS DATA

INTERACTS

SAVES RECORDED DATA

ACTIVATES

2D

RECORDE

R PLAY&PA

USE

INTERACTS

SAVES RECORDED DATA

3D

RECODER FORWARD

& REWIND

RECORDED

DATA

USES

USESINTERACTS

SAVES RECORDED DATA

8/3/2019 karthik chb0911015

17/34



purpose user

Data base Memory Used for

memory purpose

User can load

data in this

database

Data type is

char

Play & pause Controls Controls data in

database

User can control

the streaming

Signal

transmission

Rewind &

forward

Controls Controls data in

database

User can control

the streaming

Signal

transmission

Interacts DVR controller Used to record

data

User can record

live streaming or

future telecasting

Signal

transmission

Table 2. 1 Data dictionary

2.7 CFD (Control Flow Diagram)

This representation allows you to know the control of data in DVR this representation

follows as below

8/3/2019 karthik chb0911015

18/34



Fig 2. 1 CFD

User first interacts with setup box for recording live streaming Then setup box interacts with dvr for recoding purpose

The dvr records data that is mentioned by the user

User can pause live streaming

User can rewind or forward video that already recorded

All the storage will be done in database

Database has got 550 hours of storage capacity

2.8 Test cases

USER

DATA BASE

INTERACTS

SET-UP

BOXINTERAC

TS DVR

SAVES RECORDED DATA

RECORDS

USES

USES

SAVES RECORDED DATA

REWIND

OR

FORWARD PLAY&PA

USE

TESTSPCIFICATION/REPORT

Test Case/Test Data Test procedure Test Cycle

Test

Case

Feature Criti

cal

Test

Cases

Test

Strategy

Test

Data

Test

Setup

Expected

Results

Obta

ined

8/3/2019 karthik chb0911015

19/34



No

lts

TC_0 Enter the

channeldisplayed

N Check

for theconfor

mation

Black

Box

Input Requir

edchanne

l will

be

displa

yed

Channel

will bedisplayed

TC_1 Pause the

live

stream

Y The

live

transmi

ssion

should

get

paused

Black

Box

Signal

trans

missio

n

Live

transm

ission

will be

paused

Live

transmiss

ion

should

resume

whenever

the user

wishes

TC_2 length of

time

required

for the

recording

Y It

should

take

starting

&

ending

time of

recordi

ng

Black

Box

Signal

trans

missio

n

It

should

start at

desire

d time

Recoding

should

start at

given

time &

end at

given

time

TC_3 Stop

button

Y Recodi

ng will

stop by

pressin

g this

button

Black

Box

Navig

ator

proces

s

Recor

ding

will

stop

by

pressin

Recordin

g will

stop at

any case

by

pressing

8/3/2019 karthik chb0911015

20/34



Table 2. 2 Test cases

g this

button

this

button

TC_4 fast

forwardor skip

commerci

als in a

recorded

video

Y Skippin

g ads inrecorde

d video

Black

Box

Fast

forwarding

record

ed

video

Ads will

beskipped

by this

feature

TC-5 Copying

recorded

content

into DVD

Y It

should

write

into

DVD

Black

Box

Com

munic

ating

perso

n

Copyi

ng

recodi

ng

conten

t into

DVD

It should

write

data into

DVD

8/3/2019 karthik chb0911015

21/34

PART-C

CHAPTER 3

________________________________________________________________________________

3.1 Introduction

Object orientation analysis is an approach to software design in which decomposition of

system is based upon the concept of an object. An object is an entity whose behavior is

characterized by the actions that it suffers and that it requires of another objects. Object oriented

approach has many automated tools to produce an application.

3.2 Use cases

Data card

SD card slot

Copy to DVD

Play& Pause

Rewind& Forward

Replay& Stop

3.2.1 Data card

For user specification data cards for validation of customer account by placing data card

only user is able to watch channels

3.2.2 Sd card slot

This future is for copying recorded data from data base ,this slot can increase the speed of

copying data ,this is better than DVD writer

3.2.3 Copy to DVD

User can directly copy content from database by using recorder in the digital video recorder

3.2.4 Play or pause

User can pause the ongoing live streaming & play at required spot on match

3.2.5 Rewind & forward

User can rewind or forward content recorded in database

8/3/2019 karthik chb0911015

22/34



3.2.6 Replay or stop

User can replay the live streaming or stop any recoding data even though he given the

ending time

3.3 Actors in use case diagram User

DVR

Set-up box

3.4 Use case specifications

Use case name Data card slot

Use case ID UC_1

Actors Set-up box

Purpose User id for set-up box

Overview This is used for security purpose

Only person with data card can interact with

set-up box

Precondition Wont work without data card

Post condition Works after inserting data card

Cross reference Get the instructions from manual

Use case name Sd card slot

Use case ID UC_2

Actors Set-up box

Purpose Memory support in set-up box

Overview This is used for copying purpose

Precondition Can copy data in the slot

Post condition Copy is completed


8/3/2019 karthik chb0911015

23/34



Use case name Copy to DVD

Use case ID UC_3

Actors Set-up box

Purpose Copying dataOverview User can copy data into DVD writer

Precondition copying data

Post condition Copy is completed


Use case name Play & pause

Use case ID UC_4

Actors User, DVR

Purpose For pausing live streaming

Overview This is for pausing live streaming

Precondition Live streaming

Post condition Paused live stream


Use case name Rewinding& forwarding

Use case ID UC_5

Actors User, DVR

Purpose For rewinding& forwarding

Overview For rewinding

For fast forwarding

Precondition

Post condition


8/3/2019 karthik chb0911015

24/34



Use case name Replay or stop

Use case ID UC_6

Actors User , DVR

Purpose Stopping at desired time

Overview Replay of pause content

Stopping at desired time

Precondition Pause of live streaming

Post condition Stop at recording spot


3.5 Use Case Diagram

Fig 3. 1Use Case Diagram

copy to dvd

set-up box

( data card )

( sd card slot )

( copy to dvd )

play& pause

forward& rewindNewActor1

( play& pause )

( forward& rewind )

( replay & stop ) replay & stop

data card

sd card slot

DVR

( play& pause )

( forward& rewind )

( replay & stop )

8/3/2019 karthik chb0911015

25/34



3.6 Capsule in DVR

Class name

Purpose Records in the memory

Attributes recorder

Operation Interaction for user

Records live streaming

Class name

Purpose Interaction

Attributes recorder

Operation Interaction for user

3.6.1 Class Diagram

dv r

+ / p1 : RECORDING

# / t3 : Timing

# / t1 : Timing

# / t4 : Timing

# / t5 : Timing

# / t6 : Timing

# / t7 : Timing

# / t8 : Timing

+ / p2 : MEMORY

INTERACTION

+ / p2 : RECORDING~

8/3/2019 karthik chb0911015

26/34



Fig 3. 2 State Diagram

3.6.2 Capsule Structure Diagram

Fig 3. 3 Capsule Structure Diagram

/ bhR1 : dvr

/ bvR1

: INTERACTION

+ / p1: RECORDING

+ / p2: MEMORY

+ / p2

: RECORDING~/ bhR1 : dvr

+ / p1: RECORDING

+ / p2: MEMORY

/ bvR1

: INTERACTION

+ / p2

: RECORDING~

8/3/2019 karthik chb0911015

27/34



3.7 Results Discussion

The whole system is tested according to the test cases developed in section 2.8

Fig 3. 4 Test Execution 1

Tc-0 is tested

8/3/2019 karthik chb0911015

28/34



Testing for tc-2

Fig 3. 5 Testing Case2

The testing for tc-0 is done in above slide

Entering date , start time, end time for recording

Tc-1,tc-3,tc-4,tc-5 testing is started in next testing case

8/3/2019 karthik chb0911015

29/34



Fig 3. 6 Testing Case3

In the above output every test case is tested

After stopping main menu is displayed again

3.8 conclusion

The concepts of both Structured Analysis and Object Oriented Analysis along with Object

Oriented Design have been used to prepare a model of the system to be implemented. Also test cases

where established for which test stubs where created and tested to check the interface and the overall

8/3/2019 karthik chb0911015

30/34



working of the system. It can be seen that RRRT is an effective tool to create these models both quickly

and efficiently.

3.9 Comments on Learning Outcome

By solving this assignment I came across many issues with related with real time concepts.When I started solving these assignment came to know the lot of methods that I was not knowing

before. This assignment made to learn many things as well as some concepts got refreshed. By this,

I found that I can solve some problems by using different methods such as structural and object

oriented and UML.

8/3/2019 karthik chb0911015

31/34



References

________________________________________________________________________________

[1] Humphrey W.S. , Characterizing the software process, IEEE Software, march 1988

[2] Humphrey W.S., Managing the software process, Addison Wesley, 1989

[3] Paulk M.C., Curtis B., Chrissis M.B., Capability maturity model for software, Software

engineering

institute, CMU/SEI-91-TR-24, DTIC Number AD240603, august 1991

[4] Paulk M.C., Curtis B., Chrissis M.B.,Weber C.V., Capability maturity model for software,

Version

1.1. Software engineering institute, CMU/SEI-93-TR-24, august 1993

[5] http://www.sqa.net/iso9126

8/3/2019 karthik chb0911015

32/34



APPENDIX A

///////////////////DVR/////////////////

int hh,mm,ss,time,a,D,M,Y;

cout

8/3/2019 karthik chb0911015

33/34



cout

8/3/2019 karthik chb0911015

34/34


cout

Documents

karthik chb0911015