The document is a software requirements specification (SRS) for the Aloha social network. It describes the purpose, scope, definitions, intended audience, and overview of the document. It then provides an overall description of the product including its perspective, functions, operating environment, user characteristics, constraints, assumptions, and apportioning of requirements. The document outlines specific requirements including external interfaces, functional requirements grouped into user registration/profile, friends/suggestions, posts/shares, and chat. It also includes use cases, non-functional requirements, and a requirement traceability matrix. The document describes the change control mechanism for documenting, assessing, designing/testing, and final assessment of changes.
The document describes a case study for developing an online notice board system. It includes requirements gathering activities like preparing a questionnaire and defining functional and non-functional requirements. It also includes analysis models like use case diagram, class diagram, state chart diagram, sequence diagram, activity diagram, component diagram, and deployment diagram. Decision tables are created to model rules for different actions based on notice and result conditions for students and administrators. The case study follows a prototyping process model to validate requirements and identify errors early through user feedback.
The document describes a prisoner management system created using Java. It includes UML diagrams like use case, class, activity, and sequence diagrams that were used to design the database and system. The system allows a warden to add, delete, search for, update, and display prisoner records. It also provides prisoner functions like adding, deleting, finding, and releasing prisoners. The source code for the classes and database connection is provided along with sample outputs.
This document is the final year project report for a student who developed an attendance and access system. It includes sections on acknowledging contributors, describing the project objectives and scope, discussing the software and hardware used including LABView, a fingerprint reader, camera and card scanner. It also covers setting up a database in Microsoft Access to store student and attendance data. The system reads student cards and captures their photo and fingerprint, updates the database with time in/out and can generate web reports.
Ignou MCA 4th semester mini project report. College admission system. This project is based on real working system of University seat allocation to affiliate colleges. College admission system provide seat allocation process for various UG PG programs for every academic session.
The document describes the requirements for an online movie ticket booking system. It includes sections for the software requirements specification, user cases, interface requirements, and architectural design. The system allows customers to browse movie listings, select seats, purchase tickets, and receive confirmations. Administrators can manage movies, customer accounts, and bookings. Diagrams show the user case, activity flow, and high-level architecture. The goal is to provide an automated way for customers to book tickets in advance through a website.
SRS for student database management systemSuman Saurabh
This document is a software requirements specification for a student management portal being developed for LNMIIT. It outlines the purpose, scope, functions, users and operating environment of the system. The key functions are to maintain student records and grades, allow students to view their information, and give medical officers and coaches access to relevant health and sports data of students. It will be a web-based system built using Java, PHP and MySQL that can be accessed by around 20 staff, 1 administrator and 150 students concurrently.
Sana Khan is seeking a professionally satisfying and challenging career where her knowledge in computer hardware, networking, and systems administration can be utilized. She has over two years of experience planning, implementing, administering, and troubleshooting multiple operating systems. As a Network Administrator, her responsibilities included administrating servers, managing user accounts, installing and maintaining network components, monitoring systems, and troubleshooting various issues. She has technical skills in Windows, networking, hardware, and certifications in networking and fiber optics.
The document describes a case study for developing an online notice board system. It includes requirements gathering activities like preparing a questionnaire and defining functional and non-functional requirements. It also includes analysis models like use case diagram, class diagram, state chart diagram, sequence diagram, activity diagram, component diagram, and deployment diagram. Decision tables are created to model rules for different actions based on notice and result conditions for students and administrators. The case study follows a prototyping process model to validate requirements and identify errors early through user feedback.
The document describes a prisoner management system created using Java. It includes UML diagrams like use case, class, activity, and sequence diagrams that were used to design the database and system. The system allows a warden to add, delete, search for, update, and display prisoner records. It also provides prisoner functions like adding, deleting, finding, and releasing prisoners. The source code for the classes and database connection is provided along with sample outputs.
This document is the final year project report for a student who developed an attendance and access system. It includes sections on acknowledging contributors, describing the project objectives and scope, discussing the software and hardware used including LABView, a fingerprint reader, camera and card scanner. It also covers setting up a database in Microsoft Access to store student and attendance data. The system reads student cards and captures their photo and fingerprint, updates the database with time in/out and can generate web reports.
Ignou MCA 4th semester mini project report. College admission system. This project is based on real working system of University seat allocation to affiliate colleges. College admission system provide seat allocation process for various UG PG programs for every academic session.
The document describes the requirements for an online movie ticket booking system. It includes sections for the software requirements specification, user cases, interface requirements, and architectural design. The system allows customers to browse movie listings, select seats, purchase tickets, and receive confirmations. Administrators can manage movies, customer accounts, and bookings. Diagrams show the user case, activity flow, and high-level architecture. The goal is to provide an automated way for customers to book tickets in advance through a website.
SRS for student database management systemSuman Saurabh
This document is a software requirements specification for a student management portal being developed for LNMIIT. It outlines the purpose, scope, functions, users and operating environment of the system. The key functions are to maintain student records and grades, allow students to view their information, and give medical officers and coaches access to relevant health and sports data of students. It will be a web-based system built using Java, PHP and MySQL that can be accessed by around 20 staff, 1 administrator and 150 students concurrently.
Sana Khan is seeking a professionally satisfying and challenging career where her knowledge in computer hardware, networking, and systems administration can be utilized. She has over two years of experience planning, implementing, administering, and troubleshooting multiple operating systems. As a Network Administrator, her responsibilities included administrating servers, managing user accounts, installing and maintaining network components, monitoring systems, and troubleshooting various issues. She has technical skills in Windows, networking, hardware, and certifications in networking and fiber optics.
This project report describes a Software Project Management Tool. The tool aims to help organizations efficiently manage multiple projects by tracking activities, schedules, resources and time spent. It allows clients to check project status. The Business Development Officer can add new projects and view/update details. Developers can fill timesheets tracking time spent. The HR manager provides resources to projects. The Project Manager plans tasks and assigns them to developers, and checks timesheets. The tool is intended to provide transparency into resource allocation and progress across all levels of a project.
The document describes an Academic Management System (AMS) project presented by students. The AMS allows a college to maintain student, staff, fees, and exam information electronically. It aims to simplify information management and allow quick access to records. The project involved designing the system using tools like Rational Rose, writing code in Java/JSP, and testing the software. Key modules include administration, student, faculty, and department functions. The system uses a database, login authentication, and allows generating reports. The document outlines objectives, outcomes, schedule, architecture, and design diagrams for the AMS.
Android Based Application Project Report. Abu Kaisar
This document describes a project report for a counseling hour mobile application created for the Wireless Programming course. The application allows students to book counseling sessions with teachers and teachers to update their profiles and counseling times. It includes chapters on introduction and objectives, background studies, system design diagrams, software and hardware requirements, and proposed features for students and teachers. The goal is to make it easier for students and teachers to communicate about counseling sessions through a mobile app rather than traditional methods.
This document outlines the requirements for a mobile application to facilitate communication between students, teachers, and administrators at Wireless Lan communicator. The app will allow users to call, video call, message, share documents and assignments. Key features include login/registration, profile management, contacts, file sharing, and an administrator interface to manage student/teacher data.
This document provides a summary of a student's project report on a Student Result Management System. The report includes an introduction, objectives of the project, technologies used such as PHP, MySQL, and JavaScript. It also covers system requirements, design aspects like use case and class diagrams, database structure, and screenshots of the input/output screens. The overall goal of the project is to develop a web-based application to manage student results and simplify the result preparation process.
1. The document provides information on an e-ticket booked from Sattenapalle to Tirupati on train 12734 NARAYANADRI EXP. Key details include passenger name, PNR number, travel dates, ticket class and fare.
2. It lists valid IDs required for travel and provides various terms and conditions regarding e-ticket booking, cancellation and refund on IRCTC.
3. It ends by providing information on COVID-19 vaccination and urging people to register online as only registered beneficiaries will be vaccinated.
The document provides details for a project proposal approval form for an MCA student named Hitesh Jangid. The form includes the student's enrollment number, study center, regional center code, contact details, project title ("Project Management System"), software to be used (Xampp, Sublime Text), confirmation of previous projects completed, and spaces for the guide's details and signature. It also has sections for office use only including approval/rejection, suggestions for reformulating the project, and the project proposal number.
The document describes a final year project to develop a mobile and web application called SpringsVision Events for planning and managing social events. A team of 4 students - Syed Absar Karim, Umair Ahmed, Shafaq Yameen, and Zaid Hussain - presented their project to create an online platform for scheduling events, adding social networking features, and mobile support to the supervisor Mr. Nadeem Mahmood. The project aims to provide a useful tool for personal event management and sharing on social media.
This document summarizes a project report for a payroll system developed by a group of students for their Software Engineering course. The objectives of the project were to apply extreme programming techniques learned in class by developing a payroll system that calculates employee pay and deductions. Key deliverables included accepting employee hours and pay rates, calculating net pay, and generating payslips and payroll records. The system was developed in Visual Basic based on user stories gathered from clients. Testing with clients provided feedback that was used to improve the system, such as adding different pay rates for employees and calculating year-to-date totals.
Robert Smith has over 15 years of experience in IT with expertise in Windows operating systems, networking, virtualization, and project management. He has held roles such as systems administrator, infrastructure specialist, and technical support analyst. His skills include deployment, administration and support of Windows servers, desktops, applications and networking infrastructure.
Integer Optimisation for Dream 11 Cricket Team Selectionsaurav singla
A retrospective approach to team selection using the real-world data collected from Player performances in the last 10 matches, to propose a Dream 11 Fantasy team for the upcoming cricket match.
This document is a project report that proposes developing a web application to securely store files on a cloud server using hybrid cryptography. It aims to address data security and privacy issues for cloud storage. The application would use a hybrid cryptography technique combining symmetric and asymmetric encryption to encrypt files before uploading them to the cloud. Only authorized users with decryption keys would be able to access and download encrypted files from the cloud server. The report outlines the problem statement, objectives, methodology, design, and implementation of the proposed application to provide secure file storage on the cloud.
Online Examination System For Android AAD Report Akshay KalapgarAkshayKalapgar
Online Examination System is used for conducting online objective test. The test will be customized such that system will have automated checking of answers based on the user interaction. This project helps the faculties to create their own test based on the subject. This also helps the instruction to perform online quiz, test paper such that the academic performance of the students can be increased and can take the feedback from both students and parents.
This Android application (stand alone too), where one can set the question for different technology i.e. Android, Java etc and one can register them self for test as a student, he can choose the choice of technology (Android, Java), and simultaneously he can get the exam result. After submit or End of the Test the form will be submitted and evaluated. Scores will be given to the user on his request. The question and answers can be text or pictures or audios or even videos. Initial plan is to develop a objective type text based question and answer. The main programming language is android/Java database as a sqlite3.
The document is a project report submitted by Meet Patel for their internship at Codefuel Technology Pvt Ltd. It details the development of a "Meal Planner" Android application. The report includes an introduction to Codefuel Technology, the tasks performed during the internship, an overview of the Meal Planner project including objectives, technologies used, system flow, and screenshots of the application interface. It concludes with limitations and references.
This project is aimed at developing an online movie ticket booking system website for customers.Online movie ticket booking system is a project developed for booking movie ticket online.This project saves lots of time and reduces the work of the customer.In online movie ticket booking system booking the movie ticket can be done from anywhere and at any time(24*7).some features provided to the users are new registration,login in,see movies by category,compare ticket price and timing,Customer can book ticket online without registration but if he/she registers then he/she will get different types of special offers,e-newsletters,movie updates and lots more The user can also cancel or update their order
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introduction, purpose, project summary, requirements definition, considerations, and a document change log. The project summary section provides an executive overview with objectives, scope, references, and outstanding issues. The requirements definition section outlines goals, usability requirements, security requirements, business questions, data requirements, and design constraints. The purpose is to help define and document the project scope and requirements.
This document is a project report for developing an online assessment tool for Sainsbury's Supermarket Ltd. It outlines the inception phase of the project, which included proposing the topic, researching online assessment and learning management systems, and planning initial tasks. The objectives are to create a convenient way for employees to complete required assessments online after training and for managers to manage user content. The report discusses technologies for online applications and reviews similar existing tools. It presents initial requirements gathering, use case modeling, risk assessment, and outlines plans for the elaboration, construction, transition and implementation phases of the project using the RUP methodology.
This document discusses user interface design issues for mobile applications. It addresses small screen sizes, responsive vs adaptive design, limited multimedia, online vs offline viewing, portrait and landscape views, content layout challenges, and font selection. Guidelines from sources like Google and Don Norman are reviewed. Evaluation techniques like heuristic evaluation and usability basics are presented. Visual design concepts like color theory, fonts, layouts and graphics are covered. The document gives an overview of a sample university application and discusses implementation of the home, open day, and facilities screens. It concludes with a planned evaluation of the application.
This document provides a software requirements specification (SRS) for an office automation system. It describes the purpose of the system as automating processes in a college office such as managing student, employee, and transaction data. The SRS outlines functional requirements for modules including attendance, courses, fees, donations, exams, profiles, and reports. It also provides technical requirements for the system such as the needed software (VB.NET and SQL Server), hardware specifications, and user characteristics. Diagrams are included showing the login process and main navigation levels of the system.
The document provides details on planned quality assurance enhancements for work order management at Al-Borj, including:
- Adding a QA tab to the work order form for quality inspection notes and potentially reopening closed work orders.
- Creating a new QA Rating classification.
- Modifying portals and reports to support the QA process, including a new QA Specialist portal.
- Configuring notifications when work orders are closed to trigger QA inspections.
- Integrating the changes with their Maximo system while maintaining work order state changes.
The document outlines requirements for customizing the TRIRIGA system and its forms, processes, roles and security to implement the quality assurance process as
This document has been released originally in template format and is meant to be modified upon first use. <information> is a Cloud Service Provider (CSP) offering that has undergone either a Privacy Threshold Analysis (PTA) or Privacy Impact Assessment (PIA). This document includes a the PTA/PIA for <information>.
This project report describes a Software Project Management Tool. The tool aims to help organizations efficiently manage multiple projects by tracking activities, schedules, resources and time spent. It allows clients to check project status. The Business Development Officer can add new projects and view/update details. Developers can fill timesheets tracking time spent. The HR manager provides resources to projects. The Project Manager plans tasks and assigns them to developers, and checks timesheets. The tool is intended to provide transparency into resource allocation and progress across all levels of a project.
The document describes an Academic Management System (AMS) project presented by students. The AMS allows a college to maintain student, staff, fees, and exam information electronically. It aims to simplify information management and allow quick access to records. The project involved designing the system using tools like Rational Rose, writing code in Java/JSP, and testing the software. Key modules include administration, student, faculty, and department functions. The system uses a database, login authentication, and allows generating reports. The document outlines objectives, outcomes, schedule, architecture, and design diagrams for the AMS.
Android Based Application Project Report. Abu Kaisar
This document describes a project report for a counseling hour mobile application created for the Wireless Programming course. The application allows students to book counseling sessions with teachers and teachers to update their profiles and counseling times. It includes chapters on introduction and objectives, background studies, system design diagrams, software and hardware requirements, and proposed features for students and teachers. The goal is to make it easier for students and teachers to communicate about counseling sessions through a mobile app rather than traditional methods.
This document outlines the requirements for a mobile application to facilitate communication between students, teachers, and administrators at Wireless Lan communicator. The app will allow users to call, video call, message, share documents and assignments. Key features include login/registration, profile management, contacts, file sharing, and an administrator interface to manage student/teacher data.
This document provides a summary of a student's project report on a Student Result Management System. The report includes an introduction, objectives of the project, technologies used such as PHP, MySQL, and JavaScript. It also covers system requirements, design aspects like use case and class diagrams, database structure, and screenshots of the input/output screens. The overall goal of the project is to develop a web-based application to manage student results and simplify the result preparation process.
1. The document provides information on an e-ticket booked from Sattenapalle to Tirupati on train 12734 NARAYANADRI EXP. Key details include passenger name, PNR number, travel dates, ticket class and fare.
2. It lists valid IDs required for travel and provides various terms and conditions regarding e-ticket booking, cancellation and refund on IRCTC.
3. It ends by providing information on COVID-19 vaccination and urging people to register online as only registered beneficiaries will be vaccinated.
The document provides details for a project proposal approval form for an MCA student named Hitesh Jangid. The form includes the student's enrollment number, study center, regional center code, contact details, project title ("Project Management System"), software to be used (Xampp, Sublime Text), confirmation of previous projects completed, and spaces for the guide's details and signature. It also has sections for office use only including approval/rejection, suggestions for reformulating the project, and the project proposal number.
The document describes a final year project to develop a mobile and web application called SpringsVision Events for planning and managing social events. A team of 4 students - Syed Absar Karim, Umair Ahmed, Shafaq Yameen, and Zaid Hussain - presented their project to create an online platform for scheduling events, adding social networking features, and mobile support to the supervisor Mr. Nadeem Mahmood. The project aims to provide a useful tool for personal event management and sharing on social media.
This document summarizes a project report for a payroll system developed by a group of students for their Software Engineering course. The objectives of the project were to apply extreme programming techniques learned in class by developing a payroll system that calculates employee pay and deductions. Key deliverables included accepting employee hours and pay rates, calculating net pay, and generating payslips and payroll records. The system was developed in Visual Basic based on user stories gathered from clients. Testing with clients provided feedback that was used to improve the system, such as adding different pay rates for employees and calculating year-to-date totals.
Robert Smith has over 15 years of experience in IT with expertise in Windows operating systems, networking, virtualization, and project management. He has held roles such as systems administrator, infrastructure specialist, and technical support analyst. His skills include deployment, administration and support of Windows servers, desktops, applications and networking infrastructure.
Integer Optimisation for Dream 11 Cricket Team Selectionsaurav singla
A retrospective approach to team selection using the real-world data collected from Player performances in the last 10 matches, to propose a Dream 11 Fantasy team for the upcoming cricket match.
This document is a project report that proposes developing a web application to securely store files on a cloud server using hybrid cryptography. It aims to address data security and privacy issues for cloud storage. The application would use a hybrid cryptography technique combining symmetric and asymmetric encryption to encrypt files before uploading them to the cloud. Only authorized users with decryption keys would be able to access and download encrypted files from the cloud server. The report outlines the problem statement, objectives, methodology, design, and implementation of the proposed application to provide secure file storage on the cloud.
Online Examination System For Android AAD Report Akshay KalapgarAkshayKalapgar
Online Examination System is used for conducting online objective test. The test will be customized such that system will have automated checking of answers based on the user interaction. This project helps the faculties to create their own test based on the subject. This also helps the instruction to perform online quiz, test paper such that the academic performance of the students can be increased and can take the feedback from both students and parents.
This Android application (stand alone too), where one can set the question for different technology i.e. Android, Java etc and one can register them self for test as a student, he can choose the choice of technology (Android, Java), and simultaneously he can get the exam result. After submit or End of the Test the form will be submitted and evaluated. Scores will be given to the user on his request. The question and answers can be text or pictures or audios or even videos. Initial plan is to develop a objective type text based question and answer. The main programming language is android/Java database as a sqlite3.
The document is a project report submitted by Meet Patel for their internship at Codefuel Technology Pvt Ltd. It details the development of a "Meal Planner" Android application. The report includes an introduction to Codefuel Technology, the tasks performed during the internship, an overview of the Meal Planner project including objectives, technologies used, system flow, and screenshots of the application interface. It concludes with limitations and references.
This project is aimed at developing an online movie ticket booking system website for customers.Online movie ticket booking system is a project developed for booking movie ticket online.This project saves lots of time and reduces the work of the customer.In online movie ticket booking system booking the movie ticket can be done from anywhere and at any time(24*7).some features provided to the users are new registration,login in,see movies by category,compare ticket price and timing,Customer can book ticket online without registration but if he/she registers then he/she will get different types of special offers,e-newsletters,movie updates and lots more The user can also cancel or update their order
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introduction, purpose, project summary, requirements definition, considerations, and a document change log. The project summary section provides an executive overview with objectives, scope, references, and outstanding issues. The requirements definition section outlines goals, usability requirements, security requirements, business questions, data requirements, and design constraints. The purpose is to help define and document the project scope and requirements.
This document is a project report for developing an online assessment tool for Sainsbury's Supermarket Ltd. It outlines the inception phase of the project, which included proposing the topic, researching online assessment and learning management systems, and planning initial tasks. The objectives are to create a convenient way for employees to complete required assessments online after training and for managers to manage user content. The report discusses technologies for online applications and reviews similar existing tools. It presents initial requirements gathering, use case modeling, risk assessment, and outlines plans for the elaboration, construction, transition and implementation phases of the project using the RUP methodology.
This document discusses user interface design issues for mobile applications. It addresses small screen sizes, responsive vs adaptive design, limited multimedia, online vs offline viewing, portrait and landscape views, content layout challenges, and font selection. Guidelines from sources like Google and Don Norman are reviewed. Evaluation techniques like heuristic evaluation and usability basics are presented. Visual design concepts like color theory, fonts, layouts and graphics are covered. The document gives an overview of a sample university application and discusses implementation of the home, open day, and facilities screens. It concludes with a planned evaluation of the application.
This document provides a software requirements specification (SRS) for an office automation system. It describes the purpose of the system as automating processes in a college office such as managing student, employee, and transaction data. The SRS outlines functional requirements for modules including attendance, courses, fees, donations, exams, profiles, and reports. It also provides technical requirements for the system such as the needed software (VB.NET and SQL Server), hardware specifications, and user characteristics. Diagrams are included showing the login process and main navigation levels of the system.
The document provides details on planned quality assurance enhancements for work order management at Al-Borj, including:
- Adding a QA tab to the work order form for quality inspection notes and potentially reopening closed work orders.
- Creating a new QA Rating classification.
- Modifying portals and reports to support the QA process, including a new QA Specialist portal.
- Configuring notifications when work orders are closed to trigger QA inspections.
- Integrating the changes with their Maximo system while maintaining work order state changes.
The document outlines requirements for customizing the TRIRIGA system and its forms, processes, roles and security to implement the quality assurance process as
This document has been released originally in template format and is meant to be modified upon first use. <information> is a Cloud Service Provider (CSP) offering that has undergone either a Privacy Threshold Analysis (PTA) or Privacy Impact Assessment (PIA). This document includes a the PTA/PIA for <information>.
This document presents the requirements for a gym management software system called MindMuscle-Xtreme. It provides an overview of the purpose and scope, which is to design a user-friendly system to efficiently manage all aspects of running a gym. The document describes high-level requirements including user interfaces, database and system requirements. It also provides details on the proposed system design, including entity relationship diagrams, data flow diagrams and screenshots of example interfaces.
The document is the version 2.7 of the IT Handbook for the University System of Georgia (USG), updated in February 2018. It provides an overview and history of changes made to the handbook. The handbook establishes IT standards, best practices, and compliance requirements for USG organizations to follow related to governance, project management, security, privacy, facilities, and other IT functions. It is intended to help IT professionals and ensure practices align with laws, regulations, and Board of Regents policies.
This document provides a software requirements specification for an e-store project. It includes sections on introduction, overall description, specific requirements, and supporting information. The specific requirements section details functional requirements for the e-store such as selling configured products, providing product details and search, maintaining customer profiles, and enabling online purchases. It also covers usability, reliability, performance, security, and other requirements. The goal of the document is to comprehensively define the requirements for the e-store software system.
This document provides software requirement specifications for an iPortman Administration module. It includes sections on the overall description of the product, specific requirements, and appendices. The product will provide functionality for system administration, including default configurations, system initialization, user management, workflow configurations, and document configurations. It is meant to improve operations control and increase productivity for port management operations.
This document provides an overview of the design of a My Account application. It describes the single page application approach using AngularJS, which allows dynamic updates to parts of the page rather than reloading the whole page. It also describes the use of RESTful APIs and services to interface with backend systems like SAP. Key components like controllers, services, forms and databases are listed. The system architecture shows how the client interfaces with the Grails server, which communicates with SAP via SOAP.
Aloha Social Networking Portal - Design DocumentMilind Gokhale
The document provides an overview of the design for the Aloha social networking website. It describes the project perspective, tools used, architecture including application and database architecture, use cases, class diagram, sequence diagrams, user interface, deployment diagram, coding standards, error handling, data model, risks and mitigation plans. The architecture follows a three-tier structure with presentation, controller and data access layers. Key features include registration, account management, adding friends, scribbling posts, commenting, and chatting. The system will be developed using Spring MVC, MySQL database, and deployed on Apache Tomcat.
P6 Team Member – An Implementation Story (How to make Project Manager's life ...p6academy
Referenced: www.p6academy.com
Source: http://coll15.mapyourshow.com
Presentation will cover experience with early limitations and later improvements in implementation of Team Member. Focus of the presentation will be on ways that we used Team Member in contract and procurement management processes as well as on good and bad sides of Team Member. We will present modifications we've implemented to extend Team Member functionalities and to improve our Contract Management process. We’ll present where we are today with Team Member, difficulties we’ve encountered with different versions of Team Member and future plans with Team Member 8.4. We’ll go through key advantages of using Team Member as a simple tool to gather information about project progress and as collaborate tool on a project.
The document provides requirements for implementing a pilot virtualization desktop solution at a customer's data center location. It outlines pre-implementation requirements including setting up an organizational unit and user groups in Active Directory, configuring DHCP and DNS, and providing necessary network infrastructure such as IP address ranges. It also requests information on Active Directory configuration including domains, sites, trusts and functional levels. Customer resources are required to assist with tasks such as Active Directory integration and change control. Defining these requirements upfront is important for ensuring a successful pilot deployment.
This document provides requirements for the Virtual-EDU system being developed for NJIT. It outlines features such as instant messaging, audio/video streaming, customizable user profiles, virtual spaces for collaboration, online testing capabilities, and an improved user interface. The system is being designed to enable more effective communication between professors and students through a secure online platform. The document is intended to ensure both the development team and NJIT understand all agreed upon requirements to build Virtual-EDU.
The document is a software requirements specification (SRS) for a new online booking system for Cool Ski Resorts. It provides an overview of the project, outlines the system features and user requirements. Key aspects include: allowing customers to book rooms, equipment and classes online; managing inventory, payments and financial reports; and improving work efficiency for staff. The system is intended to digitize current paper-based processes and provide a better experience for customers.
Guidelines For The Issuance And Management Of EV Code Signing CertificateCodeSigningStore
The Guidelines for the Issuance and Management of Extended Validation Code Signing Certificates present criteria established by the CA/Browser Forum for use by certification authorities when issuing, maintaining, and revoking certain digital certificates for use in signing digital objects.
P6 Team Member allows procurement officers to easily update the status of procurement tasks and communicate with project managers. Procurement officers can check boxes when milestones are complete, update actual start dates of activities, and view and edit activity details. Project managers maintain oversight of procurement statuses through P6 Web to incorporate impacts into the project schedule. P6 Team Member provides a simple interface for non-scheduling users while still integrating procurement information into the master P6 project.
This document contains the bylaws of the Black Data Processing Associates (BDPA) Middle Tennessee chapter from June 2005. The bylaws define the organization's name, objective to share IT knowledge and expertise with minorities, and business areas. It outlines membership which includes full members and student members. The bylaws also describe the officers of the association including responsibilities, and the board of directors. It covers committees, nominations/elections, meetings, financial policies, amendments, and the BDPA Education and Technology Foundation.
The document provides a software requirement specification for a Facebook social networking system. It outlines requirements for key features such as creating events, attending events, searching for friends, adding friends, creating groups, uploading photos/videos, sharing status updates, sending/receiving messages, commenting, and more. It describes the user interfaces for standard users and administrators. It also covers overall product description, user characteristics, constraints, and functional and non-functional requirements.
Similar to Aloha Social Networking Portal - SRS (20)
This document summarizes two tasks for a final project using Yelp data:
1. Predicting business categories using an information retrieval approach. The dataset was divided into training and test sets. Categories were predicted for businesses in the test set based on features extracted from reviews in the training set. Precision and recall were calculated by comparing predictions to ground truths.
2. Predicting the most discussed attributes for each city, such as "good for kids" or "music". An attribute map was created using WordNet. Attributes were ranked for cities in test and training sets using BM25. Precision and recall were calculated by comparing test set predictions to those from the training set. Challenges included data cleaning, feature extraction, and evaluation
Collaborative filtering is a technique used in recommender systems to predict a user's preferences based on other similar users' preferences. It involves collecting ratings data from users, calculating similarities between users or items, and making recommendations. Common approaches include user-user collaborative filtering, item-item collaborative filtering, and probabilistic matrix factorization. Recommender systems are evaluated both offline using metrics like MAE and RMSE, and through online user testing.
This document outlines the sprints and epics planned for a restaurant management system over three sprints from July 6 to August 13, 2015. Sprint 1 focuses on account, organization, and data creation. Epics include order creation, queue and delivery, and completion. Sprint 2 adds user creation, roles, and permissions. New features include delivery options and time tracking. Sprint 3 covers menu, restaurant, and inventory management. Reporting is added at the outlet and chain level. Complex items like raw material adjustment are deferred due to time constraints.
This document summarizes the results of a technology survey comparing Visualforce and Lightning platforms in Salesforce. It finds that while Lightning is designed for mobile and integrates with Bootstrap, it has poor performance with slow loading and scrolling. Visualforce has better performance with fast page loads but some JavaScript issues. Considering performance is a major concern, Visualforce is chosen as it has good performance and easily integrates additional libraries. The document also provides an outline for a landing page with menu, cart, and food category tabs.
The document summarizes two surveys:
1) A survey of current manual order management systems in small restaurants, which typically involve paper order slips that are tracked through the kitchen and to customer tables.
2) Surveys of two automated order management systems: a fully automated sushi restaurant in Japan that uses conveyor belts and barcodes for contactless ordering and payment, and U.S. restaurant chain Chili's which provides tablets at tables to electronically place and pay for orders.
This document outlines 7 epics and user stories to develop the basic features of a restaurant management system. The epics include order creation, order queue and delivery, order completion, menu management, managing restaurant information, reporting per outlet and for the chain, and inventory management. Future epics proposed are marketing campaign management, both for individual restaurants and chains, and personalization features using customer order histories and preferences.
Visualforce allows users to build custom web pages on Salesforce using the model-view-controller (MVC) pattern. It provides tools like Visualforce tags and components to create user interfaces that leverage standard and custom objects along with Apex controllers and logic. Visualforce pages can be developed using the Developer Console or Force.com IDE and integrated with other technologies to create responsive, custom applications.
Paper written based on study of algorithms for external memory sorting in the coursework of CSCI-B 503 Algorithms Design and Analysis under guidance of Prof Funda Ergun
This document discusses a one sample runs test, which is used to determine if a sample is randomly drawn from a population. It defines a run as a series of like items. The document provides an example of coin flips and illustrates how different outcomes would indicate random or non-random patterns. It presents the formula for the runs test and applies it to an example of testing if diseased trees are randomly or non-randomly grouped. The requirements, advantages, and other applications of the runs test are outlined.
This document discusses internet marketing. It begins with an introduction to the history and development of the internet from its origins in the early 1980s to its current widespread use for activities like communication, social networking, e-commerce, and media consumption. Internet marketing refers to marketing products or services online using tools like display advertising, email marketing, interactive advertising, and search engine optimization. The document then provides examples and descriptions of these different internet marketing tools and techniques. It concludes by discussing the advantages, disadvantages, effects on different industries, and scope for further growth of internet marketing.
The document summarizes a case study about a company called Mebrisk India that underwent changes to its operations and supply chain management over time. It describes the company's conditions before and after the director Parthiv Vyas implemented a "Plan Revamp" in 1997-1999 to improve coordination between suppliers, production, and sales. The new director Kevin Mathais questions whether the changes were necessary. The case examines whether further changes should be made or if the original revamp should be maintained, and how to best achieve coordination between all parts of the supply chain in a dynamic environment.
This presentation was prepared as part of the curriculum studies for CSCI-659 Topics in Artificial Intelligence Course - Machine Learning in Computational Linguistics.
It was prepared under guidance of Prof. Sandra Kubler.
CYBER SECURITY ENHANCEMENT IN NIGERIA. A CASE STUDY OF SIX STATES IN THE NORT...AJHSSR Journal
ABSTRACT: Security plays an important role in human life and endeavors. Securing information and
disseminating are critical challenges in the present day. This study aimed at identifying innovative technologies
that aid cybercrimes and can constitute threats to cybersecurity in North Central (Middle Belt) Nigeria covering
its six States and the FCT Abuja. A survey research design was adopted. The researchers employed the use of
Google form in administering the structured questionnaire. The instruments were faced validated by one expert
each from ICT and security. Cronbach Alpha reliability Coefficient was employed and achieved 0.83 level of
coefficient. The population of the study was 200, comprising 100 undergraduate students from computer science
and Computer/Robotics Education, 80 ICT instructors, technologists and lecturers in the University and
Technical Colleges in the Middle Belt Nigeria using innovative technologies for their daily jobs and 20 officers
of the crime agency such as: Independent Corrupt Practices Commission (ICPC) andEconomic and Financial
Crimes Commission (EFCC). Three research purposes and questions as well as the hypothesis guided the study
on Five (5) point Likert scale. Data collected were analyzed using mean and standard deviation for the three
research questions while three hypotheses were tested using t-test at 0.05 level of significance. Major findings
revealed that serious steps are needed to better secure the cybers against cybercrimes. Motivation, types, threats
and strategies for the prevention of cybercrimes were identified. The study recommends that government,
organizations and individuals should place emphasis on moral development, regular training of its employees,
regular update of software, use strong password, back up data and information, produce strong cybersecurity
policy, install antivirus soft and security surveillance (CCTV) in offices in order to safeguard its employees and
properties from being hacked and vandalized.
KEYWORDS: Cybersecurity, cybercrime, cyberattack, cybercriminal, computer virus, Virtual Private Networks
(VPN).
Discover essential SEO Google tools to boost your website's performance, from Google Analytics and Search Console to Keyword Planner and Page Speed Insights.
Learn more: https://elysiandigitalservices.com/seo-google-tools/
UR BHatti Academy dedicated to providing the finest IT courses training in the world. Under the guidance of experienced trainer Usman Rasheed Bhatti, we have established ourselves as a professional online training firm offering unparalleled courses in Pakistan. Our academy is a trailblazer in Dijkot, being the first institute to officially provide training to all students at their preferred schedules, led by real-world industry professionals and Google certified staff.
On Storytelling & Magic Realism in Rushdie’s Midnight’s Children, Shame, and ...AJHSSR Journal
ABSTRACT: Salman Rushdie’s novels are humorous books about serious times. His cosmopolitanism and
hybrid identity allowed him access to multiple cultures, religions, languages, dialects, and various modes of
writing. His style is often classified as magic realism, blending the imaginary with the real. He draws
inspiration from both English literature and Indian classical sources. Throughout his works, there is a lineage of
‘bastards of history’, a carnival of shameful characters scrolling all along his works. Rushdie intertwines fiction
with reality, incorporating intertextual references to Western literature in his texts, and frequently employing
mythology to explore history. This paper focuses on Rushdie’s three novels: Midnight’s Children, Shame, and
Haroun and the Sea of Stories, analyzing his postmodern storytelling techniques that aim to explore human
vices and follies while offering socio-political criticism.
KEYWORDS : Magic Realism, Rushdie, Satire, Storytelling, Transfictional Identities
ChatGPT 4o for social media step by step Guide.pdfalmutabbil
In this comprehensive guide, we'll delve into the exciting world of ChatGPT and explore
its practical applications for social media success. Learn how to craft captivating posts
that resonate with your audience, leverage automation to save precious time, and utilize
ChatGPT's analytical prowess to stay ahead of the curve.
Using Playlists to Increase YouTube Watch TimeSocioCosmos
Discover how to use playlists to keep viewers engaged and increase your watch time.
https://www.sociocosmos.com/product-category/youtube/youtube-comments/
1. AlohaSocial Network
Software Requirement Specification (SRS)
Document/Version Number: Version 1.1
Creation Date: February 5, 2015
Account/Client: SOFTA Inc.
Author: Milind Gokhale; Renuka Deshmukh; Mrunal Pagnis; Vivek Supe
Editor: Milind Gokhale; Renuka Deshmukh; Mrunal Pagnis; Vivek Supe
Last Edit Date: February 28, 2015
File Name: SRS_Aloha_My_Group.docx
2. Revision History
Date Description Author Comments
02/25/2015 Initial Draft Vivek Supe, Mrunal Pagnis Initial draft of the document
02/26/2015 Version 0.1 Vivek Supe, Milind Gokhale,
Renuka Deshmukh, Mrunal
Pagnis
Inserted the basic
requirements.
02/27/2015 Version 1.0 Renuka Deshmukh, Milind
Gokhale
First Revision
02/28/2015 Version 1.1 Vivek Supe, Milind Gokhale,
Renuka Deshmukh, Mrunal
Pagnis
Added use cases and
Formatting changes
Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
Signature Printed Name Title Date
John Doe Senior Architect February 28, 2015
Balaprasath Rajan Professor February 28, 2015
3. Table of Contents
Aloha Social Network..........................................................................................................................................0
Software Requirement Specification (SRS)....................................................................................................0
Revision History...................................................................................................................................................0
Document Approval ............................................................................................................................................0
Table of Contents ................................................................................................................................................0
1 Introduction.................................................................................................................................................2
1.1 Purpose................................................................................................................................................2
1.2 Scope....................................................................................................................................................2
1.3 Definitions & acronyms......................................................................................................................2
1.4 Intended Audience..............................................................................................................................2
1.5 Overview..............................................................................................................................................2
2 Overall Description......................................................................................................................................3
2.1 Product Perspective............................................................................................................................3
2.2 Product Functions...............................................................................................................................3
2.3 Operating Environment......................................................................................................................3
2.4 User characteristics ............................................................................................................................3
2.5 Constraints ..........................................................................................................................................3
2.6 Assumptions and Dependencies........................................................................................................3
2.6.1 Assumptions................................................................................................................................3
2.7 Apportioning of requirements...........................................................................................................4
3 Specific Requirements................................................................................................................................5
3.1 External interface requirements........................................................................................................5
3.1.1 User interfaces............................................................................................................................5
3.1.2 Hardware Interfaces...................................................................................................................5
3.1.3 Software interfaces ....................................................................................................................5
3.1.4 Communication interfaces.........................................................................................................5
3.2 Functional requirements....................................................................................................................6
3.2.1 Classes for classification of specific requirements...................................................................6
3.2.2 User Registration profile and settings - FRU.............................................................................6
3.2.3 Friends and Suggestions - FRF ...................................................................................................9
3.2.4 Posts and Shares (Scribbles) - FRP...........................................................................................10
3.2.5 Chat - FRC..................................................................................................................................12
4. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 0. <Table of Contents
1
3.3 Use Cases...........................................................................................................................................14
3.3.1 Use Case UC1............................................................................................................................14
3.3.2 Use Case UC2............................................................................................................................15
3.3.3 Use Case UC3............................................................................................................................15
3.3.4 Use Case UC4............................................................................................................................15
3.3.5 Use Case UC5............................................................................................................................15
3.3.6 Use Case UC6............................................................................................................................16
3.3.7 Use Case UC7............................................................................................................................16
3.3.8 Use Case UC8............................................................................................................................16
3.3.9 Use Case UC9............................................................................................................................16
3.3.10 Use Case UC10..........................................................................................................................17
3.3.11 Use Case UC11..........................................................................................................................17
3.3.12 Use Case UC12..........................................................................................................................17
3.4 Non-functional Requirements .........................................................................................................18
3.4.1 Performance requirements .....................................................................................................18
3.4.2 Security requirements..............................................................................................................18
3.4.3 Software Quality Attributes Requirements............................................................................18
3.5 Requirement Traceability Matrix.....................................................................................................19
4 Change Control Mechanism.....................................................................................................................20
4.1 Documenting the change request:..................................................................................................20
4.2 Formal assessment:..........................................................................................................................20
4.3 Designing and testing:......................................................................................................................20
4.4 Final assessment:..............................................................................................................................20
5 Appendices ................................................................................................................................................21
5.1 Appendix 1: Glossary ........................................................................................................................21
5. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 1. Introduction
2
1 Introduction
1.1 Purpose
The purpose of this Software Requirement Specification document is to give an overview of
the functional and non-functional requirements of a social networking website for the web.
1.2 Scope
Aloha is a web portal which allows users to connect with their friends and family through a
common platform. Furthermore, users’ can share scribbles and ChitChat with their friends. These
chats can be saved or deleted as per the users’ wishes. Users can also maintain, update or delete
their account.
1.3 Definitions & acronyms
The following table explains terms and acronyms specific to this SRS.
Term/Acronym Description/Definition
Aloha Aloha is a social networking website.
FR Functional Requirement
UC Use Case
Scribble Scribble is a post shared by the user on his slate.
ChitChat Chatting activity between two users registered on Aloha.
Slate Wall where users scribble.
1.4 Intended Audience
This document is intended for a varied set of audiences. This document serves as a contract
agreement with SOFTA. This document is intended for the SOFTA authorities, the design team,
developers, project manager, team leads, supervisors, security analysts, testing team and the QA
team to better understand the system requirements.
1.5 Overview
The remaining document has three sections. The second section gives a generic overview of
the systems including requirements and functions in a broader view. It gives an insight into the
user characteristics, constraints and the operating environment of the system.
The third section gives a detailed look of the functional and non-functional requirements of
the system. It also gives a complete description explaining these requirements. This section also
gives information about the quality attributes the system needs to satisfy. Section four explains
the methodology followed in case of any change in requirements. Section five is a list appendix
that helps to better understand the SRS.
6. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 2. Overall Description
3
2 Overall Description
2.1 Product Perspective
Aloha is a free online social networking website which allows users to connect with their
friends and family. It gives a global platform for users around the world to connect with each
other. Users can also share scribbles and engage in chitchat conversations. This is an independent
product and will be the first release of the product.
2.2 Product Functions
User can register to the social network and login whenever he wishes to do so. User can
build his profile, add or edit information, set visibility to various profile sections, see his own
profile and upload profile picture to his profile.
With this application users can connect with their friends and family through a common
platform. A user can search for his friends and will be shown appropriate results if matching
profiles are found. Any user can post scribbles to his profile which will be visible to his
connections.
2.3 Operating Environment
Minimum: 2 CPU Cores (Recommended: 4 CPU Cores or more)
Recommended memory: 2 GB for Windows platforms, 1 GB for Linux
Minimum disk space: 500 MB
Recommended disk space: 1024 MB
Java Platform Enterprise Edition (Java EE)
Apache 8.x
JDK 6+ for Spring Framework
MySQL 5.x.x
2.4 User characteristics
Standard users may belong to any demographic group including any gender, nationality
that can use computer’s browser. Aloha requires its users to be above 18 years of age. Aloha does
not require its users to have any specific computer knowledge. User interface is in English
language so users should have a Basic English reading knowledge.
2.5 Constraints
1. Aloha will support the following browsers – IE 8+, Chrome 27.0+, Firefox 30+.
2. Aloha supports English language only.
3. Aloha requires certificates issued by CA to use HTTPS.
4. The first version of the website is intended to be viewed best on a desktop browser.
2.6 Assumptions and Dependencies
2.6.1 Assumptions
1. There will be availability of Internet via 3G, 4G or Wi-Fi.
2. The user of the site will be acquainted with Basic English language.
3. The user should have a valid email address in order to register into Aloha.
7. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 2. Overall Description
4
4. Central server of the system must be able to handle all the incoming requests
simultaneously.
5. The user has basic knowledge of computers and internet.
6. In the current functionality the user will be able to invite one friend at a time to Aloha
network.
2.7 Apportioning of requirements
Requirements like multiple invites from user’s Gmail contacts will be planned in the future
releases of the product. Also video sharing in Scribbles and ChitChat may be included in future.
Certain machine learning algorithms will be included for friend suggestions in future releases.
8. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
5
3 Specific Requirements
3.1 External interface requirements
3.1.1 User interfaces
Standard users will use the web browser to use Aloha. Thus, it shall have a login page for
users to login to Aloha. For those who are first time users will fill up registration details. After
logging into the system, the user will be shown his profile and the slate containing the posts
shared by user’s friends. User is given options to logout, search people and change any of his
personal settings on his home page.
3.1.2 Hardware Interfaces
N/A
3.1.3 Software interfaces
E-mail Interface
This interface uses the SMTP/POP service provided by third party to send emails to
required user. This service will help notify users with required actions through a conventional
medium.
Captcha Service Interface
Captcha service will be used for human identification.
3.1.4 Communication interfaces
ALOHA is based on HTTP as it is a website. Moreover TCP/IP is used for chatting
functionality.
9. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
6
3.2 Functional requirements
3.2.1 Classes for classification of specific requirements
The functional requirements are grouped as below
1. User Registration profile and settings – [FRU]
2. Friends and suggestions – [FRF]
3. Posts and Shares (Scribbles) – [FRP]
4. ChitChat – [FRC]
3.2.2 User Registration profile and settings - FRU
3.2.2.1 Functional Requirement FRU1
ID – FRU1
Name – User Registration
Description – User will create an account if there is no existing account associated with user’s
email-id. User should enter account details such as name, email-id, contact number, birth date,
captcha and password. All these are required fields and account creation cannot proceed
unless these are filled. User is registered after this information is validated and user agrees
with the terms and conditions. User must be 18 years old or more. Contact number should be
a 10 digit numeric field. First and last name should not exceed 20 characters each. Password
should be at least 8 characters long, at most 15 characters including at least one capital and
small letter, a special character and a number. Any of the above fields must not have ( ‘ , “, : , ;
, <, >, {, }, -, %, $, |, ], [).
Dependency – None
3.2.2.2 Functional Requirement FRU2
ID – FRU2
Name – Email Verification
Description – When the user has registered, a verification link is sent to the email-id set at the
time of registration so as to verify given email-id as genuine. After user has verified the
account it will be marked as verified. Account privileges will not be given to the user until
verification is complete. User should be able to re-send the verification link to his email-id.
Dependency – FRU1
3.2.2.3 Functional Requirement FRU3
ID – FRU3
Name – Login
Description – User must be registered in order to Login. Input will be the email-id and
password for login. The hash of password should match to the hash of password stored in the
database. If three attempts of password are wrong then a captcha should appear. If more than
8 attempts go wrong, then the account will be locked and an e-mail will be sent to the user
10. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
7
notifying about the wrong password attempts. To unlock the account, user must click on the
unlock link sent to him in the email. If user clicks on forgot password then reset password link
should be emailed to the user. Input to each field must be validated.
Dependency – FRU1
3.2.2.4 Functional Requirement FRU4
ID – FRU4
Name – Add/Edit Education
Description – A part of building user profile. User should be able to add the educational
details. These fields can remain empty. User must be logged in and his account should be
marked as verified to be able to add education. Input to each field must be validated.
Dependency – FRU2, FRU3
3.2.2.5 Functional Requirement FRU5
ID – FRU5
Name – Add/Edit Personal information
Description – A part of building user profile. User should be able to add the personal details
like language, gender, about user and his interests. These fields can remain empty. User must
be logged in and his account should be marked as verified to be able to add personal
information. Input to each field must be validated.
Dependency – FRU2, FRU3
3.2.2.6 Functional Requirement FRU6
ID – FRU6
Name – Add account information
Description – A part of building user profile. User should be able to add the account details like
name, birth date, email-id, phone number and address. Name, birth date and email-id cannot
be empty while the other two can remain empty. User must be logged in. Input to each field
must be validated.
Dependency –FRU3
3.2.2.7 Functional Requirement FRU7
ID – FRU7
Name – Edit account information
Description – A part of building user profile. User should be able to edit the account details like
name, birth date, email-id, phone number and address. Name, birth date and email-id cannot
be empty while the other two can remain empty. If email is changed then email verification
module should be called. User must be logged in. Input to each field must be validated.
11. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
8
Dependency –FRU2, FRU3
3.2.2.8 Functional Requirement FRU8
ID – FRU8
Name – Upload Profile Picture
Description – User should be able to upload the profile picture. The size of profile picture
should be at least 160px * 160px. User may leave this field empty. Profile image should be
visible to all.
Dependency –None
3.2.2.9 Functional Requirement FRU9
ID – FRU9
Name – Set account visibility settings
Description – User should be able to make account details private or public according to his
wish. By default the account details will be visible to public.
Dependency –None
3.2.2.10 Functional Requirement FRU10
ID – FRU10
Name – Set personal information visibility
Description – User should be able to make personal information private or public according to
his wish. By default the personal information will be visible to public.
Dependency –None
3.2.2.11 Functional Requirement FRU11
ID – FRU11
Name – Show Profile
Description – Any logged-in user should be able to see any user’s profile on Aloha.
Dependency –FRU1, FRU2, FRU3
3.2.2.12 Functional Requirement FRU12
ID – FRU12
Name – Delete Account
Description – User may delete his account permanently from ALOHA depending on his wish.
User will be removed from his friends list once deleted. User information will be cleared.
Dependency – FRU1, FRU2, FRU3
12. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
9
3.2.3 Friends and Suggestions - FRF
3.2.3.1 Functional Requirement FRF1
ID – FRF1
Name – Add Friend
Description – A registered user of Aloha should be able to send add friend requests to other
users of Aloha. User can send friend request to already registered users of Aloha. User can
search his friend on Aloha among the registered users and then send a friend request to
him/her.
Dependency – FRU1
3.2.3.2 Functional Requirement FRF2
ID – FRF2
Name – Accept/Ignore Friend Request
Description – If a user gets a friend request from another user, then the user receiving the
request should have an option to accept or ignore the friend request. If the user selects to
accept the friend request, the requestor is added to the friend list of the acceptor. If the user
selected to ignore the request, the sender continues to see the status of the request as
“Request Sent” and the request is removed from the queue of the request receiver.
Dependency – FRF1
3.2.3.3 Functional Requirement FRF3
ID – FRF3
Name – Delete Friend
Description – A registered user of Aloha should be able to un-friend any of the existing friends
in his/her friend’s list.
Dependency – FRU1, FRF1
3.2.3.4 Functional Requirement FRF4
ID – FRF4
Name – List Friends
Description – Whenever the user is on any person’s profile page, he should have an option to
view currently open user profile’s friends on a page. User can have many friends and the
maximum number of friends shown at a time will be 20, and paging will be implemented to
show more friends if the user has more than 20 friends.
Dependency – FRU3, FRU1, FRF1
3.2.3.5 Functional Requirement FRF5
ID – FRF5
13. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
10
Name – Search User
Description – User should be able to search for his/her friends who may be registered on
Aloha. User will put the name of the friend and click search after which the search results will
display all the people registered on Aloha by the searched name. When the search results are
displayed the maximum number of results shown at a time will be 20, and paging will be
implemented to show more results.
Dependency – FRU3
3.2.3.6 Functional Requirement FRF6
ID – FRF6
Name – Friend Suggestions
Description – User will be given suggestions for adding more friends. The friend suggestions
will be based on the users having maximum number of mutual friends with the user. The
maximum number of friend suggestions displayed will be 20 at a time, and paging will be
implemented to show more suggestions.
Dependency – FRU3
3.2.3.7 Functional Requirement FRF7
ID – FRF7
Name – Invite Friend
Description – User should be able to invite more friends to join the Aloha network. User will be
given an option to enter the email address of the person to invite. User will be able to invite
one friend at a time.
Dependency – FRU3, FRU1
3.2.3.8 Functional Requirement FRF8
ID – FRF8
Name – Show Online Friends
Description – User should be able to see currently online friends among all his friends on
Aloha. The user can chat with online friends by clicking on the currently available friends in the
online friends list.
Dependency – FRU3, FRU1
3.2.4 Posts and Shares (Scribbles) - FRP
3.2.4.1 Functional Requirement FRP1
ID – FRP1
Name – Scribble
14. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
11
Description – A registered user of Aloha can share scribbles with his friends. The scribble can
only be plain English text with maximum 500 characters. User can enter the scribble in the
designated text area and on clicking Scribble button; it should be visible to the user and his
friends.
Dependency – FRU3
3.2.4.2 Functional Requirement FRP2
ID – FRP2
Name – Erase
Description – A user can erase a scribble that has been posted. After deletion, the scribble
should not be visible on the users’ or his friends’ slates. Deletion of a scribble should also
remove all the comments associated with that scribble.
Dependency – FRU3, FRP1
3.2.4.3 Functional Requirement FRP3
ID – FRP3
Name – List Scribbles
Description – After a user logs into Aloha, he can see a listing of scribbles posted by him and
his friends. The maximum number of scribbles displayed at a time will be 20, and paging will
be implemented for more scribbles.
Dependency – FRU3
3.2.4.4 Functional Requirement FRP4
ID – FRP4
Name – Comment
Description – For each scribble visible to the user he has the ability to comment on it to
express his opinion. The comment can contain only text and cannot exceed 500 characters in
length. To comment, user can see a text area under the scribble, where he can enter the text.
Dependency – FRU3, FRP1
3.2.4.5 Functional Requirement FRP5
ID – FRP5
Name – Delete Comment
Description – A user can delete a comment written by him or a comment on his scribbles. For
deleting a scribble that he is authorized to delete, a user can see a delete link near the
comment.
Dependency – FRU3, FRP4
15. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
12
3.2.4.6 Functional Requirement FRP6
ID – FRP6
Name – Like a Scribble
Description – Users can like a scribble by clicking on the “Thumb’s Up” button below the
scribble. For any scribble, all users can see a count of the “Liked” scribble.
Dependency – FRU3, FRP1
3.2.4.7 Functional Requirement FRP7
ID – FRP7
Name – Unlike a Scribble
Description – Users can dislike a scribble by clicking on the “Thumb’s Down” button below the
scribble. For any scribble, all users can see a count of the “Disliked” scribble.
Dependency – FRU3, FRP1
3.2.5 Chat - FRC
3.2.5.1 Functional Requirement FRC1
ID – FRC1
Name – ChitChat
Description – User should be able to initiate ChitChat with any user in the friend list who is
online. The other user must seamlessly understand that the ChitChat has been initiated and
the ChitChat message must be forwarded to the intended user. User should be able to receive
ChitChat from any user in the friend list who is online and within the friend list of that user.
Thus the receiving entity can send message back to the originator, thus, completing a two-way
conversation. The message cannot be greater than 250 characters in length.
Dependency – FRU3, FRF8
3.2.5.2 Functional Requirement FRC2
ID – FRC2
Name – Send File
Description – Using this functionality user can send text files to online users. This helps user to
share text documents with users on this platform. The maximum file size would be limited to
25 MB.
Dependency – FRU3, FRF8
3.2.5.3 Functional Requirement FRC3
ID – FRC3
Name – Store ChitChat
16. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
13
Description – User should be able to store ChitChat on exit. So that if the user wants to keep
history of the previous session he can keep it to be brought back.
Dependency – FRU3, FRF8
3.2.5.4 Functional Requirement FRC4
ID – FRC4
Name – Retrieve ChitChat
Description – User should be able to retrieve ChitChat when the ChitChat when the user wants
to see ChitChat history.
Dependency – FRU3, FRF8
17. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
14
3.3 Use Cases
Figure 1: Use Case Diagram
3.3.1 Use Case UC1
3.3.1.1 Objective
Registration
3.3.1.2 Priority
High
3.3.1.3 Actors
End-User
3.3.1.4 Pre-conditions
The user has internet and opens the website on his browser.
3.3.1.5 Post-conditions
The user is now a member of Aloha website.
18. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
15
3.3.2 Use Case UC2
3.3.2.1 Objective
Email Verification
3.3.2.2 Priority
High
3.3.2.3 Actors
End-User
3.3.2.4 Pre-conditions
The user is registering to aloha website as a new user.
3.3.2.5 Post-conditions
The user is now a registered user on Aloha and can update account, post scribbles, add
friends and chat with other registered friends.
3.3.3 Use Case UC3
3.3.3.1 Objective
Login
3.3.3.2 Priority
High
3.3.3.3 Actors
End-User
3.3.3.4 Pre-conditions
User is a registered member of Aloha.
3.3.3.5 Post-conditions
The user logs in successfully and can now view his profile, friends and scribbles.
3.3.4 Use Case UC4
3.3.4.1 Objective
Manage Account
3.3.4.2 Priority
Medium
3.3.4.3 Actors
End-User
3.3.4.4 Pre-conditions
A user is logged into Aloha.
3.3.4.5 Post-conditions
The user account has been successfully updated as per his requirements, like, update
account, visibility setting, etc.
3.3.5 Use Case UC5
3.3.5.1 Objective
Delete Account
3.3.5.2 Priority
Medium
3.3.5.3 Actors
End-User
19. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
16
3.3.5.4 Pre-conditions
User is a registered member of Aloha.
3.3.5.5 Post-conditions
Account is successfully deleted.
3.3.6 Use Case UC6
3.3.6.1 Objective
Add Friend
3.3.6.2 Priority
High
3.3.6.3 Actors
End-User
3.3.6.4 Pre-conditions
User is a registered member of Aloha.
3.3.6.5 Post-conditions
Friend is added successfully.
3.3.7 Use Case UC7
3.3.7.1 Objective
List Friends
3.3.7.2 Priority
High
3.3.7.3 Actors
End-User
3.3.7.4 Pre-conditions
User is a registered member of Aloha.
3.3.7.5 Post-conditions
User sees a list of his friends.
3.3.8 Use Case UC8
3.3.8.1 Objective
Invite Friend
3.3.8.2 Priority
Low
3.3.8.3 Actors
End-User
3.3.8.4 Pre-conditions
User is a registered member of Aloha.
3.3.8.5 Post-conditions
Friend invite is sent successfully on his email allowing him to register as a new user.
3.3.9 Use Case UC9
3.3.9.1 Objective
Scribble
3.3.9.2 Priority
High
20. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
17
3.3.9.3 Actors
End-User
3.3.9.4 Pre-conditions
User is a registered member of Aloha.
3.3.9.5 Post-conditions
Posted scribbles are visible to the user and his friends.
3.3.10 Use Case UC10
3.3.10.1 Objective
Comment
3.3.10.2 Priority
High
3.3.10.3 Actors
End-User
3.3.10.4 Pre-conditions
User is a registered member of Aloha.
3.3.10.5 Post-conditions
Posted comments are visible to the user and his friends.
3.3.11 Use Case UC11
3.3.11.1 Objective
ChitChat
3.3.11.2 Priority
High
3.3.11.3 Actors
End-User
3.3.11.4 Pre-conditions
User is a registered member of Aloha.
3.3.11.5 Post-conditions
The user successfully performs direct chitchat with his friend.
3.3.12 Use Case UC12
3.3.12.1 Objective
Send File
3.3.12.2 Priority
High
3.3.12.3 Actors
End-User
3.3.12.4 Pre-conditions
User is a registered member of Aloha.
3.3.12.5 Post-conditions
The second user successfully receives the send file.
21. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
18
3.4 Non-functional Requirements
3.4.1 Performance requirements
3.4.1.1 Scalability
System should be able to handle a large number of users. For e.g. Handling around
thousand users at the same time.
3.4.1.2 Speed
The application should be fast. It should not slow down with increase in the number of
users. Search functionality should be fast to enable better end-user experience. The system
should be quick enough to be able to respond to the user actions within a short period of time.
E.g. the search user functionality of Aloha should perform a quick search among the users on
the database.
3.4.2 Security requirements
During user registration, the given email address is validated.
The password should be at least 8 characters, containing at least a small character and one
capital, a number and a special character.
Password is stored as a hash value in database.
We are transferring all data via HTTPS i.e. via SSL so that the data is encrypted during the
transit. Thus safeguarding the user information.
Re-capcha service is used during registration for human identification.
3.4.3 Software Quality Attributes Requirements
3.4.3.1 Usability
Aloha User interface should be simple and clear to be able to understand by any user.
3.4.3.2 Availability
The system should be available at all times. It should be ensured that there should be
minimum or no downtime to ensure better user experience.
3.4.3.3 Availability
The system should be reliable. It should yield correct results if a user performs searches
for a person. Also, if the user sends chitchat message or media, the system should
ensure that the correct message is delivered to the correct destination without any loss
or change in content.
3.4.3.4 Testability
The application should be testable. A separate test environment should be set up where
testers and the Quality Assurance engineers can test the application for bugs and/or
incomplete or missed requirements.
3.4.3.5 Maintainability
The system should be developed in such a way that it is extensible. It should be easy to
incorporate new features requirements or accommodate a change in the existing
requirements.
22. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 3. Specific Requirements
19
3.5 Requirement Traceability Matrix
The requirement traceability matrix is available at –
https://documentcenter.whatsapp.com/srs/requirements/RTM1.xlsx
The Link for requirement traceability matrix will be updated from time to time and will be made
available in this section of the SRS.
23. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 4. Change Control Mechanism
20
4 Change Control Mechanism
4.1 Documenting the change request:
Before the change is considered the client must document the change and its requirement
so that developer can understand the implication that the changes have.
4.2 Formal assessment:
If a new change requirement is brought in, it must be approved by the change control
board to be considered for development.
4.3 Designing and testing:
If the request is accepted it is queued for development. Once the request is picked up by
the developer the configuration files are checked out by the developer and changes are made on
those. Once the changes are fixed the system will be tested on a sandbox with various baseline
test cases.
4.4 Final assessment:
Once that is proven to be a success the product is pushed into the repository. But if the
change is too drastic it will be posted to the next version of the software.
24. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 5. Appendices
21
5 Appendices
5.1 Appendix 1: Glossary
Term/Acronym Description/Definition
SRS Software Requirement Specification
API Application Programming Interface
HTTP Hyper Text Transfer Protocol
HTTPS Hyper Text Transfer Protocol over SSL
SSL Secure Socket Layer
IE Internet Explorer
TCP/IP Transfer Control Protocol/Internet Protocol
CA Certificate Authority
CAPTCHA Completely Automated Public Turing test to tell Computers and
Humans Apart
25. Aloha Social Network: Software Requirement Specification (SRS)
Chapter 5. Appendices
22
References:
1. Software requirements specification,
http://en.wikipedia.org/wiki/Software_requirements_specification
2. Donn Le Vie, Jr., “Writing Software Requirements Specifications (SRS)”
http://techwhirl.com/writingsoftwarerequirementsspecifications/ (accessed Jan 30, 2015)
3. Software Requirements Specification Instructions,
https://www.dir.texas.gov/SiteCollectionDocuments/IT%20Leadership/Framework/Framework
%20Extensions/SDLC/SDLC_softwareRequirements_instructions.pdf
4. "What Is Change Control? - Definition from WhatIs.com." Search Disaster Recovery. Accessed
March 1, 2015. http://searchdisasterrecovery.techtarget.com/definition/change-control
5. http://csis.pace.edu/~marchese/cs615sp/L12New/se_l12new_files/image014.jpg.