INDIAN WILD LIFE

Software Requirement Specification

TALENTED CREATORS Lakireddy Balireddy College Of Engineering

Mylavaram-521230 Team Members
A. ALEKYA A. SREE LAKHSMI 08761A0502 07251A0562

Project Guide
K. Thirupathi Rao
Department Of Compuer Science and Engineering

Table of Contents
1. Introduction 1.1 Methodology 1.2 Purpose 1.3 Scope 1.4 Definitions, Acronyms and Abbreviations 1.5 Tools Used 1.6 References 1.7 Technologies to be used 1.8 Overview 2. Overall Description 2.1 Product Perspective 2.2 Software Interface 2.3 Hardware Interface 2.4 Communication Interface 2.5 Constraints 2.6 ER Diagram 2.7 Schema 2.8 Use-Case Model Survey 2.9 Architecture Design 3. Specific Requirements 3.1 Use-Case Reports 3.2 Activity Diagrams 3.3 Sequence Diagrams 16 19 22 11 11 12 12 13 13 14 14 15 3 5 6 6 8 9 9 10

1. Introduction
1.1 Methodology
Rational Unified Process RUP is based on a set of building blocks, or content elements, describing what is to be produced, the necessary skills required and the step-by-step explanation describing how specific development goals are to be achieved. The main building blocks, or content elements, are the following:

Roles (who) A Role defines a set of related skills, competencies and responsibilities. Work Products (what) A Work Product represents something resulting from a task, including all the documents and models produced while working through the process. Tasks (how) A Task describes a unit of work assigned to a Role that provides a meaningful result. Within each iteration, the tasks are categorized into nine disciplines: Six "engineering disciplines"

Business Modelling Requirements Analysis and Design Implementation Test

Deployment Three supporting disciplines Configuration and Change Management Project Management

Environment Four Project Life cycle Phases The RUP has determined a project life cycle consisting of four phases. These phases allow the process to be presented at a high level in a similar way to how a 'waterfall'-styled project might be presented, although in essence the key to the process lies in the iterations of development that lie within all of the phases. Also, each phase has one key objective and milestone at the end that denotes the objective being accomplished. The visualization of RUP phases and disciplines over time is referred to as the RUP hump chart. 1. Inception Phase 2. Elaboration Phase 3. Construction Phase 4. Transition Phase

Fig 1.1: Phases of RUP

1. Inception Phase The primary objective is to scope the system adequately as a basis for validating initial costing and budgets. In this phase the business case which includes business context, success factors (expected revenue, market recognition, etc.), and financial forecast is established. To complement the business case, a basic use case model, project plan, initial risk assessment and project description (the core project requirements, constraints and key features) are generated. After these are completed, the project is checked against the following criteria:

Stakeholder concurrence on scope definition and cost/schedule estimates. Requirements understanding as evidenced by the fidelity of the primary use cases. Credibility of the cost/schedule estimates, priorities, risks, and development process. Depth and breadth of any architectural prototype that was developed. Establishing a baseline by which to compare actual expenditures versus planned expenditures.

If the project does not pass this milestone, called the Lifecycle Objective Milestone, it either can be cancelled or repeated after being redesigned to better meet the criteria. 2. Elaboration Phase The primary objective is to mitigate the key risk items identified by analysis up to the end of this phase. The elaboration phase is where the project starts to take shape. In this phase the problem domain analysis is made and the architecture of the project gets its basic form. The outcome of the elaboration phase is:

A use-case model in which the use-cases and the actors have been identified and most of the usecase descriptions are developed. The use-case model should be 80% complete. A description of the software architecture in a software system development process.

An executable architecture that realizes architecturally significant use cases. Business case and risk list which are revised. A development plan for the overall project. Prototypes that demonstrably mitigate each identified technical risk. A preliminary user manual (optional)

This phase must pass the Lifecycle Architecture Milestone criteria answering the following questions:

Is the vision of the product stable? Is the architecture stable? Does the executable demonstration indicate that major risk elements are addressed and resolved? Is the construction phase plan sufficiently detailed and accurate? Do all stakeholders agree that the current vision can be achieved using current plan in the context of the current architecture? Is the actual vs. planned resource expenditure acceptable?

If the project cannot pass this milestone, there is still time for it to be cancelled or redesigned. However, after leaving this phase, the project transitions into a high-risk operation where changes are much more difficult and detrimental when made.The key domain analysis for the elaboration is the system architecture. 3. Construction Phase The primary objective is to build the software system. In this phase, the main focus is on the development of components and other features of the system. This is the phase when the bulk of the coding takes place. In larger projects, several construction iterations may be developed in an effort to divide the use cases into manageable segments that produce demonstrable prototypes. This phase produces the first external release of the software. Its conclusion is marked by the Initial Operational Capability Milestone. 4. Transition Phase The primary objective is to 'transit' the system from development into production, making it available to and understood by the end user. The activities of this phase include training the end users and maintainers and beta testing the system to validate it against the end users' expectations. The product is also checked against the quality level set in the Inception phase. If all objectives are met, the Product Release Milestone is reached and the development cycle is finished.

