Software Requirements Specification for Time management system PDF

Preview

Summary

Software Requirements Specification Version 1 <<Annotated Version>> January 07,2019 Time Management Application Mansi Gunsai(160110107014) Tulsi Kaneriya(160110107019) Submitted in partial fulfillment Of the requirements of (2160701)Softwar...

Description

Software Requirements Specification Version 1.0

January 07,2019 Time Management Application

Mansi Gunsai(160110107014) Tulsi Kaneriya(160110107019)

Submitted in partial fulfillment Of the requirements of (2160701)Software Engineering

Table of Contents Table of Contents...................................................................................................................................i List of Figures.........................................................................................................................................ii 1.0. Introduction.....................................................................................................................................1 1.1. Purpose..................................................................................................................................................1 1.2. Scope of Project.....................................................................................................................................1 1.3. Glossary.................................................................................................................................................2 1.4. References.............................................................................................................................................2 1.5. Overview of Document.........................................................................................................................2

2.0.

Overall Description..............................................................................................................4

2.1 2.2 2.3 2.4

System Environment........................................................................................................................4 Functional Requirements Specification............................................................................................5 User Characteristics........................................................................................................................15 Non-Functional Requirements........................................................................................................15

3.0.

Requirements Specification..........................................................................................17 3.1 External Interface Requirements....................................................................................................17 3.2 Functional Requirements................................................................................................................17 3.2.1 Search Article.........................................................................................................................17 3.2.2 Communicate..........................................................................................................................18 3.2.3 Add Author.............................................................................................................................18 3.2.4 Add Reviewer.........................................................................................................................19 3.2.5 Update Person.........................................................................................................................19 3.2.6 Update Article Status..............................................................................................................20 3.2.7 Enter Communication.............................................................................................................20 3.2.8 Assign Reviewer.....................................................................................................................21 3.2.9 Check Status...........................................................................................................................21 3.2.10 Send Communication.............................................................................................................22 3.2.11 Publish Article........................................................................................................................22 3.2.12 Remove Article.......................................................................................................................23 3.3 Detailed Non-Functional Requirements.........................................................................................23 3.3.1 Reliability...............................................................................................................................23 3.3.2 Availability 24 3.3.3 Security 25 Index...............................................................................................................................................................26

List of Figures Figure 1 - System Environment........................................................................................................................4 Figure 2 - Article Submission Process..............................................................................................................6 Figure 3 - Editor Use Cases..............................................................................................................................8 Figure 4 - Logical Structure of the Article Manager Data..............................................................................23

1.0. Introduction 1.1. Purpose The purpose of this document is to present a detailed description of the Time Management System. The goal of the system is to develop such an application which help people to live a stress free life by organizing their daily routine effectively. Smart system will organize the tasks according to the priorities given by the users which will help to increase their overall productivity at the end of the day.

1.2. Scope of Project This Software Time Management System is a multi-functioning system where a user can create a to-do list which will be including simple drag & drop interface to rearrange the tasks within a plain list or organize them into a tree.It creates a hierarchy of tasks & subtasks.Once you have added due-dates & dependencies,the application will automatically generate a smart list of actions that require immediate attention.

Smart system will suggest through notifications about how you can complete the left out tasks throughout week in spare times you have in a week and according to your response given to the application and through various algorithms that we will be using system will learn from inputs given everyday and will suggest best ways to utilize time in daily routine to enhance your productivity for the next day.Here, we will be using Html,CSS,PHP as development languages for developing webApplication & MYSQL for database.

1.3. Glossary Term Active Article

Definition The document that is tracked by the system; it is a narrative that is planned to be posted to the public website. Author Person submitting an article to be reviewed. In case of multiple authors, this term refers to the principal author, with whom all communication is made. Database Collection of all the information monitored by this system. Editor Person who receives articles, sends articles for review, and makes final judgments for publications. Field A cell within a form. Historical Society Database The existing membership database (also HS database). Member A member of the Historical Society listed in the HS database. Reader Anyone visiting the site to read articles. Review A written recommendation about the appropriateness of an article for publication; may include suggestions for improvement. Reviewer A person that examines an article and has the ability to recommend approval of the article for publication or to request that changes be made in the article. Software Requirements A document that completely describes all of the functions Specification of a proposed system and the constraints under which it must operate. For example, this document. Stakeholder Any person with an interest in the project who is not a developer. User Reviewer or Author.

