In day-to-day life it is quite hard to remember all confidential data like Mail Id, Password, bank account number, Insurance policy number, PAN number, Driving License number, education certificate Numbers, Some highly value scan copy, some confidential photo, music and videos. Crypto Locker is a
highly secure web application to store all confidential data in single credential.
This document outlines a proposal to develop a highly secure web application and hardware system to store all confidential data, like IDs, passwords, bank accounts, insurance policies, certificates, and scanned documents, in a single set of credentials. The system would have two types of users - administrators and public users. It would provide lockers for mailing/passwords, bank accounts, videos, images, music, and be managed by administrators. Non-functional requirements include secure access, 24/7 availability, performance during peak times, and a flexible service-based architecture. Optional features could make the system difficult to hack and use advanced techniques like 3D passwords and SSL. The user interface priorities are a professional look and feel, AJAX usage, and
Authentication is the process of verifying a user's identity by requiring them to provide credentials like a password or certificate. Common authentication methods include centralized authentication services like RADIUS, TACACS+, and Kerberos which verify credentials on a network authentication server. Firewalls can integrate with these authentication servers to provide user authentication and authorization when accessing the network.
Authentication verifies a user's identity by validating credentials like a username and password. Authorization then determines what access and permissions an authenticated user has. Authentication methods can include something you know like passwords, something you have like tokens or smartcards, or something you are like biometrics. Common authentication practices for systems include setting password policies, locking accounts after failed logins, and disabling unused accounts. Proper authentication helps implement access controls and security.
The document discusses various authentication techniques, including:
- Password-based authentication using clear text passwords, message digests of passwords, and adding randomness with challenges.
- Authentication tokens, which generate one-time passwords based on a seed value stored in the token and authentication server database.
- Multifactor authentication using passwords, biometrics, and authentication tokens or smart cards.
- Certificate-based authentication using digital certificates issued in a public key infrastructure for verifying user identities.
Deepak Joshi is a result-oriented software engineer and manual tester with over 4 years of experience in testing software and web applications. He is seeking a middle level role as a software engineer or manual tester, preferably in the IT product sector. He has experience testing identity, access, and compliance management products and providing technical support on Microsoft and Unix/Linux platforms. His career achievements include resolving incidents and conducting various types of testing at CIMCON and IBM in India. He has a Master's degree in Information Security and Computer Forensics from the University of East London.
This document discusses mobile security and vulnerabilities. It begins with definitions of security concepts like assets, vulnerabilities, threats, and risks. It then covers why mobile security is important and provides an overview of common mobile security issues like malware, insecure data storage, data leakage, and insecure communication channels. Specific vulnerabilities discussed include SQL injection, cross-site scripting, insecure authentication, cryptographic weaknesses, and insecure permissions. The document emphasizes that mobile apps must not store sensitive data locally and must implement secure protocols like HTTPS. It also notes that mobile devices are susceptible to malware and reverse engineering attacks.
This document outlines a proposal to develop a highly secure web application and hardware system to store all confidential data, like IDs, passwords, bank accounts, insurance policies, certificates, and scanned documents, in a single set of credentials. The system would have two types of users - administrators and public users. It would provide lockers for mailing/passwords, bank accounts, videos, images, music, and be managed by administrators. Non-functional requirements include secure access, 24/7 availability, performance during peak times, and a flexible service-based architecture. Optional features could make the system difficult to hack and use advanced techniques like 3D passwords and SSL. The user interface priorities are a professional look and feel, AJAX usage, and
Authentication is the process of verifying a user's identity by requiring them to provide credentials like a password or certificate. Common authentication methods include centralized authentication services like RADIUS, TACACS+, and Kerberos which verify credentials on a network authentication server. Firewalls can integrate with these authentication servers to provide user authentication and authorization when accessing the network.
Authentication verifies a user's identity by validating credentials like a username and password. Authorization then determines what access and permissions an authenticated user has. Authentication methods can include something you know like passwords, something you have like tokens or smartcards, or something you are like biometrics. Common authentication practices for systems include setting password policies, locking accounts after failed logins, and disabling unused accounts. Proper authentication helps implement access controls and security.
The document discusses various authentication techniques, including:
- Password-based authentication using clear text passwords, message digests of passwords, and adding randomness with challenges.
- Authentication tokens, which generate one-time passwords based on a seed value stored in the token and authentication server database.
- Multifactor authentication using passwords, biometrics, and authentication tokens or smart cards.
- Certificate-based authentication using digital certificates issued in a public key infrastructure for verifying user identities.
Deepak Joshi is a result-oriented software engineer and manual tester with over 4 years of experience in testing software and web applications. He is seeking a middle level role as a software engineer or manual tester, preferably in the IT product sector. He has experience testing identity, access, and compliance management products and providing technical support on Microsoft and Unix/Linux platforms. His career achievements include resolving incidents and conducting various types of testing at CIMCON and IBM in India. He has a Master's degree in Information Security and Computer Forensics from the University of East London.
This document discusses mobile security and vulnerabilities. It begins with definitions of security concepts like assets, vulnerabilities, threats, and risks. It then covers why mobile security is important and provides an overview of common mobile security issues like malware, insecure data storage, data leakage, and insecure communication channels. Specific vulnerabilities discussed include SQL injection, cross-site scripting, insecure authentication, cryptographic weaknesses, and insecure permissions. The document emphasizes that mobile apps must not store sensitive data locally and must implement secure protocols like HTTPS. It also notes that mobile devices are susceptible to malware and reverse engineering attacks.
Toll application - .NET and Android - SRSArun prasath
The document provides a software requirements specification for a toll application. It includes sections on introduction, overall description, and specific requirements. The introduction describes the methodology, purpose, scope and overview of the toll application. The overall description covers the product perspective, functions, interfaces, users, constraints, architecture and use case model. The specific requirements section details use case reports, activity diagrams and sequence diagrams. The toll application is meant to enable automatic payment at toll gates by tracking a user's GPS location and deducting payment when they cross virtual toll fences.
DISCLAIMER: The views are entirely that of the author of the presentation and ESS does not associate itself with the content whatsoever. ESS cannot be held liable in anyway for any claims arising out of the presentation or any repercussions from partial/complete implementation of any of the ideas presented.
The document provides a software requirements specification for version 1.0 of a Learning Management System. It includes an introduction describing the purpose, scope, definitions, and references. It also provides overall descriptions of the product perspective, software and hardware interfaces, user characteristics, constraints, architecture, use case models, class diagrams, sequence diagrams, and database diagrams. It concludes with specific requirements including use case reports, activity diagrams, and supporting information.
Vijay Kadam has over 5 years of experience in Java/J2EE application development. He has worked on projects for clients like BNYM, CCC Information Services, and various telecommunication giants. His technical skills include Java, J2EE, Spring, Hibernate, Oracle, and he has experience with frameworks like Struts, EJB, and tools like Eclipse, Ant, and Maven. Currently he works as a Senior Software Engineer at Accenture on a new accounting portal project for Zurich Insurance.
The document discusses various topics related to deriving solutions for web applications, including object-oriented software engineering, modeling, measurement and estimation, design patterns, web applications, XML, software components, web services, and future trends. It covers modeling approaches like UML, metrics for estimation and quality evaluation, design patterns for common problems, standards for XML, components, and web services. It also discusses service-oriented architecture, SOAP, WSDL, UDDI, and packaging of reusable assets.
Framework adoption for java enterprise application developmentClarence Ho
Java enterprise framework description and comparison.
Experience sharing on a project done, include the architect design, challenges and lesson learn.
Some thoughts on choosing framework and how to cope with the rapid change of technology.
Design Decisions For Understanding Software ArchitectureTiffany Graham
This document discusses the "browser wars" between Netscape and Microsoft in the 1990s. Netscape initially dominated the browser market with its Netscape Navigator. However, Microsoft was able to gain majority market share by bundling its Internet Explorer browser with Windows. As a result, Netscape struggled and was eventually acquired by America Online. The summary examines the key events in the browser war between the two companies over browser market control in 3 sentences or less.
E learning resource Locator Project Report (J2EE)Chiranjeevi Adi
This document provides an overview of an e-learning resource locator project being developed by students at Shri Dharmasthala Manjunatheshwar College of Engineering &Technology. The proposed system will allow students and professors within the Computer Science department to access and share learning materials online. Students will be able to view and download notes, presentations, and other resources. Professors can upload materials and answer student questions on discussion forums. The system is designed to make educational resources more conveniently accessible for remote learning. It will be developed using technologies like Java, J2EE, DB2 database, and NetBeans IDE.
This document contains a profile summary and work experience details for Suresh Oruganti. It summarizes his 2.2 years of experience developing web applications using Java/J2EE technologies. It also lists his education qualifications and provides details of two projects he worked on, including the roles, technologies used, and his contributions to each project.
This document provides an overview of a syllabus on Service Oriented Architecture (SOA). It discusses key topics that will be covered, including SOA characteristics, principles of service orientation, web services, SOA analysis, design, platforms, standards, composition, and security. Prerequisites include basic knowledge of object orientation, web technologies, Java programming, and software paradigms. The content will also cover current trends, software paradigms, application architecture, web-based systems, and component-based systems.
Final sds of academic a webpage based android applicationpreeta sinha
This document provides the design details of an Android application called Academic for a university. It includes sections on architectural design, data structure design, user interface design, and testing. The architectural design section describes the overall software architecture and work breakdown for administrators, students, heads of department, and staff. It also includes entity relationship diagrams, context diagrams, and data flow diagrams. The document outlines the various data tables that will be needed. It describes that the user interface will include screens for login, home page, and other functions. It discusses that unit, integration, and acceptance testing will be used to test the application.
This document is a training report submitted by Sumit Jain to fulfill the requirements for a Bachelor of Technology degree in Computer Science and Engineering. It describes a training project completed at Lio Technologies under the guidance of Mr. Rahul Sharma. The report includes an introduction to the company, objectives of the project, system analysis, feasibility study, software requirements specification, system design, screenshots, testing, implementation, maintenance, security, and conclusions.
Laboratory Information Management SystemMike Taylor
Laboratory Information Management System for scientists. Collaboration tool for healthcare industry for equipment sharing with social networking features
This document contains the resume of M.Prabhakar Naidu summarizing his professional experience and qualifications. He has over 4 years of experience in software development with Java, J2EE, JSP, and frameworks like Struts and Spring. Some of his projects include developing modules for a medical records system and a customer acquisition system for a bank. He is proficient in technologies like Java, JSP, Servlets, Hibernate and databases like Oracle and MySQL.
Local Service Search Engine Management System LSSEMSYogeshIJTSRD
Local Services Search Engine Management System LSSEMS is a web based application which helps user to find serviceman in a local area such as maid, tuition teacher, plumber etc. LSSEMS contain data of serviceman maid, tuition teacher, plumber etc. . The main purpose of LSSEMS is to systematically record, store and update the serviceman records. Kaushik Mishra | Aditya Sharma | Mohak Gund "Local Service Search Engine Management System (LSSEMS)" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Special Issue | International Conference on Advances in Engineering, Science and Technology - 2021 , May 2021, URL: https://www.ijtsrd.com/papers/ijtsrd42462.pdf Paper URL : https://www.ijtsrd.com/engineering/computer-engineering/42462/local-service-search-engine-management-system-lssems/kaushik-mishra
The document provides an overview of the Android framework, which consists of the Linux kernel, Dalvik virtual machine, core libraries, and application framework. It also summarizes the key developer tools for Android including the SDK, Eclipse plugin, emulator, and debugger. Finally, it outlines some of the main terminology for developing Android apps such as activities, intents, manifest files, resources and layouts.
This document contains the resume of Ravindra Rajpoot. It summarizes his professional experience as a senior developer working with IQOR since 2016, and previously with companies such as HCL Technologies, eClinicalWorks India Pvt. Ltd., and nearGroup. It lists his technical skills including Java, J2EE, SQL, and various frameworks. It also provides details of some projects he worked on, such as Service Logistics and a patient document management system.
The document describes the architectural design of the National Online Examination System developed by CDAC Noida.
The system was designed to be robust, fault tolerant, secure, scalable and adaptive to conduct online examinations across India. It uses open source technologies like Flex, Spring, Hibernate and Terracotta.
The architecture has three main tiers - the presentation tier uses Flex to create a rich internet application, the business tier uses Spring for its advantages over EJB and to separate cross-cutting concerns through aspect orientation. The data tier uses Hibernate for object-relational mapping and data access. Terracotta provides clustering for high availability and performance.
Managing Microservices traffic using IstioArun prasath
This document summarizes managing microservices traffic using Istio. It discusses the challenges of managing microservices like traffic management, observability, and security. It then introduces Istio as an open platform that provides traffic management, policy enforcement, metrics, logs, traces, and security for microservices without requiring code changes. It describes Istio's architecture including Pilot and Mixer and how to install Istio on Kubernetes. Finally, it outlines some of Istio's key capabilities like traffic management, policy enforcement, and collecting metrics, logs, and traces.
Istio is an open platform to connect, manage, and secure microservices.
This is presented at Bangalore Docker meetup #35.
https://www.meetup.com/Docker-Bangalore/events/244197013/
More Related Content
Similar to Highly confidential security system - sole survivors - SRS
Toll application - .NET and Android - SRSArun prasath
The document provides a software requirements specification for a toll application. It includes sections on introduction, overall description, and specific requirements. The introduction describes the methodology, purpose, scope and overview of the toll application. The overall description covers the product perspective, functions, interfaces, users, constraints, architecture and use case model. The specific requirements section details use case reports, activity diagrams and sequence diagrams. The toll application is meant to enable automatic payment at toll gates by tracking a user's GPS location and deducting payment when they cross virtual toll fences.
DISCLAIMER: The views are entirely that of the author of the presentation and ESS does not associate itself with the content whatsoever. ESS cannot be held liable in anyway for any claims arising out of the presentation or any repercussions from partial/complete implementation of any of the ideas presented.
The document provides a software requirements specification for version 1.0 of a Learning Management System. It includes an introduction describing the purpose, scope, definitions, and references. It also provides overall descriptions of the product perspective, software and hardware interfaces, user characteristics, constraints, architecture, use case models, class diagrams, sequence diagrams, and database diagrams. It concludes with specific requirements including use case reports, activity diagrams, and supporting information.
Vijay Kadam has over 5 years of experience in Java/J2EE application development. He has worked on projects for clients like BNYM, CCC Information Services, and various telecommunication giants. His technical skills include Java, J2EE, Spring, Hibernate, Oracle, and he has experience with frameworks like Struts, EJB, and tools like Eclipse, Ant, and Maven. Currently he works as a Senior Software Engineer at Accenture on a new accounting portal project for Zurich Insurance.
The document discusses various topics related to deriving solutions for web applications, including object-oriented software engineering, modeling, measurement and estimation, design patterns, web applications, XML, software components, web services, and future trends. It covers modeling approaches like UML, metrics for estimation and quality evaluation, design patterns for common problems, standards for XML, components, and web services. It also discusses service-oriented architecture, SOAP, WSDL, UDDI, and packaging of reusable assets.
Framework adoption for java enterprise application developmentClarence Ho
Java enterprise framework description and comparison.
Experience sharing on a project done, include the architect design, challenges and lesson learn.
Some thoughts on choosing framework and how to cope with the rapid change of technology.
Design Decisions For Understanding Software ArchitectureTiffany Graham
This document discusses the "browser wars" between Netscape and Microsoft in the 1990s. Netscape initially dominated the browser market with its Netscape Navigator. However, Microsoft was able to gain majority market share by bundling its Internet Explorer browser with Windows. As a result, Netscape struggled and was eventually acquired by America Online. The summary examines the key events in the browser war between the two companies over browser market control in 3 sentences or less.
E learning resource Locator Project Report (J2EE)Chiranjeevi Adi
This document provides an overview of an e-learning resource locator project being developed by students at Shri Dharmasthala Manjunatheshwar College of Engineering &Technology. The proposed system will allow students and professors within the Computer Science department to access and share learning materials online. Students will be able to view and download notes, presentations, and other resources. Professors can upload materials and answer student questions on discussion forums. The system is designed to make educational resources more conveniently accessible for remote learning. It will be developed using technologies like Java, J2EE, DB2 database, and NetBeans IDE.
This document contains a profile summary and work experience details for Suresh Oruganti. It summarizes his 2.2 years of experience developing web applications using Java/J2EE technologies. It also lists his education qualifications and provides details of two projects he worked on, including the roles, technologies used, and his contributions to each project.
This document provides an overview of a syllabus on Service Oriented Architecture (SOA). It discusses key topics that will be covered, including SOA characteristics, principles of service orientation, web services, SOA analysis, design, platforms, standards, composition, and security. Prerequisites include basic knowledge of object orientation, web technologies, Java programming, and software paradigms. The content will also cover current trends, software paradigms, application architecture, web-based systems, and component-based systems.
Final sds of academic a webpage based android applicationpreeta sinha
This document provides the design details of an Android application called Academic for a university. It includes sections on architectural design, data structure design, user interface design, and testing. The architectural design section describes the overall software architecture and work breakdown for administrators, students, heads of department, and staff. It also includes entity relationship diagrams, context diagrams, and data flow diagrams. The document outlines the various data tables that will be needed. It describes that the user interface will include screens for login, home page, and other functions. It discusses that unit, integration, and acceptance testing will be used to test the application.
This document is a training report submitted by Sumit Jain to fulfill the requirements for a Bachelor of Technology degree in Computer Science and Engineering. It describes a training project completed at Lio Technologies under the guidance of Mr. Rahul Sharma. The report includes an introduction to the company, objectives of the project, system analysis, feasibility study, software requirements specification, system design, screenshots, testing, implementation, maintenance, security, and conclusions.
Laboratory Information Management SystemMike Taylor
Laboratory Information Management System for scientists. Collaboration tool for healthcare industry for equipment sharing with social networking features
This document contains the resume of M.Prabhakar Naidu summarizing his professional experience and qualifications. He has over 4 years of experience in software development with Java, J2EE, JSP, and frameworks like Struts and Spring. Some of his projects include developing modules for a medical records system and a customer acquisition system for a bank. He is proficient in technologies like Java, JSP, Servlets, Hibernate and databases like Oracle and MySQL.
Local Service Search Engine Management System LSSEMSYogeshIJTSRD
Local Services Search Engine Management System LSSEMS is a web based application which helps user to find serviceman in a local area such as maid, tuition teacher, plumber etc. LSSEMS contain data of serviceman maid, tuition teacher, plumber etc. . The main purpose of LSSEMS is to systematically record, store and update the serviceman records. Kaushik Mishra | Aditya Sharma | Mohak Gund "Local Service Search Engine Management System (LSSEMS)" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Special Issue | International Conference on Advances in Engineering, Science and Technology - 2021 , May 2021, URL: https://www.ijtsrd.com/papers/ijtsrd42462.pdf Paper URL : https://www.ijtsrd.com/engineering/computer-engineering/42462/local-service-search-engine-management-system-lssems/kaushik-mishra
The document provides an overview of the Android framework, which consists of the Linux kernel, Dalvik virtual machine, core libraries, and application framework. It also summarizes the key developer tools for Android including the SDK, Eclipse plugin, emulator, and debugger. Finally, it outlines some of the main terminology for developing Android apps such as activities, intents, manifest files, resources and layouts.
This document contains the resume of Ravindra Rajpoot. It summarizes his professional experience as a senior developer working with IQOR since 2016, and previously with companies such as HCL Technologies, eClinicalWorks India Pvt. Ltd., and nearGroup. It lists his technical skills including Java, J2EE, SQL, and various frameworks. It also provides details of some projects he worked on, such as Service Logistics and a patient document management system.
The document describes the architectural design of the National Online Examination System developed by CDAC Noida.
The system was designed to be robust, fault tolerant, secure, scalable and adaptive to conduct online examinations across India. It uses open source technologies like Flex, Spring, Hibernate and Terracotta.
The architecture has three main tiers - the presentation tier uses Flex to create a rich internet application, the business tier uses Spring for its advantages over EJB and to separate cross-cutting concerns through aspect orientation. The data tier uses Hibernate for object-relational mapping and data access. Terracotta provides clustering for high availability and performance.
Similar to Highly confidential security system - sole survivors - SRS (20)
Managing Microservices traffic using IstioArun prasath
This document summarizes managing microservices traffic using Istio. It discusses the challenges of managing microservices like traffic management, observability, and security. It then introduces Istio as an open platform that provides traffic management, policy enforcement, metrics, logs, traces, and security for microservices without requiring code changes. It describes Istio's architecture including Pilot and Mixer and how to install Istio on Kubernetes. Finally, it outlines some of Istio's key capabilities like traffic management, policy enforcement, and collecting metrics, logs, and traces.
Istio is an open platform to connect, manage, and secure microservices.
This is presented at Bangalore Docker meetup #35.
https://www.meetup.com/Docker-Bangalore/events/244197013/
Log analysis challenges include searching logs across multiple services and servers. The ELK stack provides a solution with Logstash to centralize log collection, Elasticsearch for storage and search, and Kibana for visualization. Logstash uses input, filter, and output plugins to collect, parse, and forward logs. Example configurations show using stdin and filters to parse OpenStack logs before outputting to Elasticsearch and Kibana for analysis and dashboards.
Heat is an OpenStack template-based orchestration service that allows users to describe infrastructure and applications in text files called Heat Orchestration Templates (HOT) and automate the deployment of multi-component, multi-tier applications across OpenStack and other platforms. Heat provides the ability to define infrastructure resources like servers, networks, routers, and security groups and specify relationships between resources. It comprises several Python applications that work together to provision and manage OpenStack resources through a REST API according to the templates.
Docker - Demo on PHP Application deployment Arun prasath
Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more.
In this demo, I will show how to build a Apache image from a Dockerfile and deploy a PHP application which is present in an external folder using custom configuration files.
HP CloudSystem Matrix is Infrastructure-as-a-Service (IaaS) for private and hybrid cloud environments, allowing users to provision infrastructure in minutes for physical and virtual. This offering includes a self-service infrastructure portal for quick auto-provisioning, along with built-in lifecycle management to optimize infrastructure, manage the resource pools, and help ensure uptime. Using included Cloud APIs, you can easily customize the operating environment to your specific requirements, enabling chargeback and billing integration, integration into approval processes, and other process automation tasks. Matrix is integrated by design with broad support of heterogeneous environments, and it offers cloud-bursting to a variety of public cloud providers including HP Cloud Services. The core elements of a CloudSystem Matrix solution are:
- HP BladeSystem c7000 enclosures (1 or more)
- HP Virtual Connect
- HP Matrix Operating Environment
- HP Implementation Service
ARCHITECTING TENANT BASED QOS IN MULTI-TENANT CLOUD PLATFORMSArun prasath
Achieving QOS in a multi-tenant cloud platforms is still a difficult task and many companies follow different approaches to solve this problem. Here in this document I tried architecting a simple solution for achieving different QOS for different tenants in a Multi-tenant cloud environment based on my experiments with containers , docker and cgroup on Openstack.
This document describes a toll application that allows automatic payment of tolls using a mobile phone. The application allows users to register identities online, install an Android app, and purchase credits. When the app detects the user crossing a toll fence via GPS, funds are automatically deducted from the user's account. The proposed system eliminates physical toll booths and allows borderless travel. The document outlines the existing toll collection system, proposed toll application modules and interfaces, workflow, and concludes with potential future enhancements.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Highly confidential security system - sole survivors - SRS
1. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
solesurvivors
Highly Confidential Security System
Software Requirements Specification
Version 1.0
Mentor
Mr.R.Jayaraj (Asst. Professor), Department of CSE
Members
Arun Prasath.S
-
090105107008
Jojy George
-
100405107005
Prabhu.E
-
100405107013
Vivek Andrew Sha -
090105107121
College - Hindusthan College of Engineering and Technology, Coimbatore – 641032
Department - Computer Science and Engineering
State - Tamil Nadu
Sole Survivors | Hindusthan College of Engineering and Technology
1
2. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
Revision History
Date
Version
Description
Author
20-12-2012
1.0
Initial Release
Sole Survivors
Sole Survivors | Hindusthan College of Engineering and Technology
2
3. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
Table of Contents
Description
Page No
1. Introduction
4-9
1.1 Methodology ………………………………………………………………………… 4
1.2 Purpose ….. ………………………………………………………………………….. 5
1.3 Scope ……. ………………………………………………………………………….. 5
1.4 Definitions, Acronyms and Abbreviations … ……………………………………….. 6
1.5 References ……….…………………………………………………………………. 7
1.6 Technologies to be used ….………………………………………………………….
7
1.7 Tools to be used …. …………………………………………………………………. 7
1.8 Overview …………………………………………………………………………….. 9
2. Overall Description
9 - 18
2.1 Product Perspective ……….………………………………………………………… 9
2.2 Product Functions……………………………………………………………………. 10
2.3 Software Interface …………………………………………………………………. 10
2.4 Hardware Interface …………………………………………………………………. 11
2.5 User Characteristics …………………………………………………………………. 12
2.6 Constraints ………………………………………………………………………….. 12
2.7 Assumptions and Dependencies……………………………………………………… 12
2.8 Architecture Design …………………………………………………………………. 13
2.9 Use Case Model Survey ……………………………………………………………... 14
2.10 Database Design………………………………………………………………….…. 15
2.11 ER diagram…………………………………………………………………………. 16
3. Specific Requirements
17 - 33
3.1 Use Case Reports ……………………………………………………………………. 17
3.2 Activity Diagrams …………………………………………………………………… 20
3.3 Sequence Diagrams …………………………………………………………………. 29
4. Supporting Information
34
4.1 Index…………………………………………………………………………………. 34
Sole Survivors | Hindusthan College of Engineering and Technology
3
4. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
1. Introduction
In day-to-day life it is quite hard to remember all confidential data like Mail Id, Password, bank
account number, Insurance policy number, PAN number, Driving License number, education certificate
Numbers, Some highly value scan copy, some confidential photo, music and videos. Crypto Locker is a
highly secure web application to store all confidential data in single credential.
1.1 Methodology
The Rational Unified Process brings together elements from all of the generic process models,
supports iteration and illustrates good practice in specification and design. The RUP is normally described
from three perspectives:
A dynamic perspective that shows the phases of the model over time
A static perspective that shows the process activities that are enacted
A practice perspective that suggests good practices to be used during the process
Sole Survivors | Hindusthan College of Engineering and Technology
4
5. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
Inception
The goal of the inception phase is to establish a business case for the system. Identifying all
external entities that will interact with the system and defining these interactions. This information is used
to assess the contribution of system to business.
Elaboration
The goals of the elaboration phase are to develop an understanding of the problem domain,
establish an architectural framework, develop project plan and identify key project risks.
Construction
This phase is concerned with system design, programming and testing. Parts of the system are
developed in parallel and integrated during this phase.
Transition
This is the final phase of RUP and is concerned with moving the system from the development
community to the user community and making it work in real environment.
1.2 Purpose
Crypto Locker is a web application developed for secure and easy access of data. Crypto Locker
is a useful and convenient application that spares you the trouble of remembering the passwords and
securing the files. This application helps people to store their passwords and various types of files like
photos, music and videos in a secure and efficient manner. The application which we develop here uses
state of the art encryption technology to secure files and access over anywhere in the world using the
internet.
1.3 Scope
There are two basic users – Administrator, User.
All users have their own profile in Crypto Locker.
Administrator has an ability to manage the registered user profiles and organize the files stored in
the server.
Administrator has the ability to provide the notification message to the logged users via webpage.
Public peoples are the users used this web application to protect their important details in single
credentials.
Citizens (users) can access their files through internet from anywhere in the world.
Sole Survivors | Hindusthan College of Engineering and Technology
5
6. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
1.4 Definitions, Acronyms and Abbreviations
AJAX - Asynchronous JavaScript and XML is about updating parts of a web page, without reloading the
whole page.
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.
WASCE - Websphere Application Server Community Edition is an application server that runs and
supports J2EE and web service applications.
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 Markup 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.
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.
HTTP - Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser
and a Web Server.
HTTPS - Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).
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.
WAS (Websphere Application Server) - It is an application server that runs business applications and
supports the J2EE and web services standards.
Sole Survivors | Hindusthan College of Engineering and Technology
6
7. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
SOA: Service-Oriented Architecture is a set of principles and methodologies for designing and
developing software in the form of interoperable services.
1.5 References
IBM TGMC Sample Synopsis.
Software Engineering Theory and Practice (2nd Edition) - Shari Lawrence Pfleeger
Database Management Systems - Navathe.
Object Oriented Modeling and Design with UML (2nd Edition) - Michael Blaha, James
Rambaugh.
Java Complete Reference (7th Edition) – Herbert Schildt.
Cryptography and Network Security – William Stallings
1.6 Technologies to be used
J2EE : Programming Platform for developing and running distributed Java
AJAX : Updating parts of a web page, without reloading the whole page.
SOA : Set of principles and methodologies for designing and developing software in the form
of interoperable services.
UML : Standard for writing software blueprints, and used to visualize, specify, construct and
document.
XML : XML 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.
Jasper: Jasper Reports is an open source Java reporting tool that can write to a variety of
targets, such as: screen, a printer, into PDF, HTML, Microsoft Excel, RTF, ODT, Commaseparated values or XML files.
1.7 Tools to be used
Rational Rose
Rational Rose is an object-oriented programming (OOP) and unified modeling language (UML)
tool to design enterprise-level software applications and components. It creates visual software
application models under object-oriented principles. Example application models include the creation of
actors, use cases, relationships, entities, etc. It uses classical UML concepts to graphically model software
applications. This facilitates documenting the environment, requirements and overall design.
Sole Survivors | Hindusthan College of Engineering and Technology
7
8. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
Eclipse
Eclipse is a multi-language software development environment comprising an integrated
development environment (IDE) and an extensible plug-in system.
WPS
WPS stands for Wi-Fi Protected Setup and was designed to simplify the process of configuring
security on wireless networks.
Rational Software Architect (RSA)
IBM Rational Software Architect, (RSA) 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.
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.
Websphere Application Server (WAS)
IBM Websphere Application Server (WAS), a software application server, is the flagship product
within IBM's Websphere brand. WAS is built using open standards such as Java EE, XML, and Web
Services.
Web server – WASCE
Websphere Application Server Community Edition (from now on WASCE) is a free, certified
Java EE 5 server 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.
DB2 (Database 2)
DB2 is a family of relational database products provides an open database environment that runs
on a wide variety of computing platforms. A DB2 database can grow from a small single-user application
to a large multi-user system.
Sole Survivors | Hindusthan College of Engineering and Technology
8
9. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
1.8 Overview
The SRS will include two sections, namely:
Overall Description
This section will describe major components of the system, interconnections, and external
interfaces.
Specific Requirements
This section will describe the functions of actors, their roles in the system and the constraints
faced by the system.
2. Overall Descriptions
2.1 Product Perspective
The Crypto Locker is available for use by the administrator and the user. The administrator and
users will use the webpage as a front end. The browser goes through an http server. Application server
manages the connection between the front end and backend, all types of information and data, that are
necessary for the users are stored in DB2.
Sole Survivors | Hindusthan College of Engineering and Technology
9
10. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
2.2 Product Functions
The Crypto Locker service provides the user interface (UI) to user and administrator for creating
their profiles.
This product has the ability to send the “Account verification link” to the user’s mail, while
creating their account.
This product has the ability to send “Password Reset link” to the user’s mail, if the user forgets
the password for accessing the account.
This product is able to detect the user’s browsers.
This product provides the users to create the locker facilities for Bank account information,
Music, Video and Image files.
This product allows the registered users to store their important details on a server in an encrypted
format and while downloading, it is automatically decrypted.
This product provides the facility for administrators to generate the reports on user’s logs in .PDF
and Microsoft Excel formats.
It ask the account’s current password from the user when they want their personal credentials
from our server as a report (PDF and Excel).
2.3 Software Interface
(All users require internet for communication)
Public People (users)
Web browser (any), operating system (any)
Administrator
Web browser (any), operating system (Windows)
Web Server
WASCE, Operating System (Windows)
Data Base Server
DB2, operating system (Windows)
Development End
RAD (J2EE, java, java bean, Servlet, HTML, XML, AJAX) operating system (Windows), Web Sphere
(Web Server)
Sole Survivors | Hindusthan College of Engineering and Technology
10
11. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
2.4 Hardware Interface
2.4.1 Minimum Requirements
Crypto Locker (Server)
Processor
Storage Space
RAM
Disk Space
Intel Pentium IV –
4 GB RAM
5 TB
1 GB RAM
1 GB
AMD Athlon (1.8 GHz)
DB2 9.72
Users (Public People)
Browser
Processor
RAM
Internet Explorer 7, Firefox 13 with
Intel Pentium IV – AMD
1 GB RAM
Flash Plug-ins
Athlon (1.8 GHz)
2.4.2 Recommended Requirements
Crypto Locker (Server)
Processor
Storage Space
RAM
Disk Space
Intel Core Family (Any)
8 GB RAM
10 TB
2 GB RAM
2 GB
– AMD Phenom
DB2 9.72
(2.2 GHz)
Users (Public People)
Browser
RAM
Intel Core Family (Any) –
Latest Versions of Browsers (any)
Processor
2 GB RAM
AMD Phenom
(2.2 GHz)
Sole Survivors | Hindusthan College of Engineering and Technology
11
12. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
2.5 User Characteristics
Both users and administrator on internet will be using HTTP protocol.
Users use the FTP protocol for uploading and downloading the files from or to the server.
Administrator configures the SMTP Server for sending the mail to the user.
2.6 Constraints
GUI is only in English.
Login and password is used for the identification of the user (public people) and administrator.
Limited to HTTP, SMTP and FTP protocol.
Centralized server is used.
2.7 Assumptions and Dependencies
Crypto Locker is a platform independent web application. It is assumed that the client or user
computer has latest browser with JavaScript enabled. In addition, Firefox and Internet Explorer need the
flash plug-ins to play the media files. For configuring the SMTP Server it needs the Linux operating
system with at least kernel version 2.6.30, if server is in windows then it may need Windows Server.
Sending the message (SMS) to the users mainly depends on the network operator.
Sole Survivors | Hindusthan College of Engineering and Technology
12
13. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
2.8 Architecture Design
Sole Survivors | Hindusthan College of Engineering and Technology
13
14. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
2.9 Use Case Model Survey
2.9 Use Case Model Survey
Users (Public People)
Users can upload their files in their own personal locker. The locker includes various subsets like
Music locker, Image locker, Video locker, Password locker and Bank Account Information locker. Users
can access their personal (uploaded) files through internet. Users can participate in forum discussions to
clarify their doubts and also able to view the notifications sent from the administrator.
Sole Survivors | Hindusthan College of Engineering and Technology
14
15. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
Administrator
Administrator has the ability to manage the registered user’s profile. Administrator can send the
notification to the logged user about any changes in the service and also clarify the user’s doubts and
questions about the service.
System
While users are trying to create their account, Crypto System validates the user’s details and post
the message (success or failure) to them. Server has the ability to send the “Password reset link” to the
user’s mail, if the user forgets the password to access their account. It automatically blocks the abuse
users. When users are uploading the file, the system encrypts it by using the algorithm, when the users are
downloading their file, the system decrypts it.
2.10 Database Design
Sole Survivors | Hindusthan College of Engineering and Technology
15
16. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
2.11 ER Diagram
Sole Survivors | Hindusthan College of Engineering and Technology
16
17. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3. Specific Requirements
3.1 Use Case Reports
3.1.1 Administrator
3.1.1 Use Case Report for Administrator
USECASE
Register
Username Verification
Sign In
Validate Password
Profiles
Update Profile
Manage user Profiles
Push Notification
Generate Reports
Manage FAQ
Sign out
DESCRIPTION
The administrator create their account for managing the service
It checks the provided name with already existing name during registration
The admin can sign in into account and manage the service
The server validates the password and lets the admin use the service
The admin can view their own profile
The admin can update their own profile in case of any changes
The admin can manage the field registered user’s profile
The admin can push/send the notification in case of any changes
The admin can able to generate the reports about the service
The admin may clarify the doubts from clients
Logged out from the server
Sole Survivors | Hindusthan College of Engineering and Technology
17
18. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.1.2 Public People
3.1.2 Use Case Report for Public People (Users)
USECASE
Register
Username Verification
Sign In
Validate Password
Profiles
Update Profile
FAQ
View Notifications
Download File
Generate Reports
Upload File
Encryption/Decryption
Lockers
Sign out
DESCRIPTION
Citizens can create their account for using the service
It checks the provided name with already existing name during registration
The user can sign in into account and use the service
The server validates the password and lets the user use the service
The user can view his profile
The user can update his current status about the case
The user can able to post and reply their answers in the forum like page
The user receive the notification message from the administrator
The user can download their personal data using the secret key
The user can generate report from remote location.
The user can upload their personal data into the server
All data can be securely transmitted and received using Encryption algorithm
It includes image, video, music, password and bank account details
Logged out from the service
Sole Survivors | Hindusthan College of Engineering and Technology
18
19. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.1.3 Crypto System
3.1.3 Use Case Report for Crypto System
USECASE
Encryption
Decryption
Block abuse user
Validate Registration
Send Mail
Send Password Token
DESCRIPTION
The system encrypts the files from the user’s disk when he/she want to upload
The system decrypts the files from the server when the user want to download
Sever automatically blocks the lazy and abuse users based on the rules
Server Validates the user details and registers it into the database
Server sends the verification link to the user for the confirmation
Server sends the password token in case the user forgets the password
Sole Survivors | Hindusthan College of Engineering and Technology
19
20. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2 Activity Diagrams
3.2.1 User Registration
The user is made to fill all the mandatory fields, each user must choose a unique user name. If the
user has filled a name that is already present in the database, then the user will be prompted to fill in a
different username. After this the user must enter the new password twice. When the user clicks the
submit button the database verifies all the mandatory fields are filled or not. When all the fields are filled
the verification mail is automatically send to user’s mail, after click the verification link the user is
registered, otherwise the user is made to fill the fields again.
3.2.1 User Registration Activity
Sole Survivors | Hindusthan College of Engineering and Technology
20
21. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.2 Validate Registration
The user enters the registration details. The system validates the details and if the details are
found invalid the system rejects it else the system sends the verification mail to the user. The user needs
to follow the verification link to complete his registration.
3.2.2 Validate Registration
Sole Survivors | Hindusthan College of Engineering and Technology
21
22. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.3 Login Activity
The user enters the login credentials. The System validates the login credentials. If the login
credentials are valid then the system detects the type of user. If user is a member then the system redirects
to the member’s home page. If the user is administrator then the system redirects to the administrator’s
home page.
3.2.3 Login Activity
Sole Survivors | Hindusthan College of Engineering and Technology
22
23. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.4 Password Reset
If the user forgets his password then he should click on the Forget password link. Then the system
prompts him to enter his Mail ID. The system validates the Mail ID. If the Mail ID is valid then the
system sends the password reset mail to that Mail ID. If the Mail ID is invalid then the system displays
the error message.
3.2.4 Password Reset Activity
Sole Survivors | Hindusthan College of Engineering and Technology
23
24. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.5 Public People
The public people (user) can login to the website using a supplied username and password. After
logging in the user can perform several tasks such as generate reports, access lockers, participate in FAQ
center, edit profiles and view the notifications sent from the administrator.
3.2.5 Public People (users) on Web
Sole Survivors | Hindusthan College of Engineering and Technology
24
25. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.6 FAQ Page
The administrator and the user participate in the FAQ (Discussion forum) for clarifying their
doubts. Both admin and citizen can view the posts and may reply to the post, or may be post the questions
from the remote location.
3.2.6 FAQ
Sole Survivors | Hindusthan College of Engineering and Technology
25
26. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.7 Access Lockers
A crypto Locker service is provided for the users, who need to store their confidential details in a
single password. To access the lockers first he/she need to enter their Crypto Locker credential to login.
After that he has the ability to open locker and manage that by uploading and downloading the files. He is
also able to generate the reports about their activity for a certain period in a .PDF format documented file.
3.2.7 User Access the Lockers
Sole Survivors | Hindusthan College of Engineering and Technology
26
27. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.8 Administrator
The administrator login into their account’s home page and manage the overall activity of the
application like user management, own profile management, frequently asked Questions i.e., Discussion
forum management, notifications management and finally generate the reports.
3.2.8 Administrator on Web
Sole Survivors | Hindusthan College of Engineering and Technology
27
28. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.2.9 Crypto System
The web application has the automatic controls itself. While registration the server system
validate the user details, if there is any issues then it automatically denies the registration process, and
during the upload, download process encryption and decryption process starts with the help of key
provided by the user. Also it blocks the abuse user to prevent the server from any misbehavior activities.
3.2.9 Server system’s Activity
Sole Survivors | Hindusthan College of Engineering and Technology
28
29. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.3 Sequence Diagrams
3.3.1 User Registration
Sole Survivors | Hindusthan College of Engineering and Technology
29
30. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.3.2 Login Sequence
Sole Survivors | Hindusthan College of Engineering and Technology
30
31. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.3.3 Password Reset
Sole Survivors | Hindusthan College of Engineering and Technology
31
32. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.3.4 Upload Files
Sole Survivors | Hindusthan College of Engineering and Technology
32
33. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
3.3.5 Download Files
Sole Survivors | Hindusthan College of Engineering and Technology
33
34. Highly Confidential Security System
Software Requirements Specification
Sole Survivors
Version 1.0
20-12-2012
4. Supporting Information
4.1 Index
A
I
S
Abbreviations - 6
Inception - 5
Scope - 5
Acronyms – 6
Interface – 10, 11
Sequence Diagrams –29
Activity Diagrams – 20
Introduction - 4
SOA - 7
Administrator – 10, 15
AJAX - 6, 7
Architecture Design - 13
J
J2EE – 6, 7
Software – 10
Specific Requirements -9, 17
JSP - 6
T
M
Technologies - 7
Methodology - 4
Tools – 7
Minimum Requirements - 11
Transition - 5
O
U
Assumptions - 12
C
Constraints – 12
Construction - 5
Crypto Locker - 9
Operating System- 10, 12
D
Overview – 9
Database Design – 15
Overall Descriptions - 9
Database platform – 6
UML – 6, 7
Use Case Model - 14
Use Case Reports – 17
P
User - 14
DB2 - 6, 8
Product Perspective – 9
User Characteristics - 12
Definitions - 6
Product Functions – 10
W
Dependencies - 12
Public People - 14
WASCE – 6, 8
Development Tool - 8
Purpose - 5
WAS – 6, 8
E
R
WPS – 8
Eclipse – 8
RAD - 6
Web Server – 10
Elaboration - 5
Rational Rose - 7
X
ER Diagram - 16
RSA – 8
XML – 6, 7
H
Recommended - 11
Hardware - 11
References - 7
Development End - 10
HTTP - 6
Sole Survivors | Hindusthan College of Engineering and Technology
34