User talk:Jyoti1035

Tarzan Book store Automation System
Tarzan Book store Automation System Tarzan book store decided to introduce a automated system where its customer can search, reserve or buy books according to their needs. Tarzan Automation System maintains the list of books along with quantity. Administrator should be able to add books to the inventory. Administrator will add books with book name, author name, category (Java, Philosophy, Fiction, OS, self help etc.), price and quantity. Anybody can log on to the system to browse through the books available. It should have a facility to search books by category or author name or book name .Out of stock status needs to be displayed based on the quantity. If anybody decides to buy a book, he needs to give a customer id to do the transaction. If new customer, he needs to register with the system by giving his personal details that are name, age, sex, address and contact number. Customer should have a facility to buy more than one book at one click. Customer can either choose to buy a book or add it in his “my books” list. If he chooses to buy book/books, system needs to get the mode of payment (credit/debit card) and collect the card details. If customer chooses to add book/books to “my books”, the list of selected book need to be added to his “my books” list. Next time, when customer logs in, there should be an option to view “my books”. From there, option is needed to buy the book. Also, customer needs to have an option to see his previously ordered books with buy date. And the system should keep the reports of the entire sale done, in sorted order based on date specified. Deliverables 1. Use case, Sequence diagram and ERD. 2. Class Diagram 3. Unit Test Plan 4. Coding Incorporate the additional features in the case study 1. Scheduling the job using CRONTAB at 10:00 am daily. 2. Log files are to be archived for each run. The log files have to be renamed with the current run time stamp and moved to the archive folder. TCS Internal 3. Purge the Log files in the archive folder which are greater than one month. 4. The purging script for the database tables has to be maintained. Maintain 3 months of data in the tables (2 last months plus 1 current month). 5. Ensure the script is restart-able (driver script). Use Shell script as a driver for executing the loading, ftp, archiving, purging database and log archive and executing C++ code executables. 6. Use make feature to create the executable for the C++ code. 7. Use Oracle as the database instead of flat files.

