Karthik chb0911015

MSRSAS - Postgraduate Engineering and Management Programme - PEMP
ASSIGNMENT EMBEDDED COMMUNICATION

POSTGRADUATE ENGINEERING AND MANAGEMENT PROGRAMME (PEMP)
SYSTEM
Module Code Module Name Course Department
ESD 525 Real Time Software Engineering M.Sc in Real-Time Embedded Systems Computer Engineering
Name of the Student Reg. No Batch Module Leader
Karthik.K CHB0911015 Full-time 2011 Mr. Deepak V
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
Declaration Sheet
Student Name Reg. No Course Batch Module Code Module Title Module Date Module Leader Karthik k CHB0911015 Real Time Embedded System FT-11 ESD525 Real Time Software Engineering to 08-11-2011 03-12-2011 Mr. Deepak V Batch FULL-Time 2011
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 submission

Unless you have submitted proof of mitigating circumstances or have been granted an extension, the penalties 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 to ensure that the receipt of a late assignment is recorded in the ARO. If an extension was agreed, the authorization 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.
Declaration
The assignment submitted herewith is a result of my own investigations and that I have conformed to the guidelines against plagiarism as laid out in the PEMP Student Handbook. All sections of the text and results, which have been obtained from other sources, are fully referenced. I understand that cheating and plagiarism constitute a breach of University regulations and will be dealt with accordingly.
Signature of the student Karthik k Submission date stamp

(by ARO)
Date
03-11-2011
Signature of the Module Leader and date
Signature of Head of the Department and date
ii
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.
iii
Contents
____________________________________________________________________________ Declaration Sheet .......................................................................................................................... ii Abstract ........................................................................................................................................ iii Contents ....................................................................................................................................... iv List of Tables ............................................................................................................................... vi List of Figures ............................................................................................................................. vii List of Symbols .......................................................................................................................... viii PART-A ........................................................................................................................................ 1 CHAPTER 1 ................................................................................................................................. 1 1.1 Introduction......................................................................................................................... 1 1.2 Literature survey on characteristics of ISO&CMM ........................................................... 1 1.2.1 Characteristics of CMM .............................................................................................. 1 1.2.2 Characteristics of ISO .................................................................................................. 2 1.3 Comparisons of the Models ................................................................................................ 2 1.4 Conclusion .......................................................................................................................... 3 PART-B ........................................................................................................................................ 4 CHAPTER 2 ................................................................................................................................. 4 2.1 Introduction......................................................................................................................... 4 2.2 Functional Requirements .................................................................................................... 4 2.4 Entity Relationship Model .................................................................................................. 5 2.5 DATA FLOW MODEL...................................................................................................... 5 2.5.1 CONTEXT LEVEL DIAGRAM ................................................................................. 5 2.5.2 Level 1 DFD .................................................................................................................... 7 2.5.3 Level 2 DFD ................................................................................................................ 8 2.6 DATA DICTIONARY ....................................................................................................... 8 2.7 CFD (Control Flow Diagram) ............................................................................................ 9 2.8 Test cases .......................................................................................................................... 10 iv
PART-C ...................................................................................................................................... 13 CHAPTER 3 ............................................................................................................................... 13 3.1 Introduction....................................................................................................................... 13 3.2 Use cases........................................................................................................................... 13 3.2.1 Data card .................................................................................................................... 13 3.2.2 Sd card slot ................................................................................................................ 13 3.2.3 Copy to DVD ............................................................................................................. 13 3.2.4 Play or pause .............................................................................................................. 13 3.2.5 Rewind & forward ..................................................................................................... 13 3.2.6 Replay or stop ............................................................................................................ 14 3.3 Actors in use case diagram ............................................................................................... 14 3.4 Use case specifications ..................................................................................................... 14 3.5 Use Case Diagram ............................................................................................................ 16 3.6 Capsule in DVR ................................................................................................................ 17 3.6.1 Class Diagram ............................................................................................................ 17 3.6.2 Capsule Structure Diagram ........................................................................................ 18 3.7 Results Discussion ............................................................................................................ 19 3.8 conclusion ......................................................................................................................... 21 3.9 Comments on Learning Outcome ..................................................................................... 22 References............................................................................................................................... 23 APPENDIX A ......................................................................................................................... 24
List of Tables
____________________________________________________________________________ Table1. 1 Difference for ISO & CMM ......................................................................................... 3
Table 2. 1 Data dictionary ............................................................................................................ 9 Table 2. 2 Test cases ................................................................................................................... 12
vi
List of Figures
____________________________________________________________________________
Fig1. 1 Maturity levels .................................................................................................................. 1
Fig2. 1 E-R DIAGRAM ................................................................................................................ 5 Fig2. 2 ZERO LEVEL .................................................................................................................. 6 Fig2. 3 level 1................................................................................................................................ 7 Fig2. 4 level 2................................................................................................................................ 8
Fig 3. 1Use Case Diagram .......................................................................................................... 16 Fig 3. 2 State Diagram ................................................................................................................ 18 Fig 3. 3 Capsule Structure Diagram ............................................................................................ 18 Fig 3. 4 Test Execution 1 ............................................................................................................ 19 Fig 3. 5 Testing Case2................................................................................................................. 20 Fig 3. 6 Testing Case3................................................................................................................. 21
vii
List of Symbols
___________________________________________________________________________
Acronyms
RTES UML DFD OOA RRT FR NFR PSPEC CSPEC
Real Time Embedded Systems Unified Model Language Data Flow Diagram Object Oriented Analysis Rational Rose Real Time Functional Requirement Non- Functional Requirement Process Specifications Control Specifications
Real Time Software Engineering
viii
PART-A CHAPTER 1
1.1 Introduction
The day today software developers can no longer afford to deliver poor quality software developers, modern software development organization are paying a great deal of attention to quality management, the iso was specifically for designed for system development. Today a
growing number of is developers use standard as control of implementing quality systems. Many companies are eager to obtain a certificate because of market pressure. In this session, we discuss the use of standard in control of quality of software. Iso model which is most popular standard in Europe and Japan [1], it is compared with capability maturity model(cmm), which is common standards followed in USA[2][3][4] [3][4].
1.2 Literature survey on characteristics of ISO&CMM

