Thursday, 13 October 2016

Yaad aataa hai roz O shab koi

Yaad aataa hai roz O shab koi
Hum se rutha hai be sabab koi

Lab E joo chhaaoN me darakhtoN ki
Woh mulaaqaat thi ajab koi!!

Jab tujhe pahli baar dekhaa tha
Woh bhi tha mausam E tarab koi

Kuchh khabar le K teri mahfil se
Door baitha hai jaaN ba lab koi

Na Gham E zindagi na dard E firaaq
Dil meN yuNhi si hai talab koi

Yaad aati haiN door ki baateN
Pyaar se dekhta hai jab koi

ChoT khaayi hai baarhaa lekin!
Aaj to dard hai ajab koi

Jin ko mitna tha mit chuke ‘Nasir’
Un ko ruswaa kare na ab koi

Wo sahilon pe gaane waale kya hue by Nasir Kazmi

Wo sahilon pe  gaane waale kya hue
Wo kashtiyan Chalane waale kya hue
wo dil mennkhubne waali aankheN kya huiN
Wo hont muskuraane waale kya hue
Wo subh aate aate rah gayi kahan
Jo qaafle the aane waale kya hue
MaiN jin ki raah dekhta hun rat bhar
Wo raushani dikhane waale kya hue
Ye kaun log hain mere idhar udhar
Wo dosti nibhaane waale kya hue
Imaaraten to jal k rakh ho gayin
Imaaraten banaane waale kya hue
Ye aap ham to bojh hain  zamin ka
Zamin ka bojh uthaane waale kya hue

Kya zamana tha k har roz mila karte the

Kya zamana tha k har roz mila karte the
Raat bhar chaNd k hamraah phira karte the
JahaaN tanhaaiyaaN sar phoR k so jati haiN
Un makaanoN main ajab log raha karte the
Kar diya aaj zamaane ne unhen bhi majbur
Kabhi yeh log mere dukh ki dawa karte the
Dekh kar jo hamain chup chap guzar jata hai
Kabhi us shakhs ko hum pyar kiya karte the
IttefaaQaat E zamana bhi ajab haiN ‘Nasir’
Aaj woh dekh rahe haiN jo suna karte the

Software Requirements Specification


Software Requirements Specification
for
<Project>


Table of Contents
Table of Contents........................................................................................................................... ii
Revision History............................................................................................................................. ii
1.   Introduction.............................................................................................................................. 1
1.1   Purpose................................................................................................................................. 1
1.2   Document Conventions........................................................................................................ 1
1.3   Intended Audience and Reading Suggestions........................................................................ 1
1.4   Product Scope....................................................................................................................... 1
1.5   References............................................................................................................................ 1
2.   Overall Description.................................................................................................................. 2
2.1   Product Perspective.............................................................................................................. 2
2.2   Product Functions................................................................................................................. 2
2.3   User Classes and Characteristics........................................................................................... 2
2.4   Operating Environment......................................................................................................... 2
2.5   Design and Implementation Constraints................................................................................ 2
2.6   User Documentation............................................................................................................. 2
2.7   Assumptions and Dependencies........................................................................................... 3
3.   External Interface Requirements........................................................................................... 3
3.1   User Interfaces..................................................................................................................... 3
3.2   Hardware Interfaces............................................................................................................. 3
3.3   Software Interfaces............................................................................................................... 3
3.4   Communications Interfaces.................................................................................................. 3
4.   System Features....................................................................................................................... 4
4.1   System Feature 1.................................................................................................................. 4
4.2   System Feature 2 (and so on)................................................................................................ 4
5.   Other Nonfunctional Requirements....................................................................................... 4
5.1   Performance Requirements................................................................................................... 4
5.2   Safety Requirements............................................................................................................. 5
5.3   Security Requirements.......................................................................................................... 5
5.4   Software Quality Attributes.................................................................................................. 5
5.5   Business Rules...................................................................................................................... 5
6.   Other Requirements................................................................................................................ 5
Appendix A: Glossary................................................................................................................... 5
Appendix B: Analysis Models....................................................................................................... 5
Appendix C: To Be Determined List........................................................................................... 6


Name
Date
Reason For Changes
Version












1.     Introduction

1.1     Purpose

<Identify the product whose software requirements are specified in this document, including the revision or release number. Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem.>

