Archive for the ‘Technology/Programming’ Category

Table of Contents
Description 1.0 Introduction 1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms, and Abbreviations
1.4 References
1.5 Technologies to be used.
1.6 Overview
2.0 Overall Description
2.1 Product Perspective
2.2 Software Interface
2.3 Hardware Interface
2.4 Product Function
2.5 User Characteristics
2.6 Constraints
2.7 Architecture Design
2.8 Use Case Model Description
2.9 Class Diagram
2.10 Sequence Diagrams
2.11 Database Design
2.11.1 ER Diagram .
2.11.2 Data Dictionary.
2.12 Assumptions and Dependencies
3.0 Specific Requirements
3.1 Use Case Reports
3.2 Supplementary Requirements

Software Requirements Specification
1.0 Introduction:
This document contains specific requirements of our project Work to worker -services to the unorganized sector. Our project is a web based solution to solve the problem of the unorganized sector such as masons, carpenters, gardener etc. It is an approach to reduce unemployment and also make finding right people for the right job much more easier. Objective of this system is to provide work to the workers and solution is focused on the unorganized sector . In this web based innovative solution, the worker registers himself for a particular skill/skills that he is good at, the profile of the worker is visible to all the general public who look to avail services of some kind, so using this system general public or organized sector (includes contractors) can select the worker as per their need. Now as the general public selects a particular worker for some work, our system sends notification to the worker in concern about the work and the customer details like his address and name. The general public /contractors can give feedback about the worker in the fields of his dedication, behavior, habits etc ,through the system, to ensure better services every time.

1.1 Purpose: The purpose of this SRS is to define the overall functionality of our project . It specifies all the requirement parameters needed to implement our project. The basic purpose of our project is to help the unorganized sector in getting work. They register for a particular skill or skills and later receive work updates. Further, this project also helps general public and organized sector (contractors) in getting various workers of unorganized sector at one place. It provides general public and organized sector (contractors) with choice of workers. This project also focuses on providing worker the necessary information regarding their rights, governmental scheme , health care ,etc.

1.2 Scope: Work to Worker is a Web-based solution through which worker (s) registered them selves for a specific skill. Using this system general public or organized sector user can select the worker(s) as per their need. This Online System that is to be developed provides the members(workers) with jobs information(work), online applying for jobs and many other facilities. The work for worker System is supposed to have the following features.
** Administration Panel:
* The job board is highly configurable and there are many possibilities for running the job board. The administration panel consists of a set of web pages where they can:
* Approve / Disapprove / Edit / Delete job(work) postings.
* Approve / Disapprove / Edit accounts with the click of a button.
* View / Edit / Delete resumes.
* View/Edit/Delete Emails.
* View/Edit/Delete event notifications.
* Can take action according to the reports by registered members of the website.
* Live statistics.
* Advanced content management system

** Job Seeker’s Area:
* Jobs seekers(workers) can register.
* They manage their Job Alerts.
* They can also manage their work calendars and service charges.
* Job seekers can manage other things associated with their accounts .
* Workers can further search for work from specific locality.

** Customer’s Area:
* Agencies can sign-up and browse job seekers (workers).
* Manage their advertisements (job postings).
* Additionally, job seekers can submit their profile and manage other things associated with their account.
* Provide feedback about work and workers

1.3 Definitions, Acronyms, and Abbreviations:
• HTML (Hyper Text Markup Language): It is used to create static web pages.
• JSP (Java Server Pages): It is used to create dynamic web content.
• J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java platform, which is used for developing and running distributed java applications.
• WASCE (WebSphere Application Server Community Edition): It is an application server that runs and supports the J2EE and the web service applications.
• WSAD (WebSphere Studio Application Developer ): It is a designer toolkit which is designed to develop more complex projects by providing a complete dynamic web service.
• DB2 (IBM Database 2): It is a database management system that provides a flexible and efficient database platform to raise a strong “on demand” business applications.
• HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server
• XML (Extensible Markup Language): It is a markup language that was designed to transport and store data. • Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create dynamic web pages
• Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing, interoperability, user-centered design and collaboration on the World Wide Web.

1.4 References:
Books:
1) Database system concepts (6th ed.) McGraw-Hill publication by avi silberschatz, henry f .korth, s sudarshan
2) Use case modeling by Kurt Bittner.
3) Java in a nutshell by David Flangan.
4) O‟ REILY‟s software development
5) IBM Red Books.

Web resources:
http://www.ibm.com/developerworks
http://www.google.com
1.5 Technologies to be used:
• J2EE: (Servlet, JSP, JAXP, Java Beans) Application
architecture.
• JAVA: Application architecture.
• WASCE: (WebSphere Application Server Community Edition) Web Server
• DB2: IBM Database.
• Ajax: Asynchronous Java Script and XML.
• XML: Extension Markup Language.
• Web 2.0: RSS Feed 2.0.
• RAD 7.0: Development tool.
• Localization: 3 Languages – Hindi, Kannada, and English

1.6 Overview: The SRS include two sections, namely: -I- Overall Description: This section will describe major components of the system, interconnections, and external interfaces. -I- Specific Requirements: This section will describe the functions of actors, their roles in the system and the constraints faced by the system.

2.0 Overall Description:
2.1 Product Perspective: The product is not a follow up to any other product and is a self contained innovation of IBM. It is built using all IBM technologies. The main features of our product are:

1. Secure registration of users (workers) and customers (general public/ organized sector user).

2. Workers are classified into various groups.

3. State can be modified by feedback system .