1.2 Purpose
INDIAN WILDLIFE is a web application where we get detailed information on various rare Indian animals along with coverage of all species of animals that roam in the woods of INDIA. It will incubate research and participation on subjects like animal communications, habitats, wildlife health issues, effects of global warming and various disasters.

1.3 Scope
There are four basic users- guest/anonymous, registered members(Users, GOs & NGOs),Admin

All users have their own profiles in IW. Secure registration & profile management facilities for registered members & all agencies. Apart from arousing the alertness, it will posses detailed information on various rare Indian animals along with coverage of all species of animals that roam in the woods of INDIA. Registered users can post the problems existing in the reviewers panel which is responsible for solving various queries of website users. This provides an opportunity for users to participate in wildlife blogs, forums, internships, etc., and form groups to organize local meetings, wildlife forums, and wildlife camps. It will incubate research and participation on subjects like animal communications, habitats, wildlife health issues, effects of global warming and various disasters. With this, it will act as a platform for wildlife conservationists and ecologists to share their knowledge and recent trends in this field.

1.4 Definitions, Acronyms and Abbreviations

IWL Indian Wild Life. Its a web application that provides online information about Indian wildlife for people. Admin
Administrator has the authority to add/delete users, grant permission to access magazines in the application.

WASCE
Web Sphere Application Server Community Edition is an application server that runs and supports J2EE and web service applications.

 DB2
Database_2 is a database management system that provides a flexible and efficient database platform to maintain records of students, teachers, admin and dm.

JSP
Java Server Pages is used to create dynamic web content.

J2EE
Java 2 Enterprise Edition is a programming platform which is a part of java platform for developing and running distributed java.

UML
Unified Modeling Language is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct and document

XML
Extensible Mark up Language is a text based format that let developers describe, deliver and exchange structured data between a range of applications to client for display and manipulation.

HTTP
Hypertext Transfer Protocol is a service protocol.

RAD Rational Application Developer is a development tool that helps to design web pages and also helps to design the diagrams like ER, Database schema diagrams and to generate DDL.

1.5 Tools Used

Web server WASCE
Web Sphere Application Server Community Edition (from now on WASCE) is a free, certified JavaEE5server for building and managing Java applications. It is IBM's supported distribution of Apache Geronimo that uses Tomcat for servlet container and Axis 2 for web services. Over 15 WASCE developers are committers in the Apache Geronimo project.

Development tool RAD

IBM Rational Application Developer for Web Sphere Software (RAD) is an Integrated Development Environment (IDE), made by IBM's Rational Software division, for visually designing, constructing, testing, and deploying Web services, portals, and Java (J2EE) applications.

Database platform DB2

DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications and supports the J2EE and web services standards.

Design tool Rational Software Modeller

IBM Rational Software Modeller, (RSM) made by IBM's Rational Software division, is a Unified Modeling Language UML 2.0-based visual modelling and design tool. Rational Software Modeler is built on the Eclipse open-source software framework and includes capabilities focused on visual modeling and model-driven development (MDD) with the UML for creating resilient, thought-out applications and web services.

Linux Operating System

Linux is a multi-user operating system allows multiple users to do work at time. Linux is best OS for managing and monitoring these kinds of applications very easily. Rational Software Architect made by IBM's Rational Software division, is a comprehensive modeling and development environment that uses the Unified Modeling Language (UML) for designing architecture for C++ and Java 2 Enterprise Edition (J2EE) applications and web services. Rational Software Architect is built on the Eclipse open-source framework and includes capabilities focused on architectural code analysis, C++, and model-driven development (MDD) with the UML for creating resilient applications and web services.
IBM Tivoli Directory Server

Formerly known as IBM Directory Server, is an IBM implementation of the Light weight Directory Access Protocol, and is part of the IBM Tivoli Identity & Access Management portfolio. IBM Tivoli Directory Server is a powerful, security-rich and standards-compliant enterprise directory for corporate intranets and the Internet. Directory Server is built to serve as the identity data foundation for rapid development and deployment of Web applications and security and identity management initiatives by including strong management, replication and security features. Several authentication methods are available with IBM Tivoli Directory Server, beyond basic usernames and passwords. ITDS supports digital certificate-based authentication, the Simple (SASL), ChallengeResponse Authentication Mechanism MD5 (CRAM-MD5), and Kerberos authentication. IBM Tivoli Directory Server is a powerful LDAP infrastructure that provides a foundation for deploying comprehensive identity management applications and advanced software architectures.

1.6 References

Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh. Software Engineering, Seventh Edition, Ian Sommerville. IBM Red Books. IBM TGMC Sample Synopsis. IBM www.ibm.in/developer works. Java - www.sun.com Wikipedia - www.wikipedia.com Database Management Systems Navathe, Korth. Complete Reference - J2EE - Keogh.

1.7 Technologies to be used

DB2: Relational Database Management System. RAD: Rational Application Developer. WASCE: Web sphere Application Server Community Edition. Rational Software Modeler.