1.2.1 Characteristics of CMM
Fig1. 1 Maturity levels

These levels are described in terms of Key Process Areas. A Key Process Area is a group of related activities considered important for an organization functioning at the appropriate process maturity level. Many organizations may find themselves operating at Level 1,with movement towards themselves Levels 2 and 3 posing a major challenge.
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 is relatively 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 Real Time Software Engineering 2
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 & CMM

ISO Minimum Requirements to become certified With indirect continuous improvement Designed to implement in all industry Development Focused outwards in different views CMM Five-Levels of Certification with explicit Continuous improvement Designed particularly for the software Purpose Focused inwards in different views
Re-certification must be done within one No need of any certification further year Certification will be done by 3rd party not by Certification will be done by SIE(developers the main organization 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 real capabilities 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.
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]
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 Real Time Software Engineering 5
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
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
2.5.3 Level 2 DFD

DATA RECODER
RECORDS DATA
INTERACTS
2D RECORDE R
USER
INTERACTS INTERACTS 3D RECODER
PLAY&PA USE
ACTIVATES
SET-UP BOX
USES FORWARD & REWIND
USES RECORDED DATA
SAVES RECORDED DATA
SAVES RECORDED DATA SAVES RECORDED DATA
DATA BASE
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 Set-up box Hardware Hardware Dth services Records Used recording Real Time Software Engineering for User can interact Signal transmission for Records the data Signal requested by the transmission 8 Description Format
purpose Data base Memory Used
user for User can in load Data this char type is
memory purpose data
database Play & pause Controls Controls data in User can control Signal database Rewind forward Interacts DVR controller & Controls the streaming transmission
Controls data in User can control Signal database the streaming transmission
Used to record User can record Signal data live streaming or transmission future telecasting
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
Fig 2. 1 CFD
INTERACTS
SET-UP BOX
INTERAC TS DVR
USER
REWIND OR FORWARD
PLAY&PA USE
RECORDS
USES
SAVES RECORDED DATA USES SAVES RECORDED DATA
DATA BASE
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
TESTSPCIFICATION/REPORT Test Case/Test Data Test Case Feature Criti cal Test Cases Test Strategy Test Data Test procedure Test Setup Expected Results Test Cycle Obta ined
10
No
Resu lts
TC_0
Enter the N channel displayed
Check
Black
Input
Requir ed
Channel will be
for the Box confor mation
channe displayed l be displa yed will
TC_1
Pause the Y live stream
The live transmi ssion should get paused
Black Box
Signal Live trans transm
Live transmiss ion
missio ission n
will be should paused resume whenever the user
wishes TC_2 length of Y time required for the It should take starting & ending time of recordi ng TC_3 Stop button Y Recodi Black Navig ator Recor ding Recordin g stop will at Black Box Signal trans It should Recoding should at
missio start at start n desire d time given time end given time
recording
& at
ng will Box stop by pressin g this
proces will s stop by
any case by
button
pressin pressing
11
g this this button TC_4 fast forward or skip Y Skippin Black g ads in Box recorde d video Fast forwar ding record ed video button Ads will be skipped by this
commerci als in a recorded video TC-5 Copying recorded content into DVD Y
feature
It should write into DVD
Black Box
Com munic ating perso n
Copyi ng recodi ng conten t into
It should write data into DVD
DVD
Table 2. 2 Test cases
12
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
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 Use case ID Actors Purpose Overview Data card slot UC_1 Set-up box User id for set-up box This is used for security purpose Only person with data card can interact with set-up box Precondition Post condition Cross reference Wont work without data card Works after inserting data card Get the instructions from manual
Use case name Use case ID Actors Purpose Overview
Sd card slot UC_2 Set-up box Memory support in set-up box This is used for copying purpose
Precondition Post condition Cross reference
Can copy data in the slot Copy is completed Get the instructions from manual
14
Use case name Use case ID Actors Purpose Overview Precondition Post condition Cross reference
Copy to DVD UC_3 Set-up box Copying data User can copy data into DVD writer
copying data Copy is completed Get the instructions from manual
Use case name Use case ID Actors Purpose Overview Precondition Post condition Cross reference
Play & pause UC_4 User, DVR For pausing live streaming This is for pausing live streaming
Live streaming Paused live stream Get the instructions from manual
Rewinding& forwarding UC_5 User, DVR For rewinding& forwarding For rewinding For fast forwarding
Precondition Post condition Cross reference Get the instructions from manual
15
Replay or stop UC_6 User , DVR Stopping at desired time Replay of pause content Stopping at desired time
Precondition Post condition Cross reference
Pause of live streaming Stop at recording spot Get the instructions from manual
3.5 Use Case Diagram
data c ard
sd c ard slot set-up box
<no rolename> ( data c ard ) <no rolename> ( sd c ard slot ) <no rolename> ( c opy to dv d )
c opy to dvd
play& pause
DVR New Actor1 forw ard& rewind
<no rolename> ( play& pause ) <no rolename> ( forward& rewind ) <no rolename> ( replay & stop )
<no rolename> ( play& pause ) <no rolename> ( forw ard& rewind ) <no rolename> ( replay & stop ) replay & stop
Fig 3. 1Use Case Diagram
16
3.6 Capsule in DVR