4. Profile management facilities for both laborers and customers.

5. Chat/mail/SMS services (in English and Hindi).

6. Customer can make community for reference purpose etc.

7. Customers can give their feedback for workers who worked for them.

8. Workers can view details of the project in particular location

2.2 Software Interface:
* Front End Client:
HTML, DHTML, JavaScript, Servlets & JSP
* Web Server:
WASCE (WebSphere Application Server Community Edition) WebServer.
* Data Base Server:
IBM DB2
* Back End:
Web 2.0, RSS Feeds 2.0

2.3 Hardware Interface:
** Client Side:
* Desirable:
o 1GHz processor, 256MB RAM, any OS
** Standard:
o A web application can function across various platforms on minimum configurations required to run a web application which all contemporary workstation provide

** Server Side:
* Minimum requirements for installing IBM DB2:
o All Intel & AMD processors capable of running 32-bit or 64-bit OS
o 512 MB RAM and an additional ram per 5 client connections
o 3GB of Hard Disk space
* Minimum requirements for installing Web Sphere:
o All Intel & AMD processors capable of running 32-bit or 64-bit OS
o 375 MHz processor
o 2 GB RAM
o 6 GB of Hard Disk space

2.4 Product Functions:. Functional Requirements:
** Our website provides a platform for workers and costumers to interact on work basis It gives unorganized sector a organized feel and look.
** Workers are classified on the basis of their skills
** All the users will be able to customize their profile as per their choice with the help of manage profile settings option.
** Worker can maintain the work calendar.
** Worker can view information of project (organized sector) in particular location.
** Worker is ranked (feedback) by customer after every work .His ranking specifies his skill level, so a quality check.
** Awareness is provided to workers regarding their rights, governmental schemes ,health care(AIDS, STD, communicable diseases, etc) .
** Organized sector (contractors) can form /register his worker groups

Non-Functional Requirements:-
* Secure access of confidential data (user‟s details).
* 24 X 7 availability
* Better component design to get better performance at peak time
* Flexible service based architecture for future extension

2.5 User Characteristics: Following are various users of our website:

* Administrator:- Administrator can perform any the task of the site .He can delete account on feedback basis ,organize events ,manage advertisements. In short all sort of updation , maintenance is done by the admin.
* Worker:- This user is center of attention of our site .He registers for a particular skill/skills and later get work information via notification .His work calendar is maintained and he is rated(fedback) after every job .He can also join a contractor‟s group .He is also helped by site by providing awareness regarding his rights, health, etc.
* General public:-They are job providers .They register and later search workers as per their job requirements .They are supposed to have small work needs. After the work is complete they provide feedback which helps in quality check of worker.
* Contractor:- He is supposed to be the bulk work provider. He can form/register his own worker group as per his needs. He also provides feedback.
2.6 Constraints:
* The user login name should be unique and should contain more than 8 characters.
* Login name and password is used for the registered users .There is no facility for guest.
* Password should be a combination of letter, digits, symbols with at least 8 characters .
* Worker must have access to the internet and know the basics of internet, like registering for a portal.
* Worker has to constantly upgrade his work calendar .
* Workers wages are fixed according to his standards. No bargain.

2.12 Assumptions and Dependencies:-
* We are assuming that the unorganized sector has access to web and know the basics of
internet, like registering for a portal.
* Worker fills his work calendar properly.
* A user should have a valid identity proof

3. Specific Requirements:
3.1 Use Case Reports:
REGISTRATION will contain the attributes like (username, password, usertype).Usertype choose by the visitor will describe the visitors profile. Visitors profile can be Admin, Contractor, General public, Worker from unorganized sector. On registration he will be directed to the profile info page where he will have to fill all the details.
* For every usertype chosen, information to be filled has attributes (name, gender, age, address, e-mail, phone no, id-proof, etc).
* If usertype chosen represents WORKER then directed page will come with the information to be filled by worker correctly. Worker details will have attributes (worker id, education, Rating, comments, preferred work location, skills, experience, work calendar, charges).
* If usertype chosen represents CONTRACTOR then directed page will come with the information to be filled by customer correctly.
* If usertype chosen represents GENERAL PUBLIC then directed page will come with the information to be filled by general public correctly. General Public details will have attributes (work id, work detail, work location, work time, work title, customer id, and confirmation).

3.2 Supplementary Requirements:
1) Few open source software used for statistical purpose.
2) Macromedia player should be pre-installed.
3) 24 x 7 availability of server system.
4) Backup facilities should be available with enough space.
5) Provide the session maintaining capability.
6) The server has to provide a good performance during the peak hour.

Advertisements

The last few years have seen a very swift rise of the popularity of smartphones. So much so, that is almost impossible to imagine life without them. But are they really perfect?

Android
Thanks to the customizations, free applications and variety of handsets it is available on, Android is steadily on the rise. Google claims 3,00,000 Android phones are activated on a daily basis, globally. But Android too has its own problems.

Gaming
The Android platform has still not captured the imagination of game developers. Probably because of the non-standardised hardware, gaming developers find it difficult to make the games run on every phone. This is where iPhone has a definite advantage.

Manufacturer Customisation
Google helps handset makers to put a skin over the OS. Example-HTC Sense. Almost every manufacturer is doing this. Though this is designed to make the phone have additional functionality, in most cases this has an opposite effect. Software tends to crash, memory usage goes up and battery life goes down.

