Functional Specification Document (Template) PDF

Preview

Summary

memory prayer reminder final year project...

Description

Functional Specifications Document Reminder Prayer Mat

Internal Advisor: Mam Bushra Jamil

External Advisor: Sir Maqsood Hashmi Project Manager: Mam Bushra jamil Project Team: M.Saim Saleem (Group leader) M.Haroon (Group Member) M.Waqas Hashmi (Group Member) Submission Date:

_____________________ Project Manager’s Signature

Document



Functional Specifications Document

Definition of Terms, Acronyms and Abbreviations This section should provide the definitions of all terms, acronyms, and abbreviations required to interpret the terms used in the document properly.

Term ASP RS

Description Active Server Pages Requirements Specifications

RPM

Reminder Prayer Mat

Sept. 15, 2003

Page 2 of 8



Sept. 15, 2003

Functional Specifications Document

Page 3 of 8



Functional Specifications Document

Table of Contents

1.

Introduction........................................................................................................................4 1.1 1.2 1.3

Purpose of Document..........................................................................................................................4 Project Overview..................................................................................................................................4 Scope.....................................................................................................................................................4

2.

Functional Requirements..................................................................................................4

3.

Non-functional Requirements...........................................................................................4 3.1 3.2 3.3 3.4

Performance Requirements................................................................................................................4 Safety Requirements...........................................................................................................................4 Security Requirements........................................................................................................................4 User Documentation............................................................................................................................4

4.

Assumptions and Dependencies........................................................................................4

5.

System Architecture...........................................................................................................5

6.

Use Cases............................................................................................................................5 6.1 6.2

Use Case Diagrams.............................................................................................................................5 Use Case Description..........................................................................................................................5

7.

Graphical User Interfaces.................................................................................................6

8.

High Level Design..............................................................................................................6 8.1 8.2 8.2.1 8.2.2 8.2.3

ER Diagram...........................................................................................................................................6 Data Dictionary.....................................................................................................................................6 Data 1............................................................................................................................................................ 6 Data 2............................................................................................................................................................ 6 Data n............................................................................................................................................................ 6

9.

Requirements Traceability Matrix...................................................................................7

10.

Risk Analysis......................................................................................................................8

11.

Cost Estimation Sheet........................................................................................................8

12.

References...........................................................................................................................8

13.

Appendices..........................................................................................................................9

Section 1 Sept. 15, 2003

Page 4 of 8



Functional Specifications Document

1. Introduction 1.1Purpose of Document A prayer mat is just one of those essentials that can help us to keep up the quality of our daily prayers. A prayer mat is also a SUNNAH that can bring added comfort and remove diversions. We are going to make a mat that reminder the one what is time of which prayer and how many Rakkat and sajjood values shown in our reminder prayer mat. It also tells the user Namazi the direction of Kiblah.

1.2Project Overview We are going to make a mat that reminder the one what is time of which prayer and how many Rakkat and sajjood values shown in our reminder prayer mat. We will analyze problem and their solution and we will start a trail in this project with the help of sir maqsood hashmi (head of electronic department),we will use electronic sheet for the testing of system.we also check the limitation of this project and will do the things that need to be done. We will analyze the requirment that are sure to be done are  Research work  Different tool like  7 segment display  4026 ic  6 volt bettery  A prayer mat  Micro controller  Micro Arduino  Two sensor

1.3Scope 1. Firstly, we see the need of reminder prayer mat in our masjids when many our old community and also young often forget their sajjood and rakkat asking problem’s solution to mufti and imam then we realize the need of prayer reminder mat that help our Namazi when they unfortunately forget their rakkat or sajjood also. 2. It will work when a Namazi forget then it i ndicates with a clue that remind the rakkat if he/she forget rakkat or sajjood when he forgets their sajood as well 3. So, we also put the soft button in the mat that count the sajjdah of Namazi when he/she put their hands on the mat then it nicely pushes and Sajjdah will be counted. 4. then Namazi push the head in two time the racket value is count one. 5. First, we have to make it reliable for the Namazi and comfortable 6. It will be cost effective even a normal man can get this from us.

