A memorable journey

Topic: A memorable journey

A memorable journey is that which clicks in your mind, it is that moment which impressed you a lot. I travelled a lot in my life but the most shining and the most memorable journey of my life is when I went to the Fair, it was famous by its name that is LUCKY IRANI CIRCUS which was held in the city Lahore. Lahore is the famous city of Pakistan.

Lucky Irani circus was on 25th of December. We started our journey two days earlier from Karachi .We were not came from Plane, we started our journey by car. It took long time to reached Lahore. When we arrived in Lahore, we book a guest house for taking some rest. We arrived Lahore a day earlier .After that day, the sun rises, I woke up and took bath quickly because I was much exited, and during I took bath, my mother prepared the breakfast for us. I quickly wear my T-Shirt and New Jeans and eat my breakfast. Then whole family started to load luggage in our car. So, finally the time came, we went the place where the fair was held.

In fair, there was a shop where there was a girl like snake. The head of that snake is of little girl and the rest was snake. At that instance we were much afraid of that appearance of snake. It was very horrible and terrible to watch. So we quickly went out from that shop. After that we went to some kind of that shop in which a man drives car circularly on the walls of well. I was so interesting to watch that show. After that we ate some GOAL GAPPAS and DAHI BHARAY which were very tasty. Actually we enjoyed in such a way that we never enjoyed ever in our lives. After the whole event we came back to guest house and spent a night and leave guest house earlier on next day and reached Karachi safely after a whole day driving. It was a memorable journey for me and for my whole family because we enjoyed a lot during this journey.

SRS-Software Requirement specification

Software Requirement specification
SRS

1.  INTRODUCTION

                                   This SRS document is for a software house’s website (Anysoftwarehouse.com) This document provides overview of the SRS for our website.It includes purpose of our website. It provides scope of website and definitions and reference and the overview is also written in SRS.

1.1         Purpose the purpose of this SRS document is to define website’s functionality, parameters and goals, requirements for design, requirements of clients which he wants from our software house. It may also contains the description and sequence of steps to build this site

1.2   Scope   our website will provide all information about our services, our reliable and remarkable projects, our recent projects and quality which will help people to make decisions about which is best for them. There will be login panel for users, employees and authority. People can contact our developers to get information about their products and about any query.

 

        1.3   Definitions, Acronyms, Abbreviations

SRS	Software Requirement specification
Admin	Manager of System
User	Someone Interacts with System
Privileged  user	User having Specific  Rights
IEEE	Institute of Electrical and Electronics Engineering
FAQ	Frequently Asked Questions
ASP	A Programing Language

 

      1.4    References

IEEE Guide for Developing Software Requirements Specifications, IEEE Std 1233, 1998 Edition,   

IEEE Software Engineering Standards Committee, “IEEE   Std   830-1998,   IEEE Recommended Practice for Software Requirements Specifications”, 1998.

      1.5    Overview

                    Remaining section is about the system, data requirements and characteristics of the user. The 1st section of this document is about the purpose and scope of this product and second Section is about the system, in this section system or product is described which consist of functionality of the web and its interaction with the user and with system on which it is running and the 3^rd section of this document is about the requirements of the system in detail including performance and functional requirements and also external interface.

2.   Overall Description  

                                                      This Document provides the background for those requirements which are described in section 3 like external interface, performance and functional requirements, these information are described in such a way that these are easily understandable. This is overview of the system. It also provides information about the stakeholder and its nature which is going to use it. Last part is about the constraints and assumptions

   2.1 Product Perspective As our website is independent so it is not a part of any larger system. Our website is totally self-contained so it is not dependent to any other site or program.

