President's Choice SoftwareFunctional Specification
Management Plan
|
President's Choice Software Functional Specification Management Plan |
| Contents | |||||
| Introduction | |||||
| It is the opinion of this company that we can create and supply an easy-to-use and efficient database system for the Springfield Library in a minimal amount of time. We realize the focus of the system in relation to the ergonomic and efficiency concerns, and our design will keep these ideas central without compromising the purpose of the system. A structural outline of a proposed system has already been initiated which includes all of the major aspects included in the informal specifications that were supplied to us by your company. A preliminary time frame has also been sketched out so that you can get a rough idea as to how we intend to progress through this contract with a general completion time. Thus all of the preparations can be made before the system finally arrives. Likewise, it is our belief that we can supply a workable prototype that performs all of the operations that are specified in this document by the beginning of March, 1997. It is our hope that the Springfield Library will find that our system fulfills their needs accurately, efficiently and reliably. |
| Ease Of Use, Speed, Reliability | In the specifications we received from your company it was apparent that certain considerations must be made when designing the library system. At the forefront were concerns of ease of use, speed, and reliability. In relation to your concern for speed, it seems that the majority in the computer industry, staff and companies are generally making efforts to find ways to increase the speed of their hardware, software, systems, etc. and it is likewise the case for our company also. Suffice to say, our programmers are always thinking of new ways to increase the speed and efficiency of the systems they work on. We know that we can supply an extremely efficient system that will meet your needs. As to the considerations for ease of use and reliability, every step of the implementation will be designed with these concerns prevalent. Along with this, extensive testing will used to ensure that these criteria have been fulfilled. Keeping in all this in mind, it is our policy to develop the best possible system while maximizing and utilizing your initial capital investment. Other considerations that will be kept in mind as the system progresses are expandibilty, appearance, and consistency in development. |
| The actual software used to implement this system has not been fully agreed upon at this time. It is our intention to used established software to implement your library system. There are numerous reasons for this: |
|
| Specific considerations influencing our decision for which software we will use are cost, user interface (ie. how easily YOU can use the system), simplicity of programming, portability, efficiency, expandibility, and versatility. The current possibilities are: Delphi, Access, Psybase, and Oracle. You will be informed as to our particular choice BEFORE implementation of the prototype has begun. |
| Structural Outline |
| The preliminary designs that we are contemplating have three main sections: Book Administration, Customer Administration, and Transaction Forms. |
| Book Administration | The Book Administration section deals specifically with manipulating and archiving book data. The section is broken down into five sub-sections that will have selections as follows: Add a Book, Delete a Book, Book search, Modify book data, and an option which will allow you to generate a number of different reports. |
| Add A Book | The "Add a Book" option allows you to add a new book to the database which will then be within the system so that it can be borrowed. The data attributes included for each book are as follows: |
The 'Available' category seems to be missing. Please add it. Also 'Book Category' seems to be missing from this list. Please add it as well. |
| Note that this is merely a preliminary list as there might be additions or deletions in the future by your direction. |
| Delete A Book | The "Delete a Book" option allows you to permanently remove a book from the database. In order for a book to be deleted, both the ISBN number and the Call number must be used to identify the specific book to be deleted. Currently, no option will be constructed to allow for deleted books to be recovered. |
| Modify Book Data | The "Modify Book Data" option allows you to change the information about a book that has been stored in the database. Adhereing to the policy stipulated in your specifications, the ISBN number can not be changed. If it were the case that an ISBN number must be changed, you must delete the book first with the "Delete a Book" function followed by going through the "Add a Book" function to re-introduce the book back into the system with the correct ISBN number. |
| Book Search | The "Book Search" option allows you to find a book or a list of books that fall under a criteria specified by you. The preliminary criteria that will be allowable for a search are searches by: |
|
| Note that this is just a preliminary list and might be expanded in the future. |
| Generate A Report | The "Generate a Report" option allows you to view and print lists and reports which would include the following: All books or some defineable subset of the books; all overdue books; and all books in circulation. The subset of all the books has not, at this time, been clearly defined, but might be based on one or all of the following: |
|
| Again these lists are still in the preliminary stages and should in no way be construed as to be etched in stone. |
| Customer Administration | The Customer Administration section deals specifically with manipulating and using customer data. This section can be broken down into four sub-sections: Add a New Customer, Remove a Customer, Modify Customer Data, and Generate a Customer Report. |
| Add A New Customer | The "Add a New Customer" option allows you to add a new costomer to the database. This new customer is then allowed to borrow books, elicite fines, and has access to the normal functions allowable for a regular customer. The data attributes included for each customer are as follows: |
|
| Note that this is just a preliminary list and might be expanded in the future. |
| Remove A Customer | The "Remove a Customer" option allows you to permanently remove a customer from the database. In order for a customer to be deleted, the User Identification number must be used to identify the specific customer to be removed. As has been stipulated in the specifications, no customer can be deleted if he/she has a book on loan or has any outstanding fines. As with the "Delete a book" option, no process has been initiated that allows for deleted customers to be recovered. |
| Modify Customer Data | The "Modify Customer Data" option allows you to change the information about a customer that has been stored in the database. The User Identification number cannot be changed. If it were the case that an User Identification number must be changed, you must delete the customer first with the "Remove a Customer" function followed by an "Add a New Customer" process to re-introduce the customer back into the system with the correct User Identification number. Some data, such as the Max Books and the Max Fines, can only be changed by an individual with supervisor clearance, and cannot be changed otherwise. |
| Customer Search | The "Customer Search" option allows you to find a customer or a list of customers that fall under a criteria specified by you. The preliminary criteria that will be used for customer searches are any of the customer's personal identification. These would include any of the following: |
|
| Generate Report | The "Generate a Customer Report" option allows you to view and print lists and reports which would include the following: All customers or some defineable subset of them; customers with books on loan; customers with overdue books; and customers with outstanding fines. The subset of all the customers has not, at this time, been clearly defined, but might be based on one or all of the following: |
|
| Again these lists are still in the preliminary stages and should in no way be construed as to be unchangable. |
| Transactions | The Transaction section deals specifically with borrowing, returning, renewing books and putting books on hold. This section is broken down into four sub-sections: Borrowing Books, Returning Books, Renewing Books, and Placing on Hold. |
| Borrowing A Book | To borrow a book, our system interfaces with an external mechanical device which scans and obtains information such as the customer's identification number (from their user card), ISBN number, and call number from the book. A customer may not borrow a book, if their fine limit has been reached. Our system will generate a due date in accordance with the loan duration specified for the particular media type. |
| Returning A Book | When a book is returned, it is made available for others to be borrowed, or, if the book has been placed on hold, the individual for which the book has been held will be notified. |
| Renewing A Book | The renewing a book process merely updates the due date pending that the book is not on hold, and successful validity checks executed under the borrowing a book process have been performed. |
| Holding A Book | Putting books on hold is a process which allows a customer to restrict a books availability to general customers so that he/she is ensured of being next to receive a particular book that is currently on loan. Only one hold can be placed on any one particular book copy. Holds are placed on a first come first serve basis. Any one customer can place as many holds as his book limit regardless of how many books he currently has on loan. Once a book on hold is made available, the customer has 3 days to either pick up the book or cancel his/her hold. If the customer has undertaken neither of the two options before the 3 day limit has expired, the customer is charged with 3 overdue days upon that book. |
| Possible Enhancements |
| There are numerous enhancements that could possibly be implemented to make the system easier to use and/or more versatile in execution. One such enhancement that was already mentioned is the possiblilty to store, access and possibly reinstate a deleted book or customer. Another main ideas is to incorporate more automatic functions to take the work out of the user's hands. On the prelimary sketches, a few tasks are inked in to be automatic (ie. generating a call number or User Identification number), but many others might have to be implemented as manual tasks due to lack of time. Examples of these such options would be checks for books on loan before deletion is allowed, and a similar check for deletion of customers. Other enhancements could include: |
|
| TimeLine |
 |