Poor Task Management.
Android phones have never been good at handling apps which open in the background or do not close fully upon exit.. The lack of built in task manager created this problem which was solved by many third party apps.However most people do not use them and end up sacrificing battery life and performance.

Too many screen resolutions make it tough for app makers
Varied screen resolutions for different devices(add tablets to that variety)and the app developers have a major task on their hands to make the apps look proper on every single screen. Some apps end up looking weird on some devices.

Bad battery life
The apps are to blame for this. They have a habit of being bullish when getting online updates.

Symbain^3
Symbian remained the way it was for a long time, a bit too long, according to some people. Symbain^3 arrived in 2010, with Nokia N8 Smartphone. A lot of hopes rested on the new OS. However Symbain^3 evoked a variety of responses-happiness,relief,disappointment,anger, resentment and even aggression.

Everything’s still the same?
The interface on the N8 looks lot like the one on the much older N97, which says lot about the new OS. Not much has been done to make it slicker, or even look a bit different.

Feels clunky with too many menu options
There are still too many menus to manage the options and settings in both the OS and within apps.

Handicapped Widgets
Widget size on the three home screens is limited, which not only reduces functionality, but also makes certain widgets a pain to use. Imagine catching up on your twitter timeline and only being able to read one tweet with every scroll.

Ovi Store is sparse
Despite Nokia’s best effort, the Ovi Store is far behind Apple’s App Store and Android Market in terms of the sheer number and variety of apps available.

Even Nokia may drop Symbain
There is a strong suspicion that Nokia will judge the response to the Meego based devices and then decide if it has to completely drop Symbian.

Without doubt Symbian’s glory has faded considerably, but the fact remains they were the first to introduce most of us to the concept of smart phones and apps. Most of those very apps still stand out in the crowd. This list is a mixture of old classics with new hits, just in the right proportion for people with every flavour of Symbian, old or new, to have a go.

1.Opera Mini
Opera Mini steals the cake in this list more deservingly than anywhere else. It was and still is the ‘go to browser’ for most Symbian users out there. It routes websites through Opera’s servers, and the compressed data is a boon, especially with 2G speeds that most of us are subjected to.

2.Nimbuzz
IM, VoIP,Twitter, Facebook, Myspace. Use this one app to connect you to the world. The easy to manage tabbed interface unclutters your social life, all under the roof of this one app.

3.UC Browser
With more than 400million downloads and 300million users all over the world by september this year, UC Browser, like Opera Mini, does data compression and more. Built-in file manager and an ultra cute logo are a major up.

4.Skype
One of the best VoIP clients on the horizon, legendary stability and across-platform user base of more than 800millions users.

5.Fring
A VoIP and video chat service par excellence, this one has become favourite because it allows you to use text/voice/video chat in all your favourite services like google, yahoo, ICQ etc.

6.Core Player
Core Player was to Symbian what VLC player is to PCs.

7.Xplore
Xplore provided Nokia users what apple users struggled to get till yesterday. An explorer that provides uninhibited access to the file system plus much more, AV playback, folder copying or transferring you an entire drive over Bluetooth.

8. SmartMovie
SmartMovie, like Xplore above, had a talent centuries back,(Ok, make that 8-10 years) that most mobiles are learning today: Playing AVI files flawlessly. The bundled converter makes the whole process absolutely seemless.

9.Snaptu
Snaptu can best be called as service aggregator. From facebook and twitter, to various news services and blogs, it fetches all content and brings it in easy to eye way. Plus you can click and upload pics using this app at a go.

10.Ovi Maps
Nokia is one of the few companies that actually provides what we demand from every company: Free turn-by-turn guided navigation software. This one is here for staying.

11.Shazam
Shazam identifies music by scanning small snippets from songs and comparing them against a database. With twitter and Facebook sharing thrown in to solve the sharing obsession, this one is a crowd favourite.

12.Handy Taskman
Symbian always had a built-in Task Manager, but Handy Taskman was still loved. While it shows system resources, it mainly loved for its ability to kill the tasks taht phone couldn’t.

13.Symtorrent
Symtorrent brought torrents to Symbian. Till date it is the only torrent client on Symbian side.

14.Socially
Access Facebook,Twitter,LinkedIn & Foursquare from one place.

15.Quick Office
Quick Office has been bundled with Symbian phones for a very long time now and being free doesn’t make it any less important. A light and responsive suite for viewing and editing your documents on the go. A version is now available for other mobile operating systems as well.

