This document outlines the key aspects of a proposed system called Share Snippets. It includes sections on introduction and purpose, existing and proposed systems, requirements analysis, architecture, design, and conclusions. The proposed system aims to create a community for users to share digital content such as books, software, songs and videos in one place. It analyzes functional and non-functional requirements, outlines the technical architecture using web services and Flex, and provides design diagrams including use case diagrams and class diagrams.

1. Table of contents
1. INTRODUCTION.................................................................................................................3
2. PURPOSE....................................................................................................................3
3. SCOPE........................................................................................................................3
4. EXISTING SYSTEM........................................................................................................3
5. PROPOSED SYSTEM......................................................................................................4
6. REQUIREMENT ANALYSIS..................................................................................................4
7. FUNCTIONAL REQUIREMENTS.......................................................................................4
8. NON FUNCTIONAL REQUIREMENTS...............................................................................5
9. COMPUTATIONAL RESOURCES......................................................................................6
10. LIFE CYCLE MODEL......................................................................................................6
11. ARCHITECTURE.................................................................................................................7
12. SOFTWARE ARCHITECTURE..........................................................................................7
13. TECHNICAL ARCHITECTURE.........................................................................................8
14. DESIGN............................................................................................................................9
15. OBJECTIVES................................................................................................................9
16. DESIGN CONSTRAINTS...............................................................................................9
17. DESIGN DIAGRAMS....................................................................................................9
18. USE CASE DIAGRAM 1........................................................................................10
19. USE CASE DIAGRAM 2........................................................................................10
20. CLASS DIAGRAM.................................................................................................11
21. SEQUENCE DIAGRAM...........................................................................................12
22. DATABASE SPECIFICATIONS......................................................................................13
23. DEFINITIONS, ACRONYMS, AND ABBREVIATIONS...............................................................13
24. REFERENCES...................................................................................................................14
25. CONCLUSION..................................................................................................................14

2. 1.INTRODUCTION
Share snippet system is a web site which allows users to share snippets like books,
Songs, video clips, photos, softwares etc. The main objective of this system is to give
support for sharing meta-data. We discuss the need for a user to control the degree of
meta-data sharing when searching and browsing a shared video database and we
propose a way of organizing meta-data to allow such functionality. This provides a
mechanism for customized data access to users through registering as legal users.
1.1PURPOSE
The purpose of Share Snippets system is for anyone who has anything they want to
share with others - like books, softwares, songs, videos, they want to share with people
or a hobby they want to share with others with the same interests. Share Snippets
system creates a community around your passions by making it easy to find others and
for others to find you. Since Share Snippets is based on your content, not just your
thoughts, you don’t have to update your folders every day.
1.2SCOPE
1.3EXISTING SYSTEM
The present system does not allow all the digital content to share at one place. It
does not display the uploaded digital content of the users. We cannot download
the digital content of the users. We cannot download the digital content of other
users and also there is no option for posting the comments to the snips.
The disadvantages of the existing system are
1. Accuracy of Information.
2. Who provides technical support?
3. Insurance of Security.
4. Computer hackers.

3. 5. Computer Viruses.
6. Lack of technology to support users.
1.4PROPOSED SYSTEM
The proposed system is to provide a secure and reliable system which fulfills the
requirements of an user.
The advantages of the proposed system are:
1. Share Snippets System creates a community around you and your content.
2. You have practically unlimited flexibility in choosing what you want to
share and with whom.
3. Share Snippets System is unique in several ways and it is the one place for
all the digital content.
4. Share Snippets System provides user friendliness that is it enables people
to share interests and hobbies and allows them to connect with each other.
1.5FUNCTIONAL REQUIREMENTS
 Creating a User Interface for demonstrating Network management system
Scenario.
 The process involves creating two applications for demonstrating admin, and
tower manager.
 Auto monitor mode and control through RIA based Monitoring and Control
Module (MCM).
1.6NON FUNCTIONAL REQUIREMENTS
 The project will be developed on .net framework and flex.
 Unit testing, System testing will be done for integrity check and reliability check.