Class name
<<Capsule>> dv r
+ # # # # # # # +
/ / / / / / / / /
p1 : RECOR DING t3 : T iming t1 : T iming t4 : T iming t5 : T iming t6 : T iming t7 : T iming t8 : T iming p2 : MEMORY
Purpose Attributes Operation
Records in the memory recorder Interaction for user Records live streaming
Class name
<< Ca p su le >> IN T E R A CT IO N
+ / p 2 : R E CO R D IN G ~
Purpose Attributes Operation
Interaction recorder Interaction for user
3.6.1 Class Diagram
17
Fig 3. 2 State Diagram

3.6.2 Capsule Structure Diagram
+ / p1 + / p2 : RECORDING : MEMORY + / p2 : RECORDING~
/ bhR1 : dvr
/ bv R1 : INTERACT ION
Fig 3. 3 Capsule Structure Diagram
18
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
19
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
20
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
21
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.
22
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
23
APPENDIX A
///////////////////DVR/////////////////
int hh,mm,ss,time,a,D,M,Y; cout<<"welcome"<<endl; cout<<"insert the card"<<endl; cout<<"Menu"<<endl;
cout<<"1 cout<<"2 cout<<"3 cout<<"4 cout<<"5
HBO "<<endl; GEMINI "<<endl; STAR CRICKET"<<endl; CNN "<<endl; DISCOVERY "<<endl;
cout<<" cin>>a;
enter the channel no ";
switch(a) { case 1:cout<<" HBO LIVE"; t3.informIn(RTTimespec(3,0)); break; case 2:cout<<" GEMINI LIVE"; t4.informIn(RTTimespec(3,0)); break; case 3:cout<<" STAR CRICKET LIVE"; t5.informIn(RTTimespec(3,0)); break; case 4:cout<<" CNN"; t5.informIn(RTTimespec(3,0)); break; case 5:cout<<" DISCOVERY LIVE"; t5.informIn(RTTimespec(3,0)); break; default: cout<<"invalid entry"; p2.signal2().send(); break; } p1.signal1().send(); cout<<"enter for the recording section"<<endl; int b,D,M,Y,hh,mm,ss,time; cout<<"enter the date for recording"<<endl; cin>>D; cin>>M; cin>>Y; cout<<"D:M:Y"; cout<<" the entered date is"<<D<<":"<<M<<":"<<Y<<endl; cout<<"enter the starting time for recording"<<endl; cout<<"hh:mm:ss"; cin>>hh; cin>>mm; cin>>ss; time=((60*mm*hh));
24
cout<<"
the entered
starting time is"<<hh<<":"<<mm<<":"<<ss<<endl;
cout<<"enter the stoping time for recording"<<endl; cout<<"hh:mm:ss"; cin>>hh; cin>>mm; cin>>ss; time=((60*mm*hh)); cout<<" the entered stoping time is"<<hh<<":"<<mm<<":"<<ss<<endl; t1.informIn(RTTimespec(5,0)); cout<<"enter for the recording section"<<endl; int b,D,M,Y,hh,mm,ss,time; cout<<"enter the date for recording"<<endl; cin>>D; cin>>M; cin>>Y; cout<<"D:M:Y"; cout<<" the entered date is"<<D<<":"<<M<<":"<<Y<<endl; cout<<"enter the starting time for recording"<<endl; cout<<"hh:mm:ss"; cin>>hh; cin>>mm; cin>>ss; time=((60*mm*hh)); cout<<" the entered starting time is"<<hh<<":"<<mm<<":"<<ss<<endl; cout<<"enter the stoping time for recording"<<endl; cout<<"hh:mm:ss"; cin>>hh; cin>>mm; cin>>ss; time=((60*mm*hh)); cout<<" the entered stoping time is"<<hh<<":"<<mm<<":"<<ss<<endl; cout<<"enter for the recording section"<<endl; int b,D,M,Y,hh,mm,ss,time; cout<<"enter the date for recording"<<endl; cin>>D; cin>>M; cin>>Y; cout<<"D:M:Y"; cout<<" the entered date is"<<D<<":"<<M<<":"<<Y<<endl; cout<<"enter the starting time for recording"<<endl; cout<<"hh:mm:ss"; cin>>hh; cin>>mm; cin>>ss; time=((60*mm*hh)); cout<<" the entered starting time is"<<hh<<":"<<mm<<":"<<ss<<endl; cout<<"enter the stoping time for recording"<<endl; cout<<"hh:mm:ss"; cin>>hh; cin>>mm; cin>>ss; time=((60*mm*hh)); cout<<" the entered stoping time is"<<hh<<":"<<mm<<":"<<ss<<endl; cout<<"1 Pause "<<endl; cout<<"2 Forward "<<endl;
25
cout<<"3 Rewind "<<endl; cout<<"4 Stop "<<endl; int no,n=1; while(n<2) { cout<<"enter the no value"<<endl; cin>>no; switch(no) { case 1:cout<<"paused????"<<endl; break; case 2:cout<<"Forward........................"<<endl; break; case 3:cout<<"rewinding......................"<<endl; break; case 4: n=3; cout<<"stop"<<endl; cout<< "@!@ "<<endl; cout<<" ! "<<endl; cout<<" ! "<<endl; break; default:cout<<"invalid entry"<<endl; break; } } t8.informIn(RTTimespec(1,0));
26