1.4. References IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications. IEEE Computer Society, 1998.

1.5. Overview of Document The next chapter, the Overall Description section, of this document gives an overview of the functionality of the product. It describes the informal requirements and is used to ,iestablish a context for the technical requirements specification in the next chapter.

The third chapter, Requirements Specification section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product. Both sections of the document describe the same software product in its entirety, but are intended for different audiences and thus use different language.

2.0.

Overall Description

2.1

System Environment The Time Management System has one active actors and one cooperating system.

The User can access the App without Internet . Any User can directly communicate with the system. The User accesses the entire system directly.

2.2

Functional Requirements Specification This section outlines the Functions of the System.The User is the main actor in the

system.Before the system can be initiated we assume that the User has already downloaded the App on their System.

1.

Planning – Time management systems should help you plan how to use your time according to the tasks, projects, and goals that you need or want to complete.

2.

Execution – Time management systems should help you execute the items you have planned.

3.

Evaluation – Time management systems should help you evaluate how you spent your time so that you can become more effective at planning and executing future tasks.

Initial Step-By-Step Description 1.User Inputs their task into the System and sets priorities. 2.The System asks for the notifications if the user wants to set any. 3.If User has set any tasks on the previous Day The system will ask to schedule any pending task. 4.The System will make a perfect schedule for the User for current Day.

5.The System will Evaluate at the End of the Day and will show it to User.

1)Task Scheduling Priorities Wise User will Input The tasks from the Drag & Drop Menu provided in the system as well as User can set new task with add schedule button and priority will be assigned along with each task according to priorities given the system will set tasks as well it will use yesterday’Evaluation plan to set the tasks more effectively.

2)Personal Assistant to the Users Such system can become a personal assistant for Users who will see all the tasks and Goals they have set.They will be able to arrange these tasks in an order they like to make the most of their working hours. 3)Notification System Notifications are important because of the human nature people tend to forget different things, be they important or not. It is always better to set automatic notifications if there are tasks that you may forget.

4)Suggestions By The System Smart system will suggest through notifications about how you can complete the left out tasks throughout the week in spare times you have in a week and according to your response given to the application the it will give you feedback to enhance your productivity for the next day. 5)Evaluation By The System

According to User’s response given to the system for the tasks done throughout the day the system will design a feedback model ,which will be displayed to the user at the end of the day. 2.3)User Characteristics The User any person who is not able to manage their time properly and inefficient not enough productive .So to help them to increase their productivity the App will help them. The User is expected to be Windows literate and to be able to use button, pull-down menus,and similar tools. The User is expected to have knowledge of English Language.

2.4)Non-functional requirements We are using here xampp for the connections with database and the application.The performance of the system will be according to the user input.The System is going to be reliable due to complete hierarchy of the to-do-list entered by the user.

3.0.

Requirements Specification

3.1

External Interface Requirements The only link to an external system is the link to the database to verify the Identity a

User. The Database fields of interest to the Time Management Systems are user name, Mobile number, and email address (an optional field for the Database). To use the paid features of the system as user will complete the predures of payment the paid status field will become activated and user will be able to access those features.

3.2

Functional Requirements

1) When the user will first will download the application he will have to answer some questions related to his basic daily routine.

2)Those inputs provided by the user will be stored and while setting his schedule everyday those inputs will be set automatically. 3) Everyday at the start of the day the user will enter tasks for the day priority wise. 4)According to the priority set by user the system will set the schedule for the user in best possible way. 5)The User can set Events as well from the Navigation bar alogng with reminders. 6)After setting the schedule for the entire day the user will be asked if he wants to set any notifications he will be provided with the list of tasks having higher priority to set for notifications. 7)System will be providing one more feature that is to how many times throughtout the week the user wants to repeat for a new activity added in a schedule. 8)At the end of the day the system will ask the user to input about his day and show him analysis of the entire day spent which will help user for more productivity. 9)From the inputs provided by the user everyday the machine will learn about the behavior of the user.

3.3

Detailed Non-Functional Requirements

Reliability The System is reliable for user using the Android device as it is going to be an android application. Availability The system shall allow users to restart the application after failure with the loss of at most 12 characters of input. Security   

Keep specific log or history data sets Assign certain functions to different modules Restrict communications between some areas of the program



Check data integrity for critical variables...