4.  Once the project is developed it runs around the clock from any remote client
using internet.
Maintainability:
All the modules must be clearly separate to allow different user interfaces to be
developed in future. Through thoughtful and effective software engineering, all steps of
the software development process will be well documented to ensure maintainability of the
product throughout its life time. All development will be provided with good
documentation
Performance:
The response time, utilization and throughput behavior of the system. Care is taken so
as to ensure a system with comparatively high performance.
Usability:
The ease of use and training the end users of the system is usability. System should
have qualities like- learning ability, efficiency, affect, control. The main aim of the project is
to increase the scope of page designer to design a page and to reduce the rework of the
programmer.
Modifiability:
The ease with which a software system can accommodate changes to its software is
modifiability. Our project is easily adaptable for changes that is useful for the application to
withstand the needs of the users.
Portability:
The ability of the system to run under different computing environments. The
environment types can be either hardware or software, but is usually a combination of two.
Reusability:
The extent to which existing application can be reused in new application. Our
application can be reused a number of times without any technical difficulties.
Security:
The factors that protect the software from accidental or malicious access, use,
modification, destruction, or disclosure. Security can be ensured as the project involves
authenticating the users.
1.7COMPUTATIONAL RESOURCES
The resources needed for solving this problem is:
Hardware Requirements:

5. • Pentium IV Processor
• 80 GB HDD
• Internet Connectivity
• LAN Connectivity
Software Requirements:
• SQL Server
• Visual Studio 2010
• C# Programming language
• Web service
• Flex 4.0
1.8LIFE CYCLE MODEL
This project uses V Model.
The V-model is a software development process which can be presumed to be the
extension of the waterfall model. Instead of moving down in a linear way, the process
steps are bent upwards after the coding phase, to form the typical V shape. The V-
Model demonstrates the relationships between each phase of the development life cycle
and its associated phase of testing.
The V-model deploys a well-structured method in which each phase can be
implemented by the detailed documentation of the previous phase. Testing activities
like test designing start at the beginning of the project well before coding and therefore
saves a huge amount of the project time.

6. 2.ARCHITECTURE
2.1SOFTWARE ARCHITECTURE
Creating
Web Flex
Applicatio
service
n
2.2TECHNICAL ARCHITECTURE
3.DESIGN
3.1OBJECTIVES
Design is the first step in moving from problem domain to solution domain. Design is
essentially the bridge between requirements specification and the final solution.
The goal of design process is to produce a model or representation of a system can be
used later to build that system. The produced model is called the ‘Design of the System’. It
is a plan for a solution of the system.
The objective of design phase is to:
 Create User Interface
 Create Application

7.  Create and launch instance
3.2DESIGN CONSTRAINTS
 Security: The files in which the information regarding securities and portfolios
should be secured against malicious deformations.
 Fault Tolerance: Data should not become corrupted in case of system crash or
power failure.
3.3DESIGN DIAGRAMS
This project requires:
 Use case diagrams to organize and model the behavior of the system
 Class diagrams to represent the static design view of the system
 Sequence diagrams to show the time-ordering of the messages
3.4DATABASE SPECIFICATIONS
This project involves authentication and authorization of users. It requires a database for
Login and Registration of users and for storing details.
4.DEFINITIONS, ACRONYMS, AND ABBREVIATIONS
Term or Acronym Definition
NMS Network Management System
Definitions and Acronyms
Abbreviations:
 SRS: Software Requirement Specification

8. 5.REFERENCES
 The Unified Modeling Language Users guide
By Grady Booch
 Software Engineering, A practitioners approach
By Roger S Pressman
 Software Project Management
By Walker Royce
 The applicable IEEE standards as published in ‘IEEE standards collection, for the
preparation of SRS’.
 Backup policy, Naming Conventions as per Teleparadigm Conventions.
6.CONCLUSION
As a result, NMS’s root cause analysis is change aware; Network Configuration
Manager can detect changes made to the configuration to devices and alert appropriate
individuals. Admin realizes that tracking and ensuring accuracy of every configuration
essential to your network is an enormous task. Network Configuration Manager is an
intelligent, integrated application that automates management of critical device
configurations for increased operating efficiency and improved network performance
and availability.