Software Requirements

Specification
for

Eisenhower's todo

Version 1.0 approved

Prepared by Vipul Chaudhary

PDEU, Gandhinagar

11-10-2022

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ........................................................................................................................................ 1
2. Overall Description ..................................................................................................................2
2.1 Product Perspective.......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment .................................................................................................................... 2
2.5 Design and Implementation Constraints .......................................................................................... 2
2.6 User Documentation ........................................................................................................................ 2
2.7 Assumptions and Dependencies ...................................................................................................... 2
3. External Interface Requirements ...........................................................................................3
3.1 User Interfaces ................................................................................................................................. 3
3.2 Hardware Interfaces ......................................................................................................................... 3
3.3 Software Interfaces .......................................................................................................................... 3
3.4 Communications Interfaces ............................................................................................................. 3
4. System Features .......................................................................................................................3
4.1 System Feature 1 .............................................................................Error! Bookmark not defined.
4.2 System Feature 2 (and so on) ..........................................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements .......................................................................................4
5.1 Performance Requirements .............................................................................................................. 4
5.2 Safety Requirements ........................................................................................................................ 4
5.3 Security Requirements ....................................................................Error! Bookmark not defined.
5.4 Software Quality Attributes ............................................................................................................. 4
5.5 Business Rules ................................................................................Error! Bookmark not defined.
6. Other Requirements .................................................................. Error! Bookmark not defined.
Appendix A: Glossary....................................................................................................................4
Appendix B: Analysis Models .......................................................................................................5
Appendix C: To Be Determined List ............................................................................................6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for Eisenhower’s to-do
Page 1

1. Introduction

1.1 Purpose
This is a Software Requirement Specification for EisenHower’s todo App (version 1.0). It’s purpose
if to describe function requirements, features and other implementation requirements for this
system’s (App’s) function.

1.2 Document Conventions

EisenHower’s todo is a Mobile application that will be available shortly. As a result, the SRS
document attempts to clarify currently implemented software capabilities and to describe
requirements for future additions. This document can be used as a reference for people who wish
to understand the program's present features as well as those who want to design new programme
components.

1.3 Intended Audience and Reading Suggestions

The SRS document is intended for:
• Developers that want to add new features to the Application.
• Testers who are interested in identifying any problems in the application and reporting them
for improvement.
• All Application users who are interested in learning more about the features provided by
EisenHower’s todo app.

1.4 Product Scope

This software is a to-do list arrangement programme that can be used by students, teachers, or
any worker who needs to organize their to-do lists. The primary difference between this app and
others is that it allows you to organize your to-do lists based on Eisenhower's Urgent/Important
Principle. That is, whether your work is urgent or important, urgent but unimportant, or any mix of
the two.

As a result, it will be beneficial to those who want to efficiently manage their to-do lists.

1.5 References
No references.
Software Requirements Specification for Eisenhower’s to-do
Page 2

2. Overall Description

2.1 Product Perspective

This Application is specifically designed for organizing to-do lists, but in different way, using
Eisenhower's Urgent/Important Principle. Principle says that before setting any task ask these two
questions: ‘is it important?’ And ‘is it Urgent’ and arrange them accordingly. We will provide facility
for the same method. It will be an Android mobile application an any Android mobile user can have
it, after we published on Play Store.

2.2 Product Functions

Some of the main Functions of Eisenhower’s to-do app is:
• Add Urgent and Important task
• Add Urgent and not important task
• Add Not urgent but important task
• Add Not urgent and not important task
• Mark a task as Completed
• Delete task

2.3 User Classes and Characteristics

Eisenhower’s todo Application can be used by common people for certain purposes. These users
are the principal recipients of Eisenhower’s to-do, and they are not needed to have particular
academic or instructional training. Users might be of any age as well. It is sufficient for these users
to possess some basic computer literacy without the requirement for advanced training or
expertise.

2.4 Operating Environment

Eisenhower’s todo is a android application and it can be operated only on android devices.

2.5 Design and Implementation Constraints