Karthik chb0911015

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Karthik chb0911015

Hochgeladen von

Copyright:

Verfügbare Formate

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

ASSIGNMENT EMBEDDED COMMUNICATION

Name of the Student Reg. No Batch Module Leader

Karthik.K CHB0911015 Full-time 2011 Mr. Deepak V

M.S.Ramaiah School of Advanced Studies

Penalty for late submission

Signature of the student Karthik k Submission date stamp

Signature of the Module Leader and date

Signature of Head of the Department and date

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

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

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

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

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

RTES UML DFD OOA RRT FR NFR PSPEC CSPEC

Real Time Software Engineering

1.2 Literature survey on characteristics of ISO&CMM

Fig1. 1 Maturity levels

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

1.3 Comparisons of the Models

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

Table1. 1 Difference for ISO & CMM

Real Time Software Engineering

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

2.2 Functional Requirements

2.3 Nonfunctional Requirements

Real Time Software Engineering

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

2.4 Entity Relationship Model

Fig2. 1 E-R DIAGRAM

2.5 DATA FLOW MODEL

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

Level 0 Level 1 Level 2

Fig2. 2 ZERO LEVEL

Real Time Software Engineering

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

2.5.2 Level 1 DFD

Real Time Software Engineering

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

2.5.3 Level 2 DFD

USES RECORDED DATA

SAVES RECORDED DATA

SAVES RECORDED DATA SAVES RECORDED DATA

2.6 DATA DICTIONARY

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

purpose Data base Memory Used

user for User can in load Data this char type is

memory purpose data

Table 2. 1 Data dictionary 2.7 CFD (Control Flow Diagram)

Real Time Software Engineering

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

SAVES RECORDED DATA USES SAVES RECORDED DATA

2.8 Test cases

Real Time Software Engineering

MSRSAS - Postgraduate Engineering and Management Programme - PEMP

Enter the N channel displayed

for the Box confor mation

channe displayed l be displa yed will

Pause the Y live stream

The live transmi ssion should get paused