If you know any better Symbain apps, do feel free to share with me at http://www.amaanbali@gmail.com

Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 1
The Code Warriors Work for workers : Services to the unorganized sector Software Requirements Specification Version 1.0 Team Guide: Mr. Jt Pal Members:
1. Amandeep Singh
2. Muzamil Tariq
3. Toyab Ahmed Shabir
4. Sushant Bhat
College Name: MODEL INSTITUTE OF ENGINEERING AND TECHNOLOGY (MIET) Department: Computer Science and Engineering State: Jammu and Kashmir
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 2
Revision History
Date
Version
Description
Author
<date>
1.0
Synopsis
The Code Warriors
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 3
Table of Contents
Description 1.0 Introduction 1.1 Purpose 1.2 Scope 1.3 Definition, Acronyms, and Abbreviations 1.4 References 1.5 Technologies to be used 1.6 Overview
Page No. 2.0 Overall Description 2.1 Product Perspective 2.2 Software Interface 2.3 Hardware Interface 2.4 Product Function 2.5 User Characteristics 2.6 Constraints 2.7 Architecture Design
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 4
2.8 Use Case Model Description 2.9 Class Diagram ………………………………………………………….. Sequence Diagrams……………………………………………………… 2.10 Database Design ………………………………………………………….. 2.11.1 ER Diagram ……………………………………………………… 2.11.2 Schema ……………………………………………………………. 2.12 Assumptions and Dependencies 3.0 Specific Requirements 3.1 Use Case Reports 3.2 Supplementary Requirements
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 5
Software Requirements Specification
1.0 Introduction:
This document contains specific requirements of our project Work to worker -services to the unorganized sector. Our project is a web based solution to solve the problem of the unorganized sector such as masons, carpenters, gardener etc. It is an approach to reduce unemployment and also make finding right people for the right job much more easier. Objective of this system is to provide work to the workers and solution is focused on the unorganized sector which. In this web based innovative solution, the worker registers himself for a particular skill that he is good at, the profile of the worker is visible to all the general public who look to avail services of some kind, so using this system general public or organized sector (includes contractors) can select the worker as per their need. At the time of the worker selection he can view the skill references given by those who have availed his services before. Now as the general public selects a particular worker for some work, our system sends SMS or email to the worker in concern about the work and the customer details like his address and name. The worker confirms either through the phone or an SMS about his availability for the job, if the worker is unavailable our system shows him the days on which the worker can be available and also presents him with other choice of the worker for the same job. The worker is rated in the fields of his dedication, behavior, habits etc ,through the system, to ensure better services every time. 1.1 Purpose: The purpose of this SRS is to define the overall functionality of our project . It specifies all the requirement parameters needed to implement our project. The basic purpose of our project is to help the unorganized sector in getting work. They register for a particular skill or skills and later receive SMS or emails from the site regarding available job. Further, this project also helps general public and organized sector (contractors) in getting various workers of unorganized sector at one place. It provides general public and organized sector (contractors) with choice of workers. This project also focuses on providing worker the necessary information regarding their rights, governmental scheme , health care ,etc.
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 6
1.2 Scope: Work to Worker is a Web-based solution through which worker (s) registered them selves for a specific skill. Using this system general public or organized sector user can select the worker(s) as per their need. This Online System that is to be developed provides the members(workers) with jobs information(work), online applying for jobs and many other facilities. The work for worker System is supposed to have the following features.
 Administration Panel:
 The job board is highly configurable and there are many possibilities for running the job board. The administration panel consists of a set of web pages where they can:
 Approve / Disapprove / Edit / Delete job(work) postings.
 Approve / Disapprove / Edit accounts with the click of a button.
 View / Edit / Delete resumes.
 View/Edit/Delete Emails.
Work for workers : Services to the unorganized sector
Version 1.0
Software Requirements Specification
15-12-2010
The Code Warriors
 View/Edit/Delete event notifications.
 Can take action according to the reports by registered members of the website.
 Live statistics.
 Advanced content management system.
 Job Seeker’s Area:
 Jobs seekers(workers) can sign-up and submit their resume
 They manage their Job Alerts.
 They can also manage their work calendars and service charges.
 Job seekers can manage other things associated with their accounts like uploading their profile photos and sharing their work experiences with other fellow members.
 Workers can further search for work from specific locality.
 Customer’s Area:
 Agencies can sign-up and browse job seeker’s (workers) resumes.
 Manage their advertisements (job postings).
 Additionally, job seekers can submit their profile and manage other things
 associated with their account.
 Provide feedback and rate workers for their skills.
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 7
1.3 Definitions, Acronyms, and Abbreviations: • HTML (Hyper Text Markup Language): It is used to create static web pages. • JSP (Java Server Pages): It is used to create dynamic web content. • J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java platform, which is used for developing and running distributed java applications. • WASCE (WebSphere Application Server Community Edition): It is an application server that runs and supports the J2EE and the web service applications. • WSAD (WebSphere Studio Application Developer ): It is a designer toolkit which is designed to develop more complex projects by providing a complete dynamic web service. • DB2 (IBM Database 2): It is a database management system that provides a flexible and efficient database platform to raise a strong “on demand” business applications.
• HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 8
• XML (Extensible Markup Language): It is a markup language that was designed to transport and store data. • Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create dynamic web pages. • Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing, interoperability, user-centered design and collaboration on the World Wide Web. 1.4 References: < Enter the reference taken for project development >
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 9
1.5 Technologies to be used:
• J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture. • JAVA: Application architecture. • WASCE: (WebSphere Application Server Community Edition) Web Server • DB2: IBM Database. • Ajax: Asynchronous Java Script and XML. • XML: Extension Markup Language. Web 2.0: RSS Feed 2.0. • RAD 7.0: Development tool.
• Localization: 3 Languages – Hindi, Kannada, and English
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 10
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 11
1.6 Overview: The SRS include two sections, namely: -I- Overall Description: This section will describe major components of the system, interconnections, and external interfaces. -I- Specific Requirements: This section will describe the functions of actors, their roles in the system and the constraints faced by the system. 2.0 Overall Description: 2.1 Product Perspective: The product is not a follow up to any other product and is a self contained innovation of IBM. It is built using all IBM technologies. A general view of the diagram showing how the main components of this software are related is shown as:- The main features of our product are:
1. Secure registration of users (workers) and customers (general public/ organized sector user) with SMS.
2. Workers are classified into various groups & categorized namely aware, skilled, semi skilled, etc.
3. State can be modified by feedback system & workers rating evaluation algorithms.
4. Profile management facilities for both laborers and customers.
5. Chat/mail/SMS services (in English and Hindi).
6. Customer can make community for reference purpose etc.
7. Customers can give their feedback for workers who worked for them.
8. Workers can view details of the project in particular location.
2.2 Software Interface:
 Front End Client:
HTML, DHTML, JavaScript, Servlets & JSP
 Web Server:
WASCE (WebSphere Application Server Community Edition) WebServer.
 Data Base Server:
IBM DB2
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 12
 Back End:
Web 2.0, RSS Feeds 2.0
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 13
2.3 Hardware Interface:
 Client Side:
 Desirable:
o 1GHz processor, 256MB RAM, any OS
 Standard:
o A web application can function across various platforms on minimum configurations required to run a web application which all contemporary workstation provide
 Server Side:
 Minimum requirements for installing IBM DB2:
o All Intel & AMD processors capable of running 32-bit or 64-bit OS
o 512 MB RAM and an additional ram per 5 client connections
o 3GB of Hard Disk space
 Minimum requirements for installing Web Sphere:
o All Intel & AMD processors capable of running 32-bit or 64-bit OS
o 375 MHz processor
o 2 GB RAM
o 6 GB of Hard Disk space
2.4 Product Functions:. Functional Requirements:
 Our website provides a platform for workers and costumers to interact on work basis It gives unorganized sector a organized feel and look.
 Workers are classified on the basis of their skills
 Multilingual chat and SMS service.
 All the users will be able to customize their profile as per their choice with the help of change account settings option.
 Worker can maintain the work calendar.
 Worker can view details information project (organized sector) in particular location.
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 14
 Worker is ranked by customer after every work .His ranking specifies his skill level, so a quality check.
 Awareness is provided to workers regarding their rights, governmental schemes ,health care(AIDS, STD, communicable diseases, etc) .
 Local language support is provided to workers / customers.
 Organized sector (contractors) can form /register his worker groups .
 The authentication process done by the admin is using valid documents .
 Administrator generates various reports graphs on strategic data.
Non-Functional Requirements:-
 Secure access of confidential data (user‟s details).
 24 X 7 availability
 Better component design to get better performance at peak time
 Flexible service based architecture for future extension
2.5 User Characteristics: Following are various users of our website:
 Administrator:- Administrator can perform any the task of the site .He can delete account on feedback basis ,generate reports ,organize events ,manage advertisements. In short all sort of updation , maintenance is done by the admin.
 Worker:- This user is center of attention of our site .He registers for a particular skill/skills and later get work information via SMS/email .His work calendar is maintained and he is rated after every job .He can also join a contractor‟s group .He is also helped by site by providing awareness regarding his rights, health, etc.
 General public:-They are job providers .They register and later search workers as per their job requirements .They are supposed to have small work needs. After the work is complete they provide feedback and rate the worker which helps in quality check of worker.
 Contractor:- He is supposed to be the bulk work provider. He can form/register his own worker group as per his needs. He also provides feedback and rating.
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 15
2.6 Constraints:
 The user login name should be unique and should contain more than 5 characters.
 Login name and password is used for the registered users .There is no facility for guest.
 Password should be a combination of letter, digits, symbols with at least 6 character having 1 symbol .
 Worker must have access to the internet and know the basics of internet, like registering for a portal.
 Worker has to constantly upgrade his work calendar through SMS or using website.
 Worker has to follow standard text format for reply via SMS.
 Workers wages are fixed according to his standards. No bargain.