1.2     Document Conventions

<Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities  for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.>

1.3     Intended Audience and Reading Suggestions

<Describe the different types of reader that the document is intended for, such as developers, project managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type.>

1.4     Product Scope

<Provide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its contents here.>

1.5     References

<List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.>

2.     Overall Description

2.1     Product Perspective

<Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major components of the overall system, subsystem interconnections, and external interfaces can be helpful.>

2.2     Product Functions

<Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, is often effective.>

2.3     User Classes and Characteristics

<Identify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. Distinguish the most important user classes for this product from those who are less important to satisfy.>

2.4     Operating Environment

<Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.>

2.5     Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).>

2.6     User Documentation

<List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.>

2.7     Assumptions and Dependencies

<List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).>

3.     External Interface Requirements

3.1     User Interfaces

<Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.>

3.2     Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.>

3.3     Software Interfaces

<Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.>

3.4     Communications Interfaces

<Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.>

4.     System Features

<This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.>

4.1     System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1      Description and Priority
<Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).>
4.1.2      Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.>
4.1.3      Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.>

<Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.>

REQ-1:   
REQ-2:   

4.2     System Feature 2 (and so on)

5.     Other Nonfunctional Requirements

5.1     Performance Requirements

<If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.>

5.2     Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.>

5.3     Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.>

5.4     Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.>

5.5     Business Rules

<List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they may imply certain functional requirements to enforce the rules.>

6.     Other Requirements

<Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.>
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>
<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked to closure.>

Source: http://www.frontiernet.net/~kwiegers/process_assets/srs_template.doc


Tuesday, 11 October 2016

The concept of Software as a Service

Web services and web pages
Web services are very different from Web pages that also provide access to applications across the Internet and across organizational boundaries. Web pages are targeted at human users, whereas Web services are developed for access by humans as well as automated applications. As terminology is often used very loosely, it is easy to confuse someone by describing a “service” as a Web service when it is in fact not. Consequently, it is useful to examine first the concept of software-as-a-service on which Web services technology builds and then compare Web services to Web server-based functionality.

Software as a Service
The concept of software-as-a-service is revolutionary and appeared first with the applications service provider software model. Application service providers (ASPs) are companies that package software and infrastructure elements together with business and professional services to create a complete solution that they present to the end customer as a service on a subscription basis. An ASP is a third-party (service organization) that deploys, hosts, and manages access to packaged applications at a centrally managed facility for multiple customers across a network, offering application availability and security.
Applications are delivered over networks on a subscription or rental basis, and end users access these applications remotely using Internet or leased lines. In essence, ASPs were a way for companies to outsource some or even all aspects of their IT needs.