code
BookUI { void getPayment {	int ino; vector bstlist; do {	try {		cout<<"how many books do you want to buy?"; cin>>ino; if(no==5001000||no<=0) {			throw(Exception e("number should be positive integer");		}		else		{			try			{				//int ibooks[ino];				for(int i=0; i>bookid;					cout<<"Enter quantity of book "<>quant;					if(bookid==5001000||bookid<=0||qunt==5001000||quant<=0)					{						throw(Exception e("bookid and quant must not be positve integer "));					}					else					{						bstruct bstr=(bookid,quant);						bstlist.push_back(bstr);					}				}				break;			}			catch(Exception e)			{				cout<<e.getmessage;				cout<<"Enter again: \n";			}		}	}	catch(Exception e)	{		cout<<e.getmessage<<"\n";		cout<<"Enter again: \n";	}	}while(1); } Bookcontroller { } booksystem { updateBookQuantity(int bookid[]) { d.updateBookQInDB(bookid[]); }

dbHandler {

updateBookQInDB(int bookid[]) { }

SRS
Software Requirements Specification

2.1 Introduction 2.1.1 Purpose : The main objective of this document is to illustrate the user requirments. The document gives the detailed description of the both functional and non functional requirements proposed by the client. The document is developed after a number of consultations with the client and considering the complete requirement specifications of the given Project. The final product of the team will be meeting the requirements of this document. 2.1.2 Document: Conventions The following are the list of conventions and acronyms used in this document and the project as well: Administrator: A login id representing a user with user administration privileges to the software • User: A general login id assigned to most users • Client: Intended users for the software • Layer: Represents a section of the project • User Interface Layer: The section of the assignment referring to what the user interacts with directly. • Application Logic Layer: The section of the assignment referring to the Web Server. This is where all computations are completed. • Data Storage Layer: The section of the assignment referring to where all data is recorded • Data flow diagram:It shows the dataflow between the entities. • Use Case: A broad level diagram of the project showing a basic overview • Boolean: A true/false notation • Unique Key: Used to differentiate entries in a database 2.1.3 Project Scope Project Title : Tarzan Book store Automation System Project Justification: This project is basically abook store automation ,where its customer can search, reserve or buy books according to their needs. Product Characteristics and Requirements : 1. Secured database. 2. User tracking. 3. Subject wise result view for teachers 4. Search feature. 5. Updating information. 6. Uploading/downloading of syllabus,previous year’s papers & other files. 7.Students can take up online test. Project Management Deliverables:

1. Use case, Sequence diagram and ERD. 2. Class Diagram 3. Unit Test Plan 4. Coding Project Success Criteria: Our main goal is to complete this project within allotted dead line. It is necessary to develop a method for capturing the benefits while the system is being developed, tested, and after it is rolled out. 2.1.4 References • IEEE recommended practice for Software Requirement Specifications – IEEE std 830-1933. 2.2 Overall Description 2.2.1 Product Perspective The proposed Department Management System which is being developed by our team is an on-line Department Management System. This System will provide the functionality for maintaining Student’s attendance & marks according to their stream & semester. It will also provide for publishing important announcements in the form of notices. This system will also provide subject-wise result view for teachers. The administrators can also upload various files such as syllabus, previous year’s papers which can be downloaded by the students. This system also provide a search functionality for searching a particular student record by specifying his/her enrollment no, stream & semester. Further the teachers can add/update/remove the resources and the resource users from the system. The system also incorporates the option for changing password for both teachers & students. The students can also access their attendance & marks details. They can also view the notices posted by the teachers and can also download various uploaded files. The students can also take up an online test. They can also view video tutorials & access photo gallery. 2.2.2 Product Features There are three different users who will be using this product: • Administrator • Registered Customer who will be accessing this system for serching and purchasing the books. Unregistered Customer who will be accessing this system for serchin the books. The features that are available to the Administrator are: • A administrator can maintain the record of books. • Can update/delete the book from database. • Can view customer mybook list. • Can publish various reports by book sold. • Can search for a particular customer record. • Can update their details. Can change their account password. The features available to the Registered Customer are: • Can create/view/update their mybook list. • Can search the book from the database by category/autor name/book name. • Can purchase the book from my book list. • Can update their details. • Can • Can change their account password 2.2.3 Operating Environment: The product will be operating in unix environment. Also it will be compatible with the MS DOS. The only requirement to use this product would be operating system. 2.2.4 Design and Implementation Constraints : The Product is developed using ANSI C++. The backend database for this is Oracle 10.2.0. The product is accomplished with login facility so that specific function is available to specific user.

2.2.5 Assumptions and Dependencies : The product needs following third party product. § Oracle 10g to store the database. §ANSI C++ to develop the Product.

2.3 System Features 2.3.1 Database – Storage. 2.3.1.1 Description and Priority: Proposed Database is intended to store, retrieve, update, and manipulate information related to tarzan book store which include • Administrator information • Registered customer information like username/password • Information about books. • Customers mybook list • Transaction Information. Reports

2.3.1.2 Stimulus / Response Sequences Responses for Administrator: The administrator can Login and Logout. When the Administrator Logs into the system. The system will check for validity of login .If the Login and password are valid, the response to this action is the administrator will be able to modify, view, add, deleting and all other functions that can be performed on the database. Responce for Registered Customer: The registered customer can Login and Logout. When the customer Logs into the system. The system will check for validity of login .If the Login and password are valid, the response to this action is the customer will be able to modify, view, add, deleting his details/mybook list and purchase the book from my book list. Responce for Unregistered Customer: The unregistered customer can search book by category/author name/book name and register to the system.

2.3.2 Functional Requirements This section gives the list of Functional and non functional requirements which are applicable to the System. 2.3.2.1 Interface Requirements This section describes how the software interfaces with other software products or       users for input or output. 2.3.2.1.1UserInterfaces Describes how this product interfaces with the user. This section should include a set of screen dumps or mockups to illustrate user interface features. 1. Description The user interface must be customizable by the administrator 2. Criticality: This issue is essential to the overall system. All the modules provided with the software must fit into this user interface and accomplish to the standard defined. 3. Technical issues: In order to satisfy this requirement the design should be simple and all the different interfaces should follow a standard template. There will be the possibility of changing colors and images, plus switching between interfaces with the minimum impact for the users. 4. Risks: To reduce the circumstances under which this requirement might not able to be satisfied, the --- 5. Dependencies with other requirements: All user interfaces should be able to interact with the user management module and a part of the interface must be dedicated to the login/logout module. 2.4 Non Functional Requirements 2.4.1 Hardware Interfaces Server Side: • Operating System: unix/linix/MS DOS • Processor: Pentium III or higher • RAM: 256 Mb or more • Hard Drive: 20 GB or more Client side: • Operating System: MS DOS, MAC or UNIX. • Processor: Pentium III or higher. • RAM: 256 Mb or more, Hard Drive:20 GB or more 2.4.2 Software Interfaces

• Database: Oracle 10g. • Application: ANSI C++ •Server: - 2.4.3 Communications Interfaces

Anybody can log on to the system to browse through the books available. It should have a facility to search books by category or author name or book name,and also registered to system. 2.5 Other Nonfunctional Requirements 2.5.1 Performance Requirements

The proposed system that we are going to develop will be used as the Chief performance system within the book store which interact with the administrator and customers. Therefore, it is  expected that the database would perform functionally all the requirements that are specified by the book store. 2.5.2 Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure. Therefore, it is required to take the database backup 2.5.3 Security Requirements We are going to develop a secured database. There are different categories of users namely administrator, registered customer and unregistered customer. Depending upon the category of user the access rights are decided. It means if the user is an administrator then he can be able to modify the data, delete, append etc. All other users only have the rights to retrieve the information about database. Software Quality Attributes The Quality of the database is maintained in such a way so that it can be very user friendly to all the users of the database 2.5.4 Hardware Constraints The system requires a database in order to store persistent data. The database should have backup capabilities. 2.5.5 Software Constraints The development of the system will be constrained by the availability of required software such as server,database and development tools. 2.5.6 Design Constraints The system must be designed to allow secure usability. That is, the system must be designed in such a way that will be easy to use and visible on authenticated page.