2.7 Architecture Design:
Work for workers : Services to the unorganized sector
Version 1.0
Software Requirements Specification
15-12-2010
The Code Warriors
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 16
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 17
2.8 Use Case Diagram :
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 18
generates report(10)
orgainses events(6)
selects worker(9)
submits work detail(8)
gives feedback(7)
admin-1
contractor-4
general public-3
register(2)
user login(1)
manages profile(3)
chat/communication(4)
manages work calender(5)
worker-2
Multilevel use case diagram
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 19
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 20
selects worker(9)
submits work detail(8)
gives feedback(7)
contractor-4
general public-3
chat/communication(4)
Single level use case diagram
2.9 Class Diagram:
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 21
Package com.wtw.servlet
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 22
Package com.wtw.util
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 23
Work for workers : Services to the unorganized sector
Version 1.0
Software Requirements Specification
15-12-2010
The Code Warriors
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 24
Package com.wtw.bean
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 25
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 26
Package com.wtw.manager 2.10 Sequence Diagrams:
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 27
Sequence diagram1
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 28
Work for workers : Services to the unorganized sector
Version 1.0
Software Requirements Specification
15-12-2010
The Code Warriors
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 29
Sequence diagram2
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 30
Sequence diagram3 2.10.1 Database Design: 2.10.2 ER Diagram:
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 31
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 32
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 33
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 34
DATA DICTIONARY:- 1. USER TABLE
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 35
KEY
NAME
DATA TYPE
LENGTH
NULLABLE
PK
USER_ID
VARCHAR
10
NO
USER_NAME
VARCHAR
15
N0
PASSWORD
VARCHAR
15
NO
USER_TYPE
VARCHAR
15
NO
FIRST_NAME
VARCHAR
20
NO
MIDDLE_NAME
VARCHAR
20
NO
LAST_NAME
VARCHAR
20
NO
GENDER
VARCHAR
6
NO
D.O.B
DATE
NO
ABOUT_ME
BLOB
512KB
YES
CV
BLOB
512KB
YES
ADDRESS
VARCHAR
100
NO
CITY
VARCHAR
25
NO
STATE
VARCHAR
35
NO
EMAIL
VARCHAR
35
NO
PHONE NO.
INTEGER
NO
ID_PROOF_TYPE
VARCHAR
80
NO
ID_PROOF_PATH
VARCHAR
80
NO
LANGUAGES
XML
YES
ADV_STATUS
CHAR
1
NO
ONLINE_STATUS
CHAR
1
NO
HINT_QUEST
VARCHAR
80
NO
HINT_ANS
VARCHAR
80
NO
PIC_PATH
VARCHAR
200
YES
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 36
2. WORK
KEY
NAME
DATA TYPE
LENGTH
NULLABLE
PK
WORK_ID
VARCHAR
10
NO
FK
CUSTOMER_ID
VARCHAR
10
NO
FK
WORKER_ID
VARCHAR
10
NO
GROUP_ID
VARCHAR
10
NO
WORK_TYPE
VARCHAR
20
NO
WORK_LOC
VARCHAR
50
NO
WORK_LOC_CITY
VARCHAR
25
NO
WORK_LOC_STATE
VARCHAR
30
NO
WORK_DETAIL
BLOB
256KB
NO
WORK_STATUS
INTEGER
NO
COMMENTS
XML
NULLABLE
EST_TIME
INTEGER
NO
START_TIME
TIMESTAMP
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 37
FINISH_TIME
TIMESTAMP
3.WORKER
KEY
NAME
DATA TYPE
LENGTH
NULLABLE
FK
WORKER_ID
VARCHAR
10
NO
PREFFERD_LOC
XML
NULLABLE
QUALIFICATIONS
XML
NO
SKILLS
XML
NO
WORK_CAL
XML
NO
CHARGES_DAILY
DECIMAL
5,2
NO
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 38
CHARGES_HOURLY
DECIMAL
5,2
NO
GROUP_ID
VARCHAR
10
YES
R_SKILLS
INTEGER
NO
R_CHARGES
INTEGER
NO
R_TIME
INTEGER
NO
R_BEHAVIOUR
INTEGER
NO
4. CONTRACTOR TABLE
KEY
NAME
DATA TYPE
LENGTH
NULLABLE
FK
CONTRACTOR_ID
VARCHAR
10
NO
COMPANY_NAME
VARCHAR
50
NO
COMPANY_LOC
VARCHAR
50
NO
LICENSE
VARCHAR
50
NO
GROUP_ID
XML
NULLABLE
5. CHAT TABLE
KEY
NAME
DATA TYPE
LENGHTH
NULLABLE
PK
CHAT_ID
VARCHAR
10
NO
FK
SENDER_ID
VARCHAR
10
NO
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 39
FK
RECEIVER_ID
VARCHAR
10
NO
TIME
TIMESTAMP
NO
MSG
XML
NO
6. EVENTS TABLE
KEY
NAME
DATA TYPE
LENGTH
NULLABLE
PK
EVENT_ID
VARCHAR
10
NO
EVENT_ORG
VARCHAR
80
NO
DATE
DATE
NO
NAME
VARCHAR
40
NO
DETAILS
BLOB
512KB
NO
LOCATION
VARCHAR
40
NO
CITY
VARCHAR
40
NO
STATE
VARCHAR
40
NO
OTHERS
VARCHAR
500
NO
2.11 Assumptions and Dependencies:-
 We are assuming that the unorganized sector has access to web and know the basics of internet, like registering for a portal.
 Worker fills his work calendar properly.
 A user should have a valid identity proof .
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 40
3. Specific Requirements: 3.1 Use Case Reports: REGISTRATION will contain the attributes like (username, password, user ID, ID).ID choose by the visitor will describe the visitors profile. Visitors profile can be Admin, Contractor, General public, Worker from unorganized sector. On registration he will be directed to the profile info page where he will have to fill all the details.
 For every ID chosen, information to be filled has attributes (name, gender, age, address, e-mail, phone no, id-proof, user-id).
 If ID chosen represents WORKER then directed page will come with the information to be filled by worker correctly. Worker details will have attributes (worker id, education, Rating, comments, preferred work location, skills, experience, work calendar, charges).
 If ID chosen represents CONTRACTOR then directed page will come with the information to be filled by customer correctly. Contractor details will have attributes (Contractor id, Group id).this contractor id will be extended to the an extra profile info containing the information related to the GROUP with attributes (group id, worker id)
 If ID chosen represents GENERAL PUBLIC then directed page will come with the information to be filled by general public correctly. General Public details will have attributes (work id, work detail, work location, work time, work title, customer id, and confirmation).