1.8 Overview
Existing system: This type of system doesnt exist. Proposed system: 1. It allows users to post articles. 2. Search no .of articles 3. View and download articles 4. Rating will be there for every article, so that one can really go after that. On the whole it is an amusing website for promoting awareness and conservation of indias wild life. Apart from arousing the alertness it will posses detailed information on various rare Indian animals along with coverage of all species of animals that roam in the woods of INDIA. With this, it will act as a platform for wildlife conservationists and ecologists to share their knowledge and recent trends in this field. It will incubate research and participation on subjects like animal communications, habitats, wildlife health issues, effects of global warming and various disasters.

Our plan: 1. 2. 3. 4. 5. 6. 7. Creating users for students with Registration no. and also for staff. Post news-letters. View news-letters. Search for articles. Provide career opportunities in this field. Comment on articles (opinions). Upload/download pictures, videos.

2. Overall Description
2.1 Product Perspective

Fig 2.1: Product Perspective

2.2 Software Interface Client on Internet

Web Browser, Operating System (any)

Client on Intranet
Web Browser, Operating System (any)

Web Server
WASCE, Operating System (any)

Data Base Server

DB2, Operating System (any)

Development End
RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows), Web Sphere (Web Server)

2.3 Hardware Interface

Minimum Requirements: Client Side Processor Internet Explorer - 6 Intel Pentium III or AMD 800 MHz Server Side Processor RAD DB2 - 9.5 Intel Pentium III or AMD 800 MHz RAM 1 GB Disk Space 3.5 GB 500 MB 256 MB (Excluding Data Size) RAM 128 MB Disk Space 100 MB

Recommended Requirements: Client Side Processor Internet Explorer - 6 All Intel or AMD - 1 GHZ Server Side Processor RAD All Intel or AMD - 2 GHZ 512 MB RAM 2 GB Disk Space 3.5 GB 500 MB (Excluding Data Size) RAM 256 MB Disk Space 100 MB

DB2 - 9.5

2.4 Communication Interface

Client (students) on Internet will be using HTTP/HTTPS protocol. Client (staff) on Internet will be using HTTP/HTTPS protocol.

2.5 Constraints
GUI is only in English. Login and password is used for the identification of users. Only registered members will be authorized to use the services. Limited to HTTP/HTTPS.

2.6. ER DIAGRAM

2.7 SCHEMA:

2.8 Use Case Model Survey

Actors:
Registered User: Student/faculty is considered to be user .He/She will be available with a platform which enables them to share their technical knowledge in the form of articles by submitting them to moderator .In addition the users can view others articles and comment, rate them. Registered User is given with user id and password. Guest/Anonymous: Guest is an anonymous user who is interested in technical stuff and he can view the articles and rate them .But an anonymous user doesnt have the privilege of submitting the articles .A guest cannot log in to the website.

G.O & N.G.O: They provide career opportunities and funds to this field.
Admin: Administrator maintains all the registered users and can add new users. He has the right of deleting a user.

2.9 ARCHITECTURAL DIAGRAM

3. SPECIFIC REQUIREMENTS 3.1 USE CASE DIAGRAMS USECASES OF REGISTERED USER:

Use case Login View profile Search Article Update profile Submit Article Comment Article Read Article Report abusive comments Download Article Rate Article Logout

Description Registered user can login to avail the services. Every registered user has his/her profile having personal details. An user can search for articles by using a keyword. Registered user has an option of editing his personal details. Registered user can submit their articles for publishing. Registered user can comment on a article and can put forward their views. User can read an article. User can report to moderator about on a comment which is abusive. User can download articles. Registered Article can rate the articles. Registered user can end his/her session by logging out.

USECASES OF ADMIN:

Use case Login View profile Search Article Update profile Submit Article Comment Article Read Article Delete abusive comments Download Article Rate Article Categorize articles

Description Admin can log in. Admin has his/her own profile having personal details. Admin can search for articles by using a keyword. Admin has an option of editing his personal details. Admin can submit their articles for publishing. Admin can comment on an article and can put forward their views. Admin can read an article. Admin can directly remove an abusive comment Admin can download articles. Admin can rate the articles. Admin can categorize articles based on the topic.

Reject Article Add moderator Post word of the day Post Article Logout

Admin has the privilege of rejecting Article. Admin can add moderator. Admin can post word of the day. Admin can post article directly. Admin can end his/her session by logging out.

Delete Comments Admin can delete comments which are reported abusive by the others.

USECASES OF GUEST:

Use case Search Article Comment Article Read Article Download Article Rate Article Register

Description Guest can search for articles by using a keyword. Guest can comment on a article and can put forward their views. Guest can read an article. Guest can download articles. Registered Article can rate the articles. Guest can register, if he/she is either student or faculty.

3.2 ACTIVITY DIAGRAMS FOR SUBMITTING ARTICLE:

USER ACTIVITIES:

Question:

LOGIN:

ACCEPT OR REJECT ARTICLE:

REGISTRATION:

3.3 SEQUENCE DIAGRAMS Anonymous user:

Registration:

Request:

We convey a special thanks to our department and to our college. We also convey a special thanks to all these softwares and websites, they have been helping a lot in doing the project.

Special Thanks