2. Functional Requirements

Sept. 15, 2003

Page 5 of 8



Functional Specifications Document

1. A prayer mat is just one of those essentials that can help us to keep up the quality of our daily prayers. And praying on a clean floor is not an issue. A prayer mat is also a SUNNAH that can bring added comfort and remove diversions. 2. One user at a time interact with Reminder Prayer Mat. 3. We know that many of the people in the work even our around are often forget their rakkat, sajjood as well in prayer. 4. We analyze there are need to do some different to help our Muslim society when we see the people in Masjid when they often ask prayer problem to our mufti sahib.so we see the need of our people. 5. Then our team decide to work on this project and design it. 6. We create a small embedded system in prayer mat.

Analyza and Design We will analyze our requirments and the customer services as well and try to design in rough work to analyze then we will design it in proteus also to check the look and design of PCB that is use in Reminder Prayer Mat and can it grab a user attenion that help us to meet the goal.

Implementation After design process in proteus for PBC(Printed Circuit Board) and we will printed our design in PCB Chip for testing and insert the components to this PCB(Printed Circuit Board) and connected with 6voltage beattery for supply.Then we will use the Micro Arduino for coding in microcontroller and insert code in microcontroller for proform working.we will implement the planing to requirments that essential in this project and implement to procced this project.

Testing After the implementation and deployment our project already complete but to check the running system and accuracy we willl test our remindar mat to either it work nicely or not if it occur some error then we have to check the error in Sensor and Buttons or in programming the we will solve it for better performance.

Evaluation After the testing process we evaluate our project and check the feasibility of the project and then we will launch our project in market companies such as: Taj company that we will meet and discuss our plan and then see for project to launch in market that need to be notice and then we almost to launch our Remindar Prayer Mat(RPM).

3. Non-functional Requirements We will launch our project in market companies such as: Taj company that we will meet and discuss our plan and then see for project to launch in market that need to be notice and then we almost to launch our Remindar Prayer Mat.

3.1Performance Requirements

Sept. 15, 2003

Page 6 of 8



Functional Specifications Document

The RPM(Reminder Prayer Mat) is working very smoothly and working with user interaction easily. RPM is an embedded system that is marge with the prayer Mat and working as a electronic IT device. 3.22 Safety Requirements In the using RPM we will cover all instrument with the plastic sheet that will not be effective by a cold are hot weather. If the microcontroller chip is burn or destroyed in any condition then the backup of RPM is save in backup chip. In the using of RPM prayer mat small babies are not allow to run on prayer mat. Using the charger by charging the RPM prayer mat. If the RPM prayer mat circuit is shot, it will not be effect any human by shot circuit, because we will use small voltage battery like as 6V.

3.3Security Requirements In the security purpose our project will be approved by the Islamic scholars and Mufti’s. The owner of copyright may assign the copyright or grant any interest in the copyright by license. Licenses may also be granted by the Copyright Board to republish a work withheld from the public. Registration of copyright with the Copyright Office is not obligatory, but if registration has taken place the Register of Copyrights gives prima facie evidence of the particulars entered therein.

3.48.5 Business Rules 3.5List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they might imply certain functional requirements to enforce the rules. Mention all users who will be accessing the software and describe their respective rights. 3.6 3.7User Documentation RPM prayer mat sizes are approximately 2.5 ft × 4 ft (0.76 m × 1.22 m) - 4 ft × 6 ft (1.2 m × 1.8 m), enough to kneel above the fringe on one end and bend down and place the head on the other. Easy to use for the user.RPM prayer mat User requirements, often referred to as user needs, describe what the user does with the system, such as what activities that users must be able to perform. That is easily move from one place to another place and it will be a light weight and we will make to sure it in flexible and round it easily.

Sept. 15, 2003

Page 7 of 8



Functional Specifications Document

7. References 1. Sir Maqsood Hashmi is helping for this project and take idea about that and also make testing PCB for this model. 2. Ph: +92 333 8108477 3. Email:- [email protected]

Sept. 15, 2003

Page 8 of 8...