| The above is a breakdown of our time distrabution planned for the ensuing project. We have estimated that there will be five major sections that will follow one after the other. |
| Functional Specification | The first section is the Functional Specification and Management Plan. This section can be further broken down into three parts: User Interaction, the Management Plan, and the Final Summary. User interaction is scheduled from January 16 - 25, 1997; the Management Plan is scheduled from January 17 - 27, 1997; and the Final Summary is scheduled from January 24 - 27, 1997. |
| Overall Design | The second section is the Overall Design Specifications. This section is broken down into three parts: major and sub-modules design, modification and management remarks, and the final summary. Modules design is scheduled from January 27 to February 8; modifications and management remarks is schedualed from February 8 - 10; and the summary from February 9 - 11. |
| Detailed Design | The third section is the Detailed Design which will act with direct correlation to the implementation phase and testing phase. This section is broken down into three parts: prototype programming; prototype testing; and summary. The programming and testing phases are rather hard to specify, but the prototype programming is tentatively scheduled from February 12 -20, and the testing from February 15 - 25; the summary is scheduled from February 26 - 27. The testing will be carefully planned with numerous sets of tests implemented to ensure accuracy. |
| User Manual | The fourth section is the writing of the user manual. The actual writing of the user manual will be performed in three phases including outline, detailed draft, and final proof. The outline is schedualed from February 28 to March 1; the detailed write up is schedualed for March 2 - 12; and the final proof is is schedualed for March 13 - 18. The user manual will be concerned with how to use our system, error recognition and handling, and numerous examples as to how the processes are used. |
| Prototype | The fifth and final section will be the prototype demonstation for your company. The demonstration is tentatively scheduled for some time between March 31 and April 14, 1997. |
We were wondering about the minimal system - Does PC Software plan to deliver a fully functional system by April 14th or just a partial implementation? If only a partial system can be delivered, which features does the company anticipate providing?
| Summary |
| To conclude, here is a list of the main features mentioned in this document: |
|
| Conclusion | The system design and implementation prosses for the library system has already been tentatively scheduled culminating in the prototype demonstration performed for your company some time in early April, 1997. It is the belief that we at PC Software Inc. will provide for you a comprehensive and efficient system that will meet your needs by that time. It is our hope that your experience with our company will be a pleasant and mutually benificial undertaking. |
Send mail to the Group Leader
or the Webmaster
Back to the Main Page