High level design

After SRSD, the document which we prepared is HLD.
HLD is a high level design document where we found out the modules of our project.
In this document we have design the complete architecture of the project. We also named the modules and also designed the control flow diagram for each and every module of the project.
We identified data types and storage classes for each and every variable.

We have modules like:
1. Initialization module
2. Validation module
3. Input and output modules etc

We also had a session on “Embedded System in Defence Perspective”.
In this we learnt about Real time systems, spy satellites, cruise missiles etc.

Testing plan

After SRSD we got template for preparing testing plan for user acceptance testing and system testing. This template was very confusing and we did not know what should be filled in the template. We tried to fill this template, but all the points were looking like same thing. The template contained the columns like Action, Function, Testing Data and Pre Requisites.

We had a teleconference with our quality expert, he cleared the doubts.

We got to know the difference between
1. Action and Function
2. Testing Data and Pre Requisites
3. User acceptance testing and System testing
I also learnt how to fill this template and what should be filled in the template.
I learnt preparing test cases,what should we fill in each and every column,naming conventions for use case_id and test case_id.

V model

In our project we are using V model for developing software. Almost all the softwares in avionics follow V model for developing.

Before this we studied Water fall model, Spiral model and also studied the differences of all these 3 models. We conclude this was the best model that is used in avionics.

Objectives of V model:
1. Minimization of project Risk.
2. Quality is guaranteed.
3. This model is cost effective.

SRSD

Ahhhh! At last we prepared SRSD and we delivered the document for approval. After approval the deliverable will be mailed to our client.


When our client explained about ALS (Aircraft Landing Scheduler), I taught the project is simple, and we started to write the code. I did not know that we should prepare a SRSD before coding. As the day passed I came to know that we should prepare few documents before coding, i.e. SRSD, HLD-high level design document, DDD-detail design document etc.
That day I went home and started to browse internet and I came to know about SRSD, HLD, DDD.It took me whole night to know about these documents. That night I realized before preparing SRSD we should know so many things about the domain and also we should capture requirements from the client. Now I have an idea about SRSD.I also learnt, what and all should be included in SRSD.
The outline of SRSD that we have prepared in our project.

TABLE OF CONTENTS
Revision History
1.Introduction

1.1.Product Overview

1.2.Purpose

1.3.Scope

1.4.Reference

1.5.Definitions and Abbreviations

2.Overall Description

2.1.Product Purpose

2.2.Product Functions

2.3.User Characteristics

2.4.General Constraints

2.5.Assumptions and Dependency

3. Specific Requirements
3.1.External Interface Requirements
3.1.1.User interface
3.1.2.Hardware Interface
3.1.3.SoftwareInterface

3.1.4 Operations
3.2 Software System Attributes
3.2.1 Reliability
3.2.2 Availability
3.2.3 Security

3.2.4 Maintainability
3.2.5 Portability
3.2.6 Performance

3.4 Database Requirements

3.5 Risk Analysis

I learnt many things while preparing SRSD.I learnt how an aircraft lifts takes place, naming the runways, basic aerodynamics. I learnt how does communication takes place between pilot and ATC (Air Traffic Controller).Day by day my confidence level is increasing by learning all these.

In SRSD we included use cases, which are inputs for test cases when we proceed for testing.

We also did Risk analysis to make the project proceed smoothly without any problems.
Risk analysis contains two parts:
1. Risk of the system
2. Risk of the project

Preparation of SRSD

My training started and I was very happy on my first day as I joined a corporate training. On first day of our training we introduced each other and we went through some concepts of C programming.
In avionics the first and basic step is to learn C programming concepts like functions, pointers, arrays, structures etc. So the first week discussion was on C concepts. In First week I came to know the importance of C in avionics because in avionics all the systems will work on embedded C.

The second week we got a real time project that is Aircraft landing scheduler.
The idea of the project is scheduling the aircrafts for safe landing according to the priority. By seeing this, you may think the project is very simple but it is very complex real time systems.
After I finished my engineering, I was thinking coding is the difficult part to develop software. Before coding there are many steps which is most difficult than coding.
In this project I’m undergoing a software lifecycle. At present we are preparing a software requirement specification document. In SRSD the main thing is to capture requirements from the client, this is the most difficult part of software life cycle.

To prepare SRSD of our project, we need knowledge of avionics domain. We also have a Tech Lead who gives the domain knowledge of avionics.