Our site has ability to operate in different constraints like as:

             1- System Interface

             2- User interface

             3- Hardware Interface

             4-Software Interface

             5- Memory Constraints

             6- Operations

             7- Site adaption Requirements

   2.1.1   System Interface System interface may consist of CPU monitor and the user of system. User may be a visitor of the site or the client of our software house. User can visit our website, our work, our projects, latest events occurring in our software house and the latest news and also can contact our developers about their queries and their requirements about their product.

   2.1.2    User Interface A user can visit our website, can search within our site, can view our gallery, can contact to our developers but he will not be able to make any kind of change to our site. He can use our site at different web browsers it is flexibility of our site. He can also view website in different configuration. So user interface is consisting of configuration characteristics. 

   2.1.3    Hardware Interface This is about the type of the hardware which should use for our website and it also includes other specific hardware like mouse, keyboard and printer. Is Keyboard can operate on our site or not similarly specified situations in which a mouse should operate or not. Hardware and Processor should be most efficient so a user may get best results.

   2.1.4    Software Interface Software Interfaces includes required software product to complete the project. As for the front end of the website visual studio may be used and for the back end and for storing record Oracle database is used. So different software used in completing the project

   2.1.5   Memory Constraints Our website has taken 5MB space of Computer’s Secondary Memory.     

   2.1.6   Operations Our website provides different modes of operations such as management operations and authorized operations     

   2.1.7   Site adaptation requirements our website will represent our software house. This will help us to show our achievements. People will visit this and they will be assured that we can fulfill their needs in a best way.

2.2   Product Functions

                                      This includes all the major functions of the website which it will perform as management and authorized functions. Admin can make changes to the site. He can update the data, news, events and Projects and a user can view all these things. Workers can also create their accounts and can see their current status and details. Visitors will be able to contact to the developers for any query. Our website will consist of following menus or pages:

Home:   All basic information will be on homepage.

News & Events:   This will consist of all latest news and occurring Events of our software house.

Projects:   our all completed projects will be listed in this menu. A visitor can visit them.

Register:   This menu is for the registering the privileged users.

Login:   This is for the admin and privileged user to login to the site.

Contact us:   Visitors can contact to our admin for any query or can give their feedback.

2.3   User characteristics

                                        User of the website may be a client, worker and Admin.

A client usually can visit our site and will see our projects and services and can contact our developers if he wants a service from us or simply he can feed back us.

An employee or worker can just login to his account and can see and update his current status and details.

On the other Hand, Admin can visit the site, login and can make changes and updates the data.

 

 2.4   Constraints

                                                                 Developer  should  limit  the  privileges  of  the  user  so  that  they  cannot  harm  system  server. Website should be efficient and it should work on all browsers without any problem and issue

 2.5   Assumption and dependencies

                                                                                      To run a website a source or operating system as Windows and Mac or Mobile is required, so it is a dependent and without any operating system a website can’t run so operating system is necessary for it          

3. Specific Requirements                              

                                            This section is about the inputs and outputs. Inputs which our website can support and what will be the required outputs.

3.1 External Interface

                                   External interface is about the interaction with website of the user or admin. User and privileged users can visit site, they can use register button to register in the site and have facility to login. Admin can login to the site and can perform different operations. If admin or privileged user enter wrong name or password( which is not same as were in register form) to login then site will not give access to their account and operation will be fail and then he can try again to login. In login panel characters, symbols and numbers will be supported. 

3.2 Functions  

                     Visitors can only visit the site they are not allowed to make any change in the site.

Employee can register himself and then can see his details, on the other hand admin can make changes to the site and can manage the data but for this he have to login to the site and for the login he have to write correct information in login input boxes, if he inputs wrong information then site will reject it and he have to input correct information. Privileged users have to provide all required                              information to site to register. He is allowed to use characters and numbers and symbols in input fields.

3.3 Performance Requirements

                                                                                     Since a website may be viewed by hundred, thousand viewers simultaneously so it should in such condition that it can handle this number of viewers. So for this purpose there should be enough powerful server machines and high speed internet access and its data base should also capable to manage this number of users at the same time.

3.4 Standard compliance

                                                               Database will store all records and data and when changes are made then database will store updates.

3.5 Design constraints

                                                               This should specify design constraints that can be imposed by other standards, hardware limitations.                 

3.6 Software System Attributes                                                                                                     

                                             There are a number of attributes of software that can serve as requirements. It is important that required attributes be specified so that their achievement can be objectively verified.