Use Case narratives
Primary Actor
Use Cases
Worker
Login, Register, Manage profile, Chat/communication Maintain work calendar. logout
Administrator
Manages profiles, organizes events, generates reports Select worker
General public
Login, register, profile management, chat/communication, submit work detail, Feedback logout
Contractor
Login, register, manage profile, chat/communication, submit work detail, feedback
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 41
Use case reports:
1. Use case for ‘login’
Use Case ID:
1
Use Case Name:
login
Created By:
The code warriors
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
General public Worker contractor
Description:
As only registered users can use the system, every user has to provide his/her login information – login name and password – in order to use the system.
Trigger:
The user is prompted to enter his username and id for successful login.
Preconditions:
User requests to login to the system.
Postconditions:
The user is logged into the system and may use his type of functionality
Normal Flow:
1.The user is prompted to enter his password and username 2. after clicking submit, the user is logged in if the password and username ombination is correct.
Alternative Flows:
If the combination is not correct, the user is directed back to the same page, prompting him to enter the values correctly.
Exceptions:
No exceptions
Includes:
Priority:
High
Frequency of Use:
Used every time a user logs in. <infinite>
Business Rules:
Follows encryption at login level
Special Requirements:
No special requirements.
Assumptions:
User is assumed to login with valid username and password.
Notes and Issues:
Use case report for: register
Use Case ID:
2
Use Case Name:
Register
Created By:
Code warriors
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
Worker, general public, contractor
Description:
The user shall be able to create his profile. The user has to enter his personal information, login name, and password and all the information required for a valid profile..
Trigger:
The user is directed to the registration page as soon as he logs in successfully.
Preconditions:
The request is sent after completion of log in to create a profile.
Postconditions:
The user is directed to his profile page where he enters his required information.
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 42
Normal Flow:
The user enters the following information to his profile. The user enters his username and password. 1.User enters his personal details like his full name, address, e mail, date of birth. 2. The user uploads his profile picture. 3. The worker makes his work calendar. 4. The workers enroll themselves in the groups.
Alternative Flows:
1.If the user name already exists, the user is directed back to the page which prompts him to enter his username and password again. 2. The fields marked with „mandatory‟, if left unfilled directs the user back to the registration page.
Exceptions:
Registration is successful only if the user enters the information that is mandatory to be added in his profile.
Includes:
Login function.
Priority:
High
Frequency of Use:
Every time a user makes an account, this use case is used.
Business Rules:
Special Requirements:
Assumptions:
Notes and Issues:
Notes and Issues:
Use case report: manage profile
Use Case ID:
3
Use Case Name:
Manage profile
Created By:
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
General public Workers Contractor Administrator
Description:
Manage profile includes entering all the required information for making a profile. The description for various users is as: Workers
1. Workers enter their name, age, address, email address, phone number.
2. Worker maintains his work calendar.
3. Worker seeks work and confirms work requests.
4. Worker can communicate with other workers using the chat feature using his profile.
5. Worker uploads his photo and can share information using messages.
General public/contractor:
1. General public user enters his valid information like name, email, address, phone number.
2. Uploads profile photograph
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 43
3. Defines his work need and number of workers needed.
4. Provides valid feedback for the worker he availed.
Administrator
1. Administrator has the privilege to delete a profile thst is not valid or is in active.
2 Imports work calendar and decides which worker is free and accordingly assigns work.
2. Manages the feedback and ranking of the workers.
Trigger:
As soon as registration is complete the user is directed to his profile page where the information is added.
Preconditions:
All the fields required in registration must be complete.
Postconditions:
The services can be availed after completion of profile information.
Normal Flow:
All the fields marked with *mandatory should be filled. The user is directed to this profile page after successful completion of registration
Alternative Flows:
1.If all the fields are not submitted the user is directed back to profile page with a message that some fields are mandatory. 2. if al the data regarding the profile is added, the user is ready to avail the services
Exceptions:
No exceptions
Includes:
registration
Priority:
High
Frequency of Use:
Every time a user makes a profile, it is used. <<depends on number of users>>
Business Rules:
Special Requirements:
Assumptions:
Notes and Issues:
Notes and Issues:
Use case report: chat/ communication
Use Case ID:
4
Use Case Name:
Chat/communication
Created By:
“the code warriors”
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
Workers General public Contractor/builder
Description:
Chat/communication feature is used to make communication easy between worker, general public and contractor
Trigger:
Chat feature is enabled when user is online clicks on the availability option and makes it “available”
Preconditions:
The user must be logged in to use the feature of communication.
Postconditions:
As soon as user finishes his work and logs out of his profile, chat is disabled.
Normal Flow:
User logs in his profile and makes use of chat feature.
Alternative Flows:
If user is available he can chat and communicate with others.
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 44
Exceptions:
Some users may prefer to stay offline
Includes:
Profile
Priority:
Medium
Frequency of Use:
Depends on users
Business Rules:
Special Requirements:
Assumptions:
Notes and Issues:
Use case report: manage work calendar
Use Case ID:
5
Use Case Name:
Manage work calendar
Created By:
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
Workers Administrator
Description:
It includes managing the work calendar, ie the worker‟s availability on any given day. It includes all the working days and free days. Work calendar also includes the details of the work that worker did, like number of hours etc. Administrator: The admin selects the worker after inspecting his work schedule.
Trigger:
As soon as worker logs in his profile and gets a work request.
Preconditions:
The worker must be logged in. Worker should get a work request.
Postconditions:
Worker gets work on basis of his schedule.
Normal Flow:
Login>profile>work calendar
Exceptions:
No exceptions
Includes:
profile
Priority:
high
Frequency of Use:
Every time user logs in his profile for finding work<<<high>
Business Rules:
Special Requirements:
Assumptions:
Notes and Issues:
Notes and Issues:
Use case report: organize events
Use Case ID:
6
Use Case Name:
Organize events
Created By:
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
Administrator
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 45
Description:
The administrator organizes events such as training for the workers, etc.
Trigger:
Whenever an event is organized, this action is fired.
Preconditions:
There should be enough users for the system
Postconditions:
The event is stored on the home page
Normal Flow:
Administrator sends requests to the users for participation, the users acknowledge their willingness to participate using their profiles.
Alternative Flows:
If the event is cancelled, the users are directed back to their profiles and not the event page.
Exceptions:
Event may or may not occur
Includes:
Profiles
Priority:
Low
Frequency of Use:
Less frequent
Business Rules:
Special Requirements:
Assumptions:
Notes and Issues:
Use case report: feedback
Use Case ID:
7
Use Case Name:
Feedback
Created By:
Code warriors
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
General public Contractor/builder Administrator
Description:
General public The people who avail the services of the workers provide a valid feedback about the workers Contractor The contractors who avail the services of the workers will provide a feedback about them. Administrator Manages all the feedback from the general public and the contractor
Trigger:
General public and contractors provide feedback in their profiles After the completion of work.
Preconditions:
1.Work should have been completed and work Calander updatd by worker 2.users providing feedbacks should be loged in
Postconditions:
Feedback is generatred and users are directed back to their profile page
Normal Flow:
1.general public>profile>feedback 2.contractor>profile>feedback
Alternative Flows:
Exceptions:
Users may opt no to provide feedbacks
Includes:
profiles
Priority:
medium
Frequency of Use:
Frequent
Business Rules:
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 46
Special Requirements:
Assumptions:
Notes and Issues:
Use case reports: submit work details
Use Case ID:
8
Use Case Name:
Submit work details
Created By:
The Code warriors
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
1.General public 2.contractor/builder
Description:
Submits work detail of the work to be performed.details include 1.type of work 2.work location 3.no. of workers needed 4.time of work
Trigger:
When user logs in his profile and wants to avail services
Preconditions:
User must be logged in
Postconditions:
User gets confirmation message after availability of workers is confirmed by the system.
Normal Flow:
General public>login>profile>work specification>confirmation message contractor>login>profile>work specification>confirmation message
Alternative Flows:
Exceptions:
Includes:
Profiles
Priority:
<<high>>
Frequency of Use:
<<high>> every time user needs work, he uses this use case.
Business Rules:
Special Requirements:
Assumptions:
Notes and Issues:
Use case report: logout
Use Case ID:
9
Use Case Name:
logout
Created By:
Last Updated By:
Date Created:
15-12-2010
Date Last Updated:
24-12-2010
Actors:
Workers
Work For Workers: Services to unorganized sector Version 1.0
Work for workers : Services to the unorganized sector Version 1.0
Software Requirements Specification 15-12-2010
The Code Warriors
THE CODE WARRIORS Page 47
General public Contractor/builder
Description:
After the user ends working with the system, he logs out in order no one can use his profile.
Trigger:
As soon as user clicks on the logout button!!
Preconditions:
The user requests to log out from the system.
Postconditions:
The user is logged out from the system.
Normal Flow:
All settings are saved and user logs out.
Alternative Flows:
Exceptions:
Includes:
profiles
Priority:
<<high>>
Frequency of Use:
<<high>>
Business Rules:
Special Requirements:
Assumptions:
3.2 Supplementary Requirements: <Team Name>/ <College Name> Page 9