Function of Application service providers 
The basic idea behind an ASP is to “rent” applications to subscribers. The whole application
is developed in terms of the user interface, workflow, business, and data components that are all bound together to provide a working solution. An ASP hosts the entire application and the customer has little opportunity to customize it beyond setting up tables,or perhaps the final appearance of the user interface (such as adding company logos).
Access to the application for the customer is provided simply via browsing and manually initiated purchases and transactions occur by downloading reports. This activity can take place by means of a browser. This is not a very flexible solution, but offers considerable benefits in terms of deployment providing the customer is willing to accept it “as is”. By providing a centrally hosted Internet application, the ASP takes primary responsibility for managing the software application on its infrastructure, using the Internet as the conduit between each customer and the primary software application. What this means for an enterprise is that the ASP maintains the application, the associated infrastructure, and the customer’s data, and ensures that the systems and data are available whenever needed.
An alternative of this is where the ASP is providing a software module that is downloaded to the customer’s site on demand – this is for situations where the software does not work in a client/server fashion, or can be operated remotely via a browser. This softwaremodule might be deleted at the end of the session, or may remain on the customer’s machine until replaced by a new version, or the contract for using it expires. Although the ASP model introduced the concept of software-as-a-service first, it suffered from several inherent limitations such as the inability to develop highly interactive applications, inability to provide complete customizable applications, and inability to integrate applications. This resulted in monolithic architectures, highly fragile, customerspecific, non-reusable integration of applications based on tight coupling principles.
Today we are in the midst of another significant development in the evolution of softwareas-
a-service. The new architecture allows for loosely coupled asynchronous interactions on the basis of eXtensible Markup Language (XML) standards with the intention of making access to, and communications between, applications over the Internet easier.
The Web services paradigm allows the software-as-a-service concept to expand to include the delivery of complex business processes and transactions as a service. Perceiving the relative benefits of Web services technology, many ASPs are modifying their technical infrastructures and business models to be more akin to those of Web services providers. The use of Web services provides a more flexible solution for ASPs. The core of the application – the business and data components – remains on the ASP’s machines, but is now accessed programmatically via Web services interfaces. The customers can now build their own custom business processes and user interfaces.
When comparing Web services to Web-based applications we may distinguish four key differences 
◆ Web services act as resources to other applications that can request and initiate those Web services, with or without human intervention. This means that Web services can call on other Web services to outsource parts of a complex transaction to those other Web services. This provides a high degree of flexibility and adaptability not available in today’s Web-based applications. 
◆ Web services are modular, self-aware, and self-describing applications; a Web service knows what functions it can perform and what inputs it requires to produce its outputs, and can describe this to potential users and to other Web services. A Web service can also describe its non-functional properties: for instance, the cost of invoking the service, the geographical areas the Web service covers, security measures involved in using the Web service, performance characteristics, contact  information, and more.
◆ Web services are more visible and manageable than Web-based applications; the state of a Web service can be monitored and managed at any time by using external application management and workflow systems. Despite the fact that a Web service may not run on an in-house (local) system or may be written in an unfamiliar programming language, it still can be used by local applications, which may detect its state (active or available) and manage the status of its outcome. 
◆ Web services may be brokered or auctioned. If several Web services perform the same task, then several applications may place bids for the opportunity to use the requested service. A broker can base its choice on the attributes of the “competing” Web services (cost, speed, degree of security).

Introduction to web services


What are Web Services?
Web services are an emerging technology that enables disparate applications running on different machines to exchange data and integrate with one another without requiring additional, proprietary third-party software or hardware.

Function of Web services
Web services are self-describing and self-contained network-available modules that perform concrete business functions and are deployed easily because they are based on common industry standards and existing technology, such as XML and HTTP.

Advantages of Web Services
·        Applications that rely on the Web services paradigm can exchange data regardless of the language, platform, or internal protocols they use.
·        They reduce application interface costs.
·        Provide a universal mechanism for integrating business processes within an enterprise and, ultimately, among multiple organizations.

Loosely couple
Services are most often built in a way that is independent of the context in which they are used. This means that the service provider and the consumers are loosely coupled. At the middleware level, the concept of loose coupling requires that the “service-oriented” approach be independent of specific technologies or operating systems.

Service providers
Organizations that provide the service implementations, supply their service descriptions, and provide related technical and business support
Service clients
End-user organizations that use some service
Service aggregators

Organizations that consolidate multiple services into a new, single orchestrated service offering what is commonly known as a business process.

Monday, 10 October 2016

What are web services?



A Web service is a self-describing, self-contained software module available via a network,such as the Internet, which completes tasks, solves problems, or conducts transactions on behalf of a user or application. Web services constitute a distributed computer infrastructure  made up of many different interacting application modules trying to communicate over private or public networks (including the Internet and Web) to virtually form a single logical system.

A Web service can be: 
(i) a self-contained business task, such as a funds withdrawal or funds deposit service;
(ii) a full-fledged business process, such as the automated purchasing of office supplies; 
(iii) an application, such as a life insurance application or demand forecasts and stock replenishment; 
(iv) a service-enabled resource, such as access to a particular back-end database containing patient medical records.

Web services can vary in function from simple requests (e.g., credit checking and authorization, pricing enquiries, inventory status checking, or a weather report) to complete business applications that access and combine information from multiple sources, such as an insurance brokering system, an insurance liability computation, an automated travel planner, or a package tracking system.

Web services address the problems of rigid implementations of predefined relationships and isolated services scattered across the Internet. The long-term goal of Web services technology is to enable distributed applications that can be dynamically assembled according to changing business needs, and customized based on device (such as personal computers, workstations, laptops, WAP-enabled cellular phones, personal digital assistants), network (such as cable, UMTS, XDSL, Bluetooth, etc.) and user access while enabling wide utilization of any given piece of business logic wherever it is needed. Once a Web service is deployed, other applications and Web services can discover and invoke it.