3.6.1 Reliability

                All functions of the website are fully reliable and fulfil the requirements.

3.6.2 Availability

                Required functions are available and able to perform at their demand.

3.6.3 Security

                Website’s security is strict. Visitors just can visit the site and cannot make any change to the site. No one can login to another’s account and see their information.

3.6.4 Maintainability

                Maintenance can be performed at any time when needed. Functions of the site are easily modifiable.

3.6.5 Portability

                 Website can run on any operating system such as windows, Linux and mac. It can run on any web browser.

3.7 Organizing the specific Requirement

                                                                          

3.7.1 System Mode

                                         Our website can run on normal mode.

3.7.2 User Class

                                       There are 3 types of user

            1. Admin

            2. Employee

            3. Privileged user

3.7.3 Objects

                               Different objects can perform different actions depending on their role.

Sets of objects may share attributes and services. These are grouped together as classes.

  3.7.4 Feature

Our website includes different features like News, Events, projects, Expertise, register & Login page which perform different functions and each of these pages having different features respectively.

  3.7.6 Response

                 Functions defined in the form of Response:

Response 1: All Users interacting with the system.

Response 2:  All functions performed by the users.

3.8 Additional Comments

                All the required functionalities of system are described above are working properly. All inputs and outputs are Responsive.  All  the document is created using English language.

peshawar attack DP

Attack in peshawar DP

We in the condolence of peshawar attack will change our dps's of atleast 3 days.

Polymorphism in OOP

Polymorphism and virtual functions

Polymorphism

The word Polymorphism is a combination of two words i.e poly and morphism. Poly means many and morphism mean form. In object-oriented-programming, Polymorphism is the cability of objects of different types two reply to the functions of the same name.The user  not have to know the exact type of the object in advance. The action of the object can be apply at the run time. It is called Late-Binding or Dynamic binding. Polymorphism is implemented by using virtual functions.

Pointer to objects

A pointer can also refer to an object of a class. The member of an object can be accessed through pointers by using the symbol - >. The symbol is known as member access operator.

Syntax

The syntax of referencing an object with pointer is as follow:

ptr-> member.

Virtual Function

                     Virtual means existing effect but not in reality. A type of function that appears to existing some part of a program but does not exist really is called virtual function. Virtual functions are used to apply polymorphism. They enable the user to execute completly different by same function call. 

                     A virtual function is defined in the parent class and can overridden is child classes. It is defined by using the key word virtual.

Early Binding

                   The assignment of types to variables and expressions at compilation time is known as early binding.It is also called static binding. The early binding occurs when every thing require to call a function is known at compile time. Early binding enables the the compiler to know exactly which function will be called when a certain statement is executed.

                   When a program is compiled, the compiler cheaks the functions call and decides which function is to be executed. This process takes place during compilation process in normal programs with functions.It is an example of early binding.

Late Binding

The assignment of types to variables and expression at execution time is known as late binding. It is also known as dynamic binding. The late binding occurs when some information to call a function is decided at execution time. The compiler does not know at compile time which function will be executed.It provide more flexibility.

The use of virtual function to implement polymorphism is an example of late binding. In virtual functions, the compiler does not know at compile time which object is reffered by the pointer. The compiler executes the function depending on the contents of the pointer rather then the type of compiler.

Sandwich Model in SE

Requirement and Modeling
or
Sandwich Model

                             It is important to understand the relationship between requirement management and system modeling.They are mutually supportive activities that should not be equated.We can compare this relationship  to the terminology 'SANDWICH'.

                             In this analogy,Requirement Management is the "Bread & butter" of development cycle.The "Filling" is provided by the system modeling layer explains the analysis and design that has led to the subsequent layers of requirement.Some People talk about the requirement modeling. This is a misnomer.You infact model the system design, not requirement.
                         

                             'Modeling' supports the design activity and is where most of the creative work takes place. It assists the engineer in understanding enough of the system to decompose the requirements at a particular level into the next level down. The requirements themselves are a complete snapshot of what is required a teach level in increasing level of details.

