SOFTWARE REQUIREMENT SPECIIFICATION
AND
PROJECT MANAGEMENT PLANING
FOR
SMART BIO-WASTE MANAGEMENT SYSTEM
PRESENTED
BY
YAHYA SHUAIBU
SUBMITTED
TO
DR AYUB KHAN
INTRODUCTION.
Purpose
The main aim is to describe the smart bio waste
management system that
1. Classified different type of bio waste e.g. liquid, so that
conservation can be done easily
2. Provide a system that would raise an alarm whenever a
bin is full
3. Provide direction for the collection offices and create a
path on a particular device e.g. mobile
SCOPE
• The system should be designed in such a way that
it will collect individual refuse to classified
different type of bio-waste like Solid and Liquid.
• Also the system should be able to collect the refuse
and emptied the bin as per defined schedule time
and network path.
OVERVIEW
• It manages the functionality of the system in terms of
hardware, software and human ware.
• It covers the complete society and can be implemented as
well as used in various community of places
• It helps in energy conservation that would result from
gaseous elements in the bin
• To protect the community and society in general
REQUIREMENT SPECIFICATION
External Specific Requirement
ď‚§User Interface:
ď‚§It should be the connector between the various
system and the system or between other part or unit
of the system
REQUIREMENTS
ď‚§Hardware interface
Consist of the tools to be used in controlling the bin
1. Mobile device for tracking and creation of part
2. Alarm signal for sending information
3. Network device for receiving signals
4. Wireless device for communication between the
bin and the administrator's as well as the users
5. A camera would be used to locate a position of
the bin and also serve as a CCTV
INTERFACE
Software interface
• This include the embedded application that will
used in supporting the various functions of the
system
• A GPS for detecting the location or direction
• A Web Server and Data base at the server side
Telecommunication, like a service providers
SPECIFIC REQUIREMENT
• User should dispose the refuse accordingly, either solid
or liquid
• The administrator should locate the place and empty the
bin
• Some of the refuse should be recycled
• Need for quick response from the system for
evacuation
DESIGN CONSTRAINT'S
• The system must be designed to allow the usability
by the users and the municipal officials
• The system should respond when ever a bin is full
for evacuation
• System must be developed for easy use by both
the user and the officials
SOFTWARE SYSTEM ATTRIBUTES
The system should be able to:
ď‚§Reliability: Error free operation
ď‚§Availability: Should be available all the time
ď‚§Security: Should be secured
ď‚§Safety requirement: Their should be back up to avoid
loss of data
ď‚§Maintainability: The designer should be able to
maintain and upgrade the system
SYSTEM ARCHITECTURE
Recycle Bin
Mobile device
Network
Administrator
(Server)
PROJECT MANAGEMENT PLANNING
Cost Analysis
• We identify all the cost and benefits of carrying out the
project and operating the delivered application,
• Expressing these cost and benefits in common units
• The development cost include salary and other
employment cost of the staff involved.
• Setup cost for putting the project into use , it include any
hardware and ancillary equipment
COST-BENEFIT EVALUATION
• Net Profit: Difference between the total project and the
project cash flow
• Pay Back: the time taken to pay back the initial investment
on the project
• Return on investment: Net profitability
• Net present value: profitability Injection and timings
• Internal rate of return: Profit of percentage and interest
RISK ANALYSIS
The following issues are very rare and will result in
system or project failure
• Poor internet network or low speed
• Lack of proper maintenance
• Electricity cut out
• Protection from theft and natural disaster
CONCLUSION
In brief we discussed the details requirement analysis and
specification based on the need of the customer
• From the specification given by the user we try to
develop the basic planning management of the project.
• Other concern issues and analysis will be further
discuss between various stakeholders as the project
continue
THANK YOU

SRS and PMP of Smart Bio- Waste Management System

  • 1.
    SOFTWARE REQUIREMENT SPECIIFICATION AND PROJECTMANAGEMENT PLANING FOR SMART BIO-WASTE MANAGEMENT SYSTEM PRESENTED BY YAHYA SHUAIBU SUBMITTED TO DR AYUB KHAN
  • 2.
    INTRODUCTION. Purpose The main aimis to describe the smart bio waste management system that 1. Classified different type of bio waste e.g. liquid, so that conservation can be done easily 2. Provide a system that would raise an alarm whenever a bin is full 3. Provide direction for the collection offices and create a path on a particular device e.g. mobile
  • 3.
    SCOPE • The systemshould be designed in such a way that it will collect individual refuse to classified different type of bio-waste like Solid and Liquid. • Also the system should be able to collect the refuse and emptied the bin as per defined schedule time and network path.
  • 4.
    OVERVIEW • It managesthe functionality of the system in terms of hardware, software and human ware. • It covers the complete society and can be implemented as well as used in various community of places • It helps in energy conservation that would result from gaseous elements in the bin • To protect the community and society in general
  • 5.
    REQUIREMENT SPECIFICATION External SpecificRequirement ď‚§User Interface: ď‚§It should be the connector between the various system and the system or between other part or unit of the system
  • 6.
    REQUIREMENTS ď‚§Hardware interface Consist ofthe tools to be used in controlling the bin 1. Mobile device for tracking and creation of part 2. Alarm signal for sending information 3. Network device for receiving signals 4. Wireless device for communication between the bin and the administrator's as well as the users 5. A camera would be used to locate a position of the bin and also serve as a CCTV
  • 7.
    INTERFACE Software interface • Thisinclude the embedded application that will used in supporting the various functions of the system • A GPS for detecting the location or direction • A Web Server and Data base at the server side Telecommunication, like a service providers
  • 8.
    SPECIFIC REQUIREMENT • Usershould dispose the refuse accordingly, either solid or liquid • The administrator should locate the place and empty the bin • Some of the refuse should be recycled • Need for quick response from the system for evacuation
  • 9.
    DESIGN CONSTRAINT'S • Thesystem must be designed to allow the usability by the users and the municipal officials • The system should respond when ever a bin is full for evacuation • System must be developed for easy use by both the user and the officials
  • 10.
    SOFTWARE SYSTEM ATTRIBUTES Thesystem should be able to: ď‚§Reliability: Error free operation ď‚§Availability: Should be available all the time ď‚§Security: Should be secured ď‚§Safety requirement: Their should be back up to avoid loss of data ď‚§Maintainability: The designer should be able to maintain and upgrade the system
  • 11.
    SYSTEM ARCHITECTURE Recycle Bin Mobiledevice Network Administrator (Server)
  • 12.
    PROJECT MANAGEMENT PLANNING CostAnalysis • We identify all the cost and benefits of carrying out the project and operating the delivered application, • Expressing these cost and benefits in common units • The development cost include salary and other employment cost of the staff involved. • Setup cost for putting the project into use , it include any hardware and ancillary equipment
  • 13.
    COST-BENEFIT EVALUATION • NetProfit: Difference between the total project and the project cash flow • Pay Back: the time taken to pay back the initial investment on the project • Return on investment: Net profitability • Net present value: profitability Injection and timings • Internal rate of return: Profit of percentage and interest
  • 14.
    RISK ANALYSIS The followingissues are very rare and will result in system or project failure • Poor internet network or low speed • Lack of proper maintenance • Electricity cut out • Protection from theft and natural disaster
  • 15.
    CONCLUSION In brief wediscussed the details requirement analysis and specification based on the need of the customer • From the specification given by the user we try to develop the basic planning management of the project. • Other concern issues and analysis will be further discuss between various stakeholders as the project continue
  • 16.