Types Of Bugs

Posted: February 1, 2011 in Technology/Programming

Jim gray in his popular presented some of the bugs which are named after some famous scientist names.

Bohrburgs :

Most of the bugs that we come across are reproducible, and are known as bohrbugs. They are named after niel bohr, who proposed a simple and easy to understand atomic model in 1913. In bohr’s modelthings like the path and the momentum of the electron in ana atom are predictable. Similarly bohrbugs are predictable-you can produce them if you run a software with similar conditions. For example when the program crashes with a null pointer access, it always crashes there for a given input; so ypou can easily reproduce it.

Heisenbugs:

All experienced programmers have faced situations where the bug that crashed the software just disappears when the software is restarted. No matter how much time and effort is spent trying to reproduce the problem, the bug eludes us. Such bugs were named as heisenbugs, after Werner Heisenberg, who is known for his ‘uncertainity principle’. According to his theory, it is not possible to accurately or certainly determine the position and velocity of an electron in an atom at a particular moment. When bugs change their behavior when you try to debug, probe or isolate, they are called as heisenbugs. It can happen for example, when you use uninitialized variables. When the program is run, it will access the variables that are uninitialized and hence result in a bug. However when you try to debug the program, the program must work just fine, because many de buggers initialize uninitialized variables to zero’s and so you might not hit the problem!!

Mandelbugs

When the cause of the bug is too complex to understand and the resulting bug appears too chaotic, it is called a mandelbug. These are named after benoit Mandelbrot, who is considered the father of fractal geometry(  fractals are complex, self similar structures). A bug in an operating system that depends on scheduling is an example of mandelbug.

Schrodenbug

Sometimes you look into the code, and find that it has a bug or a problem that should have never allowed it to work at the first place. When you try out the code, the bug promptly shows up, and the software fails!!!

Though it sounds very uncommon, such bugs do occur and are known as schrodinbugs. They are named after the scientist Erwin schrodinger, who proposed a theoretical ‘cat experiment’. In quantum physics,quantum particles like atoms could exist in two or more quantum states, but schrodinger suggested that in more classical objects like a cat which is made up of many atoms, existing in two states was impossible. He theorized about a scenario in which a cat a cat is kept in a sealed chamber, with a vial of poison ( attached to radioactive atom). If the atom decayed, the voil would be smashed and the poson would leak, killing the cat. But with chamber sealed there could be no way to know whether the cat is dead or alive. So till the chamber is opened, theoretically the cat would be in two states-dead or alive. In quantum physics this is called as superposition state, where the cat is both alive and dead.

Coming back to bugs, by merely observing the problem in the code, you change the outcome-either the software works or breaks. So these kind of bu