Requirement and modeling

                                  A model is an abstraction of a system that deliberately focuses on some aspects of a system to the exclusion of others. Models exist the requirement engineers in analyzing  this requirements at a particular level so as to:

• Communicate with the customer and improve mutual understanding of the system to be developed.
• Determine how to satisfy the requirements.

Software configuration management

Presentation on Software configuration management 

The topic of my today's presentation is Software configuration management. Firstly we see that what is meant by configuration?

What is configuration?

The way a computer system or program is prepared for particular use is known as configuration.For example we will see that a simple USB have multiple functions i.e we can store data or make it boot-able drive,so in both cases we actually configure that USB to our point of use.

What is Software Configuration Management?

In software engineering,configuration management is a task of tracking and controlling the change in software system.

or

Configuration management is concerned  with the policies,processes and tools for managing changing software system.

Implementation of Configuration Management 

• Configuration management is useful for individual projects or personal software process (PSP) as it is easy for one person to forget what changes have been made.
• It is also essential for Team projects or Team software process (TSP) where several developers are working at same time on a software system.Sometimes,these developers are all working at same place but sometimes development team are distributed with members in different locations across world.

Standards for configuration management

• IEEE 828-(1998)
• IEEE 1042

Activities involves in Configuration Management

There are several activities involve in configuration management.These are given below:-

Change Management

The management of change and development within a business or similar organization.

Version Management

This involves keeping track of multiple versions of system components and ensure that changes have been made to components.

System building

It is the process of integrating program components,data and libraries and then compiling and linking these to create executable system.

Release Management

It is the process of managing software releases from development stage to software release.It is new but rapidly growing discipline with in software engineering. 

Software configuration management

Configuration management in terms of Quality

Configuration management is sometimes considered to be a part of Software quality management with same manager having both:

• Quality management responsibilities
• Configuration management responsibilities

When a new version of software has been implemented,it is handed over by the development team to quality assurance team (QA) .The QA team cheaks that system quality is acceptable. If so,all changes to system have to agreed on and recorded before they are implemented.

Terminologies

One of the problems of configuration management is that different companies talk about the same concept using different term,so that's why different terminologies were introduced.

Configuration Item

Anything associated with a software project e.g design,code,test data,document, etc that has been placed in configuration control.

Base-Line

A specification or product that has been formally reviewed and agreed by responsible management, that thereafter serves as the basis for further development.

It should always be possible to re-create a base-Line from its constituent components.

Version

The re-release of a configuration item is called its version.Versions have always a unique identifiers,which is often composed of the configuration item name plus version number.

Release

A version of a system that has been released to customers for use.

Main-Line

A sequence of base-lines representing different versions of system.

What is meant by Inheritance in OOP?

Inheritance

                            A programming technique that is used to reuse an existing class to build a new class is known as inheritance.The new class inherits all the behavior of the original class. The existing class that is re-used to create a new class is known as super class,base class,or parent class.The new class that inherits the properties and functions of an existing class is known as subclass,derived class or child class.The inheritance relationship between the classes of program is called a class hierarchy .

                            Inheritance is one of the most powerful feature of object-oriented-programming.The basic principle of inheritance is that each subclass shares common properties with the class from which it is derived.The child class inherits all capabilities of the parent class and can add its own capabilities.

Example

                           Suppose we have a class named Vehicle.The subclass of this class may share similar properties such as wheels and motors etc. Additionally, a subclass may have its own particular characteristics.For example,a subclass Bus may have seats for people but another subclass.Truck may have space to carry goods.

            A class of animals can be derived in to sub classes like mammals,amphibians,insects,reptiles.A class of vehicles can be divided into cars,trucks,buses,and motorcycles.A class of shapes can be divided into the sub-classes lines,ellipse and boxes,etc.  

Super class and sub classes in inheritance

                 
The above figure shows that vehicle is parent class and bus,truck and motorcycle are three sub classes.The upward arrows indicate that the sub classes are derived from the parent vehicle class.