There is no much of constraint on design but our app will work only in portrait mode, as of now it
doesn’t support landscape mode, we will be implementing that in future.

2.6 User Documentation

There will be how to use tutorial on our YouTube channel ‘veer creations’, however this document
is intended to be an indirect documentation from now on.

2.7 Assumptions and Dependencies

This app data is dependent on device local storage, it should be shared with application, other than
that nothing external factor is affecting process of this application.
Software Requirements Specification for Eisenhower’s to-do
Page 3

3. External Interface Requirements

3.1 User Interfaces

For user interface shake we are not going to depend on any external resources, it all will be on
system.

3.2 Hardware Interfaces

Eisenhower’s todo works without communicating at all, with any external hardware device. It just
needs to access local storage memory allocated to this app as cache.

3.3 Software Interfaces

Eisenhower’s todo will be using sqlite and SQL data engine for storing task details into dataset as
a local storage.

3.4 Communications Interfaces

Eisenhower’s todo doesn’t need any communication interface, as it works offline.

4. System Features
Eisenhower’s todo will be using system local storage cache to store all data locally.

4.1 Add Task

4.1.1 Description and Priority

This feature gives user functionality of add task to the list, there will be many types of
tasks but that is the main feature we are offering, it has the highest priority.
4.1.2 Stimulus/Response Sequences
Go to Home page -> click on add button as per your task type, there will be 4 parts
for different types of tasks, click on accordingly and then add details it’s asking and
then click on final add and now system will access local storage SQLite and it will
add to your dataset.
4.1.3 Functional Requirements
REQ-1: Add Task

4.2 Complete Task

4.2.1 Description and Priority

This feature will help in to complete task, whenever you completed a task, you will be
removing this task from the list and it will be considered as completed.
Software Requirements Specification for Eisenhower’s to-do
Page 4

4.1.2 Stimulus/Response Sequences

From all task list which ever task is completed, just long press on it and it will be
marked as completed.
4.1.3 Functional Requirements
REQ-1: Complete Task

4.3 Delete Task

4.2.1 Description and Priority

This feature will help user when user mistakenly add some tasks and but he wasn’t
wanting to add, so we need to give facility of remove task. It is having second priority
as it is also one of crucial feature need to be there.
4.1.2 Stimulus/Response Sequences
Go to list and find out your unwanted task and there will be one delete icon, just click
on it and click on yes for just for shake of confirmation.
4.1.3 Functional Requirements
REQ-1: Delete Task

5. Other Nonfunctional Requirements.

5.1 Performance Requirements

The memory, storage space, and computing power requirements for are quite low. The initiative
attempts to give users convenience and usefulness for no cost.

5.2 Safety and Security Requirements

Since our system doesn't use any external systems, there shouldn't be much to worry about in
terms of security; we are certain that it will be completely safe.

5.3 Software Quality Attributes

Our software is simple to use, adheres to UX guidelines, and is fully compatible with Android. Over
time, we will maintain any bugs we find and give the best possible product.

Appendix A: Glossary
• EisenHower’s principal: The important are never urgent, and the urgent are never
important. He is claimed to have ordered his workload and priorities using the "Eisenhower
Software Requirements Specification for Eisenhower’s to-do
Page 5

Principle." He understood that having excellent time management requires both efficiency
and effectiveness.

• SQLite: In the C programming language, SQLite is a database engine. It is a library that

software developers incorporate, not a stand-alone app.

• data engine: The fundamental software component that a database management system
employs to generate, read, update, and remove data from a database is called a database
engine.
• local storage

• interface: the location where disparate systems come together to interact or communicate
with one another

• cache: A cache is a high-speed data storage layer used in computing that keeps a portion
of data, often temporary in nature, so that requests for that data in the future can be fulfilled
more quickly than by accessing the data's primary storage location.

Appendix B: Analysis Models

USECASE DIAGRAM:
Software Requirements Specification for Eisenhower’s to-do
Page 6

Class Diagram:

Sequence Diagram:

1. Add task
Software Requirements Specification for Eisenhower’s to-do
Page 7

2. Complete task

3. Delete task